Feb 13, 2018 Product Overview. Cisco introduces the Cisco ® Catalyst ® 6500 Enhanced Series Chassis (6500-E Series) delivering up to 2 terabits per second of system bandwidth capacity and 80 Gbps of per-slot bandwidth. In a system configured for VSS, this translates to a system capacity of 4 Tbps. The Cisco ® Catalyst ® 6500 Enhanced Series Chassis will be capable of delivering up to 180 Gbps of per. Feature Cisco Catalyst 6500 Series Chassis Configurations. 3-slot. 6-slot. 9-slot. 9 vertical slots. 13-slot Backplane Bandwidth. 32-Gbps shared bus. 256-Gbps switch fabric. 720-Gbps switch fabric Layer 3 Forwarding Performance. Cisco Catalyst 6500 Supervisor Engine 1A Multilayer Switch Feature Card (MSFC2): 15 mpps.
- Cisco 6506 Chassis Supervisor Slot Machine
- Cisco 6506 Chassis Supervisor Slot Software
- Cisco 6506 Chassis Supervisor Slot Set
- Cisco Blade Chassis
The Catalyst 6500 is a modular chassisnetwork switch manufactured by Cisco Systems since 1999, capable of delivering speeds of up to '400 million packets per second'.[1]
A 6500 comprises a chassis, power supplies, one or two supervisors, line cards and service modules. A chassis can have 3, 4, 6, 9 or 13 slots each (Catalyst model 6503, 6504, 6506, 6509, or 6513, respectively) with the option of one or two modular power supplies. The supervisor engine provides centralised forwarding information and processing; up to two of these cards can be installed in a chassis to provide active/standby or stateful failover. The line cards provide port connectivity and service modules to allow for devices such as firewalls to be integrated within the switch.
- 2Operating systems
- 3Methods of operation
- 4Power supplies
- 4.1Chassis support
- 4.2Power redundancy options
Supervisor[edit]
The 6500 Supervisor comprises a Multilayer Switch Feature Card (MSFC) and a Policy Feature Card (PFC). The MSFC runs all software processes, such as routing protocols. The PFC makes forwarding decisions in hardware.
The supervisor has connections to the switching fabric and classic bus, as well as bootflash for the Cisco IOS software.
The latest generation supervisor is the Supervisor 2T.This supervisor was introduced at Cisco Live Las Vegas in July 2011.It provides 80 gigabits per slot on all slots of 6500-E chassis.
Operating systems[edit]
The 6500 currently supports three operating systems: CatOS, Native IOS and Modular IOS.
CatOS[edit]
CatOS is supported for layer 2 (switching) operations only. To be able to perform routing functions (e.g. Layer 3) operations, the switch must be run in hybrid mode. In this case, CatOS runs on the Switch Processor (SP) portion of the Supervisor, and IOS runs on the Route Processor (RP) also known as the MSFC. To make configuration changes, the user must then manually switch between the two environments.
CatOS does have some functionality missing and[2] is generally considered 'obsolete' compared to running a switch in Native Mode.
Native IOS[edit]
Cisco IOS can be run on both the SP and RP. In this instance, the user is unaware of where a command is being executed on the switch, even though technically two IOS images are loaded—one on each processor. This mode is the default shipping mode for Cisco products and enjoys support of all new features and line cards.
Modular IOS[edit]
Modular IOS is a version of Cisco IOS that employs a modern UNIX-based kernel to overcome some of the limitations of IOS.[3] Additional to this is the ability to perform patching of processes without rebooting the device and in service upgrades.
Methods of operation[edit]
The 6500 has five major modes of operation: Classic, cef256, dcef256, cef720 and dcef720.
Classic Bus[edit]
The 6500 classic architecture provides 32 Gbit/s centralised forwarding performance.[4] The design is such that an incoming packet is first queued on the line card and then placed on to the global data bus (dBus) and is copied to all other line cards, including the supervisor. The supervisor then looks up the correct egress port, access lists, policing and any relevant rewrite information on the PFC. This is placed on the result bus (rBus) and sent to all line cards. Those line cards for whom the data is not required terminate processing. The others continue forwarding and apply relevant egress queuing.
The speed of the classic bus is 32gb half duplex (since it is a shared bus) and is the only supported way of connecting a Supervisor 32 engine (or Supervisor 1) to a 6500.
cef256[edit]
This method of forwarding was first introduced with the Supervisor 2 engine. When used in combination with a switch fabric module, each line card has an 8Gbit/s connection to the switch fabric and additionally a connection to the classic bus. In this mode, assuming all line cards have a switch fabric connection, an ingress packet is queued as before and its headers are sent along the dBus to the supervisor. They are looked up in the PFC (including ACLs etc.) and then the result is placed on the rBus. The initial egress line card takes this information and forwards the data to the correct line card along the switch fabric. The main advantage here is that there is a dedicated 8 Gbit/s connection between the line cards. The receiving line card queues the egress packet before sending it from the desired port.
The '256' is derived from a chassis using 2x8gb ports on 8 slots of a 6509 chassis: 16 * 8 = 128, 128 * 2 = 256. The number is doubled because of the switch fabric being 'full duplex'.
dcef256[edit]
dcef256 uses distributed forwarding. These line cards have 2x8gb connections to the switch fabric and no classic bus connection. Only modules that have a DFC (Distributed Forwarding Card) can use dcef.
Unlike the previous examples, the line cards hold a full copy of the supervisor's routing tables locally, as well as its own L2 adjacency table (i.e. MAC addresses). This eliminates the need for any connection to the classic bus or requirement to use the shared resource of the supervisor. In this instance, an ingress packet is queued, but its destination looked up locally. The packet is then sent across the switch fabric, queued in the egress line card before being sent.
cef720[edit]
This mode of operation acts identically to cef256, except with 2x20gb connections to the switch fabric and there is no need for a switch fabric module (this is now integrated into the supervisor). This was first introduced into the Supervisor Engine 720.
The '720' is derived from a chassis using 2x20gb ports on 9 slots of a 6509 chassis. 40 * 9 = 360 * 2 = 720. The number is doubled to the switch fabric being 'full duplex'. The reason 9 slots are used for the calculation instead of 8 for the cef256 is that it no longer needs to waste a slot with the switch fabric module.
dcef720[edit]
This mode of operation acts identically to dcef256, except with 2x20gb connections to the switch fabric.
Power supplies[edit]
The 6500 is able to deliver high densities of Power over Ethernet across the chassis. Because of this, power supplies are a key element of configuration.
Chassis support[edit]
The following goes through the various 6500 chassis and their supported power supplies and loads.
6503[edit]
The original chassis permits up to 2800W and uses rear-inserted power supplies different from the others in the series.
6504-E[edit]
This chassis permits up to 5000W (119A @ 42V) of power and, like the 6503, uses rear-inserted power supplies.
6506, 6509, 6506-E and 6509-E[edit]
The original chassis can support up to a maximum of 4000W (90A @ 42V) of power, because of backplane limitations. If a power supply above this is inserted, it will deliver at full power up to this limitation (i.e. a 6000W power supply is supported in these chassis, but will output a maximum of 4000W).
The 6509-NEB-A supports a maximum of 4500W (108A @ 42V).
With the introduction of the 6506-E and 6509-E series chassis, the maximum power supported has been increased to in excess of 14500 W (350A @ 42V).
6513[edit]
This chassis can support a maximum of 8000W (180A @ 42V). However, to obtain this, it must be run in combined mode. Therefore, it is suggested that it be run in redundant mode to obtain a maximum of 6000W (145A @ 42V).
Power redundancy options[edit]
The 6500 supports dual power supplies for redundancy. These may be run in one of two modes: redundant or combined mode.
Redundant mode[edit]
When running in Redundant mode, each power supply provides approximately 50% of its capacity to the chassis. In the event of a failure, the unaffected power supply will then provide 100% of its capacity and an alert will be generated. As there was enough to power the chassis ahead of time, there is no interruption to service in this configuration. This is also the default and recommended way to configure power supplies.
Combined mode[edit]
In combined mode, each power supply provides approximately 83% of its capacity to the chassis. This allows for greater utilisation of the power supplies and potentially increased PoE densities.
In systems that are equipped with two power supplies, if one power supply fails and the other power supply cannot fully power all of the installed modules, system power management will shut down devices in the following order:
- Power over Ethernet (PoE) devices— The system will power down PoE devices in descending order, starting with the highest numbered port on the module in the highest numbered slot.
- Modules—If additional power savings are needed, the system will power down modules in descending order, starting with the highest numbered slot. Slots containing supervisor engines or Switch Fabric Modules are bypassed and are not powered down.
This shut down order is fixed and cannot be changed.
Online Insertion & Removal[edit]
OIR is a feature of the 6500 which allows hot swapping most line cards without first powering down the chassis. The advantage of this is that one may perform an in-service upgrade. However, before attempting this, it is important to understand the process of OIR and how it may still require a reload.
To prevent bus errors, the chassis has three pins in each slot which correspond with the line card. Upon insertion, the longest of these makes first contact and stalls the bus (to avoid corruption). As the line card is pushed in further, the middle pin makes the data connection. Finally, the shortest pin removes the bus stall and allows the chassis to continue operation.
However, if any part of this operation is skipped, errors will occur (resulting in a stalled bus and ultimately a chassis reload). Common problems include:
- Line cards being inserted incorrectly (and thus making contact with only the stall and data pins and thus not releasing the bus)
- Line cards being inserted too quickly (and thus the stall removal signal is not received)
- Line cards being inserted too slowly (and thus the bus is stalled for too long and forces a reload).
See also[edit]
References[edit]
- ^Cisco Catalyst 6500 Series Supervisor Engine 720
- ^Comparison of the Cisco Catalyst and Cisco IOS Operating Systems for the Cisco Catalyst 6500 Series Switch
- ^Cisco Catalyst 6500 Series with Cisco IOS Software Modularity
- ^Cisco Catalyst 6500 Supervisor Engine 32 Architecture
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:
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
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.
Cisco 6506 Chassis Supervisor Slot Machine
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
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:
Cisco 6506 Chassis Supervisor Slot Software
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.
Cisco 6506 Chassis Supervisor Slot Set
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.