Removing a Module from an Active Device

Release Notes for 07.8.04

Removing a Module from an Active Device

Before you remove a module from a routing switch in operation, first disable the module. Disabling the module before removing it prevents a brief service interruption on other unmanaged modules. The brief interruption can be caused by the device re-initializing other modules when you remove an enabled module.

NOTE: This section does not apply to the active or standby Redundant Management modules. The disable module and enable module commands are not supported on management modules.

To disable a module, enter the following command at the Privileged EXEC level of the CLI:

disable module <slot-num>

Where <slot-num> specifies the slot number as follows:

•Slots in a 4-slot chassis are numbered 1 – 4, from top to bottom.

•Slots in an 8-slot chassis are numbered 1 – 8, from left to right.

•Slots in a 15-slot chassis are numbered 1 – 15, from left to right.

Example

ProCurve 9300# disable module 3

This command disables the module in slot 3.

NOTE: If you remove the module without first disabling it, the routing switch re-initializes the other modules in the device, causing a brief interruption in service after which the device resumes normal operation.

You do not have to enable a module after inserting it in the chassis. The module is automatically enabled when you insert the module into a running device or when you power on the device.

To replace a removed module with a different type of module, you must configure the slot for the new module. To configure a slot for a module, use the module command at the global CONFIG level of the CLI.

After disabling a module, if you decide not to remove the module, re-enable the module using the following command:

enable module <slot-num>

Example

The following command re-enables the module in slot 3:

ProCurve 9300# enable module 3

Configuring the ProCurve 9315M

When configuring a ProCurve 9315M 15-slot routing switch, take into account the guidelines and restrictions in this section.

Minimum Software Release Supported

The ProCurve 9315M requires software release 07.5.04 or greater.

NOTE: On a ProCurve 9315M, software release 07.5.04 is the earliest release supported. If a management module is running software earlier than release 07.5.04, you cannot upgrade the module in a 9315M chassis. Instead, you must upgrade it in a 9304M or 9308M chassis. For more information, see “Upgrading Software on an M2, M4, or EP Management Module to Release 07.8.04a” on page 7.

14