Table of Contents
Release Notes for Catalyst 6000 Family for Cisco IOS Release 12.0 XE
Current Release (February 7, 2000): 12.0(7)XE1
Previous Release: 12.0(7)XE (Deferred)
 | Caution
These Release Notes are for the Cisco IOS on the Catalyst 6000 Family Release 12.0 XE Supervisor Software product, which runs Cisco IOS Release 12.0 XE on both the supervisor engine and the MSFC. If you are running Catalyst software on the supervisor engine and Cisco IOS Release 12.0 XE only on the MSFC, refer to the Release Notes for Catalyst 6000 Family Multilayer Switch Feature Card Cisco IOS Release 12.0 XE publication. |
Note For information about the deferral of 12.0(7)XE, refer to the Field Notice at:
http://www.cisco.com/warp/customer/770/fn11211.shtml
This document consists of these sections:
Cisco IOS Release 12.0 XE supports the Catalyst 6000 family switches. Release 12.0 XE is based on Cisco IOS Release 12.0 T.
Release 12.0 XE will be merged into Release 12.1 E, which will eventually be merged into 12.1 T. All maintenance updates will be placed into Cisco IOS Release 12.1 E releases. No maintenance updates will be placed into Release 12.0 XE.
For more information about the Cisco IOS software release process, see the Cisco IOS Software Releases: Product Bulletin #537 located on CCO and on the Documentation CD-ROM.
These release notes do not describe features that are available in Release 12.0, Release 12.0 T, or other Release 12.0 Early Deployment (ED) releases.
For information about features in Release 12.0, see the Cross-Platform Release Notes for Cisco IOS Release 12.0 on CCO and the Documentation CD-ROM.
For information about features in other platforms, see the Release Notes for Cisco IOS Release 12.0 index on CCO and the Documentation CD-ROM.
For a list of the software caveats that apply to Release 12.0(7)XE1, see the "Open Caveats in IOS Release 12.0(7)XE1" section and the "Open Caveats in IOS Release 12.0(7)XE" section, the Caveats for Cisco IOS Release 12.0 T document, and the Caveats for Cisco IOS Release 12.0 document that accompany these release notes. All caveats in Release 12.0 and Release 12.0 T are also in Release 12.0 XE1. The caveats documents are updated for every maintenance release and are located on Cisco Connection Online (CCO) and the Documentation CD-ROM.
Release 12.0 XE requires the following MSFC memory configurations:
- 128-MB synchronous dynamic random-access memory (SDRAM) DIMM
(upgrade from the default 64-MB configuration if necessary)
- 16-MB Flash SIMM
The following Supervisor Engine 1 default memory configurations are acceptable for Release 12.0 XE:
- 64-MB SDRAM DIMM
- 16-MB Flash SIMM
Table 1 lists the minimum supervisor engine version and the current recommended Cisco IOS releases for Catalyst 6000 family modules and chassis.
Table 1: Minimum, Recommended, and Default Cisco IOS Releases
Product Number
append with "=" for spares
| Product Description
| Minimum Software Version
| Recommended Software Version
|
| Supervisor Engine 1
|
WS-X6K-SUP1A-MSFC
| Supervisor Engine 1 with ROMMON version 5.2(1) or later, dual-port 1000BaseX uplinks, with enhanced QoS features1, Policy Feature Card (PFC), and Multilayer Switch Feature Card (MSFC)
| 12.0(7)XE
| 12.0(7)XE1
|
| Ethernet, Fast Ethernet, and Gigabit Ethernet
|
WS-X6416-GE-MT
| 16-Port Gigabit Ethernet MT-RJ with enhanced QoS features
| 12.0(7)XE
| 12.0(7)XE1
|
WS-X6408-GBIC
| 8-Port Gigabit Ethernet GBIC
| 12.0(7)XE
| 12.0(7)XE1
|
WS-X6408A-GBIC
| 8-Port Gigabit Ethernet GBIC with enhanced QoS features
| 12.0(7)XE
| 12.0(7)XE1
|
WS-X6224-100FX-MT
| 24-Port 100FX Multimode MT-RJ
| 12.0(7)XE
| 12.0(7)XE1
|
WS-X6248-RJ-45
| 48-Port 10/100TX RJ-45
| 12.0(7)XE
| 12.0(7)XE1
|
WS-X6248-TEL
| 48-Port 10/100TX RJ-21
| 12.0(7)XE
| 12.0(7)XE1
|
WS-X6024-10FL-MT
| 24-Port 10BaseFL MT-RJ with enhanced QoS features
| 12.0(7)XE
| 12.0(7)XE1
|
| Modular Chassis
|
WS-C6009
| Catalyst 6009 chassis (9-slot)
| 12.0(7)XE
| 12.0(7)XE1
|
WS-C6509
| Catalyst 6509 chassis (9-slot)
| 12.0(7)XE
| 12.0(7)XE1
|
WS-C6006
| Catalyst 6006 chassis (6-slot)
| 12.0(7)XE
| 12.0(7)XE1
|
WS-C6506
| Catalyst 6506 chassis (6-slot)
| 12.0(7)XE
| 12.0(7)XE1
|
1Also supported: WS-X6K-SUP1-2GE with PFC and MSFC.
|
Note The ATM modules (WS-X6101-OC12-MMF or WS-X6101-OC12-SMF), the Multilayer Switch Module (WS-X6302-MSM), and the FlexWAN module (WS-X6182-2PA) are not supported. These modules will remain powered down if detected in the system. They will not affect system behavior.
Table 2 lists the software versions and applicable ordering information for Cisco IOS for the Catalyst 6000 family.
Table 2: Orderable Software Images
| Filename
| Description
| Orderable Product Number (Installed on System)
| Orderable Product Number (Spare UpgradeFloppy Media)
|
c6msfc-boot-mz.120-7.XE1.bin
| Boot loader
| N/A
| N/A
|
c6sup-js-mz.120-7.XE1.bin
| IOS Release 12.0(7)XE1 Enterprise
| SC6IOSA-12.0.7XE
| SC6IOSA-12.0.7XE=
|
c6sup-ds-mz.120-7.XE1.bin
| IOS Release 12.0(7)XE1 Desktop
| SC6IOSB-12.0.7XE
| SC6IOSB-12.0.7XE=
|
c6sup-is-mz.120-7.XE1.bin
| IOS Release 12.0(7)XE1 IP
| SC6IOSC-12.0.7XE
| SC6IOSC-12.0.7XE=
|
c6sup-ds-mz.120-7.XE1.bin
| IOS Release 12.0(7)XE1 IP/IPX
| SC6IOSD-12.0.7XE
| SC6IOSD-12.0.7XE=
|
Note Cisco IOS Release 12.0(7)XE is deferred.
The orderable software images contain the following feature sets:
- The IP feature set includes support for wire speed Layer 2 switching (bridging) and Layer 3 switching (routing). IP routing protocols supported include RIPv1, RIPv2, OSFP, IGRP, EIGRP, EGP, and BGP4.
Note EGP, BGP4 and IS-IS routing protocols require the additional purchase of the InterDomain Routing Feature License (FR-IRC6).
- The IP/IPX feature set adds support for wire speed IPX Layer 3 switching.
- The Desktop feature set adds support for AppleTalk Phase 1/2, DECnet Phase IV, and IS-IS routing.
- The Enterprise feature set adds support for DECnet Phase V and CLNS/OSI routing.
There are no new features in Release 12.0(7)XE1.
Note The spanning-tree portfast command bpdu-guard keyword has been replaced with the bpduguard keyword. The spanning-tree portfast command still accepts the bpdu-guard keyword.
Refer to Chapter 1, "Product Overview," of the Catalyst 6000 Family IOS Software Configuration Guide for the list of features for the Catalyst 6000 family switches available in IOS Release 12.0(7)XE.
For general product information about the Catalyst 6000 family switches, refer to the Catalyst 4000, 5000, and 6000 Family Software Product Bulletin. For general information about the Catalyst 6000 12.0(7)XE IOS Release, refer to the Cisco IOS on the Catalyst 6000 Family Release 12.0(7)XE Supervisor Software Product Bulletin. Catalyst 6000 family switch product bulletins are at:
http://www.cisco.com/warp/public/cc/pd/si/casi/ca6000/prodlit/
These Release Notes describe the following additional features:
With the exception of the following list, all features currently supported by the Catalyst 5.3 software are also supported in IOS Release 12.0(7)XE.
These features are not supported in IOS Release 12.0(7)XE on Catalyst 6000 family switches:
Note Wire-rate ACLs are supported.
- QoS for Internetwork Packet Exchange (IPX)
- QoS for MAC-layer traffic
- Accelerated server load balancing (ASLB)
- Hot Standby Router Protocol (HSRP) between redundant supervisor engines
Note HSRP to external routers is supported.
- Catalyst software port security feature
- Common Open Policy Server (COPS)
- Resource Reservation Protocol (RSVP)
- GARP VLAN Registration Protocol (GVRP)
- GARP multicast registration protocol (GMRP)
- VLAN Management Policy Server (VMPS) client or server
- Remote SPAN (RSPAN)
- CiscoView
- CiscoWorks2000
Many of the above features will be supported in future IOS versions.
This section provides usage guidelines and restrictions for the Catalyst 6000 family switches.
- Ensure that the sum of the logical interfaces across all instances of spanning tree for different VLANs does not exceed 4000. The sum of all logical interfaces equals the number of trunks and channels on the switch times the number of active VLANs on that trunk, plus the number of nontrunking interfaces on the switch.
Note When numerous protocol features (such as VTP pruning, EtherChannel, and RMON) are enabled concurrently, the number of supported logical spanning tree interfaces is reduced. To achieve these numbers, keep switched traffic off the management VLAN.
- You must have a boot loader image in the MSFC bootflash: device to boot successfully. Do not reset the switch when there is no boot loader image in the MSFC bootflash: device. If there is no boot loader image in the MSFC bootflash: device and the state of the switch does not support the copy command, see the "Recovering From Loss of the Boot Loader Image" section.
- Integrated Routing and Bridging (IRB) and Concurrent Routing and Bridging (CRB) have deliberately been disabled on the Catalyst 6000 family switches. Routable Layer 2 VLANs and VLAN interfaces should be used for normal bridging and inter-VLAN routing. Bridge groups are supported only to bridge non-routable protocols.
- The Ethernet interfaces on a standby supervisor engine are always active.
- All Ethernet interfaces on all modules, including those on a standby supervisor engine, support EtherChannel (maximum of eight interfaces) with no requirement that interfaces be contiguous or on the same module.
- All Ethernet interfaces on all modules support Inter-Switch Link (ISL) and 802.1Q VLAN trunking.
- The link state messages (LINK-3-UPDOWN and LINEPROTO-5-UPDOWN) are disabled by default. Enter a logging event link status command on each interface where you want the messages enabled.
- You can specify the Catalyst 6000 family switch as the MLS route processor (MLS-RP) for Catalyst 5000 family switches using MLS. Refer to the Layer 3 Switching Configuration GuideCatalyst 5000 Family, 4000 Family, 2926G Series, 2926 Series, 2948G for MLS configuration procedures.
- Cisco IOS Release 12.0(7)XE and subsequent releases support:
- The data-link switching plus (DLSw+) feature.
- The Web Cache Control Protocol (WCCP) feature, versions 1 and 2.
- The IP HTTP server feature is disabled by default. Enter an ip http server command to use the feature.
- The IOS show controllers command generates no output on a Catalyst 6000 family switch. Use the show module command.
- With QoS disabled, an EtherChannel can contain interfaces with both strict-priority queues and interfaces without strict-priority queues. With QoS enabled, an EtherChannel cannot contain both interface types. If you enable QoS, interfaces drop out of any EtherChannels that contain both interface types.
- To avoid the case where all traffic is out of profile, the burst size specified in a QoS policing rule must be at least as large as the maximum packet size permissible in the traffic to which the rule is applied.
- When using the Network Address Translation (NAT) router feature on the Catalyst 6000 packets traversing the NAT outside interface might, under certain configurations, be software routed instead of being Layer 3 switched, regardless of whether they should or should not be translated. For packets traversing the NAT outside interface, only those packets requiring NAT should be software routed. IOS only translates traffic that is traversing from NAT inside to NAT outside interfaces and vice versa.
- Make the ACL used for NAT more specific to limit the software-handled packets to only those packets requiring NAT translation. For example, if you use a general ACL (such as permit ip any any) to specify the traffic that requires NAT, then all traffic inbound or outbound on the NAT outside interface will be software routed (including traffic not originating or destined to NAT inside interfaces). If it is possible to use a more specific ACL (such as permit ip 10.1.1.0 0.0.0.255 any), then only the NAT outside traffic matching that ACL will be software routed. This traffic will still be software routed regardless of whether it is originating or destined to NAT inside interfaces. However, by making the ACL more specific, you can limit the amount of traffic that is software routed due to the NAT ACL.
- By default, the Catalyst 6000 family switch sends Internet Control Message Protocol (ICMP) unreachables when a packet is denied by an access group; these access-group denied packets are not dropped in hardware but are bridged to the MSFC so it can generate the ICMP-unreachable message. To drop access-group denied packets in hardware, you must disable ICMP unreachables using the no ip unreachables interface configuration command. Note that the ip unreachables command is enabled by default.
- MAC address-based IOS ACLs are not supported for packets shortcut in hardware. MAC address-based IOS ACLs will be applied on software-switched packets.
- If you enable multicast routing globally, then you should also enable multicast routing (using the ip pim command) on all Layer 3 interfaces on which you anticipate receiving IP multicast traffic. This command causes the packets to be sent to the process switching level for creating the route entry. However, if you disable multicast routing on the RPF interface, then the entry cannot be created and the packet is dropped. If the source traffic rate exceeds what can be handled by the process level, it can have an undesirable impact on the system. For instance, routing protocol packets such as EIGRP hello packets might get lost.
- 24-port 100FX switching modules (WS-X6224-100FX-MT) with a hardware version of 1.1 or lower only support IEEE 802.1Q VLAN trunking; they do not support ISL trunking. Do not configure ISL trunks on 24-port 100FX switching modules (WS-X6224-100FX-MT) with a hardware version of 1.1 or lower. The restriction against ISL VLAN trunking is the only known problem with hardware version 1.1 or lower of these modules. If you do not require ISL VLAN trunking, these modules are fully functional. The ISL VLAN trunking problem has been corrected in hardware version 1.2 or later. If you wish to return a WS-X6224-100FX-MT module with a hardware version of 1.1 or lower, contact Cisco Systems. You can identify WS-X6224-100FX-MT hardware versions using one of the following two methods:
- Command line interface (CLI) methodUse the show module command to identify the hardware version of the WS-X6224-100FX-MT module.
- Physical inspection methodThe part number is printed on a label on the outer edge of the component side of the module. Versions 73-3245-04 or lower do not support ISL trunking.
- The RJ-21 connectors on the 48-port 10/100TX switching module (WS-X6248-TEL) do not support Category 3 RJ-21 telco connectors and cabling. Category 3 connectors and cabling cause carrier sense errors. Use Category 5 RJ-21 telco connectors and cables (the module is keyed for Category 5 telco connectors and cables).
- The in and out ports displayed in Layer 3 table entries are set by the hardware at the time the entry is created. They are not guaranteed to be accurate in case multiple flows are using the same entry (for example, if the flowmask is 'Dest-only' and some kind of load-sharing is active ) or if the source or destination of the Layer 3 entry move in the Layer 2 topology. Also note that the port information is not always available when the Layer 3 entry is established. This is the case if the destination port of the rewritten packet is unknown when the shortcut is created.
- For EtherChannels, you can configure the QoS trust state and default CoS directly on the EtherChannel interface with the mls qos trust or mls qos cos commands, respectively. These two parameters must be the same for all physical interfaces in the channel. No other QoS queueing configuration commands can be applied to EtherChannel interfaces. Other QoS queueing configuration commands can be applied, however, to individual EtherChannel physical interfaces. Once the physical interfaces are bundled into an EtherChannel, QoS classification, marking, and policing by the Policy Feature Card (PFC) for the channel packets is determined by the service-policy attached to the EtherChannel interface. The service-policies attached to the individual physical interfaces of the EtherChannel do not matter. The same is true for the port-based and VLAN-based QoS state of the EtherChannel interface. You can disable the PFC QoS features using the no mls qos interface configuration command on the EtherChannel interface.
- Software release 12.0 XE does not support the IEEE bridging protocol for bridge groups. You should configure bridge groups to use VLAN-bridge or DEC protocol spanning tree.
- The maximum recommended number of Layer 3 multicast entries is 10 KB. The maximum recommended number of multicast entries supported in the Layer 2 forwarding table is 12 KB.
- After enabling Protocol Independent Multicast (PIM) on an interface, you need to enter the ip mroute-cache command on the interface to enable multicast fast-switching. If you have "no ip mroute-cache" configured, multicast packets that are not hardware switched will go to the process level which increases the load on the router.
- The following RMON, RMON2, and SMON MIB objects are supported:
- RMON-MIB supports etherStats, etherHistory, alarms, events
- RMON2-MIB supports probeConfig and usrHistory
- SMON-MIB supports portCopyTable
This section describes open and resolved caveats in Cisco IOS Release 12.0(7)XE1.
This section describes open caveats in Cisco IOS Release 12.0(7)XE1.
- DLSw Ethernet redundancy is not supported. (CSCdp93599)
- Downloading images to an Intel Value series 200 flash card in the PCMCIA slot may in rare circumstances fail to write a valid image. Downloading during periods of low system activity reduces the likelihood of this failure (see the related resolved CSCdm52806 caveat). (CSCdm52806)
- On the WS-X6408-GBIC 8-port Gigabit Ethernet switching module, when QoS is enabled:
- It is safe to ignore port_rx_enable errors messages displayed following a no shutdown command or reload.
- QoS WRR configuration commands for WS-X6408-GBIC ports are not saved in NVRAM. You must manually reenter any non-default QoS WRR configuration commands for WS-X6408-GBIC ports after reboot.
- Gigabit EtherChannels can contain ports on one or more WS-X6408-GBIC switching modules. Gigabit EtherChannels fail that contain ports on a WS-X6408-GBIC switching module and on a WS-X6K-SUP1-2GE supervisor engine.
- (CSCdp81930)
- Power cycling the standby supervisor is not supported. (CSCdp55523)
- When using the UplinkFast feature, the system does not send out the dummy multicast packets used to notify upstream users of forwarding-path changes. Normal Layer 2 aging is used to delete invalid entries. (CSCdm65881)
- Partial support exists for the following MIBs:
- The CISCO-STACK-MIB supports chassisGrp, moduleGrp, portGrp, and vlanGrp.
- BRIDGE-MIB (RFC 1493) supports all objects, tables, and groups except dot1dBasePortTable, dot1dTpPortTable, and dot1DStaticGroup. (CSCdm44194)
- CISCO-FLASH-MIB supports only the route processor bootflash: device.
- CISCO-PROCESS-MIB supports only the route processor.
- CISCO-VLAN-MEMBERSHIP-MIB supports the vmMembershipTable.
- CISCO-STP-EXTENSIONS-MIB supports stpxUplinkFastObjects and stpxBackboneFastObjects. (CSCdp50869)
- These MIBs are not supported:
- CISCO-SWITCH-ENGINE-MIB (CSCdm62652)
- CISCO-COPS-CLIENT-MIB
- CISCO-QOS-MIB
- CISCO-PIB-MIB
- A traceback message displays when you exit the switch console. This message is harmless and can be safely ignored. (CSCdp35517)
- If the system is not booted from a local flash device and the NVRAM configuration is not valid (or present), the service config option defaults to "on." Therefore, since the route processor is booted remotely from a device on the switch processor, the service config feature is enabled after the erase startup-config command is issued. (CSCdp12598)
- The show ibc command misleadingly displays ISL status as "disabled" and the GBIC as "missing." This is because the IBC in this system indicates the internal interface between the switch processor and the route processor. This interface is an electrical connection. As a result trunk and media types are not given for this interface. (CSCdp21121, CSCdp21380)
- The interface range command is not supported by the HTTP user interface. The command will execute on only the first interface in the specified range. The only workaround is not to use the interface range command when using the HTTP interface. (CSCdm54771)
- In a switch with redundant supervisor engines, the slot0: device and the MSFC bootflash: device on the standby supervisor are accessible. The bootflash: device on the standby supervisor is not accessible. Because converting from Catalyst software to IOS requires formatting the supervisor engine bootflash: device, do not convert switches while redundant supervisor engines are installed. With the switch in a non-redundant configuration, do the conversion separately for each supervisor engine, then configure redundancy. (CSCdp55717)
This section describes resolved caveats in Cisco IOS Release 12.0(7)XE1.
- Downloading images to an Intel Series 2+ flash card in the PCMCIA slot may in rare circumstances fail to write a valid image. Downloading during periods of low system activity reduces the likelihood of this failure. This problem is fixed in release 12.0(7)XE1 (see the related still-open CSCdm52806 caveat). (CSCdm52806)
- Removing an aggregate policer might cause a reload. This problem is fixed in Release 12.0(7)XE1. (CSCdp72307)
- Occasionally, following an error that causes a reload, files in the MSFC bootflash:device are corrupted, which might make the MSFC unbootable. This problem is resolved in Release 12.0(7)XE1. (CSCdp53157)
- Occasionally, during a reload caused by an error, the attempt to write the crashinfo file may fail, which causes another reload. The second reload overwrites the crashinfo file from the original error. This problem is resolved in Release 12.0(7)XE1. (CSCdm79471)
- After a system reload, the ip mtu command does not function properly if it was saved with the write memory command. To use the ip mtu command to Layer 3 switch jumbo packets (packets greater than 1500 bytes), you must reenter the command manually after a reload. Note that you must reenter the ip mtu command even though the show running-configuration and show interface commands display the command as already having been entered. This problem is fixed in Release 12.0(7)XE1. (CSCdp59546)
- To ensure correct Layer 3 switching of routed jumbo IP packets, enter an ip mtu <MTU_size> command on the Layer 3 interfaces where you have enabled jumbo frame support with the mtu command. Ensure that the size specified by the mtu command and the ip mtu command is always the same. Enter another ip mtu <MTU_size> command whenever you change the MTU size. To reset the IP MTU value to the default, use the ip mtu <default_size> command, where <default_size> is the default for the interface. Do not use the no ip mtu command. This problem is fixed in Release 12.0(7)XE1 (entry of ip mtu interface commands is no longer necessary to ensure correct Layer 3 switching of routed jumbo IP packets). (CSCdp58561)
- When writing images to a 24-MB Flash PC card, the following messages may be seen:
%HEARTBEAT-2-NOT_RUNNING
- and/or
%SYS-SP-3-CPUHOG
- These messages are harmless and can be ignored. This problem is fixed in Release 12.0(7)XE1. (CSCdp57389)
- You cannot use SNMP to create VLANs. This problem is fixed in Release 12.0(7)XE1. (CSCdp52396)
- Unicast and multicast IP packets may not get properly routed if a multicast boundary is applied to an interface. A workaround is to specify a "permit any any" ACE as the last statement of the ACL associated with the multicast boundary. Note that you cannot configure any other access-group on the interface on which a multicast boundary is configured. This problem is fixed in Release 12.0(7)XE1. (CSCdp22095)
- A trunking interface on a Catalyst 6000 family switch running 12.0(7)XE might change to access mode roughly five minutes after the trunking encapsulation is changed. This event occurs if the interface is configured for trunking, is operating normally as a trunk, and the trunking encapsulation is changed from ISL to 802.1Q, or vice versa, and the interface is not receiving trunking protocol packets from the opposing interface. If this problem occurs, the interface stays in access mode unless you either issue a shut command followed by a no shut command on the interface, or you issue the switchport mode access interface configuration command followed by the switchport mode trunk interface configuration command. To prevent this problem from occurring, you can configure the switchport nonegotiate option along with the switchport mode trunk command. This should only be done if the opposing interface is configured the same way. This problem is fixed in Release 12.0(7)XE1. (CSCdp56961)
This section describes open caveats for IOS Release 12.0(7)XE.
- DLSw Ethernet redundancy is not supported. (CSCdp93599)
- After a system reload, the ip mtu command does not function properly if it was saved with the write memory command. To use the ip mtu command to Layer 3 switch jumbo packets (packets greater than 1500 bytes), you must reenter the command manually after a reload. Note that you must reenter the ip mtu command even though the show running-configuration and show interface commands display the command as already having been entered. This problem is fixed in Release 12.0(7)XE1. (CSCdp59546)
- To ensure correct Layer 3 switching of routed jumbo IP packets, enter an ip mtu <MTU_size> command on the Layer 3 interfaces where you have enabled jumbo frame support with the mtu command. Ensure that the size specified by the mtu command and the ip mtu command is always the same. Enter another ip mtu <MTU_size> command whenever you change the MTU size. To reset the IP MTU value to the default, use the ip mtu <default_size> command, where <default_size> is the default for the interface. Do not use the no ip mtu command. This problem is fixed in Release 12.0(7)XE1 (entry of ip mtu interface commands is no longer necessary to ensure correct Layer 3 switching of routed jumbo IP packets). (CSCdp58561)
- Power cycling the standby supervisor is not supported. (CSCdp55523)
- Downloading images to the PCMCIA slot may in rare circumstances fail to write a valid image. Downloading during periods of low system activity reduces the likelihood of this failure. (CSCdm52806)
- When using the UplinkFast feature, the system does not send out the dummy multicast packets used to notify upstream users of forwarding-path changes. Normal Layer 2 aging is used to delete invalid entries. (CSCdm65881)
- When writing images to a 24-MB Flash PC card, the following messages may be seen:
%HEARTBEAT-2-NOT_RUNNING
- and/or
%SYS-SP-3-CPUHOG
- These messages are harmless and can be ignored. This problem is fixed in Release 12.0(7)XE1. (CSCdp57389)
- Partial support exists for the following MIBs:
- The CISCO-STACK-MIB supports chassisGrp, moduleGrp, portGrp.
- BRIDGE-MIB (RFC 1493) supports all objects, tables, and groups except dot1dBasePortTable, dot1dTpPortTable, and dot1DStaticGroup. (CSCdm44194)
- CISCO-FLASH-MIB supports only the route processor bootflash: device.
- CISCO-PROCESS-MIB supports only the route processor.
- CISCO-VLAN-MEMBERSHIP-MIB supports the vmMembershipTable.
- These MIBs are not supported:
- CISCO-SWITCH-ENGINE-MIB (CSCdm62652)
- CISCO-STP-EXTENSIONS-MIB (CSCdp50869)
- CISCO-COPS-CLIENT-MIB
- CISCO-QOS-MIB
- CISCO-PIB-MIB
- You cannot use SNMP to create VLANs. This problem is fixed in Release 12.0(7)XE1. (CSCdp52396)
- A traceback message displays when you exit the switch console. This message is harmless and can be safely ignored. (CSCdp35517)
- Unicast and multicast IP packets may not get properly routed if a multicast boundary is applied to an interface. A workaround is to specify a "permit any any" ACE as the last statement of the ACL associated with the multicast boundary. Note that you cannot configure any other access-group on the interface on which a multicast boundary is configured. This problem is fixed in Release 12.0(7)XE1. (CSCdp22095)
- A trunking interface on a Catalyst 6000 family switch running 12.0(7)XE might change to access mode roughly five minutes after the trunking encapsulation is changed. This event occurs if the interface is configured for trunking, is operating normally as a trunk, and the trunking encapsulation is changed from ISL to 802.1Q, or vice versa, and the interface is not receiving trunking protocol packets from the opposing interface. If this problem occurs, the interface stays in access mode unless you either issue a shut command followed by a no shut command on the interface, or you issue the switchport mode access interface configuration command followed by the switchport mode trunk interface configuration command. To prevent this problem from occurring, you can configure the switchport nonegotiate option along with the switchport mode trunk command. This should only be done if the opposing interface is configured the same way. This problem is fixed in Release 12.0(7)XE1. (CSCdp56961)
- If the system is not booted from a local flash device and the NVRAM configuration is not valid (or present), the service config option defaults to "on." Therefore, since the route processor is booted remotely from a device on the switch processor, the service config feature is enabled after the erase startup-config command is issued. (CSCdp12598)
- The show ibc command misleadingly displays ISL status as "disabled" and the GBIC as "missing." This is because the IBC in this system indicates the internal interface between the switch processor and the route processor. This interface is an electrical connection. As a result trunk and media types are not given for this interface. (CSCdp21121, CSCdp21380)
- The interface range command is not supported by the HTTP user interface. The command will execute on only the first interface in the specified range. The only workaround is not to use the interface range command when using the HTTP interface. (CSCdm54771)
This section describes troubleshooting guidelines for the Catalyst 6000 family switch configuration and is divided into the following subsections:
This section contains troubleshooting guidelines for system-level problems:
- When the system is booting and running power-on diagnostics, do not reset the switch.
- After you initiate a switchover from the active supervisor engine to the standby supervisor engine, or when you insert a redundant supervisor engine in an operating switch, always wait until the supervisor engines have synchronized and all modules are online before you remove or insert modules or supervisor engines or perform another switchover.
- If you have an interface whose speed is set to auto connected to another interface whose speed is set to a fixed value, configure the interface whose speed is set to a fixed value for half duplex. Alternately, you can configure both interfaces to a fixed-value speed and full duplex.
This section contains troubleshooting guidelines for module problems:
- When you hot insert a module into a chassis, be sure to use the ejector levers on the front of the module to seat the backplane pins properly. Inserting a module without using the ejector levers might cause the supervisor engine to display incorrect messages about the module. For module installation instructions, refer to the Catalyst 6000 Family Module Installation Guide.
- Whenever you connect an interface that has duplex set to autonegotiate to an end station or another networking device, make sure that the other device is configured for autonegotiation as well. If the other device is not set to autonegotiate, the autonegotiating port will remain in half-duplex mode, which can cause a duplex mismatch resulting in packet loss, late collisions, and line errors on the link.
Note Catalyst 6000 family switches do not support ISL-encapsulated Token Ring frames. To support trunked Token Ring traffic in your network, make trunk connections directly between switches that support ISL-encapsulated Token Ring frames. When a Catalyst 6000 family switch is configured as a VTP server, you can configure Token Ring VLANs from the switch.
Although DTP is a point-to-point protocol, some internetworking devices might forward DTP frames. To avoid connectivity problems that might be caused by a switch acting on these forwarded DTP frames, do the following:
- For interfaces connected to devices that do not support DTP, in which trunking is not currently being used, configure interfaces with the switchport mode access command, which puts the interface into access mode and sends no DTP frames.
- When manually enabling trunking on a link to devices that do not support DTP, use the switchport nonegotiate and switchport mode trunk commands, which puts the interface into trunking mode without sending DTP frames.
The Spanning Tree Protocol (STP) blocks certain ports to prevent physical loops in a redundant topology. On a blocked port, switches receive spanning tree bridge protocol data units (BPDUs) periodically from neighboring switches. You can configure the frequency with which BPDUs are received by entering the spanning-tree vlan vlan_ID hello-time command (the default frequency is set to 2 seconds). If a switch does not receive a BPDU in the time period defined by the spanning-tree vlan vlan_ID max-age command (20 seconds by default), the blocked port transitions to the listening state, the learning state, and to the forwarding state. As it transitions, the switch waits for the time period specified by the spanning-tree vlan vlan_ID forward-time command (15 seconds by default) in each of these intermediate states. Therefore, a blocked spanning tree interface moves into the forwarding state if it does not receive BPDUs from its neighbor within approximately 50 seconds.
Note We do not recommend using the UplinkFast feature on switches with more than 20 active VLANs. The convergence time might be unacceptably long with more than 20 active VLANs.
Use the following guidelines to debug STP problems:
- After a switchover from the active to the standby supervisor engine, the interfaces on the standby supervisor engine take longer to come up than other interfaces.
- Keep track of all blocked spanning tree interfaces in each switch in your network. For each of the blocked spanning tree ports, keep track of the output of the show interface command. Check to see if the interface has registered a lot of alignment, FCS, or any other type of line errors. If these errors are incrementing continuously, the interface might drop input BPDUs. If the input queue counter is incrementing continuously, the interface is losing input packets because of a lack of receive buffers. This problem can also cause the interface to drop incoming BPDUs.
- On a blocked spanning tree interface, check the duplex configuration to ensure that the interface duplex is set to the same type as the interface of its neighboring device.
- On trunks, make sure that the trunk configuration is set properly on both sides of the link.
- On trunks, if the neighboring device supports it, set duplex to full on both sides of the link to prevent any collisions under heavy traffic conditions.
If you lose the boot loader image, please refer to the following link for boot loader image recovery procedures:
http://www.cisco.com/warp/customer/473/14.html
Use the procedures in this section to convert from Catalyst software to Cisco IOS for the Catalyst 6000 family switches.
Note The system configuration is lost during the conversion to IOS. Reconfigure the switch after the conversion. We strongly recommend that you back up your supervisor engine Catalyst OS and your MSFC IOS configurations (for example to a TFTP server) before you begin the conversion. The MSFC IOS configuration can be used as a basis for configuring the newly converted system.
 | Caution
