Guest

Cisco ME 2400 Series Ethernet Access Switches

Release Notes for the Cisco ME 2400 Ethernet Access Switches, Cisco IOS Release 12.2(35)SE1 and Later

  • Viewing Options

  • PDF (364.3 KB)
  • Feedback
Release Notes for the Cisco ME 2400 Ethernet Access Switches, Cisco IOS Release 12.2(35)SE1 and Later

Table Of Contents

Release Notes for the
Cisco ME 2400 Ethernet Access Switches, Cisco IOS Release 12.2(35)SE1 and Later

Contents

System Requirements

Hardware Supported

Upgrading the Switch Software

Finding the Software Version and Feature Set

Deciding Which Files to Use

Archiving Software Images

Upgrading a Switch

Recovering from a Software Failure

Installation Notes

New Features

New Hardware Features

New Software Features

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Configuration

QoS

SPAN and RSPAN

Trunking

VLAN

Open Caveats

Resolved Caveats

Caveats Resolved in Cisco IOS Release 12.2(35)SE5

Caveats Resolved in Cisco IOS Release 12.2(35)SE2

Caveats Resolved in Cisco IOS Release 12.2(35)SE1

Documentation Updates

Updates to the Command Reference and Software Configuration Guide

EtherChannel

QoS Update

MVR over Trunk Ports

mvr (interface configuration)

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for the
Cisco ME 2400 Ethernet Access Switches, Cisco IOS Release 12.2(35)SE1 and Later


Revised June 10, 2008

Cisco IOS Release 12.2(35)SE1, 12.2(35)SE2, and 12.2(35)SE5 run on the Cisco ME 2400 Series Ethernet Access switches.

These release notes include important information about Cisco IOS Release 12.2(35)SE1, and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:

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

If your switch is on, use the show version privileged EXEC command. See the "Finding the Software Version and Feature Set" section.

If you are upgrading to a new release, see the software upgrade filename for the software version. See the "Deciding Which Files to Use" section.

For the complete list of Cisco ME 2400 switch documentation, see the "Related Documentation" section.


Note The system message guide for this release refers to Cisco IOS Release 12.2(35)SE, but applies to Cisco IOS Release 12.2(35)SE1 and later.


You can download the switch software from this site (registered Cisco.com users with a login password):

http://www.cisco.com/cgi-bin/Software/Iosplanner/Planner-tool/iosplanner.cgi

This software 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 software releases become available, they will be posted to Cisco.com in the Cisco IOS software area.

Contents

This information is in the release notes:

"System Requirements" section

"Upgrading the Switch Software" section

"Installation Notes" section

"New Features" section

"Minimum Cisco IOS Release for Major Features" section

"Limitations and Restrictions" section

"Open Caveats" section

"Resolved Caveats" section

"Documentation Updates" section

"Related Documentation" section

"Obtaining Documentation, Obtaining Support, and Security Guidelines" section

System Requirements

The system requirements are described in this section:

"Hardware Supported" section

Hardware Supported

Table 1 lists the hardware supported on Cisco IOS Release 12.2(35)SE1 and SE2.

Table 1 Supported Hardware 

Device
Description
Supported by Minimum Cisco IOS Release

ME-2400-24TS-A

24 10/100 ports and 2 SFP module slots, AC power

