The Modular Cisco Catalyst switches, such as the 6500, 6000, 5500,
5000, 4500, and 4000 Series, support Online Insertion and Removal (OIR) or Hot
Swap of all modules (power supplies, fan trays, Supervisor Modules and other
Line and Service Modules). You can add, replace, or remove modules without
interrupting the system power or causing other software or interfaces to shut
down.

This document provides some simple checks you can carry out when you
move modules to a different chassis or when you insert new modules into a
chassis.

The OIR feature was developed to enable you to replace faulty parts
without affecting system operation. When a card is inserted, power is available
on the card, and it initializes itself to start working.

When you remove or insert a module while the switch is powered on and
operating, this is what the switch does:

Determines if there is sufficient power for the
module.

Scans the backplane for configuration changes.

Initializes all newly inserted modules, notes any removed modules,
and places them in the administratively shutdown state.

Places any previously configured interfaces on the module back to the
state they were in when they were removed. Any newly inserted interfaces are
put in the administratively shutdown state, as if they were present (but
unconfigured) at boot time. If you insert a similar switching-module type into
a slot, the ports are configured and brought online up to the port count of the
original switching module.

Caution: When a module is inserted or removed, the switching bus can sometimes
stall for about 3 seconds. This can disrupt the adjacencies in protocols such
as Open Shortest Path First (OSPF), Border Gateway Protocol (BGP), or
Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP) if their
timers have been configured for fast convergence.

Note: Do not remove or install more than one module at a time. The switch
can bring only an identical replacement module online. If the replacement
module is different from the removed module, you must configure it before the
switch can bring it online.

If you plan to move a blade to a different slot within the same
chassis, you have to check the Release Notes for the Cisco IOS or CatOS version
that the current supervisor runs in order to check if the module that is going
to be moved can be inserted in any slot, or if that module needs to be inserted
in some particular slots.

If you plan to move a module to a different chassis model, make sure
the Cisco IOS or CatOS version that the supervisor engine runs, and the
supervisor itself, support the module to be inserted. The Release Notes for the
IOS or CatOS have to be checked before you move a module to a different
chassis.

These are things to check before you move the module:

Does the supervisor run CatOS or Cisco IOS?

Verify if the CatOS or Cisco IOS version supports the module to be
inserted.

Verify if the supervisor supports the module that is going to be
inserted.

Verify if the module needs to be inserted in certain slots
only.

In this example, there are two chassis:

A 6506 chassis with:

WS-X6K-SUP1A-2GE that runs in Hybrid mode 6.4(19) + MSFC
12.(11b)

WS-X6408A-GBIC

A 6509 chassis with:

WS-SUP32-GE-3B that runs in Native mode
12.2(18)SXF7

WS-X6516A-GIBIC

In this example, both GBIC modules will be swapped. This is how the
configuration looks:

First, you need to check the Release Notes for Cisco IOS Software
Release 12.2(18)SXF7 which is the version that Supervisor Engine 32 runs. You
need to check if this IOS supports module WS-X6408A-GIBIC.

Then, you need to take a look at which supervisors support module
WS-X6408A-GIBIC. As you can see in the Release Notes, only Supervisor Engine
720, Supervisor Engine 32 and Supervisor Engine 2 support this module.

Finally, you need to check the minimum IOS each supervisor requires to
support module WS-X6408A-GIBIC.

Supervisor

Minimum IOS

With Supervisor Engine 720

12.2(14)SX

With Supervisor Engine 32

12.2(18)SXF

With Supervisor Engine 2

12.2(17d)SXB

Note: Each supervisor requires a minimum IOS version in order to support a
module.

If you search for module WS-X6516A-GBIC, you will see that "The
WS-X6516A-GBIC version of this module is not supported in software release 6.x.
The WS-X6516A-GBIC version is supported in software release 7.5(1)."

In this case, for Supervisor Engine 1 to support module WS-X6516A-GBIC,
the supervisor needs to be upgraded to at least CatOS version 7.5(1).

Note: DRAM memory requirements need to be checked if you attempt a software
upgrade.

After the changes have been saved, remove the module from the
chassis.

Once the module is physically removed from the chassis, the
configuration will also be removed from the show run
command output.

Note: The side effect of this CLI is that all the configuration related
to the removed module will be deleted. Also, when the card is re-inserted, all
of the deleted configuration needs to be re-entered.

Once the old configurations for the non-present modules have been
cleared from the configuration, the SNMP MIB configuration for those
non-present modules should be removed as well.

After you physically remove a module from the chassis, the
configuration for the module still appears. This is actually left in by design
to allow for easier replacement. If the same type of module is inserted, it
will use the already configured module configuration. If another type of module
is inserted into the slot, the module configuration is cleared.

If the module clear-config command is not
applied before you remove the module and is applied after you remove the
module, then this command will only go into effect when you add modules from
this point forward so it will not clear the current state. This means that the
configuration for a non-present module will remain until a different model of
module is inserted. As soon as a different model of module is inserted, then
the configuration will be removed from the show run
command output.

show module—Displays the module status and
information. In the Mod Sub-Module fields, the show
module command displays the supervisor engine number but appends
the module type and information of the uplink daughter card.

If you have checked that the power supplies deliver enough power to
turn on all of the modules, then enter the power enable module
[module slot number] command in order to
enable the power for the module that appears as PwrDeny:

Switch(config)#power enable module 4

If you are still unable to determine the problem, or if the error
message is not present in the documentation, contact the
Cisco
Technical Support escalation center.