 Feedback
|
Table Of Contents
Release Notes for the Catalyst 2900 XL and Catalyst 3500 XL Switches, Cisco IOS Release 12.0(5)WC14
Browser and Java Plug-In Requirements
Cluster Requirements and Guidelines
Minimum Cisco IOS Release for Major Features
Installing the Required Plug-In
Displaying the CMS Access Page
Guidelines for Upgrading Switch Software
Overview of the Switch Upgrade Process
Determining the Switch Software Version
Which Software Files to Download from Cisco.com
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
Configuring for an LRE Upgrade
Global Configuration of LRE Upgrades
Controller Configuration of LRE Upgrades
Using the CLI to Upgrade an 8-MB Catalyst 2900 XL Switch
Using the CLI to Upgrade a Catalyst 3500 XL Switch
Cisco IOS Limitations and Restrictions
CMS Limitations and Restrictions
LRE Limitations and Restrictions
Resolved Caveats in Cisco IOS Release 12.0(5)WC14
Resolved Caveats in Cisco IOS Release 12.0(5)WC13
Resolved Caveats in Cisco IOS Release 12.0(5)WC12
Corrections to Software Configuration Guide
Correction to Command Reference
Corrections to Catalyst 2900 XL Hardware Installation Guide
Catalyst 2900 XL Hardware Installation Guide Corrections and Updates
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for the Catalyst 2900 XL and Catalyst 3500 XL Switches, Cisco IOS Release 12.0(5)WC14
September 7, 2006
Cisco IOS Release 12.0(5)WC14 runs on Catalyst 2900 series XL and Catalyst 3500 series XL switches with 8-MB CPU DRAM. This release also runs on Catalyst 2900 series Long-Reach Ethernet (LRE) XL switches with 16-MB CPU DRAM. This release does not run on Catalyst 2900 series XL switches with 4-MB CPU DRAM.
Note
Throughout this document, Catalyst 2900 XL switch refers to both the Catalyst 2900 XL switches and the Catalyst 2900 LRE XL switches, unless otherwise noted.
These release notes include important information about this Cisco IOS release and any limitations, restrictions, and caveats that apply to it. See the "Related Documentation" section for the complete list of Catalyst 2900 XL and Catalyst 3500 XL documentation.
Note
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:
•
•
•
You can download the switch software from this site:
•
(for registered Cisco.com users with a login password)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 the following sections:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Hardware Requirements
This release supports the 8-MB Catalyst 2900 XL switches (see Table 1), 16-MB Catalyst 2900 LRE XL switches, (see Table 2) and Catalyst 3500 XL switches (see Table 3).
Note
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:
•
•
•
•
•
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 4 lists the recommended platforms for using CMS.
Table 4 Recommended Minimum Platform Configuration for Web-Based Management
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)
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 5 lists the browsers supported by CMS.
CMS requires the Java plug-ins described in the "Installing the Required Plug-In" section.
Table 5 Browser Requirements
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
1 Netscape Communicator version 4.60 and 6.0 are not supported. (CSCdx34982)
2 CMS is not supported on machines running Windows 98 and Netscape Navigator. The workaround is to use Microsoft Internet Explorer if your operating system is Windows 98.
3 Microsoft Internet Explorer is not supported on Solaris 2.5.1 or higher.
Note
To access CMS, follow the procedures in the "Initial Switch Configuration" section.
Cluster Requirements and Guidelines
When creating a switch cluster, we recommend that the highest-end, command-capable switch in the cluster be the command switch and that the command switch has the latest software version installed. If there are switches in the cluster with older software versions, they should all be upgraded to the latest software version. All switches in the same platform should be upgraded to the latest software version.
Table 6 lists the cluster capabilities and minimum software versions for the switches. The switches are listed in the order of highest- to lowest-end switch. A lower-end switch cannot be the command switch of a switch listed above it in the table (for example, a Catalyst 2900 XL switch cannot be the command switch of a cluster that has Catalyst 3550 switches.)
Table 6 Switch Software and Cluster Capability
Catalyst 3750
Cisco IOS Release 12.1(11)AX
Member or command switch
Catalyst 3550
Cisco IOS Release 12.1(4)EA1 or later
Member or command switch
Catalyst 2970
Cisco IOS Release 12.1(11)AX
Member or command switch
Catalyst 2950
Cisco IOS Release 12.0(5.2)WC(1) or later
Member or command switch
Catalyst 2955
Cisco IOS Release 12.1(12c)EA1 or later
Member or command switch
Catalyst 2950-LRE
Cisco IOS Release 12.1(11)YJ
Member or command switch
Catalyst 2940
Cisco IOS Release 12.1(13)AY
Member or command switch
Catalyst 3500 XL
Cisco IOS Release 12.0(5.1)XU or later
Member or command switch
Catalyst 2900 LRE XL (16-MB switches)
Cisco IOS Release 12.0(5.1)WC1 or later
Member or command switch
Catalyst 2900 XL (8-MB switches)
Cisco IOS Release 12.0(5.1)XU or later
Member or command switch
Catalyst 2900 XL (4-MB switches)
Cisco IOS Release 11.2(8.5)SA6 (recommended)
Member switch only1
Catalyst 1900 and 2820
Cisco IOS Release 9.00(-A or -EN)
Member switch only
1 Catalyst 2900 XL (4-MB) switches appear in the front-panel and topology views of CMS. However, CMS does not support configuration or monitoring of these switches.
Some versions of the Catalyst 2900 XL software do not support clustering, and if you have a cluster with switches that are running different versions of Cisco IOS software, software features added 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 Catalyst 2900 XL switch running Cisco IOS Release 11.2(8)SA6, the windows and functionality can be different from a switch running Cisco IOS Release 12.0(5)WC(1) or later.
Note
New Features
There are no new hardware or software features for this release.
Minimum Cisco IOS Release for Major Features
Table 7 lists the minimum software release required to support the major features of the Catalyst 2900 XL and Catalyst 3500 XL switches.
Table 7 Catalyst 2900 XL (including 2900 LRE XL) and Catalyst 3500 XL Features and the Minimum Cisco IOS Release Required
Bridge protocol data unit (BPDU) filtering
Cisco IOS Release 12.0(5)WC7
Port security MAC address aging
Cisco IOS Release 12.0(5)WC5
Bridge protocol data unit (BPDU) guard
Cisco IOS Release 12.0(5)WC5
Remote Authentication Dial-In User Service (RADIUS)
Cisco IOS Release 12.0(5)WC5
UniDirectional Link Detection (UDLD) recovery
Cisco IOS Release 12.0(5)WC5
Support for the Cisco Coarse Wave Division Multiplexing (CWDM) Gigabit Interface Converter (GBIC) modules
Cisco IOS Release 12.0(5)WC5
Enhanced web-based switch management (CMS)
Cisco IOS Release 12.0(5)WC3
MAC address notification
Cisco IOS Release 12.0(5)WC3
Internet Group Management Protocol (IGMP) filtering
Cisco IOS 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
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)
Extended cluster member compatibility with the Catalyst 2950 and Catalyst 3550 switches
Cisco IOS Release 12.0(5)WC(1)
Multicast VLAN Registration (MVR)
Cisco IOS Release 12.0(5)WC(1)
Cross-stack UplinkFast
Cisco IOS Release 12.0(5)XW
Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration
Cisco IOS Release 12.0(5)XW
Support for the single-port 1000BASE-T GBIC module (WS-G5482)
Cisco IOS Release 12.0(5)XW
WS-C3524-PWR XL switch with 10/100 inline-power ports
Cisco IOS Release 12.0(5)XU
WS-C2924M-XL-EN-DC switch with DC power connector
Cisco IOS Release 12.0(5)XU
WS-X2932-XL Catalyst 2900 XL 1-port 1000BASE-T module
Cisco IOS Release 12.0(5)XU
Hot Standby Router Protocol (HSRP) for clustering
Cisco IOS Release 12.0(5)XU
Extended discovery of cluster candidates up to 7 hops from the command switch
Cisco IOS Release 12.0(5)XU
Support for up to 16 switches in a cluster
Cisco IOS Release 12.0(5)XU
VLAN Trunking Protocol (VTP) pruning
Cisco IOS Release 12.0(5)XU
Change management Virtual LAN (VLAN) for a cluster
Cisco IOS Release 12.0(5)XU
Private VLAN edge support
Cisco IOS Release 12.0(5)XU
UDLD for detecting unidirectional links
Cisco IOS Release 12.0(5)XU
Extended cluster member functionality for Catalyst 1900 and 2820 switches
Cisco IOS Release 12.0(5)XP
Remote monitoring (RMON) support through the command-line interface (CLI) or Simple Network Management Protocol (SNMP)
Cisco IOS Release Cisco IOS Release 12.0(5)XP
Change management VLAN
Cisco IOS Release 12.0(5)XP
Quality of service (QoS) based on IEEE 802.1P class of service (CoS) values
Cisco IOS Release 12.0(5)XP
WS-C3548-XL switch with 48 10/100 ports
Cisco IOS Release 12.0(5)XP
WS-X2931-XL Catalyst GigaStack GBIC module
Cisco IOS Release 12.0(5)XP
Catalyst 3500 series XL switches (except WS-C3548-XL)
Cisco IOS Release 11.2(8)SA6
Cluster management
Cisco IOS Release 11.2(8)SA6
Terminal Access Control Access System Plus (TACACS+)
Cisco IOS Release 11.2(8)SA6 (Enterprise Edition Software)
Network Time Protocol (NTP)
Cisco IOS Release 11.2(8)SA6
Spanning Tree Protocol (STP) UplinkFast
Cisco IOS Release 11.2(8)SA6
(Enterprise Edition Software)250 VLANs (some models: see the "Limitations and Restrictions" section)
Cisco IOS Release 11.2(8)SA6
Catalyst 2900 series XL 1000BASE-X modules
Cisco IOS Release 11.2(8)SA5
Catalyst 2900 series XL asynchronous transmission mode (ATM) modules
Cisco IOS Release 11.2(8)SA5
IEEE 802.1Q trunking
Cisco IOS Release 11.2(8)SA5
(Enterprise Edition Software)Inter-Switch Link (ISL) trunking
Cisco IOS Release 11.2(8)SA4
(Enterprise Edition Software)VLAN Membership Policy Server (VMPS)
Cisco IOS Release 11.2(8)SA4 (Enterprise Edition Software)
8192 media access control (MAC) addresses on modular switches
Cisco IOS Release 11.2(8)SA4
Switch Network View stack management
Cisco IOS Release 11.2(8)SA3
Web-based switch management
Cisco IOS Release 11.2(8)SA
Fast EtherChannel port groups
Cisco IOS Release 11.2(8)SA
Initial Switch Configuration
This section provides these procedures:
•
•
•
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
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:
Use this procedure to create an initial configuration for the switch:
Note
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
Continue with configuration dialog? [yes/no]: yStep 2
Enter IP address: ip_addressStep 3
Enter IP netmask: ip_netmaskStep 4
Would you like to enter a default gateway address? [yes]: yStep 5
IP address of the default gateway: ip_address
Note
Note
Step 6
Note
Enter enable secret: secret_passwordStep 7
Would you like to configure a Telnet password? [yes] y
Note
Step 8
Enter Telnet password: telnet_passwordStep 9
Note
Would you like to enable as a cluster command switch? yStep 10
Enter cluster name: cls_name
Note
Step 11
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 endStep 12
•
•
Use this configuration? [yes/no]: yAfter 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:
•
•
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. 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
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
From the Start menu, disable the options by selecting Start > Programs > Network Associates > Virus Scan Console > Configure.
or
From the task bar, 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
You must have Java plug-in 1.0.4 installed in order to run CMS. If you start CMS without having installed the required Java plug-in, CMS halts and displays this error message:
CMS will start momentarily. If it does not, please verify that JavaScript is enabled and the Java Plug-in is installed.
You will need to shut down CMS and download Java plug-in 1.0.4 from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Solaris Platforms
These Java plug-ins are supported on the Solaris platform:
Caution
•
•
•
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
Displaying the CMS Access Page
After the browser is configured, display the CMS access page:
Step 1
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
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
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.
Downloading Software
This section provides these topics about downloading the switch software:
•
•
•
•
•
•
•
•
•
•
Note
Guidelines for Upgrading Switch Software
When upgrading the LRE switch software, follow these rules:
•
•
•
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.
–
–
•
•
•
•
•
•
•
Overview of the Switch Upgrade Process
The software upgrade procedure has these major steps:
•
•
The tar command extracts the Cisco IOS image, the e2rb.bin LRE firmware file, and the CMS files from the tar file during the TFTP copy to the switch.
•
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 flash memory does not have enough space for two images, your new image is copied over the existing one.
Note
•
–
–
Features provided by the new software are not available until you reload the switch.
Determining the Switch Software Version
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the CMS 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:
Switch> show versionCisco Internetwork Operating System SoftwareIOS (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 usernameImage text-base: 0x00003000, data-base: 0x0034A3B8You 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
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 8 describes the file extensions and what they mean for the upgrade procedure. Table 9 and Table 10 list the software files that you need from Cisco.com.
Downloading the New Software
This procedure is for copying the combined tar file to the Catalyst 2900 XL or Catalyst 3500 XL switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
Note
Before downloading the new image, use the dir user EXEC command to confirm that you have enough space on the flash. The new image and HTML files will be slightly larger than the size of the tar file.
If you do not have enough space on the flash for the tar file, delete any old unused IOS images. If that does not free up enough flash space, delete the HTML files.
Caution
Follow these steps to download the software and, if necessary, the TFTP server application, from Cisco.com to your management station:
Step 1
Step 2
•
http://www.cisco.com/public/sw-center/sw-lan.shtml
To download the files, select Catalyst 2900XL Software, Catalyst 2900 LRE XL Software, or Catalyst 3500XL Software.
Step 3
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
switch# copy flash:config.text tftpStep 2
Address or name of remote host []? ip_addressStep 3
Destination filename [config.text]? yes/noStep 4
Archiving Software Images
Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to which you are upgrading. You should keep these copies of the archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. For more information, see Product Bulletin 2863 at this URL:
http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note
Upgrading the Switch
This section provides these topics about upgrading the switch:
•
•
•
•
•
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:
•
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.
–
–
•
Follow these steps to use CMS to upgrade switch software. Refer to the online help for more details.
Step 1
Step 2
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
Note
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
Recovering from an Incomplete CMS Software Upgrade
An upgrade failure can create multiple copies of Cisco IOS images and other files in flash memory. This would not leave enough space for the CMS 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 CMS files, log in to the switch, and upgrade the software as described in the "Upgrading Member Switches" section.
Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch
If you are upgrading a Catalyst 2900 XL switch that is not an LRE switch, see the "Recovering from an Incomplete CMS Software Upgrade" section.
Follow these steps to upgrade the LRE switch software:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enableswitch#Enter a password if you are prompted to do so.
Step 4
switch# show bootBOOT path-list: flash:current_image
Config file: flash:config.textEnable Break: 1Manual Boot: noHELPER path-list:NVRAM/Config filebuffer size: 32768If 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 -rwx 111 May 17 2001 13:25:53 info.ver165 -rwx 8192 May 17 2001 13:22:13 e2rb.bin4 drwx 10240 May 17 2001 13:25:52 html167 -rwx 1496 May 17 2001 13:21:46 config.text6 -rwx 111 May 17 2001 13:23:41 info176 -rwx 1422 Jan 01 1970 00:14:43 env_vars7741440 bytes total (4692992 bytes free)Step 5
switch# config terminalStep 6
switch(config)# no IP http serverStep 7
Note
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2900XL-c3h2s-mz-120-5.3.WC.1.binStep 8
switch(config)# endStep 9
switch# delete flash:html/*Step 10
Step 11
switch# delete flash:html/Snmp/*
Note
Step 12
Step 13
Caution
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 Cisco IOS image and the HTML files from the combined tar file during the TFTP copy to the switch.
Step 14
switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 15
switch(config)# IP http serverStep 16
switch(config)# endStep 17
switch# reloadSystem configuration has been modified. Save? [yes/no]: yProceed with reload? [confirm]Step 18
Your Telnet session ends when the switch resets.
Step 19
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 2900 LRE XL switch can store and properly apply LRE binaries if there are updates required to the firmware on the switch local LRE controllers or connected CPE devices.
Other upgrade-related features include:
•
•
Note
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:
•
•
•
Note
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:
•
•
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
Note
See the reference pages for the upgrade commands in the Catalyst 2900 XL and Catalyst 3500 XL 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:
Note
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:
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> enSwitch# hw-module slot 0 upgrade lreYou 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:
•
•
•
•
•
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 1/1You are about to start an LRE upgrade on CPE Lo0/1.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:Starting remote upgrade on CPE Lo0/100:21:51: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceLongReachEthernet0/1, changed state to downThe 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 up00:22:39: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceLongReachEthernet0/1, changed state to upThe 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 InterfaceLongReachEthernet0/1, changed state to downUpgrade data transfer is complete. Reset the CPE device.
00:23:56: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to upThe 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 UP00:23:59: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to up00:24:02: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceLongReachEthernet0/1, changed state to upOperation resumes in the profile link up state.
Switch#Using the CLI to Upgrade an 8-MB Catalyst 2900 XL Switch
Caution
This procedure is for upgrading Catalyst 2900 XL switches with 8 MB of DRAM. You upgrade a switch by extracting the Cisco IOS image file and the HTML files from a combined tar file. You copy the files to the switch from a TFTP server and extract the files by entering the tar privileged EXEC command with these results:
•
•
•
If you are unsure whether your switch has 4 MB or 8 MB of memory, you can verify memory capacity at Step 4.
Follow these steps to upgrade the switch software by using the tar privileged EXEC command to start a TFTP transfer:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enable switch#Enter a password if you are prompted to do so.
Step 4
switch# show versionCisco Internetwork Operating System Software IOS (tm)C2900XL Software (C2900XL-HS-M), Version 11.2(8.2)SA6, RELEASE SOFTWARE (fc1)Copyright (c) 1986-1998 by cisco Systems, Inc.Compiled Mon 23-Nov-98 20:59 by paulinesImage text-base: 0x00003000, data-base: 0x00202144ROM: Bootstrap program is C2900XL boot loader2900XL-EN-84.3 uptime is 1 day, 22 hours, 23 minutesSystem restarted by power-onRunning default softwarecisco WS-C2924-XL (PowerPC403GA) processor (revision 0x11)Processor board ID 0x0E, with hardware revision 0x01Last reset from power-onProcessor is running Enterprise Edition Software24 Ethernet/IEEE 802.3 interface(s)32K bytes of flash-simulated non-volatile configuration memory.Base ethernet MAC Address: 00:50:80:39:EC:40Motherboard assembly number: 73-3382-04Power supply part number: 34-0834-01Motherboard serial number: FAA02499G7XModel number: WS-C2924-XL-ENSystem serial number: FAA0250U03PConfiguration register is 0xFStep 5
switch# show bootIf there is no file defined in the BOOT path-list, enter the dir flash: privileged EXEC command to display the contents of flash memory. For example, the file named c2900XL-c3h2-mz-120-5.3.WC.1.bin is the image file.
c2900XL-c3h2-mz-120-5.3.WC.1.binswitch# dir flash:Directory of flash:/4 d--x 6848 Apr 04 1993 15:23:11 html6 -rwx 79 Apr 04 1993 15:20:34 env_vars5 ---x 106 Apr 04 1993 15:20:36 info68 -rwx 1399 May 16 2000 14:43:42 config.text259 ---x 106 Apr 04 1993 15:23:12 info.ver3612672 bytes total (940032 bytes free)Step 6
switch# config terminal Enter configuration commands, one per line. End with CNTL/Z.Step 7
switch(config)# no IP http serverStep 8
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2900XL-c3h2s-mz-120-5.3.WC.1.bin
Note
Step 9
switch(config)# endStep 10
switch# delete flash:html/*Step 11
Step 12
switch# delete flash:html/Snmp/*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.
Caution
Step 13
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 (1557286 bytes)!!!!!!!!!!!!!!!!!!!!html/ (directory)extracting html/Detective.html.gz (1139 bytes)!extracting html/ieGraph.html.gz (553 bytes)extracting html/DrawGraph.html.gz (787 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 command.
Step 14
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 15
switch(config)# IP http serverStep 16
switch(config)# endStep 17
switch# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm]Step 18
Your Telnet session ends when the switch resets.
Step 19
Using the CLI to Upgrade a Catalyst 3500 XL Switch
This procedure is for upgrading Catalyst 3500 XL switches by copying the combined tar file to the switch. You copy the files to the switch from a TFTP server and extract the files by entering the tar privileged EXEC command, with these results:
•
•
•
Follow these steps to upgrade the switch software by using a TFTP transfer:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enable switch#Enter the password if you are prompted to do so.
Step 4
switch# show boot BOOT path-list: flash:current_image Config file: flash:config.text Enable Break: 1 Manual Boot: no HELPER path-list: NVRAM/Config file buffer size: 32768
Step 5
Step 6
switch# rename flash:current_image flash:new_image Source filename [current_image]? Destination filename [new_image]?For example:
switch# rename flash:c3500XL-c3h2-mz-112.8.2-SA6.bin flash:c3500XL-c3h2s-mz-120-5.3.WC.1.binStep 7
switch# dir flash: Directory of flash:/3 -rwx 415 Jun 13 1993 05:15:37 placement.txt4 d--x 6848 May 03 2000 10:47:58 html70 -rwx 20 Mar 21 1993 09:17:03 prefs.text6 ---x 106 Mar 01 1993 21:56:52 info228 ---x 106 Apr 04 1993 15:17:54 info.ver69 -rwx 2188 Mar 13 1993 03:38:28 config.text230 -rwx 744 Mar 25 1993 19:16:46 vlan.dat115 -rwx 354 Mar 13 1993 04:17:15 env_vars3612672 bytes total (936960 bytes free)Step 8
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 9
switch(config)# no IP http serverStep 10
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c3500XL-c3h2s-mz-120-5.3.WC.1.bin
Note
Step 11
switch(config)# endStep 12
switch# delete flash:html/*Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Caution
Step 13
switch# tar /x tftp://server_ip_address/path/filename.tar flash: Loading /path/filename.tar from server_ip_address (via VLAN1):!) extracting info (110 bytes)extracting c3500XL-c3h2s-mz-120-5.3.WC.1.bin (1271095 bytes)!!!!!!!!!!!!!!!!!!!!html/ (directory)extracting html/Detective.html.gz (1139 bytes)!extracting html/ieGraph.html.gz (553 bytes)extracting html/DrawGraph.html.gz (787 bytes)extracting html/GraphFrame.html.gz (802 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.
Step 14
switch# config terminal Enter configuration commands, one per line. End with CNTL/Z.Step 15
switch(config)# IP http serverStep 16
switch(config)# endStep 17
switch# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm]Step 18
Your Telnet session ends when the switch resets.
Step 19
Upgrading Member Switches
Follow these steps to upgrade the software on a Catalyst 2900 XL or Catalyst 3500 XL member switch:
Step 1
switch# show cluster membersFrom 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
switch# rcommand 1Step 3
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
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 switch command reference.
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.
Cisco IOS Limitations and Restrictions
These are the Cisco IOS restrictions for this release.
•
The workaround is to do an snmpget dot1dBasePortIfIndex by using the index found from the snmpwalk dot1dTpFdbPort query. (CSCdz55568)
•
There is no workaround. (CSCdz73429)
•
The workaround is to use the command show interface status privileged EXEC command to find out the type of CWDM GBIC module that is installed in the switch. (CSCin29895)
•
•
•
Data transmission continues normally if the LRE link is restored. (CSCdt22573)
•
•
•
There is no workaround. This is a limitation of the Ethernet switch on the Cisco 585 LRE CPE. (CSCdx03708)
•
There is no workaround. (CSCdx25940)
•
When this occurs, the locked MAC address does not appear in the output of the show mac dynamic USER exec command, but it is still reachable because it is in the Content-Addressable Memory (CAM) table of the switch.
The workaround is to enter the clear mac-address-table secure interface interface-id privileged EXEC command on the secure port. (CSCdy88929)
•
•
•
The workaround is to make sure that the switch is able to make the initial contact with the TACACS+ server. Then, the configured timeouts and retries take effect. If the switch is reloaded, the timeout returns to 14 seconds until the TACACS server is reached. (CSCeg25894)
•
Note
•
•
Caution
•
•
•
Caution
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.
After resetting the configuration revision number, add the switch to the VTP domain.
Note
•
•
•
•
–
–
CMS Limitations and Restrictions
These are the Cluster Management Suite (CMS) restrictions for this release:
•
•
•
The workaround, if you do not want to disable the proxy server settings on the browser, is to download a browser from a different vendor and use it without the proxy server settings configured to access the CMS.
LRE Limitations and Restrictions
These are the LRE restrictions for this release:
•
Data transmission continues normally if the LRE link is restored. (CSCdt22573)
•
Note
The workaround is to set the LRE interface to the LRE-10 or the LRE-10LL profile. (CSCdv01167)
•
switch(config)# interface longReachEthernet 0/?<1-28> LongReachEthernet interface numberThe correct range is:
<1-24> LongReachEthernet interface numberThe workaround is to only use ports 1 through 24. (CSCdz78081)
•
A Catalyst 2900 LRE command switch command switch no longer fails when it receives SNMP packets with invalid variable bindings.
Important Notes
This section describes important information related to this release.
•
•
Note
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900LRE•
•
•
Note
Resolved Caveats
These caveats were resolved in these releases:
•
•
•
Resolved Caveats in Cisco IOS Release 12.0(5)WC14
These caveats were resolved in Cisco IOS Release 12.0(5)WC14:
•
An SNMP access list is now correctly applied when you enter the snmp-server tftp-server-list global configuration command.
•
Symptoms: Router may generate and/or forward crafted IP packets with the source IP address being the routers tunnel interface for GRE or mGRE tunnels. Incorrect packet decoding may be seen with "debug tunnel."
Conditions: The router needs to receive a specially crafted GRE packet sent to the tunnel end-point. The outer IP packet must come from the configured tunnel source and be sent to the configured tunnel destination IP address Present Routed bit must be set to 1.
Workaround: Upgrade Cisco IOS to a version containing fixes for: CSCuk27655 or CSCea22552 or CSCei62762.
Further information: On the 6th September 2006, Phenoelit Group posted an advisory:
* Cisco Systems IOS GRE decapsulation fault
Cisco's statement and further information are available on the Cisco public website at:
http://www.cisco.com/warp/public/707/cisco-sr-20060906-gre.shtml
•
The Cisco IOS Stack Group Bidding Protocol (SGBP) feature in certain versions of Cisco IOS software is vulnerable to a remotely-exploitable denial of service condition. Devices that do not support or have not enabled the SGBP protocol are not affected by this vulnerability. Cisco has made free software available to address this vulnerability for affected customers. There are workarounds available to mitigate the effects of the vulnerability.
Cisco has published a Security Advisory on this issue; it is available at http://www.cisco.com/warp/public/707/cisco-sa-20060118-sgbp.shtml
•
An interface no longer shuts down when 500 or more broadcasts are received on the interface before the port storm-control broadcast action shutdown interface configuration command is entered.
•
The assert message CEST: Assert failure in ../src-l2-les-common/stp_les_shim.c line 1340 has been replaced with this error message:
%MULTI_VLAN_PORT-2-PORT_FAULTY_CONNECT: Ensure that the multi-VLAN port is connected to the router/server port. System memory limit reached. Unexpected multi VLAN-port behavior.
The message appears when a large number of Spanning Tree Protocol (STP) topology-change notices are received on a multi-VLAN port due to a large number of VLANs assigned on the port.
Note
•
The interface listed in the logging source-interface interface configuration command is no longer administratively shut down after the device is reloaded or power cycled.
After you upgrade the switch to Cisco IOS Release 12.0(5)WC14, the interface might still be shut down. If this occurs, follow these steps:
a.
b.
c.
•
SNMP v2 traps now correctly send the internal SNMP variable sysUpTime as a TIMETICKS SNMP data type (in hundredths of a second). In previous releases, the SNMP v2 traps sent the sysUpTime variable as an INTEGER data type, and it was not read as a time value.
•
A vulnerability exists in the IOS HTTP server in which HTML code inserted into dynamically generated output, such as the output from a show buffers command, will be passed to the browser requesting the page. This HTML code could be interpreted by the client browser and potentially execute malicious commands against the device or other possible cross-site scripting attacks. Successful exploitation of this vulnerability requires that a user browse a page containing dynamic content in which HTML commands have been injected. Cisco will be making free software available to address this vulnerability for affected customers. There are workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20051201-http.shtml.
Resolved Caveats in Cisco IOS Release 12.0(5)WC13
These caveats were resolved in Cisco IOS Release 12.0(5)WC13:
•
Cisco IOS may permit arbitrary code execution after exploitation of a heap-based buffer overflow vulnerability. Cisco has included additional integrity checks in its software, as further described below, that are intended to reduce the likelihood of arbitrary code execution.
Cisco has made free software available that includes the additional integrity checks for affected customers.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20051102-timers.shtml
•
Through normal software maintenance processes, Cisco is removing deprecated functionality. These changes have no impact on system operation or feature availability.
Resolved Caveats in Cisco IOS Release 12.0(5)WC12
These Cisco IOS caveats were resolved in Cisco IOS Release 12.0(5)WC12:
•
A memory leak no longer occurs when a switch is configured with the logging synchronous global configuration command.
•
FCS errors, frame errors, alignment errors, and collision fragments no longer occur when you reload a Catalyst 2924 XL switch that has a 2914-XL-V (4-port FastEthernet [FE]) module installed.
•
A document that describes how the Internet Control Message Protocol (ICMP) could be used to perform a number of Denial of Service (DoS) attacks against the Transmission Control Protocol (TCP) is publicly available. This document has been published through the Internet Engineering Task Force (IETF) Internet Draft process and is entitled "ICMP Attacks Against TCP" (draft-gont-tcpm-icmp-attacks-03.txt).
These attacks, which only affect sessions terminating or originating on a device itself, can be of three types:
d.
e.
f.
Successful attacks can cause connection resets or reduction of throughput in existing connections, depending on the attack type.
Multiple Cisco products are affected by the attacks described in this Internet draft.
Cisco has made free software available to address these vulnerabilities. In some cases, there are workarounds available to reduce the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20050412-icmp.shtml
The disclosure of these vulnerabilities is being coordinated by the National Infrastructure Security Coordination Centre (NISCC), based in the United Kingdom. NISCC is working with multiple vendors whose products are potentially affected. Its posting is at this URL:
http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en
•
A memory leak no longer occurs on a Catalyst 3500 XL switch that has authentication, authorization, and accounting (AAA) configured with the aaa accounting exec default [start-stop | stop-only | wait-start] global configuration command.
•
When a Catalyst 3500 XL switch port and any other switch port are connected by an IEEE 802.1q trunk link, the port on the Catalyst 3500 XL switch no change to the PVID-inconsistent state if the native VLAN is changed from VLAN 1 to any other VLAN on both switches.
•
The logging source-interface vlan vlan-id global configuration command is now supported on a Catalyst 3500 XL switch.
•
A Catalyst 3500XL switch no longer fails or reloads when it is configured with these AAA commands:
aaa authorization commands 15 no_tacacs noneaaa authentication login default group list-name lineaaa accounting send stop-record authentication failure•
A switch no reloads under these conditions:
–
–
•
This error message no longer appears on a Catalyst 3500 XL switch when a default port is removed and the switch cannot use STP:
set_group_bandwidth: Group has no default portDocumentation Updates
These are the updates to the product documentation:
•
•
•
Corrections to Software Configuration Guide
These are corrections for the software configuration guide:
•
This is the correct procedure:
Beginning in privileged EXEC mode, follow these steps to assign a port for static-access VLAN membership:
•
After an upgrade is complete, the switch configuration shows this information about the LRE interfaces, which does not affect the switch functionality:
<output truncated>!controller LongReachEthernet 0!controller LongReachEthernet 1!controller LongReachEthernet 2!controller LongReachEthernet 3!controller LongReachEthernet 4!controller LongReachEthernet 5!controller LongReachEthernet 6!!<output truncated>•
/en/US/docs/ios/12_0/np1/configuration/guide/1cip.html#wp7406
•
By default, a trunk port sends to and receives traffic from all VLANs in the VLAN database. If the switch is configured with a number of VLANs and it is connected to Cisco IP Phones through IEEE 802.1Q trunk ports, the switch sends spanning-tree BPDUs for all VLANs to all of the phones. This can flood the phones with traffic.
Beginning in privileged EXEC mode, follow these steps to configure a VLAN list that allows only voice and data VLANs on the trunk port:
l
For more information about these commands, refer to the switch command reference.
•
The no snmp-server global configuration command disables all running versions on the device. No specific Cisco IOS command exists to enable SNMP. The first snmp-server global configuration command that you enter enables all versions of SNMP.
For more information about disabling and enabling SNMP, refer to the command reference for this release.
•
•
Note
•
•
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:
–
–
•
•
•
This is a correction to the "Controlling Switch Access with RADIUS" section in the "Configuring the System" chapter:
Note
These system messages were not included in the "System Messages" chapter:
Error Message AAAA-CLUSTER_MEMBER_1-3-INVSTATE:[chars]AUTHOR/[chars]:Internal state is invalid:astruct 0x[addr] ustruct 0x[addr]Explanation The data structures for the AAA feature are not initialized properly. This is an internal software error.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool at this URL: https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl.
Use the Bug Toolkit to look for similar reported problems at this URL: http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl.
For information about contacting TAC, refer to the "Obtaining Technical Assistance" section in the preface of the software configuration guide.
Error Message LRE_UPGRADE-4-INIT_RESOURCE: cannot locate lre firmware filesExplanation This message means that the LRE upgrade module cannot locate a required resource. The Long-Reach Ethernet (LRE) upgrade module requires a directory in flash memory named flash:/lre-bin. This directory stores the LRE-related firmware files for the LRE switch and the LRE CPE devices. The upgrade module cannot initialize unless a directory already exists in flash memory.
Recommended Action Verify that the flash:/lre-bin directory exists. If the directory is missing, create an empty directory named flash:/lre-bin. If the directory already exists, report this message to your Cisco technical support representative.
For more information about system messages, refer to the "System Messages" chapter of the Catalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide.
Error Message REDUNDANT POWER SYSTEM IS FAULTYExplanation This message means that the redundant power system (RPS) is not operating properly.
Recommended Action The RPS is not providing power to the switch. Verify that the AC power to the RPS is properly connected. If the RPS is correctly connected to AC power, verify that the cable between the RPS and the switch is properly connected. If that does not resolve the problem, contact your Cisco representative for a replacement.
Error Message VQPCLIENT-2-CHUNKFAIL Could not allocate memory for VQPExplanation This message means that the VQP Client process cannot allocate the required memory for its internal data structures.
Recommended Action There might be a memory shortage in the switch. Check the configuration and the number of features that are configured. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support privileged EXEC command to gather data that might provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message VQPCLIENT-2-DENY Host <mac addr> denied on interface <intf>Explanation This message means that the access for the host with the MAC address shown is denied by the VQP server on the interface. <mac addr> is the MAC address of the interface. <inft> is the interface number.
Recommended Action Verify the VMPS database file, or remove the host from the interface. This error message appears when either the wrong host is connected to the dynamic access port, on when the VMPS database does not contain the required host entry.
Error Message VQPCLIENT-2-INITFAIL Platform-specific VQP initialization failed. QuittingExplanation This message means that the VQP client process is not able to initialize the platform-specific software or hardware.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool at this URL: https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl.
Use the Bug Toolkit to look for similar reported problems at this URL: http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl.
For information about contacting TAC, see the "Obtaining Technical Assistance" section in the preface of the software configuration guide.
Error Message VQPCLIENT-2-IPSOCK Could not obtain IP socket.Explanation This message means that the VQP client process cannot open the IP socket to communicate to the VQP server.
Recommended Action Check the IP configuration for the management VLAN interface. Follow the IP address configuration and VQP client configuration steps listed in the configuration manual. If the problem persists, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message VQPCLIENT-2-PROCFAIL Could not create process for VQP. Quitting.Explanation This message means that the VQP client process is not starting on the switch. This process is required to configure the dynamic access ports with proper VLANs.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool at this URL: https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl.
Use the Bug Toolkit to look for similar reported problems at this URL: http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl.
For information about contacting TAC, see the "Obtaining Technical Assistance" section in the preface of the software configuration guide.
Error Message VQPCLIENT-2-SHUTDOWN Interface <intf> shutdown by VMPSExplanation This message means that the interface is shut down as requested by the VMPS configuration. <intf> is the interface number.
Recommended Action No action is required. This is only an informational message that means that the necessary action has been taken when the VQP Server provides the port status to the client process.
Error Message VQPCLIENT-2-TOOMANY Interface <intf> shutdown by active host limitRecommended Action This message means that the number of active hosts on the interface has reached the maximum limit of 20. <intf> is the interface number.
Recommended Action Reduce the number of hosts on the dynamic access port.
Error Message VQPCLIENT-3-IFNAME Invalid interface <intf> in responseRecommended Action This message means that the response from the VQP server does not contain the correct interface name. <intf> is the interface number.
Recommended Action Verify the VLAN Membership Policy Server (VMPS) configuration. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message VQPCLIENT-3-THROTTLE Throttling VLAN change on <intf>Explanation This message means that the VLAN assignment for the interface changed too frequently in a short time. <inft> is the interface number.
Recommended Action Check the VMPS configuration. Limit the number of hosts on the dynamic access port. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message VQPCLIENT-3-VLANNAME Invalid VLAN <intf> in responseExplanation This message means that the interface cannot be assigned to the VLAN specified by the server because either the VLAN name is wrong or a configuration error occurred. <inft> is the interface number.
Recommended Action Verify the VMPS configuration. Check the VLAN database configuration for the specified VLAN. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message VQPCLIENT-7-NEXTSERV Trying next VMPSExplanation This message means that the VQP client process is trying to contact the next VMPS server that is configured to get the response.
Recommended Action No action is required This is only an informational and debug message.
Error Message VQPCLIENT-7-PROBE Probing primary server <ipaddr>Explanation This message means that the VQP client process is trying to contact the primary VMPS server that is configured to check the connectivity. <ipaddr> is the server IP.
Recommended Action No action is required This is only an informational and debug message.
Error Message VQPCLIENT-7-RECONF Reconfirming VMPS responsesExplanation This message means that the VQP client process is trying to reconfirm the VLAN assignment for the dynamic access ports.
Recommended Action No action is required This is only an informational and debug message.
Correction to Command Reference
The lre rate selection sequence global configuration command was introduced in 12.0(5)WC6. The switch command reference incorrectly states that this command was introduced in 12.0(6)WC6.
Corrections to Catalyst 2900 XL Hardware Installation Guide
This information was not included in the "Overview" chapter of the Catalyst 2900 Series XL Hardware Installation Guide:
Note
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7505/portadpt/atm_port/pa_a3/
5117ovr.htm#1038789These corrections apply to the "Technical Specifications" chapter of the Catalyst 2900 Series XL Hardware Installation Guide:
Catalyst 2900 XL Hardware Installation Guide Corrections and Updates
This is a correction to fiber-optic power specifications in Table A-2 in the "Technical Specifications" chapter:
Table 11 Technical Specifications for the Catalyst 2924C XL Switches
Optical transmitter wavelength
1300 nm1
Optical receiver sensitivity
-19 to -14 dBm2
Optical transmitter power
-19 to -14 dBm
1 nm = nanometers
2 dBm = decibel milliwatt
•
•
–
–
These updated warnings apply to the "Translated Warnings Chapter" of the Catalyst 2900 Series XL Hardware Installation Guide:
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
Overtemperature Warning
Chassis Power Connection
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:
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Cisco will continue to support documentation orders using the Ordering tool:
•
http://www.cisco.com/en/US/partner/ordering/
•
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
•
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.htm
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section section.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0601R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Copyright © 1998-2006, Cisco Systems, Inc. All rights reserved.
