Table Of Contents
Release Notes for the Catalyst 2950 Switch Cisco IOS Release 12.1(9)EA1
Recommended Platform Configuration for Web-Based Management
Operating System and Browser Support
Installing the Required Plug-In
Creating Clusters with Different Releases of IOS Software
Guidelines for Downloading Switch Software
Determining the Software Version and Feature Set
Upgrading a Switch by Using CMS
Upgrading a Switch by Using the CLI
Downloading the Software and TFTP Server Application
Copying the Current Startup Configuration from the Switch to a PC or Server
Using the CLI to Upgrade a Catalyst 2950 Switch
Upgrading Catalyst 2950, Catalyst 2900 XL, or Catalyst 3500 XL Member Switches
Upgrading Catalyst 1900 or Catalyst 2820 Member Switches
Recovering from Software Failure
Setting Up the Catalyst 2950 Initial Configuration
Configuring Browsers and Accessing CMS
Configuring Netscape Communicator (All Versions)
Configuring Microsoft Internet Explorer (4.01)
Configuring Microsoft Internet Explorer (5.0)
Displaying the CMS Access Page
Connecting Catalyst 2950G-24-EI-DC Switches to Compatible Devices
Obtaining Technical Assistance
Release Notes for the Catalyst 2950 Switch Cisco IOS Release 12.1(9)EA1
April 26, 2002
The Cisco IOS Release 12.1(9)EA1 runs on Catalyst 2950 switches.
These release notes include important information about this IOS release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:
•
If you are installing a new switch, refer to the IOS release label on the rear panel of your switch.
•
•
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 information is in the release notes:
•
•
•
•
•
•
•
System Requirements
These are the system requirements for this IOS release:
•
•
Hardware Supported
The Catalyst 2950 switch is supported by either the standard software image (SI) or the enhanced software image (EI). The enhanced software image provides a richer set of features, including access control lists (ACLs), enhanced quality of service (QoS) features, the Secure Shell Protocol, extended-range VLANs, the IEEE 802.1W Rapid Spanning Tree Protocol (RSTP), and the IEEE 802.1S Multiple STP (MSTP).
Table 1 lists the hardware supported by this release:
Table 1 Hardware Supported
Catalyst 2950-12
Standard image
12 fixed autosensing 10/100 Ethernet ports
Catalyst 2950-24
Standard image
24 fixed autosensing 10/100 Ethernet ports
Catalyst 2950C-24
Enhanced image
24 fixed autosensing 10/100 Ethernet ports and 2 100BASE-FX ports
Catalyst 2950G-12-EI
Enhanced image
12 fixed autosensing 10/100 Ethernet ports and 2 GBIC1 module slots
Catalyst 2950G-24-EI
Enhanced image
24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots
Catalyst 2950G-24-EI-DC
Enhanced image
24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots with DC-input power
Catalyst 2950G-48-EI
Enhanced image
48 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots
Catalyst 2950T-24
Enhanced image
24 fixed autosensing 10/100 Ethernet ports and 2 10/100/1000 Ethernet ports2
GBIC Modules
—
•
•
•
•
•
•
Redundant power system
—
Cisco RPS 300 Redundant Power System
1 GBIC = Gigabit Interface Converter
2 The 10/100/1000 ports operate only in full-duplex mode.
3 This feature is only supported when your switch is running the enhanced software image.
Hardware Not Supported
Table 2 lists the hardware that is not supported by this release:
Table 2 Hardware Not Supported
GBIC module
1000BASE-T GBIC (model WS-G4582)
Redundant power system
Cisco RPS 600 Redundant Power System
Software Compatibility
These are the software compatibility requirements for this IOS release:
•
•
•
•
Recommended Platform Configuration for Web-Based Management
Table 3 lists the recommended platforms for Web-based management.
Table 3 Recommended 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 is required.
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.
For information about supported operating systems, see the next section.
Operating System and Browser Support
You can access the web-based interfaces by using the operating systems and browsers listed in Table 4. The switch checks the browser version when starting a session to ensure that the browser is supported. If the browser is not supported, the switch displays an error message, and the session does not start.
Table 4 Supported Operating Systems and Browsers
Windows 95
Service Pack 1
4.61, 4.7x
4.01a, 5.0, 5.5
Windows 98
Second Edition
4.61, 4.7x
4.01a, 5.0, 5.5
Windows NT 4.0
Service Pack 3 or later
4.61, 4.7x
4.01a, 5.0, 5.5
Windows 2000
None
4.61, 4.7x
4.01a, 5.0, 5.5
Solaris 2.5.1 or later
Sun-recommended patch cluster for the OS and Motif library patch 103461-24
4.61, 4.7x
Not supported
1 Netscape Communicator versions 4.60 and 6.0 are not supported.
2 Service Pack 1 or higher is required for Internet Explorer 5.5.
Note
Note
Installing the Required Plug-In
A Java plug-in is required for the browser to access and run the Java-based Cluster Management Suite (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 2000, Windows 95, Windows 98, and Windows NT 4.0 Platforms" 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 2000, Windows 95, Windows 98, and Windows NT 4.0 Platforms
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
•
•
•
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.
Creating Clusters with Different Releases of IOS Software
When a cluster consists of Catalyst 3550 switches and a mixture of other Catalyst switches, we strongly recommend using only the Catalyst 3550 switches as the command and standby command switches. When the command switch is a Catalyst 3550 switch, all standby command switches must also be Catalyst 3550 switches. The Catalyst 3550 switch that has the latest software should be the command switch.
If your cluster has Catalyst 2950, Catalyst 2900 XL, and Catalyst 3500 XL switches, the Catalyst 2950 switch should be the command switch. The Catalyst 2950 switch that has the latest software should be the command switch.
If your switch cluster has Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, and Catalyst 3500 XL switches, either the Catalyst 2900 XL or Catalyst 3500 XL should be the command switch. The Catalyst 2900 or 3500 XL switch that has the latest software should be the command switch.
Table 5 lists the cluster capabilities and software versions for the switches.
Some versions of the Catalyst 2900 XL software do not support clustering, and if you have a cluster with switches that are running different versions of IOS software, software features added on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a Catalyst 2900 XL switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)WC(1) or later.
Note
Downloading Software
This section describes these procedures for downloading software:
•
•
•
•
•
Note
Note
Guidelines for Downloading Switch Software
When using CMS to upgrade multiple switches from the Cisco TFTP server, the Cisco TFTP server application can process multiple requests and sessions. When using CMS to upgrade multiple switches from the Cisco TFTP server, you must first disable the TFTP Show File Transfer Progress and the Enable Logging options to avoid TFTP server failures. If you are performing multiple-switch upgrades with a different TFTP server, it must be capable of managing multiple requests and sessions at the same time.
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.
If a failure occurs while copying a new image to the switch, and the old image has already been deleted, refer to the "Recovering from Corrupted Software" section in the "Troubleshooting" chapter of the Catalyst 2950 Desktop Switch Software Configuration Guide.
Determining the Software Version and Feature Set
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. In the display, check the line that begins with System image file is. This line shows the directory name in Flash memory where the image is stored. A couple of lines below the image name, you see Running Enhanced Image if you are running the enhanced software image or Running Standard Image if you are running the standard software image.
Note
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in Flash memory.
Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined .tar file. This file contains both the IOS image file and the HTML files (needed for the CMS). You must use the combined .tar file to upgrade the switch through the CMS.
The .tar file is an archive file from which you can extract files by using the archive tar command.
Note
Table 6 lists the software filenames for this IOS release.
Upgrading a Switch by Using CMS
You can upgrade switch software by using CMS. From the menu bar, select Administration > Software Upgrade. For detailed instructions, click Help.
If you are using Cluster Manager to upgrade a switch cluster, you can use the Software Upgrade feature 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 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
Upgrading a Switch by Using the CLI
To download switch software by using the CLI, follow these procedures in this order:
•
•
Use the archive tar command to extract the IOS image and the HTML files from the .tar file during the TFTP copy to the switch. If you are upgrading from a release earlier than Release 12.1(6)EA2, use the tar command instead of the archive tar command.
•
If the upgrade to the new software fails or if the new startup configuration fails, you can reinstall the previous version of the switch software and use the copy of the startup configuration file to start the switch. If a failure occurs while copying a new image to the switch, and the old image has already been deleted, see the "Guidelines for Downloading Switch Software" section.
•
•
–
–
If you are upgrading a member switch in a switch cluster, because a member switch might not be assigned an IP address, command-line software upgrades through TFTP are managed through the command switch.
Note
Downloading the Software and TFTP Server Application
This procedure is for copying the combined .tar file to the Catalyst 2950 switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
Follow these steps to download the software and, if necessary, the TFTP server application, from Cisco.com to your management station:
Step 1
Step 2
•
http://www.cisco.com/public/sw-center/sw-lan.shtml
•
http://www.cisco.com/public/sw-center/sw-lan.shtml
To download the enhanced and standard software files, select Download Cisco Catalyst 2950 software.
Step 3
The readme.txt file describes how to download the TFTP server application. New features provided by the software are not available until you reload the software.
Copying the Current Startup Configuration from the Switch to a PC or Server
When you make changes to a switch configuration, your changes become part of the running configuration. When you enter the command to save those changes to the startup configuration, the switch copies the configuration to the config.text file in Flash memory. To ensure that you can recreate the configuration if a switch fails, you might want to copy the config.text file from the switch to a PC or server.
This 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 the CLI to Upgrade a Catalyst 2950 Switch
This procedure is for upgrading Catalyst 2950 switches by copying the .tar file to the switch. You copy the files to the switch from a TFTP server and extract the files by entering the archive tar 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
Note
switch# rename flash:current_image flash:new_image Source filename [current_image]? Destination filename [new_image]?For example:
switch# rename flash:c2950-i6q4l2-mz.121-6.EA2c.bin flash:c2950-i6q4l2-mz.121-9.EA1.binStep 7
switch# dir flash:Directory of flash:/3 drwx 10176 Mar 01 2001 00:04:34 html6 -rwx 2343 Mar 01 2001 03:18:16 config.text171 -rwx 1667997 Mar 01 2001 00:02:39 c2950-i6q4l2-mz.121-9.EA1.bin7 -rwx 3060 Mar 01 2001 00:14:20 vlan.dat172 -rwx 100 Mar 01 2001 00:02:54 env_vars7741440 bytes total (4788224 bytes free)Step 8
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 9
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2950-i6q4l2-mz.121-9.EA1.bin
Note
Step 10
switch(config)# endStep 11
switch# delete flash:html/*Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 12
Caution
switch# archive 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 c2950-i6q4l2-mz.121-9.EA1.bin (2239579 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 archive tar command.
Step 13
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 14
switch(config)# endStep 15
switch# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm]Step 16
Your Telnet session ends when the switch resets.
After the switch reboots, use Telnet to return to the switch, and enter the show version user EXEC command to verify the upgrade procedure. 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.
Upgrading Catalyst 2950, Catalyst 2900 XL, or Catalyst 3500 XL Member Switches
Follow these steps to upgrade the software on a member switch:
Step 1
switch# show cluster membersFrom the output, 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> 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
Note
switch# rename flash:current_image flash:new_image Source filename [current_image]? Destination filename [new_image]?For example:
switch# rename flash:c2950-i6q4l2-mz.121-6.EA2c.bin flash:c2950-i6q4l2-mz.121-9.EA1.binStep 7
switch# dir flash:Directory of flash:/3 drwx 10176 Mar 01 2001 00:04:34 html6 -rwx 2343 Mar 01 2001 03:18:16 config.text171 -rwx 1667997 Mar 01 2001 00:02:39 c2950-i6q4l2-mz.121-9.EA1.bin7 -rwx 3060 Mar 01 2001 00:14:20 vlan.dat172 -rwx 100 Mar 01 2001 00:02:54 env_vars7741440 bytes total (4788224 bytes free)Step 8
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 9
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2950-i6q4l2-mz.121-9.EA1.bin
Note
Step 10
switch(config)# endStep 11
switch# delete flash:html/*Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 12
Caution
switch-1# archive 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 13
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 14
switch(config)# endStep 15
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 2950 Desktop Switch 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. If this message does not appear, refer to the installation and configuration guide that shipped with your switch for more information.
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.
Recovering from Software Failure
If the software fails, you can reload the software. For detailed recovery procedures, refer to the "Troubleshooting" chapter in the Catalyst 2950 Desktop Switch Software Configuration Guide.
Installation Notes
You can assign IP information to your switch by using the setup program, the Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration (refer to the Catalyst 2950 Desktop Switch Software Configuration Guide), or by manually assigning an IP address (refer to the Catalyst 2950 Desktop Switch Software Configuration Guide).
This section describes these installation procedures:
•
•
Setting Up the Catalyst 2950 Initial Configuration
The first time that you access the switch, it runs a setup program that prompts you for an IP address and other configuration information necessary for the switch to communicate with the local routers and the Internet. This information is also required if you plan to use the CMS to configure and manage the switch.
Note
Follow these steps to create an initial configuration for the switch:
Step 1
Would you like to enter the initial configuration dialog? [yes/no]: yesAt any point you may enter a question mark '?' for help.Use ctrl-c to abort configuration dialog at any prompt.Default settings are in square brackets '[]'.Basic management setup configures only enough connectivityfor management of the system, extended setup will ask youto configure each interface on the system.Would you like to enter basic management setup? [yes/no]: yesStep 2
On a command switch, the host name is limited to 28 characters; on a member switch to 31 characters. Do not use -n, where n is a number, as the last character in a host name for any switch.
Enter host name [Switch]: host_nameStep 3
The password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, allows spaces, but ignores leading spaces.
Enter enable secret: secret_passwordStep 4
Enter enable password: enable_passwordStep 5
The password can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces.
Enter virtual terminal password: terminal-passwordStep 6
Step 7
Enter interface name used to connect to themanagement network from the above interface summary: vlan 1Step 8
Configuring interface vlan1:Configure IP on this interface? [yes]: yesIP address for this interface: 10.4.120.106Subnet mask for this interface [255.0.0.0]: 255.255.255.0Step 9
If you enter N, the switch appears as a candidate switch in the CMS. In this case, the message in Step 10 does not appear.
Would you like to enable as a cluster command switch? [yes/no]: yesStep 10
Enter cluster name: cluster_nameThe cluster name can be 1 to 31 alphanumeric characters, dashes, or underscores.
The initial configuration appears:
The following configuration command script was created:hostname host_nameenable secret 5 $1$Max7$Qgr9eXBhtcBJw3KK7bc850enable password grandkey1line vty 0 15password grandkeysnmp-server community public!no ip routing!interface Vlan1no shutdownip address 172.20.139.145 255.255.255.224!interface Vlan2shutdownno ip address!interface FastEthernet0/1!interface FastEthernet0/2!...<output abbreviated)!!!interface GigabitEthernet0/1!interface GigabitEthernet0/2!endStep 11
[0] Go to the IOS command prompt without saving this config.[1] Return back to the setup without saving this config.[2] Save this configuration to nvram and exit.Enter your selection [2]:Make your selection, and press Return.
After you complete the setup program, the switch can run the created default configuration. If you want to change this configuration or want to perform other management tasks, use one of these tools:
•
•
Configuring Browsers and Accessing CMS
For the browser to use CMS, a Java plug-in is required, as described in the "Installing the Required Plug-In" section. After you have assigned an IP address to the switch and installed the plug-in, you can access the switch from your browser and use the CMS to configure other switches. To use the web-based tools, see the "Software Compatibility" section to set up the appropriate browser options.
This section describes these installation procedures:
•
•
•
•
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
a.
b.
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.
If you are using Microsoft Internet Explorer 5.0 to make configuration changes to the switch, note that this browser does not automatically reflect the latest configuration changes. Make sure that you click Refresh for every configuration change.
Displaying the CMS Access Page
After the browser is configured, display the CMS access page:
Step 1
Step 2
Note
The Cisco Systems Access page appears. For more information on setting passwords and privilege levels, refer to the Catalyst 2950 Desktop Switch Software Configuration Guide.
Step 3
If you access CMS from a standalone or a cluster-member switch, Device Manager appears.
New Features
These are the new supported hardware and the new software features provided in IOS Release 12.1(9)EA1.
•
•
New Hardware Features
For a list of supported hardware, see the "Hardware Supported" section.
New Software Features
Cisco IOS Release 12.1(9)EA1 contains these new features or enhancements:
•
•
•
•
•
•
•
•
–
–
Limitations and Restrictions
You should review this section before you begin working with the switches. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
These are the limitations and restrictions:
•
Port Configuration Conflicts
Certain combinations of port features create configuration conflicts (see Table 7). If you try to enable incompatible features, CMS issues a warning message, and you cannot make the change. Reload the page to refresh CMS.
In Table 7, No means that the two referenced features are incompatible, and both should not be enabled; Yes means that both can be enabled at the same time and do not cause an incompatibility conflict. A dash means not applicable.
Table 7 Conflicting Features
-
No
Yes
No
Yes
Yes
No
No
-
Yes
No
Yes
No
No
Yes
Yes
-
No
Yes
Yes1
Yes
No
No
No
-
Yes
Yes
No
Yes
Yes
Yes
Yes
-
Yes
-
Yes
No
Yes1
Yes1
Yes
-
-
No
No
Yes
No
-
-
-
1 Switch Port Analyzer (SPAN) can operate only if the monitor port or the port being monitored is not a protected port.
SPAN Limitations
When using the Switched Port Analyzer (SPAN) feature, the monitoring port receives copies of sent and received traffic for all monitored ports. If the monitoring port is 50 percent oversubscribed for a sustained period of time, it will probably become congested. One or more of the ports being monitored might also experience a slowdown.
Important Notes
This section describes important information related to this IOS release. These sections are included:
•
•
•
Read-Only Mode in CMS
CMS provides two levels of access to the configuration options. If your privilege level is 15, you have read-write access to CMS. If your switch privilege level is from 1 to 14, you have read-only access to CMS. In the read-only mode, some show commands are not available when these switches are running these software releases:
•
•
•
Therefore, the windows that use these show commands do not display data. These windows display an error message.
In the Front Panel view or Topology view, CMS does not display error messages. In the Front Panel view, if the switch is running one of the software releases listed previously, the device LEDs do not appear. In Topology view, if the member is an LRE switch, the customer premises equipment (CPEs) connected to the switch do not appear. The Bandwidth and Link graphs also do not appear in these views.
To view switch information, you need to upgrade the member switch software. For information about upgrading switch software, see the "Downloading Software" section.
Connecting Catalyst 2950G-24-EI-DC Switches to Compatible Devices
When connecting the ports on Catalyst 2950G-24-EI-DC switches to compatible devices, follow these guidelines:
Caution
Caution
Changing the Management VLAN
The management interface configuration command is not supported in Release 12.1(6)EA2 or later. To shut down the current management VLAN interface and to enable the new management VLAN interface, use the shutdown and no shutdown interface configuration commands. Refer to the Catalyst 2950 Desktop Switch Command Reference for information about using the shutdown interface configuration command.
IGMP Filtering
IGMP filtering controls only group specific query and membership reports, including join and leave reports. It does not control general IGMP queries.
Caveats
These are the open and resolved caveats:
Open Caveats
This section describes possible unexpected activity by Release 12.1(9)EA1:
•
In an UplinkFast network topology, the alternate port becomes the root port when the original root port loses connectivity. On switches running Release 12.1(6)EA2 or later, if connectivity is restored on the original root port, dummy multicast frames are not sent from that port.
There is no workaround.
•
When multicast data is received on a blocked trunk port in a VLAN on the switch, it might take unnecessary cycles to process these packets, possibly affecting the stability of the spanning tree states.
The workaround is to not send multicast data on a port that is in the STP blocked state in the VLAN on which data is sent.
•
If a port is configured as a secure port with the violation mode as restrict, the secure ports might process packets even after maximum limit of MAC addresses is reached, but those packets are not forwarded to other ports.
There is no workaround.
•
When a Catalyst 2950 switch in a cluster is the command switch of a Catalyst 3550 member switch, the Catalyst 3550 switch does not show any egress policy information in the Attach tab of the QoS Policies window.
There is no workaround.
•
When the Catalyst 2950 switch is in VTP transparent mode, and it receives frames from a trunk port with an unknown VLAN ID number, certain frames might be sent to the same trunk port with a VLAN ID that is the same as the switch management VLAN and a source MAC address that is the same as its destination MAC address.
The workaround is to configure the switch to nontransparent mode or to avoid frames that have an unknown VLAN ID.
•
When an ACL is created with different masks in Release 12.1(6)EA2 or later, you get an error message. However, when the access-list is created with different masks in Release 12.0(5)WC2 or earlier, you do not get an error message.
There is no workaround.
•
Traffic interruption can occur for several seconds during a cross-stack UplinkFast (CSUF) root-port transition.
There is no workaround.
•
On the Catalyst 2950 switches, you can monitor incoming traffic on multiple ports by using the CLI; however, you can only select one port if you are using CMS.
The workaround is to use the CLI to monitor incoming traffic on multiple ports.
•
When a Catalyst 2950 cluster command-switch is running Cisco IOS Release 12.1(6)EA2 or later and you enter the no cluster commander-address global configuration command on a member switch of this cluster, the member switch cannot be removed from the cluster if there are any member switches beyond that member switch.
The workaround is to enter the no cluster member n global configuration command on the command switch to remove the member from the cluster.
•
When you enter the show controllers ethernet-controller interface-id or show interfaces interface-id counters privileged EXEC command, if a large number of erroneous frames are received on an interface, the receive-error counts might be smaller than the actual values, and the receive-unicast frame count might be larger than the actual frame count.
There is no workaround.
•
If the cluster command-switch is a Catalyst 2900 XL switch, a Catalyst 2950 switch running software earlier than Release 12.1(6)EA2, or a Catalyst 3500 XL switch that is connected to a Catalyst 2950 switch running Release 12.1(6)EA2 or later or to a Catalyst 3550 switch, the command switch does not find any cluster candidates beyond the Catalyst 2950 or 3550 switch if it is not a member of the cluster.
The workaround is to add the Catalyst 2950 or 3550 switch to the cluster. You can then see any cluster candidates connected to it.
•
Layer 3 CPU packets from a SPAN-source port configured to monitor transmitted traffic are not mirrored to the SPAN-destination port on a Catalyst 2950 switch.
There is no workaround.
•
If a stack contains Catalyst 3550, 3500 XL, or 2900 XL switches, then the cross-stack UplinkFast (CSUF) feature does not work if the management VLAN on these switches is changed to a VLAN other than VLAN 1.
The workaround is to ensure that the management VLAN of all the Catalyst 3550, 3500 XL, and 2900 XL switches in the stack is set to VLAN 1.
•
In some network topologies, when UplinkFast is enabled on all Catalyst 2950 switches and BackboneFast is not enabled on all switches, a temporary loop might be caused when the STP root switch is changed.
The workaround is to enable BackboneFast on all switches.
•
At times, the Window-XP pop-up window might not appear while authenticating a client (supplicant) because the user information is already stored in Windows XP. However, the Extensible Authentication Protocol over LAN (EAPOL) response to the switch (authenticator) might have an empty userid that causes the 802.1X port to be deauthenticated.
The workaround is to manually re-initiate authentication by either logging off or detaching the link and then re-connecting it.
•
The ip http authentication enable global configuration command is not saved to the configuration file because this is the default configuration. Therefore, this configuration is lost after a reboot.
The workaround is to manually enter the command again after a reboot.
•
In the CMS topology view, icons for the fiber-optic, ATM, and FDDI links are not visible.
There is no workaround.
•
A Catalyst 2950 command switch running IOS Release 12.1(6)EA2 cannot use the rcommand privileged EXEC command to start a Telnet session on a Catalyst 3550 member running
IOS Release 12.1(4)EA1, when the aaa authorization exec default group tacacs+ global configuration command is configured on both the command switch and the member.The workaround is to upgrade the Catalyst 3550 switch to IOS Release 12.1(6)EA1a.
•
The Catalyst 2950 command switch might not show the Catalyst 1900, Catalyst 2820, and Catalyst 2900 XL 4-MB (models C2908-XL, C2916M-XL, C2924C-XL, and C2924-XL) switches as candidates even though their management VLAN is the same as the command switch. This occurs only when their management VLAN is not VLAN 1.
There is no workaround.
•
There might be a link on the Fast Ethernet port of the Catalyst 2950switch when it is forced to 10 Mbps and full-duplex mode and its link partner is forced to 100 Mbps and forced duplex mode. The LED on the Catalyst 2950 switch might display the link, and the error counters might increment.
The workaround is to configure both sides of a link to the same speed or use auto-negotiation.
•
The receive count output for the show controllers ethernet-controller interface-id privileged EXEC command shows the incoming packets count before the ASIC makes a decision of whether to drop the packet or not. Therefore, for ports in the STP blocking states, even though the receive count shows incoming frames, the packet is not forwarded to the other port.
There is no workaround.
•
A Catalyst 2950 command switch can discover only the first Catalyst 3550 switch if the link between the Catalyst 3550 switches is an 802.1Q trunk and the native VLAN is not the same as the management VLAN of the Catalyst 2950 switch or if the link between the Catalyst 3550 switches is an ISL trunk and the management VLAN is not VLAN 1.
The workaround is to connect Catalyst 3550 switches by using the access link on the command switches management VLAN or to configure an 802.1Q trunk with a native VLAN that is the same as the management VLAN of the command switch.
•
If two Catalyst 2950 switches are used in a network and if access ports are used to connect two different VLANs whose VLAN IDs are separated by the correct multiple of 64, it is possible to create a situation where the two switches use the same bridge ID in the same spanning-tree instances. This might cause a loss of connectivity in the VLAN as the spanning tree blocks the ports that should be forwarding.
The workaround is to not cross-connect VLANs. For example, do not use an access port to connect VLAN 1 to VLAN 65 on either the same switch or from one switch to another switch.
•
On a Catalyst 2950 switch, the Multicast VLAN Registration (MVR) receiver port joins only 255 groups when the Internet Group Management Protocol (IGMP) join message is sent to all 256 MVR groups configured. Multicast data for the 256th group is not received.
The workaround is to set the mode to dynamic for Catalyst 2950 switches that are connected to IGMP-capable devices. Then, MVR members can join any group but can only support 255 IP multicast streams at any given time.
•
A source-based distribution port group does not share the broadcast with all the group members. When the destination of the packets is a broadcast or unknown unicast or multicast, the packets are forwarded only on one port member of a port group, instead of being shared among all members of the port group.
There is no workaround.
•
Two problems occur when the Catalyst 2950 switch is in transparent mode:
–
–
There is no workaround.
•
Internal loopback in half-duplex mode causes input errors. We recommend that you configure the PHY to operate in full duplex before setting the internal loopback.
There is no workaround.
•
When the Catalyst 2950 switch boots up without being configured, it prompts the user with a configuration dialog. The switch allows the user to omit the dialog and to enable traps without configuring a community string. If the host trap receiver is configured without defining the community strings, when the switch attempts to generate a trap, it fails and displays an error message.
The workaround is to follow the configuration sequence by creating a community string before configuring traps for the host.
•
Aging of dynamic addresses does not always occur exactly after the specified aging time elapses. It might take up to three times this time period before the entries are removed from the table.
There is no workaround.
•
If any VLAN other than VLAN 1 is configured as the management VLAN, the switch reports an incorrect shutdown for VLAN 1. VLAN 1 is not administratively down, even though the running configuration has shut down in VLAN 1.
There is no workaround.
•
The UniDirectional Link Detection (UDLD) protocol does not always detect a unidirectional link when there is a loop between the TX and RX strands on the same port (TX/RX loop condition).
This is an intermittent problem, and there is no workaround.
•
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.
•
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 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.
To avoid a possible conflict, either set the system time for the entire cluster on the command switch, or configure NTP on the command switch to use an NTP server to provide time to the cluster. Do not use both methods at the same time.
•
You can use Cluster Manager to configure an Hot Standby Router Protocol (HSRP) standby group and bind it to a cluster. However, you cannot use Cluster Manager to configure more than one standby group. If you want to configure more than one standby group, use the CLI.
There is no workaround.
•
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.
•
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.
•
HSRP does not support a virtual MAC address entry or a built-in address (BIA) for a cluster.
There is no workaround.
•
All members of an HSRP standby group must be cluster members.
There is no workaround.
•
If the storm control filter is enabled for unicast or multicast traffic and the rising threshold is reached, all traffic on the port is filtered. No unicast, multicast, or broadcast traffic is forwarded from the port.
There is no workaround.
•
Cisco IOS does perform some checks on entered IP addresses. For example, it does not allow the broadcast address to be entered. However, it does not check for the broadcast address on the same subnet as the HSRP Versatile Interface Processor (VIP) or the management VLAN IP address. This means that you could configure HSRP with a virtual IP address that is the same as the network broadcast address.
There is no workaround.
•
If you use the command switch Domain Name System (DNS) server name to start CMS for a member that is running an earlier software release, CMS might not display the switch image, or it might display the command switch image. This can also occur when a standby group is configured for a cluster and you access CMS by entering the command-switch IP address and not the virtual IP address.
The workaround is to always use the command-switch IP address to access CMS. If a standby group is configured for a cluster, always use the virtual IP address to access CMS.
•
If you click the list of switches in CMS and press the Page Down key on the keyboard, the entire list moves to the bottom of the window. This only happens with Windows NT.
The workaround is to collapse the list into a single icon, which returns the list to the top of the window.
Resolved Caveats
These problems were resolved in IOS Release 12.1(9)EA1:
•
If the link between two switches is up and PAgP is configured on both switches, traffic is now forwarded correctly.
•
In the show interfaces command output, the interface status is no longer inconsistent when the switch boots or when a link is up or down.
•
When you are using the AVVID Voice Wizard in CMS, cluster members no longer fail if the client PC or workstation running CMS is not connected to the cluster through the command switch.
•
On the Catalyst 2950 switches, you can now monitor incoming traffic on multiple ports by using CMS.
•
If more than 14 interfaces are added to a multicast static MAC address, the switch no longer loses the entire entry after a reload.
•
If the MVR query-response time on an MVR receiver port is set to the default value (0.5 seconds), when the receiver port leaves a multicast group and rejoins it, the receiver port now sends or receives traffic in less than 10 seconds.
•
If you configure an SNMP community string larger than 123 characters and then configure a VLAN with an ID greater than 99, the Catalyst 2950 switch no longer resets and restarts.
These problems were resolved in IOS Release 12.1(6)EA2c:
•
When a switch boots and CDP is disabled, the switch no longer sends CDP information.
•
In an UplinkFast network topology, the time needed to transition the port state is now correct.
•
Forwarding notifications are no longer lost after a reload when spanning tree is disabled in VLANs other than VLAN 1.
•
When IGMP snooping is enabled on the Catalyst 2950 switch, the Enhanced Interior Gateway Routing Protocol (EIGRP) packets are flooded to all the ports in the 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.
•
If a non-existent VLAN is configured as the MVR VLAN, the switch no longer reloads when it receives IGMP reports for the MVR group on a receiver port.
•
When a cluster of Catalyst 2950 switches is powered on with STP UplinkFast enabled, it no longer creates a spanning-tree loop.
•
When a topology change occurs, all the multicast MAC entries and the multicast router port entries are no longer deleted.
•
When there is a link failure between two Fast Ethernet ports on two Catalyst 2950 switches, the fail-over now works correctly. The MAC address is relearned on the secondary channel when the primary channel fails.
•
When you enter the show running-config or write memory privileged EXEC command, it no longer takes up to 8 seconds before the current configuration appears on the Catalyst 2950 switch.
These problems were resolved in Cisco IOS Release 12.1(6)EA2b:
•
An error can occur with management protocol processing. Please use the following URL for further information:
http://www.cisco.com/pcgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdw65903
•
A command switch no longer fails when it receives SNMP packets that have invalid variable bindings.
This problem was resolved in Cisco IOS Release 12.1(6)EA2a:
•
When you are using the Remote Authentication Dial-In User Service (RADUIS) client for Extensible Authentication Protocol (EAP) authentication, the Microsoft Windows2000 Internet Authentication Server authenticates only users with valid passwords.
These problems were resolved in Cisco IOS Release 12.1(6)EA2:
•
If you are copying the configuration file using ciscoConfigCopyMIB from a Catalyst 2950 switch by using Simple Network Management Protocol (SNMP) manager, the switch no longer reloads the configuration.
•
A broadcast storm no longer occurs when two 100BASE-FX ports on a Catalyst 2950 switch are connected to the 100BASE-FX ports on another Catalyst 2950 switch if these ports are in trunk mode and one of the ports is administratively down.
•
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 output.
•
When you enter the show rmon history user EXEC command, the value for the collision is now unique for each sample.
•
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.
•
The clear counters and clear counters fastethernet port interface configuration 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.
•
The output count displayed by the show interface privileged EXEC command output now appears correctly when the count is greater than 4,294,967,296 packets.
•
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 you change the privilege level for an interface on the Catalyst 2950 switches, 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.
•
If the Catalyst 2950 switch contains multicast addresses, the MIB walk of Dot1dTpFdbEntry no longer takes excess CPU cycles on the switch.
•
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 now resumes.
•
The no snmp-server enable traps snmp [authentication] global configuration command is not supported by this software release.
•
The 100BASE-FX ports in a Fast EtherChannel port group no longer loop packets when the connected device resets or reloads.
•
The SNMP walk of the Dot1dTpFdbTable no longer causes the switch to halt and put an SNMP CPU HOG error message in the logging buffer.
•
SNMP MIB variables etherStatsEntry does not display any values in Cisco IOS Release 12.0(5)XU or later.
•
When IGMP packets are received on a port for a non-existent VLAN, the Catalyst 2950 switch no longer loses buffer space on that port.
•
If you shut down the management VLAN on VLAN 1 on a Catalyst 2950 switch, set the management VLAN to 999, and then again use the shutdown command to shut down VLAN 1, the IP address of VLAN 999 now appears correctly in the show cdp neighbor detail command output on a connected device.
•
When a MAC address is learned on a member of a port group created between a Catalyst 2950 and Catalyst 2900 or 3500 XL switch, the same MAC address gets deleted and relearned on another port member of the port group on the Catalyst 2900 or 3500 XL switch. As a result, a real-time diagnostic message reporting this address relearning behavior no longer appears.
Documentation Updates
You can access all Catalyst 2950 documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/index.htm
This section provides updates to the product documentation. These changes will be included in the next version of the documentation.
Modifications
Encrypted Secure Shell (SSH), described in Chapter 7, "Administering the Switch," in the Catalyst 2950 Desktop Switch Software Configuration Guide, is not available is this release.
Errors
This information corrects errors in the Catalyst 2950 Desktop Switch Hardware Installation Guide.
•
•
•
Related Documentation
These documents provide complete information about the switch and are available from this Cisco.com site:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/index.htm
The software documents are not shipped with the product, but you can access them under the appropriate IOS software release on Cisco.com. You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the "Obtaining Documentation" section.
These publications provide more information about the switches:
•
•
•
•
•
•
•
•
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
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 Cisco.com, you can submit technical comments electronically. Click the Fax or Email option under the "Leave Feedback" at the bottom of the Cisco Documentation home page.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: 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 by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
•
•
•
•
•
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•
•
•
•
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documentation listed in the "Related Documentation" section.
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
Guest
