Release Notes for the Catalyst 2900 XL LRE Switches, Cisco IOS Release 12.0(5)WC7 [Cisco Catalyst 2900 Series LRE XL Switches]

Table Of Contents

Release Notes for the Catalyst 2900 Series LRE XL Switches for Cisco IOS Release 12.0(5)WC7

Contents

Hardware Requirements

Software Requirements

System Requirements

Browser and Java Plug-In Requirements

Cluster Requirements and Guidelines

Catalyst 2900 XL and Catalyst 3500 XL Switches

Catalyst 3550 Switches

Catalyst 2950 Switches

Catalyst 1900 and Catalyst 2820 Switches

Minimum Cisco IOS Release for Major Features

New Software Feature

Enabling BPDU Filtering

Using the spanning-tree portfast Command

Limitations and Restrictions

IOS Restrictions

LRE Restrictions

CMS Restrictions

Important Notes

Open Caveats

Open IOS Caveats

Open LRE Caveat

Resolved Caveats

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

Documentation Notes

General Documentation Notes

Corrections to Software Configuration Guide

Additions to Software Configuration Guide

Correction to Command Reference

Corrections to Hardware Installation Guide

Updated Translated Warnings

Attaching the Cisco RPS (model PWR300-AC-RPS-N1)

Overtemperature Warning

Chassis Power Connection

Initial Switch Configuration

Using the Setup Program

Installing the Required Plug-In

Accessing CMS

Configuring the HTTP Server

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

Upgrading LRE Firmware

Configuring for an LRE Upgrade

Performing an LRE Upgrade

Global Configuration of LRE Upgrades

Controller Configuration of LRE Upgrades

LRE Upgrade Behavior Details

LRE Upgrade Example

Related Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

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:

•If you are installing a new switch, refer to the IOS release label on the rear panel of your switch.

•If your switch is on and running, use the show version user EXEC command. See the "Determining the Switch Software Version" section.

•If you are upgrading to a new release, refer to the software upgrade filename for the IOS version. Before upgrading your switch to this release, read the "Upgrading the Switch IOS Software" section.

You can download the switch software from these sites:

•http://www.cisco.com/public/sw-center/sw-lan.shtml
(for registered Cisco.com users with a login password)

•http://www.cisco.com/public/sw-center/sw-lan.shtml
(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" section

•"Software Requirements" section

•"Cluster Requirements and Guidelines" section

•"Minimum Cisco IOS Release for Major Features" section

•"New Software Feature" section

•"Limitations and Restrictions" section

•"Open Caveats" section

•"Important Notes" section

•"Documentation Notes" section

•"Initial Switch Configuration" section

•"Upgrading the Switch IOS Software" section

•"Upgrading LRE Firmware" section

•"Related Documentation" section

•"Obtaining Documentation" section

•"Obtaining Technical Assistance" section on page 45

Hardware Requirements

Note Catalyst 3500 XL switches and Catalyst 2900 XL switches that are not LRE switches do not support this release.

Note This release is not for the Catalyst 2900 XL 4-MB switches. The 4-MB models are WS-C2908-XL, WS-C2916M-XL, WS-C2924C-XL, and WS-C2924-XL. These switches can only be upgraded up to Release 11.2(8.10)SA6. To be cluster members, these switches must run Release 11.2(8.x)SA6 original edition software. To determine the switch DRAM size, enter the show version user EXEC command.

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

Switch

Description

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:

•Microsoft Windows 95 (Service Pack 1 required)

•Microsoft Windows 98, second edition

•Microsoft Windows NT 4.0 (Service Pack 3 or higher required)

•Microsoft Windows 2000

•Solaris 2.5.1 or higher, with the Sun-recommended patch cluster for that operating system and Motif library patch 103461-24

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

OS

Processor Speed

DRAM

Number of Colors

Resolution

Font Size

Windows NT 4.0¹

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)

¹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

Operating System

