Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Blade Switches for FSC

Release Notes for the Cisco Catalyst Blade Switch 3040 for FSC, Cisco IOS Release 12.2(40)SE and Later

Downloads

Table Of Contents

Release Notes for the Cisco Catalyst Blade Switch 3040 for FSC, Cisco IOS Release 12.2(40)SE and Later

Contents

System Requirements

Hardware Supported

Device Manager System Requirements

Hardware Requirements

Software Requirements

Upgrading the Switch Software

Finding the Software Version and Feature Set

Deciding Which Files to Use

Archiving Software Images

Upgrading a Switch by Using the Device Manager

Upgrading a Switch by Using the CLI

Recovering from a Software Failure

Installation Notes

New Software Features

Limitations and Restrictions

Cisco IOS Limitations

Configuration

Dynamic ARP Inspection

Ethernet

IP

IP Telephony

MAC Addressing Multicasting

QoS

SPAN and RSPAN

Trunking

VLAN

Device Manager Limitations

Important Notes

Cisco IOS Notes

Device Manager Notes

Open Caveats

Resolved Caveats

Documentation Updates

Updates to the Software Configuration Guide

Information Updates

Configuration Replacement and Rollback

Understanding Configuration Replacement and Rollback

Configuration Guidelines

Configuring the Configuration Archive

Performing a Configuration Replacement or Rollback Operation

LLDP-MED Location TLV

Configuring Private VLANs

Understanding Private VLANs

Configuring Private VLANs

Tasks for Configuring Private VLANs

Default Private-VLAN Configuration

Private-VLAN Configuration Guidelines

Configuring and Associating VLANs in a Private VLAN

Configuring a Layer 2 Interface as a Private-VLAN Host Port

Configuring a Layer 2 Interface as a Private-VLAN Promiscuous Port

Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface

Monitoring Private VLANs

Updates to the Command Reference

Information Updates

location (global configuration)

location (interface configuration)

show location

private-vlan

private-vlan mapping

switchport mode private-vlan

switchport private-vlan

Updates to the System Message Guide

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for the Cisco Catalyst Blade Switch 3040 for FSC, Cisco IOS Release 12.2(40)SE and Later

Revised January 9, 2008

Cisco IOS Releases 12.2(40)SE and later run on the Cisco Catalyst Blade Switch 3040 for FSC, referred to as the switch. The switch is installed in the Fujitsu Siemens Computers (FSC) PRIMERGY BX600 system, referred to as the BX600 system.

Note Before you install the switch in the BX600 system, upgrade the BX600 system management software to version 1.68 or later for the switch to operate properly.

Check for updates to this document at this URL for information about compatibility with the BX600 system software:

http://www.cisco.com/en/US/products/ps8743/prod_release_notes_list.html

Note If you wish to use Device Manager to upgrade the switch from Cisco IOS Release 12.2(35)SE through Cisco IOS Release 12.2(40)SE1 (the LAN Base image) to Cisco IOS Release 12.2(44)SE or later (the IP base image), you must first upgrade to Cisco IOS Release 12.2(40)SE2.

These release notes include important information about Cisco IOS Release 12.2(40)SE1 and SE2 and any limitations, restrictions, and caveats that apply to them. 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 switch packaging.

•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 Catalyst Blade Switch 3040 for FSC documentation, see the "Updates to the Software Configuration Guide" section.

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

http://tools.cisco.com/support/downloads/go/MDFTree.x?butype=switches

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

•"Limitations and Restrictions" section

•"Important Notes" section

•"Open Caveats" section

•"Resolved Caveats" section

•"Documentation Updates" section

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

System Requirements

The system requirements are described in these sections:

•"Hardware Supported" section

•"Device Manager System Requirements" section

Hardware Supported

The hardware supported on this release is the Cisco Catalyst Blade Switch 3040 for FSC.

Device Manager System Requirements

These sections describes the hardware and software requirements for using the device manager:

•"Hardware Requirements" section

•"Software Requirements" section

Hardware Requirements

Table 1 lists the minimum hardware requirements for running the device manager.

Table 1 Minimum Hardware Requirements 

Processor Speed
DRAM
Number of Colors
Resolution
Font Size

Intel Pentium II1