Cisco IOS Release 12.2(250EX

ME-2400-24TS-D

24 10/100 ports and 2 SFP module slots, DC power

Cisco IOS Release 12.2(250EX

SFP modules

1000BASE-T, -BX, -SX, -LX/LH, -ZX
100BASE-BX, FX, -LX
Coarse wavelength-division multiplexing (CWDM)

Cisco IOS Release 12.2(25)EX

Cable

Catalyst 3560 SFP interconnect cable

Cisco IOS Release 12.2(25)EX


Upgrading the Switch Software

These are the procedures for downloading software. Before downloading software, read this section for important information:

"Finding the Software Version and Feature Set" section

"Deciding Which Files to Use" section

"Archiving Software Images" section

"Upgrading a Switch" section

"Recovering from a Software Failure" section

Finding the Software Version and Feature Set

The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. The image is stored on the system board flash device (flash:).

You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.

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.

Deciding 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 the Cisco IOS image file. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.

Table 2 lists the filenames for this software release.

Table 2 Cisco IOS Software Image Files 

Filename

Description

me240x-metrobase-tar.122-35.SE5.tar

Cisco ME 2400 metro base image.
This image has basic Metro Ethernet features.

me240x-metrobasek9-tar.122-35.SE5.tar

Cisco ME 2400 metro base cryptographic image.
This image has the Kerberos, Secure Shell (SSH), and basic Metro Ethernet features.


Archiving Software Images

Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.

Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:

http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html

You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.

You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 at this URL:

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_command_reference_chapter09186a00800ca744.html#wp1018426

Upgrading a Switch

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


Note For downloading software, we recommend that you connect to the TFTP server through a network node interface (NNI). If you want to connect to the server through a user network interface (UNI), see the "Troubleshooting" chapter of the software configuration guide for methods for enabling ping capability on UNIs. See the "New Software Features" section for a definition of NNIs and UNIs.


To download software, follow these steps:


Step 1 Use Table 2 to identify the file that you want to download.

Step 2 Download the software image file. If you have a SmartNet support contract, log in to cisco.com and go to this URL, and log in to download the appropriate files:

http://www.cisco.com/cgi-bin/Software/Iosplanner/Planner-tool/iosplanner.cgi

Click on "Launch the IOS Upgrade Planner" and search for ME 2400to download the appropriate files:

To download the image for a Cisco ME 2400 switch, click Cisco ME 2400 software.

To obtain authorization and to download the cryptographic software files, click Cisco ME 2400 3DES Cryptographic Software.

Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.

For more information, refer to Appendix B in the software configuration guide for this release.

Step 4 Log into the switch through the console port or a Telnet session.

Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering this privileged EXEC command:

Switch# ping tftp-server-address


Note By default, ping is supported on network node interfaces (NNIs), but you cannot ping from a user network interface (UNI) because the control-plane security feature drops ICMP response packets received on UNIs. See the "Troubleshooting" chapter of the software configuration guide for methods for pinging from the switch to a host connected to a UNI.


For more information about assigning an IP address and default gateway to the switch, refer to the software configuration guide for this release.

Step 6 Download the image file from the TFTP server to the switch. If you are installing the same version of software that is currently on the switch, overwrite the current image by entering this privileged EXEC command:

Switch# archive download-sw /overwrite /reload 
tftp:[[//location]/directory]/image-name.tar

The /overwrite option overwrites the software image in flash memory with the downloaded one.

The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.

For //location, specify the IP address of the TFTP server.

For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.

This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:

Switch# archive download-sw /overwrite 
tftp://198.30.20.19/me240x-metrobase-tar.122.35.SE1.tar

You can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.


Recovering from a Software Failure

For recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.

Installation Notes

You can assign IP information to your switch by using these methods:

The CLI-based setup program, as described in the switch hardware installation guide.

The DHCP-based autoconfiguration, as described in the switch software configuration guide.

Manually assigning an IP address, as described in the switch software configuration guide.

New Features

These sections describe the new supported hardware and the new software features provided in this release:

"New Hardware Features" section

"New Software Features" section

New Hardware Features

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

New Software Features

These are the new software features for Cisco IOS Release 12.2(35)SE1:

Support for one output policy map for each interface (with only three unique queue-limit configurations)

Support for Multicast VLAN Registration (MVR) over trunk ports to allow you to configure a trunk port as an MVR receiver port

Minimum Cisco IOS Release for Major Features

Table 3 lists the minimum software release (after the first release) required to support the major features of the Cisco ME 2400 switch. Features not listed are supported in all releases.

Table 3 Features Introduced After the First Release and the Minimum Cisco IOS Release Required 

Feature
Minimum Cisco IOS Release Required

Support for Multicast VLAN Registration (MVR) over trunk ports

12.2(35)SE1

DHCP server

12.2(25)SEG

DHCP Option-82 configurable remote ID and circuit ID

12.2(25)SEG

Multiple spanning-tree (MST) based on the IEEE 802.1s standard

12.2(25)SEG

Secure Copy Protocol

12.2(25)SEG


Limitations and Restrictions

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

These limitations apply to the Cisco ME switches:

"Configuration" section

"QoS" section

"SPAN and RSPAN" section

"Trunking" section

"VLAN" section

Configuration

These are the configuration limitations:

A static IP address might be removed when the previously acquired DHCP IP address lease expires.

This problem occurs under these conditions:

When the switch is booted without a configuration (no config.text file in flash memory).

When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1).

When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires.

The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)

The DHCP snooping binding database is not written to flash memory or a remote file in any of these situations:

When the Network Time Protocol (NTP) is configured, but the NTP clock is not synchronized. You can check the clock status by entering the show NTP status privileged EXEC command and verifying that the network connection to the NTP server and the peer work correctly.

The DHCP snooping database file is manually removed from the file system. After enabling the DHCP snooping database by configuring a database URL, a database file is created. If the file is manually removed from the file system, the DHCP snooping database does not create another database file. You need to disable the DHCP snooping database and enable it again to create the database file.

The URL for the configured DHCP snooping database was replaced because the original URL was not accessible. The new URL might not take effect after the timeout of the old URL.

No workaround is necessary; these are the designed behaviors. (CSCed50819)

When port security is enabled on an interface in restricted mode and the switchport block unicast interface command has been entered on that interface, MAC addresses are incorrectly forwarded when they should be blocked

The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)

A traceback error occurs if a crypto key is generated after an SSL client session.

There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)

