Table Of Contents
Release Notes for the Catalyst 2900 Series LRE XL Switches for Cisco IOS Release 12.0(5)WC7
Browser and Java Plug-In Requirements
Cluster Requirements and Guidelines
Catalyst 2900 XL and Catalyst 3500 XL Switches
Catalyst 1900 and Catalyst 2820 Switches
Minimum Cisco IOS Release for Major Features
Using the spanning-tree portfast Command
Resolved IOS Caveats in Release 12.0(5)WC7
Resolved CMS Caveats in Release 12.0(5)WC7
Resolved LRE Caveats in Release 12.0(5)WC7
Corrections to Software Configuration Guide
Additions to Software Configuration Guide
Correction to Command Reference
Corrections to Hardware Installation Guide
Attaching the Cisco RPS (model PWR300-AC-RPS-N1)
Installing the Required Plug-In
Displaying the CMS Access Page
Upgrading the Switch IOS Software
Guidelines for Upgrading Switch Software
Overview of the Switch Upgrade Process
Determining the Switch Software Version
Which Software Files to Download from Cisco.com
Downloading the New Software and TFTP Server Application to Your Management Station
Copying the Current Startup Configuration from the Switch to a PC or Server
Using CMS to Upgrade One or More Switches
Recovering from an Incomplete CMS Software Upgrade
Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch
Configuring for an LRE Upgrade
Global Configuration of LRE Upgrades
Controller Configuration of LRE Upgrades
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for the Catalyst 2900 Series LRE XL Switches for Cisco IOS Release 12.0(5)WC7
March 2003
Cisco IOS Release 12.0(5)WC7 runs on the Catalyst 2900 series LRE XL switches with 16-MB CPU DRAM.
Note
This release is only for Long-Reach Ethernet (LRE) switches. Do not install this release on Catalyst 3500 XL switches or on Catalyst 2900 XL switches that are not LRE switches.
These release notes include important information about this release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:
•
•
•
You can download the switch software from these sites:
•
(for registered Cisco.com users with a login password)•
(for nonregistered Cisco.com users)This release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Contents
This document has these sections:
•
•
•
•
•
•
•
•
•
•
•
•
•
Hardware Requirements
Note
Note
This software release only supports the 16-MB Catalyst 2900 LRE XL switches (see Table 1). This release also supports the Cisco 575 and 585 LRE CPE (customer premises equipment) devices.
Table 1 Catalyst 2900 LRE XL Switches with 16-MB CPU DRAM
Catalyst 2912 LRE XL
4 10/100 ports and 12 LRE ports
Catalyst 2924 LRE XL
4 10/100 ports and 24 LRE ports
Software Requirements
This section describes the requirements for the system and for the Cluster Management Suite (CMS) software.
System Requirements
These operating systems are supported for CMS management:
•
•
•
•
•
The minimum PC requirement is a Pentium processor running at 233 MHz with 64 MB of DRAM. The minimum UNIX workstation requirement is a Sun Ultra 1 running at 143 MHz with 64 MB of DRAM. Table 2 lists the recommended platforms for using CMS.
Table 2 Recommended Minimum Platform Configuration for Web-Based Management
Windows NT 4.01
Pentium 300 MHz
128 MB
65,536
1024 x 768
Small
Solaris 2.5.1
SPARC 333 MHz
128 MB
Most colors for applications
-
Small (3)
1 Service Pack 3 or higher required
Browser and Java Plug-In Requirements
When starting a CMS session, the switch verifies the browser version to ensure that the browser is supported. If the browser is not supported, an error message appears, and the session does not start. Table 3 lists the browsers supported by CMS.
CMS requires the Java plug-ins described in the "Installing the Required Plug-In" section.
Table 3 Browser Requirements
Windows 95
4.61, 4.7
5.0, or 5.5
Windows 98
-2
5.0, or 5.5
Windows NT 4.0
4.61, 4.7
5.0, or 5.5
Windows 2000
4.61, 4.7
5.0, or 5.5
Solaris 2.5.1 or higher
4.61, 4.7
—3
1 Netscape Communicator version 4.60 and 6.0 are not supported. (CSCdx34982)
2 CMS is not supported on machines running Windows 98 and Netscape Navigator. The workaround is to use Microsoft Internet Explorer if your operating system is Windows 98. (CSCdx4997)
3 Microsoft Internet Explorer is not supported on Solaris 2.5.1 or higher.
Note
To access CMS, follow the procedures in the "Initial Switch Configuration" section.
Cluster Requirements and Guidelines
This section describes the hardware and software requirements for clustering Catalyst desktop switches.
Catalyst 2900 XL and Catalyst 3500 XL Switches
Some versions of switch software do not support clustering, and other versions do not support some of the features in this release. To ensure that all cluster switches are using the same software level, we recommend that you upgrade all cluster switches to the software release that supports the features that you want.
If you have a cluster with switches that are running different versions of switch software, changes on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)XU or later.
Table 4 describes the Catalyst 2900 XL and Catalyst 3500 XL switches supported by this release and shows which switches can be command switches. All switches can function as standalone devices.
All Catalyst 2900 XL and Catalyst 3500 XL switches running Release 12.0(5.3)WC(1) and later are cluster-capable. All Catalyst 2900 XL modules are supported in cluster configurations.
We recommend that either the command switch has the latest software version installed if there switches in the cluster with older software versions or that all switches in the same platform be upgraded to the latest software version.
Note
Table 4 Catalyst 2900 XL and Catalyst 3500 XL Switches as Cluster Members
Catalyst 2900 XL (4 MB of DRAM)1
No
No
Yes
Catalyst 2900 XL (8 MB of DRAM)
Yes
Yes
Yes
Catalyst 2900 LRE XL (16 MB of DRAM)
Yes
Yes
Yes
Catalyst 3500 XL
Yes
Yes
Yes
1 These switches can act as cluster members if they are running Release 11.2(8.x)SA6 original edition software. They can interoperate with this software release, but they cannot be upgraded to it.
Catalyst 3550 Switches
Catalyst 3550 switches running Release 12.0(4)EA1 or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 3550 switches.
Note
Catalyst 2950 Switches
Catalyst 2950 switches running Release 12.0(5)WC(1) or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 2950 switches.
Note
Catalyst 1900 and Catalyst 2820 Switches
Table 5 lists the Catalyst 1900 and Catalyst 2820 switches and the minimum software release that they require to be cluster members. All Catalyst 2820 modules are supported in cluster configurations. For more information, refer to the documentation for the Catalyst 1900 and Catalyst 2820 switches.
Note
Table 5 Catalyst 1900 and Catalyst 2820 Switches as Cluster Members
Catalyst 1900
Yes
Yes
No
Catalyst 2820
Yes
Yes
No
Minimum Cisco IOS Release for Major Features
Table 6 lists the minimum software release required to support the major features of the Catalyst 2900 XL and Catalyst 3500 XL switches.
Table 6 Catalyst 2900 XL (including 2900 LRE XL) and Catalyst 3500 XL Features and the Minimum Cisco IOS Release Required
Bridge protocol data unit (BPDU) filtering
Release 12.0(5)WC7
Rate selection
Release 12.0(5)WC6
LRE switch firmware upgrade capability for the switch local LRE controllers or connected CPE devices
Release 12.0(5)WC6
Interoperability with Catalyst 2950ST-24-LRE and Catalyst 2950ST-8-LRE switches
Release 12.0(5)WC6
Port security MAC address aging
Release 12.0(5)WC5
Bridge protocol data unit (BPDU) guard
Release 12.0(5)WC5
Remote Authentication Dial-In User Service (RADIUS)
Release 12.0(5)WC5
UniDirectional Link Detection (UDLD) recovery
Release 12.0(5)WC5
Support for the Cisco Coarse Wave Division Multiplexing (CWDM) Gigabit Interface Converter (GBIC) modules
Release 12.0(5)WC5
Support for the Cisco 585 LRE CPE device
Release 12.0(5)WC4
Enhanced web-based switch management (CMS)
Release 12.0(5)WC4
MAC Address Notification
Release 12.0(5)WC4
Internet Group Management Protocol (IGMP) Filtering
Release 12.0(5)WC4
Enhanced web-based switch management (CMS)
Release 12.0(5)WC3
MAC address notification
Release 12.0(5)WC3
Internet Group Management Protocol (IGMP) filtering
Release 12.0(5)WC3
WS-C2912-LRE XL and WS-C2912-LRE XL switches with LRE ports and support for the Cisco 575 LRE CPE device
Release 12.0(5.1)WC(1)
Extended cluster member compatibility with the Catalyst 2950 and Catalyst 3550 switches
Release 12.0(5)WC(1)
Multicast VLAN Registration (MVR)
Release 12.0(5)WC(1)
Cross-stack UplinkFast
Release 12.0(5)XW
Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration
Release 12.0(5)XW
Support for the single-port 1000BASE-T GBIC module (WS-G5482)
Release 12.0(5)XW
WS-C3524-PWR XL switch with 10/100 inline-power ports
Release 12.0(5)XU
WS-C2924M-XL-EN-DC switch with DC power connector
Release 12.0(5)XU
WS-X2932-XL Catalyst 2900 XL 1-port 1000BASE-T module
Release 12.0(5)XU
Hot Standby Router Protocol (HSRP) for clustering
Release 12.0(5)XU
Extended discovery of cluster candidates up to 7 hops from the command switch
Release 12.0(5)XU
Support for up to 16 switches in a cluster
Release 12.0(5)XU
VLAN Trunking Protocol (VTP) pruning
Release 12.0(5)XU
Change management virtual LAN (VLAN) for a cluster
Release 12.0(5)XU
Private VLAN edge support
Release 12.0(5)XU
UDLD for detecting unidirectional links
Release 12.0(5)XU
Extended cluster member functionality for Catalyst 1900 and 2820 switches
Release 12.0(5)XP
Remote monitoring (RMON) support through the command-line interface (CLI) or Simple Network Management Protocol (SNMP)
Release 12.0(5)XP
Change management VLAN
Release 12.0(5)XP
Quality of service (QoS) based on IEEE 802.1P class of service (CoS) values
Release 12.0(5)XP
WS-C3548-XL switch with 48 10/100 ports
Release 12.0(5)XP
WS-X2931-XL Catalyst GigaStack GBIC module
Release 12.0(5)XP
Catalyst 3500 series XL switches (except WS-C3548-XL)
Release 11.2(8)SA6
Cluster management
Release 11.2(8)SA6
Terminal Access Control Access System Plus (TACACS+)
Release 11.2(8)SA6 (Enterprise Edition Software)
Network Time Protocol (NTP)
Release 11.2(8)SA6
Spanning Tree Protocol (STP) UplinkFast
Release 11.2(8)SA6
(Enterprise Edition Software)250 VLANs (some models: see the "Limitations and Restrictions" section)
Release 11.2(8)SA6
Catalyst 2900 series XL 1000BASE-X modules
Release 11.2(8)SA5
Catalyst 2900 series XL asynchronous transmission mode (ATM) modules
Release 11.2(8)SA5
IEEE 802.1Q trunking
Release 11.2(8)SA5
(Enterprise Edition Software)Inter-Switch Link (ISL) trunking
Release 11.2(8)SA4
(Enterprise Edition Software)VLAN Membership Policy Server (VMPS)
Release 11.2(8)SA4 (Enterprise Edition Software)
8192 media access control (MAC) addresses on modular switches
Release 11.2(8)SA4
Switch Network View stack management
Release 11.2(8)SA3
Web-based switch management
Release 11.2(8)SA
Fast EtherChannel port groups
Release 11.2(8)SA
New Software Feature
This release supports bridge protocol data unit (BPDU) filtering. BPDU filtering prevents ports that are in a Port Fast-operational state from sending or receiving BPDUs. BPDU filtering is described in these sections:
•
Enabling BPDU Filtering
The BPDU filtering feature can be globally enabled on the switch or can be enabled per interface, but the feature operates with some differences.
At the global level, you can enable BPDU filtering on Port Fast-enabled ports by using the spanning-tree portfast bpdufilter default global configuration command. This command prevents ports that are in a Port Fast-operational state from sending or receiving BPDUs. The ports still send a few BPDUs at link-up before the switch begins to filter outbound BPDUs. You should globally enable BPDU filtering on a switch so that hosts connected to these ports do not receive BPDUs. If a BPDU is received on a Port Fast-enabled port, the port loses its Port Fast-operational status, and BPDU filtering is disabled.
At the interface level, you can enable BPDU filtering on any port without also enabling the Port Fast feature by using the spanning-tree bpdufilter enable interface configuration command. This command prevents the port from sending or receiving BPDUs.
Caution
You can also use the spanning-tree bpdufilter enable interface configuration command to enable BPDU filtering on any port without also enabling the Port Fast feature. This command prevents the port from sending or receiving BPDUs.
Caution
Beginning in privileged EXEC mode, follow these steps to globally enable the BPDU filtering feature:
To disable BPDU filtering, use the no spanning-tree portfast bpdufilter global configuration command.
You can use the spanning-tree bpdufilter enable interface configuration command to re-enable BPDU filtering.
Using the spanning-tree portfast Command
Use the spanning-tree portfast global configuration command to globally enable BPDU filtering on Port Fast-enabled ports, the BPDU guard feature on Port Fast-enabled ports, or the Port Fast feature on all nontrunking ports. The BPDU filtering feature prevents the switch port from sending or receiving BPDUs. The BPDU guard feature puts Port Fast-enabled ports that receive BPDUs in an error-disabled state. Use the no form of this command to return to the default setting.
spanning-tree portfast {bpdufilter default | bpduguard default | default}
no spanning-tree portfast {bpdufilter default | bpduguard default | default}
Syntax Description
Defaults
The BPDU filtering, the BPDU guard, and the Port Fast features are disabled on all ports unless they are individually configured.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the spanning-tree portfast bpdufilter default global configuration command to globally enable BPDU filtering on ports that are Port Fast-enabled (the ports are in a Port Fast-operational state). The ports still send a few BPDUs at link-up before the switch begins to filter outbound BPDUs. You should globally enable BPDU filtering on a switch so that hosts connected to switch ports do not receive BPDUs. If a BPDU is received on a Port Fast-enabled port, the port loses its Port Fast-operational status and BPDU filtering is disabled.
You can use the spanning-tree bpdufilter enable interface configuration command to re-enable BPDU filtering.
Caution
Use the spanning-tree portfast bpduguard default global configuration command to globally enable BPDU guard on ports that are in a Port Fast-operational state. In a valid configuration, Port Fast-enabled ports do not receive BPDUs. Receiving a BPDU on a Port-Fast-enabled port means an invalid configuration, such as the connection of an unauthorized device, and the BPDU guard feature puts the port in the error-disabled state. The BPDU guard feature provides a secure response to invalid configurations because you must manually put the port back in service. Use the BPDU guard feature in a service-provider network to prevent an access port from participating in the spanning tree.
Use the spanning-tree portfast global configuration command to globally enable the Port-Fast feature on all nontrunking ports. Configure Port Fast only on ports that connect to end stations; otherwise, an accidental topology loop could cause a data packet loop and disrupt switch and network operation. A Port Fast-enabled port moves directly to the spanning-tree forwarding state when linkup occurs without waiting for the standard forward-delay time.
You can use the no spanning-tree portfast global configuration command to disable Port Fast on all ports unless they are individually configured with the spanning-tree portfast interface configuration command.
Examples
This example shows how to globally enable the BPDU filtering feature:
Switch(config)# spanning-tree portfast bpdufilterThis example shows how to globally enable the BPDU guard feature:
Switch(config)# spanning-tree portfast bpduguardThis example shows how to globally enable the Port Fast feature on all nontrunking ports:
Switch(config)# spanning-tree portfastYou can verify your settings by entering the show running-config privileged EXEC command.
Related Commands
Limitations and Restrictions
You should review this section before you begin working with the switches. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
IOS Restrictions
These are the IOS restrictions for this release:
•
•
•
Caution
Beginning in user EXEC mode, follow these steps to verify and reset the VTP configuration revision number on a switch before adding it to a VTP domain.
After resetting the configuration revision number, add the switch to the VTP domain.
Note
•
•
•
•
–
–
LRE Restrictions
These are the LRE restrictions for this release:
•
Data transmission continues normally if the LRE link is restored. (CSCdt22573)
•
Note
The workaround is to set the LRE interface to the LRE-10 or the LRE-10LL profile. (CSCdv01167)
•
switch(config)#int longReachEthernet 0/?
<1-28> LongReachEthernet interface number
The correct range is:
<1-24> LongReachEthernet interface number
The workaround is to only use ports 1 through 24. (CSCdz78081)
CMS Restrictions
These are the CMS restrictions for this release:
•
•
•
The workaround, if you do not want to disable the proxy server settings on the browser, is to download a browser from a different vendor and use it without the proxy server settings configured to access the CMS.
Important Notes
This section describes important information related to this release.
•
•
Note
•
Open Caveats
These are the open caveats in this release:
Open IOS Caveats
These are the severity 3 IOS configuration caveats in this release:
•
When trying to find the cam table (show mac) through SNMP, you have to query dot1dTpFdbPort (.1.3.6.1.2.1.17.4.3.1.2), and then based on the results poll dot1dBasePortIfIndex (.1.3.6.1.2.1.17.1.4.1.2). When you issue an snmpwalk dot1dTpFdbPort all interfaces are returned. However, the snmpwalk dot1dBasePortIfIndex displays the physical interfaces only.
The workaround is to do an snmpget dot1dBasePortIfIndex by using the index found from the snmpwalk dot1dTpFdbPort query.
•
A switch that is running in VTP server mode unexpectedly removes VLANs when there is a topology change on another device.
There is no workaround.
•
A switch might not send coldStart and warmStart SNMP traps when it is reloaded or powered up, depending on the configuration and the topology.
There is no workaround.
•
When a switch is dually uplinked to a core switch (for example, a Catalyst 5000 switch) and each uplink carries up to ten VLANs, each uplink behaves normally for approximately two to three minutes: All ports for all VLANs are in a consistent state, and one port forwards while another is blocked.
After two to three minutes, only one VLAN stops registering the current Spanning Tree Protocol (STP) root. The switch then maximizes its age setting, declares itself a root, and unblocks the blocked port.
There is no workaround.
•
If port is configured for multicast storm control and the multicast traffic reaches the threshold, the port blocks all traffic on the port.
There is no workaround.
Open LRE Caveat
This the severity 3 LRE caveat in this release:
•
When a FastEthernet port is configured with Port-Fast, STP transitions to the learning state for a brief period (approximately 1 second) before moving to the forwarding state.
There is no workaround.
Resolved Caveats
These caveats were resolved in this release:
•
•
•
Resolved IOS Caveats in Release 12.0(5)WC7
•
When a destination based port group is configured as a (MVR) receiver ports and the hosts subscribe to the multicast traffic through the port group members, you no longer receive duplicated multicast streams from all the port members.
•
This error message is no longer reported in the message log:
Assert failure in ../src-l2-les-common/stp_les_shim.c line 2443
•
This error message no longer appears when a MAC address is changed from one type (secure, static, dynamic) to another:
The same static address could not be assigned to another interface.
•
A link-up trap is now generated when a VLAN interface is shut down and then brought back up by using the shutdown and no shutdown interface configuration commands.
•
Multicast VLAN Registration (MVR) no longer stops properly receiving Internet Group Management Protocol (IGMP) messages after a VLAN assignment change or a link up or link down event from a dynamic VLAN port.
•
When a Gigabit Ethernet port is configured as an access port, that port no longer forwards incoming 801.Q-tagged VLAN frames.
•
When a Cisco IP Phone is supplied with an external power supply and inline power is enabled for the port connected to the IP phone, the output of the show power inline privileged EXEC command no longer shows "no" under the Phone column.
•
When the connection to the primary server fails, a switch no longer skips the secondary Terminal Access Controller Access Control System (TACACS) server defined in the server list.
•
A buffer leak is no longer caused by Terminal Access Controller Access Control System Plus (TACACS+) packets in the middle buffer pool.
•
Low-memory conditions no longer occur when high rates of HTTP traffic are sent to a switch.
•
A VLAN Membership Policy Server (VMPS) server no longer sends multiple VMPS requests to a switch when the server and the switch first establish a link.
•
A Gigabit Ethernet link now correctly shuts down when you enter the shutdown interface command.
•
A switch now correctly processes incoming VLAN Query Protocol (VPQ) packets from a VLAN Membership Policy Server (VMPS) server.
•
Rebooting a switch or entering the shutdown and no shutdown interface commands on a Gigastack link between two switches now stops link flap between those links and now stabilizes the link.
•
A loop no longer occurs when two switches are trunked together through a Gigabit interface by 801.Q and you remove the native VLAN from the trunk.
•
When a switch is configured with Port Fast through SNMP, the port begins forwarding immediately.
•
When a trunk port is aging out or deleting an address on a switch, this error message is no longer displayed:
Oct 29 11:52:04.844: Assert failure in ../src-malibu/co_addr.c line 2216
•
A switch now logs a message when a self-loop condition is detected. The switch now also displays the self-loopback status when you enter the show interface interface-id switchport privileged EXEC command.
•
The UniDirectional Link Detection (UDLD) protocol now immediately detects a stuck port or a unidirectional link error on the remote end of a port. In previous releases, UDLD did not detect these error conditions for approximately 2 to 3 minutes.
•
This error message is no longer randomly displayed:
Sep 11 07:10:08 UTC: %SCHED-3-STUCKMTMR: Sleep with expired managed timer 4D1C44, time 0x7A32C00A3 (00:00:00 ago). -Process= "IP SNMP", ipl= 6, pid= 61 -Traceback= 1C1E2C 1C2114 649CC 1D0CCC
•
A switch does not respond correctly to the etherHistoryUtilisation object identifier (OID) if the port speed is changed.
•
Traceback messages no longer occur when a multicast VLAN Registration (MVR) port is a dynamic access port and an MVR address is deleted.
•
When Visual Switch Manager is used to configure a switch, the configuration archive on Resource Manager Essentials (RME) now works properly, and the configuration history is registered to the RME database on schedule polling.
•
When an MVR port is a dynamic access port and an MVR address is deleted, a traceback message no longer appears.
•
When a switch is configured as a (VLAN Trunking Protocol) VTP server or VTP client, the switch continues processing Cisco Discovery Protocol (CDP), spanning-tree protocol (STP), or VTP control-plane traffic.
•
When a dynamic VLAN port loses connectivity to the VLAN, or when the shutdown and no shutdown interface configuration commands are applied to that port, the port no stops processing packets or remains in the Link Up/Protocol Down state.
•
The counters that are displayed by entering the show interface privileged EXEC command now count symbol errors as part of the input errors counter.
•
When polling the dot3StatsTable for interfaces, the counters no longer show uninitialized random values.
•
Bridge protocol data unit (BPDU) filtering was added in Release 12.0(5)WC7. For more information, see the "New Software Feature" section.
•
A switch no longer creates a traceback when the spanning-tree debugging is enabled
•
The SNMP agent now returns normal values (0 to 100, as defined in the CISCO-PROCESS-MIB) for these objects:
–
–
–
–
–
–
Resolved CMS Caveats in Release 12.0(5)WC7
•
You can change the distribution of EtherChannels from CMS.
•
Port status is now correctly displayed in the Front Panel view.
•
CMS now displays all Cisco IP Phones in a cluster that are connected to Catalyst 3524 XL switches.
•
Link status is now correctly displayed on a Catalyst 3500 XL switch in the Front Panel view.
•
Multiple SPAN instances can now be configured through CMS.
•
You can now disable port security by using the Visual Switch Manager (VSM).
Resolved LRE Caveats in Release 12.0(5)WC7
These LRE caveats were resolved in Release 12.0(5)WC7:
•
The statement lre cpe 5 speed 100 no longer appears in the running configuration for a Cisco LRE CPE 585.
Note
•
You no longer lose Ethernet connectivity on a remote CPE Fast Ethernet port if you shut down the port from the LRE interface and then reload or reboot the switch without saving the current configuration.
•
The register settings for the protected port of an LRE CPE device are no longer lost after the LRE CPE device is power-cycled.
•
This message is no longer displayed when a Catalyst 2900 LRE XL switch is reloaded:
%LRE_UPGRADE-4-INIT_RESOURCE: cannot locate lre firmware files
•
An LRE port no longer appears to be randomly shut down.
Documentation Notes
You can access all Catalyst 2900 documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/index.htm
This section provides updates to the product documentation.
These changes will be included in the next version of the documentation.
General Documentation Notes
•
–
–
–
Corrections to Software Configuration Guide
These corrections apply to Catalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide:
•
When you start the switch, the switch automatically requests configuration information from a DHCP server only if a configuration file is not present on the switch.
DHCP autoconfiguration does not occur under these conditions:
–
–
•
•
•
By default, a trunk port sends to and receives traffic from all VLANs in the VLAN database. If the switch is configured with a number of VLANs and it is connected to Cisco IP Phones through 802.1Q trunk ports, the switch sends spanning-tree BPDUs for all VLANs to all of the phones. This can flood the phones with traffic
Beginning in privileged EXEC mode, follow these steps to configure a VLAN list that allows only voice and data VLANs on the trunk port:
l
For more information about these commands, refer to the switch command reference.
Additions to Software Configuration Guide
This information was not included in the software configuration guide for this release.
•
Error Message LRE_UPGRADE-4-INIT_RESOURCE: cannot locate lre firmware filesExplanation This message means that the LRE upgrade module cannot locate a required resource. The LRE upgrade module requires a directory in Flash memory named flash:/lre-bin. This directory stores the LRE-related firmware files for the LRE switch and LRE CPE devices. The upgrade module cannot initialize unless a directory already exists in Flash memory.
Recommended Action Verify that the flash:/lre-bin directory exists. If the directory is missing, create an empty directory named flash:/lre-bin. If the directory already exists, report this message to your Cisco technical support representative. (CSCdz56235)
For more information about system messages, refer to the "System Messages" chapter of the Catalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide.
•
Correction to Command Reference
The lre rate selection sequence global configuration command was introduced in 12.0(5)WC6. The switch command reference incorrectly states that this command was introduced in 12.0(6)WC6. (CSCea10612)
Corrections to Hardware Installation Guide
These corrections apply to the "Technical Specifications" section of the Catalyst 2900 Series XL Hardware Installation Guide:
•
•
–
–
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
Initial Switch Configuration
This section provides these procedures:
•
•
•
This section assumes that you have already installed the switch and connected devices to it, as described in the switch hardware installation guide.
Using the Setup Program
You can use an automatic setup program to assign switch IP information, host and cluster names, and passwords and to create a default configuration for continued operation. Later, you can use CMS or the command-line interface (CLI) to customize your configuration. To run the setup program, access the switch from the PC terminal that you connected to the console port. For information about connecting a PC or terminal to the switch console port, refer to the switch hardware installation guide.
Note
The first time that you access the switch, it runs a setup program that prompts you for IP and other configuration information necessary for the switch to communicate with local routers and the Internet. This information is also required if you plan to use CMS to configure and manage the switch.
You will need the following information from your system administrator:
Use this procedure to create an initial configuration for the switch:
Note
At any point you can enter a question mark for help. Use Ctrl-C to stop the configuration dialog at any prompt. The default settings are in square brackets.
Step 1
Continue with configuration dialog? [yes/no]: yStep 2
Enter IP address: ip_addressStep 3
Enter IP netmask: ip_netmaskStep 4
Would you like to enter a default gateway address? [yes]: yStep 5
IP address of the default gateway: ip_address
Note
Note
Step 6
Note
Enter enable secret: secret_passwordStep 7
Would you like to configure a Telnet password? [yes] y
Note
Step 8
Enter Telnet password: telnet_passwordStep 9
Note
Would you like to enable as a cluster command switch? yStep 10
Enter cluster name: cls_name
Note
Step 11
The following configuration command script was created: ip subnet-zero interface VLAN1 ip address 172.20.153.36 255.255.255.0 ip default-gateway 172.20.153.01 hostname host_name enable secret 5 $1$M3pS$cXtAlkyR3/6Cn8/ line vty 0 15 password telnet_password snmp community private rw snmp community public ro cluster enable cls_name endStep 12
•
•
Use this configuration? [yes/no]: yAfter you complete the setup program, the switch can use the created default configuration. If you want to change this configuration or want to perform other management tasks, use one of these tools:
•
•
The switch software configuration guide provides more information about how to set a password to protect the switch against unauthorized Telnet access and how to access the switch if you forget the password.
Installing the Required Plug-In
A Java plug-in is required for the browser to access CMS. Download and install the plug-in before you start CMS. Each platform, Windows and Solaris, supports three plug-in versions. For information on the supported plug-ins, see the "Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users" section and the "Solaris Platforms" section.
You can download the recommended plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
If the Java applet does not initialize after you have installed the plug-in, open the Java Plug-in Control Panel (Start > Programs > Java Plug-in Control Panel), and verify these settings:
In the Proxies tab, verify that the Use browser settings is checked and that no proxies are enabled.
Note
From the Start menu, disable the options by selecting Start > Programs > Network Associates > Virus Scan Console > Configure.
or
From the taskbar, right-click the Virus Shield icon, and in the Quick Enable menu, disable the options by deselecting Internet Filter or Download Scan.
Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users
These Java plug-ins are supported on the Windows platform:
•
•
•
You can download these plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Guidelines for Installing and Enabling the Java Plug-In
If CMS does not launch automatically, you might not have a supported Java plug-in installed or the Java plug-in might not be enabled. CMS does not automatically detect if a supported Java plug-in is installed. If you start CMS without the required Java plug-in installed, CMS does not start. To make sure that a supported Java Plug-In is correctly installed and enabled, follow these guidelines:
•
•
•
Solaris Platforms
These Java plug-ins are supported on the Solaris platform:
Caution
•
•
•
If you have a SmartNet contract, you can download these plug-ins and instructions from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
To install the Java plug-in, follow the instructions in the README_FIRST.txt file.
If you do not have a SmartNet contract, download the plug-in from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
Accessing CMS
Before using the web-based CMS tools, see the "Software Requirements" 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 "Displaying the CMS Access Page" section.
Displaying the CMS Access Page
After the browser is configured, display the CMS access page:
Step 1
http://10.1.126.45:184/level/14/where 10.1.126.45 is the switch IP address, 184 is the HTTP port, and level/14 is the privilege level. You do not need to enter the HTTP port if the switch is using HTTP port 80 (the default) or enter the privilege level if you have read-write access to the switch (privilege level is 15).
For information about the HTTP port and privilege levels, refer to the switch software configuration guide.
Step 2
If you configure a local username and password, make sure you enable it by using the ip http authentication global configuration command. Enter your username and password when prompted.
Step 3
If you access CMS from a standalone or member switch, Device Manager appears. If you access CMS from a command switch, you can display the Front Panel and Topology views.
For complete information about CMS, refer to the switch software configuration guide.
Upgrading the Switch IOS Software
This section provides topics about upgrading the switch software:
•
•
•
•
•
•
•
•
Note
Guidelines for Upgrading Switch Software
Note
When upgrading the LRE switch software, follow these rules:
•
•
•
•
•
•
•
•
•
Overview of the Switch Upgrade Process
The software upgrade procedure has these major steps:
•
•
The tar command extracts the IOS image, the e2rb.bin LRE firmware file, and the HTML files from the .tar file during the TFTP copy to the switch.
•
When you upgrade a switch, the switch continues to operate while the new software is copied to Flash memory. If Flash memory has enough space, the new image is copied to the selected switch but does not replace the running image until you reboot the switch.
Note
If Flash memory does not have enough space for two images, your new image is copied over the existing one.
Note
•
–
–
Features provided by the new software are not available until you reload the switch.
Determining the Switch Software Version
The IOS image is stored as a .bin file in a directory that is named with the IOS release. A subdirectory contains the HTML files needed for web management. The image is stored on the system board Flash device (flash:).
You can use the show version user EXEC command to see the software version that is running on your switch. For example:
3500-239-34> show versionCisco Internetwork Operating System SoftwareIOS (tm) C3500xl Software (C3500xl-C3H2S-M), Version 12.0(0.0.2)WC5, RELEASE SOFT)
Copyright (c) 1986-2002 by cisco Systems, Inc.Compiled Tue 14-May-02 12:57 by antoninoImage text-base: 0x00003000, data-base: 0x0034A3B8You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that might be stored in Flash memory.
Note
Which Software Files to Download from Cisco.com
New software releases are posted on Cisco.com and are also available through authorized resellers. From Cisco.com, you can also download a TFTP server application to copy the switch software from your PC to the switch.
Table 7 describes the file extensions and what they mean for the upgrade procedure. Table 8 lists the software files that you need from Cisco.com.
Note
Note
Downloading the New Software and TFTP Server Application to Your Management Station
Follow these steps to download the new software and, if necessary, the TFTP server application, from Cisco.com to your management station:
Step 1
Step 2
If you have a SmartNet support contract, go to this URL, and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
If you do not have a SmartNet contract, go to this URL, and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
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.
The following procedure requires a configured TFTP server such as the Cisco TFTP server available on Cisco.com.
Beginning in privileged EXEC mode, follow these steps to copy a switch configuration file to the PC or server that has the TFTP server application:
Step 1
switch# copy flash:config.text tftpStep 2
Address or name of remote host []? ip_addressStep 3
Destination filename [config.text]? yes/noStep 4
Using CMS to Upgrade One or More Switches
Note
You can use the Software Upgrade window in Cluster Manager to upgrade all or some of the switches in a cluster at once. When doing an upgrade, enter the image_name.tar filename in the New File Name field. The .tar file contains both the IOS image and the web-management code.
•
Follow these steps to use CMS to upgrade switch software. Refer to the online help for more details.
Step 1
Step 2
You can enter just the filename or a pathname into the New Image File Names field. You do not need to enter a pathname if the image file is in the directory that you have defined as the TFTP root directory.
Note
Note
New images are copied to Flash memory and do not affect operation. The switch checks Flash memory to ensure that there is sufficient space before the upgrade takes place. If there is enough space, the new image is copied to the switch without replacing the old image, and after the new image is completely downloaded, the old one is erased. In this case, you can still reboot your switch by using the old image if a failure occurs during the copy process.
If there is not enough space in Flash memory for the new and old images, the old image is deleted, and the new image is downloaded.
Note
Recovering from an Incomplete CMS Software Upgrade
An upgrade failure can create multiple copies of IOS images and other files in Flash memory. This would not leave enough space for the HTML files to also be copied to Flash memory; thus, you will not be able to access the switch through CMS.
If a failure occurs, ensure that the image file in Flash memory has the same name as the contents of the boot variable.
If the contents of the boot variable and the image file name are the same, the switch can reset successfully. If they are different, rename the image file, or reset the boot variable by entering the system boot name global configuration command. The boot variable and the image file name should be the same.
To recover from the incomplete download of the HTML files, log in to the switch, and upgrade the software.
Using the CLI to Upgrade a Catalyst 2900 LRE XL Switch
Note
If you are upgrading a Catalyst 2900 XL switch that is not an LRE switch, see the "Recovering from an Incomplete CMS Software Upgrade" section.
Follow these steps to upgrade the LRE switch software:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enableswitch#Enter a password if you are prompted to do so.
Step 4
switch# show bootConfig file: flash:config.textEnable Break: 1Manual Boot: noHELPER path-list:NVRAM/Config filebuffer size: 32768If there is no file defined in the BOOT path-list, enter the dir flash: privileged EXEC command to display the contents of Flash memory. The file named c2900XL-c3h2-mz-120-5.1.WC.1.bin is your previous image file.
switch# dir flash:Directory of flash:/175 -rwx 111 May 17 2001 13:25:53 info.ver165 -rwx 8192 May 17 2001 13:22:13 e2rb.bin4 drwx 10240 May 17 2001 13:25:52 html167 -rwx 1496 May 17 2001 13:21:46 config.text6 -rwx 111 May 17 2001 13:23:41 info176 -rwx 1422 Jan 01 1970 00:14:43 env_vars7741440 bytes total (4692992 bytes free)Step 5
switch# config terminalStep 6
switch(config)# no IP http serverStep 7
Note
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2900XL-c3h2s-mz-120-5.3.WC.1.binStep 8
switch(config)# endStep 9
switch# delete flash:html/*Step 10
Step 11
switch# delete flash:html/Snmp/*
Note
Step 12
Step 13
Caution
switch# tar /x tftp://server_ip_address/path/filename.tar flash:Loading /path/filename.tar from server_ip_address (via VLAN1): !extracting info (111 bytes)extracting c2900XL-c3h2s-mz.120-5.3.WC.1.bin (1750311 bytes)!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!html/ (directory)extracting html/ClusterBuilder.html.gz (670 bytes)extracting html/ClusterManager.html.gz (624 bytes)extracting html/back.html.gz (211 bytes)!. . .Depending on the TFTP server being used, you might need to enter only one slash (/) after the server_ip_address in the tar privileged EXEC command. The tar privileged EXEC command extracts the IOS image and the HTML files from the combined .tar file during the TFTP copy to the switch.
Step 14
switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Step 15
switch(config)# IP http serverStep 16
switch(config)# endStep 17
switch# reloadSystem configuration has been modified. Save? [yes/no]: yProceed with reload? [confirm]Step 18
Your Telnet session ends when the switch resets.
Step 19
If you have a previously opened browser session to the upgraded switch, close the browser, and restart it to ensure that you are using the latest HTML files.
Upgrading LRE Firmware
The 2900 LRE XL switch can store and properly apply LRE binaries if there are updates required to the firmware on the switch 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 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 entering LRE upgrade controller configuration commands from the controller configuration submode. Use the upgrade configuration command in the controller submode 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
See the reference pages for the upgrade commands in the Catalyst 2900 XL and Catalyst 3500 XL Command Reference for further details.
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 submode 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
The following is an example of how an LRE upgrade can proceed:
Switch#hw-module slot 0 upgrade lre force remote lo 1/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 comes out of reset. 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 has come out of reset. 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#Related Documentation
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 and the switch software:
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from 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 may have 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.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top 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: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco 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 website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•
•
•
•
Cisco TAC Website
You can use the Cisco TAC website 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 website, 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 website. Some services on the Cisco TAC website require 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://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
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.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Net Readiness Scorecard, Networking Academy, and ScriptShare are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, 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, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, TransPath, 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. (0303R)
Copyright © 2001-2003, Cisco Systems, Inc.
All rights reserved.
Guest