64 MB2

256

1024 x 768

Small

1 We recommend Intel Pentium 4.

2 We recommend 256-MB DRAM.


Software Requirements

Table 2 lists the supported operating systems and browsers for using the device manager, which does not require a plug-in. The device manager verifies the browser version when starting a session to ensure that the browser is supported.

Note Windows NT and Windows 98 are no longer supported.

Table 2 Supported Operating Systems and Browsers 

Operating System
Minimum Service Pack or Patch
Microsoft Internet Explorer1
Netscape Navigator

Windows 2000

None

5.5 or 6.0

7.1

Windows XP

None

5.5 or 6.0

7.1

1 Service Pack 1 or higher is required for Internet Explorer 5.5.


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

•"Upgrading a Switch by Using the Device Manager" section

•"Upgrading a Switch by Using the CLI" 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. A subdirectory contains the files needed for web management. 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 and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the CLI, use the tar file and the archive download-sw privileged EXEC command.

Note If you wish to use Device Manager to upgrade the switch from Cisco IOS Release 12.2(35)SE through Cisco IOS Release 12.2(40)SE1 (the LAN Base image) to Cisco IOS Release 12.2(44)SE or later (the IP base image), you must first upgrade to Cisco IOS Release 12.2(40)SE2.

Table 3 lists the filenames for this software release.

Table 3 Cisco IOS Software Image Files 

Filename

Description

cbs40x0-lanbase-tar.122-40.SE2.tar

Cisco Catalyst Blade Switch 3040 for FSC image file and device manager files.
This image has Layer 2+ features.

cbs40x0-lanbasek9-tar.122-40.SE2.tar

Cisco Catalyst Blade Switch 3040 for FSC cryptographic image file and device manager files.
This image has the Kerberos and SSH 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/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.

Note Although you can copy any file on the flash memory to the TFTP server, it is time consuming to copy all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and archive it on an internal host in your network.

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

Upgrading a Switch by Using the Device Manager

You can upgrade switch software by using the device manager. For detailed instructions, click Help.

Note When using the device manager to upgrade your switch, do not use or close your browser session after the upgrade process begins. Wait until after the upgrade process completes.

Upgrading a Switch by Using the CLI

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.

To download software, follow these steps:

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

Step 2 Download the software image file. 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

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, see 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

For more information about assigning an IP address and default gateway to the switch, see 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/c3750-ipservices-tar.122-35.SE.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 additional 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 Express Setup program or the BX600 Management Blade WEB GUI described in the getting started guide.

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

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

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

New Software Features

These are the new software features for this release:

•Configuration replacement and rollback to replace the running configuration on a switch with any saved Cisco IOS configuration file

•IP Service Level Agreements (IP SLAs) responder support that allows the switch to be a target device for IP SLAs active traffic monitoring

•Private VLANs to allow traffic to be segmented at the data-link layer (Layer 2), limiting the size of the broadcast domain

•Support for the Link Layer Discovery Protocol Media Extensions (LLDP-MED) location TLV that provides location information from the switch to the endpoint device

•Support for the CISCO-MAC-NOTIFICATION-MIB

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.

This section contains these limitations:

•"Cisco IOS Limitations" section

•"Device Manager Limitations" section

Cisco IOS Limitations

These limitations apply to the switch:

•"Configuration" section

•"Dynamic ARP Inspection" section

•"Ethernet" section

•"IP" section

•"IP Telephony" section

•"MAC Addressing Multicasting" section

•"MAC Addressing Multicasting" section

•"QoS" section

•"SPAN and RSPAN" section

•"Trunking" section

•"VLAN" section

Configuration

The workaround is to configure the burst interval to more than 1 second.

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)

•When connected to some third-party devices that send early preambles, a switch port operating at 100 Mp/s full duplex or 100 Mp/s half duplex might bounce the line protocol up and down. The problem is observed only when the switch is receiving frames.

The workaround is to configure the port for 10 Mp/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)

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

Dynamic ARP Inspection

•When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN is within the configured rate limit, the port might go into an error-disabled state. (CSCse06827)

Ethernet

This is the Ethernet limitation:

Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address. More than one traffic stream might map to same member ports, based on hashing results calculated by the ASIC.