If an IGMP report packet has two multicast group records, the switch removes or adds interfaces depending on the order of the records in the packet:

If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the switch removes the port from the group.

If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the switch adds the port to the group.

There is no workaround. (CSCec20128)

When IGMP snooping is disabled and you enter the switchport block multicast interface configuration command, IP multicast traffic is not blocked.

The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.

There is no workaround. (CSCee16865)

QoS

This is a quality of service (QoS) limitation:

CSCsb98219

When you use the bandwidth policy-map class command to configure more than one class in a policy map for Class-based Weighted Fair Queuing (CBWFQ), and the committed information rate (CIR) bandwidth for any of the classes is less than 2 percent of the interface rate, the CBWFQ classes in the policy may not receive the configured CIR bandwidths.

There is no workaround, but it is unlikely that a CBWFQ class would be configured with such a low CIR bandwidth.

SPAN and RSPAN

This is the SPAN limitation:

Cisco Discovery Protocol (CDP) and Port Aggregation Protocol (PAgP) packets received by network node interfaces (NNIs) from a SPAN source are not sent to the destination interfaces of a local SPAN session. The workaround is to use the monitor session session_number destination {interface interface-id encapsulation replicate} global configuration command for local SPAN. (CSCed24036)

Trunking

These are the trunking limitations:

IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the output interface for the multicast route entry assigned to the multicast group and an interface in VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no workaround. (CSCdz42909).

For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not counted on the interface statistics. There is no workaround. (CSCec35100).

VLAN

These are the VLAN limitations:

If the number of VLANs times the number of trunk ports exceeds the recommended limit of 5,000, the switch can fail.

The workaround is to not configure more than the recommended number of VLANs and trunks. (CSCeb31087)

A CPUHOG message sometimes appears when you configure a private VLAN. Enable port security on one or more of the ports affected by the private VLAN configuration.

There is no workaround. (CSCed71422)

Open Caveats

This section describes the open caveats in this software release.

CSCse11323

When 256 policy maps are configured globally on the system, the creation of the 257th policy map is rejected. The platform supports a maximum of 256 policy maps. If you then delete some existing policy maps and again configure the rejected policy map, when you try to attach that policy map to an interface, it might be rejected without any descriptive error message explaining the reason for the rejection or with an unexpected and incorrect error message.

The workaround is to delete the problematic policy map and to reconfigure it with a different name. The new policy map should be accepted as expected.

CSCsg36159

When using the CLI, you can configure a qualified queue-limit under class-default for the policy map even though the configuration is not supported.

The workaround is to only use qualified queue-limits under nondefault classes.

Resolved Caveats

These sections describe the caveats have been resolved in these releases:

Caveats Resolved in Cisco IOS Release 12.2(35)SE5

Caveats Resolved in Cisco IOS Release 12.2(35)SE2

Caveats Resolved in Cisco IOS Release 12.2(35)SE1

Caveats Resolved in Cisco IOS Release 12.2(35)SE5

These caveats are resolved in Cisco IOS Release 12.2.(35)SE5:

CSCed87897

The output of the show ip route privileged EXEC command now correctly displays the default gateway.

CSCsh89429

The switch no longer reloads when the write core privileged EXEC command is entered when testing a core dump configuration and FTP is selected as the file transfer protocol.

