Table Of Contents
Release Notes for the Catalyst 2900 Series LRE XL Switches for Cisco IOS Release 12.0(5)WC6
Contents
Hardware Requirements
Software Requirements
System Requirements
Browser and Java Plug-In Requirements
Cluster Requirements and Guidelines
Catalyst 2900 XL and Catalyst 3500 XL Switches
Catalyst 3550 Switches
Catalyst 2950 Switches
Catalyst 1900 and Catalyst 2820 Switches
Minimum Cisco IOS Release for Major Features
New Software Features in this Release
Limitations and Restrictions
Open Caveats
Important Notes
Documentation Notes
General Documentation Notes
Updated Translated Warnings
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
Overtemperature Warning
Chassis Power Connection
Catalyst 2950G-24-EI-DC Service Requirement
Initial Switch Configuration
Using the Setup Program
Installing the Required Plug-In
Accessing CMS
Configuring the HTTP Server
Displaying the CMS Access Page
Upgrading the Switch IOS Software
Guidelines for Upgrading Switch Software
Overview of the Switch Upgrade Process
Determining the Switch Software Version
Which Software Files to Download from Cisco.com
Downloading the New Software and TFTP Server Application to Your Management Station
Copying the Current Startup Configuration from the Switch to a PC or Server
Using CMS to Upgrade One or More Switches
Recovering from an Incomplete CMS Software Upgrade
Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch
Upgrading LRE Firmware
Configuring for an LRE Upgrade
Performing an LRE Upgrade
Global Configuration of LRE Upgrades
Controller Configuration of LRE Upgrades
LRE Upgrade Behavior Details
LRE Upgrade Example
Related Documentation
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Cisco TAC Web Site
Cisco TAC Escalation Center
Release Notes for the Catalyst 2900 Series LRE XL Switches for Cisco IOS Release 12.0(5)WC6
November 2002
Cisco IOS Release 12.0(5)WC6 runs on the Catalyst 2900 series LRE XL switches with 8-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)WC5.
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.
•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 IOS Software" section.
You can download the switch software from these sites:
•http://www.cisco.com/public/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)
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.
Contents
This document has these sections:
•"Hardware Requirements" section
•"Software Requirements" section
•"Cluster Requirements and Guidelines" section
•"Minimum Cisco IOS Release for Major Features" section
•"New Software Features in this Release" section
•"Limitations and Restrictions" section
•"Open Caveats" section
•"Important Notes" section
•"Documentation Notes" section
•"Initial Switch Configuration" section
•"Upgrading the Switch IOS Software" section
•"Upgrading LRE Firmware" section
•"Related Documentation" section
•"Obtaining Documentation" section
•"Obtaining Technical Assistance" section
Hardware Requirements
Note Catalyst 3500 XL switches and Catalyst 2900 XL switches that are not LRE switches do not support this release. These switches can only be upgraded to Release 12.(5)WC5.
Note This release is not for the Catalyst 2900 XL 4-MB switches. The 4-MB models are WS-C2908-XL, WS-C2916M-XL, WS-C2924C-XL, and WS-C2924-XL. These switches can only be upgraded up to Release 11.2(8.10)SA6. To be cluster members, these switches must run Release 11.2(8.x)SA6 original edition software. To determine the switch DRAM size, enter the show version user EXEC command.
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)
•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 Recommended Minimum Platform Configuration for Web-Based Management
OS
|
Processor Speed
|
DRAM
|
Number of Colors
|
Resolution
|
Font Size
|
Windows NT 4.01
|
Pentium 300 MHz
|
128 MB
|
65,536
|
1024 x 768
|
Small
|
Solaris 2.5.1
|
SPARC 333 MHz
|
128 MB
|
Most colors for applications
|
-
|
Small (3)
|
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.
Table 3 Browser Requirements
Operating System
|
|
Microsoft Internet Explorer
|
Windows 95
|
4.61, 4.7
|
5.0, or 5.5
|
Windows 98
|
-2
|
5.0, or 5.5
|
Windows NT 4.0
|
4.61, 4.7
|
5.0, or 5.5
|
Windows 2000
|
4.61, 4.7
|
5.0, or 5.5
|
Solaris 2.5.1 or higher
|
4.61, 4.7
|
-3
|
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.
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 switch 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 switch 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.
Note We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, and Catalyst 3500 XL switches, either the Catalyst 2900 XL or Catalyst 3500 XL should be the command switch.
Table 4 Catalyst 2900 XL and Catalyst 3500 XL Switches as Cluster Members
Switch
|
Release 12.0(5.3)WC(1) or higher?
|
Command Capable?
|
Member Capable?
|
Catalyst 2900 XL (4 MB of DRAM)1
|
No
|
No
|
Yes
|
Catalyst 2900 XL (8 MB of DRAM)
|
Yes
|
Yes
|
Yes
|
Catalyst 2900 LRE XL (16 MB of DRAM)
|
Yes
|
Yes
|
Yes
|
Catalyst 3500 XL
|
Yes
|
Yes
|
Yes
|
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.
Note We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has a Catalyst 3550 switch, that switch should be the command switch.
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.
Note We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has Catalyst 2900 XL, Catalyst 2950, and Catalyst 3500 XL switches, the Catalyst 2950 should be the command switch.
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.
Note We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, and Catalyst 3500 XL switches, either the Catalyst 2900 XL or Catalyst 3500 XL should be the command switch.
Table 5 Catalyst 1900 and Catalyst 2820 Switches as Cluster Members
Switch
|
Release 9.00 (-EN)
|
Member Capable?
|
Command Capable?
|
Catalyst 1900
|
Yes
|
Yes
|
No
|
Catalyst 2820
|
Yes
|
Yes
|
No
|
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
|
Minimum Release Required
|
Enhanced web-based switch management (CMS)
|
Release 12.0(5)WC3
|
MAC address notification
|
Release 12.0(5)WC3
|
Internet Group Management Protocol (IGMP) filtering
|
Release 12.0(5)WC3
|
Support for the Cisco 585 LRE CPE device
|
Release 12.0(5)WC4
|
Enhanced web-based switch management (CMS)
|
Release 12.0(5)WC4
|
MAC Address Notification
|
Release 12.0(5)WC4
|
Internet Group Management Protocol (IGMP) Filtering
|
Release 12.0(5)WC4
|
Port security MAC address aging
|
Release 12.0(5)WC5
|
Bridge protocol data unit (BPDU) guard
|
Release 12.0(5)WC5
|
Remote Authentication Dial-In User Service (RADIUS)
|
Release 12.0(5)WC5
|
UniDirectional Link Detection (UDLD) recovery
|
Release 12.0(5)WC5
|
Support for the Cisco Coarse Wave Division Multiplexing (CWDM) Gigabit Interface Converter (GBIC) modules
|
Release 12.0(5)WC5
|
WS-C2912-LRE XL and WS-C2912-LRE XL switches with LRE ports and support for the Cisco 575 LRE CPE device
|
Release 12.0(5.1)WC(1)
|
Rate selection
|
Release 12.0(5)WC6
|
LRE switch firmware upgrade capability for the switch local LRE controllers or connected CPE devices
|
Release 12.0(5)WC6
|
Interoperability with Catalyst 2950ST-24-LRE and Catalyst 2950ST-8-LRE switches
|
Release 12.0(5)WC6
|
Extended cluster member compatibility with the Catalyst 2950 and Catalyst 3550 switches
|
Release 12.0(5)WC(1)
|
Multicast VLAN Registration (MVR)
|
Release 12.0(5)WC(1)
|
Cross-stack UplinkFast
|
Release 12.0(5)XW
|
Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration
|
Release 12.0(5)XW
|
Support for the single-port 1000BASE-T GBIC module (WS-G5482)
|
Release 12.0(5)XW
|
WS-C3524-PWR XL switch with 10/100 inline-power ports
|
Release 12.0(5)XU
|
WS-C2924M-XL-EN-DC switch with DC power connector
|
Release 12.0(5)XU
|
WS-X2932-XL Catalyst 2900 XL 1-port 1000BASE-T module
|
Release 12.0(5)XU
|
Hot Standby Router Protocol (HSRP) for clustering
|
Release 12.0(5)XU
|
Extended discovery of cluster candidates up to 7 hops from the command switch
|
Release 12.0(5)XU
|
Support for up to 16 switches in a cluster
|
Release 12.0(5)XU
|
VLAN Trunking Protocol (VTP) pruning
|
Release 12.0(5)XU
|
Change management virtual LAN (VLAN) for a cluster
|
Release 12.0(5)XU
|
Private VLAN edge support
|
Release 12.0(5)XU
|
UDLD for detecting unidirectional links
|
Release 12.0(5)XU
|
Extended cluster member functionality for Catalyst 1900 and 2820 switches
|
Release 12.0(5)XP
|
Remote monitoring (RMON) support through the command-line interface (CLI) or Simple Network Management Protocol (SNMP)
|
Release 12.0(5)XP
|
Change management VLAN
|
Release 12.0(5)XP
|
Quality of service (QoS) based on IEEE 802.1P class of service (CoS) values
|
Release 12.0(5)XP
|
WS-C3548-XL switch with 48 10/100 ports
|
Release 12.0(5)XP
|
WS-X2931-XL Catalyst GigaStack GBIC module
|
Release 12.0(5)XP
|
Catalyst 3500 series XL switches (except WS-C3548-XL)
|
Release 11.2(8)SA6
|
Cluster management
|
Release 11.2(8)SA6
|
Terminal Access Control Access System Plus (TACACS+)
|
Release 11.2(8)SA6 (Enterprise Edition Software)
|
Network Time Protocol (NTP)
|
Release 11.2(8)SA6
|
Spanning Tree Protocol (STP) UplinkFast
|
Release 11.2(8)SA6
(Enterprise Edition Software)
|
250 VLANs (some models: see the "Limitations and Restrictions" section)
|
Release 11.2(8)SA6
|
Catalyst 2900 series XL 1000BASE-X modules
|
Release 11.2(8)SA5
|
Catalyst 2900 series XL asynchronous transmission mode (ATM) modules
|
Release 11.2(8)SA5
|
IEEE 802.1Q trunking
|
Release 11.2(8)SA5
(Enterprise Edition Software)
|
Inter-Switch Link (ISL) trunking
|
Release 11.2(8)SA4
(Enterprise Edition Software)
|
VLAN Membership Policy Server (VMPS)
|
Release 11.2(8)SA4 (Enterprise Edition Software)
|
8192 media access control (MAC) addresses on modular switches
|
Release 11.2(8)SA4
|
Switch Network View stack management
|
Release 11.2(8)SA3
|
Web-based switch management
|
Release 11.2(8)SA
|
Fast EtherChannel port groups
|
Release 11.2(8)SA
|
New Software Features in this Release
Cisco IOS Release 12.0(5)WC6 contains these new features or enhancements:
•The config-lre-sequence global configuration command to create new sequences or to add or to delete profiles in a user-defined sequence.
•The config-lre-controller global configuration command for all upgrade related commands.
•CMS support for the rate selection and LRE upgrade features.
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.
•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 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, from 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 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)
•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 switch software configuration guide for a table that defines these conflicts.
•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
|
Purpose
|
Step 1
|
show vtp status
|
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. Write down the domain name.
b. Write down the configuration revision number.
c. Continue with the next steps to reset the configuration revision number on the switch.
|
Step 2
|
enable
|
Enter privileged EXEC mode.
|
Step 3
|
vlan database
|
Enter VLAN database mode.
|
Step 4
|
vtp domain domain-name
|
Change the domain name from the original one displayed in Step 1 to a new name.
|
Step 5
|
exit
|
The VLAN information on the switch is updated and the configuration revision number is reset to 0. You return to privileged EXEC mode.
|
Step 6
|
show vtp status
|
Verify that the configuration revision number has been reset to 0.
|
Step 7
|
vlan database
|
Enter VLAN database mode.
|
Step 8
|
vtp domain domain-name
|
Enter the original domain name on the switch.
|
Step 9
|
exit
|
The VLAN information on the switch is updated, and you return to privileged EXEC mode.
|
Step 10
|
show vtp status
|
(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.
•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.
Open Caveats
These are the open caveats in this release:
•CSCdv01167
A high number of collisions can occur for FTP transfers when a large number of packets are sent in a burst from a high-speed interface (such as Fa0/1) to a low-speed interface (such as Lo0/2), which can cause lower than expected transmission speeds.
The workaround is to set the LRE interface to the LRE-10 or the LRE-10LL profile.
Note Not all environments are able to support the LRE-10 profile.
•CSCdx03708
VLAN-tagged packets from multiple VLANs with the same source MAC address received on different Cisco 585 LRE CPE Ethernet ports create a single MAC address (ingress port entry). Any network designed with the assumption that MAC addresses are maintained per VLAN does not work.
There is no workaround; the Ethernet switch on the Cisco 585 LRE CPE does not support VLANs. All the ports are assumed to be in the same VLAN.
•CSCdx25940
Maximum-sized ISL frames (frames of between 1537 and 1544 bytes) are discarded by the CPE device on ingress. Some chips and switches on the CPE device support a maximum frame size of 1536 bytes, which causes any maximum-sized ISL frames coming into the CPE from an end device or from an LRE switch to be discarded.
There is no workaround. You must ensure that the network does not send ISL tagged frames of sizes between 1537 and 1544 bytes to an LRE switch.
•CSCdy40452
With LRE link persistence enabled, if you enter a shutdown command followed by a no shutdown command on the interface and wait for the LRE link to come up, when the link drops (for example, if you unplug the cable) the LRE link persistence function does not wait for the set delay duration before the link is reported as down. This only occurs the first time after a switch comes up and after a no shutdown command is entered.
The workaround is to remove the cable from the switchport and reconnect it. You can also reset the LRE interface with the command lre reset local.
•CSCdy82784
The running configuration includes lre cpe 5 speed 100 when your LRE switch is connected to a Cisco 585 LRE CPE, even though the Cisco 585 LRE CPE supports only four Ethernet ports.
There is no workaround.
•CSCdz36516
You can lose Ethernet connectivity on a remote CPE Fast Ethernet port if you shutdown remote CPE Fast Ethernet port from LRE interface, and then reload or reboot the switch without saving the current configuration.
The workaround is to issue the shutdown followed by no shutdown interface configuration commands.
Important Notes
This section describes important information related to this release.
•The cluster setup privileged EXEC command was removed in Release 12.0(5)WC5.
•The e2rb.bin LRE firmware file is required for the LRE switch operation. This file is deleted and then replaced with the most current version when you upgrade the LRE switch software. Do not delete this file after upgrading your LRE switch.
Note If you accidentally delete the e2rb.bin file after upgrading your switch, the file is available at this site:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900LRE
•The MVR threshold feature was removed in Release 12.0(5.3)WC(1). To limit rates, use the port multicast storm control feature instead of the MVR threshold feature.
Documentation Notes
You can access all Catalyst 2900 documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/index.htm
This section provides updates to the product documentation.
These changes will be included in the next version of the documentation.
General Documentation Notes
•This 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, and accessing CMS
–Procedures for upgrading the switch software
•DHCP autoconfiguration does not occur as described in the "DHCP Client Request Process" section under the "Using DHCP-Based Autoconfiguration" section in the software configuration guide.
When you start the switch, the switch automatically requests configuration information from a DHCP server only if a configuration file is not present on the switch.
DHCP autoconfiguration does not occur under these conditions:
–When a configuration file is present and the service config global configuration command is disabled on the switch.
–When a configuration file is present and the service config global configuration command is enabled on the switch. In this case, the switch broadcasts TFTP requests for the configuration file.
•The software configuration guide incorrectly states that flow control is supported on ports running at 100 Mbps in full-duplex mode. Flow control is supported only on installed, 1000-Mbps module ports.
•The 2900XL/3500XL documentation does not specify that Enterprise edition (which requires 8 Megabyes of flash) is required to configure TACACS+.
•In the Catalyst 2900 Series XL Hardware Installation Guide in the section "Technical Specifications," Table A-4 shows an incorrect figure for the power consumption. The actual power consumption is 70W rather than 150W.
•In the Catalyst 2900 Series XL Hardware Installation Guide in the section "Technical Specifications," Table A-4 should also include this information:
–2912 LRE XL and 2924 LRE XL KVA rating: 0.07 KVA
–2950 ST LRE KVA rating - 0.030 KVA
Updated Translated Warnings
These warnings have been updated for this release.
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
|
Warning
|
Attach only the Cisco RPS (model PWR300-AC-RPS-N1) to the RPS receptacle.
|
Waarschuwing
|
Slechts de Cisco RPS (model PWR300-AC-RPS-N1) aan de RPS contactdoos verbinden.
|
Varoitus
|
Kiinnitä RPS-vastakappaleeseen vain Cisco RPS (malli PWR300-AC-RPS-N1).
|
Avertissement
|
Raccordez le bloc d'alimentation Cisco RPS (modèle PWR300-AC-RPS-N1) uniquement au connecteur RPS.
|
Warnung
|
An die RPS-Steckhülse darf nur das Cisco RPS (Modell PWR300-AC-RPS-N1) angeschlossen werden.
|
Figyelem!
|
Az RPS csatlakozóhoz csak Cisco RPS (PWR300-AC-RPS-N1 modell) aljzatot csatlakoztasson.
|
Avvertenza
|
Collegare soltanto il Cisco RPS (modello PWR300-AC-RPS-N1) alla presa RPS.
|
Advarsel!
|
Koble bare Cisco RPS (modell PWR300-AC-RPS-N1) til RPS-stikkontakten.
|
Aviso
|
Anexe o RPS Cisco (modelo PWR300-AC-RPS-N1) apenas ao receptáculo RPS.
|
¡Advertencia!
|
Sólo conecte el Cisco RPS (modelo PWR300-AC-RPS-N1) al receptáculo RPS.
|
Varning!
|
Koppla endast Ciscos RPS (modell PWR300-AC-RPS-N1) till RPS-uttaget.
|
|
|
|
|
|
|
Overtemperature Warning
|
Warning
|
To prevent the switch from overheating, do not operate it in an area that exceeds the maximum recommended ambient temperature of 113°F (45°C). To prevent airflow restriction, allow at least 3 inches (7.6 cm) of clearance around the ventilation openings.
|
Waarschuwing
|
Om oververhitting van de schakelaar te voorkomen, mag u die niet bedienen in een ruimte die de maximale aanbevolen omgevingstemperatuur van 113°F (45°C) overschrijdt. Om beperking van de luchtstroom te voorkomen, dient u ten minste 3 inch (7,6 cm) speling te laten rondom de ventilatie-openingen.
|
Varoitus
|
Estääksesi kytkimen ylikuumenemisen älä käytä sitä sellaisissa paikoissa, joiden lämpötila ylittää ympäristön enimmäislämpötilaksi suositellun 45°C. Jätä vähintään 7,6 cm:n vapaa tila tuuletusaukkojen ympärille, jotta ilma pääsee vapaasti virtaamaan.
|
Attention
|
Pour éviter une surchauffe du commutateur, ne pas le faire fonctionner dans un local dont la température ambiante dépasse le maximum recommandé de 45°C (113°F). Pour faciliter la circulation d'air, aménager un dégagement d'au moins 7,6 cm (3 pouces) autour des bouches d'aération.
|
Warnung
|
Um eine Überhitzung des Schalters zu vermeiden, ist das System nicht in einem Bereich zu betreiben, in dem die empfohlene Höchsttemperatur von 45°C überschritten wird. Damit der Luftfluß nicht behindert wird, ist ein Freiraum von mindestens 7,6 cm um die Belüftungsöffnungen herum einzuhalten.
|
Figyelem!
|
A túlmelegedés megelõzése végett ne üzemeltesse a kapcsolót olyan területen, ahol a hõmérséklet meghaladja a 45°C maximális ajánlott környezeti hõmérsékletet. A megfelelõ légáramlás biztosítása érdekében a szellõzõnyílások körül hagyjon szabadon legalább 7,6 cm helyet.
|
Avvertenza
|
Per evitare il surriscaldamento dell'interruttore, non usare l'apparecchiatura in un'area che supera la temperatura ambientale minima consigliata di 45°C. Per evitare una limitazione del flusso dell'aria, lasciare come minimo uno spazio libero di 7,6 cm intorno alle aperture di ventilazione.
|
Advarsel
|
For å unngå at bryteren overopphetes skal utstyret ikke brukes på steder hvor anbefalt maks omgivelsestemperatur overstiger 113 grader Farenheit (45°C). La det være minst 3 tommer (7,6 cm) klaring rundt ventilasjonsåpningene for at luftsirkulasjonen skal være uhindret.
|
Aviso
|
Para evitar sobreaquecimento do interruptor, não utilize o equipamento numa àrea que exceda uma temperatura máxima de 45°C. Para evitar o bloqueamento da circulação de ar, deixe pelo menos um espaço de 7.6 cm em volta das aberturas de ventilação.
|
¡Advertencia!
|
Para evitar que el interruptor se recaliente, no se debe usar en áreas cuya temperatura ambiente exceda la máxima recomendada, esto es, 45°C (113°F). Para no entorpecer la corriente de aire, dejar por lo menos 7,6 cm (3 pulgadas) de espacio muerto alrededor de la rejilla de ventilación.
|
Varning!
|
För att undvika överhettning av strömbrytaren skall den inte användas i utrymme vars temperatur överskrider den maximalt rekommenderade omgivningstemperaturen 45°C. Kontrollera att det finns minst 7,6 cm fritt utrymme runt ventilationsöppningarna så att luftflödet inte begränsas.
|
|
|
|
|
|
|
Chassis Power Connection
|
Warning
|
Before connecting or disconnecting ground or power wires to the chassis, ensure that power is removed from the DC circuit. To ensure that all power is OFF, locate the circuit breaker on the panel board that services the DC circuit, switch the circuit breaker to the OFF position, and tape the switch handle of the circuit breaker in the OFF position.
|
Waarschuwing
|
Voordat u aarddraden of elektriciteitsdraden op het frame aansluit of van het frame neemt, dient u te controleren of de stroom naar het gelijkstroomcircuit uitgeschakeld is. Om u ervan te verzekeren dat alle stroom UIT is geschakeld, kiest u op het schakelbord de stroomverbreker die het gelijkstroomcircuit bedient, draait de stroomverbreker naar de UIT positie en plakt de schakelaarhendel van de stroomverbreker met plakband in de UIT positie vast.
|
Varoitus
|
Varmista, että tasavirtapiirissä ei ole virtaa ennen maadoitus- tai virtajohtojen kytkemistä asennuspohjaan tai ennen niiden irrottamista. Varmistaaksesi, että virta on KATKAISTU täysin, paikanna tasavirrasta huolehtivassa kojetaulussa sijaitseva suojakytkin, käännä suojakytkin KATKAISTU-asentoon ja teippaa suojakytkimen varsi niin, että se pysyy KATKAISTU-asennossa.
|
Attention
|
Avant de connecter ou de déconnecter les câbles d'alimentation (pôles et terre) du châssis, vérifiez que le circuit de courant continu est hors tension : localisez le disjoncteur sur le panneau de commande du circuit de courant continu, poussez-le sur la position fermée (OFF) et, à l'aide d'un ruban adhésif, bloquez sa poignée sur cette position.
|
Warnung
|
Gleichstrom-Unterbrechung Bevor Sie Erdungs- oder Stromkabel an das Chassis anschließen oder von ihm abtrennen, ist sicherzustellen, daß der Gleichstrom-Stromkreis unterbrochen ist. Um sicherzustellen, daß sämtlicher Strom AUS ist, machen Sie auf der Schalttafel den Unterbrecher für die Gleichstromschaltung ausfindig, stellen Sie den Unterbrecher auf OFF, und kleben Sie den Schaltergriff des Unterbrechers mit Klebeband in der AUS-Stellung fest.
|
Figyelem!
|
Mielõtt a föld- vagy a fázisvezetéket a házhoz csatlakoztatja, feltétlenül szakítsa meg az egyenáramú áramkör tápellátását. Úgy gondoskodhat arról, hogy mindenféle tápellátás meg legyen szakítva, hogy megkeresi az árammegszakítót az egyenáramú áramkört kiszolgáló kártyán, az árammegszakítót OFF (KI) helyzetbe állítja, és árammegszakító kapcsolóját az OFF (KI) helyzetben leragasztja.
|
Avvertenza
|
Prima di collegare o distaccare i cavi elettrici o di messa a terra dallo chassis, assicuratevi che il circuito DC non sia alimentato. Per verificare che tutta l'alimentazione sia scollegata (OFF), individuare l'interruttore automatico sul quadro strumenti che alimenta il circuito CC, mettere l'interruttore in posizione OFF e fissarlo con nastro adesivo in tale posizione.
|
Advarsel
|
Før til- eller frakobling av jord- og strømledninger til kabinettet, kontroller at strømmen er frakoblet likestrømkretsen. Sørg for at all strøm er slått AV. Dette gjøres ved å lokalisere strømbryteren på brytertavlen som betjener likestrømkretsen, slå strømbryteren AV og teipe bryterhåndtaket på strømbryteren i AV-stilling.
|
Aviso
|
Antes de conectar ou desconectar a ligação à terra ou a alimentação do chassis, certifique-se de que desligou a fonte de alimentação de energia do circuito de corrente contínua. Para se assegurar que toda a corrente foi DESLIGADA, localize o disjuntor no painel que serve o circuito de corrente contínua e coloque-o na posição OFF (Desligado), segurando nessa posição a manivela do interruptor do disjuntor com fita isoladora.
|
¡Advertencia!
|
Antes de conectar o desconectar el circuito de tierra o de alimentación del chasis, asegúrese que la alimentación del circuito CC esté cortada (OFF). Para asegurarse de que toda la alimentación esté cortada (OFF), localice el interruptor automático en el panel que alimenta el circuito de corriente continua, cambie el interruptor automático a la posición de apagado (OFF) y sujete con cinta la palanca del interruptor automático en posición de apagado (OFF).
|
Varning!
|
Innan du kopplar jord- eller elledningar till eller från chassit måste du kontrollera att strömförsörjningen till likströmskretsen är bruten. Kontrollera att all strömförsörjning är BRUTEN genom att slå AV det överspänningsskydd som skyddar likströmskretsen och tejpa fast överspänningsskyddets omkopplare i FRÅN-läget.
|
|
|
|
|
|
|
Catalyst 2950G-24-EI-DC Service Requirement
|
Warning
|
The Catalyst 2950G-24-EI-DC contains no field-replaceable units (FRUs). Do not open the chassis or attempt to remove or replace any components. For information about obtaining service for this unit, contact your reseller or Cisco sales representative.
|
Waarschuwing
|
De Catalyst 2950G-24-EI-DC bevat geen FRU's (field-replaceable units ofwel veldvervangbare eenheden). Open het chassis niet en probeer geen onderdelen te verwijderen of te vervangen. Voor informatie omtrent het onderhoud voor deze eenheid dient u contact op te nemen met uw doorverkoper of verkoopvertegenwoordiger van Cisco.
|
Varoitus
|
Catalyst 2950G-24-EI-DC ei sisällä kenttäkorjattavia laitteita. Runkoa ei saa avata, eikä osia saa yrittää poistaa tai korjata. Laitteen huoltoa koskevia tietoja saa jälleenmyyjältä tai Ciscon myyntiedustajalta.
|
Attention
|
Le Catalyst 2950G-24-EI-DC ne dispose pas d'unités remplaçables sur site (FRU). Il est recommandé de ne pas ouvrir le châssis ni de retirer ou remplacer des composants. Pour plus de détails sur la maintenance de cette unité, contactez votre revendeur ou votre ingénieur commercial Cisco.
|
Warnung
|
Der Catalyst 2950G-24-EI-DC enthält keine vor Ort austauschbaren Einheiten (FRUs). Das Gehäuse nicht öffnen und Komponenten nicht entfernen oder ersetzen. Serviceinformationen zu dieser Einheit erhalten Sie von Ihrem Wiederverkäufer oder von Ihrem Cisco-Vertreter.
|
Figyelem!
|
A Catalyst 2950G-24-EI-DC készülék nem tartalmaz helyszínen cserélhetõ részegységeket. Ne nyissa fel a házat, és ne próbálja meg eltávolítani vagy kicserélni semelyik alkatrészt. A készülékhez igénybe vehetõ karbantartási szolgáltatásokról viszonteladójától vagy Cisco értékesítési képviselõjétõl kérhet információt.
|
Avvertenza
|
Catalyst 2950G-24-EI-DC non ha componenti sostituibili sul posto (FRU). Non aprite lo chassis o tentate di rimuovere o sostituire componenti. Per maggiori informazioni sui servizi di assistenza per questo dispositivo, contattate il vostro rivenditore Cisco.
|
Advarsel
|
Catalyst 2950G-24-EI-DC inneholder ingen kunde-utskiftbare deler (FRU-deler). Gjør ikke forsøk på å åpne kabinettet eller fjerne eller skifte ut noen av komponentene. Ta kontakt med forhandleren eller en Cisco-salgsrepresentant for informasjon om hvor det kan utføres service på enheten.
|
Aviso
|
O interruptor Catalisador 2950G-24-EI-DC não contém nenhuma unidade substituível em campo. Não abrir o chassis ou tentar remover ou substituir quaisquer componentes. Para mais informações sobre a manutenção desta unidade, contactar o seu revendedor ou um representante de vendas da Cisco.
|
¡Advertencia!
|
El Catalyst 2950G-24-EI-DC no contiene componentes reemplazables en las instalaciones (Field-Replaceable Units, FRU). No abra el chasis ni intente reemplazar componentes. Para más información sobre cómo reparar este aparato, póngase en contacto con su distribuidor o representante de Cisco.
|
Varning!
|
Catalyst 2950G-24-EI-DC innehåller inte några enheter som kan bytas ut på fältet. Öppna inte chassit och försök inte heller att ta bort eller byta ut några delar. Kontakta återförsäljaren eller representanten för Cisco om du behöver information om service av enheten.
|
|
|
|
|
|
|
Initial Switch Configuration
This section provides these procedures:
•"Using the Setup Program" section
•"Installing the Required Plug-In" section
•"Displaying the CMS Access Page" section
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.
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 switch 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
Note Enter a host name for the switch, and press Return.
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.
Step 6 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 7 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.
Step 8 Enter the Telnet password, and press Return:
Enter Telnet password: telnet_password
Step 9 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 10 is not displayed.
Would you like to enable as a cluster command switch? y
Step 10 Assign a name to the cluster, and press Return.
Enter cluster name: cls_name
Note The cluster name can be 1 to 31 alphanumeric characters, dashes, or underscores.
Step 11 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
end
Step 12 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 and the "Displaying the CMS Access Page" section.)
•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 and the "Solaris Platforms" section.
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.
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/pcgi-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.
Accessing CMS
Before using the web-based CMS tools, see the "Software Requirements" section and the "Installing the Required Plug-In" section to set up the appropriate browser options. After you have assigned an IP address to the switch and installed the plug-in, you can access the switch from your browser and use the CMS to configure other switches.
Note If you have downloaded a new version of the CMS, you must clear your browser cache before launching the new CMS version.
The browser prompts for a username and password when you access CMS:
•If no username is configured on your switch (the default), you only need to enter the enable password in the appropriate field. For more information, see the "Displaying the CMS Access Page" section.
•If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch. For more information, see the "Configuring the HTTP Server" section.
Configuring the HTTP Server
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
| |
Command
|
Purpose
|
Step 1
|
configure terminal
|
Enter global configuration mode.
|
Step 2
|
ip http authentication {aaa | enable | local | tacacs}
|
Configure the HTTP server interface for the type of authentication you want to use.
•aaa—Means that the AAA facility is used for authentication.
•enable—Means that the enable password, which is the default method of HTTP server user authentication, is being used.
•local—Means that the local user database as defined on the Cisco router or access server is used for authentication.
•tacacs—Means that the TACACS server is used for authentication.
|
Step 3
|
end
|
Return to privileged EXEC mode.
|
Step 4
|
show running-config
|
Verify your entries.
|
After you have configured the HTTP server interface, display the CMS access page as described in "Displaying the CMS Access Page" section.
Displaying the CMS Access Page
After the browser is configured, display the CMS access page:
Step 1 Enter the switch IP address and your privilege level in the browser Location field (Netscape Communicator) or Address field (Microsoft Internet Explorer). For example:
http://10.1.126.45:184/level/14/
where 10.1.126.45 is the switch IP address, 184 is the HTTP port, and level/14 is the privilege level. You do not need to enter the HTTP port if the switch is using HTTP port 80 (the default) or enter the privilege level if you have read-write access to the switch (privilege level is 15).
For information about the HTTP port and privilege levels, refer to the switch software configuration guide.
Step 2 When prompted for a username and password, enter only the switch enable password. CMS prompts you a second time for a username and password. Enter only the enable password again.
If you configure a local username and password, make sure you enable it by using the ip http authentication global configuration command. Enter your username and password when prompted.
Step 3 Click Cluster Management Suite.
If you access CMS from a standalone or member switch, Device Manager appears. If you access CMS from a command switch, you can display the Front Panel and Topology views.
For complete information about CMS, refer to the switch software configuration guide.
Upgrading the Switch IOS Software
This section provides topics about upgrading the switch software:
•"Guidelines for Upgrading Switch Software" section
•"Overview of the Switch Upgrade Process" section
•"Determining the Switch Software Version" section
•"Which Software Files to Download from Cisco.com" section
•"Downloading the New Software and TFTP Server Application to Your Management Station" section
•"Copying the Current Startup Configuration from the Switch to a PC or Server" section
•"Using CMS to Upgrade One or More Switches" section
•"Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch" section
Note Before upgrading your switch to Release 12.0(5)WC6, read the "Guidelines for Upgrading Switch Software" section for important information.
Guidelines for Upgrading Switch Software
Note Release 12.0(5)WC6 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)WC5.
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 LREswitch software, use the CMS procedure described in the "Using CMS to Upgrade One or More Switches" section or use the CLI procedures described in the "Recovering from an Incomplete CMS Software Upgrade" section.
•If your switch is running Release 11.2(8)SA3, SA4, or SA5 (Catalyst 2900 XL only), we recommend that you upgrade the switch software by using VSM. If you are upgrading a switch running Release 11.2(8)SA6 or later to this release, we recommend that you use Cluster Manager. For CMS instructions for upgrading switch software, refer to the switch software configuration guide or the online help for that release.
•When using CMS, you cannot upgrade Catalyst 2900 XL, Catalyst 2900 LRE XL, and 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 XL and Catalyst 3500 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.
–For Catalyst 1900 and Catalyst 2820 switches, enter the image_name.bin filename in the New File Name field. The .bin file contains the software 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.
•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.
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.
•Downloading the .tar file from Cisco.com, as described in the "Downloading the New Software and TFTP Server Application to Your Management Station" section. This file contains the IOS image file, the e2rb.bin LRE firmware 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 LRE firmware 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.
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.
Note If a failure occurs during the copy process, you can still reboot your switch by using the old image that is still on the switch.
If Flash memory does not have enough space for two images, your 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 switch 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.
–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, the "Recovering from an Incomplete CMS Software Upgrade" section, the "Recovering from an Incomplete CMS Software Upgrade" section.
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:).
You can use the show version user EXEC command to see the software version that is running on your switch. For example:
3500-239-34> show version
Cisco Internetwork Operating System Software
IOS (tm) C3500xl Software (C3500xl-C3H2S-M), Version 12.0(0.0.2)WC5, RELEASE SOFT)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Tue 14-May-02 12:57 by antonino
Image text-base: 0x00003000, data-base: 0x0034A3B8
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.
Note You can use CMS to see the software versions that are running on all the switches in a cluster. Launch CMS, and select Reports > Inventory. CMS displays a window that shows the software versions for all the switches in the cluster.
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 and Table 9 list 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 LRE firmware file, and the HTML files. The procedures in this document are for upgrading a switch by using the combined .tar file.
Table 7 Possible Extensions for IOS Software Files
Extension
|
Description
|
.bin
|
The IOS image file and the e2rb.bin LRE firmware file that you can copy to the switch through TFTP.
|
.tar
|
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.
|
Table 8 Catalyst 2900 XL Switch Software Files
Filename
|
Description
|
c2900xl-c3h2s-mz.120-5.WC5a.bin
|
IOS image-only file
|
c2900xl-c3h2s-tar.120-5.WC5a.tar
|
IOS image file and HTML (CMS) files
Note The CMS files are only available in the .tar file.
|
Table 9 Catalyst 2900 LRE XL Switch Software Files
Filename
|
Description
|
e2rb.bin
|
LRE firmware file
|
c2900xl-c3h219s-mz.120-5.WC4.bin
|
IOS image-only file
|
c2900xl-c3h219s-tar.120-5.WC4.tar
|
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 Use Table 8 and Table 9 to identify the files that you want to download.
Step 2 Download the files from one of these locations:
If you have a SmartNet support contract, go to one of these URLs, and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XL
If you do not have a SmartNet contract, go to one of these URLs, and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XL
Step 3 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.
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.
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 image_name.tar filename in the New File Name field. The .tar file contains both the IOS image and the web-management code.
–For Catalyst 2900 XL and Catalyst 3500 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.
–For Catalyst 1900 and Catalyst 2820 switches, enter the image_name.bin filename in the New File Name field. The .bin file contains the switch software 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 In Cluster Manager, select System > Software Upgrade to display the Software Upgrade window.
Step 2 Enter the .tar filename (for Catalyst 2900 XL and Catalyst 3500 XL switches) or the .bin filename (for Catalyst 1900 and Catalyst 2820 switches) that contains the IOS 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 upgrade procedure.
Note Close your browser after the upgrade process is complete.
On the Catalyst 2900 XL and Catalyst 3500 XL switches, 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.
On the Catalyst 1900 and Catalyst 2820 switches, the new image overwrites the current image during the upgrade.
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 switch software configuration guide.
Recovering from an Incomplete CMS Software Upgrade
An upgrade failure can create multiple copies of IOS images and other files in Flash memory. This would not leave enough space for the HTML files to also be copied to Flash memory; thus, you will not be able to access the switch through CMS.
If a failure occurs, ensure that the image file in Flash memory has the same name as the contents of the boot variable.
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.
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)WC5.
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.
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:
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:
BOOT path-list: flash:current_image
Config file: flash:config.text
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.
175 -rwx 111 May 17 2001 13:25:53 info.ver
165 -rwx 8192 May 17 2001 13:22:13 e2rb.bin
4 drwx 10240 May 17 2001 13:25:52 html
167 -rwx 1496 May 17 2001 13:21:46 config.text
6 -rwx 111 May 17 2001 13:23:41 info
176 -rwx 1422 Jan 01 1970 00:14:43 env_vars
7 -rwx 1750311 May 17 2001 13:24:58 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 Enter global configuration mode:
Step 7 Disable access to the switch HTML pages:
switch(config)# no IP http server
Step 8 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 9 Return to privileged EXEC mode:
Step 10 Remove the HTML files:
switch# delete flash:html/*
Step 11 Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 12 If upgrading from Release 11.2(8)SA5 or earlier, remove the files in the Snmp directory:
switch# delete flash:html/Snmp/*
Note Make sure the S in Snmp is uppercase.
Step 13 Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 14 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 the IOS image file, the e2rb.bin LRE firmware file, 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)!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
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.
Step 15 Enter global configuration mode:
switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 16 Re-enable access to the switch HTTP pages:
switch(config)# IP http server
Step 17 Return to privileged EXEC mode:
Step 18 Reload the new software with this command:
System configuration has been modified. Save? [yes/no]: y
Proceed with reload? [confirm]
Step 19 Press Return to confirm the reload.
Your Telnet session ends when the switch resets.
Step 20 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.
Upgrading LRE Firmware
The 2950 LRE switch has the capability to store and properly apply LRE binaries in case there are updates required to the firmware on the switch local LRE controllers or connected CPE devices.
Other upgrade-related features include:
•Access to an earlier version of the LRE software if required.
•Simplifying the upgrade process as much as possible, especially in cases where you want to upgrade multiple CPE devices by entering a single command.
Note Whether upgrading a single CPE device or all CPE devices connected to an LRE switch, the expected duration of an LRE upgrade is 3 to 6 minutes (CPE devices connected to marginal links might take longer than this to upgrade).
You perform an upgrade with this command:
hw-module slot x upgrade lre [force][local lo n | remote lo x/y]
Automatic upgrading is not supported. You can upgrade in one of these ways:
•Upgrade a single remote CPE device.
•Upgrade a single local LRE controller (local LRE chipset).
•Upgrade all CPE devices and local chipsets that require an upgrade (a system-wide upgrade, which is the default)
Note There are no LRE firmware upgrade patch files available with this release.
Configuring for an LRE Upgrade
In the absence of any LRE Upgrade configurations, the LRE upgrade attempts to upgrade all local LRE controllers and CPE devices to the most recent compatible versions of the LRE binaries required for each LRE target device. LRE upgrade configurations should rarely be required. The primary purpose of LRE upgrade configuration commands is to provide for downgrades of LRE binaries.
If you wish to override the switch automatic selection of LRE binaries, you have two methods available:
•Global LRE upgrade configuration commands
•LRE Controller configuration commands
You can use config global commands to specify the LRE binary or binaries for a specified target type. (A target type is the family [and optionally the model or model revision] of a device containing one or more upgradable hardware elements.) A target can be a local LRE controller on the switch or a remote CPE device.
You can perform global LRE upgrade configurations by entering LRE upgrade controller configuration commands from the controller configuration submode. Use the upgrade configuration command in the controller submode to override the system default selection of an LRE binary to be applied on a particular remote CPE device or local LRE controller. Controller configurations take precedence over global upgrade configurations.
The preserve keyword causes the LRE upgrade mechanism to not upgrade the local controller on which preserve is configured or any of the CPE devices connected to that controller. If you want to preserve (in other words, not upgrade) some of the CPE devices connected to a particular controller but allow upgrades to others, you can enter controller upgrade configuration commands for the links that you want to upgrade.
The no form of the upgrade command removes the command for applying a particular LRE binary. To resume default upgrade behavior for a given controller, configure the no upgrade commands on that controller.
Note You also need to remove global configurations that might also affect the controller and devices connected to it.
Note When a config global command and a config controller command conflict, the config controller command has precedence.
See the reference pages for the upgrade commands in the Catalyst 2950 Desktop Switch Command Reference for further details.
Performing an LRE Upgrade
You can upgrade either on a system-wide basis (in other words, upgrading the software on all connected CPE devices and local LRE chipsets) or on individual CPE device or LRE controllers. By default, a system-wide upgrade applies the most recent versions of LRE binaries that are most compatible with each upgradable hardware module. The system-wide upgrade method is the one that you use in almost all situations.
When executing upgrades, you can elect to upgrade a single CPE device or local controller by using this command hw-module slot <x> upgrade lre [local lo n | remote lo x/y]. If no local or remote option is given, a system-wide upgrade is performed.
Global Configuration of LRE Upgrades
Beginning in privileged EXEC mode, follow these steps to perform a system-wide upgrade to configure the LRE binary to apply to a target device and upgradable hardware element combination:
| |
Command
|
Purpose
|
Step 1
|
configure terminal
|
Enter global configuration mode.
|
Step 2
|
lre binary default target_device LRE_binary
|
Enter the device to which the LRE binary should be applied; and the LRE binary to be applied.
|
Step 3
|
end
|
Return to privileged EXEC mode.
|
Step 4
|
show lre upgrade version
|
Verify the change.
|
Note The lre upgrade default mode command essentially overrides the system default selection of an LRE binary for a specified family of CPE devices (target device).
Controller Configuration of LRE Upgrades
Beginning in privileged EXEC mode, follow these steps to explicitly direct the LRE binaries to be applied to either the local controller or a specific VDSL link:
| |
Command
|
Purpose
|
Step 1
|
configure terminal
|
Enter global configuration mode.
|
Step 2
|
controller lre chipset_number
|
Enter the particular LRE local chipset on the switch to be applied.
|
Step 3
|
upgrade <[remote lo x/y] LRE_Binary | preserve>
|
Enter the LRE binary to be applied, or set preserve, which prevents the upgrade of any CPE devices connected to a controller or local chipset.
|
Step 4
|
end
|
Return to privileged EXEC mode.
|
Step 5
|
show lre upgrade version
|
Verify the change.
|
You can use the upgrade configuration command in the controller submode to override the system default selection of an LRE binary that will be applied on either end of a particular LRE link. Controller configurations take precedence over global upgrade configurations.
The preserve keyword causes the LRE upgrade mechanism to not upgrade the local controller on which preserve is configured or any of the CPE devices connected to that controller. If you want to preserve (in other words, not upgrade) some of the CPE devices connected to a particular controller but allow upgrades to others, you can enter controller upgrade configuration commands for the links you want to upgrade.
The no form of the command removes the command for applying a particular LRE binary. To resume default upgrade behavior for a given controller, do not configure the custom upgrade commands on that controller.
LRE Upgrade Behavior Details
You see on the console screen when you start an upgrade:
Switch#hw-module slot 0 upgrade lre
You are about to start an LRE upgrade on all LRE interfaces.
Users on LRE links being upgraded will experience a temporary disruption of Ethernet
connectivity.
Start LRE upgrade ? [yes]:
If you answer yes or press the Enter key, the upgrade starts. If you answer no, you get the EXEC prompt.
You can expect this link behavior of the CPE device during an upgrade:
•When the upgrade starts, the link is probably in the link-up state, the state of the link that is useful to you.
•When the upgrade starts, the remote CPE device resets. Ethernet connectivity is temporarily lost at this point.
•The CPE device comes up, with the link slower (about 1 Mbps upstream and 4 Mbps downstream) but more reliable. The increased reliability is required for a successful LRE binary transfer. The LRE link stays at a slower speed for the duration of the upgrade. Ethernet connectivity is available.
•When the upgrade is complete, the CPE device is again reset so that the upgraded LRE binaries are loaded and executed on the target CPE device(s) and local LRE chipsets. Ethernet connectivity is again disrupted until the CPE device comes out of reset.
•The link comes up when the CPE device comes back up, and then progresses to where it resumes full operation at its intended data rate.
LRE Upgrade Example
The following is an example of how an LRE upgrade can proceed:
Switch#hw-module slot 0 upgrade lre force remote lo 0/1
You are about to start an LRE upgrade on CPE Lo0/1.
Users on LRE links being upgraded will experience a temporary
disruption of Ethernet connectivity.
Start LRE upgrade ? [yes]:
Starting remote upgrade on CPE Lo0/1
00:21:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface
LongReachEthernet0/1, changed state to down
The CPE device is reset and the link is down. Ethernet connectivity is unavailable at this point.
00:22:37: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to up
00:22:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface
LongReachEthernet0/1, changed state to up
The CPE device comes out of reset. Ethernet connectivity is available but at low speeds. Upgrade data transfer begins.
00:23:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface
LongReachEthernet0/1, changed state to down
Upgrade data transfer is complete. Reset the CPE device.
00:23:56: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to up
The CPE device has come out of reset. The desired profile is applied.
00:23:58: %LRE_LINK-3-UPDOWN: Interface Lo0/1, changed state to UP
00:23:59: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to up
00:24:02: %LINEPROTO-5-UPDOWN: Line protocol on Interface
LongReachEthernet0/1, changed state to up
Operation resumes in the profile link up state.
Related Documentation
You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the "Obtaining Documentation" section.
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=)
•Installation Note for the CWDM Passive Optical System (not orderable but available on Cisco.com)
•Cisco LRE CPE Hardware Installation Guide (order number DOC-7811469=)
•Release Notes for the Cisco LRE CPE (not orderable but is available on Cisco.com)
Obtaining Documentation
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The 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 through an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/public/ordsum.html
•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 Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: 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 online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
http://www.cisco.com
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, the Cisco Arrow logo, 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. (0208R)
Copyright © 1998-2002, Cisco Systems, Inc.
All rights reserved.
