Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 April 2002 Cisco IOS Release 12.0(5)WC4 runs only on the Catalyst 2900 LRE XL switches with 16-MB CPU DRAM. Note This release is only for Long-Reach Ethernet (LRE) switches. Do not install this release on Catalyst 3500 XL switches or on Catalyst 2900 XL switches that are not LRE switches. For information about those switches, refer to Cisco IOS release 12.0(5)WC3b. These release notes include important information about this release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch: • • • If you are installing a new switch, refer to the IOS release label on the rear panel of your switch. If your switch is on and running, use the show version user EXEC command. See the “Determining the Switch Software Version” section on page 25. If you are upgrading to a new release, refer to the software upgrade filename for the IOS version. Before upgrading your switch to this release, read the “Upgrading the Switch Software” section on page 23. http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml (for registered Cisco.com users with a login password) http://www.cisco.com/public/sw-center/sw-lan.shtml (for nonregistered Cisco.com users) You can download the switch software from these sites: • • This release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future releases become available, they will be posted to Cisco.com in the Cisco IOS software area. Corporate Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA Copyright © 2002. Cisco Systems, Inc. All rights reserved. OL-2312-01 Contents Contents This document has the following sections: • • • • • • • • • • • • • “Hardware Requirements” section on page 2 “Cluster Requirements and Guidelines” section on page 4 “Minimum Cisco IOS Release for Major Features” section on page 5 “New Features in this Release” section on page 6 “Limitations and Restrictions” section on page 9 “Caveats” section on page 11 “Important Notes” section on page 18 “Documentation Notes” section on page 18 “Initial Switch Configuration” section on page 18 “Upgrading the Switch Software” section on page 23 “Related Documentation” section on page 33 “Obtaining Documentation” section on page 34 “Obtaining Technical Assistance” section on page 35 Hardware Requirements This software release only supports the 16-MB Catalyst 2900 LRE XL switches (see Table 1). This release also supports the Cisco 575 and 585 LRE CPE (customer premises equipment) devices. Table 1 Catalyst 2900 LRE XL Switches with 16-MB CPU DRAM Switch Description Catalyst 2912 LRE XL 4 10/100 ports and 12 LRE ports Catalyst 2924 LRE XL 4 10/100 ports and 24 LRE ports Software Requirements This section describes the requirements for the system and for the Cluster Management Suite (CMS) software. System Requirements These operating systems are supported for CMS management: • • • Microsoft Windows 95 (Service Pack 1 required) Microsoft Windows 98, second edition Microsoft Windows NT 4.0 (Service Pack 3 or higher required) Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 2 OL-2312-01 Software Requirements • • Microsoft Windows 2000 Solaris 2.5.1 or higher, with the Sun-recommended patch cluster for that operating system and Motif library patch 103461-24 The minimum PC requirement is a Pentium processor running at 233 MHz with 64 MB of DRAM. The minimum UNIX workstation requirement is a Sun Ultra 1 running at 143 MHz with 64 MB of DRAM. Table 2 lists the recommended platforms for using CMS. Table 2 OS Recommended Minimum Platform Configuration for Web-Based Management Processor Speed 1 DRAM Number of Colors Resolution Font Size Windows NT 4.0 Solaris 2.5.1 Pentium 300 MHz SPARC 333 MHz 128 MB 65,536 128 MB Most colors for applications 1024 x 768 – Small Small (3) 1. Service Pack 3 or higher required Browser and Java Plug-In Requirements When starting a CMS session, the switch verifies the browser version to ensure that the browser is supported. If the browser is not supported, an error message appears, and the session does not start. Table 3 lists the browsers supported by CMS. CMS requires the Java plug-ins described in the “Installing the Required Plug-In” section on page 21. Table 3 Browser Requirements Operating System Windows 95 Windows 98 Windows NT 4.0 Windows 2000 Solaris 2.5.1 or higher Netscape Communicator1 4.61, 4.7 4.61, 4.7 4.61, 4.7 4.61, 4.7 4.61, 4.7 Microsoft Internet Explorer2 4.01a, 5.0, or 5.5 4.01a, 5.0, or 5.5 4.01a, 5.0, or 5.5 4.01a, 5.0, or 5.5 – 1. Netscape Communicator version 4.60 and 6.0 are not supported. 2. Microsoft Internet Explorer is not supported on Solaris 2.5.1 or higher. Note In CMS, Internet Explorer versions 4.01 and 5.0 do not display edge devices that are not connected to the command switch. Other functionality is similar to that of Netscape Communicator. Note If you receive an Internet Explorer error message that the page might not display correctly because your security settings prohibit the ActiveX controls, your security settings are set too high. To lower security settings, go to Tools > Internet Options, and select the Security tab. Select the indicated Zone, and move the Security Level for this Zone slider from High to Medium (the default). To access CMS, follow the procedures in the “Initial Switch Configuration” section on page 18. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 3 Cluster Requirements and Guidelines Cluster Requirements and Guidelines This section describes the hardware and software requirements for clustering Catalyst desktop switches. Catalyst 2900 XL and Catalyst 3500 XL Switches Some versions of IOS software do not support clustering, and other versions do not support some of the features in this release. To ensure that all cluster switches are using the same software level, we recommend that you upgrade all cluster switches to the software release that supports the features that you want. If you have a cluster with switches that are running different versions of IOS software, changes on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)XU or later. Table 4 describes the Catalyst 2900 XL and Catalyst 3500 XL switches supported by this release and shows which switches can be command switches. All switches can function as standalone devices. All Catalyst 2900 XL and Catalyst 3500 XL switches running Release 12.0(5.3)WC(1) and later are cluster-capable. All Catalyst 2900 XL modules are supported in cluster configurations. We recommend that either the command switch has the latest software version installed if there switches in the cluster with older software versions or that all switches in the same platform be upgraded to the latest software version. Table 4 Catalyst 2900 XL and Catalyst 3500 XL Switches as Cluster Members Switch Catalyst 2900 XL (4 MB of DRAM)1 Catalyst 2900 XL (8 MB of DRAM) Catalyst 2900 LRE XL (16 MB of DRAM) Catalyst 3500 XL Release 12.0(5.3)WC(1) or higher? No Yes Yes Yes Command Capable? No Yes Yes Yes Member Capable? Yes Yes Yes Yes 1. These switches can act as cluster members if they are running Release 11.2(8.x)SA6 original edition software. They can interoperate with this software release, but they cannot be upgraded to it. Catalyst 3550 Switches Catalyst 3550 switches running Release 12.0(4)EA1 or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 3550 switches. Catalyst 2950 Switches Catalyst 2950 switches running Release 12.0(5)WC(1) or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 2950 switches. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 4 OL-2312-01 Minimum Cisco IOS Release for Major Features Catalyst 1900 and Catalyst 2820 Switches Table 5 lists the Catalyst 1900 and Catalyst 2820 switches and the minimum software release that they require to be cluster members. All Catalyst 2820 modules are supported in cluster configurations. For more information, refer to the documentation for the Catalyst 1900 and Catalyst 2820 switches. Table 5 Catalyst 1900 and Catalyst 2820 Switches as Cluster Members Switch Release 9.00 (-EN) Member Capable? Yes Yes Command Capable? No No Catalyst 1900 Yes Catalyst 2820 Yes Minimum Cisco IOS Release for Major Features Table 6 lists the minimum software release required to support the major features of the Catalyst 2900 XL and Catalyst 3500 XL switches. Table 6 Catalyst 2900 XL (including 2900 LRE XL) and Catalyst 3500 XL Features and the Minimum Cisco IOS Release Required Feature Support for the Cisco 585 LRE CPE device Enhanced web-based switch management (CMS) MAC Address Notification Internet Group Management Protocol (IGMP) Filtering WS-C2912-LRE XL and WS-C2912-LRE XL switches with LRE ports and support for the Cisco 575 LRE CPE device Extended cluster member compatibility with the Catalyst 2950 and Catalyst 3550 switches Multicast VLAN Registration (MVR) Cross-stack UplinkFast Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration Support for the single-port 1000BASE-T Gigabit Interface Converter (GBIC) (WS-G5482) WS-C3524-PWR XL switch with 10/100 inline-power ports WS-C2924M-XL-EN-DC switch with DC power connector WS-X2932-XL Catalyst 2900 XL 1-port 1000BASE-T module Hot Standby Router Protocol (HSRP) for clustering Extended discovery of cluster candidates up to 7 hops from the command switch Support for up to 16 switches in a cluster VLAN Trunking Protocol (VTP) pruning Change management Virtual LAN (VLAN) for a cluster Minimum Release Required Release 12.0(5)WC4 Release 12.0(5)WC4 Release 12.0(5)WC4 Release 12.0(5)WC4 Release 12.0(5.1)WC(1) Release 12.0(5)WC(1) Release 12.0(5)WC(1) Release 12.0(5)XW Release 12.0(5)XW Release 12.0(5)XW Release 12.0(5)XU Release 12.0(5)XU Release 12.0(5)XU Release 12.0(5)XU Release 12.0(5)XU Release 12.0(5)XU Release 12.0(5)XU Release 12.0(5)XU Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 5 New Features in this Release Table 6 Catalyst 2900 XL (including 2900 LRE XL) and Catalyst 3500 XL Features and the Minimum Cisco IOS Release Required Feature Private VLAN edge support UniDirectional Link Detection (UDLD) for detecting unidirectional links Extended cluster member functionality for Catalyst 1900 and 2820 switches Remote monitoring (RMON) support through the command-line interface (CLI) or Simple Network Management Protocol (SNMP) Change management VLAN Quality of service (QoS) based on IEEE 802.1P class of service (CoS) values WS-C3548-XL switch with 48 10/100 ports WS-X2931-XL Catalyst GigaStack GBIC Catalyst 3500 series XL switches (except WS-C3548-XL) Cluster management Terminal Access Control Access System Plus (TACACS+) Network Time Protocol (NTP) Spanning Tree Protocol (STP) UplinkFast 250 VLANs (some models: see the “Limitations and Restrictions” section on page 9) Catalyst 2900 series XL 1000BASE-X modules Catalyst 2900 series XL asynchronous transmission mode (ATM) modules IEEE 802.1Q trunking Inter-Switch Link (ISL) trunking VLAN Membership Policy Server (VMPS) 8192 media access control (MAC) addresses on modular switches Switch Network View stack management Web-based switch management Fast EtherChannel port groups Minimum Release Required Release 12.0(5)XU Release 12.0(5)XU Release 12.0(5)XP Release 12.0(5)XP Release 12.0(5)XP Release 12.0(5)XP Release 12.0(5)XP Release 12.0(5)XP Release 11.2(8)SA6 Release 11.2(8)SA6 Release 11.2(8)SA6 (Enterprise Edition Software) Release 11.2(8)SA6 Release 11.2(8)SA6 (Enterprise Edition Software) Release 11.2(8)SA6 Release 11.2(8)SA5 Release 11.2(8)SA5 Release 11.2(8)SA5 (Enterprise Edition Software) Release 11.2(8)SA4 (Enterprise Edition Software) Release 11.2(8)SA4 (Enterprise Edition Software) Release 11.2(8)SA4 Release 11.2(8)SA3 Release 11.2(8)SA Release 11.2(8)SA New Features in this Release This section describes the new features in this release. New Hardware Support Release 12.0(5)WC4 supports the Cisco 585 LRE CPE device. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 6 OL-2312-01 New Features in this Release New Software Support This section describes the new software features in this release. MAC Address Notification You can use MAC address notification to track users coming to and going from your network. Whenever a new MAC address is learned or an old MAC address is removed from the switch, an SNMP notification (trap) is generated. If you have many users coming into and going from the network, you can set a trap interval time so that traps can be bundled and sent at regular intervals. The MAC notification history table stores the MAC address activity for each hardware port for which the trap is enabled. MAC address notifications are generated for dynamic and secure MAC addresses. Events are not generated for self addresses, multicast addresses, or other static addresses. CMS Enhancements The CMS software has several enhancements: • Access modes CMS now provides two levels of access to the configuration options: read-write and read-only. Read-write access requires privilege level 15. Read-only access requires privilege level from 1 to 14. Privilege level 0 denies access to CMS. • Guide and expert modes CMS now provides two modes that control how the VLAN and voice VLAN configuration options are presented. Guide mode takes you step-by-step through these options. Expert mode displays the entire configuration window and lets you decide how to complete a task. • Voice VLAN wizard CMS provides a wizard to help you configure a port to forward voice traffic with an 802.1P priority and configure the port as an 802.1Q trunk and as a member of the voice VLAN. • Consistent menu bar, toolbar, and popup menus There are several changes to the CMS menus: – CMS now has a single menu bar and a toolbar for configuring and monitoring a single switch or a switch cluster. The menu bar and toolbar does not change if you have the Front Panel view, the Topology view, or neither view displayed. – The menu-bar options are now in these groups: CMS, Administration, Cluster, Device, Port, VLAN, Reports, View, Window, and Help. – The menu bar of a Catalyst 2900 XL or Catalyst 3500 XL command switch displays all Layer 2 options available from the cluster, including options from member switches from other cluster-capable switch platforms, such as the Catalyst 2950 and Catalyst 3550 switches. It does not display the Catalyst 2950 Layer 2+ options and the Catalyst 3550 Layer 3 options. – Popup menu options appear only if they are supported by all of the selected objects. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 7 New Features in this Release • Views of your switch cluster As before, CMS provides a Front Panel view of a switch cluster and a Topology view of a switch cluster and the devices attached to it. You can now display both views at the same time, display either view, or display neither view. You do not need to display a view to use the menu bar. For configuring and monitoring a standalone switch, CMS continues to provide Device Manager, previously referred to as Switch Manager. • Front Panel view enhancements You can press the left mouse button and drag your mouse across the ports that you want to select. You can highlight the ports and find out their VLAN membership modes. The cluster tree can display icons for Layer 2, Layer 3, and LRE standby-command switches. • Topology view enhancements You can press the left mouse button and drag your mouse across the devices and links that you want to select. You have more options for controlling the type of information displayed in the Topology view. When you drag your mouse over a yellow or red device icon, a tool tip displays a status message. This view displays device icons for connected Cisco 575 and 585 LRE customer premises equipment (CPE) devices, Cisco access points, Cisco IP phones, Cisco Discovery Protocol (CDP)-capable hubs, and routers. This view displays link icons for routed and LRE links. • Dialog enhancements CMS provides change notification by adding a green border around a field or table cell that has an unsaved change. CMS also provides error checking by adding a red border around a field where you entered invalid data. An error message also displays in the window status bar. When you drag your mouse over a table heading, a tool tip displays the complete heading. On some table columns, you can sort information in ascending or descending order. Editable table cells are shown with a pencil icon. Links to the Internet are shown with a globe icon. • Online help links Links in the online help can display configuration windows, related help topics, and related information from Cisco.com. • Printing You can print reports, graphs, and online help topics. For more information about CMS enhancements, refer to the “What’s New” section in the online help on your switch. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 8 OL-2312-01 Limitations and Restrictions Limitations and Restrictions You should review this section before you begin working with the switches. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software. • You cannot configure a connected Cisco 585 LRE CPE device. You cannot monitor a Cisco 585 LRE CPE device from the switch LEDs or from CMS. Use the cluster setup privileged EXEC command to monitor a Cisco 585 LRE CPE device. You can still monitor a Cisco 575 LRE CPE device from the switch LEDs, the CLI, and from CMS. When packets from multiple VLANS that have the same source MAC address are received on different Ethernet ports of a Cisco 585 LRE CPE device, the LRE CPE creates a single ingress port entry in the packets. The packets are not correctly switched back to the VLANs if the network was designed with the assumption that MAC address and ingress port entries are maintained for each specific VLAN. There is no workaround. This is a limitation of the Ethernet switch on the Cisco 585 LRE CPE. (CSCdx03708) • • Incoming Inter-Switch Link (ISL) frames are discarded by Cisco LRE CPE devices. ISL frames are not supported on the Cisco LRE CPE devices. There is no workaround. (CSCdx25940) A configuration conflict occurs if a switch cluster has Catalyst 2900 LRE XL switches using both private and public profiles. If one LRE switch in a cluster is assigned a public profile, all LRE switches in that cluster must have that same public profile. Before you add an LRE switch to a cluster, make sure that you assign it the same public profile used by other LRE switches in the cluster. Catalyst 2900 LRE XL switches support 250 VLANs and 64 spanning-tree instances. If a port group is set up between the LRE port of a Catalyst 2900 LRE XL switch and the Fast EtherChannel (FEC) ports of another switch through the LRE CPE devices, and the LRE link on an LRE port drops, the LRE switch no longer uses the LRE port for data transmission. However, the other switch might continue sending data through the FEC port. The packets being sent to the LRE port of the LRE switch are lost. Data transmission continues normally if the LRE link is restored. (CSCdt22573) You can connect the switch to a PC by using the switch console port and the supplied rollover cable and the DB-9 adapter. You need to provide a RJ-45-to-DB-25 female DTE adapter if you want to connect the switch console port to a terminal. You can order a kit (part number ACS-DSBUASYN=) with this RJ-45-to-DB-25 female DTE adapter from Cisco. Certain combinations of port features create configuration conflicts. Refer to the “Avoiding Configuration Conflicts” section in the “Troubleshooting” chapter of the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide for a table that defines these conflicts. • • • • • Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 9 Limitations and Restrictions • When you add a VTP client, follow this caution and procedure: Caution Before adding a VTP client to a VTP domain, always verify that its VTP configuration revision number is lower than the configuration revision number of the other switches in the VTP domain. If necessary, reset the switch configuration revision number to 0. Switches in a VTP domain always use the VLAN configuration of the switch with the highest VTP configuration revision number. If you add a switch that has a revision number higher than the revision number in the VTP domain, it can erase all VLAN information from the VTP server and VTP domain. Beginning in user EXEC mode, follow these steps to verify and reset the VTP configuration revision number on a switch before adding it to a VTP domain. Command Step 1 Purpose Check the VTP configuration revision number. If the number is 0, add the switch to the VTP domain. If the number is greater than 0, follow these steps: a. b. c. show vtp status Write down the domain name. Write down the configuration revision number. Continue with the next steps to reset the configuration revision number on the switch. Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 enable vlan database vtp domain domain-name exit show vtp status vlan database vtp domain domain-name exit show vtp status Enter privileged EXEC mode. Enter VLAN database mode. Change the domain name from the original one displayed in Step 1 to a new name. The VLAN information on the switch is updated and the configuration revision number is reset to 0. You return to privileged EXEC mode. Verify that the configuration revision number has been reset to 0. Enter VLAN database mode. Enter the original domain name on the switch. The VLAN information on the switch is updated, and you return to privileged EXEC mode. (Optional) Verify that the domain name is the same as in Step 1 and that the configuration revision number is 0. After resetting the configuration revision number, add the switch to the VTP domain. Note You can use the vtp transparent vlan database command to disable VTP on the switch and then change its VLAN information without affecting the other switches in the VTP domain. For more information about using vtp transparent mode, refer to the switch software configuration guide. • Host names and Domain Name System (DNS) server names that contain commas on a cluster command switch, member switch, or candidate switch can cause CMS to behave unexpectedly. You can avoid this instability in the interface by not using commas in host names or DNS names. Do not use commas when also entering multiple DNS names in the Device Configuration tab (Administration > IP Addresses) in CMS. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 10 OL-2312-01 Caveats • The range of seconds for the span-tree max-age global configuration command is now 6 to 200 seconds. If you had used this command in Release 11.2(8)SA6 or earlier to set a value greater than this range and now upgrade your software to Release 11.2(8.1)SA6 or later, the switch sets this value to the default: 20 seconds for IEEE STP and 10 seconds for IBM STP. When using the SPAN feature, the monitoring port receives copies of sent and received traffic for all monitored ports. If the monitoring port is 50 percent oversubscribed for a sustained period of time, it will probably become congested. One or more of the ports being monitored might also experience a slowdown. When using the Software Image Management (SWIM) application in the Resource Manager Essentials (RME) suite of the CiscoWorks2000 product family to perform automated system software and boot loader upgrades, you should note the following: – Catalyst 2900 series XL switches require Release 11.2(8)SA4 or later and RME version 2.1 • • or 2.2. – Catalyst 3500 series XL switches require Release 11.2(8.1)SA6 or later and RME version 2.2. Caveats This section describes open caveats and possible unexpected activity in Release 12.0(5)WC4: • • • “Open IOS Caveats” section on page 11 “Open Cluster Configuration Caveats” section on page 13 “Open CMS Caveats” section on page 14 Note This release is only for Long-Reach Ethernet (LRE) switches. Do not install this release on Catalyst 3500 XL switches or on Catalyst 2900 XL switches that are not LRE switches. For information about those switches, refer to Cisco IOS Release 12.0(5)WC3b. Open IOS Caveats This section describes the severity 3 IOS configuration caveats in Release 12.0(5)WC4: • CSCdt01392 Ethernet statistics that appear in the output of the show interface privileged EXEC command for LRE ports show the counters of the MAC counters on the switch instead of the MAC counters on the CPE device. The workaround is to use the show controllers ethernet-controller privileged EXEC command to see the Ethernet statistics on the CPE device. To clear the Ethernet statistics counters on the CPE device, use the clear controllers ethernet-controller privileged EXEC command. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 11 Caveats • CSCdu41214 When a source port is set at a higher speed than an egress (outgoing) port in a multicast, the transmit buffers are held in use and become full before the packets can be sent out of the egress ports. This causes the source port to run out of buffer space for the remaining traffic it needs to send, and packets are eventually dropped from the source port, causing an Input ignored multicast error. The problem is caused by oversubscription on the egress ports. If multicast traffic is being sent out on multiple ports, the lowest-speed egress port limits the rate at which frames are dropped at the ingress port. The workaround is to upgrade to Release 12.0(5)WC4. Software modifications in this release alleviate the problem in these ways: – The shared memory allocation can be modified so that uplink ports have a larger share of the available switch buffers, and the downlink ports have fewer buffers. This can be done by using the following hidden CLI: – Use the switchport uplink interface configuration command to specify that the interface is an uplink port. All ports not configured as uplink will be treated as downlink ports. – Use the switchbuffers uplink global command to enable the buffer redistribution. You have to reset the switch before these commands take effect. • CSCdt53253 If a port on a switch is configured as a dot1q trunk, and the switch is receiving dot1q frames that have the cfi bit set in the dot1q header, the switch drops these frames. Depending on the number of frames that are received with this bit set, connectivity to the switch can be lost. The workaround is to prevent dot1q frames with the cfi bit set from being sent to the switch. CSCdt83042 High rates of traffic sent to a MAC address that is used by an MVR multicast group and received on an MVR receiver port can cause excessive CPU utilization rates and consume enough resources on the switch CPU so that normal spanning-tree processing is interrupted. This can prevent spanning-tree loops from being broken. The workaround is to enable multicast storm control on all MVR receiver ports. CSCdt84558 In MVR, when changing the configuration of a port from receiver to source, the port does not start receiving multicast traffic. The workaround is to save the configuration and reboot the switch to restore proper traffic flooding. CSCdt83212 MVR does not initialize on a switch if that switch is a cluster member and does not have an IP address. The workaround is to set an IP address on the switch. CSCdt48569 If you configure VLAN1 as the management VLAN and configure it as administratively down, VLAN1 correctly appears as administratively down in the output of the show ip interface brief privileged EXEC command. If you configure any VLAN other than VLAN1 as the management VLAN and configure VLAN1 as administratively down, VLAN1 incorrectly appears as up in the output of the show ip interface brief command. There is no workaround. • • • • Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 12 OL-2312-01 Caveats • CSCdt18106 If you perform an snmpwalk SNMP operation on the CISCO-IP-STAT-MIB, continuous loops occur through the first element in the MIB tree when IP accounting precedence is configured for a VLAN interface other than VLAN1. The CISCO-IP-STAT-MIB is not supported. The workaround is to perform individual snmpget SNMP requests to retrieve data. CSCds58369 If the switch is configured from the dynamic IP pool, a duplicate or different IP address might be assigned. The workaround is to make sure that the DHCP server contains reserved addresses that are bound to each switch by the switch hardware address so that the switch does not obtain its IP address from the dynamic pool. • • CSCdm24487 The serial port shares the same status bit for hardware flow control and for ready. The workaround is to not use flow control on the console port. CSCdp85954 Root guard is inconsistent when configured on a port that is in the spanning-tree blocked state when configured. There is no workaround. • Open Cluster Configuration Caveats This section describes the severity 3 cluster configuration caveats in Release 12.0(5)WC4: • CSCdt48011 Two problems could occur when a switch is in transparent mode: – If the switch is a leaf switch, any new VLANs added to it are not propagated upstream through VTP messages. As a result, the switch does not receive flooded traffic for that VLAN. – If the switch is connected to two VTP servers, it forwards their pruning messages. If the switch has a port on a VLAN that is not requested by other servers through their pruning messages, it does not receive flooded traffic for that VLAN. There is no workaround. • CSCdp70389 When changing the management VLAN on a cluster with command-switch redundancy enabled, the cluster can break if HSRP is configured on any of the cluster members in the new management VLAN. The workaround is to not change the management VLAN to a VLAN where a member is configured as part of a standby group. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 13 Caveats Open CMS Caveats This section describes the severity 3 CMS configuration caveats in Release 12.0(5)WC4: • CSCdx31546 The CMS Runtime Status window incorrectly shows the Ethernet link, speed, and duplex status for connected Cisco 585 LRE CPE devices. The fields should say N/A. To verify the actual status for a Cisco 585 LRE CPE device, use the show remote interfaces status user EXEC command. • CSCdt42854 Running a CMS link graph for more than 24 hours can cause an OutOfMemoryException error. There is no workaround. CSCdt47877 When running CMS with Windows 98 and JRE plug-in 1.3, the tool tip that shows the exact coordinates of a point on a graph is so small that it is unreadable. There is no workaround. CSCdt58668 After a sudden increase in network traffic, followed by a decrease to a the level, checking the Logarithmic Scaling check box in the Link Graph window has no effect if the Total Bytes, Total Packets, or Total Errors options are plotted. There is no workaround. CSCdp67822 CMS requires a Java plug-in from Sun Microsystems. If you are using Internet Explorer and you disable Java plug-ins by using the Java Plug-In Control Panel, the initial Splash screen shows that the plug-in and Java are enabled, but Internet Explorer fails. The workaround is to not disable Java plug-ins on the Java Plug-In Control Panel. CSCdp82224 The CMS Time Management supports the configuration of the Network Time Protocol (NTP) and system time. When you make changes on this window from a command switch, Java propagates the changes to all cluster members. A conflict can arise if you configure NTP and also use the Set Current Time and Set Daylight Saving Time tabs. The workaround is to either set the system time for the entire cluster on the command switch or configure NTP on the command switch to use an NTP server to provide time to the cluster. Do not use both methods at the same time. • • • • • CSCdp85928 CMS can behave unexpectedly if host names or DNS server names that it processes contain commas. This means that host names or DNS server names on a cluster command switch, member, or neighbor can cause instability in the HTML interface. The workaround is to not include commas in host names or DNS server names in CMS. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 14 OL-2312-01 Caveats Resolved Caveats This section describes caveats that have been resolved: • • • • “Resolved IOS Caveats in Release 12.0(5)WC4” section on page 15 “Resolved CMS Caveats in Release 12.0(5)WC4” section on page 17 “Resolved IOS Caveat in Release 12.0(5)WC2b” section on page 17 “Resolved CMS Caveat in Release 12.0(5)WC2b” section on page 17 Resolved IOS Caveats in Release 12.0(5)WC4 These configuration caveats were resolved in Release 12.0(5)WC4: • CSCdt67450 Alignment and collision Ethernet counters on the Cisco LRE CPE devices no longer increment if an an Ethernet link is not present. All Cisco LRE CPE devices are now shipped with this software correction. • CSCdv00304 When a spanning tree reconverges and VTP is pruning enabled, a Catalyst 2900 XL or 3500 XL switch no longer stops forwarding traffic for a single VLAN. • CSCdw44304 When a corrupted STP packet has a maximum age between 0 and 1 second, the switch no longer ages out the bridge protocol data units (BDPU). This causes a new spanning-tree root to be elected. • CSCdt83966 When a receiver VLAN is shut down locally, suspended throughout the VTP domain, or deleted from the VTP database, the show mvr, show mvr int, and show mvr member privileged EXEC commands now show that MVR and its members are disabled. The receiver ports remain as MVR ports, and forwarding of MVR traffic resumes after the VLAN is restored and spanning tree has transitioned to a forwarding state. • CSCdu10578 If an IGMP general query is received on a port that is assigned to a VLAN, but that port is not the receiver port VLAN, the query no longer interrupts the multicast streams controlled by MVR in the multicast VLAN and receiver port. • CSCdw00322 A switch no longer continues allocating memory for a process that has already been terminated. Note Memory that is retained for a process that has already been terminated is often referred to as dead memory. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 15 Caveats • CSCdu10578 An IGMP general query received on a port that is assigned to a VLAN no longer interrupts the multicast streams controlled by MVR in the multicast VLAN and the receiver port VLAN. • CSCdv02485 Topology changes no longer cause a software forced-reload on a Catalyst 3524 XL switch. Note • This condition had occurred with heavy, high-priority traffic on a switch. CSCdv62652 It is no longer necessary to clear the MAC address table on a Catalyst 3548 XL switch to be able to ping through the Fast EtherChannel (FEC) ports on that switch after shutting down a port belonging to the FEC. (See also CSCdv58536.) • CSCdv58536 Executing a shutdown interface command on a FEC port does not shut down other FEC ports on the same switch. • CSCds45300 A Catalyst 2900 XL or Catalyst 3500 XL switch now responds to V2 MIB objects for 64-bit counters. • CSCdv57676 Extra characters are no longer added to the login prompt when you log in by using Telnet. CSCdu73533 After you replicate the authentication, authorization, and accounting (AAA) configuration to a cluster member switch, the tacacs server host line is no longer lost after the member switches are rebooted. • • CSCdv53949 It is no longer necessary to reload the switch for the snmp-server queue-length global configuration command to take effect. • CSCdv56078 Sending a large amount of CDP neighbor announcements no longer consumes all of a router's available memory. • CSCdv56187 The output of the debug ethernet-controller addresses privileged EXEC command now shows the physical port numbers of the switch instead of the internal STP port numbers. • CSCdv63206 A Cisco router no longer overwrites a MAC address for one of its interfaces stored in the ARP table with an external MAC address received from an ARP packet. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 16 OL-2312-01 Caveats • CSCdv60082 When an access port receives misconfigured ISL frames that have the Type and Priority bits set, the frames are now dropped instead of being broadcast to other ports. Resolved CMS Caveats in Release 12.0(5)WC4 These CMS caveats were resolved in Release 12.0(5)WC4: • CSCdw72081 A command switch no longer fails when it receives SNMP packets that have invalid variable bindings. • CSCdt82729 If you launch the VMPS Configuration window from the device pop-up menu in VSM, it no longer displays incorrect information. • CSCdv21358 The CMS software now accepts device passwords that contain these characters: ‘, “, ., /, \, <, >, [, ], {, }, #, %, |, ^, and ~. • CSCds86420 Two identical items for the same switch are no longer listed if you select a switch in the tree by selecting Administration > Console Baud Rate, clicking cancel, and selecting Administration > Console Baud Rate again. • CSCdt49955 When viewing CMS dialogue windows, an exception error no longer occurs when you press the Shift key on the keyboard at the same time as you select the Add or Remove CMS buttons. Resolved IOS Caveat in Release 12.0(5)WC2b • CSCdw65903 An error can occur with management protocol processing. Please use the following URL for further information: http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903 Resolved CMS Caveat in Release 12.0(5)WC2b • CSCdw72136 A Catalyst 2900 LRE command switch command switch no longer fails when it receives SNMP packets with invalid variable bindings. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 17 Important Notes Important Notes This section describes important information related to this release. • • The cluster setup privileged command was removed from Release 12.0(5)WC4 and above. The MVR threshold feature was removed in Release 12.0(5.3)WC(1). Use the port multicast storm control feature instead of the MVR threshold feature to limit rates. Documentation Notes The following information is now only in the release notes and is no longer in the manuals: • • Hardware, software, and cluster requirements. Procedures for initial switch configuration. – Using the setup program. – Installing browser plug-ins. – Accessing CMS. • Procedures for upgrading the switch software. Initial Switch Configuration This section provides these procedures: • • • “Using the Setup Program” section on page 18 “Installing the Required Plug-In” section on page 21 “Displaying the CMS Access Page” section on page 23 This section assumes that you have already installed the switch and connected devices to it, as described in the switch hardware installation guide. Using the Setup Program You can use an automatic setup program to assign switch IP information, host and cluster names, and passwords and to create a default configuration for continued operation. Later, you can use CMS or the command-line interface (CLI) to customize your configuration. To run the setup program, access the switch from the PC terminal that you connected to the console port. For information about connecting a PC or terminal to the switch console port, refer to the switch hardware installation guide. Note If the switch will be a cluster member, you do not always need to assign IP information or a password, as the switch will be managed through the IP address of the command switch. If you are configuring a command switch or standalone switch, you need to assign IP information. Refer to the switch software configuration guide for more information. The first time that you access the switch, it runs a setup program that prompts you for IP and other configuration information necessary for the switch to communicate with local routers and the Internet. This information is also required if you plan to use CMS to configure and manage the switch. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 18 OL-2312-01 Initial Switch Configuration You will need the following information from your system administrator: Switch IP address ___________.___________.___________._________ Subnet mask (netmask) ___________.___________.___________._________ Default gateway (router) ___________.___________.___________._________ Enable secret password ___________________________________________ Use this procedure to create an initial configuration for the switch: Note Be sure that the rollover cable is connecting a PC serial port to the switch console port. The data characteristics are 9600 baud, 8 data bits, 1 stop bit, and no parity. Use the supplied rollover cable and DB-9 adapter to connect a PC to the switch console port. You need to provide a RJ-45-to-DB-25 female DTE adapter if you want to connect the switch console port to a terminal. You can order a kit (part number ACS-DSBUASYN=) containing that adapter from Cisco. For console port and adapter pinout information, refer to the “Cable and Connector Specifications” appendix in the Catalyst 2900 Series XL Hardware Installation Guide and the Catalyst 3500 Series XL Hardware Installation Guide. At any point you can enter a question mark for help. Use Ctrl-C to stop the configuration dialog at any prompt. The default settings are in square brackets. Step 1 Enter Y at the first prompt. Continue with configuration dialog? [yes/no]: y Step 2 Enter the switch IP address, and press Return: Enter IP address: ip_address Step 3 Enter the subnet mask, and press Return: Enter IP netmask: ip_netmask Step 4 Enter Y at the next prompt to specify a default gateway (router): Would you like to enter a default gateway address? [yes]: y Step 5 Enter the IP address of the default gateway, and press Return. IP address of the default gateway: ip_address Step 6 Enter a host name for the switch, and press Return. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 19 Initial Switch Configuration Note On a command switch, the host name is limited to 28 characters; on a member switch to 31 characters. Do not use -n, where n is a number, as the last character in a host name for any switch. Enter a host name: host_name Step 7 Enter a secret password, and press Return. Note The password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, allows spaces, but ignores leading spaces. Enter enable secret: secret_password Step 8 Enter Y to enter a Telnet password: Would you like to configure a Telnet password? [yes] y Note The password can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces. Enter the Telnet password, and press Return: Enter Telnet password: telnet_password Step 9 Step 10 Enter Y to configure the switch as the cluster command switch. Enter N to configure it as a member switch or as a standalone switch. Note If you enter N, the switch appears as a candidate switch in Cluster Builder. In this case, the message in Step 11 is not displayed. Would you like to enable as a cluster command switch? y Step 11 Assign a name to the cluster, and press Return. Enter cluster name: cls_name Note Step 12 The cluster name can be 1 to 31 alphanumeric characters, dashes, or underscores. The initial configuration is displayed: The following configuration command script was created: ip subnet-zero interface VLAN1 ip address 172.20.153.36 255.255.255.0 ip default-gateway 172.20.153.01 hostname host_name enable secret 5 $1$M3pS$cXtAlkyR3/6Cn8/ line vty 0 15 password telnet_password snmp community private rw snmp community public ro cluster enable cls_name Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 20 OL-2312-01 Initial Switch Configuration end Step 13 Verify that the information is correct. • • If the information is correct, enter Y at the prompt, and press Return. If the information is not correct, enter N at the prompt, press Return, and begin again at Step 1. Use this configuration? [yes/no]: y After you complete the setup program, the switch can use the created default configuration. If you want to change this configuration or want to perform other management tasks, use one of these tools: • CMS from your browser (See the “Installing the Required Plug-In” section on page 21 and the “Displaying the CMS Access Page” section on page 23.) Command-line interface (CLI) (Refer to the switch software configuration guide.) • The switch software configuration guide provides more information about how to set a password to protect the switch against unauthorized Telnet access and how to access the switch if you forget the password. Installing the Required Plug-In A Java plug-in is required for the browser to access CMS. Download and install the plug-in before you start CMS. Each platform, Windows and Solaris, supports three plug-in versions. For information on the supported plug-ins, see the “Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users” section on page 22 and the “Solaris Platforms” section on page 22. You can download the recommended plug-ins from this URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/java Note Uninstall older versions of Java plug-ins before installing the Java plug-in. If the Java applet does not initialize after you have installed the plug-in, open the Java Plug-in Control Panel (Start > Programs > Java Plug-in Control Panel), and verify these settings: In the Proxies tab, verify that the Use browser settings is checked and that no proxies are enabled. Note If you are running McAfee VirusScan on Windows 2000 and the plug-in takes a long time to load, you can speed up CMS operation by disabling the VirusScan Internet Filter option, the Download Scan option, or both. From the Start menu, disable the options by selecting Start > Programs > Network Associates > Virus Scan Console > Configure. or From the taskbar, right-click the Virus Shield icon, and in the Quick Enable menu, disable the options by deselecting Internet Filter or Download Scan. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 21 Initial Switch Configuration Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users These Java plug-ins are supported on the Windows platform: • • • Java plug-in 1.3.1 Java plug-in 1.3.0 Java plug-in 1.2.2_05 You can download these plug-ins from this URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/java Note If you start CMS without having installed the required Java plug-in, the browser automatically detects this. If you are using a supported Internet Explorer browser, it automatically downloads and installs the Java plug-in 1.3.1 (default). If you are using a supported Netscape browser, the browser displays a Cisco.com page that contains the Java plug-in and installation instructions. If you are using Windows 2000, Netscape Communicator might not detect the missing Java plug-in. Solaris Platforms These Java plug-ins are supported on the Solaris platform: Caution To avoid performance and compatibility issues, do not use Java plug-ins later than Java plug-in 1.3.1. • • • Java plug-in 1.3.1 Java plug-in 1.3.0 Java plug-in 1.2.2_07 If you have a SmartNet contract, you can download these plug-ins and instructions from this URL: http://www.cisco.com/cgi-bin/tablebuild.pl/java To install the Java plug-in, follow the instructions in the README_FIRST.txt file. If you do not have a SmartNet contract, download the plug-in from this URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/java Note Uninstall older versions of the Java plug-in before installing Java plug-in JRE 1.3.1. Note If you are using Internet Explorer 5.0 to make configuration changes, this browser does not automatically reflect the latest configuration changes. Make sure to click Refresh for every configuration change. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 22 OL-2312-01 Upgrading the Switch Software Displaying the CMS Access Page After the browser is configured, display the CMS access page: Step 1 Step 2 Enter the switch IP address in the browser Location field (Netscape Communicator) or Address field (Internet Explorer), and press Return. Enter your username and password when prompted. The password provides level 15 access. The Cisco Systems Access page appears. For more information on setting passwords and privilege levels, refer to the switch software configuration guide. Note Step 3 If no username is configured on the switch, leave the username field blank. Click Cluster Management Suite to display the appropriate CMS application. Upgrading the Switch Software This section provides topics about upgrading the switch software: • • • • • • • • • • “Guidelines for Upgrading Switch Software” section on page 24 “Overview of the Switch Upgrade Process” section on page 25 “Determining the Switch Software Version” section on page 25 “Which Software Files to Download from Cisco.com” section on page 26 “Downloading the New Software and TFTP Server Application to Your Management Station” section on page 27 “Copying the Current Startup Configuration from the Switch to a PC or Server” section on page 27 “Using CMS to Upgrade One or More Switches” section on page 28 “Using CMS to Upgrade One or More Switches” section on page 28 “Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch” section on page 29 “Using the CLI to Upgrade LRE Member Switches” section on page 32 Note Before upgrading your switch to Release 12.0(5)WC4, read the “Guidelines for Upgrading Switch Software” section on page 24 for important information. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 23 Upgrading the Switch Software Guidelines for Upgrading Switch Software Note Release 12.0(5)WC4 is only for Long-Reach Ethernet (LRE) switches. Do not install this release on Catalyst 3500 XL switches or on Catalyst 2900 XL switches that are not LRE switches. For information about those switches, refer to Cisco IOS release 12.0(5)WC3b. When upgrading the LRE switch software, follow these rules: • • The minimum software version required on the LRE switches is Cisco IOS Release 12.0(5.3)WC(1). To upgrade the LRE switch software, use the CLI procedure described in the “Downloading the New Software and TFTP Server Application to Your Management Station” section on page 27, or the CMS procedure in the “Using CMS to Upgrade One or More Switches” section on page 28. Note The e2rb.bin file is required on the LRE switches. Do not delete this file. If you accidentally delete the e2rb.bin file, it available at this site: http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900LRE • If you are using the CLI to upgrade a switch, follow the steps in the “Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch” section on page 29. See the “Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch” section on page 29 before downloading the .tar file with the CLI. We recommend that you delete the existing LRE firmware file (e2rb.bin) from the switch (Step 6). After copying the new image and HTML files to the switch Flash memory (Step 16), install the new LRE firmware file (Step 17). [CSCdu27029] When using CMS, you cannot upgrade Catalyst 2900 XL, Catalyst 2900 LRE XL, or Catalyst 3500 XL switches at the same time. However, you can group together and upgrade Catalyst 1900 and Catalyst 2820 switches at the same time. For Catalyst 2900 LRE XL switches, enter the image_name.tar filename in the New File Name field. The .tar file contains both the IOS image and the web-management code. • • When using CMS to upgrade multiple switches from the Cisco TFTP server, the Cisco TFTP server application can process multiple requests and sessions. When using CMS to upgrade multiple switches from the Cisco TFTP server, you must first disable the TFTP Show File Transfer Progress and the Enable Logging options to avoid TFTP server failures. If you are performing multiple-switch upgrades with a different TFTP server, it must be capable of managing multiple requests and sessions at the same time. If you are using VSM to upgrade a specific switch, follow the steps in the “Using CMS to Upgrade One or More Switches” section on page 28. • Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 24 OL-2312-01 Upgrading the Switch Software Overview of the Switch Upgrade Process The software upgrade procedure has these major steps: • • Deciding which software files to download from Cisco.com, as described in the “Which Software Files to Download from Cisco.com” section on page 26. Downloading the .tar file from Cisco.com, as described in the “Downloading the New Software and TFTP Server Application to Your Management Station” section on page 27. This file contains the IOS image file, the e2rb.bin file, and the HTML files. From Cisco.com, you can also download a TFTP server application to copy the switch software from your PC to the switch, if necessary. The tar command extracts the IOS image, the e2rb.bin file, and the HTML files from the .tar file during the TFTP copy to the switch. • Copying the current startup configuration file, as described in the “Copying the Current Startup Configuration from the Switch to a PC or Server” section on page 27. When you upgrade a switch, the switch continues to operate while the new software is copied to Flash memory. If Flash memory has enough space, the new image is copied to the selected switch but does not replace the running image until you reboot the switch. If a failure occurs during the copy process, you can still reboot your switch by using the old image. If Flash memory does not have enough space for two images, the new image is copied over the existing one. Note If a failure occurs while copying a new image to the switch, and the old image has already been deleted, you will need to use the XMODEM protocol to recover an image for the switch. For more information, refer to the “Recovering from Corrupted Software” section in the “Troubleshooting” chapter of the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide. • Using CMS or the CLI to upgrade the software on your switch or switch cluster: – If you are using CMS to upgrade a switch, follow the steps in the “Using CMS to Upgrade One or More Switches” section on page 28. – If you are using the CLI to upgrade a switch, follow the steps in the “Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch” section on page 29. Features provided by the new software are not available until you reload the switch. Determining the Switch Software Version The IOS image is stored as a .bin file in a directory that is named with the IOS release. A subdirectory contains the HTML files needed for web management. The image is stored on the system board Flash device (flash:). Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 25 Upgrading the Switch Software You can use the show version user EXEC command to see the software version that is running on your switch. For example: 2900LRE-239-34> show version Cisco Internetwork Operating System Software IOS (tm) C2900xl Software (C2900xl-C3H2L9S-M), Version 12.0(5)WC4, RELEASE SOFT) Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Tue 02-Apr-02 12:57 by antonino Image text-base: 0x00003000, data-base: 0x0035AF3C You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that might be stored in Flash memory. Which Software Files to Download from Cisco.com New software releases are posted on Cisco.com and are also available through authorized resellers. From Cisco.com, you can also download a TFTP server application to copy the switch software from your PC to the switch. Table 7 describes the file extensions and what they mean for the upgrade procedure. Table 8 lists the software files that you need from Cisco.com. Note We recommend that you download the combined .tar file that contains the IOS image file, the e2rb.bin file, and the HTML files. The procedures in this document are for upgrading a switch by using the combined .tar file. Note The e2rb.bin file is required on the LRE switches. Do not delete this file. If you accidentally delete the e2rb.bin file, it available at this site: http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900LRE Table 7 Possible Extensions for IOS Software Files Extension Description .bin .tar The IOS image file and the e2rb.bin file that you can copy to the switch through TFTP. A compacted file from which you can extract files by using the tar privileged EXEC command. The .tar file that you download from Cisco.com contains both the .bin and HTML (CMS) files. Note The CMS files are only available in the .tar file. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 26 OL-2312-01 Upgrading the Switch Software Table 8 Catalyst 2900 LRE XL Switch Software Files Filename e2rb.bin c2900xl-c3h219s-mz.120-5.WC4.bin c2900xl-c3h219s-tar.120-5.WC4.tar Description LRE firmware file IOS image-only file LRE firmware file, IOS image file, and HTML (CMS) files Note The CMS files are only available in the .tar file. Downloading the New Software and TFTP Server Application to Your Management Station Follow these steps to download the new software and, if necessary, the TFTP server application, from Cisco.com to your management station: Step 1 Step 2 Use Table 8 to identify the files that you want to download. Download the files from one of these locations: If you have a SmartNet support contract, go to this URL, and download the appropriate files: http://www.cisco.com/cgi-bin/tablebuild.pl/cat2900XL If you do not have a SmartNet contract, go to this URL, and download the appropriate files: http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL Use the CLI or CMS to perform a TFTP transfer of the file or files to the switch after you have downloaded the correct files to your PC or workstation. The readme.txt file describes how to download the TFTP server application. New features provided by the software are not available until you reload the software. Step 3 Copying the Current Startup Configuration from the Switch to a PC or Server When you make changes to a switch configuration, your changes become part of the running configuration. When you enter the command to save those changes to the startup configuration, the switch copies the configuration to the config.text file in Flash memory. To ensure that you can recreate the configuration if a switch fails, you might want to copy the config.text file from the switch to a PC or server. The following procedure requires a configured TFTP server such as the Cisco TFTP server available on Cisco.com. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 27 Upgrading the Switch Software Beginning in privileged EXEC mode, follow these steps to copy a switch configuration file to the PC or server that has the TFTP server application: Step 1 Copy the file in Flash memory to the root directory of the TFTP server: switch# copy flash:config.text tftp Step 2 Enter the IP address of the device where the TFTP server resides: Address or name of remote host []? ip_address Step 3 Enter the name of the destination file (for example, config.text): Destination filename [config.text]? yes/no Step 4 Verify the copy by displaying the contents of the root directory on the PC or server. Using CMS to Upgrade One or More Switches You can use the Software Upgrade window in Cluster Manager to upgrade all or some of the switches in a cluster at once. Consider these conditions when doing an upgrade: • When using CMS, you cannot upgrade Catalyst 2900 XL, Catalyst 2900 LRE XL, or Catalyst 3500 XL switches at the same time. However, you can group together and upgrade Catalyst 1900 and Catalyst 2820 switches at the same time. For Catalyst 2900 LRE XL switches, enter the enter the image_name.tar filename in the New File Name field. The .tar file contains both the IOS image and the web-management code. • Upgrade Catalyst 1900 and Catalyst 2820 switches last. To function efficiently, these switches need to be rebooted shortly after the upgrade occurs. If you do not click Reboot Cluster in 30 seconds after the upgrade, the Catalyst 1900 and Catalyst 2820 switches automatically reboot. Follow these steps to use CMS to upgrade switch software. Refer to the online help for more details. Step 1 Step 2 In Cluster Manager, select System > Software Upgrade to display the Software Upgrade window. Enter the .tar filename that contains the switch software image and the web-management code. You can enter just the filename or a pathname into the New Image File Names field. You do not need to enter a pathname if the image file is in the directory that you have defined as the TFTP root directory. Note You can also use Cluster Manager to upgrade a single switch by following the same software upgrade procedure. Note Close your browser after the upgrade process is complete. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 28 OL-2312-01 Upgrading the Switch Software New images are copied to Flash memory and do not affect operation. The switch checks Flash memory to ensure that there is sufficient space before the upgrade takes place. If there is enough space, the new image is copied to the switch without replacing the old image, and after the new image is completely downloaded, the old one is erased. In this case, you can still reboot your switch by using the old image if a failure occurs during the copy process. If there is not enough space in Flash memory for the new and old images, the old image is deleted, and the new image is downloaded. Note If a failure occurs while copying a new image to the switch, and the old image has already been deleted, you need to use the XMODEM protocol to recover an image for the switch. For more information, refer to the “Recovering from Corrupted Software” section in the “Troubleshooting” chapter of the Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide. Note If you are upgrading a Catalyst 2900 LRE XL switch, see the “Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch” section. Recovering from an Incomplete CMS Software Upgrade If you do not follow the preceeding procedure, an upgrade can fail due to insufficient space because of multiple software images or other files in Flash memory. When the upgrade fails, the image file is copied to Flash memory, but there is insufficient space for the HTML files, and you lose access to CMS. If a failure occurs, ensure that the image file in Flash memory has the same name as the contents of the boot variable. You can compare these two names by following Steps 12 and 13 in the procedure. If the contents of the boot variable and the image file name are the same, the switch can reset successfully. If they are different, rename the image file, or reset the boot variable by entering the system boot name global configuration command. The boot variable and the image file name should be the same. To recover from the incomplete download of the HTML files, log in to the switch, and upgrade the software as described in the “Using the CLI to Upgrade LRE Member Switches” section on page 32. Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch Note This release is only for Long-Reach Ethernet (LRE) switches. Do not install this release on Catalyst 3500 XL switches or Catalyst 2900 XL switches that are not LRE switches. For information about those switches, refer to Cisco IOS release 12.0(5)WC3b. Follow these steps to upgrade the LRE switch software: Step 1 If your PC or workstation cannot act as a TFTP server, copy the file to a TFTP server to which you have access. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 29 Upgrading the Switch Software Step 2 Access the CLI by starting a Telnet session or by connecting to the switch console port through the RS-232 connector. To start a Telnet session on your PC or workstation, enter this command: server% telnet switch_ip_address Enter the Telnet password if you are prompted to do so. Step 3 Enter privileged EXEC mode: switch> enable switch# Enter a password if you are prompted to do so. Step 4 Display the name of the running (default) image file (BOOT path-list). This example shows the name in italic: switch# show boot BOOT path-list: Config file: Enable Break: Manual Boot: HELPER path-list: NVRAM/Config file buffer size: 32768 flash:current_image flash:config.text 1 no If there is no file defined in the BOOT path-list, enter the dir flash: privileged EXEC command to display the contents of Flash memory. The file named c2900XL-c3h2-mz-120-5.1.WC.1.bin is your previous image file. switch# dir flash: Directory of flash:/ 175 165 4 167 6 176 7 -rwx -rwx drwx -rwx -rwx -rwx -rwx 111 8192 10240 1496 111 1422 1750311 May May May May May Jan May 17 17 17 17 17 01 17 2001 2001 2001 2001 2001 1970 2001 13:25:53 13:22:13 13:25:52 13:21:46 13:23:41 00:14:43 13:24:58 info.ver e2rb.bin html config.text info env_vars c2900XL-c3h2s-mz.120-5.1.WC.1.bin 7741440 bytes total (4692992 bytes free) Step 5 Using the exact, case-sensitive name of the combined .tar file that you downloaded, rename the running image file to that name, and replace the .tar extension with a .bin extension. The image file name is then the same as the downloaded file name but with a .bin extension. This step does not affect the operation of the switch. switch# rename flash:c2900XL-c3h219s-mz.120-5.1.WC.1.bin flash:c2900XL-c3h219s-mz.120-5.3.WC.1.bin Destination filename [c2900XL-c3h2s-mz.120-5.3.WC.1.bin]? Step 6 Delete the e2rb.bin file: switch# delete flash:e2rb.bin Step 7 Step 8 Press Enter to confirm deletion of the e2rb.bin file. Enter global configuration mode: switch# config terminal Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 30 OL-2312-01 Upgrading the Switch Software Step 9 Disable access to the switch HTML pages: switch(config)# no IP http server Step 10 If you entered the boot global configuration command with the name of the image file, enter this command to change it to the new name: Note You do not need to perform this step if the show boot privileged EXEC command entered in Step 4 displays no image name; the switch automatically finds the correct file to use when it resets. switch(config)# boot system flash:new_image For example: switch(config)# boot system flash:c2900XL-c3h2s-mz-120-5.3.WC.1.bin Step 11 Return to privileged EXEC mode: switch(config)# end Step 12 Remove the HTML files: switch# delete flash:html/* Step 13 Step 14 Press Enter to confirm the deletion of each file. Do not press any other keys during this process. If upgrading from Release 11.2(8)SA5 or earlier, remove the files in the Snmp directory: switch# delete flash:html/Snmp/* Note Step 15 Step 16 Make sure the S in Snmp is uppercase. Press Enter to confirm the deletion of each file. Do not press any other keys during this process. Enter the following command to copy the new image and HTML files to the switch Flash memory: Caution In this step, the tar privileged EXEC command copies the combined .tar file that contains both the image and the HTML files. You do not need to copy an HTML.tar file in this procedure. switch# tar /x tftp://server_ip_address/path/filename.tar flash: Loading /path/filename.tar from server_ip_address (via VLAN1): ! extracting info (111 bytes) extracting c2900XL-c3h2s-mz.120-5.3.WC.1.bin (1750311 bytes)!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! html/ (directory) extracting html/ClusterBuilder.html.gz (670 bytes) extracting html/ClusterManager.html.gz (624 bytes) extracting html/back.html.gz (211 bytes)! ... Depending on the TFTP server being used, you might need to enter only one slash (/) after the server_ip_address in the tar privileged EXEC command. The tar privileged EXEC command extracts the IOS image and the HTML files from the combined .tar file during the TFTP copy to the switch. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 31 Upgrading the Switch Software Step 17 Copy the e2rb.bin file to the switch Flash memory: switch# copy tftp://server_ip_address/path/e2rb.bin flash: Destination filename [e2rb.bin]? Accessing tftp://server_ip_address/path/e2rb.bin... Loading /path/e2rb.bin from server_ip_address (via VLAN1): !! [OK - 8192 bytes] 8192 bytes copied in 0.259 secs Step 18 Enter global configuration mode: switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Step 19 Re-enable access to the switch HTTP pages: switch(config)# IP http server Step 20 Return to privileged EXEC mode: switch(config)# end Step 21 Reload the new software with this command: switch# reload System configuration has been modified. Save? [yes/no]: y Proceed with reload? [confirm] Step 22 Press Return to confirm the reload. Your Telnet session ends when the switch resets. After the switch reboots, use Telnet to return to the switch, and enter the privileged EXEC show version command to verify the upgrade procedure. If you have a previously opened browser session to the upgraded switch, close the browser, and restart it to ensure that you are using the latest HTML files. Step 23 Using the CLI to Upgrade LRE Member Switches Because a member switch might not be assigned an IP address, command-line software upgrades through TFTP are managed through the command switch. Upgrading Catalyst 2900 LRE XL Member Switches Follow these steps to upgrade the software on a Catalyst 2900 XL or Catalyst 3500 XL member switch: Step 1 In privileged EXEC mode on the command switch, display information about the cluster members: switch# show cluster members From the display, select the number of the member switch that you want to upgrade. The member number is in the SN column of the display. You need this member number for Step 2. Step 2 Log in to the member switch (for example, member number 1): switch# rcommand 1 Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 32 OL-2312-01 Related Documentation Step 3 Start the TFTP copy function as if you were initiating it from the command switch. switch-1# tar /x tftp://server_ip_address//path/filename.tar flash: Source IP address or hostname [server_ip_address]? Source filename [path/filename]? Destination filename [flash:new_image]? Loading /path/filename.bin from server_ip_address (via!) [OK - 843975 bytes] Step 4 Reload the new software with the following command: switch-1# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm] Press Enter to start the download. You lose contact with the switch while it reloads the software. For more information on the rcommand privileged EXEC command, refer to the Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference. Related Documentation You can order printed copies of documents with a DOC-xxxxxx= number. These publications provide more information about the switches and the switch software: • • • • • • • • • • Catalyst 2900 Series XL and Catalyst 3500 Series XL Software Configuration Guide (order number DOC-786511=) Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference (order number DOC-7812155=) Cluster Management Suite (CMS) online help (available only from the switch CMS software) Catalyst 2900 Series XL Hardware Installation Guide (order number DOC-786461=) Catalyst 3500 Series XL Hardware Installation Guide (order number DOC-786456=) Catalyst 2900 Series XL Modules Installation Guide (order number DOC-CAT2900-IG=) Catalyst 2900 Series XL ATM Modules Installation and Configuration Guide (order number DOC-785472=) 1000BASE-T Gigabit Interface Converter Installation Note (not orderable but is available on Cisco.com) Catalyst GigaStack Gigabit Interface Converter Hardware Installation Guide (order number DOC-786460=) Cisco LRE CPE Hardware Installation Guide (order number DOC-7811469=) Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 33 Obtaining Documentation Obtaining Documentation The following sections provide sources for obtaining documentation from Cisco Systems. World Wide Web You can access the most current Cisco documentation on the World Wide Web at the following sites: • • • http://www.cisco.com http://www-china.cisco.com http://www-europe.cisco.com Cisco Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Cisco Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription. Ordering Documentation Cisco documentation is available in the following ways: • Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace: http://www.cisco.com/cgi-bin/order/order_root.pl Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store: http://www.cisco.com/go/subscription Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387). • • Documentation Feedback If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. You can e-mail your comments to bug-doc@cisco.com. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 34 OL-2312-01 Obtaining Technical Assistance To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address: Cisco Systems, Inc. Document Resource Connection 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments. Obtaining Technical Assistance Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website. Cisco.com Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco. Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available. Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco. To access Cisco.com, go to the following website: http://www.cisco.com Technical Assistance Center The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract. Contacting TAC by Using the Cisco TAC Website If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website: http://www.cisco.com/tac Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 35 Obtaining Technical Assistance P3 and P4 level problems are defined as follows: • • P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue. P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration. In each of the above cases, use the Cisco TAC website to quickly find answers to your questions. To register for Cisco.com, go to the following website: http://www.cisco.com/register/ If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website: http://www.cisco.com/tac/caseopen Contacting TAC by Telephone If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml P1 and P2 level problems are defined as follows: • • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available. P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available. This document is to be used in conjunction with the documents listed in the “Related Documentation” section. CCIP, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0203R) Copyright © 2002, Cisco Systems, Inc. All rights reserved. Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 36 OL-2312-01 Obtaining Technical Assistance Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 OL-2312-01 37 Obtaining Technical Assistance Release Notes for the Catalyst 2900 LRE XL Switches, Cisco IOS Release 12.0(5)WC4 38 OL-2312-01