If this happens, traffic distribution is uneven on EtherChannel ports.

Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:

•for random source-ip and dest-ip traffic, configure load balance method as src-dst-ip

•for incrementing source-ip traffic, configure load balance method as src-ip

•for incrementing dest-ip traffic, configure load balance method as dst-ip

•Configure the number of ports in the EtherChannel so that the number is equal to a power of 2 (for example, 2, 4, or 8)

For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal. (CSCeh81991)

IP

This is the IP limitation:

When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time might be slow when you are using the console. The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)

IP Telephony

This is the IP telephony limitation:

After you change the access VLAN on a port that has IEEE 802.1x enabled, the IP phone address is removed. Because learning is restricted on IEEE 802.1x-capable ports, it takes approximately 30 seconds before the address is relearned. No workaround is necessary. This limitation is unlikely to affect the Cisco Catalyst Blade Switch 3040 for FSC because IP phones are not usually connected to the switch uplink ports. (CSCea85312)

MAC Addressing Multicasting

These are the multicasting limitations:

•If the number of multicast routes and Internet Group Management Protocol (IGMP) groups are more than the maximum number specified by the show sdm prefer global configuration command, the traffic received on unknown groups is flooded in the received VLAN even though the show ip igmp snooping multicast-table privileged EXEC command output shows otherwise. The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. (CSCdy09008)

•IGMP filtering is applied to packets that are forwarded through hardware. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port. There is no workaround. (CSCdy82818)

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

•Incomplete multicast traffic can be seen under either of these conditions:

–You disable IP multicast routing or re-enable it globally on an interface.

–A switch mroute table temporarily runs out of resources and recovers later.

The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)

After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.

Use one of these workarounds:

–Cancel membership in the multicast group by using the no ip igmp join-group group-address interface configuration command on an SVI.

–Disable IGMP snooping on the VLAN interface by using the no ip igmp snooping vlan vlan-id global configuration command. (CSCeh90425)

QoS

These are the quality of service (QoS) limitations:

•Some switch queues are disabled if the buffer size or threshold level is set too low with the mls qos queue-set output global configuration command. The ratio of buffer size to threshold level should be greater than 10 to avoid disabling the queue. The workaround is to choose compatible buffer sizes and threshold levels. (CSCea76893)

•When auto-QoS is enabled on the switch, priority queuing is not enabled. Instead, the switch uses shaped round robin (SRR) as the queuing mechanism. The auto-QoS feature is designed on each platform based on the feature set and hardware limitations, and the queuing mechanism supported on each platform might be different. There is no workaround. (CSCee22591)

•A QoS service policy with a policy map containing more than 62 policers cannot be added to an interface by using the service-policy interface configuration command.

The workaround is to use policy maps with 62 or fewer policers. (CSCsc59418)

SPAN and RSPAN

These are the SPAN and Remote SPAN (RSPAN) limitations:

•Egress SPAN routed packets (both unicast and multicast) show the incorrect source MAC address. For remote SPAN packets, the source MAC address should be the MAC address of the egress VLAN, but instead the packet shows the MAC address of the RSPAN VLAN. For local SPAN packets with native encapsulation on the destination port, the packet shows the MAC address of VLAN 1. This problem does not appear with local SPAN when the encapsulation replicate option is used. This limitation does not apply to bridged packets. The workaround is to use the encapsulate replicate keywords in the monitor session global configuration command. Otherwise, there is no workaround. This is a hardware limitation. (CSCdy81521)

•During periods of very high traffic when two RSPAN source sessions are configured, the VLAN ID of packets in one RSPAN session might overwrite the VLAN ID of the other RSPAN session. If this occurs, packets intended for one RSPAN VLAN are incorrectly sent to the other RSPAN VLAN. This problem does not affect RSPAN destination sessions. The workaround is to configure only one RSPAN source session. This is a hardware limitation. (CSCea72326)

•Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP) packets received 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)

•When the logging event-spanning-tree interface configuration command is configured and logging to the console is enabled, a topology change might generate a large number of logging messages, causing high CPU utilization. CPU utilization can increase with the number of spanning-tree instances and the number of interfaces configured with the logging event-spanning-tree interface configuration command. This condition adversely affects how the switch operates and could cause problems such as STP convergence delay.