Netscape Communicator¹

Microsoft Internet Explorer

Windows 95

4.61, 4.7

5.0, or 5.5

Windows 98

-²

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

—³

¹Netscape Communicator version 4.60 and 6.0 are not supported. (CSCdx34982)

²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)

³Microsoft Internet Explorer is not supported on Solaris 2.5.1 or higher.

Note If you receive an Internet Explorer error message that the page might not display correctly because your security settings prohibit the ActiveX controls, your security settings are set too high. To lower security settings, go to Tools > Internet Options, and select the Security tab. Select the indicated Zone, and move the Security Level for this Zone slider from High to Medium (the default).

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 We strongly recommend that the highest-end, command-capable switch in the cluster 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.

Table 4 Catalyst 2900 XL and Catalyst 3500 XL Switches as Cluster Members

Switch

Release 12.0(5.3)WC(1) or higher?

Command Capable?

Member Capable?

Catalyst 2900 XL (4 MB of DRAM)¹

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

¹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 We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has a Catalyst 3550 switch, that switch should be the command switch.

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 We strongly recommend that the highest-end, command-capable switch in the cluster be the command switch. If your switch cluster has Catalyst 2900 XL, Catalyst 2950, and Catalyst 3500 XL switches, the Catalyst 2950 should be the command switch.

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 We strongly recommend that the highest-end, command-capable switch in the cluster 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.

Table 5 Catalyst 1900 and Catalyst 2820 Switches as Cluster Members

Switch

Release 9.00 (-EN)

Member Capable?

Command Capable?

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

Feature

Minimum 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

•Using the spanning-tree portfast Command

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 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.

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 Enabling BPDU filtering on an interface is the same as disabling spanning tree on it and can result in spanning-tree loops.

Beginning in privileged EXEC mode, follow these steps to globally enable the BPDU filtering feature:

Command

Purpose

Step 1

configure terminal

Enter global configuration mode.

Step 2

spanning-tree portfast bpdufilter default

Globally enable BPDU filtering.

By default, BPDU filtering is disabled.

Step 3

interface interface-id

Enter interface configuration mode, and specify the interface connected to an end station.

Step 4

spanning-tree portfast

Enable the Port-Fast feature.

Step 5

end

Return to privileged EXEC mode.

Step 6

show running-config

Verify your entries.

Step 7

copy running-config startup-config

(Optional) Save your entries in the configuration file.

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

bpdufilter default

Globally enable BPDU filtering on Port Fast-enabled ports and prevent the switch port connected to end stations from sending or receiving BPDUs.

bpduguard default

Globally enable the BPDU guard feature on Port Fast-enabled ports and place the ports that receive BPDUs in an error-disabled state.

default

Globally enable the Port Fast feature on all nontrunking ports. When the Port Fast feature is enabled, the port changes directly from a blocking state to a forwarding state without making the intermediate spanning-tree state changes.

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

Release

Modification

12.0(5)WC7

This command was first introduced.

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 Enabling BPDU filtering on an interface is the same as disabling spanning tree on it and can result in spanning-tree loops.

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 bpdufilter 
This example shows how to globally enable the BPDU guard feature:
Switch(config)# spanning-tree portfast bpduguard 
This example shows how to globally enable the Port Fast feature on all nontrunking ports:
Switch(config)# spanning-tree portfast 
You can verify your settings by entering the show running-config privileged EXEC command.

Related Commands

Command

Description

show running-config

Displays the current operating configuration. For syntax information, select Cisco IOS Configuration Fundamentals Command Reference for Release 12.1 > Cisco IOS File Management Commands > Configuration File Commands.

spanning-tree bpdufilter

Prevents a port from sending or receiving BPDUs.

spanning-tree bpduguard

Puts a port in the error-disabled state when it receives a BPDU.

spanning-tree portfast (interface configuration)

Enables the Port Fast feature on an interface in all its associated VLANs.

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:

•You can connect the switch to a PC by using the switch console port and the supplied rollover cable and the DB-9 adapter. You need to provide a RJ-45-to-DB-25 female DTE adapter if you want to connect the switch console port to a terminal. You can order a kit (part number ACS-DSBUASYN=) with this RJ-45-to-DB-25 female DTE adapter from Cisco.

•Certain combinations of port features create configuration conflicts. Refer to the "Avoiding Configuration Conflicts" section in the "Troubleshooting" chapter of the switch software configuration guide for a table that defines these conflicts.

•When you add a VTP client, follow this caution and procedure:

Caution Before adding a VTP client to a VTP domain, always verify that its VTP configuration revision number is lower than the configuration revision number of the other switches in the VTP domain. If necessary, reset the switch configuration revision number to 0. Switches in a VTP domain always use the VLAN configuration of the switch with the highest VTP configuration revision number. If you add a switch that has a revision number higher than the revision number in the VTP domain, it can erase all VLAN information from the VTP server and VTP domain.

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.

Command

Purpose

Step 1

show vtp status

Check the VTP configuration revision number.

If the number is 0, add the switch to the VTP domain.

If the number is greater than 0, follow these steps:

a. Write down the domain name.

b. Write down the configuration revision number.

c. Continue with the next steps to reset the configuration revision number on the switch.

Step 2

enable

Enter privileged EXEC mode.

Step 3

vlan database

Enter VLAN database mode.

Step 4

vtp domain domain-name

Change the domain name from the original one displayed in Step 1 to a new name.

Step 5

exit

The VLAN information on the switch is updated and the configuration revision number is reset to 0. You return to privileged EXEC mode.

Step 6

show vtp status

Verify that the configuration revision number has been reset to 0.

Step 7

vlan database

Enter VLAN database mode.

Step 8

vtp domain domain-name

Enter the original domain name on the switch.

Step 9

exit

The VLAN information on the switch is updated, and you return to privileged EXEC mode.

Step 10

show vtp status

(Optional) Verify that the domain name is the same as in Step 1 and that the configuration revision number is 0.

After resetting the configuration revision number, add the switch to the VTP domain.

Note You can use the vtp transparent vlan database command to disable VTP on the switch and then change its VLAN information without affecting the other switches in the VTP domain. For more information about using vtp transparent mode, refer to the switch software configuration guide.

•Host names and Domain Name System (DNS) server names that contain commas on a cluster command switch, member switch, or candidate switch can cause CMS to behave unexpectedly. You can avoid this instability in the interface by not using commas in host names or DNS names. Do not use commas when also entering multiple DNS names in the Device Configuration tab (Administration > IP Addresses) in CMS.

•The range of seconds for the span-tree max-age global configuration command is now 6 to 200 seconds. If you had used this command in Release 11.2(8)SA6 or earlier to set a value greater than this range and now upgrade your software to Release 11.2(8.1)SA6 or later, the switch sets this value to the default: 20 seconds for IEEE STP and 10 seconds for IBM STP.

•When using the SPAN feature, the monitoring port receives copies of sent and received traffic for all monitored ports. If the monitoring port is 50 percent oversubscribed for a sustained period of time, it will probably become congested. One or more of the ports being monitored might also experience a slowdown.

•When using the Software Image Management (SWIM) application in the Resource Manager Essentials (RME) suite of the CiscoWorks2000 product family to perform automated system software and boot loader upgrades, you should note the following:

–Catalyst 2900 series XL switches require Release 11.2(8)SA4 or later and RME version 2.1 or 2.2.

–Catalyst 3500 series XL switches require Release 11.2(8.1)SA6 or later and RME version 2.2.

LRE Restrictions

These are the LRE restrictions for this release:

•If a port group is set up between the LRE port of a Catalyst 2900 LRE XL switch and the Fast EtherChannel (FEC) ports of another switch through the LRE CPE devices, and the LRE link on an LRE port drops, the LRE switch no longer uses the LRE port for data transmission. However, the other switch might continue sending data through the FEC port. The packets sent to the LRE port of the LRE switch are lost.

Data transmission continues normally if the LRE link is restored. (CSCdt22573)

•A high number of collisions can occur for FTP transfers when a large number of packets are sent in a burst from a high-speed interface (such as Fa0/1) to a low-speed interface (such as Lo0/2), which can cause lower than expected transmission speeds.

Note Not all environments are able to support the LRE-10 profile.

The workaround is to set the LRE interface to the LRE-10 or the LRE-10LL profile. (CSCdv01167)

•The help that is displayed by the config interface interface configuration command on a Catalyst 2900 LRE XL switch incorrectly states that 28 LRE ports are available:

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:

•CMS does not support Netscape Navigator 6.0. The workaround is to use a supported version of Netscape Navigator. (CSCdx34982)

•CMS does not work reliably on machines running Windows 98 and Netscape Navigator. The workaround is to use Microsoft Internet Explorer. (CSCdx49978)

•If you have a proxy server configured on your web browser, CMS can run slowly and take 2 to 3 minutes to process each command that is entered.

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.

•The cluster setup privileged EXEC command was removed in Release 12.0(5)WC5.

•The e2rb.bin LRE firmware file is required for the LRE switch operation. This file is deleted and then replaced with the most current version when you upgrade the LRE switch software. Do not delete this file after upgrading your LRE switch.

Note The LRE firmware file resides in the lre-bin directory on the switch. We strongly recommend that you do not delete this directory. The lre-bin directory can be obtained from the IOS .tar file. If you delete the lre-bin directory, extract IOS from the .tar file, and copy the lre-bin directory to Flash memory.

•The MVR threshold feature was removed in Release 12.0(5.3)WC(1). To limit rates, use the port multicast storm control feature instead of the MVR threshold feature.

Open Caveats

These are the open caveats in this release:

•"Open IOS Caveats" section

•"Open LRE Caveat" section

Open IOS Caveats

These are the severity 3 IOS configuration caveats in this release:

•CSCdz55568

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.

•CSCdz73429

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.

•CSCdz87390

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.

•CSCdz88374

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.

•CSCde21637

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:

•CSCdz88873

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" section

•"Resolved CMS Caveats in Release 12.0(5)WC7" section

•"Resolved LRE Caveats in Release 12.0(5)WC7" section

Resolved IOS Caveats in Release 12.0(5)WC7

•CSCdw48256

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.

•CSCdx32678

This error message is no longer reported in the message log:

Assert failure in ../src-l2-les-common/stp_les_shim.c line 2443

•CSCdx42540

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.

•CSCdx63694

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.

•CSCdx82206

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.

•CSCdx86493

When a Gigabit Ethernet port is configured as an access port, that port no longer forwards incoming 801.Q-tagged VLAN frames.

•CSCdx92614

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.

•CSCdy16637

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.

•CSCdy20322

A buffer leak is no longer caused by Terminal Access Controller Access Control System Plus (TACACS+) packets in the middle buffer pool.

•CSCdy35596

Low-memory conditions no longer occur when high rates of HTTP traffic are sent to a switch.

•CSCdy42626

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.

•CSCdy69197

A Gigabit Ethernet link now correctly shuts down when you enter the shutdown interface command.

•CSCdy69779

A switch now correctly processes incoming VLAN Query Protocol (VPQ) packets from a VLAN Membership Policy Server (VMPS) server.

•CSCdy71667

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.

•CSCdy88935

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.

•CSCdz04972

When a switch is configured with Port Fast through SNMP, the port begins forwarding immediately.

•CSCdz16841

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

•CSCdz02913

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.

•CSCuk34772

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.

•CSCdz08471

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

•CSCdz11025

A switch does not respond correctly to the etherHistoryUtilisation object identifier (OID) if the port speed is changed.