Please note that you must follow this sequence exactly to successfully convert your system. Failure to follow these instructions exactly may result in an unusable system. See the "Product and Software Version Matrix" section for information about supported software images. Do not attempt these procedures with other software images. |
Perform these steps while the switch is running Catalyst software on the supervisor engine and IOS on the MSFC:
Step 1 Use the show module command to confirm that the PFC and MSFC are installed in your switch:
- The PFC is shown on the supervisor engine as a "sub-module" named "L3 Switching Engine."
- An MSFC on a supervisor engine in slot 1 is shown as a module in slot 15.
- An MSFC on a supervisor engine in slot 2 is shown as a module in slot 16.
Step 2 Copy the system configuration.
Note Do not store the copy in the bootflash: device, because you will format the supervisor engine bootflash: device in Step 20.
Step 3 Copy the IOS system software image (for example, c6sup-js-mz.120-7.XE.bin or later) to a Flash PC card in slot0.
Step 4 Use the dir slot0: command to confirm that the Flash PC card in slot0: contains the IOS system software image you just copied.
Step 5 Set the configuration register to boot into ROMMON:
Console> (enable) set boot config-register 0x0
Configuration register is 0x0
ignore-config: disabled
console baud: 9600
boot: the ROM monitor
Step 6 Session to the MSFC:
Console> (enable) session 15
Step 7 Copy the MSFC configuration.
Step 8 Copy the IOS boot loader image (c6msfc-boot-mz.120-7.XE.bin or later) to the MSFC bootflash: device.
Router# copy device:boot_loader_image bootflash:
Step 9 Confirm that the MSFC bootflash: contains the IOS boot loader image:
Router# dir bootflash:
Directory of bootflash:/
1 -rw- 1599488 Dec 29 1999 11:12:29 c6msfc-boot-mz.120-7.XE.bin
15990784 bytes total (14391168 bytes free)
Router#
 | Caution
