Table Of Contents
Browser and Java Plug-In Requirements
Cluster Requirements and Guidelines
Catalyst 2900 XL and Catalyst 3500 XL Switches and Modules
Catalyst 1900 and Catalyst 2820 Switches and Modules
Minimum Cisco IOS Release for Major Features
Installing the Required Plug-In
Configuring Netscape Communicator (All Versions)
Configuring Microsoft Internet Explorer (4.01)
Configuring Microsoft Internet Explorer (5.0)
Displaying the CMS Access Page
Guidelines for Upgrading Switch Software
Overview of the Switch Upgrade Process
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 VSM to Upgrade a Specific Switch
Recovering from an Incomplete VSM Software Upgrade
Using Cluster Manager 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 2900 LRE 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.4)WC(1)
August 28, 2001
Cisco IOS Release 12.0(5.4)WC(1) runs on Catalyst 2900 series XL and Catalyst 3500 series XL switches with 8-MB CPU DRAM. This release also runs on Catalyst 2900 series LRE XL switches with 16-MB CPU DRAM. This release does not run on Catalyst 2900 series XL switches with 4-MB CPU DRAM.
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 XL and Catalyst 3500 XL documentation.
Note
Before upgrading your switch to this release, read the "Upgrading the Switch Software" section. If you are upgrading a Catalyst 2900 LRE XL switch, do not use the upgrade procedures in the Release Notes for the Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.0(5)WC(1). Instead, use the procedures in the "Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch" section.
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 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 Table 2) and Catalyst 3500 XL switches (see Table 3). This software also supports the Cisco 575 LRE CPE (customer premises equipment) device.
Software Requirements
This section describes the system and Cluster Management Suite (CMS) software.
System Requirements
The following operating systems are supported for CMS management:
•
•
•
•
•
The minimum PC requirement is a Pentium processor running at 233 MHz with 64 MB of DRAM. The minimum UNIX workstation requirement is a Sun Ultra 1 running at 143 MHz with 64 MB of DRAM. Table 4 lists the recommended platforms for using CMS.
Table 4 Recommended Minimum Platform Configuration for Web-Based Management
Windows NT 4.01
Pentium 300 MHz
128 MB
65,536
1024 x 768
Small
Solaris 2.5.1
SPARC 333 MHz
128 MB
Most colors for applications
—
Small (3)
1 Service Pack 3 or higher required
Browser and Java Plug-In Requirements
When starting a CMS session, the switch verifies the browser version to ensure that the browser is supported. If the browser is not supported, an error message appears, and the session does not start. Table 5 lists the browsers supported by CMS.
CMS requires the Java plug-ins described in the "Installing the Required Plug-In" section.
Table 5 Browser Requirements
Windows 95
4.61, 4.7
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
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 and Modules
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 6 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 Cisco IOS Release 12.0(5.3)WC(1) and later are cluster-capable. All Catalyst 2900 XL modules are supported in cluster configurations.
Table 6 Catalyst 2900 XL and Catalyst 3500 XL Switches as Cluster Members
Catalyst 3500 XL
Yes
Yes
Yes
Catalyst 2900 XL (8 MB of DRAM)
Yes
Yes
Yes
Catalyst 2900 XL (4 MB of DRAM)1
No
No
Yes
Catalyst 2900 LRE XL (16 MB of DRAM)
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 2950 Switches
Catalyst 2950 switches running IOS version 12.0(5)WC(1) or higher can be command and member switches. For more information, refer to the documentation for Catalyst 2950 switches.
Catalyst 1900 and Catalyst 2820 Switches and Modules
Table 7 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 or the Catalyst 2820 switches.
Minimum Cisco IOS Release for Major Features
Table 8 lists the minimum software release required to support the major features of the Catalyst 2900 XL and Catalyst 3500 XL switches.
Table 8 Catalyst 2900 XL and Catalyst 3500 XL Features and the Minimum Cisco IOS Release Required
WS-C2912-LRE XL and WS-C2912-LRE XL switches with LRE ports
Release 12.0(5.1)WC(1)
Extended cluster member functionality for Catalyst 2950 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 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 ATM modules
Release 11.2(8)SA5
IEEE 802.1Q trunking
Release 11.2(8)SA4
(Enterprise Edition Software)Inter-Switch Link (ISL) trunking
Release 11.2(8)SA5
(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 Features in this Release
This section describes the new features in this release.
•
•
New Hardware Support
This release supports the following new devices:
•
•
•
New Software Support
This release supports the following new software features:
•
•
Limitations and Restrictions
You should review this section before you begin working with the switches. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
•
•
Caution
•
•
•
•
•
•
•
•
•
–
–
Caveats
This section describes open and resolved caveats in Cisco IOS Release 12.0(5.4)WC(1):
Open Caveats
This section describes possible unexpected activity by Cisco IOS Release 12.0(5.4)WC(1):
•
Alignment and collision Ethernet counters on the Cisco 575 LRE CPE device are not reliable. These counters can increment without an Ethernet link, and they can also be higher than expected when encountering alignment and collision conditions. This is especially noticeable if an LRE port is configured with the LRE-15, the Public-ANSI, or the Public-ETSI profiles.
There is no workaround.
•
If a port group is set up between the LRE port of a Catalyst 2900 LRE XL switch and the FEC ports of another switch through the LRE CPE devices, and the LRE link on an LRE port drops, the LRE switch no longer uses the LRE port for data transmission. However, the other switch might continue sending data through the FEC port. The packets being sent to the LRE port of the LRE switch are lost.
If the LRE link is restored, data transmission continues as normal.
There is no workaround.
•
Ethernet statistics that appear in the output of the show interface command for LRE ports show the counters of the MAC on the switch instead of the MAC on the CPE device.
The workaround is to use the show controllers ethernet-controller command to see the Ethernet statistics on the CPE device. To clear the Ethernet statistics counters on the CPE device, use the clear controllers ethernet-controller command.
•
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, there can be a loss of connectivity to the switch.
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.
•
The connection between a switch and a console is lost whenever VLAN membership changes on an MVR port.
The workaround is to either Telnet to the switch to access the CLI or to reboot the switch to restore the console session.
•
When the 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 commands do not 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.
When the multicast VLAN is shut down, suspended, or deleted, source ports configured as access ports are affected in much the same way that receiver ports are affected by the removal of the receiver VLAN. If the multicast VLAN is shut down, suspended, or deleted, source ports that are trunk ports are removed from MVR. After the VLAN is restored, these source ports must be manually added to MVR.
A workaround for the ports not being removed automatically from MVR is to manually remove any MVR source access ports or receiver ports that were configured in a VLAN that has been removed. You can do this by using the no mvr type [receiver | source] interface configuration command.
There is no workaround for the fact that these interfaces will be listed as active when the mvr show commands are used, even though the interface is down.
•
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 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 interrupts the multicast streams controlled by MVR in the multicast VLAN and receiver port.
The workaround is to make sure that no IGMP queries are sent to those VLANs.
•
Running a CMS link graph for more than 24 hours can cause an OutOfMemoryExeception error.
There is no workaround.
•
When running CMS with Windows 98 and JRE plug-in 1.3, the tooltip box 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 Byts, Total Packets, or Total Errors boxes are plotted.
There is no workaround.
•
If you select a switch in the tree by using Cluster Management and choose Console Baud Rate, the baud rate dialog appears with the selected switch in the Selected Device list. If you then click cancel and select Console Baud Rate again, two identical items for the same switch are listed.
There is no workaround.
•
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 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.
•
When you use the show rmon history command, the value for the collision is cumulative, not unique for each sample. The value for a collision in a given sample can be calculated by subtracting from the previous sample.
There is no workaround.
•
If you shut down the management VLAN on VLAN1 on a Catalyst 2950 switch, set the management VLAN to 999, and then again use the shutdown command to shut down VLAN1, the IP address of VLAN 999 does not appear in the show cdp neighbor detail command display on a connected device.
The workaround is to reboot the switch.
•
Two problems occur when the Catalyst 2950 switch is in transparent mode:
–
–
There is no workaround.
•
On Catalyst 2900 XL and 3500 XL switches, when you change the privilege level for the interface, you can execute commands with the newly configured privilege level. However, the switch does not save the arguments associated with the command, and after a reload, the configured commands are not executable.
There is no workaround.
•
CMS dialogue windows can display two list selection boxes with Add and Remove buttons between them. If you press the Shift key on the keyboard at the same time as either Add or Remove, sometimes an exception error occurs. The exception error is displayed only inside the Java console window and is not displayed by CMS. As a result, the Add or Remove buttons might not function correctly. If you continue to click these buttons, multiple entries are added to the available or selected lists.
The workaround is to not hold down the Shift key when clicking Add or Remove.
•
If you launch the VMPS Configuration window from the device pop-up menu in Visual Switch Manager (VSM), it displays incorrect information.
The workaround is to not launch the VMPS Configuration window from the device popup menu, as VLAN Membership Policy Server (VMPS) is not supported on the Catalyst 2950 switches.
•
If you continuously ping a switch from a PC and the links from the switch to the network are brought down, when the link from the switch to the network is restored, pinging does not resume.
The workaround is to enter the clear cam command.
•
If you enter the snmpwalk command 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 workaround is to use individual snmpget requests to retrieve data.
•
The usage of the c2950BandwidthUseage MIB always shows zero, instead of displaying the current bandwidth usage statistics.
There is no workaround.
•
On a Catalyst 3524 XL-PWR switch running Cisco IOS 12.0(5.2)XU, if an IP phone is connected to a Fast Ethernet port that is set to 10 Mbps half duplex and the switch is powered on and off, the IP phone does not power up.
The workaround is to disconnect the Ethernet cable and then reconnect it.
•
When you connect two switches by GigaStack GBICs and you manually set 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 gets 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.
•
Cluster Management Suite 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 Cluster Manager System Time Management window 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 Daylight Saving Time and Set Current 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.
•
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.
•
When you change 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.
•
Root guard is inconsistent when configured on a port that is in the STP blocked state at the time of configuration.
There is no workaround.
•
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
The following problems were resolved in Cisco IOS Release 12.0(5.4)WC(1):
•
When MVR is enabled and the MVR VLAN has been configured on a Catalyst 3508 XL switch, and at least one port has been set up as a receiver port, the switch no longer fails.
•
Cisco Discovery Protocol (CDP) packets that are sent out on Long Reach Ethernet ports now include the voice VLAN type-length-value (TLV) in their advertisements. An IP phone that is connected through a Cisco 575 LRE CPE device now sees the call center application running on the LRE switch.
•
When an ASIC does not pass the power-on self-test (POST) due to a built-in self-test (BIST) failure, an IOS error message now appears, and the ASIC is not initialized.
•
A Catalyst 2900 XL or 3500 XL switch no longer sends DHCP request packets every 4.5 seconds if no IP address is configured on interface VLAN 1.
•
Support for the CDP v2 values of native VLAN, half-duplex, and full-duplex modes is now consistent across all Catalyst 2900 XL and 3500 XL switches.
•
A Catalyst 2924 XL switch no longer runs a routine that sometimes causes packets to be noticeably dropped for approximately 2 milliseconds every 41 minutes.
•
When a Catalyst 3500 XL switch is scanned with Cisco Secure Scanner using the Active Probe named Php-Overflow, the switch no longer fails.
•
The Cross-stack UplinkFast feature no longer takes 10 to 15 seconds to recover from a failed link when the management VLAN is configured for a non-default VLAN.
•
A Catalyst 3500 XL switch that receives a 64- or 66-byte 802.1q encapsulated frame on a trunk port no longer counts the frame as a runt.
•
A switch now saves and uses a gateway address that it learns from a DHCP server.
•
After the no shutdown command is entered for an interface that is connected to a PC and STP is disabled on the VLAN to which that port belongs, frames are forwarded to that interface.
•
The switchports in a VLAN are no longer disabled after the MTU of that VLAN is changed to a value greater than 1500 bytes in the VLAN database.
•
The no snmp-server enable traps snmp [authentication] command now prevents authentication failure traps from being sent to the NMS.
•
When the sh line command is run from a console or vty session, the error message SCHED-3-UNEXPECTEDEVENT error for Exec process no longer appears.
•
A switch configured for Cross-stack UplinkFast that has failed over to a backup link no longer loses connectivity when the primary link is restored.
•
When configuring a switch using the switchport trunk command, and a line of text exceeds 80 characters, the text is now parsed correctly by IOS.
•
An MVR receiver port that receives multicast data traffic exceeding the configured threshold does not shut down. 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.
•
The MVR threshold feature causes switch ports to be shut down when creating MVR groups. The MVR threshold feature was removed in Release 12.0(5.3)WC(1).
•
The connection between a switch and console is no longer lost when VLAN membership changes on an MVR port.
•
After the last receiver port is removed from a receiver VLAN, you can now make a port in another VLAN a receiver port.
•
The power inline never command now correctly changes the link pulse from a power link pulse to a standard link pulse.
•
If a client is moved from one secure port to another, and the maximum secure address count on the second port is exceeded, the switch now sends security violation traps.
•
Cisco IOS software now prevents the successful prediction of TCP Initial Sequence Numbers.
•
When a loopback command is followed by a no loopback command on a port connected to a device, such as an Ethernet time clock, that port now correctly comes out of loopback.
Important Notes
This section describes important information related to this release.
The MVR threshold feature has been removed from Release 12.0(5.3)WC(1). Use the port multicast storm control feature instead of the MVR threshold feature to limit rates.
In this release, 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.
•
–
–
•
•
•
•
–
•
To view the contents of the documentation CD, double-click the index.htm file. Your browser launches, and you can select and view the documents on the CD.
If your PC is set to automatically launch CDs, the index page opens when you insert the CD or when you click the CD icon. If you need more information about how to set your PC to automatically launch CDs, consult your PC operating system documentation or systems administrator.
•
–
–
–
The PUBLIC-ANSI, PUBLIC-ETSI, LRE-5, LRE-10, and LRE-15 profiles described in the manuals and online help have the interleaver feature enabled for maximum protection against small interruptions on the LRE link.
The interleaver feature delays the data, while increasing protection for the data against very small interruptions in the LRE link. By enabling the low latency feature, data is more susceptible to interruptions on the LRE link, but the delay is removed. The LL in these profiles stands for low latency. In these profiles, the interleaver feature is turned off.
Table 9 lists all of the LRE profiles available on the Catalyst 2900 LRE XL switches.
Note
Note
•
Note
•
Caution
•
–
–
•
.
•
Figure 1 Crossover Cable Pinouts
•
Initial Switch Configuration
This section provides these procedures:
•
•
•
•
This section assumes 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 abort 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 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 that in the Proxies tab the Use browser settings is checked and that no proxies are enabled.
If you are running McAfee VirusScan on Windows 2000 and the plug-in takes a long time to load, you can speed up CMS operation by disabling the ViruScan Internet Filter option, the Download Scan option, or both:
•
or
•
Windows 2000, Windows 95, Windows 98, and Windows NT 4.0 Users
These Java plug-ins are supported on the Windows platform:
Caution
plug-in 1.3.0.
•
If you start CMS without having installed the required Java plug-in, the switch automatically detects this. If you are using a supported Internet Explorer browser, it automatically downloads and installs the plug-in. If you are using a supported Netscape browser, the browser displays a Cisco.com (previously Cisco Connection Online [CCO]) page that contains the Java plug-in and installation instructions. If you are using Windows 2000, Netscape Communicator might not detect the missing Java plug-in. You can download the plug-in from one of these URLs:
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
•
This plug-in is not downloaded automatically. However, you can download it from this URL:
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
Solaris Users
These Java plug-ins are supported on the Solaris platform:
Caution
plug-in 1.3.0.
•
This plug-in is supported, but not provided on the Cisco.com URL.
•
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
•
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
–
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Configuring Your Browser
To access CMS, your Netscape Communicator or Microsoft Internet Explorer browser must be properly configured.
Configuring Netscape Communicator (All Versions)
Follow these steps to configure Netscape Communicator:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Configuring Microsoft Internet Explorer (4.01)
Follow these steps to configure Microsoft Internet Explorer 4.01:
Step 1
Step 2
Step 3
a.
b.
Step 4
Step 5
Configuring Microsoft Internet Explorer (5.0)
Note
Follow these steps to configure Microsoft Internet Explorer 5.0:
Step 1
Step 2
Step 3
a.
b.
Step 4
a.
b.
Note
Displaying the CMS Access Page
After the browser is configured, display the Cluster Management Suite access page:
Step 1
Step 2
Step 3
Upgrading the Switch Software
This section provides topics about upgrading the switch software:
•
•
•
•
•
•
•
•
•
•
•
Note
Note
Guidelines for Upgrading Switch Software
When upgrading 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 IOS Release 11.2(8.x)SA6 original edition software to be cluster members. No original edition software package is available for this release of IOS. To determine the switch DRAM size, enter the show version user EXEC command.
•
•
•
•
•
•
–
–
•
•
Overview of the Switch Upgrade Process
See the following sections if you are using CMS or the CLI to upgrade the software on your switch or switch cluster:
•
•
•
–
–
–
–
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.
•
•
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 11 describes the file extensions and what they mean for the upgrade procedure. Table 12 and Table 13 list the software files you need from Cisco.com.
Note
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 VSM to Upgrade a Specific Switch
Note
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.txt5 -rwx 1644050 Mar 01 1993 19:36:14 c2900XL-c3h2s-mz-112.8.SA5.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_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 VSM 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 VSM.
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 Cluster Manager to Upgrade One or More Switches
You can use the Software Upgrade feature of the Cluster Manager to upgrade all or some of the switches in a cluster at once. Consider the following conditions when doing an upgrade:
•
•
•
•
Note
Follow these steps to use Cluster Manager to upgrade 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 Name 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 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 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
Note
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. The procedure returns 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 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 bootIf there is no file defined in the BOOT path-list, enter dir flash: 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 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 2900 LRE XL Switch
Note
Follow these steps to upgrade the LRE switch software:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enableswitch#Enter a password if you are prompted to do so.
Step 4
switch# show bootConfig file: flash:config.textEnable Break: 1Manual Boot: noHELPER path-list:NVRAM/Config filebuffer size: 32768If there is no file defined in the BOOT path-list, enter dir flash: to display the contents of Flash memory. The file named c2900XL-c3h2-mz-120-5.1.WC.1.bin is your previous image file.
switch# dir flash:Directory of flash:/175 -rwx 111 May 17 2001 13:25:53 info.ver165 -rwx 8192 May 17 2001 13:22:13 e2rb.bin4 drwx 10240 May 17 2001 13:25:52 html167 -rwx 1496 May 17 2001 13:21:46 config.text6 -rwx 111 May 17 2001 13:23:41 info176 -rwx 1422 Jan 01 1970 00:14:43 env_vars7741440 bytes total (4692992 bytes free)Step 5
switch# rename flash:c2900XL-c3h2s-mz.120-5.1.WC.1.bin flash:c2900XL-c3h2s-mz.120-5.3.WC.1.binDestination filename [c2900XL-c3h2s-mz.120-5.3.WC.1.bin]?Step 6
switch# delete flash:e2rb.binStep 7
Step 8
switch# config terminalStep 9
switch(config)# no IP http serverStep 10
Note
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2900XL-c3h2s-mz-120-5.3.WC.1.binStep 11
switch(config)# endStep 12
switch# delete flash:html/*Step 13
Step 14
switch# delete flash:html/Snmp/*
Note
Step 15
Step 16
Caution
switch# tar /x tftp://server_ip_address/path/filename.tar flash:Loading /path/filename.tar from server_ip_address (via VLAN1): !extracting info (111 bytes)extracting c2900XL-c3h2s-mz.120-5.3.WC.1.bin (1750311 bytes)!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!html/ (directory)extracting html/ClusterBuilder.html.gz (670 bytes)extracting html/ClusterManager.html.gz (624 bytes)extracting html/back.html.gz (211 bytes)!. . .Depending on the TFTP server being used, you might need to enter only one slash (/) after the server_ip_address in the tar command. The tar command extracts the IOS image and the HTML files from the combined .tar file during the TFTP copy to the switch.
Step 17
switch# copy tftp://server_ip_address/path/e2rb.bin flash:Destination filename [e2rb.bin]?Accessing tftp://server_ip_address/path/e2rb.bin...Loading /path/e2rb.bin from server_ip_address (via VLAN1): !![OK - 8192 bytes]8192 bytes copied in 0.259 secsStep 18
switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 19
switch(config)# IP http serverStep 20
switch(config)# endStep 21
switch# reloadSystem configuration has been modified. Save? [yes/no]: yProceed with reload? [confirm]Step 22
Your Telnet session ends when the switch resets.
Step 23
If you have a previously opened browser session to the upgraded switch, close the browser, and start it again to ensure that you are using the latest HTML files.
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 command, with the following 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 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.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 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 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.
You should see the TFTP successfully downloaded operational code message. When the download is complete, 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
The following 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:
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 documents listed in the "Related Documentation" section.
AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, 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 Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, 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. (0106R)
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
Guest