•CSCdz18267

Traceback messages no longer occur when a multicast VLAN Registration (MVR) port is a dynamic access port and an MVR address is deleted.

•CSCdz13910

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.

•CSCdz18267

When an MVR port is a dynamic access port and an MVR address is deleted, a traceback message no longer appears.

•CSCdz35564

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.

•CSCdz45265

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.

•CSCdz42687

The counters that are displayed by entering the show interface privileged EXEC command now count symbol errors as part of the input errors counter.

•CSCdz47360

When polling the dot3StatsTable for interfaces, the counters no longer show uninitialized random values.

•CSCdz86732

Bridge protocol data unit (BPDU) filtering was added in Release 12.0(5)WC7. For more information, see the "New Software Feature" section.

•CSCdz89542

A switch no longer creates a traceback when the spanning-tree debugging is enabled

•CSCin34695

The SNMP agent now returns normal values (0 to 100, as defined in the CISCO-PROCESS-MIB) for these objects:

–cpmProcExtUtil5SecRev

–cpmProcExtUtil1MinRev

–cpmProcExtUtil5MinRev

–cpmProcExtUtil5SecRev

–cpmProcExtUtil1MinRev

–cpmProcExtUtil5MinRev

Resolved CMS Caveats in Release 12.0(5)WC7

•CSCdx34179

You can change the distribution of EtherChannels from CMS.

•CSCdx90717

Port status is now correctly displayed in the Front Panel view.

•CSCdy36691

CMS now displays all Cisco IP Phones in a cluster that are connected to Catalyst 3524 XL switches.

•CSCdy43965

Link status is now correctly displayed on a Catalyst 3500 XL switch in the Front Panel view.

•CSCdy85745

Multiple SPAN instances can now be configured through CMS.

•CSCdz08376

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:

•CSCdy82784

The statement lre cpe 5 speed 100 no longer appears in the running configuration for a Cisco LRE CPE 585.

Note The Cisco 585 LRE CPE supports only four Ethernet ports.

•CSCdz36516

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.

•CSCdz41800

The register settings for the protected port of an LRE CPE device are no longer lost after the LRE CPE device is power-cycled.

•CSCdz56235

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

•CSCdz78324

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

•This information is now only in the release notes and is no longer in the manuals:

–Hardware, software, and cluster requirements

–Procedures for initial switch configuration: using the setup program, installing browser plug-ins, and accessing CMS

–Procedures for upgrading the switch software

Corrections to Software Configuration Guide

These corrections apply to Catalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide:

•DHCP autoconfiguration does not occur as described in the "DHCP Client Request Process" section under the "Using DHCP-Based Autoconfiguration" section in the 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:

–When a configuration file is present and the service config global configuration command is disabled on the switch.

–When a configuration file is present and the service config global configuration command is enabled on the switch. In this case, the switch broadcasts TFTP requests for the configuration file.

•The software configuration guide incorrectly states that flow control is supported on ports running at 100 Mbps in full-duplex mode. Flow control is supported only on installed, 1000 Mbps module ports.

•The Catalyst 2900 XL and Catalyst 3500 XL documentation does not specify that the Enterprise edition (which requires 8-MB of Flash memory) is required to configure TACACS+.

•The VLAN chapter in the Catalyst 2900 XL and Catalyst 3500 XL Software Configuration Guide does not show how to use the switchport trunk allowed vlan add command. (CSCdw47096)

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:

Command

Purpose

configure terminal

Enter global configuration mode.

interface interface_id

Enter interface configuration mode and the port to be added to the VLAN.

switchport mode trunk

Configure VLAN membership mode for trunks.

switchport trunk allowed vlan add vlan-list

Define the voice and data VLANs that are allowed to send and receive on the port.
The vlan-list parameter is a range of VLAN IDs. Separate nonconsecutive VLAN IDs with a comma and no spaces; use a hyphen to designate a range of IDs. Valid IDs are from 2 to 1001.