CSCsi74508

A switch no longer displays this error message when reading from or writing to the configuration file:

%DATACORRUPTION-1-DATAINCONSISTENCY: write of 11 bytes to 10 bytes 
-Traceback= 0x41186A90 0x411A3960 0x411C1F88 0x413C24B8 0x4031EEDC 0x4032D144 
0x411C3974 0x41193D9C 0x4119420C 0x411DF55C 0x411C70AC 0x411E3184 0x425590F4 
0x4254BD7C 0x421B5CE0 0x421B5CC4

CSCsi94450

When DHCP snooping is enabled on a VLAN, the broadcast DHCP request is now correctly sent over the trusted port and the connected hosts correctly receive their IP addresses.

Caveats Resolved in Cisco IOS Release 12.2(35)SE2

These caveats are resolved in Cisco IOS Release 12.2.(35)SE2:

CSCsb12598

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

Cisco IOS is affected by the following vulnerabilities:

Processing ClientHello messages, documented as Cisco bug ID CSCsb12598

Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304

Processing Finished messages, documented as Cisco bug ID CSCsd92405

Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.


Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.


A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.

CSCsb40304

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

Cisco IOS is affected by the following vulnerabilities:

Processing ClientHello messages, documented as Cisco bug ID CSCsb12598

Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304

Processing Finished messages, documented as Cisco bug ID CSCsd92405

Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.


Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.


A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.

CSCsd92405

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

Cisco IOS is affected by the following vulnerabilities:

Processing ClientHello messages, documented as Cisco bug ID CSCsb12598

Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304

Processing Finished messages, documented as Cisco bug ID CSCsd92405

Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.


Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.


A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.

CSCsh34864

There is no longer the potential for a spontaneous reload when you configure a UNI community VLAN with a VLAN ID greater than 1000.

Caveats Resolved in Cisco IOS Release 12.2(35)SE1

These are the Cisco IOS caveats resolved in Cisco IOS Release 12.2.(35)SE1:

CSCsb12598

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

Cisco IOS is affected by the following vulnerabilities:

Processing ClientHello messages, documented as Cisco bug ID CSCsb12598

Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304

Processing Finished messages, documented as Cisco bug ID CSCsd92405

Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.


Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.


A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.

CSCsb40304

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

Cisco IOS is affected by the following vulnerabilities:

Processing ClientHello messages, documented as Cisco bug ID CSCsb12598

Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304

Processing Finished messages, documented as Cisco bug ID CSCsd92405

Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.


Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.


A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.

CSCsc20515

If you create a private VLAN domain with a primary and secondary VLAN, configure the secondary VLAN as a community VLAN, and associate ports to the private VLAN, the LEDs on the ports that belong to the secondary VLAN display as amber. If you configure one of these ports as a SPAN destination port and later configure it again as a member of the secondary community VLAN, the LED now correctly again shows as amber.

CSCsc21602

When an output policy-map is configured with a qualified queue-limit and associated class-map and the class-map includes extra match statements, the queue-limit configuration is no longer rejected.

CSCsc26465

When you install a CWDM SFP module in the switch, the output of the show inventory user EXEC command now lists the CWDM device.

CSCsd92405

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

Cisco IOS is affected by the following vulnerabilities:

Processing ClientHello messages, documented as Cisco bug ID CSCsb12598

Processing ChangeCipherSpec messages, documented as Cisco bug ID CSCsb40304

Processing Finished messages, documented as Cisco bug ID CSCsd92405

Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.


Note Another related advisory has been posted with this advisory. This additional advisory also describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.


A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.

CSCse21219

If a Putty client is used to change the configuration to a device with SSH, the switch no longer stops responding to incoming traffic, such as SSH, Telnet, or ping packets.

CSCse38455

You can no longer create QoS configurations with more than 46 policers on a Cisco ME 2400 switch. This has always been an unsupported configuration. However, in previous releases, the switch did not check on the amount of policers configured. Unexpected and incorrect QoS behavior for traffic streams assigned to any policer after the first 46 unique policers could occur.

The switch now confirms that the maximum number of most policers in a policymap is 46. This check is consistent with both per-port and per-port-per-VLAN configurations.

CSCse47012

When a hierarchical port-shaping output policy-map with child class-based actions is attached to an interface and an input policy map is modified or detached and re-attached, the class-based actions in the hierarchical output policy map now continue to work correctly.