High CPU utilization can also occur with other conditions, such as when debug messages are logged at a high rate to the console.

Use one of these workarounds:

–Disable logging to the console.

–Rate-limit logging messages to the console. (CSCsg91027)

–Remove the logging event spanning-tree interface configuration command from the interfaces.

The workaround is to configure aggressive UDLD. (CSCsh70244)

Trunking

These are the trunking limitations:

•The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link [ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber. This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the frame to an IEEE 802.1Q trunk interface. There is no workaround. (CSCdz33708)

•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

This is the VLAN limitation:

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

The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)

Device Manager Limitations

This is the device manager limitation for this release:

When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not start.

The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)

Important Notes

These sections describe the important notes related to this software release:

•"Cisco IOS Notes" section

•"Device Manager Notes" section

Cisco IOS Notes

These notes apply to Cisco IOS software:

•The behavior of the no logging on global configuration command changed in Cisco IOS Release 12.2(18)SE and later. You can only use the logging on and then the no logging console global configuration commands to disable logging to the console. (CSCec71490)

•In Cisco IOS Release 12.2(25)SEC, the implementation for multiple spanning tree (MST) changed from the previous release. Multiple STP (MSTP) complies with the IEEE 802.1s standard. Previous MSTP implementations were based on a draft of the IEEE 802.1s standard.

•If the switch requests information from the Cisco Secure Access Control Server (ACS) and the message exchange times out because the server does not respond, a message similar to this appears: 

00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not 
responding.

If this message appears, make sure that there is network connectivity between the switch and the ACS. You should also make sure that the switch has been properly configured as an AAA client on the ACS.

•Cisco IOS Release 12.2(40)SE1 and later

If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade the switch software to Cisco IOS Release 12.2(40)SE1 (or later), when you enter the auto qos voip cisco-phone interface configuration command on another interface, you might see this message: 

AutoQoS Error: ciscophone input service policy was not properly applied

policy map AutoQoS-Police-CiscoPhone not configured

If this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.

Device Manager Notes

These notes apply to the device manager:

•We recommend this browser setting to more quickly display the device manager from Microsoft Internet Explorer.

From Microsoft Internet Explorer:

1. Choose Tools > Internet Options.

2. Click Settings in the Temporary Internet files area.

3. From the Settings window, choose Automatically.

4. Click OK.

5. Click OK to exit the Internet Options window.

•The HTTP server interface must be enabled to display the device manager. By default, the HTTP server is enabled on the switch. Use the show running-config privileged EXEC command to see if the HTTP server is enabled or disabled.

•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.cisco.com:84), you must enter http:// as the URL prefix. Otherwise, you cannot start the device manager.

Open Caveats

This section describes the open severity 3 Cisco IOS configuration caveats with possible unexpected activity in this software release:

•CSCsb85001

If traffic is passing through VMPS ports and you perform a shut operation, a dynamic VLAN is not assigned and a VLAN with a null ID appears.

The workaround is to clear the MAC address table. This forces the VMPS server to correctly reassign the VLAN.

•CSCsc30733

This error message appears during authentication when a method list is used and one of the methods in the method list is removed: 

AAA-3-BADMETHODERROR:Cannot process authentication method 218959117

There is no workaround. However, this is only an informational message and does not affect switch functionality.

•CSCsc96474

The switch might display tracebacks similar to these examples when a large number of IEEE 802.1x supplicants try to repeatedly log in and log out.

Examples:

Jan 3 17:54:32 L3A3 307: Jan 3 18:04:13.459: %SM-4-BADEVENT: Event 'eapReq' is invalid for the current state 'auth_bend_idle': dot1x_auth_bend Fa9

Jan 3 17:54:32 L3A3 308: -Traceback= B37A84 18DAB0 2FF6C0 2FF260 8F2B64 8E912C Jan 3 19:06:13 L3A3 309: Jan 3 19:15:54.720: %SM-4-BADEVENT: Event 'eapReq_no_reAuthMax' is invalid for the current ate 'auth_restart': dot1x_auth Fa4

