 Feedback
|
Table Of Contents
Release Notes for the Catalyst 2950 LRE Switches for Cisco IOS Release 12.1(11)YJ1
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 LRE Switch
Recovering from Software Failure
Configuring for an LRE Upgrade
Global Configuration of LRE Upgrades
Controller Configuration of LRE Upgrades
Setting Up the Catalyst 2950 Initial Configuration
Open Cluster Configuration Caveats
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
Catalyst 2950G-24-EI-DC Service Requirement
Modifications to the Catalyst 2950 Desktop Switch Hardware Installation Guide
Obtaining Technical Assistance
Release Notes for the Catalyst 2950 LRE Switches for Cisco IOS Release 12.1(11)YJ1
January, 2003
The Cisco IOS Release 12.1(11)YJ1 runs on Catalyst 2950 Long-Reach Ethernet (LRE) switches. Cisco IOS Release 12.1(11)EA1, intended for non-LRE Catalyst 2950 switches, should not be installed on Catalyst 2950 LRE 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.
•
•
For the complete list of Catalyst 2950 switch documentation, see the "Related Documentation" 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 (previously Cisco Connection Online [CCO]) in the Cisco IOS software area.
Note
Contents
These release notes contain the following sections:
•
•
•
System Requirements
The following sections describe system requirements:
Hardware Supported
The Catalyst 2950 LRE switches are supported by the Cisco IOS 12.1(11)YJ1 release. The YJ1 release is for managing Catalyst 2950 LRE switches and LRE customer premises equipment (CPE) devices.
Table 1 lists the hardware supported by this release:
Hardware Not Supported
Table 2 lists the hardware that is not supported by this release:
Table 2 Hardware Not Supported
Catalyst 2950-12
12 fixed autosensing 10/100 Ethernet ports
Catalyst 2950-24
24 fixed autosensing 10/100 Ethernet ports
Catalyst 2950C-24
24 fixed autosensing 10/100 Ethernet ports and 2 100BASE-FX ports
Catalyst 2950G-12-EI
12 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots
Catalyst 2950G-24-EI
24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots
Catalyst 2950G-24-EI-DC
24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots with DC-input power
Catalyst 2950G-48-EI
48 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots
Catalyst 2950SX-24
24 fixed autosensing 10/100 Ethernet ports and 2 1000BASE-SX ports
Catalyst 2950T-24
24 fixed autosensing 10/100 Ethernet ports and 2 10/100/1000 Ethernet ports1
Gigabit Interface Converter (GBIC) modules
•
•
•
•
•
•
•
Redundant power system
Cisco RPS 600 Redundant Power System
1 The 10/100/1000 ports operate only in full-duplex mode.
Software Compatibility
The following sections describe the 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 or higher
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.75 or 6.2
5.5 or 6.0
Windows 98
Second Edition
4.75 or 6.2
5.5 or 6.0
Windows NT 4.0
Service Pack 3 or later
4.75 or 6.2
5.5 or 6.0
Windows 2000
None
4.75 or 6.2
5.5 or 6.0
Windows XP
None
4.75 or 6.2
5.5 or 6.0
Solaris 2.5.1 or later
Sun-recommended patch cluster for the OS and Motif library patch 103461-24
4.75 or 6.2
Not supported
1 Netscape Communicator version 6.0 is 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 XP, Windows 2000, Windows 95, Windows 98, and Windows NT 4.0 Plug-Ins" section and the "Solaris Plug-Ins" 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
On McAfee VirusScan, from the Start menu, to disable the VirusScan Internet Filter option, the Download Scan option, or both, select 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 XP, Windows 2000, Windows 95, Windows 98, and Windows NT 4.0 Plug-Ins
These Java plug-ins are supported in the Windows environments:
•
•
•
You can download these plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
Solaris Plug-Ins
These Java plug-ins are supported on the Solaris platform:
•
•
•
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.
Table 5 Switch Software and Cluster Capability
Catalyst 3550
Release 12.1(4)EA1 or later
Member or command switch
Catalyst 3500 XL
Release 12.0(5.1)XU or later
Member or command switch
Catalyst 2950
Release 12.0(5.2)WC(1) or later
Member or command switch
Catalyst 2950 LRE
Release 12.1(11)YJ or later
Member or command switch
Catalyst 2900 XL (8-MB switches)
Release 12.0(5.1)XU or later
Member or command switch
Catalyst 2900 XL (4-MB switches)
Release 11.2(8.5)SA6 (recommended)
Member switch only1
Catalyst 1900 and 2820
Release 9.00(-A or -EN)
Member switch only
1 Catalyst 2900 XL (4-MB) switches appear in the front-panel and topology views of CMS. However, CMS does not support configuration or monitoring of these switches.
Some versions of the Catalyst 2900 XL software do not support clustering, and if you have a cluster with switches that are running different versions of 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.1(11)YJ or later.
Note
Downloading Software
This section contains the following sections:
•
•
•
•
For information about the software releases that support the Catalyst 2950 LRE switches, see the "Limitations and Restrictions" section.
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 for this release.
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:). (The HTML and LRE binaries are located in the same directory as the IOS binary.)
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 EI or Running Standard Image if you are running the SI.
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.
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 download-sw command.
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:
•
•
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.
Downloading the Software and TFTP Server Application
This procedure is for copying the combined .tar file to the Catalyst 2950 LRE switches. 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 files, select Download Cisco Catalyst 2950 LRE 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
The changes you make to a switch configuration 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 LRE Switch
This procedure is for upgrading Catalyst 2950 LRE switches by using the archive download-sw privileged exec command to automatically extract and download the images to the switch. The archive download-sw command automatically deletes the old version and copies the new version to Flash if the Flash does not have space to store the old and new versions simultaneously. The archive download-sw command initiates this process:
•
•
•
•
•
For further information on this command, see the command reference for this release .
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
Step 7
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.
Recovering from Software Failure
If the software fails, you can reload it. For detailed recovery procedures, refer to the "Troubleshooting" chapter in the Catalyst 2950 Desktop Switch Software Configuration Guide for this release.
Upgrading LRE Switch Firmware
The Catalyst 2950 LRE switches can store and properly apply LRE binaries if in the future there are updates required to the firmware on the switches' local LRE controllers or connected CPE devices.
Other upgrade-related features include:
•
•
Note
You perform an upgrade with this command:
hw-module slot x upgrade lre [force][local lo n | remote lo x/y]
Automatic upgrading is not supported. You can upgrade in one of these ways:
•
•
•
Note
Configuring for an LRE Upgrade
In the absence of any LRE Upgrade configurations, the LRE upgrade attempts to upgrade all local LRE controllers and CPE devices to the most recent compatible versions of the LRE binaries required for each LRE target device. LRE upgrade configurations should rarely be required. The primary purpose of LRE upgrade configuration commands is to provide for downgrades of LRE binaries.
If you wish to override the switch's automatic selection of LRE binaries, you have two methods available:
•
•
You can use config global commands to specify the LRE binary or binaries for a specified target type. (A target type is the family [and optionally the model or model revision] of a device containing one or more upgradable hardware elements.) A target can be a local LRE controller on the switch or a remote CPE device.
You can perform global LRE upgrade configurations by issuing LRE upgrade controller configuration commands from the controller configuration mode. You can use the upgrade configuration command in the controller mode to override the system default selection of an LRE binary to be applied on a particular remote CPE device or local LRE controller. Controller configurations take precedence over global upgrade configurations.
The preserve keyword causes the LRE upgrade mechanism to not upgrade the local controller on which preserve is configured or any of the CPE devices connected to that controller. If you want to preserve (in other words, not upgrade) some of the CPE devices connected to a particular controller but allow upgrades to others, you can enter controller upgrade configuration commands for the links that you want to upgrade.
The no form of the upgrade command removes the command for applying a particular LRE binary. To resume default upgrade behavior for a given controller, configure the no upgrade commands on that controller.
Note
Note
For further details, see pages for the upgrade commands in the Catalyst 2950 Desktop Switch Command Reference for this release.
Performing an LRE Upgrade
You can upgrade either on a system-wide basis (in other words, upgrading the software on all connected CPE devices and local LRE chipsets) or on individual CPE device or LRE controllers. By default, a system-wide upgrade applies the most recent versions of LRE binaries that are most compatible with each upgradable hardware module. The system-wide upgrade method is the one that you use in almost all situations.
When executing upgrades, you can elect to upgrade a single CPE device or local controller by using this command hw-module slot <x> upgrade lre [local lo n | remote lo x/y]. If no local or remote option is given, a system-wide upgrade is performed.
Global Configuration of LRE Upgrades
Beginning in privileged EXEC mode, follow these steps to perform a system-wide upgrade to configure the LRE binary to apply to a target device and upgradable hardware element combination:
Note
Controller Configuration of LRE Upgrades
Beginning in privileged EXEC mode, follow these steps to explicitly direct the LRE binaries to be applied to either the local controller or a specific VDSL link:
You can use the upgrade configuration command in the controller mode to override the system default selection of an LRE binary that will be applied on either end of a particular LRE link. Controller configurations take precedence over global upgrade configurations.
The preserve keyword causes the LRE upgrade mechanism to not upgrade the local controller on which preserve is configured or any of the CPE devices connected to that controller. If you want to preserve (in other words, not upgrade) some of the CPE devices connected to a particular controller but allow upgrades to others, you can enter controller upgrade configuration commands for the links you want to upgrade.
The no form of the command removes the command for applying a particular LRE binary. To resume default upgrade behavior for a given controller, do not configure the custom upgrade commands on that controller.
LRE Upgrade Behavior Details
You see on the console screen when you start an upgrade:
Switch>enSwitch#hw-module slot 0 upgrade lreYou are about to start an LRE upgrade on all LRE interfaces.Users on LRE links being upgraded will experience a temporary disruption of Ethernet connectivity.Start LRE upgrade ? [yes]:If you answer yes or press the Enter key, the upgrade starts. If you answer no, you get the EXEC prompt.
You can expect this link behavior of the CPE device during an upgrade:
•
•
•
•
•
LRE Upgrade Example
This is an example of how an LRE upgrade can proceed:
Switch#hw-module slot 0 upgrade lre force remote lo 0/1You are about to start an LRE upgrade on CPE Lo0/1.Users on LRE links being upgraded will experience a temporarydisruption of Ethernet connectivity.Start LRE upgrade ? [yes]:Starting remote upgrade on CPE Lo0/1Switch#00:21:51: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceLongReachEthernet0/1, changed state to downThe CPE device is reset and the link is down. Ethernet connectivity is unavailable at this point.
00:22:37: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to up00:22:39: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceLongReachEthernet0/1, changed state to upThe CPE device finishes resetting. Ethernet connectivity is available but at low speeds. Upgrade data transfer begins.
00:23:55: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceLongReachEthernet0/1, changed state to downUpgrade data transfer is complete. Reset the CPE device.
00:23:56: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to upThe CPE device finishes resetting. The desired profile is applied.
00:23:58: %LRE_LINK-3-UPDOWN: Interface Lo0/1, changed state to UP00:23:59: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to up00:24:02: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceLongReachEthernet0/1, changed state to upOperation resumes in the profile link-up state.
Switch#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 for this release), or by manually assigning an IP address (refer to the Catalyst 2950 Desktop Switch Software Configuration Guide for this release).
This section contains the following sections:
•
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 myline vty 0 15password my_passwordsnmp-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:
•
•
Accessing CMS
Before using the web-based CMS tools, see the "Software Compatibility" section and the "Installing the Required Plug-In" section to set up the appropriate browser options. 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.
Note
The browser prompts for a username and password when you access CMS:
•
•
Configuring the HTTP Server
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
After you have configured the HTTP server interface, display the CMS access page as described in the "Displaying CMS" section.
Displaying CMS
To display the CMS access page, follow these steps:
Step 1
Step 2
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 for this release.
Step 3
When you access CMS from a standalone or a cluster-member switch, Device Manager appears.
New Software Features
Release 12.1(11)YJ1 contains these new features or enhancements:
•
•
•
•
•
•
•
•
•
•
–
–
–
•
–
–
•
•
•
•
•
•
•
•
Limitations and Restrictions
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.
This section contains the following sections:
Immediate-Leave Limitation
When the Internet Group Management Protocol (IGMP) Immediate-Leave is configured, new ports are added to the group membership each time a join message is received, and ports are pruned (removed) each time a leave message is received.
If the join and leave messages arrive at high rate, the CPU can become busy processing these messages. For example, the CPU usage is approximately 50 percent when 50 pairs of join and leave messages are received each second. Depending on the rate at which join and leave messages are received, the CPU usage can become very high, even up to 100 percent, as the switch continues processing these messages.
The workaround is to use the Immediate-Leave processing feature only on VLANs where a single host is connected to each port. (CSCdx95638)
RSPAN Limitation
In a Remote Switched Port Analyzer (RSPAN) session, if at least one Catalyst 2950 switch is used as an intermediate or destination switch and if traffic for a port is monitored in both directions, traffic does not reach the destination switch. (CSCdy38476)
These are the workarounds:
•
•
Guidelines for Applying ACLs
Follow these guidelines for applying access control lists (ACLs) to interfaces:
•
•
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
Yes
No
Yes
Yes
-
No
Yes
Yes1
Yes
No
No
No
-
Yes
Yes
No
Yes
Yes
Yes
Yes
-
Yes
-
Yes
Yes
Yes1
Yes1
Yes
-
-
No
No
Yes
No
-
-
-
1 Switched Port Analyzer (SPAN) cannot operate if the monitor port or the port being monitored is not a protected port.
SPAN Limitation
When using the SPAN feature, the monitoring port receives copies of sent and received traffic for all monitored ports. If the monitoring port is oversubscribed, it will probably become congested. This might also affect how one or more of the monitored ports forwards traffic.
Important Notes
This section describes important information related to this IOS release. These sections are included:
CMS Notes
This section contains the following information:
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 data is not displayed, and an error message appears when these switches are running these software releases:
•
•
•
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 a Long-Reach Ethernet (LRE) switch, the customer premises equipment (CPE) devices 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 "Upgrading LRE Switch Firmware" section.
Configuring CMS
These notes apply to the CMS configuration:
•
•
•
•
Resize the browser window again when CMS is not busy.
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.
Open Non-LRE Caveats
This sections contains the following non-LRE open caveats in this release:
•
Open IOS Caveats
These are the severity 3 IOS configuration caveats:
•
If a stack that has Catalyst 2950 switches also has Catalyst 2900 XL or Catalyst 3500 XL switches, cross-stack UplinkFast (CSUF) does not function if the management VLAN on the Catalyst 2900 XL or Catalyst 3500 XL switches is changed to a VLAN other than VLAN 1 (the default).
The workaround is to make sure that the management VLANs of all Catalyst 2900 XL or 3500 XL switches in the stack are set to VLAN 1.
•
When you use the policy-map global configuration command to create a policy map, and you do not specify any action for a classmap, the association between that class map and policy map is not saved when you exit policy-map configuration mode.
The workaround is to specify an action in the policy map.
•
The default VLANs cannot be removed from the allowed list on a trunk port, and only one management VLAN can be active at a time.
Note
The workaround is to have only one active management VLAN at a time.
•
A switch does not use the default gateway address in the DHCP offer packet from the server during automatic-install process.
The workaround is to manually assign an IP address to the switch.
•
A Secure Shell (SSH) session does not terminate when the underlying transport is lost.
The workaround is to use the disconnect ssh command to terminate the SSH session.
•
Assigning a non-existant VLAN identifier to a static access port-channel or EtherChannel by setting the ciscoVlanMembershipMIB:vmVlan object does not automatically create the VLAN in the VLAN database.
There is no workaround.
•
If you issue a write configuration to NVRAM from a subdirectory, the configuration file is written in that subdirectory, causing the save configuration to not be applied when the switch is rebooted.
The workaround is use the pwd command to verify that the current directory is the root directory before writing configuration to the NVRAM.
•
The Address Resolution Lookup (ARL) entries of the MAC table do not always timeout exactly after the specified aging time elapses. It can take up to three times this time period before the entries are removed from the table.
There is no workaround.
•
The speed and duplex parameters for Gigabit Ethernet ports can be modified and effective only when the copper link is active. You cannot modify these parameters from the Port Settings dialog in CMS.
The workaround is to use command line interface to perform this configuration.
•
CMS does not work when a switch is running the crypto software image, and the virtual terminal (VTY) lines have been configured to use only SSH by using the transport input ssh line vty 0 15 interface configuration command.
The workaround is to allow SSH and Telnet access through the VTY lines by using the transport input ssh telnet interface configuration command.
•
The show version command displays only the first 75 characters of the system image filename.
There is no workaround.
•
If two switch ports in two different VLANs are connected to each other, both switch ports continue forwarding. If two additional ports in the two different VLANs are connected together, a loop is formed.
The workaround is to remove the loop from the switch.
•
When you set the c2900PortUseageApplication object value in the CISCO-C2900 MIB, to monitor, portgroupDest, portGrouping, network, or networkGroup, the setting is rejected.
The workaround for the monitor keyword is to use the CLI to configure a SPAN session.
The workaround for the portGroupDest and portGrouping values is to use the EtherChannel CLI commands to configure load balancing.
There are no workarounds for the network and networkGroup values. These are unsupported values.
•
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 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.
•
Layer 3 CPU packets from a SPAN-source port configured to monitor sent 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 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 Windows 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 user ID 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.
•
A Catalyst 2950 command switch running 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 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 2950 switch 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 Ethernet interface 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.
•
When changing the management VLAN on a cluster with command-switch redundancy enabled, the cluster can break if Hot Standby Router Protocol (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.
Open Cluster Configuration Caveats
These are the severity 3 cluster caveats in this release:
•
When a Catalyst 2950 cluster command switch is running 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 a Catalyst 2950 switch is the cluster 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 cluster command switch is one of the following, 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.
•
You can use Cluster Manager to configure a 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.
Open CMS Caveats
These are the severity 3 CMS configuration caveats:
•
You cannot switch modes (for example, from Guide Mode to Expert Mode) for an open CMS window.
The workaround is to close the open window, select the mode that you want, and then reopen the CMS window.
Note
•
In read-only mode, time ranges are not displayed. See the "CMS Notes" section for more information about CMS modes.
There is no workaround.
•
If you try to create a time-range entry that specifies multiple days with the same time, the CMS displays only the first day in the list of days. This is an example of such a time-range entry:
periodic Monday Wednesday Friday 8:00 to 17:00.The periodic time-range entries with specific days use this syntax:
periodic Monday 8:00 to Tuesday 17:00.or
periodic Monday 8:00 to Monday 17:00The workaround is to create a specific time-range entry for each day.
•
The data that is displayed by using the Stack Bar and Stack Area options in the Link Graph window is incorrect.
The workaround is to use the Line, Bar, or Area options instead.
•
You cannot add a switch that does not have Terminal Access Control Access System Plus (TACACS+) configured on it to a cluster if all the other cluster members are configured with TACACS+.
The workaround is to configure TACACS+ on the switch before adding it to the cluster.
•
A red border appears around the text-entering area of some CMS dialogs. The color of the border changes to green when text is entered. This is only a cosmetic error. The colored border does not prevent you from entering text.
There is no workaround.
Note
•
When there are no CMS windows open, the CMS keyboard shortcuts do not work.
The workaround is to leave one CMS window open. For example, leave the Help > About window open.
•
When a Catalyst 2950 switch becomes a command switch, it automatically creates an IP extended ACL called CMP-NAT-ACL that specifies a set of IP addresses subject to cluster-NAT address translation. Although CMS allows you to modify or delete this ACL, do not modify or delete this ACL.
There is no workaround.
•
The cursor is not displayed in the text-entering areas in CMS. However, in some cases you can still enter text. This problem occurs with certain combinations of both the browser and the Java plug-in. For example, it can occur when Netscape Communicator 6.2.3 is used with Java Plug-In 1.3.1_02 or 1.3.1_03.
These are the two workarounds:
–
–
•
You cannot add a class to a new policy when you launch Device > QoS > Policies in Guide Mode.
The workaround is to launch Device > QoS > Policies in Expert Mode, and then add the class to the policy.
•
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.
•
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 than the command switch, 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.
•
In the CMS topology view, icons for the fiber-optic, ATM, and FDDI links are not visible.
There is no workaround.
Open LRE Caveats
These are the LRE caveats in this release:
•
VLAN-tagged packets from multiple VLANs with the same source MAC address received on different Cisco 585 LRE CPE Ethernet ports create a single MAC address (ingress port entry). Any network designed with the assumption that MAC addresses are maintained per VLAN does not work.
There is no workaround; the Ethernet switch on the Cisco 585 LRE CPE does not support VLANs. All the ports are assumed to be in the same VLAN.
•
Maximum-sized ISL frames (frames between 1537 and 1544 bytes) are discarded by the CPE device on ingress. Some chips and switches on the CPE device support a maximum frame size of 1536 bytes, which causes any maximum-sized ISL frames coming into the CPE from an end device or from an LRE switch to be discarded.
There is no workaround. You must ensure that the network does not send ISL tagged frames of sizes between 1537 and 1544 bytes to an LRE switch.
•
The system runs out of memory and fails after too many RMON buckets are requested.
There is no workaround; only 1000 buckets per interface are supported.
•
The flow control auto-negotiation settles in the incorrect outcome if you use a Cisco-made 1000BASE-T GBIC with any switch not listed in the Table 1 of the 1000BASE-T GBIC Switch Compatibility Matrix: http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/1000gbic/1000comp.htm.
The workaround is to use the Cisco 1000BASE-T GBIC only with compatible switches.
•
The Flash write operation is slower on LRE switches than on non-LRE switches.
There is no workaround.
•
If a Gigabit Ethernet interface that was part of an EtherChannel is set to be the destination interface of a SPAN monitoring session, the Gigabit Ethernet interface line protocol remains down and suspended from the EtherChannel after the SPAN monitoring session is removed.
The workaround is to issue the shutdown command followed by the no shutdown command on the Gigabit Ethernet interface, which makes the port active and reincludes it into the EtherChannel.
•
The Cisco 585 LRE CPE has 4 Fast Ethernet ports. When connected to an LRE switch, the default value for the maximum number of secure MAC addresses is 1. (You can use the show port-security command to display the current maximum value.)
The workaround is to use the switchport port-security maximum <value> interface configuration command to change the default value. For interfaces connected to Cisco 575 LRE CPEs, the default value of 1 is sufficient. For interfaces connected to Cisco 585 LRE CPEs, the value can be changed to 5, because the CPE has 4 Fast Ethernet ports and one additional MAC address for internal purposes.
•
In an LRE switch, the messages sent to the syslog servers have two timestamps.
There is no workaround.
•
The Cisco 575 LRE CPE does not support all of the Fast Ethernet statistics displayed by the show controllers ethernet-controller longReachEthernet 0/4 cpe command. (The Cisco 585 LRE CPE supports all the LRE and CPE Fast Ethernet statistics.)
There is no workaround. These CPE Fast Ethernet statistics are supported by the Cisco 575 LRE CPE:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
The copper physical entry is not included when the entPhysicalTable object is retrieved.
There is no workaround needed.
•
When an 802.1X client connected to a Cisco 575 LRE CPE has been authorized by a Catalyst 2950 LRE switch to connect to a port, if the Ethernet link between the Cisco 575 LRE CPE and the client drops, the switch does not mark that port as unauthorized.
The workaround is to use the shut interface configuration command followed by the no shut interface configuration command to force an LRE link transition. You can also configure dot1x on the switch to perform periodic authentication of the client. Use the configuration command dot1x re-authentication interface configuration command, and then set the time period between re-authentication attempts with the dot1x timeout re-authperiod <CmdArg> seconds interface configuration command.
•
When a 802.1X protocol enabled client attempts to connect to a Catalyst 2950 LRE switch with dot1x configured on a port, the client cannot be authenticated. The CLI show dot1x interface interface configuration command displays the port state as unauthorized.
There is no workaround.
•
The Gigabit Ethernet ports of a Catalyst 2950 LRE switch might get into err-disable states when the plastic SFPs are first installed.
The workaround is to enter the shutdown followed by the no shutdown interface configuration commands.
Resolved Non-LRE Caveats
This section contains the non-LRE resolved IOS caveat in this release.
This IOS caveat was resolved in Release 12.1(11)YJ1:
•
A security fix prevents incorrectly-formed Secure Shell (SSH) packets from halting a switch.
For more information, refer to this URL:
http://www.cisco.com/warp/public/707/ssh-packet-suite-vuln.shtml
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.
Updated Translated Warnings
These warnings have been updated for this release.
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
Overtemperature Warning
Chassis Power Connection
Catalyst 2950G-24-EI-DC Service Requirement
Modifications to 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
These 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 this URL:
Translated documentation is available at this 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 might be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
•
http://www.cisco.com/public/ordsum.html
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing 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 online 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 with these tasks:
•
•
•
•
•
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
•
•
•
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site 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 this URL:
All customers, partners, and resellers who have a valid Cisco service 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 this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. 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 automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this 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). When you call the center, 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.
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0208R)
Copyright © 2002-2003, Cisco Systems, Inc.
All rights reserved.