CSCsf04754

Multiple Cisco products contain either of two authentication vulnerabilities in the Simple Network Management Protocol version 3 (SNMPv3) feature. These vulnerabilities can be exploited when processing a malformed SNMPv3 message. These vulnerabilities could allow the disclosure of network information or may enable an attacker to perform configuration changes to vulnerable devices. The SNMP server is an optional service that is disabled by default. Only SNMPv3 is impacted by these vulnerabilities. Workarounds are available for mitigating the impact of the vulnerabilities described in this document.

The United States Computer Emergency Response Team (US-CERT) has assigned Vulnerability Note VU#878044 to these vulnerabilities.

Common Vulnerabilities and Exposures (CVE) identifier CVE-2008-0960 has been assigned to these vulnerabilities.

This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20080610-snmpv3.shtml

CSCsg62606

A hierarchical output policy map with a child policy that includes priority with police now correctly provides the configured bandwidth allocations.

CSCsg96306

The entAliasMappingIdentifier now correctly maps the ifIndices of SFP ports.

CSCsg90953

If you change the policer configuration on an ME switch, the configuration change now correctly takes affect when you detach the service policy, modify it, and then reattach it.

Documentation Updates

This section contains documentation update for this release.

Updates to the Command Reference and Software Configuration Guide

These are updates to the Cisco ME 2400 Command Reference and Cisco ME 2400 Software Configuration Guide for Cisco IOS Release 12.2(35)SE1:

EtherChannel

When you configure one end of an EtherChannel in either PAgP or LACP mode, the system negotiates with the other end of the channel to determine which ports should become active. In previous releases, the incompatible ports were suspended. Beginning with Cisco IOS Release 12.2(35)SE, instead of a suspended state, the local port is put into an independent state and continues to carry data traffic as would any other single link. The port configuration does not change, but the port does not participate in the EtherChannel.

QoS Update

Beginning with this release, the switch supports configuration and attachment of a unique output policy map for each port on the switch. However, these output policy maps can contain only three configurations of queue limits. You can include these three unique queue-limit configurations in as many output policy maps as there are switch ports. If you try to attach an output policy map that has a fourth queue-limit configuration, you see an error message, and the attachment is not allowed. There are no limitations on the configurations of bandwidth, priority, or shaping.

MVR over Trunk Ports

In Cisco IOS Release 12.2(25)SEG and earlier, only access ports could be configured as Multicast VLAN Registration (MVR) receiver ports. Beginning with this release, you can also configure trunk ports as MVR receiver ports. This section was added to the "Configuring IGMP" chapter of the software configuration guide:

Beginning in privileged EXEC mode, follow these steps to configure a trunk port as an MVR receiver port:

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

mvr

Enable MVR on the switch.

Step 3 

interface interface-id

Enter the Layer 2 port to configure and enter interface configuration mode.

Step 4 

switchport mode trunk

Set trunking mode to TRUNK unconditionally.

Note When you are configuring a trunk port as an MVR receiver port, we recommend that the source port is configured as a network node interface (NNI) and the MVR trunk receiver port is configured as a user node interface (UNI).

Step 5 

mvr type receiver

Specify that the trunk port is an MVR receiver port.

Step 6 

mvr vlan source-vlan-id receiver vlan receiver-vlan-id

Enable this trunk port to distribute MVR traffic coming from the MVR VLAN to the VLAN on the trunk identified by the receiver VLAN.

Step 7 

mvr vlan vlan-id group ip-address receiver vlan-id

(Optional) Configure the trunk port to be a static member of the group on the receiver VLAN.

Step 8 

end

Return to privileged EXEC mode.

Step 9 

show mvr

show mvr interface

or

show mvr members

Verify the configuration.

Step 10 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

This example shows how to configure a port as an MVR trunk receiver port, assign it to a VLAN, configure the port to be a static member of a group, and verify the results.

Switch(config)# mvr
Switch(config)# interface fastethernet 0/10
Switch(config)# switchport mode trunk
Switch(config)# mvr type receiver
Switch(config)# mvr vlan 100 receiver vlan 201
Switch(config)# mvr vlan 100 group 239.1.1.1 receiver vlan 201
Switch(config)# end
Switch# show mvr interface