Jan 3 19:06:13 L3A3 310: -Traceback= B37A84 18DAB0 3046F4 302C80 303228 8F2B64 8E912C Jan 3 20:41:44 L3A3 315: .Jan 3 20:51:26.249: %SM-4-BADEVENT: Event 'eapSuccess' is invalid for the current state 'auth_restart': dot1x_auth Fa9

Jan 3 20:41:44 L3A3 316: -Traceback= B37A84 18DAB0 304648 302C80 303228 8F2B64 8E912C

There is no workaround.

•CSCsd03580

When IEEE 802.1x is globally disabled on the switch by using the no dot1x system-auth-control global configuration command, some interface level configuration commands, including the dot1x timeout and dot1x mac-auth-bypass commands, become unavailable.

The workaround is to enable the dot1x system-auth-control global configuration command before attempting to configure interface level IEEE 802.1x parameters.

•CSCsg18176

When dynamic ARP inspection is enabled and IP validation is disabled, the switch drops ARP requests that have a source address of 0.0.0.0.

The workaround is to configure an ARP access control list (ACL) that permits IP packets with a source IP address of 0.0.0.0 (and any MAC) address) and apply the ARP ACL to the desired DAI VLANs.

•CSCsg21537

When MAC addresses are learned on an Etherchannel port, the addresses are incorrectly deleted from the MAC address table even when the MAC address table aging timeout value is configured to be longer than the ARP timeout value. This causes intermittent unicast packet flooding in the network.

•CSCsg30295

When you configure an IP address on a switch virtual interface (SVI) with DCHP and enable DHCP snooping on the SVI VLAN, the switch SVI cannot obtain an IP address.

The workaround is to not enable DCHP snooping on the SVI VLAN or to use a static IP address for the SVI.

•CSCsi63999

Changing the spanning tree mode from rapid STP to MSTP can cause tracebacks when the virtual port error-disable feature is enabled when the STP mode is changed.

There is no workaround.

•CSCsi70454

The configuration file used for the configuration replacement feature requires the character string end\n at the end of the file. The Windows Notepad text editor does not add the end\n string, and the configuration rollback does not work.

These are the workarounds. (You only need to do one of these.)

–Do not use a configuration file that is stored by or edited with Windows Notepad.

–Manually add the character string end\n to the end of the file.

The workaround is to configure routed IPv4 multicast and IPv6 unicast traffic in different switch ports.

•CSCsj52956

In Cisco IOS Release 12.2(37)SE or later, the TxBufferFullDropCount counter always increments even when the switch is a standalone switch.

There is no workaround.

•CSCsj53001

In Cisco IOS Release 12.2(37)SE or later, the Total output drops field in the show interfaces privileged EXEC command output displays ASIC drops.

–On some interfaces, the Total output drops field is always 0 even though the show platform port-asic stats drop privileged EXEC command output shows ASIC drops.

–The Total output drops value is the same for all the ports that are linked to the same ASIC.

There is no workaround.

on the subinterfaces.

•CSCsj74022

The switch does not correctly update the entPhysicalChildIndex objects from the ENTITY-MIB, and some of the entPhysicalChildIndex entries are missing from the table. This adversely affects network management applications such as CiscoWorks CiscoView because they cannot manage the switch.

There is no workaround.

•CSCsj77933

In Cisco IOS Release 12.2(35)SE and Cisco IOS Release 12.2(37)SE, if you enter a space before a comma in the define interface-range or the interface range global configuration command, the space before the comma is not saved in the switch configuration.

There is no workaround.

•CSCsj87991

A switch configured for Link Layer Discovery Protocol (LLDP) might not correctly report the enabled switch capabilities in the LLDP type, length, and value (TLV) attributes. System capabilities appear correctly, but the enabled capabilities are not identified if the switch is configured only as a Layer 2 switch.

There is no workaround.

Resolved Caveats

This section describes the caveats that have been resolved in Cisco IOS Release 12.2(40)SE1:

•CSCsg81334

If IEEE 802.1x critical authentication is not enabled and the RADIUS authentication server is unavailable during MAC authentication bypass (MAB) reauthentication, when the RADIUS server comes back up, MAB now correctly authenticates previously authenticated clients.

•CSCsi08513

