Can occupy any slot in any Cisco Catalyst 6503-E, 6504-E, 6506, 6506-E, 6509, 6509-E, 6509-V-E, or 6509-NEB-A chassis; or Cisco 7604, 7606, 7609, or 7600-S Series chassis Can occupy only slots 9 through 13 in a Cisco Catalyst 6513 or Cisco 7613 chassis.
- Cisco 6506 Chassis Supervisor Slot For Sale
- Cisco 6506 Chassis Supervisor Slot Free
- Cisco 6506 Chassis Supervisor Slot Tool
Dear ARS networking gurus,
I need to upgrade our two Cisco 6506 chassis to two 6509E. We have confirm from Cisco and our Cisco equipment vendor that our modules and power supplies are transferable from one chassis to the other.
Below are the module and SW version info.
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX 00000000000
2 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX 00000000000
3 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX 00000000000
4 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX 00000000000
5 5 Supervisor Engine 720 10GE (Active) VS-S720-10G 00000000000
6 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX 00000000000
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 0000.0000.0000 to 0000.0000.0000 2.9 12.2(14r)S5 12.2(33)SXI4 Ok
2 0000.0000.0000 to 0000.0000.0000 2.9 12.2(14r)S5 12.2(33)SXI4 Ok
3 0000.0000.0000 to 0000.0000.0000 2.9 12.2(14r)S5 12.2(33)SXI4 Ok
4 0000.0000.0000 to 0000.0000.0000 2.8 12.2(14r)S5 12.2(33)SXI4 Ok
5 0000.0000.0000 to 0000.0000.0000 2.0 8.5(2) 12.2(33)SXI4 Ok
6 0000.0000.0000 to 0000.0000.0000 2.8 12.2(14r)S5 12.2(33)SXI4 Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
1 Centralized Forwarding Card WS-F6700-CFC 00000000000 2.1 Ok
2 Centralized Forwarding Card WS-F6700-CFC 00000000000 4.1 Ok
3 Centralized Forwarding Card WS-F6700-CFC 00000000000 4.1 Ok
4 Centralized Forwarding Card WS-F6700-CFC 00000000000 4.0 Ok
5 Policy Feature Card 3 VS-F6K-PFC3C 00000000000 1.0 Ok
5 MSFC3 Daughterboard VS-F6K-MSFC3 00000000000 1.0 Ok
6 Centralized Forwarding Card WS-F6700-CFC 00000000000 4.0 Ok
I do not have experience on such migration and I was wondering if you guys can share your expertise on this.
Below are the questions I have:
1. hardware compatibility: Have you experience any hardware migration issue?
2. software compatibility: Will existing SW version from 6506 work on 6509E?
3. migration steps:
a. turn off both 6506
1. proper steps of shutting it down
b. take out modules
c. install power supplies 6909E chassis
d. install sup on both chassis
e. power it on and test
f. install other modules
Thanks for reading and any advice will be greatly appreciated.
Henry
Contents
Introduction
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.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on the Cisco Catalyst 6500 Series Switch with Supervisor Engine 720 and running Cisco IOS® Software Release 12.2(18)SXD6.
The information in this document was created from the devices in a specific lab environment. If your network is live, make sure that you understand the potential impact of any command.
Related Products
This configuration can also be used with these Cisco Catalyst switches:
Cisco Catalyst 6000 Series
Cisco Catalyst 5500 Series
Cisco Catalyst 5000 Series
Cisco Catalyst 4500 Series
Cisco Catalyst 4000 Series
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Background Information
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.
Online Insertion and Removal of Modules
Checklist for Online Insertion and Removal
In this section, you are presented with the list of items to be checked before you perform an online insertion and removal of modules:
Verify if the module is supported by the supervisor engine of the destination switch.
Verify if the module is supported by the release of OS (IOS or CatOS) that runs on the destination switch.
Verify if the module can be placed in the choosen slot on the destination switch.
Move the Module to a Different Slot in a Same Switch
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.
For example, module WS-X6748-SFP in a 13-slot chassis with a supervisor that runs Cisco IOS Software Release 12.2SX is only supported in slots 9 through 13 and does not power up in other slots. This information can be found in the Release Notes for Cisco IOS Release 12.2SX on the Supervisor Engine 720, Supervisor Engine 32, and Supervisor Engine 2.
Move the Module to a Different Switch
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:
Cisco 6506 Chassis Supervisor Slot For Sale
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.
As seen in the Release Notes for Cisco IOS Release 12.2SX on the Supervisor Engine 720, Supervisor Engine 32, and Supervisor Engine 2, module WS-X6408A-GIBIC is supported for Cisco IOS Software Release 12.2SX.
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.
Then, you need to check if the Supervisor Engine 1 that runs in Hybrid mode supports module WS-X6516A-GIBIC. Because the supervisor runs CatOS, you need to check the Release Notes for Catalyst 6000 Family Software Release 6.x.
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.
Erase Configurations Related to a Module
Before the Module is Removed
If a module is physically removed and the configuration is not needed anymore, then apply the module clear-config command from the global configuration mode before you physically remove the module.
Note: The module clear-config command is currently available only in Cisco Catalyst 6500/6000 Series Switches.
Note: The command works when applied before you remove the module.
This is an example of the command usage from the switch:
Complete these steps:
Apply the module clear-config command in global configuration mode.
Once the command is applied and the configuration is saved, check the output of the show run command to see if the command is there.
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 the Module is Removed
Cisco 6506 Chassis Supervisor Slot Free
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.
Verify
Use this section to confirm that your configuration works properly.
The Output Interpreter Tool (registered customers only) (OIT) supports certain show commands. Use the OIT to view an analysis of show 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.
Troubleshoot
Use this section to troubleshoot any issues with the newly inserted modules.
Module Status is Minor Error
Cisco 6506 Chassis Supervisor Slot Tool
After you insert a module into a slot, the module shows a status of Minor Error from the show module command output. This is probably due to a bad module, a bad slot, or a badly seated module.
Perform these steps in order to recover the module. Schedule a maintenance window in case the switch is in production and perform these actions:
Turn on the diagnostics to a complete level, so when the switch is reloaded detailed information about the modules is displayed.
Issue the hw-module module [module slot number] reset command in order to reset a particular module.
Enter the show environment command in order to check any possible alarms about the module. Enter the show diagnostic module [module slot number] command.
If you still receive errors after you reset the module, then complete these steps:
Reseat the module. Physically reseat the module.
Check the output of the show environment command.
Enter the show diagnostic module [module slot number] command.
If the module still shows up with a minor error after these steps, then complete these next steps:
Try the module in a different slot.
Check the output of the show environment command.
Enter the show diagnostic module [module slot number] command.
Module Status is Unknown / PwrDown
After a module was inserted, the status of this module shows up as Unknown in the show module command output.
This output shows the status of module WS-X6748-GE-TX as Unknown:
When a module appears as Unknown on the show module command output, make sure you check these:
The supervisor engine and the software it runs support the module.
The specifications of the module. Make sure the module can be inserted in any slot or if it can only be inserted in specific slots.
Note: For both options, check the Release Notes of the software version that the supervisor engine runs.
Module Status is Unknown / PwrDeny
After you insert a module, the status of it is PwrDeny. If this is the case, check if there is enough power to turn on the module that appears as PwrDeny.
This output shows two modules with a status of Unknown / PwrDeny:
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:
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.