Release Notes for the Cisco Catalyst Blade Switch 3130 and 3032 for Dell, Cisco IOS Release 12.2(58)SE1
Available Languages
Table Of Contents
Device Manager System Requirements
Cisco Network Assistant Compatibility
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Minimum Cisco IOS Release for Major Features
Cisco X2 Transceiver Modules and SFP Modules
Updates to the Switch Getting Started Guide
Updates to the Software Configuration Guide
Correction to the "Configuring STP" Chapter
Correction to the "Configuring Network Security with ACLs" Chapter
Correction to the "Unsupported Commands" Chapter
Updates for the System Message Guide
Obtaining Documentation and Submitting a Service Request
Release Notes for the Cisco Catalyst Blade Switch 3130 and 3032 for Dell, Cisco IOS Release 12.2(58)SE1
Revised December 22, 2011
Note
Cisco IOS Release 12.2(58)SE images for all platforms were removed from Cisco.com because of a severe defect, CSCto62631. The solution for the defect is in Cisco IOS Release 12.2(58)SE1.
Cisco IOS Release 12.2(58)SE1 runs on the Cisco Catalyst Blade Switch 3130 and 3032 for Dell switches. The Cisco Catalyst Blade Switch 3130 supports support stacking through Cisco StackWise Plus technology. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note
These release notes include important information about Cisco IOS Release 12.2(58)SE and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:
•
•
•
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpmFor the complete list of the Cisco Catalyst Blade Switch 3130 and 3032 for Dell documentation, see the "Related Documentation" section.
Contents
•
•
•
•
•
•
•
•
System Requirements
•
•
Hardware Supported
Table 1 Cisco Catalyst Blade Switch 3130 for Dell and 3032 for Dell Supported Hardware
CBS3032G1 , CBS3130G-S, and CBS3130X-S
•
•
•
•
Cisco IOS Release 12.2(40)EX1
Cisco X2 transceiver modules
X2-10GB-SR
X2-10GB-LRM
X2-10GB-CX4X2-10GB-LR
X2-10GB-LX412.2(40)EX3
12.2(46)SE
SFP modules3
GLC-T
GLC-SX-MM
GLC-LH-SM12.2(40)EX3
Supports OneX (CVR-X2-SFP10G) and these SFP+ modules
(For the Catalyst Blade Switch 3130)
SFP-10G-SR
Only version 02 or later CX14 cables are supported:
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5MCisco IOS Release 12.2(55)SE1
1 This switch supports only the IP base software image.
2 X2 supported only on the CBS3130X-S model.
3 SFP = small form-factor pluggable
4 The CX1 cables are used with the OneX converters.
Caution
Device Manager System Requirements
•
•
Hardware Requirements
Table 2 Minimum Hardware Requirements
233 MHz minimum1
512 MB2
256
1024 x 768
Small
1 We recommend 1 GHz.
2 We recommend 1-GB DRAM.
Software Requirements
•
•
The device manager verifies the browser version when starting a session and does not require a plug-in.
Cisco Network Assistant Compatibility
Cisco IOS 12.2(40)EX1 and later is only compatible with Cisco Network Assistant 5.3 and later. You can download Network Assistant from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistant
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
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. 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.
Note
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 command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Table 3 lists the filenames for this software release.
Note
The universal software images support multiple feature sets. Use the software activation feature to deploy a software license and to enable a specific feature set. For information about software activation, see the Cisco Software Activation for Dell document on Cisco.com:
http://www.cisco.com/en/US/products/ps8742/products_installation_and_configuration_guides_list.html
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 from 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:
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
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/docs/ios/fundamentals/command/reference/cf_t1.html
Upgrading a Switch by Using the Device Manager or Network Assistant
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note
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
Step 2
a.
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm
b.
c.
d.
Download the image you identified in Step 1.
Step 3
For more information, see Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, see 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/image-name.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 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:
•
•
•
•
New Software Features
•
•
•
•
•
•
•
•
•
•
•
•
•
Minimum Cisco IOS Release for Major Features
Table 4 lists the minimum software release (after the first release) required to support the major features of the Catalyst Blade Switch 3130 and 3032 for Dell. 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.
•
•
Cisco IOS Limitations
•
•
•
•
Access Control List
•
There is no workaround. (CSCse33114)
•
The workaround is to block traffic from the specific MAC address by using the mac address-table static mac-addr vlan vlan-id drop global configuration command. (CSCse73823)
Address Resolution Protocol
•
The workaround is to set the burst interval to more than 1 second. We recommend setting the burst interval to 3 seconds even if you are not experiencing this problem.(CSCse06827))
Cisco X2 Transceiver Modules and SFP Modules
•
The workaround is to use Cisco X2-10GB-LX4 transceiver modules with a version identification number of V03 or later. (CSCsh60076)
•
Use one of these workarounds:
–
–
–
•
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
Configuration
•
PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 0, class 51, max_msg 128, total throttled 984323
-Traceback= 6625EC 5DB4C0 5DAA98 55CA80 A2F2E0 A268D8No workaround is necessary. Under normal conditions, the switch generates this notification when snooping the next ARP packet. (CSCse47548)
•
The workaround is to not configure VLANs with protected ports as part of a fallback bridge group. (CSCsg40322)
•
The workaround is to stop the traffic in the direction in which it is not being forwarded, and then restart it after 2 seconds. You can also use the shutdown interface configuration command followed by the no shutdown command on the interface. (CSCsh04301)
•
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port.(CSCsi26392)
•
There is no workaround. (CSCec74610)
•
There is no workaround. It does not impact functionality. (CSCta72141)
EtherChannel
•
–
–
The EtherChannel ports are put in the suspended state because each partitioned stack sends LACP packets with different LACP Link Aggregation IDs (the system IDs are different). The ports that receive the packets detect the incompatibility and shut down some of the ports. Use one of these workarounds for ports in this error-disabled state:
–
–
The EtherChannel ports are put in the error-disabled state because the switches in the partitioned stacks send STP BPDUs. The switch or stack at the other end of the EtherChannel receiving the multiple BPDUs with different source MAC addresses detects an EtherChannel misconfiguration.
After the partitioned stacks merge, ports in the suspended state should automatically recover. (CSCse33842)
•
No workaround is necessary. The problem corrects itself after the link-up or link-down event. (CSCse75508)
•
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 879A58There is no workaround. (CSCsh12472)
HSRP
•
There is no workaround. (CSCth00938)
IEEE 802.1x Authentication
•
Use one of these workarounds (CSCsd90495):
–
–
•
–
–
Use one of these workarounds (CSCse04534):
–
–
•
The workaround is not use the VLAN assignment option. (CSCse22791)
Multicasting
•
–
–
–
The workaround is to not generate multicast packets with a TTL value of 0 or 1, or disable multicast routing in the VLAN. (CSCeh21660)
•
–
–
–
There is no workaround. (CSCei08359)
•
The workaround is to not send RPF-failed multicast traffic, or make sure that the source IP address of the RPF-failed packet is reachable. (CSCsd28944)
•
There is no workaround. (CSCsd45753)
•
No workaround is necessary because the problem corrects itself when the rate or number of IGMP reports are reduced. (CSCse27757)
•
–
–
–
The workaround is to disable the IGMP snooping throttle limit by using the no ip igmp max-groups number interface configuration command and then to reconfigure the same limit again. (CSCse39909)
QoS
•
There is no workaround. (CSCeh18677)
•
There is no workaround. (CSCsc63334)
•
The workaround is to use a different name for the interface-level policy map. (CSCsd84001)
•
There is no workaround. (CSCsd72001)
•
There is no workaround. (CSCsg79627)
•
Use one of these workarounds:
–
–
•
01:01:32: %BIT-4-OUTOFRANGE: bit 1321 is not in the expected range of 0 to 1024There is no impact to switch functionality.
There is no workaround. (CSCtg32101)
RADIUS
RADIUS change of authorization (COA) reauthorization is not supported on the critical auth VLAN.
There is no workaround. (CSCta05071)
Routing
•
–
–
The workaround is to reduce the number of OSPF neighbors to 200 or less. (CSCse65252)
•
The workaround is to not send traffic to unknown destinations. (CSCse97660)
SPAN and RSPAN
•
There is no workaround. This is a hardware limitation. (CSCei10129)
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
Stacking
•
The workaround is to use the logging monitor global configuration command to set the severity level to block the low-level messages on the stack member consoles. (CSCsd79037)
•
The workaround is to reboot the new member switch. Use the remote command all show run privileged EXEC command to compare the running configurations of the stack members. (CSCsf31301)
•
The workaround is to delete files in the flash memory to create more free space. (CSCsg30073)
•
–
–
–
You can use one of these workarounds:
–
–
•
The workaround is to apply the switch provision configuration before you reboot the switch. Enter both the switch current-stack-member-number renumber new-stack-member-number and the switch stack-member-number provision type global configuration commands, and reload the switch. (CSCsl63862)
•
The workaround is to use the session stack-member-number privileged EXEC command. (CSCsz38090)
VLANs
•
The workaround is to enter the shutdown and no shutdown interface configuration commands on the port to reset the authentication status. (CSCsf98557)
•
The workaround is to remove unnecessary VLANs to reduce CPU utilization when many links are flapping. (CSCtl04815)
Device Manager Limitations
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
•
The workaround when using Firefox is to either temporarily or permanently accept the certificate. If you temporarily accept the certificate, close and then reopen the Firefox browser window. If you permanently accept the certificate, delete the certificate, then close and restart Firefox:
–
–
The workaround when using Internet Explorer is to click Click here for Options in the warning message and click Display Blocked Content. Close the browser window and launch a new session. (CSCsk80229)
Important Notes
•
Cisco IOS Notes
•
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.
•
AutoQoS Error: ciscophone input service policy was not properly appliedpolicy map AutoQoS-Police-CiscoPhone not configuredIf 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
•
•
•
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
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 launch the device manager.
Open Caveats
•
When you make port security changes on an interface, such as configuring aging time, violations, or aging type, error messages and tracebacks might appear.
There is no workaround.
•
Unicast EIGRP packets destined for the switch are sent to the host queue instead of to the higher priority routing protocol queue.
Note
There is no workaround.
•
When a switch or switch stack running Multiple Spanning Tree (MST) is connected to a switch running Rapid Spanning Tree Protocol (RSTP), the MST switch acts as the root bridge and runs per-VLAN spanning tree (PVST) simulation mode on boundary ports connected to the RST switch. If the allowed VLAN on all trunk ports connecting these switches is changed to a VLAN other than VLAN 1 and the root port of the RSTP switch is shut down and then enabled, the boundary ports connected to the root port move immediately to the forward state without going through the PVST+ slow transition.
There is no workaround.
•
When a switch is using a DHCP server to assign IP addresses and an interface on the switch has RIP enabled, if the switch reloads, the interface loses some RIP configuration (specifically RIP authentication mode and RIP authentication key-chain). This does not happen when the IP address is statically configured on the interface. The problem occurs only when you configure RIP before an IP address is assigned by the DHCP server.
There is no workaround, but you can use an embedded event manager (EEM) script to add the interface configuration commands on the interface:
ip rip authentication mode
ip rip key-chain
•
When you configure a port to be in a dynamic VLAN by entering the switchport access vlan dynamic interface configuration command on it, the switch might reload when it processes ARP requests on the port.
The workaround is to configure static VLANs for these ports.
Resolved Caveats
•
When you enter the show inventory command on a switch that has an X2 module, the output incorrectly reports the X2 module version ID (VID) as V01 even though the label has a higher VID.
There is no workaround.
•
When you reload a stack master, the ip vrf forwarding command does not appear in the running configuration, which causes AAA authentication to fail. This issue does not occur with standalone switches.
The workaround is to reenter the ip vrf forwarding command.
•
A Link Aggregation Control Protocol (LACP) bundle takes up to 70 seconds to form when NetFlow sampling is enabled.
The workaround is to disable NetFlow sampling.
•
When you configure a switch to send messages to a syslog server in a VPN Routing and Forwarding (VRF) instance, the messages are not sent to the server.
The workaround is to remove the VRF configuration.
•
When ports in an EtherChannel are linking up, the message
EC-5-CANNOT_BUNDLE2might appear. This condition is often self-correcting, indicated by the appearance ofEC-5-COMPATIBLEmessage following the first message. On occasion, the issue does not self-correct, and the ports may remain unbundled.The workaround is to reload the switch or to restore the EtherChannel bundle by shutting down and then enabling the member ports and the EtherChannel in this order:
–
–
–
–
•
A Cisco Catalyst 3130 switch that is a member of a switch stack frequently reports that a redundant power system (RPS) is faulty even though there is no RPS installed and the switch is receiving power from the blade server chassis:
Jun 9 13:41:15: %PLATFORM_ENV-1-PWR_RPS: Redundant power supply faulty or in standby mode
Jun 9 13:42:38: %PLATFORM_ENV-1-PWR_RPS: Redundant power supply faulty or in standby mode (switchB-2)
Jun 9 13:46:16: %PLATFORM_ENV-1-PWR_RPS: Redundant power supply faulty or in standby mode
Jun 9 13:47:39: %PLATFORM_ENV-1-PWR_RPS: Redundant power supply faulty or in standby mode (switchB-2)Use one of these workarounds to filter the RPS message:
–
For example
Switch(config)# logging discriminator filter1 mnemonics drops PWR_RPSSwitch(config)# logging buffered discriminator filter1Switch(config)# logging console discriminator filter1Switch(config)# logging host ip-address discriminator filter1–
•
When you connect a switch as a VLAN Trunk Protocol (VTP) client to a Catalyst 4000 switch configured as a VTP client or server and the VTP database contains more than 512 VLANs, the database is not correctly updated.
The workaround is to connect the VTP client directly to a Catalyst 6500 VTP server.
•
A host switch connected to a stack member switch can download a downloadable access control list (dACL) with more than 13 access control entries, but the dACL is not applied to an interface.
There is no workaround.
•
This message appears after inserting the CVR-X2-SFP converter module and the X2-10GB-SR transceiver modules in the10-Gigabit slots of the Catalyst 3750-E and 3560-E switches:
%GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Te1/0/1 has bad crcThere is no workaround.
•
When a Catalyst 3750-E or 3560-E switch has a 10/100/1000BASE-TX SFP module installed in a TwinGig SFP Converter Module, and you configure the SFP module to send at 100 Mb/s, save the configuration, and reload the switch, the speed setting is not saved to the running configuration.
There is no workaround.
•
On a stack member, the show interface command output incorrectly displays a media-type setting.
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch.
•
The switch does not generate SNMP traps when a power supply is disconnected.
There is no workaround.
•
Enabling the Cisco Discovery Protocol (CDP) on a tunnel interface causes the switch to fail when a a CDP packet is received on the interface.
Note
The workaround is to use the no cdp enable interface configuration command to disable CDP on the interface.
•
When a FlexLinks backup interface is configured on a member switch in a switch stack, the backup interface incorrectly shows that all VLANs are in the forwarding state.
The workaround is to use the show interface trunk interface configuration command to display the status of the backup link.
•
When you configure storm control with range command on two interfaces that belong to an EtherChannel group, this message appears:
%SYS-3-CPUHOG: Task is running for (2097)msecs, more than (2000)msecs (0/0), process = Virtual Exec.The workaround is to configure storm control on a port channel interface.
•
When MAC Authentication Bypass (MAB) is used in multi-authentication mode, a security violation occurs after successful authentication.
The workaround is to use a different authentication mode (single, multidomain or multihost).
•
The config.text.backup file is present after the switch is restored to the factory defaults.
There is no workaround.
•
When you enter the ipv6 traffic-filter interface configuration command, it might not filter traffic as expected, and it might allow traffic to pass through.
There is no workaround.
•
QoS ACL commands might appear differently in the running configuration after the master switch is reloaded or removed from the stack. The functionality of the commands remains the same.
There is no workaround.
•
When you disconnect the spanning tree protocol (STP) peer link, the STP port path cost configuration changes.
There is no workaround.
•
Two stacks that have members with fiber SFP modules are connected in a cross-stack EtherChannel with this configuration:
–
–
If a member in one stack is reloaded, this error message appears on a member switch port in the other stack and the port is error disabled.
%PLATFORM_PM-3-INTVLANINUSE: internal vlan-id 1012 allocated for interface Gi2/0/2 is still in use (3750-b-2)-Traceback= 173E7F0 198F40C 176DA04 1774E70 173FBDC 1744574 16C9C28 17C65C4 17C67D8 1BB7308 1BADD78 (3750-b-2)The workaround is to configure Layer 2 EtherChannels with SVIs and to use the EtherChannel Active mode.
•
When a spanning-tree bridge protocol data unit (BPDU) is received on an 802.1Q trunk port and has a VLAN ID is greater than or equal to 4095, the spanning-tree lookup process fails.
There is no workaround.
•
On a switch running Protocol-Independent Multicast (PIM) and Source Specific Multicast (SSM), multicast traffic might not be sent to the correct port after the switch reloads.
The workaround is to enter the clear ip route privileged EXEC command or reconfigure PIM and SSM after a reload.
•
When a stack is running per-VLAN spanning-tree plus (PVST+) and you create a VLAN, the STP topology change resets the aging time for all members and ages out all the MAC addresses for the new VLAN. If a cookie for the new VLAN on the member is not created when the master sends the member an HRPC message to update the aging timer, the member changes the aging time for VLAN 1 to that set during the topology change.
After the topology change, the aging time for the new VLAN is reset to that before the STP topology changed. However, the aging time for VLAN 1 does not change. The MAC addresses learned on VLAN 1 and on the member switch ports age out before aging time for the new VLAN.
The workaround is to disable STP before creating a new VLAN in the stack.
•
When you enter the default interface, switchport, or no switchport interface configuration command on the switch, this message appears: EMAC phy access error, port 0, retrying......
There is no workaround.
•
On a switch running Cisco IOS Release 12.2(55)SE with the parser config cache interface global configuration command in the configuration, when you use the CISCO-MAC-NOTIFICATION-MIB to enable the SNMP MAC address notification trap, the trap is enabled, but the trap setting does not appear in the switch configuration.
The workaround is to remove the parser config cache interface command from the configuration.
•
The CPU usage on a standalone switch varies as the switch updates the running configuration.
There is no workaround.
•
When the switch stack elects a new stack master, by default the MAC address of the new master becomes the stack MAC address. Configuring a persistent MAC address sets a delay after stack master change before the stack master MAC address change. A timer value of 0 means that the MAC address of the current master is used indefinitely.
When you enter the stack-mac persistent timer 0 global configuration command on a stack and the master switch is not the original owner of the stack MAC address, ports on member switches do not go through Rapid Spanning Tree Protocol (STP) transitions directly into the forwarding state.
The workaround is to not use the stack-mac persistent timer 0 command on the switch stack.
•
When 802.1x MAC authentication bypass with multidomain authentication and critical VLAN are enabled on an interface on a switch running Cisco IOS Release 12.2(53)SE or later, if the switch loses connectivity with the AAA server, the switch might experience high CPU usage and show these messages:
AUTH-EVENT (Gi0/15) Received clear security violationAUTH-EVENT (Gi0/15) dot1x_is_mab_interested_in_mac: Still waiting for a MAC on port GigabitEthernet0/15There is no workaround.
•
Neighbor discovery fails for IPv6 hosts connected to the switch when the IPv6 MLD snooping feature is enabled globally on the switch.
The workaround is to disable IPv6 MLD snooping on the switch.
•
The port manager callback might cause more than 90% CPU usage for up to 20 minutes under these conditions:
–
–
The workaround is to disable VTP pruning.
•
The switch sends temperature trap messages when its temperature is between 58 and 60° C.
There is no workaround.
•
A switch running Cisco IOS Release 12.2(58)SE might reload if:
–
–
Use one of these workarounds:
–
–
–
Documentation Updates
Note
http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
•
•
•
Updates to the Switch Getting Started Guide
When you launch Express Setup, you are prompted for the switch password. Enter the default password, cisco. The switch ignores text in the username field. Before you complete and exit Express Setup, you must change the password from the default password, cisco.
Updates to the Software Configuration Guide
Correction to the "Configuring STP" Chapter
In the "Displaying the Spanning-Tree Status" section of the "Configuring STP" chapter, this note should appear:
Note
Correction to the "Configuring Network Security with ACLs" Chapter
The "Creating a Numbered Extended ACL" section of the "Configuring Network Security with ACLs" chapter has an error. Contrary to the note in this section, ICMP echo-replies can be filtered.
Correction to the "Unsupported Commands" Chapter
The "Miscellaneous" section of the "Unsupported Commands" chapter should include the logging discriminator global configuration command.
Updates for the System Message Guide
New System Messages
Error Message IP-3-SBINIT: Error initializing [chars] subblock data structure. [chars]Explanation The subblock data structure was not initialized. [chars] is the structure identifier.
Recommended Action No action is required.
Error Message VLMAPLOG-6-ARP: vlan [dec] (port [chars]) denied arp ip [inet] -> [inet], [dec] packet[chars]Explanation A packet from the virtual LAN (VLAN) that matches the VLAN access-map (VLMAP) log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-L4: vlan [dec] (port [chars]) denied [chars] [inet]([dec]) -> [inet]([dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [chars] is the protocol, the first [inet] is the source IP address, the second [dec] is the source port, the second [inet] is the destination IP address, the third [dec] is the destination port, the fourth [dec] denotes the number of packets, and the third [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-IGMP: vlan [dec] (port [chars]) denied igmp [inet] -> [inet] ([dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Group Management Protocol (IGMP) message type, the third [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-ICMP: vlan [dec] (port [chars]) denied icmp [inet] -> [inet] ([dec]/[dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Control Message Protocol (ICMP) message type, the third [dec] is the ICMP message code, the fourth [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-IP: vlan [dec] (port [chars]) denied ip protocol=[dec] [inet] -> [inet], [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [dec] is the protocol number, the first [inet] is the source IP address, the second [inet] is the destination IP address, the third [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message AUTHMGR-7-STOPPING: Stopping '[chars]' for client [enet] on Interface [chars] AuditSessionID [chars]Explanation The authentication process has been stopped. The first [chars] is the authentication method, [enet] is the Ethernet address of the host, the second [chars] is the interface for the host, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message AUTHMGR-7-NOMOREMETHODS: Exhausted all authentication methods for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation All available authentication methods have been tried. The first [chars] is the client identifier, the second [chars]s is the interface for the client, and the third [chars] is the session ID.
Recommended Action No action is required.
Modified System Messages
Error Message AUTHMGR-5-MACMOVE: MAC address ([enet]) moved from Interface [chars] to Interface [chars]Explanation The client moved to a new interface but did not log off from the first interface. [enet] is the MAC address of the client, the first [chars] is the earlier interface, and the second [chars] is the newer interface.
Recommended Action No action is required.
Error Message AUTHMGR-5-MACREPLACE: MAC address ([enet]) on Interface [chars] is replaced by MAC ([enet])Explanation A new client has triggered a violation that caused an existing client to be replaced. The first [enet] is the first client, [chars] is the interface, the second [enet] is the new client.
Recommended Action No action is required.
Error Message MAB-5-FAIL: Authentication failed for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation Authentication was unsuccessful. The first [chars] is the client, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message MAB-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation Authentication was successful. The first [chars] is the client, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Deleted System Messages
Error Message IP-3-STCKYARPOVR: Attempt to overwrite Sticky ARP entry: [inet], hw: [enet] by hw: [enet]\n", MSGDEF_LIMIT_FASTExplanation Multiple stations are configured with the same IP address in a private VLAN. (This could be a case of IP address theft.) [inet] is the IP address that is configured, the first [enet] is the original MAC address associated with the IP address, and the second [enet] is the MAC address that triggered this message.
Recommended Action Change the IP address of one of the two systems.
Related Documentation
User documentation in HTML format includes the latest documentation updates and might be more current than the complete book PDF available on Cisco.com.
These documents provide complete information about the Cisco Catalyst Blade Switch 3130 and 3032 for Dell and are available from this Cisco.com site:
http://www.cisco.com/en/US/products/ps6748/tsd_products_support_series_home.html•
•
•
Note
•
•
•
•
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html–
–
–
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htmlSubscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2011 Cisco Systems, Inc. All rights reserved.
Feedback