MAC flap-notification no longer occurs when a switch is running VLAN bridge spanning-tree protocol (STP) and fallback bridging is configured on the VLANs running STP.

•CSCsi10584

Multiple Spanning-Tree Protocol (MSTP) convergence time has been improved for Cisco IOS Release 12.2.

•CSCsl22576

You can use Device Manager to upgrade the switch from Cisco IOS Release 12.2(35)SE through Cisco IOS Release 12.2(40)SE1 (the LAN Base image) to Cisco IOS Release12.2(44)SE or later (the IP base image). However, to do this, you must first upgrade to Cisco IOS Release 12.2(40)SE2.

If you wish to upgrade from a LAN base image to the IP base image without first upgrading to Cisco IOS Release 12.2(40)SE2, you must use one of these methods to upgrade the switch:

–Use the CLI to upgrade to Cisco IOS Release 12.2(44)SE or later.

–Use the TFTP option in CNA to upgrade to Cisco IOS Release 12.2(44)SE or later.

Documentation Updates

This section contains these documentation updates:

•"Updates to the Software Configuration Guide" section

•"Information Updates" section

•"Updates to the Command Reference" section

•"Updates to the System Message Guide" section

Updates to the Software Configuration Guide

These are the updates to the software configuration guide:

•"Information Updates" section

•"Configuration Replacement and Rollback" section

•"LLDP-MED Location TLV" section

•"Configuring Private VLANs" section

Information Updates

•This information about the dot1x timeout tx-period seconds interface configuration command is incorrect:

The range for seconds is from 5 to 65535.

The correct range is from 1 to 65535 seconds.

•This information in the "MAC Address-Table Move Update" section of the "Understanding Flex Links and the MAC Address-Table Move Update" chapter is incorrect:

The switch then starts forwarding traffic from the server to the PC through port 4, which reduces the loss of traffic from the server to the PC.

This is the correct information:

Switch A does not need to wait for the MAC address-table update. The switch detects a failure on port 1 and immediately starts forwarding server traffic from port 2, the new forwarding port. This change occurs in 100 milliseconds (ms). The PC is directly connected to switch A, and the connection status does not change. Switch A does not need to update the PC entry in the MAC address table.

•This caution was added to the "Configuring System Message Logging" chapter of the software configuration guide.

Caution Logging messages to the console at a high rate can cause high CPU utilization and adversely affect how The private-vlan mapping interface configuration command only affects private-VLAN traffic that is Layer 3 switched.

Configuration Replacement and Rollback

The configuration replacement and rollback feature replaces the running configuration with any saved Cisco IOS configuration file. You can use the rollback function to roll back to a previous configuration.

These sections contain this information:

•"Understanding Configuration Replacement and Rollback" section

•"Configuration Guidelines" section

•"Configuring the Configuration Archive" section

•"Performing a Configuration Replacement or Rollback Operation" section

Understanding Configuration Replacement and Rollback

To use the configuration replacement and rollback feature, you should understand these concepts:

•"Archiving a Configuration" section

•"Replacing a Configuration" section

•"Rolling Back a Configuration" section

Archiving a Configuration

The configuration archive provides a mechanism to store, organize, and manage an archive of configuration files. The configure replace privileged EXEC command increases the configuration rollback capability. As an alternative, you can save copies of the running configuration by using the copy running-config destination-url privileged EXEC command, storing the replacement file either locally or remotely. However, this method lacks any automated file management. The configuration replacement and rollback feature can automatically save copies of the running configuration to the configuration archive.

You use the archive config privileged EXEC command to save configurations in the configuration archive by using a standard location and filename prefix that is automatically appended with an incremental version number (and optional timestamp) as each consecutive file is saved. You can specify how many versions of the running configuration are kept in the archive. After the maximum number of files are saved, the oldest file is automatically deleted when the next, most recent file is saved. The show archive privileged EXEC command displays information for all the configuration files saved in the configuration archive.

The Cisco IOS configuration archive, in which the configuration files are stored and available for use with the configure replace command, is in any of these file systems: FTP, HTTP, RCP, TFTP.

Replacing a Configuration

