Table Of Contents
Release Notes for the
Cisco ME 3400 Ethernet Access Switch, Cisco IOS Release 12.2(46)SEFinding the Software Version and Feature Set
Recovering from a Software Failure
Minimum Cisco IOS Release for Major Features
Updates to the Software Configuration Guide
Updates to the System Message Guide
Update to the Hardware Installation Guide
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the
Cisco ME 3400 Ethernet Access Switch, Cisco IOS Release 12.2(46)SE
Revised October 22, 2008
Cisco IOS Release 12.2(46)SE runs on the Cisco ME 3400 Series Ethernet Access switches.
These release notes include important information about Cisco IOS Release 12.2(46)SE and any limitations, restrictions, and caveats that apply to the release. 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.
•
•
For the complete list of Cisco ME 3400 switch documentation, see the "Related Documentation" 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:
•
•
•
Hardware Supported
Table 1 lists the hardware supported on Cisco IOS Release 12.2(46)SE.
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
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.
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:
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
To download software, follow these steps:
Step 1
Step 2
http://www.cisco.com/pcgi-bin/Software/Iosplanner/Planner-tool/iosplanner.cgi
Click on "Launch the IOS Upgrade Planner" and search for ME 3400 to download the appropriate files:
•
•
Step 3
For more information, refer to Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-address
Note
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
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /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/me340x-metroipaccess-tar.122.46.SE.tarYou 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:
•
•
•
New Features
These sections describe the new supported hardware and the new software features provided in this release:
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(46)SE:
•
•
•
•
•
•
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 3400 switch. Features not listed are supported in all releases.
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
These are the configuration limitations:
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•
–
–
–
No workaround is necessary; these are the designed behaviors. (CSCed50819)
•
However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. (CSCed79734)
•
When you enter the show ip arp inspection log privileged EXEC command, the log entries from all switches in the stack are moved to the switch on which you entered the command.
There is no workaround. (CSCed95822)
•
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
EtherChannel
This is the EtherChannel limitation:
•
15:50:11: %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Port-channel1 (ifindex 1632) -Traceback= A585C B881B8 B891CC 2F4F70 5550E8 564EAC 851338 84AF0C 4CEB50 859DF4 A7BF28 A98260 882658 879A58
There is no workaround. (CSCsh12472)
IP
This is the IP limitation:
•
MAC Addressing
This is the MAC addressing limitation:
When a MAC address is configured for filtering on the internal VLAN of a routed port, incoming packets from the MAC address to the routed port are not dropped. (CSCeb67937)
Multicasting
These are the multicasting limitations:
•
•
•
•
•
•
–
–
There is no workaround. (CSCec20128)
•
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•
–
–
The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)
REP
This is the Resilient Ethernet Protocol (REP) limitation:
•
–
–
–
–
–
You cannot enable these functions on REP segments without edge ports.
Routing
These are the routing limitations:
•
•
•
–
–
–
The workaround is to change any one of the listed conditions. (CSCed53633)
QoS
These are the quality of service (QoS) limitations:
•
There is no workaround, but it is unlikely that a CBWFQ class would be configured with such a low CIR bandwidth. (CSCsb98219)
•
There is no workaround. (CSCsk00594)
SPAN and RSPAN
These are the SPAN and Remote SPAN (RSPAN) limitations.
•
There is no workaround. If possible, disable multicast routing. If possible, use ingress SPAN to observe the same traffic. (CSCeb01216)
•
•
There is no workaround. (CSCsj21718)
•
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:
•
•
VLAN
These are the VLAN limitations:
•
The workaround is to not configure more than the recommended number of VLANs and trunks. (CSCeb31087)
•
There is no workaround. (CSCed71422)
Open Caveats
This section describes the open caveats in this software release.
•
If you enter the no ip vrf vrf-name global configuration command to delete a VPN routing/forwarding instance on the switch when routing is not enabled on the switch, the VRF instance is held in the delete queue. The VRF entry does not appear in the output when you enter the show running-config privileged EXEC command, but it is shown when you enter the show ip vrf privileged EXEC command. When a VRF instance is in the deleted queue, it is using one of the system's maximum allowable VRFs, and you cannot configure a new VRF with the same name.
The workaround is to enable IP routing on the switch by entering the ip routing global configuration. When you enable routing, the VRF is cleared from the deleted queue.
•
When several per-port, per-VLAN parent policies are attached to the input of one or more interfaces and a child policy of these parent policies is modified, the parent policies are detached from the interfaces and reattached during the process. Because the modified policy is large, the TCAM entries are being used up, and the attached policies should be removed. However, some of the parent policies are not removed from the interface, and the TCAM entries are cleared. If you save the configuration and reload the switch, the policies are detached, but the TCAM is full, and you cannot attach other policies.
This error message appears:
QOSMGR-4-QOS_TCAM_RESOURCE_EXCEED_MAX: Exceeded a maximum of QoS TCAM resources
The workaround is to manually detach the policy maps from all the interfaces by entering the no service-policy input policy-map-name interface configuration command on each interface.
•
When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.
The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command.
•
A switch intermittently fails and displays this error message when the uni-vlan community configuration is in the switch running configuration:
Traceback= B941C4 1AA018 19610C 1930B8 BD0720 BC7D0CJun 2 09:30:45.325 MDT: %SCHED-7-WATCH: Attempt to lock uninitializedwatched semaphore (address 0).The traceback is seen due to the presence of the command "uni-vlan community".You only need to do one of these workaround:
–
–
Resolved Caveats
These are the caveats that have been resolved in this release:
•
A switch no longer fails under these conditions:
–
–
•
If you configure IP SLA to generate a syslog message for a reaction trap and an operation with a trigger of timeout or connectionless, a syslog message now appears when triggered.
•
Traceback messages no longer appear if you enter the no switchport interface configuration command to change a Layer 2 interface from a port channel to a routed port.
•
When you clear counters on an interface and then disable storm control on that interface, an incorrect value (an unusually large number) for McastSuppDiscards no longer appears when you enter the show interface counters privileged EXEC command. This could occur when the interface had storm control enabled and experienced traffic with a data rate higher than the storm-control threshold so that storm control is dropping packets.
•
The switch no longer reloads with no stack trace information if you try to configure REP when there is a large number of MAC addresses (more than 8000) on more than 900 VLANs on the switch.
•
A traceback error appeared when you entered the show aaa subscriber profile privileged EXEC command. This command is not supported on the switch and has been removed from the command-line interface.
•
The default queue limit for QoS has been changed from 48 to 160 (256-byte) packets.
•
If you specify the router ID before entering the autonomous-system autonomous-system-number address-family configuration command, the router ID is no longer lost when the switch reloads.
•
Any form of the passive-interface command entered in one instance propagates to all configured address-family instances for the same EIGRP routing process.
•
When the ip pim sparse-mode and ip wccp web-cache redirect in configuration commands are applied on a global table interface, traffic is now sent to multicast receivers.
•
Outgoing packets are no longer dropped from an interface with policy-based routing (PBR):
–
–
•
An end host no longer remains in the guest VLAN after IEEE 802.1X authentication.
•
The ip sla responder global configuration command no longer has to be removed and then added again to the running configuration after you reload a switch.
•
A debug exception error that causes the switch to fail no longer occurs. In previous releases, this failure occurred when one or more switches were configured in the same Resilient Ethernet Protocol (REP) segment.
•
The IP SLA Ethernet MIB no longer returns the incorrect value for the sum of squares of the positive jitter from destination to source.
•
When IEEE 802.1x is enabled on the switch, EAP notification packets are no longer dropped.
Documentation Updates
This section contains these documentation updates:
•
•
•
Updates to the Software Configuration Guide
This information is added to the "Using Route Maps to Redistribute Routing Information" section in the "Configuring IP Unicast Routing" chapter:
Note
Updates to the System Message Guide
These sections include messages that have been added to, changed. or deleted in the system message guide.
New System Messages
These new messages have been added to the system message guide:
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars]Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. [enet] is the supplicant MAC address, and [chars] is the interface. This message might appear if the IEEE 802.1x feature is enabled.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, manually remove it from that port.
Error Message %PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED: Unable to create [chars]Explanation The switch cannot create the specified managed object. [chars] is the object name.
Recommended Action No action is required.
Error Message %PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER: PAgP running on [chars] informing virtual switches of dual-active: new active id [enet], old id [enet]Explanation Port Aggregation Protocol (PAgP) received a new active ID on the specified interface, which means that all virtual switches are in a dual-active scenario. The interface is informing virtual switches of this, which causes one switch to go into recovery mode. [chars] is the interface. The first [enet] is the new active ID. The second [enet] is the ID that it replaces.
Recommended Action No action is required.
Error Message %PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR: Failure in adding to [chars] registryExplanation The switch could not add a function to the registry. [chars] is the registry name.
Recommended Action No action is required.
Error Message %PM-6-EXT_VLAN_ADDITION: Extended VLAN is not allowed to be configured in VTP CLIENT mode.Explanation The switch did not add a VLAN in VTP client mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section in the system message guides.
Error Message SPANTREE-6-PORTADD_ALL_VLANS: [chars] added to all VlansExplanation The interface has been added to all VLANs. [chars] is the added interface.
Recommended Action No action is required.
Error Message SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all VlansExplanation The interface has been deleted from all VLANs. [chars] is the deleted interface.
Recommended Action No action is required.
Error Message SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].Explanation The VLAN Trunking Protocol (VTP) domain name was changed through the configuration to the name specified in the message. [chars] is the changed domain name.
Recommended Action No action is required.
Error Message PLATFORM_ENV-1-DUAL_PWR: Faulty internal power supply [chars] detectedExplanation A faulty internal power supply was detected in one of the two power supplies on the switch. [chars] is the power supply name.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Tracebacks Reports" section of the system message guide.
Error Message PLATFORM_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefixExplanation A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ip unicast failed route privileged EXEC command lists the failed prefixes.
Recommended Action No action is required.
Error Message REP-4-LINKSTATUS: [chars] (segment [dec]) is [chars]Explanation The Resilient Ethernet Protocol (REP) link status has changed. The first [chars] is the interface name that has a link-status change. The [dec] is the REP segment number of the interface. The second [chars] is the new link status.
Recommended Action No action is required.
Error Message REP-5-PREEMPTIONFAIL: can not perform preemption on segment [dec] due to [char]Explanation The Resilient Ethernet Protocol (REP) preempt operation failed. This could be due to an invalid port ID or a neighbor_offset number specified with the rep block port interface configuration command. This could also be caused by entering the rep block port preferred interface configuration command if there is no REP port configured with the preferred keyword. [dec] is the segment number, and [char] is the reason for the failure.
Recommended Action Correct the configuration, and run REP manual preemption on the primary edge port by entering the rep preempt segment command.
Changed System Message
This system message has changed (both explanation and action).
Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will remain stand-alone.Explanation The aggregation port is down. The port remains standalone until the aggregation port is up. The first [chars] is the EtherChannel. The second [chars] is the port number.
Recommended Action Ensure that the other ports in the bundle have the same configuration.
Deleted System Messages
These system messages have been deleted.
Error Message %VQPCLIENT-2-INITFAIL: Platform-specific VQP initialization failed. QuittingError Message %VQPCLIENT-2-IPSOCK: Could not obtain IP socketError Message %VQPCLIENT-7-NEXTSERV: Trying next VMPS [IP_address]Error Message %VQPCLIENT-7-PROBE: Probing primary server [IP_address]Error Message %VQPCLIENT-2-PROCFAIL: Could not create process for VQP. QuittingError Message %VQPCLIENT-7-RECONF: Reconfirming VMPS responsesError Message %VQPCLIENT-2-SHUTDOWN: Interface [chars] shutdown by VMPSError Message %VQPCLIENT-3-THROTTLE: Throttling VLAN change on [chars]Update to the Hardware Installation Guide
This is an installation update to the Cisco ME3400 Hardware Installation Guide.
Cisco Ethernet Switches are equipped with cooling mechanisms, such as fans and blowers. However, these fans and blowers can draw dust and other particles, causing contaminant buildup inside the chassis, which can result in a system malfunction.
You must install this equipment in an environment as free as possible from dust and foreign conductive material (such as metal flakes from construction activities).
These standard provide guidelines for acceptable working environments and acceptable levels of suspended particulate matter:
•
•
•
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/ps6580/tsd_products_support_series_home.html
•
•
•
•
•
•
•
•
•
•
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
–
–
–
–
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
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)
© 2008 Cisco Systems, Inc. All rights reserved.
Guest
