Guest

Cisco Catalyst 2950 LRE Series Switches

Release Notes for the Catalyst 2950 LRE Switches and for Cisco IOS Release 12.1(11)YJ4

  • Viewing Options

  • PDF (508.4 KB)
  • Feedback
Release Notes for the Catalyst 2950 LRE Switches for Cisco IOS Release 12.1(11)YJ4

Table Of Contents

Release Notes for the Catalyst 2950 LRE Switches for Cisco IOS Release 12.1(11)YJ4

Contents

System Requirements

Supported Hardware

Unsupported Hardware

Software Compatibility

Creating Clusters with Different Releases of IOS Software

Downloading Software

Determining the Software Version and Feature Set

Determining Which Files to Use

Upgrading a Switch by Using CMS

Upgrading a Switch by Using the CLI

Downloading the Software and TFTP Server Application

Copying the Current Startup Configuration from the Switch to a PC or Server

Using the CLI to Upgrade a Catalyst 2950 LRE Switch

Recovering from Software Failure

Upgrading LRE Switch 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

New Features

New Hardware Features

New Software Features

Limitations and Restrictions

Hardware and Software Compatibility Matrixes

LRE Limitations

IOS Limitations

Cluster Limitation

CMS Limitations

Important Notes

CMS Notes

Hardware Support in CMS

Read-Only Mode in CMS

Configuring CMS

IOS Notes

Changing the Management VLAN

IGMP Filtering

Open Non-LRE Caveats

Open IOS Caveats

Open CMS Caveats

Open LRE Caveats

Resolved Non-LRE Caveats

Resolved Cluster Caveats

Resolved LRE Caveats

Documentation Updates

Addition to the Command Reference and Software Guide

cpe toggle

Correction to the Hardware Installation Guide

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 2950 LRE Switches for Cisco IOS Release 12.1(11)YJ4


May 2003

The Cisco IOS Release 12.1(11)YJ4 runs on Catalyst 2950 Long-Reach Ethernet (LRE) switches. This release should not be installed on non-LRE Catalyst 2950 switches.

These release notes include important information about this IOS release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:

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

If your switch is running, use the show version user EXEC command.

If you are upgrading to a new release, refer to the software upgrade filename for the IOS version.

For the complete list of Catalyst 2950 switch documentation, see the "Related Documentation" section.

This IOS release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future IOS releases become available, they will be posted to Cisco.com (previously Cisco Connection Online [CCO]) in the Cisco IOS software area.


Note Cisco IOS 12.1(11)YJ4 supports profiles that are compliant with the ETSI 997 bandplan.


Contents

These release notes contain these sections:

System Requirements

Downloading Software

Recovering from Software Failure

Upgrading LRE Switch Firmware

New Features

Limitations and Restrictions

Important Notes

Open Non-LRE Caveats

Open LRE Caveats

Resolved Non-LRE Caveats

Resolved Cluster Caveats

Resolved LRE Caveats

Documentation Updates

Related Documentation

Obtaining Documentation

Obtaining Technical Assistance

System Requirements

These sections describe system requirements:

Supported Hardware

Unsupported Hardware

Software Compatibility

Supported Hardware

The Cisco IOS Release 12.1(11)YJ4 supports the Catalyst 2950 LRE switches and the LRE customer premises equipment (CPE) devices.

Table 1 lists the hardware supported by this release:

Table 1 Supported Hardware

Hardware
Description

Catalyst 2950ST-24 LRE

24 LRE ports, 2 10/100/1000BASE-T ports, and 2 SFP ports

Catalyst 2950ST-8 LRE

8 LRE ports, 2 10/100/1000BASE-T ports, and 2 SFP ports

Catalyst 2950ST-24 LRE 997

24 LRE ports, 2 10/100/1000BASE-T ports, and 2 SFP ports with DC-input power

Cisco 575 LRE CPE

1 10/100 port

Cisco 576 LRE 997 CPE

1 10/100 port

Cisco 585 LRE CPE

4 10/100 ports

1000BASE-SX SFP Module
1000BASE-LX/LH SFP Module
100 BASE-ZX SFP Module

Small-form-factor pluggable (SFP) devices

Redundant power system

Cisco RPS 300 Redundant Power System
Cisco RPS 675 Redundant Power System1

1 Cluster Management Suite (CMS) does not support the RPS 675 in this release.


The Cisco RPS 675 Redundant Power System (model PWR675-AC-RPS-N1=) supports the
Catalyst 2950 LRE switches. For information about the Cisco RPS 675, refer to the Cisco RPS 675 Redundant Power System Hardware Installation Guide.

Unsupported Hardware

Table 2 lists the hardware that is not supported by this release:

Table 2 Unsupported Hardware 

Hardware
Description

Catalyst 2950-12

12 fixed autosensing 10/100 Ethernet ports

Catalyst 2950-24

24 fixed autosensing 10/100 Ethernet ports

Catalyst 2950C-24

24 fixed autosensing 10/100 Ethernet ports and 2 100BASE-FX ports

Catalyst 2950G-12-EI

12 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots

Catalyst 2950G-24-EI 

24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots

Catalyst 2950G-24-EI-DC

24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots with DC-input power

Catalyst 2950G-48-EI

48 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots

Catalyst 2950SX-24

24 fixed autosensing 10/100 Ethernet ports and 2 1000BASE-SX ports

Catalyst 2950T-24

24 fixed autosensing 10/100 Ethernet ports and 2 10/100/1000 Ethernet ports1

Gigabit Interface Converter (GBIC) modules

1000BASE-SX GBIC

1000BASE-LX/LH GBIC

1000BASE-ZX GBIC

1000BASE-T GBIC (model WS-5483)

1000BASE-T GBIC (model WS-G4582)

Coarse Wave Division Multiplexer (CWDM) fiber-optic GBIC

GigaStack GBIC

Redundant power system

Cisco RPS 600 Redundant Power System

1 The 10/100/1000 ports operate only in full-duplex mode.


Software Compatibility

For information about the recommended platforms for web-based management, operating systems and browser support, Java plug-in guidelines and installation procedures, refer to the Catalyst 2950 Desktop Switch Hardware Installation Guide.

Creating Clusters with Different Releases of IOS Software

Table 3 lists the cluster capabilities and software versions for the switches.

Table 3 Switch Software and Cluster Capability 

Switch
IOS Release
Cluster Capability

Catalyst 3550

Release 12.1(4)EA1 or later

Member or command switch

Catalyst 3500 XL

Release 12.0(5.1)XU or later

Member or command switch

Catalyst 2950

Release 12.0(5.2)WC(1) or later

Member or command switch

Catalyst 2950 LRE

Release 12.1(11)YJ or later

Member or command switch

Catalyst 2900 XL (8-MB switches)

Release 12.0(5.1)XU or later

Member or command switch

Catalyst 2900 XL (4-MB switches)

Release 11.2(8.5)SA6 (recommended)

Member switch only1

Catalyst 1900 and 2820

Release 9.00(-A or -EN)

Member switch only

1 Catalyst 2900 XL (4-MB) switches appear in the front-panel and topology views of CMS. However, CMS does not support configuration or monitoring of these switches.


Some versions of the Catalyst 2900 XL software do not support clustering, and if you have a cluster with switches that are running different versions of IOS software, software features added on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a Catalyst 2900 XL switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.1(11)YJ or later.


Note The CMS is not forward-compatible, which means that if a member switch is running a software version that is newer than the release running on the command switch, the new features are not available on the member switch. If the member switch is a new device supported by a software release that is later than the software release on the command switch, the command switch cannot recognize the member switch and it is displayed as an unknown device in the Front Panel view. You cannot configure any parameters or generate a report through CMS for that member; instead, you must launch the Device Manager application to perform configuration and obtain reports for that member.


Downloading Software

This section contains the following sections:

Determining the Software Version and Feature Set

Determining Which Files to Use

