Text Part Number: 78-6218-07 Rev. A0 Release Notes for Catalyst 6000 Family Software Release 5.x Current Release (January 3, 2000) 5.3(4)CSX Previous Releases 5.3(3)CSX, 5.3(2)CSX, 5.3(1a)CSX, 5.2(3)CSX, 5.2(2)CSX, 5.2(1)CSX, 5.1(1)CSX Note Release notes for prior Catalyst 6000 family software releases were accurate at the time of release.
Release 5.x Memory Requirements • • • • • • • • • • • Open and Resolved Caveats in Software Release 5.2(3)CSX, page 24 Open and Resolved Caveats in Software Release 5.2(2)CSX, page 26 Open and Resolved Caveats in Software Release 5.2(1)CSX, page 30 Open Caveats in Software Release 5.1(1)CSX, page 33 Troubleshooting, page 33 Documentation Updates for Software Release 5.3, page 36 Documentation Updates for Software Release 5.2, page 38 Documentation Updates for Software Release 5.
Product and Software Version Matrix Table 1 Minimum, Recommended, and Default Supervisor Engine Software Versions (continued) Product Number append with “=” for spares Product Description Minimum Supervisor Software Version Recommended/Default Supervisor Software Version Ethernet, Fast Ethernet, and Gigabit Ethernet WS-X6416-GE-MT 16-port Gigabit Ethernet MT-RJ with enhanced QoS features 5.3(1a)CSX 5.3(2)CSX WS-X6408A-GBIC 8-port Gigabit Ethernet GBIC with enhanced QoS features 5.3(1a)CSX 5.
Orderable Software Images Orderable Software Images Table 2 lists the software versions and applicable ordering information for the Catalyst 6000 family supervisor engine software. Table 2 Orderable Software Images Filename Orderable Product Number Flash on System Orderable Product Number Spare Upgrade (Floppy Media) 5.3(4)CSX cat6000-sup.5-3-4-CSX.bin SFC6K-SUP-5.3.4-CSX SWC6K-SUP-5.3.4-CSX= 5.3(3)CSX cat6000-sup.5-3-3-CSX.bin SFC6K-SUP-5.3.3-CSX SWC6K-SUP-5.3.3-CSX= 5.3(2)CSX cat6000-sup.
Features for Supervisor Engine Software Release 5.3 • On switches with a Policy Feature Card (PFC): Note IPX VACLs, QoS ACLs, COPS-DS, and RSVP for Qualitative Service were introduced in software release 5.3(1a)CSX but were not fully tested; you were instructed not to use them. These features can be used in software releases 5.3(3)CSX or later as they have been fully tested. — VLAN access control lists (VACLs) using IP, IPX, and MAC ACLs. VACL enhancements in software release 5.
Features for Supervisor Engine Software Release 5.2 Features for Supervisor Engine Software Release 5.2 This section describes the new features available in software release 5.2. • GARP VLAN Registration Protocol (GVRP; see IEEE 802.1p) provides 802.1Q-compliant VLAN pruning and dynamic VLAN creation on 802.1Q trunk ports. • GARP Multicast Registration Protocol (GMRP; see IEEE 802.1p) maintains Layer 2 multicast groups that determine which switch ports need to participate in multicasts.
Usage Guidelines and Restrictions When you change an IPX flow to destination-source, the show mls entry ipx destination command used to specify a specific destination, displays all IPX Layer 3 entries rather than just those for a specific destination IPX address. (CSCdm46984) • The following bug was mistakenly listed as open in software release 5.3(3)CSX. This bug never affected release 5.3(3)CSX or previous releases.
Open and Resolved Caveats in Software Release 5.3(4)CSX • The set port qos trust command and the trust-ipprec and trust-dscp port keywords are not allowed on 10-, 10/100-, and 100 Mbps ports. Instead, configure ACLs with the trust-cos, trust-dscp, and trust-ipprec ACE keywords. Note that the trust-cos port keyword can be used on 10-, 10/100-, and 100 Mbps ports to enable receive queue drop thresholds. • 24-port 100FX Switching Modules (WS-X6224-100FX-MT) with a hardware version of 1.
Open Caveats in Software Release 5.3(4)CSX • The ToS byte remains unchanged in bridged multicast packets when Multicast Multilayer Switching (MMLS) is enabled. The system does not support multiple, different rewrites for a single packet. The rewrite that is generated for multicast is a Layer 3 rewrite so there is no rewrite for the Layer 2 forwarding.
Open and Resolved Caveats in Software Release 5.3(4)CSX The fix involves performing an intermediate step, clearing the ACL mapping on the ports that have a different ACL mapping than the other ports, and mapping them to all have the same ACL before trying to channel them together (it is important to clear the older mapping first).
Resolved Caveats in Software Release 5.3(4)CSX • In systems with redundant supervisor engines, after a switchover to the redundant supervisor engine, the following message might be reported to the console: Got main interrupt val : 0x2 Interrupt in DBus Slave block: 0x200 Soft reset of titan : done Note that this bug has no impact and you should ignore these messages.
Open and Resolved Caveats in Software Release 5.3(4)CSX • Occasionally, after a system reset or power on, you will see that the standby supervisor engine shows 0 ports and the standby ports are not enabled. This problem might happen if one of the supervisor engine is approximately 20 seconds later than the other to begin booting the runtime image after a system reset or system power on. The workaround is to try to reset the standby supervisor engine from the active supervisor engine’s console port.
Open and Resolved Caveats in Software Release 5.3(3)CSX (b) Successfully committing the ASLB configuration (c) Modifying the configuration (d) Unsuccessfully committing the modified configuration Step (d) results in an inconsistent state. In release 5.3(4)CSX, the configuration is restored to the original when the modified configuration is not successfully committed. This problem is resolved in software release 5.3(4)CSX.
Open and Resolved Caveats in Software Release 5.3(3)CSX — set port qos 4/1 policy cops — set port channel 4/1-8 des The above sequence of steps causes the problem. The fix shown below ensures that you never map different ACLs to different ports which might channel together, and later switch them to all map to the same ACL.
Open Caveats in Software Release 5.3(3)CSX Note that this bug has no impact on the system and these messages should be ignored. (CSCdp06845) • Occasionally, after a system reset or power on, you will see that the standby supervisor engine shows 0 ports and the standby ports are not enabled. This problem might happen if one of the supervisors is approximately 20 seconds later than the other to begin booting the runtime image after a system reset or system power on.
Open and Resolved Caveats in Software Release 5.3(3)CSX • Occasionally, removal or insertion of a module does not generate any SYSLOG messages. (CSCdm63338) Resolved Caveats in Software Release 5.3(3)CSX This section describes resolved caveats in supervisor engine software release 5.3(3)CSX: • System power up time and redundant supervisor engine switchover time too slow. System bringup time and redundant supervisor engine switchover time have been improved.
Resolved Caveats in Software Release 5.3(3)CSX • The usage display for the clear qos acl map command is: Usage: clear qos acl map clear qos acl map The second syntax form fails when entered with multiple port numbers or multiple VLAN numbers. This problem is resolved in software release 5.3(3)CSX. (CSCdm89542) • Do not use Netflow Data Export (NDE) version 1 (the default NDE configuration is version 7).
Open and Resolved Caveats in Software Release 5.3(3)CSX • When using TACACS+, if you open a telnet session to the switch and enter a username and close the telnet session without entering a password, the TACACS+ session from the switch to the TACACS+ server remains open. This problem is resolved in software release 5.3(3)CSX. (CSCdp02341) • Avoid using Ctrl-C after entering the configure network command.
Open and Resolved Caveats in Software Release 5.3(2)CSX • Occasionally after system power up, console display shows minor hardware problem for some modules. Additionally, after a switchover to the redundant supervisor engine, “Change Status” messages are displayed. This problem is resolved in software release 5.3(3)CSX. (CSCdp24868) Open and Resolved Caveats in Software Release 5.3(2)CSX This section describes open and resolved caveats in supervisor engine software release 5.3(2)CSX.
Open and Resolved Caveats in Software Release 5.3(2)CSX The message errors are that it should state 9 instead of 10 operators and should not include “eq” in the logical operator’s list. (CSCdm88490) • Occasionally replacing an existing QoS ACL might fail with a Cannot configure more than 10 logical operators message when there are less than 10 logical operators in the new ACL. To workaround this problem, enter a clear qos acl map command to delete the old ACL and then create the new ACL.
Open and Resolved Caveats in Software Release 5.3(1a)CSX • ATM-related bug: In a configuration of about 150 VLANs and with a lot of unresolved ARPs on the ATM module, the supervisor engine complains about the SCP queue being full. This problem is resolved in software release 5.3(2)CSX. (CSCdp05776) • ATM-related bug: The ports of the ATM singlemode fiber-optic module are not added to the spanning tree. This problem is resolved in software release 5.3(2)CSX.
Open and Resolved Caveats in Software Release 5.3(1a)CSX • A QoS IP ACL can contain nine ACEs that use port operator parameters. If you attempt to add a tenth QoS IP ACE that uses a port operator parameter to an ACL, the following incorrect message is displayed: Cannot configure more than 10 logical operators (gt, lt, eq, neq, range) in an IP ACL. The message errors are that it should state 9 instead of 10 operators and should not include “eq” in the logical operator’s list.
Resolved Caveats in Software Release 5.3(1a)CSX • If traffic is received through a port that has port security enabled before the port is in the forwarding state, the port is shutdown. This problem is fixed in software release 5.3(1a)CSX. (CSCdk73206) • If the switch is in VTP client mode, entry of a copy device:filename config command may generate messages about nonexistent VLANs. Wait until the show vlan command displays the VLANs and then enter the copy command again.
Open and Resolved Caveats in Software Release 5.2(3)CSX • This bug does not effect system operation. The 48-Port 10/100TX Switching Modules (WS-X6248-TEL and WS-X6248-RJ-45) “Send admin” flow control field (show port flowcontrol mod_num/port_num) might show “desired” when the port is connected as well as when it is not connected or disabled. This problem is fixed in software release 5.3(1a)CSX.
Resolved Caveats in Software Release 5.2(3)CSX • If the switch is in VTP client mode, entry of a copy device:filename config command may generate messages about nonexistent VLANs. Wait until the show vlan command displays the VLANs and then enter the copy command again. This problem is fixed in software release 5.3(1)CSX.
Open and Resolved Caveats in Software Release 5.2(2)CSX • When a port goes into the errdisable state, it may cause the MAC addresses of other devices to be learned from the port that is in the errdisable state. This problem is fixed in software release 5.2(3)CSX. (CSCdm48887) • Occasionally, SNMP cannot access the ifDescriptors of some modules. This problem is fixed in software release 5.2(3)CSX.
Resolved Caveats in Software Release 5.2(2)CSX generate the same message until you remove the MSM from the source port list with a set span disable mod_num/port_num command. This problem is fixed in software release 5.3(1)CSX. (CSCdm20365) • When you turn off the power on any module, you cannot turn the power back on through SNMP. The workaround is to use the CLI command set module power up mod_num. This problem is fixed in software release 5.3(1)CSX.
Open and Resolved Caveats in Software Release 5.2(2)CSX • If protocol filtering is configured for an EtherChannel before the channel forms, it works correctly. If you configure protocol filtering after the channel has formed, it may not work correctly for transmitted traffic. This problem is fixed in software release 5.2(2)CSX.
Resolved Caveats in Software Release 5.2(2)CSX • Because of a race condition when 10/100 ports are trunking and channeling, all VLANs are not added to the spanning tree except the native VLAN. This problem is fixed in software release 5.2(2)CSX. (CSCdm26399) • When accessing the MSM through the session command, a timeout occurs when uploading an image from MSM bootflash to supervisor engine slot 0 (sup-slot0). This problem does not occur when connected to the MSM console port.
Open and Resolved Caveats in Software Release 5.2(1)CSX Open and Resolved Caveats in Software Release 5.2(1)CSX This section describes open and resolved caveats in supervisor engine software release 5.2(1)CSX. Open Caveats in Software Release 5.2(1)CSX This section describes open caveats in supervisor engine software release 5.2(1)CSX: • Changing the console port baud rate from 19,200 to 38,400 incorrectly sets the console port to 9600 baud. After a reset, the console port baud rate is 38,400.
Resolved Caveats in Software Release 5.2(1)CSX • The supervisor engine software incorrectly allows configuration of an MSM as a SPAN destination port. When configured as a SPAN destination port, the MSM ignores the SPAN traffic. If you configure an MSM as a SPAN destination port, remove it from the destination port list with a set span disable mod_num/port_num command. This problem is fixed in software release 5.2(2)CSX.
Open and Resolved Caveats in Software Release 5.2(1)CSX • In systems with redundant supervisor engines, occasionally during bootup or after a switchover to the redundant supervisor engine, a switching bus sequence error syslog message is reported to the console as follows: %SYS-1-MOD_SEQERROR:Switching bus sequence error occurred on module 8 This message might be generated for some or all installed modules. Ignore this message. This problem is fixed in software release 5.2(1)CSX.
Open Caveats in Software Release 5.1(1)CSX Open Caveats in Software Release 5.1(1)CSX This section describes caveats for Catalyst 6000 family software release 5.1(1)CSX.
Troubleshooting System Troubleshooting 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 download a new Flash image, the next reboot might take longer than normal if Erasable Programmable Logic Devices (EPLDs) on the supervisor engine need to be reprogrammed.
VLAN Troubleshooting VLAN Troubleshooting This section contains troubleshooting guidelines for VLAN problems: Note Catalyst 6000 and 6500 series 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 or 6500 series switch is configured as a VTP server, you can configure Token Ring VLANs from the switch.
Documentation Updates for Software Release 5.3 — show port—Check to see if the port has registered a lot of alignment, FCS, or any other type of line errors. If these errors are incrementing continuously, the port might drop input BPDUs. — show mac—If the Inlost counter is incrementing continuously, the port is losing input packets because of a lack of receive buffers. This problem can also cause the port to drop incoming BPDUs.
Documentation Updates for Software Release 5.3 • In the QoS chapter of the Catalyst 6000 Family Software Configuration Guide, Software Release 5.3, the section “Classification, Marking, and Policing with an L3 Switching Engine” has a note that should be: Note With an L3 Switching Engine, the Catalyst 6000 family switches provide QoS only for the Ethertype field values shown in Table 35-2 in Ethernet_II and Ethernet_SNAP frames.
Documentation Updates for Software Release 5.2 • The show qos acl map command syntax is documented incorrectly in the QoS chapter of the Catalyst 6000 Family Software Configuration Guide, Software Release 5.3. It is: show qos acl map {config | runtime} {acl_name | mod_num/port_num | vlan | all} See the online version of the Catalyst 6000 Family Command Reference, Software Release 5.3 publication for complete information about the syntax.
Documentation Updates for Software Release 5.2 • The Catalyst 6000 and 6500 Series Software Configuration Guide, Software Release 5.2, does not contain documentation for the set port negotiation command. Refer to the “Understanding How Port Negotiation Works” section on page 40 and the “Configuring Port Negotiation” section on page 40 for information about port negotiation. • The Catalyst 6000 and 6500 Series, Software Release 5.
Documentation Updates for Software Release 5.2 Understanding How Port Negotiation Works Note Port negotiation does not involve negotiating port speed. You cannot disable port negotiation with the set port speed command. Port negotiation exchanges flow-control parameters, remote fault information, and duplex information. Configure port negotiation with the set port negotiation command. Port negotiation is enabled by default. The ports on both ends of a link must have the same setting.
Uploading a System Image Using Xmodem or Ymodem This example shows how to disable port negotiation and verify the configuration: Console> (enable) set port negotiation 2/1 disable Port 2/1 negotiation disabled Console> (enable) show port negotiation 2/1 Port Link Negotiation ----- ---------------2/1 disabled Console> (enable) Uploading a System Image Using Xmodem or Ymodem When you need a system image on the switch, but the switch does not have network access and you do not have a software image on a Flas
Documentation Updates for Software Release 5.1 Note If you are transferring from a local computer, you may need to configure the terminal emulation program to ignore RTS/DTR signals. Step 3 Step 4 To upload from a remote computer: (a) Connect a modem to the console port and to the telephone network. (b) The modem and console port must communicate at the same speed, which can be from 1200 to 38400 bps, depending on the speed supported by your modem.
Additional Documentation • The Catalyst 6000 and 6500 Series Software Configuration Guide, Software Release 5.1, page 6-3. Incorrectly lists ISL as the default trunk encapsulation. The default is negotiate mode. If both ports are set to negotiate mode, the trunk uses ISL encapsulation. • The Catalyst 6000 and 6500 Series Software Configuration Guide, Software Release 5.1, Table 9-1.
Cisco Connection Online • • • Catalyst 6000 Family Software Configuration Guide Catalyst 6000 Family Command Reference Catalyst 6000 Family System Message Guide Cisco Connection Online 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.
Documentation CD-ROM Documentation CD-ROM 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.
Documentation CD-ROM 46 Release Notes for Catalyst 6000 Family Software Release 5.