You must have a boot loader image in the MSFC bootflash: device to boot successfully. Do not reset the switch unless there is a boot loader image in the MSFC bootflash: device. If there is no boot loader image in the MSFC bootflash: device and the state of the switch does not support the copy command, see the "Recovering From Loss of the Boot Loader Image" section. |
Step 10 Set the configuration register of the MSFC to boot into ROMMON:
Router# configure terminal
Router(config)# config-register 0x0
Router(config)# end
Router#
00:08:02: %SYS-5-CONFIG_I: Configured from console by console
Router#
Step 11 Return to the supervisor engine:
Router# exit
Step 12 Reset the switch:
Console> (enable) reset
This command will reset the system.
Note Perform these steps while the switch is in ROMMON.
Step 13 Verify that the switch has booted into supervisor engine ROMMON. Look for "System Bootstrap, Version 5.2(1)CSX" or later.
Step 14 At the supervisor engine ROMMON prompt, boot the IOS system software image that is in slot0.
rommon 1 > boot slot0:c6sup-js-mz.120-7.XE.bin
Step 15 Verify that the switch has booted into MSFC ROMMON. Look for "System Bootstrap, Version 12.0(3)XE."
Step 16 Use the BOOTLDR command to set the BOOTLDR environment variable to use the IOS boot loader image that you just copied into the MSFC bootflash: device.
System Bootstrap, Version 12.0(3)XE, RELEASE SOFTWARE
Copyright (c) 1998 by cisco Systems, Inc.
Cat6k-MSFC platform with 65536 Kbytes of main memory
rommon 1 > BOOTLDR=bootflash:c6msfc-boot-mz.120-7.XE.bin
Note Previous IOS boot loader versions do not support Cisco IOS for the Catalyst 6000 family switch.
Step 17 Use the sync command to save the environment variables you just configured to NVRAM so they are read on the next reset:
rommon 2 > sync
Step 18 Enter a reset command:
rommon 3 > reset
Step 19 Boot the MSFC with the same command used for the supervisor engine:
rommon 1 > boot slot0:c6sup-js-mz.120-7.XE.bin
Note The MSFC ROMMON dir command will not display the contents of slot0.
Note Perform these steps while the switch is running IOS Release 12.0 XE on both the supervisor engine and the MSFC.
Note The show config command works reliably only after the first reload.
Step 20 Format the supervisor engine bootflash: device:
Router# format sup-bootflash:
Note The sup-bootflash: device is not reliably usable until it has been formatted.
Step 21 Configure the MSFC to use the boot loader image:
Router(config)# boot bootldr bootflash:c6msfc-boot-mz.120-7.XE.bin
Step 22 To autoboot an image stored in the supervisor engine bootflash: device, copy the system software image from slot0:
Router# copy slot0:c6sup-js-mz.120-7.XE.bin sup-bootflash:
Step 23 Configure the switch to autoboot the image:
Note To avoid boot failure, include the device name (slot0: or sup-bootflash:) in the following commands.
Router(config)# boot system flash slot0:c6sup-js-mz.120-7.XE.bin
or:
Router(config)# boot system flash sup-bootflash:c6sup-js-mz.120-7.XE.bin
Step 24 Set the configuration register parameter to autoboot:
Router(config)# config-register 0x102
Step 25 Copy the running configuration to the startup configuration in NVRAM:
Router# copy running-config startup-config
Step 26 Reload the switch:
Router# reload
Step 27 Configure the switch as described in the Catalyst 6000 Family IOS Software Configuration Guide.
This section describes caveats for the Catalyst 6000 family Cisco IOS Release 12 documentation. These changes will be included in the next update to the documentation.
- The Catalyst 6000 Family IOS Software Configuration Guide incorrectly describes a show broadcast interface command. See the online version of the Catalyst 6000 Family IOS Command Reference publication:
- http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/ios127xe/cmdref/show1.htm#88146
- for information about the show interfaces counters broadcast command.
- The technical documentation incorrectly describes a spanning-tree disable interface configuration command. This command is not implemented in Cisco IOS Release 12.0(7)XE. (CSCdp54100)
- See the online version of the Catalyst 6000 Family IOS Command Reference publication for revised information about these commands:
- show mls statistics
- show interfaces status
- errdisable recovery
- show errdisable recovery
Use the following command to copy a file to the slot0: device on a redundant supervisor engine:
Router# copy source_device:source_filename slaveslot0:target_filename
Use the following command to copy a file to the bootflash: device on a redundant supervisor engine:
Router# copy source_device:source_filename slavesup-bootflash:target_filename
Use the following command to copy a file to the bootflash: device on a redundant MSFC:
Router# copy source_device:source_filename slavebootflash:target_filename
You can use these commands to copy the boot loader and the system software image to a redundant supervisor engine and MSFC.
To optimize server-to-server performance, you can configure the MTU size on Gigabit Ethernet interfaces to support jumbo frames. Gigabit Ethernet interfaces with the default MTU size (1500 bytes) cannot form channels with interfaces where the MTU size is larger than the default.
The jumbo frame feature supports only a single larger-than-default MTU size on the switch. Configuring a Gigabit Ethernet interface with an MTU size greater than the default automatically configures all other interfaces and EtherChannels with MTU sizes greater than the default to the newly configured size. Interfaces that have not been changed from the default are not affected.
Observe the following guidelines when configuring the jumbo frame feature:
- You can configure jumbo frame support on the following:
- Layer 3 interfaces
- Layer 2 interfaces
- Trunks (observe any restrictions imposed by the neighboring device)
- EtherChannels (observe any restrictions imposed by the neighboring device)
- You cannot configure jumbo frame support on VLAN interfaces.
- Jumbo frames are not fragmented for transmission through slower ports in the same VLAN.
To configure the MTU value, perform this task:
| Step
| Command
| Purpose
|
|
| Router(config)# interface gigabitethernet slot/interface
| Access Gigabit Ethernet interface configuration mode.
|
|
| Router(config-if)# mtu mtu_size 9216
| Set the MTU size. Valid values are from 1500 to 10240 bytes.
|
|
| Router# show interface gigabitethernet 1/2
| Verify the configuration.
|
This example shows how to set the MTU size on a Gigabit Ethernet interface and verify the configuration:
Router(config)# interface gigabitethernet 1/2
Router(config-if)# mtu 10240
Router(config-if)# end
Router# show interface gigabitethernet 1/2
GigabitEthernet1/2 is administratively down, line protocol is down
Hardware is C6k 1000Mb 802.3, address is 0030.9629.9f88 (bia 0030.9629.9f88)
MTU 10240 bytes, BW 1000000 Kbit, DLY 10 usec,
<...Output Truncated...>
Router#
Note Currently 10240 is the supported maximum MTU size, but this maximum size may change in future releases.
The following documents are available for the Catalyst 6000 family switches running IOS release 12.0(7)XE:
- Catalyst 6000 Family Installation Guide
- Catalyst 6000 Family Module Installation Guide
- Catalyst 6000 Family IOS Software Configuration Guide
- Catalyst 6000 Family IOS Command Reference
- Catalyst 6000 Family IOS System Message Guide
Feature modules describe new features supported by Release 12.0 T and are an update to the Cisco IOS documentation set. As updates, the features modules are available online only. The feature module information is included in the next printing of the Cisco IOS documentation set. Feature modules consist of a brief overview of the feature, benefits, configuration tasks, and a command reference.
To access the feature modules on CCO, follow this path:
Software and Support: Software Center: Cisco IOS Software: Software Configuration: Cisco IOS Release 12.0: New Feature Documentation: New Features in 12.0-Based Limited Lifetime Releases: New Features in Release 12.0XE
To access the feature modules on the documentation CD-ROM, follow this path:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.0: Cisco IOS 12.0XE New Features
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.








Posted: Thu Sep 21 12:03:01 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.