end

Return to privileged EXEC mode.

show interface interface-id switchport allowed-vlan

Verify your entries.

copy running-config startup-config

Save the configuration.

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.

•Release 12.0(5)WC7 includes this new system message:
Error Message    LRE_UPGRADE-4-INIT_RESOURCE: cannot locate lre firmware files
Explanation 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.

•Release 12.0(5)WC7 supports BPDU filtering. BPDU filtering prevents ports that are in a Port Fast-operational state from sending or receiving BPDUs. For more information, see "New Software Feature" section.

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:

•Table A-4 shows an incorrect figure for the power consumption. The actual power consumption is 70 W rather than 150 W.

•Table A-4 should also include this information:

–2912 LRE XL and 2924 LRE XL KVA rating: 0.07 KVA

–2950 ST LRE KVA rating: - 0.030 KVA

Updated Translated Warnings

These warnings have been updated for this release.

Attaching the Cisco RPS (model PWR300-AC-RPS-N1)

Warning

Attach only the Cisco RPS (model PWR300-AC-RPS-N1) to the RPS receptacle.

Waarschuwing

Slechts de Cisco RPS (model PWR300-AC-RPS-N1) aan de RPS contactdoos verbinden.

Varoitus

Kiinnitä RPS-vastakappaleeseen vain Cisco RPS (malli PWR300-AC-RPS-N1).

Avertissement

Raccordez le bloc d'alimentation Cisco RPS (modèle PWR300-AC-RPS-N1) uniquement au connecteur RPS.

Warnung

An die RPS-Steckhülse darf nur das Cisco RPS (Modell PWR300-AC-RPS-N1) angeschlossen werden.

Figyelem!

Az RPS csatlakozóhoz csak Cisco RPS (PWR300-AC-RPS-N1 modell) aljzatot csatlakoztasson.

Avvertenza

Collegare soltanto il Cisco RPS (modello PWR300-AC-RPS-N1) alla presa RPS.

Advarsel!

Koble bare Cisco RPS (modell PWR300-AC-RPS-N1) til RPS-stikkontakten.

Aviso

Anexe o RPS Cisco (modelo PWR300-AC-RPS-N1) apenas ao receptáculo RPS.

¡Advertencia!

Sólo conecte el Cisco RPS (modelo PWR300-AC-RPS-N1) al receptáculo RPS.

Varning!

Koppla endast Ciscos RPS (modell PWR300-AC-RPS-N1) till RPS-uttaget.

Hierarchical Navigation

Cisco Catalyst 2900 Series LRE XL Switches

Release Notes for the Catalyst 2900 XL LRE Switches, Cisco IOS Release 12.0(5)WC7

Downloads

Table Of Contents

Release Notes for the Catalyst 2900 Series LRE XL Switches for Cisco IOS Release 12.0(5)WC7

Contents

Hardware Requirements

Software Requirements

System Requirements

Browser and Java Plug-In Requirements

Cluster Requirements and Guidelines

Catalyst 2900 XL and Catalyst 3500 XL Switches

Catalyst 3550 Switches

Catalyst 2950 Switches

Catalyst 1900 and Catalyst 2820 Switches

Minimum Cisco IOS Release for Major Features

New Software Feature

Enabling BPDU Filtering

Using the spanning-tree portfast Command

Syntax Description

Defaults

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

Limitations and Restrictions

IOS Restrictions

LRE Restrictions

CMS Restrictions

Important Notes

Open Caveats

Open IOS Caveats

Open LRE Caveat

Resolved Caveats

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

Documentation Notes

General Documentation Notes

Corrections to Software Configuration Guide

Additions to Software Configuration Guide

Correction to Command Reference

Corrections to Hardware Installation Guide

Updated Translated Warnings

Attaching the Cisco RPS (model PWR300-AC-RPS-N1)