The configure replace privileged EXEC command replaces the running configuration with any saved configuration file. When you enter the configure replace command, the running configuration is compared with the specified replacement configuration, and a set of configuration differences is generated. The resulting differences are used to replace the configuration. The configuration replacement operation is usually completed in no more than three passes. To prevent looping behavior no more than five passes are performed.

You can use the copy source-url running-config privileged EXEC command to copy a stored configuration file to the running configuration. When using this command as an alternative to the configure replace target-url privileged EXEC command, note these major differences:

•The copy source-url running-config command is a merge operation and preserves all the commands from both the source file and the running configuration. This command does not remove commands from the running configuration that are not present in the source file. In contrast, the configure replace target-url command removes commands from the running configuration that are not present in the replacement file and adds commands to the running configuration that are not present.

•You can use a partial configuration file as the source file for the copy source-url running-config command. You must use a complete configuration file as the replacement file for the configure replace target-url command.

Rolling Back a Configuration

You can also use the configure replace command to roll back changes that were made since the previous configuration was saved. Instead of basing the rollback operation on a specific set of changes that were applied, the configuration rollback capability reverts to a specific configuration based on a saved configuration file.

If you want the configuration rollback capability, you must first save the running configuration before making any configuration changes. Then, after entering configuration changes, you can use that saved configuration file to roll back the changes by using the configure replace target-url command.

You can specify any saved configuration file as the rollback configuration. You are not limited to a fixed number of rollbacks, as is the case in some rollback models.

Configuration Guidelines

Follow these guidelines when configuring and performing configuration replacement and rollback:

•Make sure that the switch has free memory larger than the combined size of the two configuration files (the running configuration and the saved replacement configuration). Otherwise, the configuration replacement operation fails.

•Make sure that the switch also has sufficient free memory to execute the configuration replacement or rollback configuration commands.

•Certain configuration commands, such as those pertaining to physical components of a networking device (for example, physical interfaces), cannot be added or removed from the running configuration.

–A configuration replacement operation cannot remove the interface interface-id command line from the running configuration if that interface is physically present on the device.

–The interface interface-id command line cannot be added to the running configuration if no such interface is physically present on the device.

•When using the configure replace command, you must specify a saved configuration as the replacement configuration file for the running configuration. The replacement file must be a complete configuration generated by a Cisco IOS device (for example, a configuration generated by the copy running-config destination-url command).

Note If you generate the replacement configuration file externally, it must comply with the format of files generated by Cisco IOS devices.

Configuring the Configuration Archive

Using the configure replace command with the configuration archive and with the archive config command is optional but offers significant benefit for configuration rollback scenarios. Before using the archive config command, you must first configure the configuration archive. Starting in privileged EXEC mode, follow these steps to configure the configuration archive:

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

archive

Enter archive configuration mode.

Step 3 

path url

Specify the location and filename prefix for the files in the configuration archive.

Step 4 

maximum number

(Optional) Set the maximum number of archive files of the running configuration to be saved in the configuration archive.

number—Maximum files of the running configuration file in the configuration archive. Valid values are from 1 to 14. The default is 10.

Note Before using this command, you must first enter the path archive configuration command to specify the location and filename prefix for the files in the configuration archive.

Step 5 

time-period minutes

(Optional) Set the time increment for automatically saving an archive file of the running configuration in the configuration archive.

minutes—Specify how often, in minutes, to automatically save an archive file of the running configuration in the configuration archive.

Step 6 

end

Return to privileged EXEC mode.

Step 7 

show running-config

Verify the configuration.

Step 8 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

Performing a Configuration Replacement or Rollback Operation

Starting in privileged EXEC mode, follow these steps to replace the running configuration file with a saved configuration file:

 
Command
Purpose

Step 1 

archive config

(Optional) Save the running configuration file to the configuration archive.

Note Enter the path archive configuration command before using this command.

Step 2 

configure terminal

Enter global configuration mode.

Step 3 

 

Make necessary changes to the running configuration.

Step 4 

exit

Return to privileged EXEC mode.

Step 5 

configure replace target-url [list] [force] [time seconds] [nolock]

Replace the running configuration file with a saved configuration file.

target-url—URL (accessible by the file system) of the saved configuration file that is to replace the running configuration, such as the configuration file created in Step 2 by using the archive config privileged EXEC command.