To return the interface to its default settings, use the no mvr [type | immediate | vlan vlan-id | group] 
interface configuration command.

Note For more information about access and trunk ports, see the software configuration guide.


The mvr interface configuration command was modified for this release. This update was added to the command reference

mvr (interface configuration)

Use the mvr interface configuration command to configure a Layer 2 port as a multicast VLAN registration (MVR) receiver or source port and set the immediate leave feature, and statically assign a port to an IP multicast VLAN and IP address. Use the no form of this command to return to the default settings.

mvr [immediate | type {receiver | source} | vlan vlan-id {[group ip-address][receiver vlan vlan-id]}}

no mvr [immediate | type {source | receiver}| vlan vlan-id {[group ip-address][receiver vlan vlan-id]}}

Syntax Description

immediate

(Optional) Enable the Immediate Leave feature of MVR on a port. Use the no mvr immediate command to disable the feature.

type

(Optional) Configure the port as an MVR receiver port or source port.

The default port type is neither an MVR source nor receiver port. The no mvr type command resets the port as neither a source or receiver port.

receiver

Configure the port as a subscriber port that can only receive multicast data. Receiver ports cannot belong to the multicast VLAN.

source

Configure the port as an uplink port that can send and receive multicast data for the configured multicast groups. All source ports on a switch belong to a single multicast VLAN.

Note When you are configuring a trunk port as an MVR receiver port, we recommend that the source port is configured as a network node interface (NNI) and the MVR trunk receiver port is configured as a user node interface (UNI).

vlan vlan-id

Specify the mvr vlan for the system.

group ip-address

(Optional) Statically configure the specified MVR IP multicast group address for the specified multicast VLAN ID. This is the IP address of the multicast group that the port or VLAN is joining.

receiver vlan vlan-id

Specify a receiver VLAN.


Defaults

A port is configured as neither a receiver nor a source.

The Immediate Leave feature is disabled on all ports.

No receiver port is a member of any configured multicast group.

Command Modes

Interface configuration

Command History

Release
Modification

12.1(14)AX

This command was introduced.

12.2(35)SE1

The receiver and vlan-id keywords were added. These are required to configure a trunk port as a MVR receiver port.


Usage Guidelines

Configure a port as a source port if that port should be able to both send and receive multicast data bound for the configured multicast groups. Multicast data is received on all ports configured as source ports.

Receiver ports on a switch can be in different VLANs, but should not belong to the multicast VLAN.

A port that is not taking part in MVR should not be configured as an MVR receiver port or a source port. A non-MVR port is a normal switch port, able to send and receive multicast data with normal switch behavior.

When Immediate Leave is enabled, a receiver port leaves a multicast group more quickly. Without Immediate Leave, when the switch receives an IGMP leave message from a group on a receiver port, it sends out an IGMP MAC-based query on that port and waits for IGMP group membership reports. If no reports are received in a configured time period, the receiver port is removed from multicast group membership. With Immediate Leave, an IGMP MAC-based query is not sent from the receiver port on which the IGMP leave was received. As soon as the leave message is received, the receiver port is removed from multicast group membership, which speeds up leave latency.

The Immediate Leave feature should be enabled only on receiver ports to which a single receiver device is connected.

The mvr vlan group command statically configures ports to receive multicast traffic sent to the IP multicast address. A port statically configured as a member of a group remains a member of the group until statically removed. In compatible mode, this command applies only to receiver ports; in dynamic mode, it can also apply to source ports. Receiver ports can also dynamically join multicast groups by using IGMP join messages.

When operating in compatible mode, MVR does not support IGMP dynamic joins on MVR source ports.

Examples

This example shows how to configure a port as an MVR receiver port:

Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mvr type receiver

This example shows how to configure a port as an MVR source port:

Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr type source

This example shows how to remove a port as an MVR port:

Switch(config)# interface gigabitethernet1/0/1
Switch(config-if))# no mvr

This example shows how to display configured receiver ports and source ports.

