Table Of Contents
Release Notes for the
Catalyst 2900 Series XL and 3500 Series XL Cisco IOS Release 12.0(5)XWCreating Clusters with Different Releases of IOS Software
Creating Clusters with Catalyst 1900 and 2820 Switches
Minimum IOS Release for Major Features
Upgrading to a New Software Release
Upgrading a Switch by Using the VSM or Cluster Manager
Recovering from an Incomplete VSM Software Upgrade
Upgrading a Switch by Using the CLI
Upgrading Catalyst 3500 Series XL Switches
Upgrading 8-MB Catalyst 2900 Series XL Switches
Installing the Required Plug-In
Windows 95, Windows 98, and Windows NT 4.0 Users
New Hardware Features in Release 12.0(5)XW
New Software Features in Release 12.0(5)XW
Setting Up the Catalyst 2900 XL Initial Configuration
Configuring Voice Ports to Carry Voice and Data Traffic on Different VLANs
Understanding Cross-Stack UplinkFast
Events that Cause Fast Convergence
Configuring Cross-Stack UplinkFast
Understanding DHCP-Based Autoconfiguration
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Release Notes for the
Catalyst 2900 Series XL and 3500 Series XL Cisco IOS Release 12.0(5)XW
December 18, 2000 (Document revised April, 2001)
Cisco IOS Release 12.0(5)XW runs on Catalyst 3500 series XL switches and Catalyst 2900 series XL 8-MB CPU DRAM switches. Catalyst 2900 series XL 4-MB CPU DRAM switches are not supported.
These release notes include important information about this IOS release and any limitations, restrictions, and caveats that apply to it. See the "Related Documentation" section for the complete list of Catalyst 2900 and 3500 XL switch documentation.
Note
Before upgrading your switch to Release 12.0(5)XW, read the "Upgrading to a New Software Release" section for important information.
This IOS 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 IOS releases become available, they will be posted to CCO in the Cisco IOS software area.
Contents
This document has the following sections:
•
•
•
•
•
•
•
•
System Requirements
This section describes these system requirements for Release 12.0(5)XW:
•
•
Hardware Supported
Table 1 lists the supported Catalyst 3500 XL switches, and Table 2 lists the supported 8-MB Catalyst 2900 XL switches.
Catalyst 2900 series XL 4-MB switches run original edition software and are not supported. These switches can be updated only to Release 11.2(8.6)SA6.
Software Compatibility
This section describes these software compatibility requirements for Release 12.0(5)XW:
•
•
Browser Support
You can access the web-based interfaces through the browsers listed in Table 3. The switch checks the browser version when starting a session to ensure that the browser is supported. If the browser is not supported, the switch displays an error message, and the session does not start.
Netscape Communicator version 4.60 is not supported.
Note
To use the Cluster Management Suite (CMS), complete the browser-configuration instructions described in the Cisco IOS Desktop Switching Software Configuration Guide.
Creating Clusters with Different Releases of IOS Software
Some versions of the Catalyst 2900 and 3500 XL 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 operating with the same level of software, we recommend that you upgrade all cluster switches to Release 12.0(5)XP or later. Table 4 lists the available versions of clustering software and their capabilities.
If you have a cluster with switches that are running different versions of IOS software, changes on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)XU or later.
Creating Clusters with Catalyst 1900 and 2820 Switches
Catalyst 1900 and 2820 switches are always member switches, not command switches. However, a cluster with a command switch that is running Release 11.2(8)SA6 cannot communicate with a Catalyst 1900 or 2820. This means that if the command switch is running Release 11.2(8)SA6, the CMS does not support a Catalyst 1900 or 2820 switch in these CMS features:
•
•
•
•
Minimum IOS Release for Major Features
Table 5 lists the minimum IOS release required to support the major features of the Catalyst 2900 and 3500 XL switches.
Table 5 Catalyst 2900 and 3500 Series XL Features and the Minimum IOS Release Required
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 1000BaseT Gigabit Ethernet GBIC (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
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
VTP pruning
Release 12.0(5)XU
Change management VLAN for a cluster
Release 12.0(5)XU
Private VLAN edge support
Release 12.0(5)XU
UniDirectional Link Detection (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
Catalyst 3500 series XL switches (except 3548 XL)
Release 11.2(8)SA6
Catalyst 3548 XL switch
Release 12.0(5)XP
Cluster management
Release 11.2(8)SA6
Terminal Access Control Access Server+ (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 1000BaseX modules
Release 11.2(8)SA5
Catalyst 2900 series XL ATM modules
Release 11.2(8)SA5
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
Inter-Switch Link (ISL) trunking
Release 11.2(8)SA4
(Enterprise Edition Software)IEEE 802.1Q trunking
Release 11.2(8)SA5
(Enterprise Edition Software)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
Upgrading to a New Software Release
This section describes these procedures for upgrading your switch software:
•
•
•
•
•
Caution
Note
Upgrading a Switch by Using the VSM or Cluster Manager
If your switch is running Release 11.2(8)SA3, SA4, or SA5, we recommend that you upgrade the switch software by using the web-based 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.
If you are using VSM to upgrade a switch running Release 11.2(8)SA6 or later, follow the procedure in the "Using VSM to Upgrade a Switch" section.
General instructions for upgrading switch software are included in the Cisco IOS Desktop Switching Software Configuration Guide; detailed instructions are provided in the online help files.
Note
Using VSM to Upgrade a Switch
Note
Tips
Note
Follow these steps to rename the image file by using the CLI, and then use VSM to upgrade the software:
Step 1
To start a Telnet session on your PC or workstation, enter the following command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 2
switch> enable switch#Enter the password if you are prompted to do so.
Step 3
switch# dir flash:Directory of flash:/2 -rwx 4484 Mar 05 1993 00:31:09 vlan.dat3 -rwx 110 Mar 01 1993 19:50:50 info92 -rwx 877 Mar 06 1993 18:39:38 placement.txt5 -rwx 1644050 Mar 01 1993 19:36:14 c2900XL-c3h2s-mz-112.8.SA6.bin6 drwx 6720 Mar 01 1993 00:18:36 html86 -rwx 110 Mar 01 1993 19:37:00 info.ver116 -rwx 3686 Mar 01 1993 19:55:33 config.text89 -rwx 25 Mar 01 1993 00:26:30 snmpengineid7 -rwx 313 Mar 01 1993 19:34:57 env_varsStep 4
switch# rename flash:c2900XL-c3h2s-mz-112.8.SA6.bin flash:boot.binEnsure that there are no other image files in Flash memory.
Step 5
System > System Configuration from the menu bar.Step 6
Step 7
Step 8
Step 9
Step 10
switch# dir flash:Directory of flash:/2 -rwx 4484 Mar 05 1993 00:31:09 vlan.dat4 -rwx 110 Mar 01 1993 19:50:50 info92 -rwx 877 Mar 06 1993 18:39:38 placement.txt5 -rwx 1644050 Mar 01 1993 19:36:14 boot.bin
6 drwx 6720 Mar 01 1993 00:18:36 html86 -rwx 110 Mar 01 1993 19:37:00 info.ver116 -rwx 3686 Mar 01 1993 19:55:33 config.text89 -rwx 25 Mar 01 1993 00:26:30 snmpengineid7 -rwx 313 Mar 01 1993 19:34:57 env_vars3612672 bytes total (840704 bytes free)Step 11
switch# show bootConfig file: flash:config.textEnable Break: noManual Boot: noHELPER path-list:NVRAM/Config filebuffer size: 32768
Recovering from an Incomplete VSM Software Upgrade
If you do not follow the procedure described in "Using VSM to Upgrade a Switch," an upgrade can fail due to insufficient space because of multiple software images or other files in Flash memory. When the upgrade fails, the image file is copied to Flash memory, but there is insufficient space for the HTML files, and you lose access to VSM.
In the event of a failure, ensure that the image file in Flash memory has the same name as the contents of the boot variable. You can compare these two names by following the last two steps in the procedure described in the "Using VSM to Upgrade a Switch" section.
If the contents of the boot variable and the image file name are the same, the switch can reset successfully. If they are different, rename the image file, or reset the boot variable by entering the system boot name global configuration command. The boot variable and the image file name should be the same.
To recover from the incomplete download of the HTML files, log in to the switch, and upgrade the software as described in the "Upgrading a Switch by Using the CLI" section.
Upgrading a Switch by Using the CLI
The CLI upgrade procedure consists of these major steps:
1.
2.
3.
Which Files to Use
Table 6 describes the file extensions and what they mean for the upgrade procedure. It is easier to upgrade the switch software by using a combined .tar file that contains the HTML files and the IOS image. The upgrade procedures in these release notes describe how to perform the upgrade by using a combined .tar file, and you must use a combined .tar file to upgrade a switch through the CMS.
Table 7 and Table 8 list the software files for this IOS release.
Downloading the New Software
Follow these steps to download the new software and, if necessary, the TFTP server application.
Step 1
Note
Step 2
If you have a SmartNet support contract, log in to one of the following URLs and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XLIf you do not have a SmartNet contract, download the appropriate files from one of the following URLs:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XLStep 3
After you have downloaded the correct files to your PC or workstation, you can use the CLI to perform a TFTP transfer of the file or files to the switch.
Upgrading Catalyst 3500 Series XL Switches
This procedure is only 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 command.
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 the following 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: 32768Step 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-XW.binStep 7
switch# dir flash: Directory of flash:/2 ---x 1644045 Apr 04 1993 15:17:15 c3500XL-c3h2s-mz-120.5-XW.bin3 -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# config 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-XW.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-XW.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 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 8-MB Catalyst 2900 Series XL Switches
This procedure is for upgrading Catalyst 2900 XL switches with 8 MB of DRAM. You upgrade a switch by extracting the 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 command.
Note
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 command to start a TFTP transfer:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter the following 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 bootStep 6
switch# dir flash:Directory of flash:/2 ---x 1644046 Apr 04 1993 15:22:13 c2900XL-c3h2s-mz-120.5-XU.bin4 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 7
switch# rename flash:current_image flash:new_image Source filename [current_image]? Destination filename [new_image]?For example:
switch# rename flash:c2900XL-h2-mz-112.8.2-SA6.bin flash:c2900XL--c3h2s-mz-120.5-XW.bin Source filename [c2900XL-h2-mz-112.8.2-SA6.bin]? Destination filename [c2900XL-c3h2s-mz-120.5-XW.bin]?Step 8
switch# config 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:c2900XL-c3h2s-mz-120.5-XW.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.
Step 13
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 14
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-XW.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 command.
Step 15
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 16
switch(config)# IP http serverStep 17
switch(config)# endStep 18
switch# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm]Step 19
Your Telnet session ends when the switch resets.
Step 20
Installing the Required Plug-In
A browser Java plug-in is required to access the HTML-based CMS. Download and install the plug-in before you start CMS.
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 the following setting:
In the Proxies tab, verify that Use browser settings is checked and that no proxies are enabled.
Windows 95, Windows 98, and Windows NT 4.0 Users
If you have a SmartNet support contract, log in to one of the following URLs and download the plug-in:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XLIf you do not have a SmartNet contract, download the plug-in from one of the following URLs:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XLIf you start CMS without having installed the required Java plug-in, the switch automatically detects the lack of the plug-in. If you are using a supported Netscape browser, the browser displays a Cisco Connection Online (CCO) page that contains the Java plug-in and instructions to install it. If you are using a supported Internet Explorer browser, it automatically downloads and installs the browser.
Solaris Users
Solaris users need to download the Java plug-in and the JRE 1.2.2_05.
Download the Java plug-in for Solaris from the following URL:
http://www.sun.com/software/solaris/netscape/ipis/
Install the plug-in by following the instructions that are posted on the URL.
Install the JRE 1.2.2_05 from the following URL:
http://www.sun.com/software/solaris/java/download.html
Follow the links in the section titled J2SE: Java[tm] 2 SDK, Standard Edition (1.2.2_05) to download and install the JRE.
New Features in This Release
This section describes the new supported hardware and the new software features for the Catalyst 2900 series XL and Catalyst 3500 series XL switches that are provided in this release.
•
•
Note
New Hardware Features in Release 12.0(5)XW
This release supports the single-port 1000BaseT GBIC (WS-G5482). Switches running earlier software versions do not recognize and automatically enable this GBIC.
Note
New Software Features in Release 12.0(5)XW
This release contains the following new software features:
•
Cross-stack UplinkFast provides a fast spanning-tree transition (fast convergence in less than 2 seconds under normal network conditions) across a stack of switches that use the GigaStack GBICs connected in a shared cascaded configuration (multidrop backbone). During the fast transition, an alternate redundant link on the stack of switches is placed into the forwarding state without causing temporary loops or loss of connectivity to the backbone. With this feature, you can have a redundant and resilient network. For more information, see the "Understanding Cross-Stack UplinkFast" section.
•
The DHCP provides configuration information to Internet hosts and internetworking devices. With DHCP-based autoconfiguration, your switch (DHCP client) can be automatically configured during bootup with IP address information and a configuration file that it receives during DHCP-based autoconfiguration. DHCP replaces BOOTP for autoconfiguration to ensure retrieval of configuration files by unicast TFTP messages. For more information, see the "Understanding DHCP-Based Autoconfiguration" section.
•
–
–
–
–
–
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.
•
•
Caution
•
•
You can view RPS status through the CLI by using the show rps privileged EXEC command.•
•
•
•
•
•
–
or 2.2.–
•
Important Notes
This section describes important information related to Release 12.0(5)XW.
•
•
Caveats
Open Caveats
This section describes possible unexpected activity by Release 12.0(5)XW.
•
There is no workaround. (CSCds40442)
•
This is an intermittent problem, and there is no workaround. (CSCds68177)
•
There is no workaround. (CSCds87929)
•
There is no workaround. (CSCds86420)
•
The workaround is to not use the same host name for multiple switches in the cluster. (CSCdr86448)
•
The workaround, if you need to reconnect the switches through their GBIC ports, is to wait until the green LED turns off, and then reconnect the switches. (CSCds89780)
•
If this occurs, the workaround is to remove and reinsert one of the GBICs. (CSCds84479)
•
The workaround is to use the graph types Line (default) or Bar to view the data. (CSCds54709)
•
There is no workaround. (CSCds82026)
•
There is no workaround. This will be fixed in a future release. (CSCds82043)
•
•
The workaround is to not disable Java plug-ins on the Java Plug-In Control Panel. (CSCdp67822)
•
The workaround is to right-click again on the device until the pop-up menu displays correctly. (CSCdp61365)
•
To avoid a possible conflict, either set the system time for the entire cluster on the command switch, or configure NTP on the command switch to use an NTP server to provide time to the cluster. Do not use both methods at the same time. (CSCdp82224)
•
•
The workaround is to not use flow control on the console port. (CSCdm24487)
•
The workaround is to not change the management VLAN to a VLAN where a member is configured as part of a standby group. (CSCdp70389)
•
•
•
•
The workaround is to not monitor private VLAN edge ports. (CSCdp84267)
•
•
There is no workaround. (CSCdp87748)
•
The workaround is to always use the command-switch IP address to access CMS. If a standby group is configured for a cluster, always use the virtual IP address to access CMS. (CSCdp75220)
•
The workaround is to not include commas in host names or DNS server names in CMS. (CSCdp85928)
•
The workaround is to collapse the list into a single icon, which returns the list to the top of the window. (CSCdp62807)
•
The workaround is to right-click another part of the chassis image to display the device pop-up menu. (CSCdp89945)
•
Resolved Caveats
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Documentation Updates
This section provides updates to the product documentation. These changes will be included in the next version of the documentation.
•
•
•
•
•
•
•
Documentation Notes
•
•
•
Setting Up the Catalyst 2900 XL Initial Configuration
The procedure for setting up the initial configuration on the Catalyst 2900 XL switches, as described in the Catalyst 2900 Series XL Installation Guide, has been updated. Follow these steps to create an initial configuration for the switch:
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_addressStep 6
Note
Enter a host name: host_nameStep 7
Note
Enter enable secret: secret_passwordStep 8
Would you like to configure a Telnet password? [yes] y
Note
Step 9
Enter Telnet password: telnet_passwordStep 10
Note
Would you like to enable as a cluster command switch? yStep 11
Enter cluster name: cls_name
Note
Step 12
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 13
•
•
Use this configuration? [yes/no]: yAfter you complete the setup program, the switch can run the created default configuration. If you want to change this configuration or want to perform other management tasks, use one of these tools:
•
•
Configuring Voice Ports to Carry Voice and Data Traffic on Different VLANs
The Cisco 7960 IP Phone contains an integrated 3-port 10/100 switch that can connect to a PC or other device. You can configure a switch port to instruct the phone to forward voice and data traffic on different virtual LANs (VLANs).
In the following configuration, data traffic is carried by VLAN 1, and voice traffic is carried by VLAN 2. In this configuration, all IP phones and other voice-related devices must be connected to switch ports that belong to VLAN 2.
Beginning in privileged EXEC mode, follow these steps to configure a port to receive voice and data from an IP phone in different VLANs:
Understanding Cross-Stack UplinkFast
Cross-stack UplinkFast (CSUF) provides a fast spanning-tree transition (fast convergence in less than 2 seconds under normal network conditions) across a stack of switches that use the GigaStack GBICs connected in a shared cascaded configuration (multidrop backbone). During the fast transition, an alternate redundant link on the stack of switches is placed into the forwarding state without causing temporary spanning-tree loops or loss of connectivity to the backbone. With this feature, you can have a redundant and resilient network in some configurations.
CSUF might not provide a fast transition all the time; in these cases, the normal STP transition occurs, which completes in 30 to 40 seconds. For more information, see the "Events that Cause Fast Convergence" section.
How CSUF Works
CSUF ensures that one link in the stack is elected as the path to the root. As shown in Figure 1, Switches A, B, and C are cascaded through the Gigastack GBIC to form a multidrop backbone, which communicates control and data traffic across the switches at the access layer. The switches in the stack use their stack ports to communicate with each other and to connect to the stack backbone; stack ports are always in the STP forwarding state. The stack root port on Switch A provides the path to the root of the spanning tree; the alternate stack root ports on Switches B and C can provide an alternate path to the spanning-tree root if the current stack root switch fails or its link to the spanning-tree root fails.
Link A, the root link, is in the STP forwarding state; Links B and C are alternate redundant links that are in the STP blocking state. If Switch A fails, if its stack root port fails, or if Link A fails, CSUF selects either the Switch B or Switch C alternate stack root port and puts it into the forwarding state in less than 1 second.
Figure 1 Cross-Stack UplinkFast Topology
CSUF implements the Stack Membership Discovery Protocol and the Fast Uplink Transition Protocol. Using the Stack Membership Discovery Protocol, all stack switches build a neighbor list of stack members through the receipt of discovery hello packets. When certain link loss or STP events occur (described in "Events that Cause Fast Convergence" section), the Fast Uplink Transition Protocol uses the neighbor list to send fast-transition requests on the stack port to stack members.
The switch sending the fast-transition request needs to do a fast transition to the forwarding state of a port that it has chosen as the root port, and it must obtain an acknowledgement from each stack switch before performing the fast transition.
Each switch in the stack determines if the sending switch is a better choice than itself to be the stack root of this STP instance by comparing STP root, cost, and bridge ID. If the sending switch is the best choice as the stack root, the switch in the stack returns an acknowledgement; otherwise, it does not respond to the sending switch (drops the packet) and prevents the sending switch from receiving acknowledgements from all stack switches.
When acknowledgements are received from all stack switches, the Fast Uplink Transition Protocol on the sending switch immediately transitions its alternate stack root port to the forwarding state. If acknowledgements from all stack switches are not obtained by the sending switch, the normal STP transitions (blocking, listening, learning, forwarding) take place, and the spanning-tree topology converges at its normal rate (2 * forward-delay time + max-age time).
The Fast Uplink Transition Protocol is implemented on a per-VLAN basis and affects only one STP instance at a time.
Events that Cause Fast Convergence
Depending on the network event or failure, fast convergence provided by CSUF might or might not occur.
Fast convergence (within 2 seconds under normal network conditions) occurs under these circumstances:
•
If two switches in the stack have alternate paths to the root, only one of the switches performs the fast transition.
•
•
•
Note
Normal STP convergence (30 to 40 seconds) occurs under these conditions:
•
•
•
•
•
Note
Limitations
The following limitations apply to CSUF:
•
•
•
•
Connecting the Stack Ports
A fast transition occurs across the stack of switches if the multidrop backbone connections are a continuous link from one GigaStack GBIC to another as shown in Figure 2. In addition, follow these guidelines:
•
•
•
•
Figure 2 GigaStack GBIC Connections and STP Convergence
Configuring Cross-Stack UplinkFast
Before enabling CSUF, make sure your stack switches are properly connected. For more information, see the "Connecting the Stack Ports" section.
Beginning in privileged EXEC mode, follow these steps to enable CSUF:
To disable CSUF on an interface, use the no spanning-tree stack-port interface configuration command. To disable UplinkFast on the switch, use the no spanning-tree uplinkfast global configuration command.
Understanding DHCP-Based Autoconfiguration
The DHCP provides configuration information to internet hosts and internetworking devices. This protocol consists of two components: one for delivering configuration parameters from a DHCP server to a device and a mechanism for allocating network addresses to devices. DHCP is built on a client-server model, where designated DHCP servers allocate network addresses and deliver configuration parameters to dynamically configured devices.
With DHCP-based autoconfiguration, your switch (DHCP client) can be automatically configured at startup with IP address information and a configuration file that it receives during DHCP-based autoconfiguration.
With DHCP-based autoconfiguration, no DHCP client-side configuration is required on your switch. However, you need to configure the DHCP server for various lease options. You might also need to configure a TFTP server, a Domain Name System (DNS) server, and possibly a relay device if the servers are on a different LAN than your switch. A relay device forwards broadcast traffic between two directly connected LANs. A router does not forward broadcast packets, but it forwards packets based on the destination IP address in the received packet. DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch.
DHCP Client Request Process
When you boot your switch, the DHCP client can be invoked and automatically request configuration information from a DHCP server under the following conditions:
•
•
•
Figure 3 shows the sequence of messages that are exchanged between the DHCP client and the DHCP server.
Figure 3 DHCP Request for IP Information from a DHCP Server
The client, Switch A, broadcasts a DHCPDISCOVER message to locate a DHCP server. The DHCP server offers configuration parameters (such as an IP address, subnet mask, gateway IP address, DNS IP address, a lease for the IP address, and so forth) to the client in a DHCPOFFER unicast message.
In a DHCPREQUEST broadcast message, the client returns a formal request for the offered configuration information to the DHCP server. The formal request is broadcast so that all other DHCP servers that received the DHCPDISCOVER broadcast message from the client can reclaim the IP addresses that they offered to the client.
The DHCP server confirms that the IP address has been allocated to the client by returning a DHCPACK unicast message to the client. With this message, the client and server are bound, and the client uses configuration information received from the server. The amount of information the switch receives depends on how you configure the DHCP server. For more information, see the "Configuring the DHCP Server" section.
If the configuration parameters sent to the client in the DHCPOFFER unicast message by the DHCP server are invalid (a configuration error exists), the client returns a DHCPDECLINE broadcast message to the DHCP server.
The DHCP server sends the client a DHCPNAK denial broadcast message, which means the offered configuration parameters have not been assigned, an error has occurred during the negotiation of the parameters, or the client has been slow in responding to the DHCPOFFER message (the DHCP server assigned the parameters to another client) of the DHCP server.
A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any one of the offers; however, the client usually accepts the first offer it receives. The offer from the DHCP server is not a guarantee that the IP address will be allocated to the client; however, the server usually reserves the address until the client has had a chance to formally request the address. If the switch accepts replies from a BOOTP server and configures itself, the switch will broadcast, instead of unicast, TFTP requests to obtain the switch configuration file.
Configuring the DHCP Server
You should configure the DHCP servers with reserved leases that are bound to each switch by the switch hardware address. If the DHCP server does not support reserved leases, the switch can obtain different IP addresses and configuration files at different boot instances. You should configure the DHCP server with the following lease options:
•
•
•
•
•
•
•
If you do not configure the DHCP server with the lease options described earlier, then it replies to client requests with only those parameters that have available values. If the IP address and subnet mask are not in the reply, the switch is not configured. If the DNS server IP address, router IP address, or TFTP server name are not found, the switch might broadcast TFTP requests. Unavailability of other lease options does not affect autoconfiguration.
Note
The DHCP server can be on the same or a different LAN as the switch. If it is on a different LAN, the switch must be able to access it through a relay device. The DHCP server can be running on a UNIX or Linux operating system; however, the Windows NT operating system is not supported in this release.
For more information, see the "Configuring the Relay Device" section. You must also set up the TFTP server with the switch configuration files; for more information, see the next section.
Configuring the TFTP Server
The TFTP server must contain one or more configuration files in its base directory. The files can include the following:
•
•
•
You must specify the TFTP server name in the DHCP server lease database. You must also specify the TFTP server name-to-IP-address mapping in the DNS server database.
The TFTP server can be on the same or a different LAN as the switch. If it is on a different LAN, the switch must be able to access it through a relay device or a router. For more information, see the "Configuring the Relay Device" section.
If the configuration filename is provided in the DHCP server reply, the configuration files for a switch can be spread over multiple TFTP servers. However, if the configuration filename is not provided, then the configuration files must reside on a single TFTP server.
Configuring the DNS
The switch uses the DNS server to resolve the TFTP server name to a TFTP server IP address. You must configure the TFTP server name-to-IP address map on the DNS server. The TFTP server contains the configuration files for the switch.
You must configure the IP addresses of the DNS servers in the lease database of the DHCP server from where the DHCP replies will retrieve them. You can enter up to two DNS server IP addresses in the lease database.
The DNS server can be on the same or a different LAN as the switch. If it is on a different LAN, the switch must be able to access it through a relay device or router. For more information, see the "Configuring the Relay Device" section.
Configuring the Relay Device
You need to use a relay device if the DHCP, DNS, or TFTP servers are on a different LAN than the switch. You must configure this relay device to forward received broadcast packets on an interface to the destination host. This configuration ensures that broadcasts from the DHCP client can reach the DHCP, DNS, and TFTP servers and that broadcasts from the servers can reach the DHCP client.
If the relay device is a Cisco router, you enable IP routing (ip routing global configuration command) and configure it with helper addresses by using the ip helper-address interface configuration command.
For example, in Figure 4, you configure the router interfaces as follows:
On interface 10.0.0.2:
router(config-if)# ip helper-address 20.0.0.2router(config-if)# ip helper-address 20.0.0.3router(config-if)# ip helper-address 20.0.0.4On interface 20.0.0.1
router(config-if)# ip helper-address 10.0.0.1Figure 4 Relay Device Used in Autoconfiguration
Obtaining Configuration Files
Depending on the availability of the IP address and the configuration filename in the DHCP reserved lease, the switch obtains its configuration information in the following ways:
•
The switch receives its IP address, subnet mask, and configuration filename from the DHCP server. It also receives a DNS server IP address and a TFTP server name. The switch sends a DNS request to the DNS server, specifying the TFTP server name, to obtain the TFTP server address. Then the switch sends a unicast message to the TFTP server to retrieve the named configuration file from the base directory of the server, and upon receipt, completes its boot-up process.
•
The switch follows the same configuration process described above.
•
The switch receives its IP address and subnet mask from the DHCP server. It also receives a DNS server IP address and a TFTP server name. The switch sends a DNS request to the DNS server, specifying the TFTP server name, to obtain the TFTP server address.
The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.cfg default configuration file. (If the network-confg file cannot be read, the switch reads the cisconet.cfg file.)
The default configuration file contains the host names-to-IP-address mapping for the switch. The switch fills its host table with the information in the file and obtains its host name. If the host name is not found in the file, the switch uses the host name in the DHCP reply. If the host name is not specified in the DHCP reply, the switch uses the default "Switch" as its host name.
After obtaining its host name from the default configuration file or the DHCP reply, the switch reads the configuration file that has the same name as its host name (hostname-confg or hostname.cfg, depending on whether network-confg or cisconet.cfg was read earlier) from the TFTP server. If the cisconet.cfg file is read, the filename of the host is truncated to eight characters.
If the switch cannot read the network-confg, cisconet.cfg, or the host-name file, it reads the router-confg file. If the switch cannot read the router-confg file, it reads the ciscortr.cfg file.
Note
Example Configuration
Figure 5 shows a sample network for retrieving IP information using DHCP-based autoconfiguration.
Figure 5 DHCP-Based Autoconfiguration Network Example
Table 9 shows the configuration of the reserved leases on the DHCP server.
DNS Server Configuration
The DNS server maps the TFTP server name maritsu to IP address 10.0.0.3.
TFTP Server Configuration (on UNIX)
The TFTP server base directory is set to /tftpserver/work/. This directory contains the network-confg file used in the two-file read method. This file contains the host name to be assigned to the switch based on its IP address. The base directory also contains a configuration file for each switch (switch1-confg, switch2-confg, and so forth) as shown in the following display:
prompt> cd /tftpserver/work/prompt> lsnetwork-confgswitch1-confgswitch2-confgswitch3-confgswitch4-confgprompt> cat network-confgip host switch1 10.0.0.21ip host switch2 10.0.0.22ip host switch3 10.0.0.23ip host switch4 10.0.0.24DHCP Client Configuration
No configuration file is present on Switch 1 through Switch 4.
Configuration Explanation
In Figure 5, Switch 1 reads its configuration file as follows:
•
•
•
•
•
Switches 2 through 4 retrieve their configuration files and IP addresses in the same way.
New and Changed Commands
This section describes the new and changed commands for this release and includes the following sections:
•
show interface
Use the show interface privileged EXEC command to display the administrative and operational status of a switching (nonrouting) port.
show interface [interface-id | vlan number] [flow-control | pruning | status | switchport [allowed-vlan | prune-elig | native-vlan]]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show interface gi0/1 flow-control command.
Switch# show interface gi0/1 flow-controlAny,Input onlyThe display shows two values separated by a comma. The first value is the value you configured by using the flowcontrol interface configuration command or through the Cluster Management Suite (or the default value if you did not configure it). The first value displayed can be one of the following settings:
•
•
•
•
The second value in the display represents the flow control value that is autonegotiated with the link partner and can be one of the following settings:
•
•
•
•
Note
The following is sample output from the show interface fa0/2 switchport command. Table 10 describes each field in the display.
Switch# show interface fa0/2 switchportName: fa0/2Switchport: EnabledAdministrative Mode: TrunkOperational Mode: TrunkAdministrative Trunking Encapsulation: ISLOperational Trunking Encapsulation: ISLNegotiation of Trunking: DisabledAccess Mode VLAN: 0 (inactive)Trunking Native Mode VLAN: 1 (default)Trunking VLANs Enabled: 1-30, 50, 100-1005Trunking VLANs Active: 1-4Pruning VLANs Enabled: 2-1001Priority for untagged frames: 0Voice VLAN: noneAppliance trust: none
The following is sample output from the show interface fa0/9 pruning command when pruning is enabled in the VTP domain:
Switch# show interface fa0/9 pruning Port Vlans pruned for lack of request by neighborFa0/9 3,4Port Vlans traffic requested of neighborFa0/9 1-3The following is sample output from the show interface status command:
Switch# show interface statusPort Name Status Vlan Duplex Speed Type------- ------------------ ------------ -------- ------ ------- ----Fa0/1 connected trunk A-Full A-100 100BaseTX/FXFa0/2 notconnect 1 Auto Auto 100BaseTX/FXFa0/3 notconnect 1 Auto Auto 100BaseTX/FXFa0/4 notconnect 1 Auto Auto 100BaseTX/FXFa0/5 notconnect 1 Auto Auto 100BaseTX/FXFa0/6 notconnect 1 Auto Auto 100BaseTX/FXFa0/7 notconnect 1 Auto Auto 100BaseTX/FXFa0/8 notconnect 1 Auto Auto 100BaseTX/FXFa0/9 notconnect 1 Auto Auto 100BaseTX/FX<output truncated>Related Commands
show spanning-tree
Use the show spanning-tree privileged EXEC command to display spanning-tree information for the specified spanning-tree instances.
show spanning-tree [brief] | [summary] | [vlan stp-list] | [interface interface-list]
Syntax Description
Command Modes
Privileged EXEC
Command History
11.2(8)SA3
This command was first introduced.
12.0(5)XW
The brief and summary keywords were added.
Usage Guidelines
If the variable stp-list is omitted, the command applies to the Spanning Tree Protocol (STP) instance associated with VLAN 1.
Examples
The following is sample output from the show spanning-tree command for VLAN 1:
Switch# show spanning-tree vlan 1Spanning tree 1 is executing the IEEE compatible Spanning Tree protocolBridge Identifier has priority 49152, address 00b0.6476.08c0Configured hello time 2, max age 20, forward delay 15Current root has priority 32768, address 0001.42cd.a200Root port is 31, cost of root path is 42Topology change flag not set, detected flag not set, changes 1Times: hold 1, topology change 35, notification 2hello 2, max age 20, forward delay 15Timers: hello 0, topology change 0, notification 0Fast uplink switchover is enabledStack port is GigabitEthernet0/1Interface Fa0/1 (port 13) in Spanning tree 1 is downPort path cost 3100, Port priority 128Designated root has priority 32768, address 0001.42cd.a200Designated bridge has priority 49152, address 00b0.6476.08c0Designated port is 13, path cost 42Timers: message age 0, forward delay 0, hold 0BPDU: sent 0, received 0<output truncated>The following is sample output from the show spanning-tree interface command for port 3:
Switch# show spanning-tree interface fa0/3Interface Fa0/3 (port 3) in Spanning tree 1 is downPort path cost 100, Port priority 128Designated root has priority 6000, address 0090.2bba.7a40Designated bridge has priority 32768, address 00e0.1e9f.4abfDesignated port is 3, path cost 410Timers: message age 0, forward delay 0, hold 0BPDU: sent 0, received 0The following is sample output from the show spanning-tree summary command:
Switch# show spanning-tree summaryUplinkFast is enabledStack port is GigabitEthernet0/1Name Blocking Listening Learning Forwarding STP Active-------------------- -------- --------- -------- ---------- ----------VLAN1 13 0 0 1 14VLAN2 1 0 0 1 2VLAN3 1 0 0 1 2<output truncated>Related Commands
spanning-tree stack-port
Use the spanning-tree stack-port interface configuration command to enable cross-stack UplinkFast (CSUF) on an interface and to accelerate the choice of a new root port when a link or switch fails or when Spanning Tree Protocol (STP) reconfigures itself. Use the no form of this command to return to the default setting.
spanning-tree stack-port
no spanning-tree stack-port
Syntax Description
This command has no arguments or keywords.
Defaults
CSUF is disabled on all interfaces.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is effective only if you enable the UplinkFast feature by using the spanning-tree uplinkfast global configuration command.
Use this command only on access switches.
You can enable CSUF only on one stack-port GBIC interface. The stack port connects to the GigaStack GBIC multidrop backbone. If you try to enable CSUF on a Fast Ethernet or a copper-based Gigabit Ethernet port, you receive an error message.
If CSUF is already enabled on an interface and you try to enable it on another interface, you receive an error message. You must disable CSUF on the first interface before enabling it on a new interface.
Examples
The following command shows how to enable CSUF on the GBIC interface gi0/1:
Switch(config)# interface gi0/1Switch(config-if)# spanning-tree stack-portYou can verify the previous command by entering the show spanning-tree command in privileged EXEC mode.
Related Commands
show spanning-tree
Displays spanning-tree information for the specified spanning-tree instances.
Syslog Error Messages
The following messages can appear in the command-line interface (CLI).
LINK_FLAP, RTD, LOG_ALERT, 0, "%s link down/up %d times per minExplanation An excessive number of link down-up events has occurred on this interface. This might be the result of reconfiguring the port, or it might indicate a faulty device at the other end of the connection.
Action If someone is reconfiguring the interface or device at the other side of the interface, ignore this message. However, if no one is manipulating the interface or the other device, it is likely that the Ethernet transceiver at one end of the link is faulty, and you should replace it.
ADDR_FLAP, RTD, LOG_ALERT, 0, "%s relearning %d addrs per minExplanation Normally, MAC addresses are learned once on a port. Occasionally, when a switched network reconfigures, due to either manual or STP reconfiguration, addresses learned on one port are relearned on a different port. However, if there is a port anywhere in the switched domain that is looped back to itself, addresses jump back and forth between the real port and the port that is in the path to the looped back port.
Action Determine the real path (port) to the MAC address. Use the debug ethernet-controller addr privileged EXEC command to see the alternate path-port on which the address is being learned. Go to the switch attached to that port. Note that the show cdp neighbors privileged EXEC command is useful in determining the next switch. Repeat this procedure until you find the port that is receiving what it is transmitting, and remove that port from the network.
MAC_TBL_SIZE, MODULES, LOG_ERR, 0,Explanation Dynamic module insertion supports less MAC addresses.
Action Reboot system to use the module.
SECURITYREJECT, PORT_SECURITY, LOG_CRIT, 0,Explanation A packet with unexpected source address is received on a secure port.
Action Remove the station with the unexpected MAC address from the secure port, or add the MAC address to the secure address table of the secure port.
SHUTDOWN, STORM_CONTROL, LOG_CRIT, 0,Explanation Excessive traffic has been detected on a port that has been configured to be shut down if a storm event is detected.
Action When the source of the packet storm has been fixed, re-enable the port by using port-configuration commands.
BLADE_EXTRACT, CHASSIS, LOG_NOTICE, 0,Explanation The hot-swap switch has been depressed.
Action Extract the module.
LOOP_DETECTED, GIGASTACK, LOG_INFO, 0, Gigastack GBIC in %s is selected as Master Loop Breaker.Explanation Loop has been detected in the Gigastack, and this Gigastack (Gigabit Interface Converter) GBIC is selected as the Master Loop Breaker. Link 2 of this Gigastack GBIC is disabled to break the loop.
Action No action is required.
LOOP_BROKEN, GIGASTACK, LOG_INFO, 0, Link loss is detected in the Gigastack loopExplanation Loop formed by Gigastack modules is broken because of link loss. Link 2 of the Master Loop Breaker is re-enabled to replace the broken line.
Action No action is required.
NO_LOOP_DETECT, GIGASTACK, LOG_ALERT, 0, The link neighbor of link %d of GigastackExplanation No acknowledgement for Gigastack loop detection request is received from one of the links on a Gigastack GBIC. Either the neighboring switch does not support the Gigastack Loop breaking algorithm, or the link between the two Gigastack GBICs is broken. Under this condition, a Gigastack loop topology is not automatically detected, and the connectivity between switches in the stack could be lost.
Action If loop topology is used in the Gigastack, make sure the latest software is running on all switches in the stack. Check the Gigastack GBICs involved to make sure they are functioning.
ADD, CMP, LOG_NOTICE, 0, The Device is added to the cluster (Cluster Name:%s, CMDR IP Address %i)Explanation The device is added to the cluster.
Action No action is required.
REMOVE, CMP, LOG_NOTICE, 0, The Device is removed from the cluster (Cluster Name:%s)Explanation The device is removed from the cluster.
Action No action is required.
MEMBER_CONFIG_UPDATE, CMP, LOG_NOTICE, 0, Received member configuration from member %dExplanation Received member configuration.
Action No action is required.
FAN_FAULT, ENVIRONMENT, LOG_CRIT, 0,Explanation An internal fan fault is detected. This message is available only on the Catalyst 3524-PWR XL switch.
Action Either check the switch itself, or use the show env privileged EXEC command to check if a fan on the switch has failed. The Catalyst 3524-PWR XL switch can operate normally with one failed fan. Replace the switch at your convenience.
OVER_TEMP, ENVIRONMENT, LOG_CRIT, 0,Explanation An overtemperature condition is detected. This message is available only on the Catalyst 3524-PWR XL switch.
Action Use the show env command to check if an overtemperature condition exists. If it does:
•
•
If a multiple-fan failure is causing the switch to overheat, replace the switch.
LINK-4, LOG_WARNING, 0,%s is experiencing errors.Explanation Excessive errors have occurred on this interface.
Action Check for duplex mismatches between both ends of the link.
Note
Related Documentation
The product documentation for the 3500 and 2900 XL switches and modules is as follows:
Quick Start Guide: Catalyst 2900 Series XL Switches
Quick Start Guide: Catalyst 3500 Series XL Switches
Catalyst 2900 Series XL Installation Guide
Catalyst 3500 Series XL Hardware Installation Guide
Cisco IOS Desktop Switching Software Configuration Guide for Cisco IOS Software Release 12.0(5)XU
Cisco IOS Desktop Command Reference (online only)
Using the Catalyst 2924M XL DC Ethernet Switch
Catalyst 2900 Series XL Modules Installation Guide
Catalyst 2900 Series XL Gigabit Ethernet Module Installation Guide
Catalyst 2900 Series XL ATM Modules Installation and Configuration Guide
Release Notes for the Catalyst 2900 Series XL ATM Modules
Catalyst GigaStack Gigabit Interface Converter Hardware Installation Guide
Release Notes for Catalyst GigaStack Gigabit Interface Converter.
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following sites:
•
•
•
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships 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 as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/public/ordsum.html
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
•
•
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
Contacting TAC by Telephone
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
•
•
This document is to be used in conjunction with the document listed in the "Related Documentation" section.
Access Registrar, AccessPath, Are You Ready, ATM Director, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, Cisco Powered Network logo, Cisco Systems Networking Academy, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, iQ Logo, iQ Readiness Scorecard, Kernel Proxy, MGX, Natural Network Viewer, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, WebViewer, Workgroup Director, and Workgroup Stack are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert Logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Collision Free, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or 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. (0010R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Guest