Upgrading a Switch by Using CMS

Upgrading a Switch by Using the CLI

For information about the software releases that support the Catalyst 2950 LRE switches, see the "Limitations and Restrictions" section.


Note Before downloading software, read this section for important information.


When you upgrade a switch, the switch continues to operate while the new software is copied to Flash memory. If Flash memory has enough space, the new image is copied to the selected switch but does not replace the running image until you reboot the switch. If a failure occurs during the copy process, you can still reboot your switch by using the old image. If Flash memory does not have enough space for two images, the new image is copied over the existing one. Features provided by the new software are not available until you reload the switch.

If a failure occurs while copying a new image to the switch, and the old image has already been deleted, refer to the "Recovering from Corrupted Software" section in the "Troubleshooting" chapter of the Catalyst 2950 Desktop Switch Software Configuration Guide for this release.

Determining the Software Version and Feature Set

The IOS image is stored as a .bin file in a directory that is named with the IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board Flash device (flash:). (The HTML and LRE binaries are located in the same directory as the IOS binary.)

You can use the show version user EXEC command to see the software version that is running on your switch. In the display, check the line that begins with System image file is. This line shows the directory name in Flash memory where the image is stored. A couple of lines below the image name, you see Running Enhanced Image if you are running the EI or Running Standard Image if you are running the SI.


Note Although the show version output always shows the software image running on the switch, the model name shown at the end of this display is the factory configuration and does not change if you upgrade the software image.


You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in Flash memory.

Determining Which Files to Use

The upgrade procedures in these release notes describe how to perform the upgrade by using a combined .tar file. This file contains both the IOS image file and the HTML files (needed for the CMS). You must use the combined .tar file to upgrade the switch through the CMS.

The .tar file is an archive file from which you can extract files by using the archive download-sw command.

Table 4 lists the software filenames for this IOS release.

Table 4 Catalyst 2950 IOS Software Files

Filename
Description

c2950lre-i6l2q4-mz.121-11.YJ4.bin

Catalyst 2950 LRE file

c2950lre-i6l2q4-tar.121-11.YJ4.tar

Catalyst 2950 LRE and CMS files

c2950lre-i6k2l2q4-mz.121-11.YJ4.bin

Catalyst 2950 LRE file that includes the crypto image

c2950lre-i6k2l2q4-tar.121-11.YJ4.tar

Catalyst 2950 LRE files that include the crypto image and the CMS files


Upgrading a Switch by Using CMS

You can upgrade switch software by using CMS. From the menu bar, select Administration > Software Upgrade. For detailed instructions, click Help.


Note You can also use Device Manager to upgrade a single switch by following the same software upgrade procedure.



Note Close your browser after the upgrade process is complete.


Upgrading a Switch by Using the CLI

To download switch software by using the CLI, follow these procedures in this order:

Decide which software files to download from Cisco.com (see the "Determining the Software Version and Feature Set" section).

Copy the current startup configuration file (see the "Copying the Current Startup Configuration from the Switch to a PC or Server" section).

If the upgrade to the new software fails or if the new startup configuration fails, you can reinstall the previous version of the switch software and use the copy of the startup configuration file to start the switch. If a failure occurs while copying a new image to the switch, and the old image has already been deleted, see the "Downloading Software" section.

If you are using the CLI to upgrade a Catalyst 2950 LRE switch, see the "Using the CLI to Upgrade a Catalyst 2950 LRE Switch" section.

If you are upgrading a member switch in a switch cluster, because a member switch might not be assigned an IP address, command-line software upgrades through TFTP are managed through the command switch.

Downloading the Software and TFTP Server Application

This procedure is for copying the combined .tar file to the Catalyst 2950 LRE switches. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.

For information about downloading a TFTP server, refer to the URLs in Step 2.

Follow these steps to download the software and, if necessary, the TFTP server application, from Cisco.com to your management station:


Step 1 Identify the files that you want to download.

Step 2 Download the files from one of these locations:

If you have a SmartNet support contract, go to this URL, and log in to download the appropriate files:

http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml

If you do not have a SmartNet contract, go to this URL, follow the instructions to register on Cisco.com, and download the appropriate files:

http://www.cisco.com/public/sw-center/sw-lan.shtml

To download the files, select Download Cisco Catalyst 2950 LRE software.

Step 3 Use the CLI or web-based interface to perform a TFTP transfer of the file or files to the switch after you have downloaded them to your PC or workstation.

The readme.txt file describes how to download the TFTP server application. New features provided by the software are not available until you reload the software.


Copying the Current Startup Configuration from the Switch to a PC or Server

The changes you make to a switch configuration become part of the running configuration. When you enter the command to save those changes to the startup configuration, the switch copies the configuration to the config.text file in Flash memory. To ensure that you can recreate the configuration if a switch fails, you might want to copy the config.text file from the switch to a PC or server.

This procedure requires a configured TFTP server such as the Cisco TFTP server available on Cisco.com.

Beginning in privileged EXEC mode, follow these steps to copy a switch configuration file to the PC or server that has the TFTP server application:


Step 1 Copy the file in Flash memory to the root directory of the TFTP server:

switch# copy flash:config.text tftp

Step 2 Enter the IP address of the device where the TFTP server resides:

Address or name of remote host []? ip_address

Step 3 Enter the name of the destination file (for example, config.text):

Destination filename [config.text]? yes/no

Step 4 Verify the copy by displaying the contents of the root directory on the PC or server.


Using the CLI to Upgrade a Catalyst 2950 LRE Switch

This procedure is for upgrading Catalyst 2950 LRE switches by using the archive download-sw privileged exec command to automatically extract and download the images to the switch. The archive download-sw command automatically deletes the old version and copies the new version to Flash if the Flash does not have space to store the old and new versions simultaneously. The archive download-sw command initiates this process:

It verifies adequate space on the Flash before downloading the new set of images.

If there is insufficient space on the Flash to hold both the old and the new images, it deletes the old set of images. The images are always stored in a sub-directory on the Flash. The sub-directory name is the same as the image release name, for example c2950lre-i6l2q4-mz.121-11.YJ.

It replaces the old set of images with the new set of images. The set includes the CMS and LRE firmwares. You do not have to manually delete the CMS directory from Flash.

After the new set is downloaded, it automatically sets the BOOT environment variable. You do not have to change the names of old file names to new file names.

If you invoke the command with the /reload or the /force-reload option, it automatically reloads the switch after the upgrade.

For further information on this command, see the command reference for this release.

Follow these steps to upgrade the switch software by using a TFTP transfer:


Step 1 If your PC or workstation cannot act as a TFTP server, copy the file to a TFTP server to which you have access.

Step 2 Access the CLI by starting a Telnet session or by connecting to the switch console port through the RS-232 connector.

To start a Telnet session on your PC or workstation, enter this command:

server% telnet switch_ip_address

Enter the Telnet password if you are prompted to do so.

Step 3 Enter privileged EXEC mode:

switch> enable 
switch#

Enter the password if you are prompted to do so.

Step 4 Display the name of the running (default) image file (BOOT path-list). This example shows the name in italic:

switch# show boot 
BOOT path-list:    flash:current_image 
Config file:       flash:config.text 
Enable Break:      1 
Manual Boot:       no 
HELPER path-list:  
NVRAM/Config file 
buffer size: 32768

Step 5 If there is no software image defined in the BOOT path-list, enter dir flash: to display the contents of Flash memory.

Step 6 Enter the archive download-sw /reload command.

Step 7 Press Return to confirm the reload.

Your Telnet session ends when the switch resets.

After the switch reboots, use Telnet to return to the switch, and enter the show version user EXEC command to verify the upgrade procedure. If you have a previously opened browser session to the upgraded switch, close the browser, and start it again to ensure that you are using the latest HTML files.


Recovering from Software Failure

If the software fails, you can reload it. For detailed recovery procedures, refer to the "Troubleshooting" chapter in the Catalyst 2950 Desktop Switch Software Configuration Guide for this release.

