Table Of Contents
Browser and Java Plug-In Requirements
Cluster Requirements and Guidelines
Catalyst 2900 XL and Catalyst 3500 XL Switches
Catalyst 1900 and Catalyst 2820 Switches
Minimum Cisco IOS Release for Major Features
New Software Features in this Release
Open Cluster Configuration Caveats
Resolved IOS Caveats in Release 12.0(5)WC3b
Resolved CMS Caveat in Release 12.0(5)WC3b
Resolved IOS Caveats in Release 12.0(5)WC3
Resolved CMS Caveats in Release 12.0(5)WC3
Resolved IOS Caveats in Release 12.0(5)WC2
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
Downloading the New Software and TFTP Server Application to Your Management Station
Copying the Current Startup Configuration from the Switch to a PC or Server
Using CMS to Upgrade a Specific Switch
Recovering from an Incomplete CMS Software Upgrade
Using CMS to Upgrade One or More Switches
Using the CLI to Upgrade an 8-MB Catalyst 2900 XL Switch
Using the CLI to Upgrade a Catalyst 3500 XL Switch
Using the CLI to Upgrade Member Switches
Upgrading Catalyst 2900 XL or Catalyst 3500 XL Member Switches
Upgrading Catalyst 1900 or Catalyst 2820 Member Switches
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Release Notes for the Catalyst 2900 Series XL and Catalyst 3500 Series XL Switches,
Cisco IOS Release 12.0(5)WC3b
March 2002
Cisco IOS Release 12.0(5)WC3b runs on the Catalyst 2900 series XL and Catalyst 3500 series XL switches with 8-MB CPU DRAM.
Note
This release is not for the Catalyst 2900 LRE XL switches. Do not install this release on the Long-Reach Ethernet (LRE) switches. For information about these switches, refer to Cisco IOS Release 12.0(5)WC2 and Cisco IOS Release 12.0(5)WC2b.
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 these sites:
•
(for registered Cisco.com users with a login password)•
(for nonregistered Cisco.com users)This release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Contents
This document has the following sections:
•
•
•
•
•
•
•
•
•
•
•
•
Hardware Requirements
Note
This release supports the 8-MB Catalyst 2900 XL switches (see Table 1) and Catalyst 3500 XL switches (see Table 2).
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 3 lists the recommended platforms for using CMS.
Table 3 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 4 lists the browsers supported by CMS.
CMS requires the Java plug-ins described in the "Installing the Required Plug-In" section.
Table 4 Browser Requirements
Windows 95
4.61, 4.7
4.01a or 5.0
Windows 98
4.61, 4.7
4.01a or 5.0
Windows NT 4.0
4.61, 4.7
4.01a or 5.0
Windows 2000
4.61, 4.7
4.01a or 5.0
Solaris 2.5.1 or higher
4.61, 4.7
-
1 Netscape Communicator version 4.60 and 6.0 are not supported.
2 Microsoft Internet Explorer is not supported on Solaris 2.5.1 or higher.
Note
Note
To access CMS, follow the procedures in the "Initial Switch Configuration" section.
Cluster Requirements and Guidelines
This section describes the hardware and software requirements for clustering Catalyst desktop switches.
Catalyst 2900 XL and Catalyst 3500 XL Switches
Some versions of IOS software do not support clustering, and other versions do not support some of the features in this release. To ensure that all cluster switches are using the same software level, we recommend that you upgrade all cluster switches to the software release that supports the features that you want.
If you have a cluster with switches that are running different versions of IOS software, changes on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)XU or later.
Table 5 describes the Catalyst 2900 XL and Catalyst 3500 XL switches supported by this release and shows which switches can be command switches. All switches can function as standalone devices.
All Catalyst 2900 XL and Catalyst 3500 XL switches running Release 12.0(5.3)WC(1) and later are cluster-capable. All Catalyst 2900 XL modules are supported in cluster configurations.
We recommend that either the command switch has the latest software version installed if there switches in the cluster with older software versions or that all switches in the same platform be upgraded to the latest software version.
Note
Table 5 Catalyst 2900 XL and Catalyst 3500 XL Switches as Cluster Members
Catalyst 2900 XL (4 MB of DRAM)1
No
No
Yes
Catalyst 2900 XL (8 MB of DRAM)
Yes
Yes
Yes
Catalyst 3500 XL
Yes
Yes
Yes
1 These switches can act as cluster members if they are running Release 11.2(8.x)SA6 original edition software. They can interoperate with this software release, but they cannot be upgraded to it.
Catalyst 3550 Switches
Catalyst 3550 switches running Release 12.0(4)EA1 or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 3550 switches.
Catalyst 2950 Switches
Catalyst 2950 switches running Release 12.0(5)WC(1) or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 2950 switches.
Catalyst 1900 and Catalyst 2820 Switches
Table 6 lists the Catalyst 1900 and Catalyst 2820 switches and the minimum software release that they require to be cluster members. All Catalyst 2820 modules are supported in cluster configurations. For more information, refer to the documentation for the Catalyst 1900 and Catalyst 2820 switches.
Table 6 Catalyst 1900 and Catalyst 2820 Switches as Cluster Members
Catalyst 1900
Yes
Yes
No
Catalyst 2820
Yes
Yes
No
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 and Catalyst 3500 XL Features and the Minimum Cisco IOS Release Required
Enhanced web-based switch management (CMS)
12.0(5)WC3
MAC Address Notification
Release 12.0(5)WC3
Internet Group Management Protocol (IGMP) Filtering
Release 12.0(5)WC3
Extended cluster member compatibility with the Catalyst 2950 and Catalyst 3550 switches
Release 12.0(5)WC(1)
Multicast VLAN Registration (MVR)
Release 12.0(5)WC(1)
Cross-stack UplinkFast
Release 12.0(5)XW
Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration
Release 12.0(5)XW
Support for the single-port 1000BASE-T Gigabit Interface Converter (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
WS-X2932-XL Catalyst 2900 XL 1-port 1000BASE-T module
Release 12.0(5)XU
Hot Standby Router Protocol (HSRP) for clustering
Release 12.0(5)XU
Extended discovery of cluster candidates up to 7 hops from the command switch
Release 12.0(5)XU
Support for up to 16 switches in a cluster
Release 12.0(5)XU
VLAN Trunking Protocol (VTP) pruning
Release 12.0(5)XU
Change management Virtual LAN (VLAN) for a cluster
Release 12.0(5)XU
Private VLAN edge support
Release 12.0(5)XU
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
WS-C3548-XL switch with 48 10/100 ports
Release 12.0(5)XP
WS-X2931-XL Catalyst GigaStack GBIC
Release 12.0(5)XP
Catalyst 3500 series XL switches (except WS-C3548-XL)
Release 11.2(8)SA6
Cluster management
Release 11.2(8)SA6
Terminal Access Control Access System Plus (TACACS+)
Release 11.2(8)SA6 (Enterprise Edition Software)
Network Time Protocol (NTP)
Release 11.2(8)SA6
Spanning Tree Protocol (STP) UplinkFast
Release 11.2(8)SA6
(Enterprise Edition Software)250 VLANs (some models: see the "Limitations and Restrictions" section)
Release 11.2(8)SA6
Catalyst 2900 series XL 1000BASE-X modules
Release 11.2(8)SA5
Catalyst 2900 series XL asynchronous transmission mode (ATM) modules
Release 11.2(8)SA5
IEEE 802.1Q trunking
Release 11.2(8)SA5
(Enterprise Edition Software)Inter-Switch Link (ISL) trunking
Release 11.2(8)SA4
(Enterprise Edition Software)VLAN Membership Policy Server (VMPS)
Release 11.2(8)SA4 (Enterprise Edition Software)
8192 media access control (MAC) addresses on modular switches
Release 11.2(8)SA4
Switch Network View stack management
Release 11.2(8)SA3
Web-based switch management
Release 11.2(8)SA
Fast EtherChannel port groups
Release 11.2(8)SA
New Software Features in this Release
This section describes the new software features in this release.
IGMP Filtering
IGMP filtering works with the MVR feature so that you can configure profiles of IP multicast groups. IGMP filters are associated with each physical switch port. These filters are applied to all VLANs associated with the physical port.
MAC Address Notification
You can use MAC address notification to track users coming to and going from your network. Whenever a new MAC address is learned or an old MAC address is removed from the switch, an SNMP notification (trap) is generated. If you have many users coming into and going from the network, you can set a trap interval time so that traps can be bundled and sent at regular intervals.
The MAC notification history table stores the MAC address activity for each hardware port for which the trap is enabled. MAC address notifications are generated for dynamic and secure MAC addresses. Events are not generated for self addresses, multicast addresses, or other static addresses.
CMS Enhancements
The CMS software has several enhancements:
•
CMS now provides two levels of access to the configuration options: read-write and read-only. Read-write access requires privilege level 15. Read-only access requires privilege level from 1 to 14. Privilege level 0 denies access to CMS.
•
CMS now provides two modes that control how the VLAN and voice VLAN configuration options are presented. Guide mode takes you step-by-step through these options. Expert mode displays the entire configuration window and lets you decide how to complete a task.
•
CMS provides a wizard to help you configure a port to forward voice traffic with an 802.1P priority and configure the port as an 802.1Q trunk and as a member of the voice VLAN.
•
There are several changes to the CMS menus:
–
–
–
–
•
As before, CMS provides a Front Panel view of a switch cluster and a Topology view of a switch cluster and the devices attached to it. You can now display both views at the same time, display either view, or display neither view. You do not need to display a view to use the menu bar. For configuring and monitoring a standalone switch, CMS continues to provide Device Manager, previously referred to as Switch Manager.
•
You can press the left mouse button and drag your mouse across the ports that you want to select. You can highlight the ports and find out their VLAN membership modes. The cluster tree can display icons for Layer 2, Layer 3, and LRE standby-command switches.
•
You can press the left mouse button and drag your mouse across the devices and links that you want to select. You have more options for controlling the type of information displayed in the Topology view. When you drag your mouse over a yellow or red device icon, a tool tip displays a status message. This view displays device icons for connected Cisco LRE customer premises equipment (CPE) devices, Cisco access points, Cisco IP phones, Cisco Discovery Protocol (CDP)-capable hubs, and routers. This view displays link icons for routed and LRE links.
•
CMS provides change notification by adding a green border around a field or table cell that has an unsaved change. CMS also provides error checking by adding a red border around a field where you entered invalid data. An error message also displays in the window status bar.
When you drag your mouse over a table heading, a tool tip displays the complete heading. On some table columns, you can sort information in ascending or descending order. Editable table cells are shown with a pencil icon. Links to the Internet are shown with a globe icon.
•
Links in the online help can display configuration windows, related help topics, and related information from Cisco.com.
•
You can print reports, graphs, and online help topics.
For more information about CMS enhancements, refer to the "What's New" section in the online help on your switch.
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
•
•
•
•
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
•
•
•
•
–
–
Caveats
This section describes open caveats and possible unexpected activity in Release 12.0(5)WC3b:
•
Note
Open IOS Caveats
This section describes the severity 3 IOS configuration caveats in Release 12.0(5)WC3b:
•
Do not use a Category 3 cable to connect a wireless access point to a Catalyst 3500-PWR XL switch.
The workaround is to use a Category 5 cable.
•
When a source port is set at a higher speed than an egress (outgoing) port in a multicast, the transmit buffers are held in use and become full before the packets can be sent out of the egress ports. This causes the source port to run out of buffer space for the remaining traffic it needs to send, and packets are eventually dropped from the source port, causing an Input ignored multicast error.
The problem is caused by oversubscription on the egress ports. If multicast traffic is being sent out on multiple ports, the lowest-speed egress port limits the rate at which frames are dropped at the ingress port.
The workaround is to upgrade to Release 12.0(5)WC3b. Software modifications in this release alleviate the problem in these ways:
–
–
–
You have to reset the switch before these commands take effect.
•
If a port on a switch is configured as a dot1q trunk, and the switch is receiving dot1q frames that have the cfi bit set in the dot1q header, the switch drops these frames. Depending on the number of frames that are received with this bit set, connectivity to the switch can be lost.
The workaround is to prevent dot1q frames with the cfi bit set from being sent to the switch.
•
High rates of traffic sent to a MAC address that is used by an MVR multicast group and received on an MVR receiver port can cause excessive CPU utilization rates and consume enough resources on the switch CPU so that normal spanning-tree processing is interrupted. This can prevent spanning-tree loops from being broken.
The workaround is to enable multicast storm control on all MVR receiver ports.
•
In MVR, when changing the configuration of a port from receiver to source, the port does not start receiving multicast traffic.
The workaround is to save the configuration and reboot the switch to restore proper traffic flooding.
•
MVR does not initialize on a switch if that switch is a cluster member and does not have an IP address.
The workaround is to set an IP address on the switch.
•
If you configure VLAN1 as the management VLAN and configure it as administratively down, VLAN1 correctly appears as administratively down in the output of the show ip interface brief privileged EXEC command. If you configure any VLAN other than VLAN1 as the management VLAN and configure VLAN1 as administratively down, VLAN1 incorrectly appears as up in the output of the show ip interface brief command.
There is no workaround.
•
If you perform an snmpwalk SNMP operation on the CISCO-IP-STAT-MIB, continuous loops occur through the first element in the MIB tree when IP accounting precedence is configured for a VLAN interface other than VLAN1. The CISCO-IP-STAT-MIB is not supported.
The workaround is to perform individual snmpget SNMP requests to retrieve data.
•
When you connect two switches by using a GigaStack Gigabit Interface Converter (GBIC) module and you manually set the duplex mode to full duplex or to autonegotiate on both ends, the link sometimes does not stabilize.
The workaround is to remove and reinsert one of the GBICs.
•
If the switch is configured from the dynamic IP pool, a duplicate or different IP address might be assigned.
The workaround is to make sure that the DHCP server contains reserved addresses that are bound to each switch by the switch hardware address so that the switch does not obtain its IP address from the dynamic pool.
•
The serial port shares the same status bit for hardware flow control and for ready.
The workaround is to not use flow control on the console port.
•
Root guard is inconsistent when configured on a port that is in the spanning-tree blocked state when configured.
There is no workaround.
Open Cluster Configuration Caveats
This section describes the severity 3 cluster configuration caveat in Release 12.0(5)WC3b:
•
When changing the management VLAN on a cluster with command-switch redundancy enabled, the cluster can break if HSRP is configured on any of the cluster members in the new management VLAN.
The workaround is to not change the management VLAN to a VLAN where a member is configured as part of a standby group.
Open CMS Caveats
This section describes the severity 3 CMS configuration caveats in Release 12.0(5)WC3b:
•
Running a CMS link graph for more than 24 hours can cause an OutOfMemoryException error.
There is no workaround.
•
When running CMS with Windows 98 and JRE plug-in 1.3, the tool tip that shows the exact coordinates of a point on a graph is so small that it is unreadable.
There is no workaround.
•
Checking the Logarithmic Scaling check box in the Link Graph window has no effect if the Total Bytes, Total Packets, or Total Errors options are plotted.
There is no workaround.
•
CMS requires a Java plug-in from Sun Microsystems. If you are using Internet Explorer and you disable Java plug-ins by using the Java Plug-In Control Panel, the initial Splash screen shows that the plug-in and Java are enabled, but Internet Explorer fails.
The workaround is to not disable Java plug-ins on the Java Plug-In Control Panel.
•
The CMS Time Management supports the configuration of the Network Time Protocol (NTP) and system time. When you make changes on this window from a command switch, Java propagates the changes to all cluster members. A conflict can arise if you configure NTP and also use the Set Current Time and Set Daylight Saving Time tabs.
The workaround is to either set the system time for the entire cluster on the command switch or configure NTP on the command switch to use an NTP server to provide time to the cluster. Do not use both methods at the same time.
•
CMS can behave unexpectedly if host names or DNS server names that it processes contain commas. This means that host names or DNS server names on a cluster command switch, member, or neighbor can cause instability in the HTML interface.
The workaround is to not include commas in host names or DNS server names in CMS.
Resolved Caveats
This section describes caveats that have been resolved:
•
•
•
•
•
Resolved IOS Caveats in Release 12.0(5)WC3b
These configuration caveats were resolved in Release 12.0(5)WC3b:
•
When a spanning tree reconverges and VTP is pruning enabled, a Catalyst 2900 XL or 3500 XL switch no longer stops forwarding traffic for a single VLAN.
•
When a corrupted STP packet has a maximum age between 0 and 1 second, the switch no longer ages out the Bridge Protocol Data Units (BDPU). This causes a new spanning-tree root to be elected.
•
An error no longer occurs with management protocol processing. Use this URL for further information:
http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
Resolved CMS Caveat in Release 12.0(5)WC3b
This CMS caveat was resolved in Release 12.0(5)WC3b:
•
A command switch no longer fails when it receives SNMP packets that have invalid variable bindings.
Resolved IOS Caveats in Release 12.0(5)WC3
These configuration caveats were resolved in Release 12.0(5)WC3:
•
When a receiver VLAN is shut down locally, suspended throughout the VTP domain, or deleted from the VTP database, the show mvr, show mvr int, and show mvr member privileged EXEC commands now show that MVR and its members are disabled. The receiver ports remain as MVR ports, and forwarding of MVR traffic resumes after the VLAN is restored and spanning tree has transitioned to a forwarding state.
•
If an IGMP general query is received on a port that is assigned to a VLAN, but that port is not the receiver port VLAN, the query no longer interrupts the multicast streams controlled by MVR in the multicast VLAN and receiver port.
•
A switch no longer continues allocating memory for a process that has already been terminated.
Note
•
An IGMP general query received on a port that is assigned to a VLAN no longer interrupts the multicast streams controlled by MVR in the multicast VLAN and receiver port VLAN.
Note
•
Topology changes no longer cause a software forced-reload on a Catalyst 3524 XL switch.
Note
•
It is no longer necessary to clear the MAC address table on a Catalyst 3548 XL switch to be able to ping through the Fast EthernetChannel (FEC) ports on that switch after shutting down a port belonging to the FEC. (See also CSCdv58536.)
•
Executing a shutdown interface command on a FEC port does not shut down other FEC ports on the same switch.
•
A Catalyst 2900 XL or Catalyst 3500 XL switch now responds to V2 MIB objects for 64-bit counters.
•
Extra characters are no longer added to the login prompt when you log in by using Telnet.
•
After you replicate the AAA configuration to a cluster member switch, the tacacs server host line is no longer lost after the member switches are rebooted.
•
It is no longer necessary to reload the switch for the snmp-server queue-length global configuration command to take effect.
•
Sending a large amount of CDP neighbor announcements no longer consumes all of a router's available memory.
•
The output of the debug ethernet-controller addresses privileged EXEC command now shows the physical port numbers of the switch instead of the internal STP port numbers.
•
A Cisco router no longer overwrites a MAC address for one of its interfaces stored in the ARP table with an external MAC address received from an ARP packet.
•
1000BASE-X GBICs are no longer reported as unknown type in the output of the show interface status privileged EXEC command.
•
When an access port receives misconfigured ISL frames that have the Type and Priority bits set, the frames are now dropped instead of being broadcast to other ports.
Resolved CMS Caveats in Release 12.0(5)WC3
These CMS caveats were resolved in Release 12.0(5)WC3:
•
If you launch the VMPS Configuration window from the device pop-up menu in VSM, it no longer displays incorrect information.
•
The CMS software now accepts device passwords that contain these characters: `, ", ., /, \, <, >, [, ], {, }, #, %, |, ^, and ~.
•
Two identical items for the same switch are no longer listed if you select a switch in the tree by selecting Administration > Console Baud Rate, clicking cancel, and selecting Administration > Console Baud Rate again.
•
When viewing CMS dialogue windows, an exception error no longer occurs when you press the Shift key on the keyboard at the same time as you select the Add or Remove CMS buttons.
Resolved IOS Caveats in Release 12.0(5)WC2
These configuration caveats were resolved in Release 12.0(5)WC2:
•
It is no longer necessary to set the maximum number of addresses on a port to a value greater than 1 to prevent a switch from shutting down a secure port if a permitted source address is detected on the port.
•
If the management VLAN is changed to any other VLAN from VLAN 1 and VLAN 1 is shut down, the IP address configured in the new management VLAN now appears in the show cdp neighbor detail privileged EXEC command.
•
When you change the privilege level for an interface on a Catalyst 2900 XL or Catalyst 3500 XL switch, you can execute commands with the newly configured privilege level. The switch now saves the arguments associated with the command, and after a reload, the configured commands are executable.
•
When an IP phone is connected to a Fast Ethernet port that is set to 10 Mbps, half duplex on a Catalyst 3524 XL-PWR switch running Cisco IOS 12.0(5.2)XU and the switch is powered cycled, the IP phone now powers up correctly.
•
When you use the show rmon history EXEC command, the value for the collision is now unique for each sample.
•
Least Recently Used (LRU) port election now works properly on a Catalyst 3500 XL switch. When forward error correction (FEC) is broken, FEC now receives ping messages and sends back responses from the correct LRU port.
•
The ifSpeed of the interfaces now reports the default value of the visible bandwidth when the link is down and reports the configured and assigned values when the link is up.
•
When FastEtherChannel is configured, a Catalyst 2924 XL switch can now transmit broadcasts after changing the default port from FE0/1 to any other port.
•
If you loop a fiber cable to itself on a Catalyst 2924 XL switch, the interface counters now match the show controller ethernet <interface> privileged EXEC command.
•
The clear counters and clear counters fastethernet <port> interface commands now clear the port security counters. These commands also clear the other counters for the interface.
•
Changing the VLAN Trunking Protocol (VTP) mode to transparent no longer causes a virtual type terminal session to lock up when executing commands, such as the show vlan privileged EXEC command, that require access to the VLAN- and VTP-related data.
In addition, ports that were shut down during VTP mode change now come back up automatically when VTP is stable.
•
A Catalyst 2924 XL switch port configured for Port Fast can now send out the cold-start trap at reload when the trap is captured from that port.
•
When the root bridge is restarted on a Catalyst 3500 XL switch and the topology is stable, removing the link between hubs no longer generates STP topology change traps from both the root bridge and the designated bridge.
•
The output count displayed by the show interface privileged EXEC command output now displays correctly when the count is greater than 4,294,967,296 packets.
•
When chassisSlots of the old-cisco-chassis-mib is queried on a Catalyst 3524-PWR XL switch by using either the MIB browser or the CLI interface, it returns a "1."
•
When performing an snmpwalk SNMP operation on the dot1dTpFdbTable (1.3.6.1.2.1.17.4.3), the response no longer omits all entries of show mac in the display in which the first byte of the host MAC address is greater than 0x00.
•
High CPU utilization no longer occurs when a switch boots with a VLAN (without an IP address) in the shutdown state while another active VLAN has an IP address.
•
Enabling spanning-tree UplinkFast no longer causes brief spanning-tree loops if the configuration message from the root switch of the spanning tree ages out.
•
When using cross-stack UplinkFast, temporary spanning-tree loops no longer occur.
Important Notes
This section describes important information related to this release.
The MVR threshold feature was removed in Release 12.0(5.3)WC(1). Use the port multicast storm control feature instead of the MVR threshold feature to limit rates.
When you are configuring a cascaded stack of Catalyst 3500 XL switches by using a GigaStack GBIC and want to include more than one VLAN in the stack, be sure to configure all the GigaStack GBIC interfaces as trunk ports by using the switchport mode trunk interface configuration command and to use the same encapsulation method by using the switchport encapsulation {isl | dot1q} interface configuration command. For more information about these commands, refer to the command reference publication for your switch.
Documentation Notes
This section lists corrections to the hardware and software documentation.
Note
•
–
–
–
–
–
–
•
Figure 1 Crossover Cable Pinouts
•
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_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 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. Each platform, Windows and Solaris, supports three plug-in versions. For information on the supported plug-ins, see the "Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users" section and the "Solaris Platforms" section.
You can download the recommended plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
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 taskbar, right-click the Virus Shield icon, and in the Quick Enable menu, disable the options by deselecting Internet Filter or Download Scan.
Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users
These Java plug-ins are supported on the Windows platform:
•
•
•
You can download these plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
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
Note
Displaying the CMS Access Page
After the browser is configured, display the CMS access page:
Step 1
Step 2
Note
Step 3
Upgrading the Switch Software
Note
This section provides topics about upgrading the switch software:
•
•
•
•
•
•
•
•
•
•
•
Note
Guidelines for Upgrading Switch Software
When upgrading the switch software, follow these rules:
•
Similarly, you cannot upgrade Catalyst 2900 XL switches with 4 MB of DRAM to an 8-MB image. The 4-MB models are WS-C2908-XL, WS-C2916M-XL, WS-C2924C-XL, and WS-C2924-XL. In addition, these switches must run Release 11.2(8.x)SA6 to be cluster members. To determine the switch DRAM size, enter the show version user EXEC command.
•
•
•
–
–
•
•
•
•
•
–
–
–
When you upgrade a switch, the switch continues to operate while the new software is copied to Flash memory. Features provided by the new software are not available until you reboot the switch.
•
•
Overview of the Switch Upgrade Process
The software upgrade procedure has these major steps:
•
•
The tar command extracts the IOS image and the HTML 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. If a failure occurs during the copy process, you can still reboot your switch by using the old image. If Flash memory does not have enough space for two images, the new image is copied over the existing one. Features provided by the new software are not available until you reload the switch.
Determining the Switch Software Version
The IOS image is stored as a .bin file in a directory that is named with the IOS release. A subdirectory contains the HTML files needed for web management. The image is stored on the system board Flash device (flash:).
You can use the show version user EXEC command to see the software version that is running on your switch. For example:
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: 0x00202144You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that might be stored in Flash memory.
Which Software Files to Download from Cisco.com
New software releases are posted on Cisco.com and are also available through authorized resellers. From Cisco.com, you can also download a TFTP server application to copy the switch software from your PC to the switch.
Table 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.
Note
Table 9 Catalyst 2900 XL Switch IOS Software Files
c2900XL-c3h2s-mz.120-5.WC3b.bin
IOS image-only file
c2900XL-c3h2s-mz.120-5.WC3b.tar
IOS image and HTML files
Table 10 Catalyst 3500 XL Cisco IOS Software Files
c3500XL-c3h2s-mz.120-5.WC3b.bin
IOS image file
c3500XL-c3h2s-mz.120-5.WCb3.tar
IOS image file and HTML files
Downloading the New Software and TFTP Server Application to Your Management Station
Follow these steps to download the new software and, if necessary, the TFTP server application, from Cisco.com to your management station:
Step 1
Step 2
If you have a SmartNet support contract, go to one of these URLs, and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XLIf you do not have a SmartNet contract, go to one of these URLs, and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XLStep 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
Using CMS to Upgrade a Specific Switch
Note
Note
Tips
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 this command:
server% telnet switch_ip_addressStep 2
Step 3
switch> enable switch#Step 4
Step 5
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.txt6 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 6
switch# rename flash:c2900XL-c3h2s-mz-112.8.SA5.bin flash:boot.binEnsure that there are no other image files in Flash memory.
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
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.txt6 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 13
switch# show bootConfig file: flash:config.textEnable Break: noManual Boot: noHELPER path-list:NVRAM/Config filebuffer size: 32768
Recovering from an Incomplete CMS Software Upgrade
If you do not follow the preceeding procedure, an upgrade can fail due to insufficient space because of multiple software images or other files in Flash memory. When the upgrade fails, the image file is copied to Flash memory, but there is insufficient space for the HTML files, and you lose access to CMS.
If a failure occurs, ensure that the image file in Flash memory has the same name as the contents of the boot variable. You can compare these two names by following Steps 12 and 13 in the procedure.
If the contents of the boot variable and the image file name are the same, the switch can reset successfully. If they are different, rename the image file, or reset the boot variable by entering the system boot name global configuration command. The boot variable and the image file name should be the same.
To recover from the incomplete download of the HTML files, log in to the switch, and upgrade the software as described in the "Using the CLI to Upgrade Member Switches" section.
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:
•
–
–
•
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
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 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:
•
•
•
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 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# 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.3.WC.1.bin Source filename [c2900XL-h2-mz-112.8.2-SA6.bin]? Destination filename [c2900XL-c3h2s-mz-120-5.3.WC.1.bin]?Step 7
switch# config terminal Enter configuration commands, one per line. End with CNTL/Z.Step 8
switch(config)# no IP http serverStep 9
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2900XL-c3h2s-mz-120-5.3.WC.1.bin
Note
Step 10
switch(config)# endStep 11
switch# delete flash:html/*Step 12
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.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 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
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: 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.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# 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.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
Using the CLI to Upgrade Member Switches
Because a member switch might not be assigned an IP address, command-line software upgrades through TFTP are managed through the command switch.
This section provides these procedures:
•
•
Upgrading Catalyst 2900 XL or Catalyst 3500 XL 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 Catalyst 2900 Series XL and Catalyst 3500 Series XL Command Reference.
Upgrading Catalyst 1900 or Catalyst 2820 Member Switches
Follow these steps to upgrade the software on a Catalyst 1900 or Catalyst 2820 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
The Telnet session accesses the menu console (the menu-driven interface) if the command switch password is privilege level 15. If the command switch password is privilege level 1, you are prompted for the password.
You lose contact with the switch while it reloads the software.
Step 4
switch-1# copy tftp://host/src_file opcodeFor example, copy tftp://spaniel/op.bin opcode downloads new system operational code op.bin from the host spaniel.
When the download is complete, the TFTP successfully downloaded operational code message appears, and the switch resets and begins using the new software.
You can also upgrade the switch software through the Firmware Configuration menu from the menu console. For more information, refer to the installation and configuration guide that shipped with your switch.
You lose contact with the switch while it reloads the software.
Related Documentation
You can order printed copies of documents with a DOC-xxxxxx= number.
These publications provide more information about the switches and the switch software:
•
•
•
•
•
•
•
•
•
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:
Cisco Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Cisco Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
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:
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:
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 documents listed in the "Related Documentation" section.
CCIP, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0201R)
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
Guest