Switch# show mvr interface
Port    Type            Mode            VLAN    Status          Immediate Leave
----    ----            ----            ----    -------         ---------------
Fa0/2   RECEIVER       Trunk          1      ACTIVE/UP      DISABLED 
Fa0/4   RECEIVER       Trunk          1      ACTIVE/UP      DISABLED 
Fa0/5   RECEIVER       Trunk          1      ACTIVE/UP      DISABLED 
Fa0/5   RECEIVER       Trunk          2      ACTIVE/UP      DISABLED 
Fa0/10  SOURCE         Access         10     ACTIVE/UP      DISABLED 
Fa0/11  SOURCE         Trunk          10     ACTIVE/UP      ENABLED 
Fa0/16  RECEIVER       Trunk          2      ACTIVE/UP      DISABLED 
Fa0/18  RECEIVER       Trunk          1      ACTIVE/UP      ENABLED 
Fa0/18  RECEIVER       Trunk          2      ACTIVE/UP      ENABLED 
Fa0/21  SOURCE         Access         10     ACTIVE/UP      DISABLED 
Fa0/24  RECEIVER       Access         4      ACTIVE/DOWN    DISABLED 
Gi0/1   RECEIVER       Trunk          1      ACTIVE/UP      DISABLED 
Gi0/1   RECEIVER       Trunk          2      ACTIVE/UP      DISABLED 
Gi0/2   SOURCE          Access           10     ACTIVE/UP       DISABLED 

This example shows how to enable Immediate Leave on a port:

Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# mvr immediate

This example shows how to disable Immediate Leave on a port:

Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no mvr immediate

This example shows how to add a port interface on VLAN 1 as a static member of IP multicast group 228.1.23.4:

Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr vlan1 group 230.1.23.4

This example shows how to add a port 5 on VLAN 100 as a static member of IP multicast group 239.1.1.1 In this example, the receiver port is a trunk port:

Switch(config)# interface fastethernet0/5
Switch(config-if)# mvr vlan 100 group 239.1.1.1 receiver vlan 201

This example shows how to remove this port from membership:

Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no mvr vlan5 group 228.1.23.4

This example shows how to remove this port from all IP multicast groups:

Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no mvr vlan5 group

This example shows the result if you try to add a port to a multicast group and the port is not a receiver port:

Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# mvr vlan 1 group 230.1.23.4
Interface Gi1/0/2 not configured as a receiver interface 

This example shows how to add on port 5 the receiver VLAN 201 with an MVR VLAN of 100.

Switch(config)# interface fastethernet0/5
Switch(config-if)# mvr vlan 100 receiver vlan 201

This example shows how to add on port 5 the receiver VLAN 201 as a static member of the IP multicast group 239.1.1.1, with an MVR VLAN of 100:

Switch(config)# interface fastethernet0/5
Switch(config-if)# mvr vlan 100 group 239.1.1.1 receiver vlan 201

You can verify your settings by entering the show mvr members privileged EXEC command.

Related Commands

Command
Description

mvr (global configuration)

Enables and configures multicast VLAN registration on the switch.

show mvr

Displays MVR global parameters or port parameters.

show mvr interface

Displays the configured MVR interfaces or displays the multicast groups to which a receiver port belongs. Also displays all MVR groups of which the interface is a member.

show mvr members

Displays all receiver ports that are members of an MVR multicast group.


Related Documentation

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

http://www.cisco.com/en/US/products/ps6581/tsd_products_support_series_home.html

You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites listed in the "" section.

Cisco ME 2400 Ethernet Access Switch Software Configuration Guide (not orderable but available on Cisco.com)

Cisco ME 2400 Ethernet Access Switch Command Reference (not orderable but available on Cisco.com)

Cisco ME 3400 and ME 2400 Ethernet Access Switch System Message Guide (not orderable but available on Cisco.com)

Cisco ME 2400 Ethernet Access Switch Hardware Installation Guide (not orderable but available on Cisco.com)

Cisco ME 3400 and ME 2400 Ethernet Access Switches Getting Started Guide (order number DOC-7817050=)

Regulatory Compliance and Safety Information for the Cisco ME 3400 and ME 2400 Ethernet Access Switches (order number DOC-7817051)

Cisco Small Form-Factor Pluggable Modules Installation Notes (order number DOC-7815160=)

Cisco CWDM GBIC and CWDM SFP Installation Note (not orderable but available on Cisco.com)

These compatibility matrix documents are available from this Cisco.com site:

http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html

Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix (not orderable but available on Cisco.com)

Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix (not orderable but available on Cisco.com)

Cisco Small Form-Factor Pluggable Modules Compatibility Matrix (not orderable but available on Cisco.com)

Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules (not orderable but available on Cisco.com)

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html