Upgrading LRE Switch Firmware

The Catalyst 2950 LRE switches can store and properly apply LRE binaries if in the future there are updates required to the firmware on the switches' local LRE controllers or connected CPE devices.

Other upgrade-related features include:

Access to an earlier version of the LRE software if required.

A simplified upgrade process, especially in cases where you want the ability to upgrade multiple CPE devices by issuing a single command.


Note Whether upgrading a single CPE device or all CPE devices connected to an LRE switch, the expected duration of an LRE upgrade is 3 to 6 minutes (CPE devices connected to marginal links might take longer than this to upgrade).


You perform an upgrade with this command:

hw-module slot module-slot number upgrade lre [force] [{local ctrlr unit number | remote interface-id}]

Automatic upgrading is not supported. You can upgrade in one of these ways:

Upgrade a single remote CPE device.

Upgrade a single local LRE controller (local LRE chipset).

Upgrade all CPE devices and local chipsets that require an upgrade (a system-wide upgrade, which is the default)


Note There are no LRE firmware upgrade patch files available with this release.


Configuring for an LRE Upgrade

In the absence of any LRE Upgrade configurations, the LRE upgrade attempts to upgrade all local LRE controllers and CPE devices to the most recent compatible versions of the LRE binaries required for each LRE target device. LRE upgrade configurations should rarely be required. The primary purpose of LRE upgrade configuration commands is to provide for downgrades of LRE binaries.

If you wish to override the switch's automatic selection of LRE binaries, you have two methods available:

Global LRE Upgrade configuration commands

LRE Controller configuration commands

You can use config global commands to specify the LRE binary or binaries for a specified target type. (A target type is the family [and optionally the model or model revision] of a device containing one or more upgradable hardware elements.) A target can be a local LRE controller on the switch or a remote CPE device.

You can perform global LRE upgrade configurations by issuing LRE upgrade controller configuration commands from the controller configuration mode. You can use the upgrade configuration command in the controller mode to override the system default selection of an LRE binary to be applied on a particular remote CPE device or local LRE controller. Controller configurations take precedence over global upgrade configurations.

The preserve keyword causes the LRE upgrade mechanism to not upgrade the local controller on which preserve is configured or any of the CPE devices connected to that controller. If you want to preserve (in other words, not upgrade) some of the CPE devices connected to a particular controller but allow upgrades to others, you can enter controller upgrade configuration commands for the links that you want to upgrade.

The no form of the upgrade command removes the command for applying a particular LRE binary. To resume default upgrade behavior for a given controller, configure the no upgrade commands on that controller.


Note You also need to remove global configurations that might also affect the controller and devices connected to it.



Note When a config global command and a config controller command conflict, the config controller command has precedence.


For further details, see the upgrade commands in the Catalyst 2950 Desktop Switch Command Reference for this release.

Performing an LRE Upgrade

You can upgrade either on a system-wide basis (in other words, upgrading the software on all connected CPE devices and local LRE chipsets) or on individual CPE device or LRE controllers. By default, a system-wide upgrade applies the most recent versions of LRE binaries that are most compatible with each upgradable hardware module. The system-wide upgrade method is the one that you use in almost all situations.

When executing upgrades, you can elect to upgrade a single CPE device or local controller by using this command hw-module slot <x> upgrade lre [local lo n | remote lo x/y]. If no local or remote option is given, a system-wide upgrade is performed.

Global Configuration of LRE Upgrades

Beginning in privileged EXEC mode, follow these steps to perform a system-wide upgrade to configure the LRE binary to apply to a target device and upgradable hardware element combination:

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

lre binary default target_device LRE_binary

Enter the device to which the LRE binary should be applied and the LRE binary to be applied.

Step 3 

end

Return to privileged EXEC mode.

Step 4 

show lre upgrade version

Verify the change.


Note The lre upgrade default mode command essentially overrides the system default selection of an LRE binary for a specified family of CPE devices (target device).


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:

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

controller lre chipset_number

Enter the particular LRE local chipset on the switch to be applied.

Step 3 

upgrade {LRE binary [remote lre-interface] | preserve}

Enter the LRE binary to be applied, or set preserve, which prevents the upgrade of any CPE devices connected to a controller or local chipset.

Step 4 

end

Return to privileged EXEC mode.

Step 5 

show lre upgrade version

Verify the change.

You can use the upgrade configuration command in the controller mode to override the system default selection of an LRE binary that will be applied on either end of a particular LRE link. Controller configurations take precedence over global upgrade configurations.

The preserve keyword causes the LRE upgrade mechanism to not upgrade the local controller on which preserve is configured or any of the CPE devices connected to that controller. If you want to preserve (in other words, not upgrade) some of the CPE devices connected to a particular controller but allow upgrades to others, you can enter controller upgrade configuration commands for the links you want to upgrade.

The no form of the command removes the command for applying a particular LRE binary. To resume default upgrade behavior for a given controller, do not configure the custom upgrade commands on that controller.

LRE Upgrade Behavior Details

You see on the console screen when you start an upgrade:

Switch>en
Switch#hw-module slot 0 upgrade lre
You 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:

When the upgrade starts, the link is probably in the link-up state, the state of the link that is useful to you.

When the upgrade starts, the remote CPE device resets. Ethernet connectivity is temporarily lost at this point.

The CPE device comes up, with the link slower (about 1 Mbps upstream and 4 Mbps downstream) but more reliable. The increased reliability is required for a successful LRE binary transfer. The LRE link stays at a slower speed for the duration of the upgrade. Ethernet connectivity is available.

When the upgrade is complete, the CPE device is again reset so that the upgraded LRE binaries are loaded and executed on the target CPE devices and local LRE chipsets. Ethernet connectivity is again disrupted until the CPE device finishes resetting.

The link comes up when the CPE device comes back up and progresses to where it resumes full operation at its intended data rate.

LRE Upgrade Example

This is an example of how an LRE upgrade can proceed:

Switch#hw-module slot 0 upgrade lre force remote lo 0/1
You are about to start an LRE upgrade on CPE Lo0/1.
Users on LRE links being upgraded will experience a temporary
disruption of Ethernet connectivity.

Start LRE upgrade ? [yes]:

Starting remote upgrade on CPE Lo0/1

Switch#
00:21:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface
LongReachEthernet0/1, changed state to down

The 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 up
00:22:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface
LongReachEthernet0/1, changed state to up

The CPE device finishes resetting. Ethernet connectivity is available but at low speeds. Upgrade data transfer begins.

00:23:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface
LongReachEthernet0/1, changed state to down

Upgrade data transfer is complete. Reset the CPE device.

00:23:56: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to up

The CPE device finishes resetting. The desired profile is applied.

00:23:58: %LRE_LINK-3-UPDOWN: Interface Lo0/1, changed state to UP
00:23:59: %LINK-3-UPDOWN: Interface LongReachEthernet0/1, changed state to up
00:24:02: %LINEPROTO-5-UPDOWN: Line protocol on Interface
LongReachEthernet0/1, changed state to up

Operation resumes in the profile link-up state.

Switch#

New Features

These are the new supported hardware and the new software features provided in Release 12.1(11)YJ4:

"New Hardware Features" section

"New Software Features" section

New Hardware Features

For a list of all supported hardware, see the "Supported Hardware" section.

New Software Features

Cisco IOS Release 12.1(11)YJ4 has these new features or enhancements:

The interleave feature —Provides maximum protection against small interruptions on the LRE link.

The upstream power back-off mechanism—Allows for normalization of the upstream receive power levels by requiring the CPE devices on shorter lines to transmit at a lower power level than the CPEs on longer lines.

Compliance with the VDSL 997 band plan for the Catalyst 2950ST-24 LRE 997 switch. Support for new profiles for the Catalyst 2950ST-24 LRE 997 switch.