list—Display a list of the command entries applied by the software parser during each pass of the configuration replacement operation. The total number of passes also appears.

force— Replace the running configuration file with the specified saved configuration file without prompting you for confirmation.

time seconds—Specify the time (in seconds) within which you must enter the configure confirm command to confirm replacement of the running configuration file. If you do not enter the configure confirm command within the specified time limit, the configuration replacement operation is automatically stopped. (In other words, the running configuration file is restored to the configuration that existed before you entered the configure replace command).

Note You must first enable the configuration archive before you can use the time seconds command line option.

nolock—Disable the locking of the running configuration file that prevents other users from changing the running configuration during a configuration replacement operation.

Step 6 

configure confirm

(Optional) Confirm replacement of the running configuration with a saved configuration file.

Note Use this command only if the time seconds keyword and argument of the configure replace command are specified.

Step 7 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

LLDP-MED Location TLV

This release supports the Link Layer Discovery Protocol Media Extensions (LLDP-MED) location TLV. The location TLV provides location information from the switch to the endpoint device. It can send this information:

•Civic location information

Provides the civic address information and postal information. Examples of civic location information are street address, road name, and postal community name information.

•ELIN location information

Provides the location information of a caller. The location is determined by the Emergency location identifier number (ELIN), which is a phone number that routes an emergency call to the local public safety answering point (PSAP) and which the PSAP can use to call back the emergency caller.

Configuring Private VLANs

This section describes how to configure private VLANs on the Cisco Catalyst Blade Switch 3040 for FSC.

Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release.

The chapter consists of these sections:

•"Understanding Private VLANs" section

•"Configuring Private VLANs" section

•"Monitoring Private VLANs" section

Note When you configure private VLANs, the switch must be in VTP transparent mode. For more information about VTP, see the software configuration guide.

Understanding Private VLANs

The private-VLAN feature addresses two problems that service providers face when using VLANs:

•Scalability: The switch supports up to 1005 active VLANs. If a service provider assigns one VLAN per customer, this limits the numbers of customers the service provider can support.

•To enable IP routing, each VLAN is assigned a subnet address space or a block of addresses, which can result in wasting the unused IP addresses, and cause IP address management problems.

Using private VLANs addresses the scalability problem and provides IP address management benefits for service providers and Layer 2 security for customers.

Private VLANs partition a regular VLAN domain into subdomains and can have multiple VLAN pairs—one for each subdomain. A subdomain is represented by a primary VLAN and a secondary VLAN.

All VLAN pairs in a private VLAN share the same primary VLAN. The secondary VLAN ID differentiates one subdomain from another. See Figure 1.

Figure 1 Private-VLAN Domain

There are two types of secondary VLANs:

•Isolated VLANs—Ports within an isolated VLAN cannot communicate with each other at the Layer 2 level.

•Community VLANs—Ports within a community VLAN can communicate with each other but cannot communicate with ports in other communities at the Layer 2 level.

Private VLANs provide Layer 2 isolation between ports within the same private VLAN. Private-VLAN ports are access ports that are one of these types:

•Promiscuous—A promiscuous port belongs to the primary VLAN and can communicate with all interfaces, including the community and isolated host ports that belong to the secondary VLANs associated with the primary VLAN.

•Isolated—An isolated port is a host port that belongs to an isolated secondary VLAN. It has complete Layer 2 separation from other ports within the same private VLAN, except for the promiscuous ports. Private VLANs block all traffic to isolated ports except traffic from promiscuous ports. Traffic received from an isolated port is forwarded only to promiscuous ports.

•Community—A community port is a host port that belongs to a community secondary VLAN. Community ports communicate with other ports in the same community VLAN and with promiscuous ports. These interfaces are isolated at Layer 2 from all other interfaces in other communities and from isolated ports within their private VLAN.

Note Trunk ports carry traffic from regular VLANs and also from primary, isolated, and community VLANs.

Primary and secondary VLANs have these characteristics:

•Primary VLAN—A private VLAN has only one primary VLAN. Every port in a private VLAN is a member of the primary VLAN. The primary VLAN carries unidirectional traffic downstream from the promiscuous ports to the (isolated and community) host ports and to other promiscuous ports.

•Isolated VLAN—A private VLAN has only one