Support for the CISCO-LRE-CPE-MIB. This MIB allows the user to manage the CPE Fast Ethernet ports and also provides the user with information about the MAC and CPE port mapping.

Support for new objects in the CISCO-IETF-VDSL-LINE-MIB. The cvdslLineConfProfile object in the CISCO-IETF-VDSL-LINE-MIB now allows a user to apply an LRE profile to an LRE interface.

Support for the IF-MIB link up/down traps for the CPE Fast Ethernet ports.

For detailed information on these features, refer to the Catalyst 2950 Desktop Switch Command Reference and Catalyst 2950 Desktop Switch Software Configuration Guide for this release.

Limitations and Restrictions

Review this section before you begin working with the switches. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.

This section contains the following sections:

Hardware and Software Compatibility Matrixes

LRE Limitations

IOS Limitations

Cluster Limitation

CMS Limitations

Hardware and Software Compatibility Matrixes

The Cisco LRE customer premises equipment (CPE) devices are not supported by certain Catalyst 2950 LRE switches. In Table 5, Yes means that the CPE is supported by the switch; No means that the CPE is not supported by the switch.

Table 5 LRE Switch and CPE Compatibility Matrix

LRE Devices
Catalyst 2950ST-8 LRE switch
Catalyst 2950ST-24 LRE switch
Catalyst 2950ST-24 LRE 997 switch

Cisco 575 LRE CPE

Yes

Yes

No

Cisco 576 LRE 997 CPE

No

No

Yes

Cisco 585 LRE CPE

Yes

Yes

No


The Catalyst 2950ST-24 LRE 997 switches are not supported by certain IOS releases. In Table 6, Yes means that the switch is supported by the IOS release; No means that the switch is not supported by the IOS release.

Table 6 LRE Switch Software Compatibility Matrix

Switch
Release 12.1(11)YJ2 and Release 12.1(11)YJ3
Release 12.1(11)YJ4 or later

Catalyst 2950ST-8 LRE

Yes

Yes

Catalyst 2950ST-24 LRE

Yes

Yes

Catalyst 2950ST-24 LRE 997

No

Yes


LRE Limitations

These are the LRE limitations:

VLAN-tagged packets from multiple VLANs with the same source MAC address received on different Cisco 585 LRE CPE Ethernet ports create a single MAC address (ingress port entry). Any network designed with the assumption that MAC addresses are maintained per VLAN does not work.

There is no workaround; the Ethernet switch on the Cisco 585 LRE CPE does not support VLANs. All the ports are assumed to be in the same VLAN. (CSCdx03708)

Maximum-sized ISL frames (frames between 1537 and 1544 bytes) are discarded by the CPE device on ingress. Some chips and switches on the CPE device support a maximum frame size of 1536 bytes, which causes any maximum-sized ISL frames coming into the CPE from an end device or from an LRE switch to be discarded.

There is no workaround. You must ensure that the network does not send ISL tagged frames of sizes between 1537 and 1544 bytes to an LRE switch. (CSCdx25940)

The system runs out of memory and fails after too many RMON buckets are requested.

There is no workaround; only 1000 buckets per interface are supported. (CSCdy38390)

The flow control auto-negotiation settles in the incorrect outcome if you use a Cisco-made 1000BASE-T GBIC with any switch not listed in the Table 1 of the 1000BASE-T GBIC Switch Compatibility Matrix:

http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/1000gbic/1000comp.htm.

The workaround is to use the Cisco 1000BASE-T GBIC only with compatible switches. (CSCdy53369)

The Flash write operation is slower on LRE switches than on non-LRE switches.

There is no workaround. (CSCdy55897)

The Cisco 585 LRE CPE has four Fast Ethernet ports. When the CPE is connected to an LRE switch, the default value for the maximum number of secure MAC addresses is 1. (You can use the show port-security command to display the current maximum value.)

The workaround is to use the switchport port-security maximum <value> interface configuration command to change the default value. For interfaces connected to Cisco 575 LRE CPEs, the default value of 1 is sufficient. For interfaces connected to Cisco 585 LRE CPEs, the value can be changed to 5, because the CPE has 4 Fast Ethernet ports and one additional MAC address for internal purposes. (CSCdy73748)

The Cisco 575 LRE CPE does not support all of the Fast Ethernet statistics displayed by the show controllers ethernet-controller longreachethernet 0/4 cpe command. (The Cisco 585 LRE CPE supports all the LRE and CPE Fast Ethernet statistics.)

There is no workaround. These CPE Fast Ethernet statistics are supported by the Cisco 575 LRE CPE (CSCdy89348):

1 Transmit receive 0 bytes

0 Bytes

0 Unicast frames

0 Broadcast frames

0 Pause frames

0 Alignment errors

0 One Collision frames

0 Multiple collisions

0 Undersize frames

0 Late collisions

0 Oversize Frames

0 Excess collisions

0 FCS errors

0 Deferred frames

When a 802.1X Protocol-enabled client attempts to connect to a Catalyst 2950 LRE switch through a CPE 585 with 802.1X configured on a port, the client cannot be authenticated. This problem does not affect the Cisco CPE 575. The show dot1x interface interface configuration command displays the port state as unauthorized.

There is no workaround. (CSCdz22965)

If a sequence is configured when an LRE interface is shut down on a Catalyst 2950 LRE switch running Cisco IOS Release 12.1(11)YJ2 or later, the sequence is not used for determining the profile. The switch attempts to re-establish the link through the default LRE-10.

The workaround is to configure a sequence only when the LRE interface is not shut down. (CSCea04914)

The CPE toggle feature automatically brings a customer premises equipment (CPE) Ethernet link from down to up if the LRE link comes up in less than 30 seconds. This feature is enabled by default. CPE toggle cannot be disabled on a Cisco 575 LRE or Cisco 576 LRE 997 CPE link.

You can now disable CPE toggle on a link from a Cisco 585 LRE CPE to a remote Ethernet device (such as PC). For more information, see the "Documentation Updates" section for more information. (CSCea55990)

There is no workaround; only 1000 buckets per interface are supported. (CSCdy38390)

When a Fast Ethernet port on a Cisco 585 LRE CPE is in half-duplex mode and the rate at which the port receives packets is higher than rate at which it can forward packets, the Pause Frames counter for the CPE port increments.

There is no workaround. (CSCea41362)

IOS Limitations

These are the IOS limitations:

When using the SPAN feature, the monitoring port receives copies of sent and received traffic for all monitored ports. If the monitoring port is oversubscribed, it will probably become congested. This might also affect how one or more of the monitored ports forward traffic.

If the storm control filter is enabled for unicast or multicast traffic and the rising threshold is reached, all traffic on the port is filtered. No unicast, multicast, or broadcast traffic is forwarded from the port.

There is no workaround. (CSCdp30543)

HSRP does not support a virtual MAC address entry or a built-in address (BIA) for a cluster.

There is no workaround. (CSCdp49419)

When changing the management VLAN on a cluster with command-switch redundancy enabled, the cluster can break if Hot Standby Router Protocol (HSRP) is configured on any of the cluster members in the new management VLAN.

The workaround is to not change the management VLAN to a VLAN in which a member is configured as part of a standby group. (CSCdp70389)

Root guard is inconsistent when configured on a port that is in the STP blocked state at the time of configuration.

There is no workaround. (CSCdp85954)

Cisco IOS software does perform some checks on entered IP addresses. For example, it does not allow the broadcast address to be entered. However, it does not check for the broadcast address on the same subnet as the HSRP Versatile Interface Processor (VIP) or the management VLAN IP address. This means that you could configure HSRP with a virtual IP address that is the same as the network broadcast address.

There is no workaround. (CSCdp87748)

All members of an HSRP standby group must be cluster members.

There is no workaround. (CSCdp97517)

Aging of dynamic addresses does not always occur exactly after the specified aging time elapses. It might take up to three times this time period before the entries are removed from the table.

There is no workaround. (CSCdr96565)

Internal loopback in half-duplex mode causes input errors. We recommend that you configure the Ethernet interface to operate in full-duplex mode before you set the internal loopback.

There is no workaround. (CSCds20365)

If the switch is configured from the dynamic IP pool, a duplicate or different IP address might be assigned.

The workaround is to make sure that the DHCP server contains reserved addresses that are bound to each switch by the switch hardware address so that the switch does not obtain its IP address from the dynamic pool. (CSCds58369)

A source-based distribution port group does not share the broadcast with all the group members. When the destination of the packets is a broadcast or unknown unicast or multicast, the packets are forwarded only on one port member of a port group, instead of being shared among all members of the port group.

There is no workaround. (CSCdt24814 [formerly CSCdt2481])

When you enter the show controllers ethernet-controller interface-id or show interfaces interface-id counters privileged EXEC command, if a large number of erroneous frames are received on an interface, the receive-error counts might be smaller than the actual values, and the receive-unicast frame count might be larger than the actual frame count.

There is no workaround. (CSCdt27223)

Two problems occur when the Catalyst 2950 switch is in transparent mode:

If the switch is a leaf switch, any new VLANs added to it are not propagated upstream through VTP messages. As a result, the switch does not receive flooded traffic for that VLAN.

If the switch is connected to two VTP servers, it forwards their pruning messages. If the switch has a port on a VLAN that is not requested by other servers through their pruning messages, it does not receive flooded traffic for that VLAN.

There is no workaround. (CSCdt48011)

If any VLAN other than VLAN 1 is configured as the management VLAN, the switch reports an incorrect shutdown for VLAN 1. VLAN 1 is not administratively down, even though the running configuration has shut down in VLAN 1.

There is no workaround. (CSCdt48569)

The receive count output for the show controllers ethernet-controller interface-id privileged EXEC command shows the incoming packet count before the ASIC determines whether to drop the packet or not. Therefore, for ports in the STP blocking states, the packet is not forwarded to the other port even though the receive count shows incoming frames.

There is no workaround. (CSCdu83640)

In some network topologies, when UplinkFast is enabled on all Catalyst 2950 switches and BackboneFast is not enabled on all switches, a temporary loop might occur when the STP root switch is changed.

The workaround is to enable BackboneFast on all switches. (CSCdv02941)

At times, the Windows XP pop-up window might not appear while authenticating a client (supplicant) because the user information is already stored in Windows XP. However, the Extensible Authentication Protocol over LAN (EAPOL) response to the switch (authenticator) might have an empty username that causes the 802.1X port to be deauthenticated.

The workaround is to manually re-initiate authentication by either logging off or detaching the link and then re-connecting it. (CSCdv19671)

If two Catalyst 2950 switches are used in a network and if access ports are used to connect two different VLANs whose VLAN IDs are separated by the correct multiple of 64, it is possible to create a situation where the two switches use the same bridge ID in the same spanning-tree instances. This might cause a loss of connectivity in the VLAN as the spanning tree blocks the ports that should be forwarding.

The workaround is to not cross-connect VLANs. For example, do not use an access port to connect VLAN 1 to VLAN 65 on either the same switch or from one switch to another switch. (CSCdv27247)

The Catalyst 2950 command switch might not show the Catalyst 1900, Catalyst 2820, and
Catalyst 2900 XL 4-MB (models C2908-XL, C2916M-XL, C2924C-XL, and C2924-XL) switches as candidates even though their management VLAN is the same as the command switch. This occurs only when their management VLAN is not VLAN 1.

There is no workaround. (CSCdv34505)

A Catalyst 2950 command switch running Release 12.1(6)EA2 cannot use the rcommand privileged EXEC command to start a Telnet session on a Catalyst 3550 member running
IOS Release 12.1(4)EA1, when the aaa authorization exec default group tacacs+ global configuration command is configured on both the command switch and the member.

The workaround is to upgrade the Catalyst 3550 switch to Release 12.1(6)EA1a. (CSCdv44005)

On a Catalyst 2950 switch, the Multicast VLAN Registration (MVR) receiver port joins only 255 groups when the Internet Group Management Protocol (IGMP) join message is sent to all 256 MVR groups configured. Multicast data for the 256th group is not received.

The workaround is to set the mode to dynamic for Catalyst 2950 switches that are connected to IGMP-capable devices. Then, MVR members can join any group but can only support 255 IP multicast streams at any given time. (CSCdv45190)

A Catalyst 2950 command switch can discover only the first Catalyst 3550 switch if the link between the Catalyst 3550 switches is an 802.1Q trunk and the native VLAN is not the same as the management VLAN of the Catalyst 2950 switch or if the link between the Catalyst 3550 switches is an ISL trunk and the management VLAN is not VLAN 1.

The workaround is to connect Catalyst 3550 switches by using the access link on the command switches management VLAN or to configure an 802.1Q trunk with a native VLAN that is the same as the management VLAN of the command switch. (CSCdv49871)

There might be a link on the Fast Ethernet port of the Catalyst 2950 switch when it is forced to 10 Mbps and full-duplex mode and its link partner is forced to 100 Mbps and forced duplex mode. The LED on the Catalyst 2950 switch might display the link, and the error counters might increment.

The workaround is to configure both sides of a link to the same speed or use auto-negotiation. (CSCdv62271)

The ip http authentication enable global configuration command is not saved to the configuration file because this is the default configuration. Therefore, this configuration is lost after a reboot.

The workaround is to manually enter the command again after a reboot. (CSCdv67047)

If a stack that has Catalyst 2950 switches also has Catalyst 2900 XL or Catalyst 3500 XL switches, cross-stack UplinkFast (CSUF) does not function if the management VLAN on the Catalyst 2900 XL or Catalyst 3500 XL switches is changed to a VLAN other than VLAN 1 (the default).

The workaround is to make sure that the management VLANs of all Catalyst 2900 XL or 3500 XL switches in the stack are set to VLAN 1. (CSCdv82224)

If a port is configured as a secure port with the violation mode as restrict, the secure ports might process packets even after maximum limit of MAC addresses is reached, but those packets are not forwarded to other ports.

There is no workaround. (CSCdw02638)

Follow these guidelines for applying access control lists (ACLs) to interfaces (CSCdw56650):

When you apply an ACL to a physical interface, some keywords are not supported, and certain mask restrictions apply to the ACLs. For information on creating ACLs for physical interfaces, refer to the "Creating a Numbered Standard ACL" section and the "Creating a Numbered Extended ACL" section of the Catalyst 2950 Desktop Switch Software Configuration Guide for Release 12.1(9)EA1.

You can apply ACLs to a management VLAN or to any traffic that is going directly to the CPU, such as SNMP, Telnet, or web traffic. For information on creating ACLs for these interfaces, refer to the "Configuring IP Services" section of the Cisco IOS IP and IP Routing Configuration Guide and the Command Reference for IOS Release 12.1.

When you set the c2900PortUseageApplication object value in the CISCO-C2900 MIB, to monitor, portgroupDest, portGrouping, network, or networkGroup, the setting is rejected.

The workaround for the monitor keyword is to use the CLI to configure a SPAN session.

The workaround for the portGroupDest and portGrouping values is to use the EtherChannel CLI commands to configure load balancing.

There are no workarounds for the network and networkGroup values. These are unsupported values. (CSCdx79221)

When the Internet Group Management Protocol (IGMP) Immediate-Leave is configured, new ports are added to the group membership each time a join message is received, and ports are pruned (removed) each time a leave message is received.

If the join and leave messages arrive at high rate, the CPU can become busy processing these messages. For example, the CPU usage is approximately 50 percent when 50 pairs of join and leave messages are received each second. Depending on the rate at which join and leave messages are received, the CPU usage can become very high, even up to 100 percent, as the switch continues processing these messages.

The workaround is to use the Immediate-Leave processing feature only on VLANs where a single host is connected to each port. (CSCdx95638)

A switch does not use the default gateway address in the DHCP offer packet from the server during automatic-install process.

The workaround is to manually assign an IP address to the switch. (CSCdy08716)

A Secure Shell (SSH) session does not terminate when the underlying transport is lost.

The workaround is to use the disconnect ssh command to terminate the SSH session. (CSCdy31309)

In a Remote Switched Port Analyzer (RSPAN) session, if at least one Catalyst 2950 switch is used as an intermediate or destination switch and if traffic for a port is monitored in both directions, traffic does not reach the destination switch. (CSCdy38476)

These are the workarounds:

Use a Catalyst 3550 or Catalyst 6000 switch as an intermediate or destination switch.

Monitor traffic in only one direction if a Catalyst 2950 switch is used as an intermediate or destination switch.

Assigning a non-existent VLAN identifier to a static access port-channel or EtherChannel by setting the ciscoVlanMembershipMIB:vmVlan object does not automatically create the VLAN in the VLAN database.

There is no workaround. (CSCdy65850)

If you issue a write configuration to NVRAM from a subdirectory, the configuration file is written in that subdirectory, causing the save configuration to not be applied when the switch is rebooted.

The workaround is to use the pwd command to verify that the current directory is the root directory before writing configuration to the NVRAM. (CSCdy69511)

If a Gigabit Ethernet port that belongs to an EtherChannel group is configured as a SPAN destination port, it is removed from the group. After the port is removed from the SPAN session, it does not rejoin the EtherChannel group and remains in the down or standalone state.

The workaround is to use the shutdown and then the no shutdown interface configuration commands to re-enable the Gigabit Ethernet port and allow the port to rejoin the EtherChannel. (CSCdy70771)

The Address Resolution Lookup (ARL) entries of the MAC table do not always timeout exactly after the specified aging time elapses. It can take up to three times this time period before the entries are removed from the table.

There is no workaround. (CSCdy75748)

When you use the show env all user EXEC command, it does not display information regarding temperature, power, and the RPS.

The workaround is to use the show rps privileged EXEC command to display the RPS information. There is no workaround to display the temperature and power information. (CSCdz83360)

Cluster Limitation

This is the cluster limitation:

When the cluster command switch is one of the following, the command switch does not find any cluster candidates beyond the Catalyst 2950 or 3550 switch if it is not a member of the cluster:

Catalyst 2900 XL switch

Catalyst 2950 switch running software earlier than Release 12.1(6)EA2

Catalyst 3500 XL switch that is connected to either a Catalyst 2950 switch running Release 12.1(6)EA2 or later or a Catalyst 3550 switch

The workaround is to add the Catalyst 2950 or 3550 switch to the cluster. You can then see any cluster candidates connected to it. (CSCdt09918)

CMS Limitations

These are the CMS limitations:

CMS requires a Java plug-in from Sun Microsystems. If you are using Internet Explorer and you disable Java plug-ins by using the Java Plug-In Control Panel, the initial Splash screen shows that the plug-in and Java are enabled, but Internet Explorer fails.

The workaround is to not disable Java plug-ins on the Java Plug-In Control Panel. (CSCdp67822)

You can use Cluster Manager to configure a HSRP standby group and bind it to a cluster. However, you cannot use Cluster Manager to configure more than one standby group. If you want to configure more than one standby group, use the CLI.

There is no workaround. (CSCdp82354)

The CMS Time Management window supports the configuration of the Network Time Protocol (NTP) and system time. When you make changes on this window from a command switch, Java propagates the changes to all cluster members. A conflict can arise if you configure NTP and also use the Set Daylight Saving Time and Set Current Time tabs.

To avoid a possible conflict, either set the system time for the entire cluster on the command switch, or configure NTP on the command switch to use an NTP server to provide time to the cluster. Do not use both methods at the same time. (CSCdp82224)

In the CMS topology view, icons for the fiber-optic, ATM, and FDDI links are not visible.

There is no workaround. (CSCdv56582)

When a Catalyst 2950 switch is the cluster command switch of a Catalyst 3550 member switch, the Catalyst 3550 switch does not show any egress policy information in the Attach tab of the QoS Policies window.

There is no workaround. (CSCdw01109)

You cannot switch modes (for example, from Guide Mode to Expert Mode) for an open CMS window.

The workaround is to close the open window, select the mode that you want, and then reopen the CMS window. (CSCdw87550)


Note For the mode change to take effect on any other CMS window that is open, you must close that window and then reopen it after you select the new mode.


The cursor is not displayed in the text-entering areas in CMS. However, in some cases you can still enter text. This problem occurs with certain combinations of both the browser and the Java plug-in. For example, it can occur when Netscape Communicator 6.2.3 is used with Java Plug-In 1.3.1_02 or 1.3.1_03.

These are the two workarounds:

Use a supported browser and Java plug-in. For more information, see the switch hardware guide.

Click in a text-entering area outside CMS, such as in the browser. Make sure that the cursor appears, and then click in the text-entering area in CMS. The cursor should now appear. If it does not, restart CMS by clicking on the reload/refresh button or by restarting the browser. (CSCdx94729)

When there are no CMS windows open, the CMS keyboard shortcuts do not work.

The workaround is to leave one CMS window open. For example, leave the Help > About window open. (CSCdy37017)

You cannot add a switch that does not have Terminal Access Control Access System Plus (TACACS+) configured on it to a cluster if all the other cluster members are configured with TACACS+.

The workaround is to configure TACACS+ on the switch before adding it to the cluster. (CSCdy36743)

If you use the command switch Domain Name System (DNS) server name to start CMS for a member that is running an earlier software release than the command switch, CMS might not display the switch image, or it might display the command switch image. This can also occur when a standby group is configured for a cluster and you access CMS by entering the command-switch IP address and not the virtual IP address.

The workaround is to always use the command-switch IP address to access CMS. If a standby group is configured for a cluster, always use the virtual IP address to access CMS. (CSCdp75220)

Important Notes

This section describes important information related to this IOS release. These sections are included:

CMS Notes

IOS Notes

CMS Notes

This section contains the following information:

Hardware Support in CMS

Read-Only Mode in CMS

Configuring CMS

Hardware Support in CMS

The Catalyst 2950ST-24 LRE 997 switch and the Cisco 576 LRE 997 CPE are not supported by CMS for the Cisco IOS Release 12.1(11)YJ4.

Read-Only Mode in CMS

CMS provides two levels of access to the configuration options. If your privilege level is 15, you have read-write access to CMS. If your switch privilege level is from 1 to 14, you have read-only access to CMS. In the read-only mode, some data is not displayed, and an error message appears when these switches are running these software releases:

Catalyst 2900 XL or Catalyst 3500 XL member switches running Release 12.0(5)WC2 or earlier

Catalyst 2950 member switches running Release 12.0(5)WC2 or earlier

Catalyst 3550 member switches running Release 12.1(6)EA1 or earlier

In the Front Panel view or Topology view, CMS does not display error messages. In the Front Panel view, if the switch is running one of the software releases listed previously, the device LEDs do not appear. In Topology view, if the member is a Long-Reach Ethernet (LRE) switch, the customer premises equipment (CPE) devices connected to the switch do not appear. The Bandwidth and Link graphs also do not appear in these views.

To view switch information, you need to upgrade the member switch software. For information about upgrading switch software, see the "Upgrading LRE Switch Firmware" section.

Configuring CMS

These notes apply to the CMS configuration:

If you use CMS on Windows 2000, it might not apply configuration changes if the enable password is changed from the CLI during your CMS session. You have to restart CMS and enter the new password when prompted. Platforms other than Windows 2000 prompt you for the new enable password when it is changed.

If you use Internet Explorer Version 5.5 and select a URL with a nonstandard port at the end of the address (for example, www.add.com:84), you must enter http:// as the URL prefix. Otherwise, you cannot launch CMS.

Within an ACL, you can change the sequence of ACEs that have the host keyword. However, because such ACEs are independent of each other, the change has no effect on the way the ACL filters traffic.

If you use the Netscape browser to view the CMS GUI and you resize the browser window while CMS is initializing, CMS does not resize to fit the window.

Resize the browser window again when CMS is not busy.

IOS Notes

This section contains the following information:

Changing the Management VLAN

IGMP Filtering

Changing the Management VLAN

The management interface configuration command is not supported in Release 12.1(6)EA2 or later. To shut down the current management VLAN interface and to enable the new management VLAN interface, use the shutdown and no shutdown interface configuration commands. Refer to the Catalyst 2950 Desktop Switch Command Reference for information about using the shutdown interface configuration command.

IGMP Filtering

IGMP filtering controls only group specific query and membership reports, including join and leave reports. It does not control general IGMP queries.

Open Non-LRE Caveats

This sections contains the following non-LRE open caveats in this release:

Open IOS Caveats

Open CMS Caveats

Open IOS Caveats

These are the IOS configuration caveats:

CSCdz06748

When the switch gets the entPhysicalTable MIB object, it does not include the copper physical entry.

There is no workaround.

CSCdx86397

The show interfaces privileged EXEC command might display incorrect information for the 10/100/1000 interfaces.

The workaround is to make sure that the management VLANs of all Catalyst 2900 XL or 3500 XL switches in the stack are set to VLAN 1.

CSCdx75308

When you use the policy-map global configuration command to create a policy map, and you do not specify any action for a classmap, the association between that class map and policy map is not saved when you exit policy-map configuration mode.

The workaround is to specify an action in the policy map.

CSCdx93122

The default VLANs cannot be removed from the allowed list on a trunk port, and only one management VLAN can be active at a time.


Note Any VLAN can be removed except for the default VLANs 1002 to 1005.


The workaround is to have only one active management VLAN at a time.

CSCdy61865

If two switch ports in two different VLANs are connected to each other, both switch ports continue forwarding. If two additional ports in the two different VLANs are connected together, a loop is formed.

The workaround is to remove the loop from the switch.

CSCdw06074

Layer 3 CPU packets from a SPAN-source port configured to monitor sent traffic are not mirrored to the SPAN-destination port on a Catalyst 2950 switch.

There is no workaround.

CSCdt83016

When the Catalyst 2950 switch boots up without being configured, it prompts the user with a configuration dialog. The switch allows the user to omit the dialog and to enable traps without configuring a community string. If the host trap receiver is configured without defining the community strings, when the switch attempts to generate a trap, it fails and displays an error message.

The workaround is to follow the configuration sequence by creating a community string before configuring traps for the host.

Open CMS Caveats

These are the CMS configuration caveats:

CSCdy88328

The speed and duplex parameters for Gigabit Ethernet ports can be modified and effective only when the copper link is active. You cannot modify these parameters from the Port Settings dialog in CMS.

The workaround is to use command line interface to perform this configuration.

CSCdx88968

In read-only mode, time ranges are not displayed. See the "CMS Notes" section for more information about CMS modes.

There is no workaround.

CSCdy17589

If you try to create a time-range entry that specifies multiple days with the same time, the CMS displays only the first day in the list of days. This is an example of such a time-range entry:

periodic Monday Wednesday Friday 8:00 to 17:00.

The periodic time-range entries with specific days use this syntax:

periodic Monday 8:00 to Tuesday 17:00.

or

periodic Monday 8:00 to Monday 17:00

The workaround is to create a specific time-range entry for each day.

CSCdx76634

The data that is displayed by using the Stack Bar and Stack Area options in the Link Graph window is incorrect.

The workaround is to use the Line, Bar, or Area options instead.

CSCdy47214

You cannot add a class to a new policy when you launch Device > QoS > Policies in Guide Mode.

The workaround is to launch Device > QoS > Policies in Expert Mode, and then add the class to the policy.

CSCdz01037

CMS does not work when a switch is running the crypto software image, and the virtual terminal (VTY) lines have been configured to use only SSH by using the transport input ssh line vty 0 15 interface configuration command.

The workaround is to allow SSH and Telnet access through the VTY lines by using the transport input ssh telnet interface configuration command.

Open LRE Caveats

These are the open LRE caveats in this release:

CSCeb13751

The show controllers lre status profile and the show controllers lre profile details privileged EXEC commands display incorrect profile information if these CPEs and switches are connected:

A Cisco 576 LRE 997 CPE is connected to a Catalyst 2950ST-24 LRE or a
Catalyst 2950ST-8 LRE switch

A Cisco CPE 575 LRE or a Cisco 585 LRE CPE is connected to a Catalyst 2950ST-24 LRE 997 switch.

There is no workaround.

CSCea61743

On a Catalyst 2950 LRE switch running Release 12.1(11)YJ4, the show controllers lre status psd privileged EXEC commands might display incorrect TX power values. The value displayed is 1.3 decibels (dB) less than the actual value.

The workaround is to add 1.3 dB to the displayed TX value.

CSCea66569

On a Catalyst 2950 LRE switch running Release 12.1(11)YJ4, an LRE port that is placed in the error-disabled state disables traffic only in one direction instead of disabling traffic in both directions.

The workaround is to enter the shutdown and then the no shutdown interface configuration commands to bring the port out of the error-disabled state. Once the link is up, traffic flows in both directions.

CSCdz12040

Entering the no snmp-server global configuration command might cause a Catalyst 2950 LRE switch to fail if it is not configured with an IP address.

There is no workaround.

CSCdz06748

The copper physical entry is not included when the entPhysicalTable object is retrieved.

There is no workaround.

CSCdz16246

The Gigabit Ethernet ports of a Catalyst 2950 LRE switch might get into err-disabled state when the plastic SFPs are first installed.

The workaround is to enter the shutdown followed by the no shutdown interface configuration commands.

CSCeb01097

On a Catalyst 2950 LRE switch running Release 12.1(11)YJ4, a Cisco 575 LRE CPE or a
Cisco 576 LRE 997 CPE that does not have an LRE link but is connected to a remote device through the Ethernet link might see repeated flaps on the Ethernet link. This does not apply to the Cisco 585 LRE CPE.

There is no workaround.

Resolved Non-LRE Caveats

These IOS caveats were resolved in Release 12.1(11)YJ4:

CSCds68177

The UniDirectional Link Detection (UDLD) protocol now detects a unidirectional link when there is a loop between the TX and RX strands on the same port (TX/RX loop condition).

CSCdy75445

When a loopback interface is created and the no shutdown interface configuration command is applied on that interface, the Catalyst 2950 switch no longer crashes.

CSCdz82994

When the aaa new-model and some vlan options are configured on a switch, this message no longer appears:

%AAAA-3-INVALIDLIST 

CSCdz37442

A switch no longer reloads when Internet Group Management Protocol (IGMP) packets are received on an EtherChannel.

CSCdy18989

The BPDU filtering feature on Port Fast-enabled ports now works as described in the Catalyst 2950 LRE software documentation. If a BPDU is received on a Port Fast-enabled port, the port loses its Port Fast-operational status, and BPDU filtering is disabled.

This IOS caveat was resolved in Release 12.1(11)YJ2:

CSCdy30410

When a Catalyst 2950 switch becomes a command switch, it automatically creates an IP extended ACL called CMP-NAT-ACL that specifies a set of IP addresses subject to cluster-NAT address translation. CMS now does not allow you to modify or delete this ACL.

This IOS caveat was resolved in Release 12.1(11)YJ1:

CSCdz64672

A security fix prevents incorrectly-formed Secure Shell (SSH) packets from halting a switch.

For more information, refer to this URL:

http://www.cisco.com/warp/public/707/ssh-packet-suite-vuln.shtml

Resolved Cluster Caveats

This cluster caveats was resolved in Release 12.1(11)YJ4:

CSCdw10837

When a Catalyst 2950 cluster command switch is running Release 12.1(6)EA2 or later and you enter the no cluster commander-address global configuration command on a member switch of this cluster, the member switch can now be removed from the cluster if there are any member switches beyond that member switch.

Resolved LRE Caveats

These LRE caveats were resolved in Release 12.1(11)YJ4:

CSCdz68590

Release 12.1(11)YJ4 now supports the profiles that are compliant with the ETSI 997 bandplan.

CSCea16410

When the Catalyst 2950 LRE switch is powered on, the front panel LEDs on the LRE ports no longer remain on and now display the correct link status.

CSCea53498

The %SM-4-BADEVENT:Event 'auth_reauth' is invalid for the current state 'access_dynamic' system error message is no longer displayed on the Catalyst 2950 LRE switch when these conditions occur:

The switch is running IOS 12.1(11)YJ2 or later.

The LRE interface is configured as a dynamic access port.

The Cisco 575 CPE is connected to the LRE interface, and the link goes down on the Ethernet port of the CPE device.

CSCea53498

When the LRE interface on a Catalyst 2950 LRE switch configured as a dynamic access port is connected to a Cisco 575 CPE, the Catalyst 2950 LRE switch no longer reports a line protocol down followed by a line protocol up when a Fast Ethernet port on a Cisco 575 CPE loses the link and regains the link.

CSCdy87390

When IGMP snooping is enabled on a switch, and the switch receives an IGMP report from a client port and sends the packet to a router port, the switch no longer adds a 4-byte frame check sequence (FCS) to the end of the frame.

CSCeb01154

The Fast Ethernet port on the Cisco 575 CPE and the Cisco 576 CPE 997 no longer flaps when you oversubscribe the LRE link.

This LRE caveat was resolved in Release 12.1(11)YJ3:

CSCea50416

If a Catalyst 2950 LRE switch is upgraded to Release 12.1(11)YJ3 and the switch restarts, the link between a Gigabit Ethernet port on the switch and an attached device is no longer down.

These LRE caveats were resolved in Release 12.1(11)YJ2:

CSCdz21936

When an 802.1X client connected to a Cisco 575 LRE CPE has been authorized by a Catalyst 2950 LRE switch to connect to a port and the Ethernet link between the Cisco 575 LRE CPE and the client drops, the switch marks that port as unauthorized.

CSCdz41800

Protected port settings are no longer lost after a Cisco 585 LRE CPE is power cycled.

CSCea04269

The LRE ports no longer experience reach problems. The LRE ports operate within the SNR requirements as described in the "Link Qualification and SNR Margins" section in the "Configuring LRE" chapter of the Catalyst 2950 Desktop Switch Software Configuration Guide.

Documentation Updates

You can access all Catalyst 2950 documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/index.htm

This section provides updates to the product documentation.

Addition to the Command Reference and Software Guide

These changes will be included in the next version of the documentation.

The CPE toggle feature was omitted in the Catalyst 2950 Desktop Switch Command Reference and Catalyst 2950 Desktop Switch Software Configuration Guide.

The CPE toggle feature automatically brings a CPE Ethernet link from down to up if the LRE link comes up in less than 30 seconds. This feature is enabled by default. CPE toggle cannot be disabled on a
Cisco 575 LRE or Cisco 576 LRE 997 CPE link. You can disable CPE toggle on a link from a Cisco 585 LRE CPE to a remote Ethernet device (such as PC). If you disable this feature on a Cisco 585 LRE
CPE, the CPE Ethernet link does not transition to the up state when the LRE link comes up.

cpe toggle

Use the cpe toggle interface configuration command to enable the CPE toggle feature. When this feature is enabled, a remote customer premises equipment (CPE) link automatically transitions from down to up if the LRE link comes up in less than 30 seconds. Use the no form of this command to disable the CPE toggle feature on a specific port or on the switch.

cpe toggle [port cpe-port-id]

no cpe toggle [port cpe-port -id]

Syntax Description

port cpe-port-id

(Optional) The CPE port identifier. Valid values are from 1 to 4.


Defaults

CPE toggle is enabled on all interfaces.

Command Modes

Interface configuration

Command History

Release
Modification

12.1(11)YJ

This command was introduced.


Usage Guidelines

A CPE Ethernet link is the connection between the CPE Ethernet port and the remote Ethernet device (such as a PC) connected to it. It is not the link between the switch LRE port and the LRE CPE device, which is referred to as the LRE link.

CPE toggle cannot be disabled on a Cisco 575 LRE or Cisco 576 LRE 997 CPE link.

You can disable CPE toggle on a link from a Cisco 585 LRE CPE to a remote Ethernet device. You can disable CPE toggle on all interfaces or on a specific interface by using the no cpe toggle [port cpe-port-id] interface configuration command. If CPE toggle is disabled and the LRE link comes up in less than 30 seconds, the CPE link transitions from down to up.

If the port keyword is not specified, this command applies to all Fast Ethernet ports on a CPE device. If the port keyword and a port ID are specified, this command applies to the specific Fast Ethernet port on the CPE and overrides the global configuration.

Examples

This example shows how to disable CPE toggle on a CPE port:

Switch# configure terminal
Switch(config)# interface longreachethernet 0/2
Switch(config-if)# no cpe toggle

Related Commands

Command
Description

show running-config

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


Correction to the Hardware Installation Guide

These changes will be included in the next version of the Catalyst 2950 Desktop Switch Hardware Installation Guide.

The front panel of the Catalyst 2950ST-24 LRE 997 switch is incorrect in Figure 2-10 on page 2-8, Figure 2-17 on page 2-20, and Figure 3-37 on page 3-43. Figure 1 shows the correct switch front panel:

Figure 1 Front Panel of the Catalyst 2950ST-24 LRE 997 Switch

Use Figure 1 to identify the positive and negative feed positions for the terminal block connection, as described in Step 2 of the "Wiring the DC-Input Power Source" section in the "Connecting to DC Power" appendix of the switch hardware installation guide. Insert the wires into the Terminal Block Plug as shown in Figure C-9 on page C-10.

Related Documentation

These documents provide complete information about the switch and are available from this Cisco.com site:

http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/index.htm

The software documents are not shipped with the product, but you can access them under the appropriate IOS software release on Cisco.com. You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the "Obtaining Documentation" section.

These publications provide more information about the switches:

Release Notes for the Catalyst 2950 Switch for Cisco IOS Release 12.1(11)EA1

Catalyst 2950 Desktop Switch Software Configuration Guide (order number DOC-7814982=)

Catalyst 2950 Desktop Switch Command Reference (order number DOC-7814984=)

Catalyst 2950 Desktop Switch System Message Guide (order number DOC-78114981=)

Catalyst 2950 Desktop Switch Hardware Installation Guide (order number DOC-7811157=)

Cluster Management Suite (CMS) online help

Cisco LRE CPE Hardware Installation Guide (order number DOC-7811469=)

Installation and Warranty Notes for the Cisco LRE 48 POTS Splitter (order number DOC-7812250=)

Cisco Small Form-Factor Pluggable Modules Installation Notes (not orderable but is available on Cisco.com)

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:

http://www.cisco.com

International Cisco websites 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 regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order monthly or quarterly subscriptions 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:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

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 comments by using the response card (if present) 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-9883

We 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:

Streamline business processes and improve productivity

Resolve technical issues with online support

Download and test software packages

Order Cisco learning materials and merchandise

Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:

http://tools.cisco.com/RPF/register/register.do

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The type 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:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. There is little or no impact to your business operations.

Priority level 3 (P3)—Operational performance of the network is impaired, but most business operations remain functional. You and Cisco are willing to commit resources during normal business hours to restore service to satisfactory levels.

Priority level 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively impacted by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority level 1 (P1)—An existing network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Cisco TAC Website

The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

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/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation 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 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.

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/go/packet

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html