Release Note for Catalyst 4900M Series Switch, Cisco IOS, 12.2(53)SG3
Available Languages
Table Of Contents
Release Notes for the Catalyst 4900M Series Switch, Cisco IOS Release 12.2(53)SG
Cisco IOS Software Packaging for the
Cisco Catalyst 4900M SwitchCisco 4900M Series Ethernet Switch
Cisco IOS Release StrategyFollowing Features are Supported only on the Catalyst 4900M
New Hardware Features in Release 12.2(53)SG
New Software Features in Release 12.2(53)SG
New Hardware Features in Release 12.2(52)SG
New Software Features in Release 12.2(52)SG
New Hardware Features in Release 12.2(50)SG5
New Software Features in Release 12.2(50)SG5
New Hardware Features in Release 12.2(50)SG4
New Software Features in Release 12.2(50)SG4
New Hardware Features in Release 12.2(50)SG3
New Software Features in Release 12.2(50)SG3
New Hardware Features in Release 12.2(50)SG2
New Software Features in Release 12.2(50)SG2
New Hardware Features in Release 12.2(50)SG1
New Software Features in Release 12.2(50)SG1
New Hardware Features in Release 12.2(50)SG
New Software Features in Release 12.2(50)SG
New Hardware Features in Release 12.2(46)SG
New Software Features in Release 12.2(46)SG
Minimum and Recommended ROMMON Release
Open Caveats in Cisco IOS Release 12.2(53)SG3
Resolved Caveats in Cisco IOS Release 12.2(53)SG3
Open Caveats in Cisco IOS Release 12.2(53)SG2
Resolved Caveats in Cisco IOS Release 12.2(53)SG2
Open Caveats in Cisco IOS Release 12.2(53)SG1
Resolved Caveats in Cisco IOS Release 12.2(53)SG1
Open Caveats in Cisco IOS Release 12.2(53)SG
Resolved Caveats in Cisco IOS Release 12.2(53)SG
Open Caveats in Cisco IOS Release 12.2(52)SG
Resolved Caveats in Cisco IOS Release 12.2(52)SG
Open Caveats in Cisco IOS Release 12.2(50)SG6
Resolved Caveats in Cisco IOS Release 12.2(50)SG6
Open Caveats in Cisco IOS Release 12.2(50)SG5
Resolved Caveats in Cisco IOS Release 12.2(50)SG5
Open Caveats in Cisco IOS Release 12.2(50)SG4
Resolved Caveats in Cisco IOS Release 12.2(50)SG4
Open Caveats in Cisco IOS Release 12.2(50)SG3
Resolved Caveats in Cisco IOS Release 12.2(50)SG3
Open Caveats in Cisco IOS Release 12.2(50)SG2
Resolved Caveats in Cisco IOS Release 12.2(50)SG2
Open Caveats in Cisco IOS Release 12.2(50)SG1
Resolved Caveats in Cisco IOS Release 12.2(50)SG1
Open Caveats in Cisco IOS Release 12.2(50)SG
Resolved Caveats in Cisco IOS Release 12.2(50)SG
Open Caveats in Cisco IOS Release 12.2(46)SG
Resolved Caveats in Cisco IOS Release 12.2(46)SG
Open Caveats in Cisco IOS Release 12.2(40)XO
Resolved Caveats in Cisco IOS Release 12.2(40)XO
Troubleshooting at the System Level
Obtaining Documentation and Submitting a Service Request
Release Notes for the Catalyst 4900M Series Switch, Cisco IOS Release 12.2(53)SG
Current Release
12.2(53)SG3—August 30, 2010Previous Release
12.2(53)SG2, 12.2(53)SG, 12.2(52)SG, 12.2(50)SG6, 12.2(50)SG5, 12.2(50)SG4, 12.2(50)SG3, 12.2(50)SG2, 12.2(50)SG1, 12.2(50)SG, 12.2(46)SG, 12.2(40)XOThese release notes describe the features, modifications, and caveats for Cisco IOS software on the Catalyst 4900M switch.
Cisco Systems announces the Cisco Catalyst 4900M Series, a premium extension to the widely deployed Catalyst 4948 Series top of rack Ethernet switches for data center server racks. Optimized for ultimate deployment flexibility, the Catalyst 4900M Series can be deployed for 10/100/1000 server access with 1:1 uplink to downlink oversubscription, mix of 10/100/1000 and 10 GbE servers or all 10GbE servers in the same rack. The Catalyst 4900M is a 320Gbps, 250Mpps, 2RU fixed configuration switch with
8 fixed wire speed X2 ports on the base unit and 2 optional half card slots for deployment flexibility and investment protection. Low latency, scalable buffer memory and high availability with 1+1 hot swappable AC or DC power supplies and field replaceable fans optimize the Catalyst 4900M for any size of data center.Support for Cisco IOS Software Release 12.2(53)SG, the default image, follows the standard Cisco Systems® support policy, available at
http://www.cisco.com/en/US/products/products_end-of-life_policy.htmlFor more information about the Cisco Catalyst 4900M Series, visit:
http://www.cisco.com/go/cat4900/docs.
Note
Although their Release Notes are unique, the 4 platforms (Catalyst 4500, Catalyst 4900,
Catalyst ME 4900, and Catalyst 4900M) use the same Software Configuration Guide, Command Reference Guide, and System Message Guide. Refer to this location:
http://www.cisco.com/go/cat4500/docs
Contents
This publication consists of these sections:
•
•
•
Cisco IOS Software Packaging for the
Cisco Catalyst 4900M SwitchCatalyst 4900M software features based on Cisco IOS Software 12.2(53)SG will support the IP Base image and the entservices image.
The IP Base image does not support enhanced routing features such as Nonstop Forwarding/Stateful Switchover (NSF/SSO), BGP, Enhanced Interior Gateway Routing Protocol (EIGRP), Open Shortest Path First (OSPF), Intermediate System-to-Intermediate System (IS-IS), Internetwork Packet Exchange (IPX), AppleTalk, Virtual Routing Forwarding (VRF-lite), GLBP, and policy-based routing (PBR). The IP Base image supports Static routes, RIPv1/v2 for IP BASE, and EIGRP-Stub for limited routing on Cisco Catalyst 4900 Series Switches.
The Enterprise Services image supports Cisco Catalyst 4900M Series software features based on Cisco IOS Software 12.2(53)SG, including enhanced routing. BGP capability is included in the Enterprises Services package.
Note
Orderable Product Numbers:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco 4900M Series Ethernet Switch
Cisco IOS Release StrategyCustomers with Catalyst 4900M switches who need the latest hardware support and software features should migrate to Cisco IOS Release 12.2(53)SG.
For more information on the Cisco 4900M Switch, visit the following URL: www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/index.htm
Cisco IOS Software Migration
Figure 1 displays the two active, 12.2(31)SGA and 12.2(50)SG, and newly introduced 12.2(53)SG extended maintenance trains.
Support for the Catalyst 4900M platform was introduced in 12.2(40)XO. Moving forward, the Cisco Catalyst 4900M platform has two maintenance trains. The Cisco IOS Release 12.2(53)SG is the latest maintenance train and includes the most recent features including support for OSPF for routed Access
Figure 1 Software Release Strategy for the Catalyst 4900M Series Switch
Summary of Migration Plan
•
Support
Support for Cisco IOS Software Release 12.2(53)SG follows the standard Cisco Systems® support policy, available at
http://www.cisco.com/en/US/products/products_end-of-life_policy.htmlSystem Requirements
Note
This section describes the system requirements:
Supported Hardware
The following tables lists the hardware supported on the Catalyst 4900M series switch.
Table 1 Supported Hardware
GLC-SC-MM
Gigabit Ethernet SFP, LC connector, and SX transceiver small form-factor pluggable module
GLC-LH-SM
Gigabit Ethernet SFP, LC connector, and LX/LH transceiver small form-factor pluggable module
GLC-ZX-SM
1000BASE-ZX small form-factor pluggable module
GLC-T
1000BASE-T small form-factor pluggable module
CWDM-SFP-xxxx
CWDM small form-factor pluggable module (See Table 2 for a list of supported wavelengths.)
X2-10GB-LR
10GBASE-LR X2 transceiver module for SMF, 1310-nm wavelength, SC duplex connector
X2-10GB-ER
10GBASE-ER X2 transceiver module for SMF, 1550-nm wavelength, SC duplex connector
X2-10GB-CX4
10GBASE-CX4 X2 transceiver module for CX4 cable, copper, Infiniband 4X connector
X2-10GB-LX4
10GBASE-LX4 X2 transceiver module for MMF, 1310-nm wavelength, SC duplex connector
X2-10GB-LRM
10GBASE-LRM X2 transceiver module for MMF, 1310-nm wavelength, SC duplex connector
X2-10GB-SR
10GBASE-SR X2 transceiver module for MMF, 850-nm wavelength, SC duplex connector
X2-10GB-ZR
10GBASE-ZR X2 transceiver module for SMF, 1550 nm wavelength up to 80 km. DOM is not supported.
X2-10GB-DWDM
10GBASE-ZR X2 transceiver module for SMF, 32 nontunable ITU 100-GHz wavelengths up to 80 km are supported. DOM is supported. Dual SC/PC connectors are supported.
CVR-X2-SFP10G
Hot-swappable input/output (I/O) converter module that fits into a 10-Gigabit Ethernet X2 slot on a switch or line card module. Hosts one 10-Gigabit Ethernet SFP+ transceiver module.
SFP-10G-SR
Cisco 10GBASE-SR SFP+ Module for MMF
Table 2 briefly describes the supported wavelengths in the Catalyst 4900M series switches.
The following tables lists the hardware supported on the Catalyst 4900M series switch.
Supported Features
Note
Table 4 lists the Cisco IOS software features for the Catalyst 4900M series switch.
Table 4 Cisco IOS Software Feature Set for the Catalyst 4900M series Switch
Storm control
Storm Control: Per-Port Multicast Suppression
Multicast storm control
IP Source Guard
IP Source Guard for Static Hosts
PVRST+
Layer 2 transparent bridging1
Layer 2 MAC2 learning, aging, and switching by software
Unicast MAC address filtering
VMPS3 Client
Layer 2 hardware forwarding up to 102 Mpps
Layer 2 Control Policing (Not supported on Supervisor Engine 6-E)
Layer 2 switch ports and VLAN trunks
Spanning-Tree Protocol (IEEE 802.1D) per VLAN
802.1s and 802.1w
Layer 2 traceroute
Unidirectional Ethernet port
Per-VLAN spanning tree (PVST) and PVST+
Spanning-tree root guard
Spanning-tree Loop guard and PortFast BPDU Filtering
Support for 9216 byte frames
Port security
Port security on Voice VLAN
Port security MAC Aging
Trunk Port Security
Unicast MAC Filtering
802.1X with Port Security
Private VLANs
Private VLAN DHCP snooping
Private VLAN trunks
IEEE 802.1Q-based VLAN encapsulation
Multiple VLAN access port
VLAN Trunking Protocol (VTP) and VTP domains
VTP v3
Support for 4096 VLANs per switch
Unidirectional link detection (UDLD) and aggressive UDLD
SNMP V3 support for Bridge-MIB with VLAN indexing
Ethernet CFM
Ethernet OAM Protocol
DTP4
RIPv15 and RIPv2, Static Routing
EIGRP6
EIGRP Stub Routing
OSPF7
BGP48
BGP route-map Continue
BGP Neighbor Policy
MBGP9
MSDP10
ICMP11 Router Discovery Protocol
Static routes
Classless interdomain routing (CIDR)
DVMRP12
NTP13
STP - Portfast BPDU Guard
STP- BPDU Filtering
STP - Root Guard
SCP14
Cisco EtherChannel technology - 10/100/1000 Mbps, 10 Gbps
Load balancing for routed traffic, based on source and destination IP addresses
Load sharing for bridged traffic based on MAC addresses
IEEE 802.1Q on all EtherChannels
Bundling of up to eight Ethernet ports
Trunk Port Security over EtherChannel
Secure Copy Protocol (SCP)
Routed Jumbo Frame support
SPAN CPU port mirroring
SPAN packet-type filtering
SPAN destination in-packets option
SPAN ACL filtering
Enhanced VLAN statistics
Secondary addressing
Bootstrap protocol (BOOTP)
Authentication, authorization, and accounting using TACACS+ and RADIUS protocol
Cisco Discovery Protocol (CDP)
CDP 2nd Port Status TLV
FlexLink and MAC Address-Table Move Update
Network Mobility Services Protocol
Sticky port security
Voice VLAN Sticky Port Security
Cisco Group Management Protocol (CGMP) server support
HSRP15 over Ethernet, EtherChannels - 10/100/1000Mbps, 10 Gbps
GLBP
VRRP
IGMP16 snooping version1, version 2, and version 3 (Full Support)
IGMP filtering
IGMP Querier
Multicast VRF-lite
VRF-aware IP services
Configurable IGMP Leave Timer
Multicast Source Discovery Protocol (MSDP)
Smartports I custom macros
Smartports II default macros
Smartports III global macros
Port Aggregation Protocol (PagP)
802.3ad LACP
SSH version 1 and version 217
show interface capabilities command
IfIndex persistence
Enhanced SNMP MIB support
SNMP18 version 1, version 2, and version 3
SNMP version 3 (with encryption)
DHCP server and relay-agent
DHCP Snooping Statistics and SYSLOG
DHCP client autoconfiguration
DHCP Option 82 data Insertion
DHCP Option 82 Pass Through
DHCP Relay Agent for IPv6
DHCP Option 82 - Configurable Remote ID and Circuit ID
Port flood blocking
Router standard and extended ACLs 19 on all ports with no performance penalty
Downloadable ACL
VLAN ACL
PACL20
VACL
RACL
Unicast RPF
Local Proxy ARP
Dynamic ARP Inspection on PVLANs
Dynamic ARP Inspection
Per-VLAN CTI
ARP QoS
MQC
Ingress/Egress Policing
Ingress Rate Limiting
Egress Bandwidth Limiting/port shaping
Per VLAN Policy & Per Port Policer
802.1p Priority
Strict Priority Scheduling
Ingress/Egress Strict Priority Queuing (Expedite)
Shaped Round Robin (SRR)
Egress Shaped Queues
Ingress/egress Shared Queues
DSCP Mapping
DSCP Filtering
AutoQoS - VoIP
PBR21
Auto QoS 1.5
Trust Boundary Configuration
Dynamic Buffer Limiting (DBL)
Per-VLAN Control Traffic Intercept
Table Map Based Classification
Interface Index Persistence
UDI - Unique Device Identifier
Per-port QoS22 rate-limiting and shaping
Per-port Per-VLAN QoS
Energy Wise
Two-Rate Three-Color Policing
Dynamic Multi-Protocol Ternary Content Addressable Memory
SmartPort macros
802.1s standards compliance
Flexible Authentication Sequencing
Multi-Authentication
Open Authentication
Web Authentication
Local Web Authentication (EPM syslog and Common session ID)
PPPoE Intermediate Agent
Identity ACL Policy Enforcement23
IPv6 routing - unicast routing "RIPng"
IPv6 Neighbor Discovery Throttingly
IPv6 MLDv1 & v2 SNooping
IPv6 Host support (- IPv6 support: Addressing; IPv6: Option processing, Fragmentation, ICMPv6,
TCP/UDP over IPv6; Applications: Ping/Traceroute/VTY/SSH/TFTP, SNMP for IPv6 objects)
IPv6 ACLs
IPv6 Management Services (CDP over IPv6, SSHv2 over IPv6)
IPv6: MLDv1/v2
IPv6:CEFv6
IPv6:MLD Snooping
Non-stop Forwarding Awareness
Non-stop Forwarding Awareness for EIGRP-stub in IP base for all supervisor engines
BGP MIB
OSPF Fast Convergence24
AutoRP
Service-Aware Resource Allocation
TwinGig Converter Module
FAT File System
EEM25
VSS client with PagP+
Ethernet Management Port
Enhanced Object Tracking subfeatures:
•
•
•
•
•
ANCP Client
Bidiectional PIM
OSPF and EIGRP Fast Convergence
Inactivity Timer
boot config command
Crashdump enhancement
Unicast MAC filtering
Energy Wise
DHCPv6 Ethernet Remote ID option
DHCPv6 Relay - Persistent Interface ID option DHCPv6 Relay Agent notification for Prefix Delegation
PIM SSM Mapping
VRF lite NSF support with routing protocols OSPF/EIGRP/BG
Layer 2 Tunneling Protocol
Online Diagnostics
PIM Accept Register - Rogue Multicast Server Protection26
Configuration Rollback
IP Multicast Load Splitting (Equal Cost Multipath (ECMP) using S, G and Next-hop)
OSPF for Routed Access
Archiving crashfiles
Cisco Network Assistant (CNA)
1 Hardware-based transparent bridging within a VLAN
2 MAC = Media Access Control
3 VMPS = VLAN Management Policy Server
4 DTP = Dynamic Trunking Protocol
5 RIP = Routing Information Protocol
6 EIGRP = Enhanced Interior Gateway Routing Protocol
7 OSPF = Open Shortest Path First
8 BGP4 = Border Gateway Protocol 4
9 MBGP = Multicast Border Gateway Protocol
10 MSDP = Multicast Source Discovery Protocol
11 ICMP = Internet Control Message Protocol
12 DVMRP = Distance Vector Multicast Routing Protocol
13 NTP = Network Time Protocol
14 SCP = Secure Copy Protocol
15 HSRP = Hot Standby Router Protocol
16 IGMP = Internet Group Management Protocol
17 SSH = Secure Shell Protocol
18 SNMP = Simple Network Management Protocol
19 ACLs = Access Control Lists
20 PACL = Port Access Control List
21 Policy-based Routing
22 QoS = Quality of Service
23 filter-ID and per-user ACL
24 The Catalyst 4500 series switch supports Fast Hellos, ISPF, and LSA Throttling.
25 EEM = Embedded Event Manager
26 The route-map keyword is not supported.
Following Features are Supported only on the Catalyst 4900M
With Cisco IOS Release 12.2(52)SG, the following features are available only with
Supervisor Engine 6-E:•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
•
–
–
–
•
•
•
Unsupported Features
These features are not supported in Cisco IOS Release 12.2(53)SG for the Catalyst 4900M switch:
•
–
–
–
–
•
•
•
•
•
•
•
•
•
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
New and Changed Information
These sections describe the new and changed information for the Catalyst 4900M series switch running Cisco IOS software:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
New Hardware Features in Release 12.2(53)SG
Release 12.2(53)SG provides no new hardware for the Catalyst 4900M switch.
New Software Features in Release 12.2(53)SG
Release 12.2(53)SG provides the following Cisco IOS software features for the Catalyst 4900M switch:
•
•
•
OSPF for Routed Access is designed specifically to enable customers to extend Layer 3 routing capabilities to the access or Wiring Closet.
Note
With the typical topology (hub and spoke) in a campus environment, where the wiring closets (spokes) are connected to the distribution switch (hub) forwarding all nonlocal traffic to the distribution layer, the wiring closet switch need not hold a complete routing table. A best practice design, where the distribution switch sends a default route to the wiring closet switch to reach inter-area and external routes (OSPF stub or totally stub area configuration) should be used when OSPF for Routed Access is used in the wiring closet.
Refer to the following link for more details:
http://www.cisco.com/en/US/docs/solutions/Enterprise/Campus/routed-ex.html
With Cisco IOS Release 12.2(53)SG, the IP Base image supports OSPF for routed access. The Enterprise Services image is required if you need multiple OSPFv2 and OSPFv3 instances without route restrictions. Additionally, Enterprise Services is required to enable the VRF-lite feature.
New Hardware Features in Release 12.2(52)SG
Release 12.2(52)SG provides no new hardware for the Catalyst 4900M series switch.
New Software Features in Release 12.2(52)SG
Release 12.2(52)SG provides the following new Cisco IOS software features for the Catalyst 4900M series switch:
•
–
–
•
•
•
–
–
•
•
•
•
•
•
•
•
–
–
–
–
–
–
–
–
•
New Hardware Features in Release 12.2(50)SG5
Release 12.2(50)SG5 provides no new hardware for the Catalyst 4900M series switch.
New Software Features in Release 12.2(50)SG5
Release 12.2(50)SG5 provides no new software for the Catalyst 4900M series switch.
New Hardware Features in Release 12.2(50)SG4
Release 12.2(50)SG4 provides no new hardware for the Catalyst 4900M series switch.
New Software Features in Release 12.2(50)SG4
Release 12.2(50)SG4 provides no new software for the Catalyst 4900M series switch.
New Hardware Features in Release 12.2(50)SG3
Release 12.2(50)SG3 provides the following hardware for the Catalyst 4500 series switch:
•
Hot-swappable input/output (I/O) converter module that fits into a 10-Gigabit Ethernet X2 slot on a switch or line card module. Hosts one 10-Gigabit Ethernet SFP+ transceiver module.
•
Cisco 10GBASE-SR SFP+ Module for MMF
New Software Features in Release 12.2(50)SG3
Release 12.2(50)SG3 provides no new features for the Catalyst 4500 series switch.
New Hardware Features in Release 12.2(50)SG2
Release 12.2(50)SG2 provides no new hardware for the Catalyst 4900M series switch.
New Software Features in Release 12.2(50)SG2
Release 12.2(50)SG2 provides no new software for the Catalyst 4900M series switch.
New Hardware Features in Release 12.2(50)SG1
Release 12.2(50)SG1 provides no new hardware for the Catalyst 4900M series switch.
New Software Features in Release 12.2(50)SG1
Release 12.2(50)SG1 provides the following new Cisco IOS software features for the Catalyst 4900M series switch:
•
New Hardware Features in Release 12.2(50)SG
Release 12.2(50)SG provides the following new hardware for the Catalyst 4900M series switch:
•
•
New Software Features in Release 12.2(50)SG
Release 12.2(50)SG provides the following Cisco IOS software features for the Catalyst 4900M series switch:
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
New Hardware Features in Release 12.2(46)SG
Release 12.2(46)SG provides no new hardware for the Catalyst 4900M series switch.
New Software Features in Release 12.2(46)SG
Note
Release 12.2(46)SG provides the following Cisco IOS software features for the Catalyst 4500 series switch:
Note
•
–
–
–
–
–
•
•
•
•
•
•
•
–
–
–
–
–
•
•
•
•
•
•
•
•
•
•
•
•
After configuring VSS dual-active on a Catalyst 6500 switches, the Catalyst 4500 series switch can detect VSS dual-active with PagP+ support.
•
•
•
•
Minimum and Recommended ROMMON Release
Table 5 Minimum and Recommended ROMMON Release for Catalyst 4900M
12.2(40r)XO
12.2(44r)SG5
Limitations and Restrictions
•
•
•
•
•
•
Workaround: Display the configuration with the show standby command, then remove the CLI. Here is sample output of the show standby GigabitEthernet1/1 command:
switch(config)# interface g1/1switch(config)# no standby 0 name (0 is hsrp group number)•
Use the standby delay reload option if the router is rebooting after reloading the image.
•
•
•
–
–
For the Catalyst 4900M switch, the rename command has been added for bootflash and slot0. For all other supervisor engines, the rename command is supported for nvram devices only.
–
–
–
–
–
–
•
•
•
•
•
•
•
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.If this message appears, check that there is network connectivity between the switch and the ACS. You should also check that the switch has been properly configured as an AAA client on the ACS.
•
–
–
–
–
•
% Hardware MTU table exhaustedIn such a scenario, the ipv6 MTU value programmed in hardware will be different from the ipv6 interface MTU value. This will happen if there is no room in the hw MTU table to store additional values.
You must free up some space in the table by unconfiguring some unused MTU values and subsequently disable/re-enable ipv6 on the interface or reapply the MTU configuration.
•
Switch(config-if)# no ip verify sourceSwitch(config-if)# no ip device tracking max"To enable IPSG with Static Hosts on a port, issue the following commands:
Switch(config)# ip device tracking ****enable IP device tracking globallySwitch(config)# ip device tracking max <n> ***set an IP device tracking maximum on intSwitch(config-if)# ip verify source tracking [port-security] ****activate IPSG on port
Caution
Note
•
•
•
•
•
CSCsy31324
•
•
Caveats
Caveats describe unexpected behavior in Cisco IOS releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.
Note
http://tools.cisco.com/security/center/publicationListing.x
Open Caveats in Cisco IOS Release 12.2(53)SG3
This section lists the open caveats in Cisco IOS Release 12.2(53)SG3:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsv42869)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy72343
•
The errors can also occur with data traffic.
This issue is seen with the TenGigabit ports of the Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
The issue is seen with release 12.2(44)XO and later releases.
Workaround: Enter shut, then no shut.
You may need to do this multiple times until the issue is resolved.
CSCsx80612
•
To observe this issue, the following CLIs are configured with window size as the period for monitoring the errors and a low threshold equal to the number of CRC errored seconds seen/expected.
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value of low threshold such that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Disable RSPAN.
CSCsu81046
•
This issue is seen with the TenGigabit ports of a Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
Workaround: Enter the commands shut then no shut.
Occasionally, you need to re-enter the commands.
CSCsx80612
•
Workaround: None.
CSCsy38640
•
Workaround: None.
CSCsu35604
•
The statistics are displayed properly on the active supervisor.
Workaround: None.
CSCsx64308
•
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value for the low threshold so that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Switch# call-home send alert-group diagnostic module 2Sending diagnostic info call-home message ...Please wait. This may take some time ...Switch#*Jan 3 01:54:24.471: %CALL_HOME-3-ONDEMAND_MESSAGE_FAILED: call-home on-demand message failed to send (ERR 18, The alert group is not subscribed)Workaround: Specify a profile name when you enter the diagnostic command.
You might want to avoid requesting on demand send for invalid modules. First, enter the
show module command to check for valid or present modules.CSCsz05888
•
show policy-map interface command are wrong.Workaround: None.
The queue transmit counters as well as the policing statistics (if any) are correct.
CSCsz20149
•
Workaround: Manually re-enter all entries with new time settings.
CSCsy27389
•
This only happens when the switch is running network mobility service protocol (nmsp). It does not happen if the phone is CDP enabled.
Workaround: Use VLAN ID or name to differentiate the IP phone and the PC sitting behind the phone on the WCS. Specifically, the IP phone is detected on the voice VLAN, and the displayed information of serial number, model number, and software version is correct. However, a PC sitting behind the phone is detected on a data VLAN, and the displayed device information is wrong and should be ignored.
CSCsz34522
•
Entering shut/no shut on the port after deleting a secondary VLAN. (CSCsz73895)
Workarounds:
–
–
CSCsz73895
•
Assuming that you configured authentication open on the port and a host is authenticated on that port, if you unconfigure open auth (no authentication open), the STP state becomes blocked on an authenticated port.
The connected host is authenticated so it should be able to send traffic and the STP state should be Forwarding.
Workaround: Enter shut, then no shut on the port.
CSCta04665
•
Workaround: None.
CSCtc46340
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
•
Workaround: None.
Despite the different default value, you can configure any value in the time range.
CSCte51948
•
The show memory debug leak lowmem command can work in extremely low memory conditions but might crash the switch due to its very high CPU intensity. It also takes between 20 and 90 minutes to complete.
Workaround: If call or packet drops persist, contact TAC rather than entering these commands on your own. CSCsi48986
•
Workaround: Disable the ip cef accounting non-recursive command.
(CSCtn68186)
Resolved Caveats in Cisco IOS Release 12.2(53)SG3
This section lists the resolved caveats in Release 12.2(53)SG3:
•
Workaround: Reload the active and standby supervisor engine.
While performing OIR of the supervisor engines, the engines must be removed completely before re-insertion. CSCsy70428
•
Cisco IOS Release 12.2(53)SG1 or 12.2(50)SG6, Layer 2 multicast is not blocked.Prior to Cisco IOS Release 12.2(53)SG1, 12.2(50)SG6, the switchport block multicast command would block IP Multicast, Layer 2 multicast, and broadcast traffic (CSCta61825).
Workaround: None CSCtb30327
Open Caveats in Cisco IOS Release 12.2(53)SG2
This section lists the open caveats in Cisco IOS Release 12.2(53)SG2:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsv42869)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy72343
•
The errors can also occur with data traffic.
This issue is seen with the TenGigabit ports of the Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
The issue is seen with release 12.2(44)XO and later releases.
Workaround: Enter shut, then no shut.
You may need to do this multiple times until the issue is resolved.
CSCsx80612
•
To observe this issue, the following CLIs are configured with window size as the period for monitoring the errors and a low threshold equal to the number of CRC errored seconds seen/expected.
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value of low threshold such that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Disable RSPAN.
CSCsu81046
•
This issue is seen with the TenGigabit ports of a Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
Workaround: Enter the commands shut then no shut.
Occasionally, you need to re-enter the commands.
CSCsx80612
•
Workaround: None.
CSCsy38640
•
Workaround: None.
CSCsu35604
•
The statistics are displayed properly on the active supervisor.
Workaround: None.
CSCsx64308
•
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value for the low threshold so that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Reload the active and standby supervisor engine.
While performing OIR of the supervisor engines, the engines must be removed completely before re-insertion.
CSCsy70428
•
Switch# call-home send alert-group diagnostic module 2Sending diagnostic info call-home message ...Please wait. This may take some time ...Switch#*Jan 3 01:54:24.471: %CALL_HOME-3-ONDEMAND_MESSAGE_FAILED: call-home on-demand message failed to send (ERR 18, The alert group is not subscribed)Workaround: Specify a profile name when you enter the diagnostic command.
You might want to avoid requesting on demand send for invalid modules. First, enter the
show module command to check for valid or present modules.CSCsz05888
•
show policy-map interface command are wrong.Workaround: None.
The queue transmit counters as well as the policing statistics (if any) are correct.
CSCsz20149
•
Workaround: Manually re-enter all entries with new time settings.
CSCsy27389
•
This only happens when the switch is running network mobility service protocol (nmsp). It does not happen if the phone is CDP enabled.
Workaround: Use VLAN ID or name to differentiate the IP phone and the PC sitting behind the phone on the WCS. Specifically, the IP phone is detected on the voice VLAN, and the displayed information of serial number, model number, and software version is correct. However, a PC sitting behind the phone is detected on a data VLAN, and the displayed device information is wrong and should be ignored.
CSCsz34522
•
Entering shut/no shut on the port after deleting a secondary VLAN. (CSCsz73895)
Workarounds:
–
–
CSCsz73895
•
Assuming that you configured authentication open on the port and a host is authenticated on that port, if you unconfigure open auth (no authentication open), the STP state becomes blocked on an authenticated port.
The connected host is authenticated so it should be able to send traffic and the STP state should be Forwarding.
Workaround: Enter shut, then no shut on the port.
CSCta04665
•
Cisco IOS Release 12.2(53)SG1 or 12.2(50)SG6, Layer 2 multicast is not blocked.Prior to Cisco IOS Release 12.2(53)SG1, 12.2(50)SG6, the switchport block multicast command would block IP Multicast, Layer 2 multicast, and broadcast traffic (CSCta61825).
Workaround: None
CSCtb30327
•
Workaround: None.
CSCtc46340
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
•
Workaround: None.
Despite the different default value, you can configure any value in the time range.
CSCte51948
•
Workaround: Disable the ip cef accounting non-recursive command.
(CSCtn68186)
Resolved Caveats in Cisco IOS Release 12.2(53)SG2
This section lists the resolved caveats in Release 12.2(53)SG2:
•
Workaround: Configure the port in multi-domain mode (rather than multi-auth mode) with the authentication host-mode multi-domain command
CSCtb28114
•
Workaround: Avoid lengthy bootflash operations, like copying large files in IOS.
CSCsw84727
•
The problem occurs when the following three conditions are met:
–
–
–
Workaround:
–
–
The port level policy-map should appear as follows.
policy-map p1class class-defaultbandwidth percent 100CSCte12571
•
This is a side effect of a heavily shared path.
Workaround: None.
CSCtc90702
•
%Error copying flash:/eem_pnt_2 (Invalid path)Workaround: Rename the flash device to the default name flash:.
CSCte05909
•
Workaround: None.
You will need to disableWake-on-LAN on the interface.
CSCtc58982
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: Enter shut, then no shut on the port.
CSCsz63355
•
Workaround: Disable explicit host tracking in the affected VLANs.
CSCsz28612
•
All software releases up to and including Cisco IOS Releases 12.2(31)SGA9, 12.2(50)SG6 and 12,2(53)SG1 are affected.
Workaround: After rebooting the switch, adjust the system clock with the clock set command.
CSCtc65375
•
%C4K_EBM-4-HOSTFLAPPING: happening between master loopback port and the source port during layer3 (IPv4 and IPv6) packets loop using ethernet oam (EOAM)This message is does not impact performance.
Workaround: None.
CSCtc26043
•
–
–
–
This occurs when the time change for the next year occurs after the time change for the current year.
Before the time change occurs, use one of these workarounds:
–
–
–
CSCtc91312
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: Create an ACL to block non-RPF packets from entering non-RPF ports.
CSCta93522
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
Open Caveats in Cisco IOS Release 12.2(53)SG1
This section lists the open caveats in Cisco IOS Release 12.2(53)SG1:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876IP Router Option may not work with IGMP version 2.
Workaround: None. (CSCsv42869)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy72343
•
The errors can also occur with data traffic.
This issue is seen with the TenGigabit ports of the Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
The issue is seen with release 12.2(44)XO and later releases.
Workaround: Enter shut, then no shut.
You may need to do this multiple times until the issue is resolved.
CSCsx80612
•
To observe this issue, the following CLIs are configured with window size as the period for monitoring the errors and a low threshold equal to the number of CRC errored seconds seen/expected.
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value of low threshold such that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Disable RSPAN.
CSCsu81046
•
This issue is seen with the TenGigabit ports of a Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
Workaround: Enter the commands shut then no shut.
Occasionally, you need to re-enter the commands.
CSCsx80612
•
Workaround: None.
CSCsy38640
•
Workaround: None.
CSCsu35604
•
The statistics are displayed properly on the active supervisor.
Workaround: None.
CSCsx64308
•
Workaround: Re-authenticate the client.
CSCsx94066
•
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value for the low threshold so that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Reload the active and standby supervisor engine.
While performing OIR of the supervisor engines, the engines must be removed completely before re-insertion.
CSCsy70428
•
Switch# call-home send alert-group diagnostic module 2Sending diagnostic info call-home message ...Please wait. This may take some time ...Switch#*Jan 3 01:54:24.471: %CALL_HOME-3-ONDEMAND_MESSAGE_FAILED: call-home on-demand message failed to send (ERR 18, The alert group is not subscribed)Workaround: Specify a profile name when you enter the diagnostic command.
You might want to avoid requesting on demand send for invalid modules. First, enter the
show module command to check for valid or present modules.CSCsz05888
•
No TCAM entries are available for the new access-list.
Workaround: Manually remove and reapply the ACL after freeing hardware TCAM resources by removing or shortening other classification policies on the switch.
CSCsy85006
•
show policy-map interface command are wrong.Workaround: None.
The queue transmit counters as well as the policing statistics (if any) are correct.
CSCsz20149
•
Workaround: Enter shut, then no shut on the port.
CSCsz63355
•
Workaround: Disable explicit host tracking in the affected VLANs.
CSCsz28612
•
Workaround: Manually re-enter all entries with new time settings.
CSCsy27389
•
This only happens when the switch is running network mobility service protocol (nmsp). It does not happen if the phone is CDP enabled.
Workaround: Use VLAN ID or name to differentiate the IP phone and the PC sitting behind the phone on the WCS. Specifically, the IP phone is detected on the voice VLAN, and the displayed information of serial number, model number, and software version is correct. However, a PC sitting behind the phone is detected on a data VLAN, and the displayed device information is wrong and should be ignored.
CSCsz34522
•
Entering shut/no shut on the port after deleting a secondary VLAN. (CSCsz73895)
Workarounds:
–
–
CSCsz73895
•
Assuming that you configured authentication open on the port and a host is authenticated on that port, if you unconfigure open auth (no authentication open), the STP state becomes blocked on an authenticated port.
The connected host is authenticated so it should be able to send traffic and the STP state should be Forwarding.
Workaround: Enter shut, then no shut on the port.
CSCta04665
•
Workaround: Create an ACL to block non-RPF packets from entering non-RPF ports.
CSCta93522
•
Workaround: Configure the port in multi-domain mode (rather than multi-auth mode) with the authentication host-mode multi-domain command
CSCtb28114
•
All software releases up to and including Cisco IOS Releases 12.2(31)SGA9, 12.2(50)SG6 and 12,2(53)SG1 are affected.
Workaround: After rebooting the switch, adjust the system clock with the clock set command.
CSCtc65375
•
Cisco IOS Release 12.2(53)SG1 or 12.2(50)SG6, Layer 2 multicast is not blocked.Prior to Cisco IOS Release 12.2(53)SG1, 12.2(50)SG6, the switchport block multicast command would block IP Multicast, Layer 2 multicast, and broadcast traffic (CSCta61825).
Workaround: None
CSCtb30327
•
Workaround: None.
CSCtc46340
•
%C4K_EBM-4-HOSTFLAPPING: happening between master loopback port and the source port during layer3 (IPv4 and IPv6) packets loop using ethernet oam (EOAM)This message is does not impact performance.
Workaround: None.
CSCtc26043
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
•
Workaround: Avoid lengthy bootflash operations, like copying large files in IOS.
CSCsw84727
•
–
–
–
This occurs when the time change for the next year occurs after the time change for the current year.
Before the time change occurs, use one of these workarounds:
–
–
–
CSCtc91312
•
%Error copying flash:/eem_pnt_2 (Invalid path)Workaround: Rename the flash device to the default name flash:.
CSCte05909
•
Workaround: None.
Despite the different default value, you can configure any value in the time range.
CSCte51948
•
Workaround: Disable the ip cef accounting non-recursive command.
(CSCtn68186)
Resolved Caveats in Cisco IOS Release 12.2(53)SG1
This section lists the resolved caveats in Release 12.2(53)SG1:
•
All broadcast traffic (such as ARP request and DHCP discovery) are not received by the port. So, protocols that use such broadcasts stop working.
Workaround:None
CSCta61825
•
–
–
Workaround: Use static neighbors.
CSCsz61756
•
Workaround: Configure an access-list to permit the CPU generated packets and apply the ACL to the class-map.
CSCsy43967
•
do show policy-map interface or do show policy-map control-plane command causes a system reload.Workaround: Enter either the show policy-map interface and show policy-map control-plane commands in Exec mode and not in policy-map config mode.
CSCsy43261
•
Workaround: Ensure that the port is active before apply the policy-map or entering the
show policy-map command.The command to activate a previously inactive interface is the following:
hw-module module [module number] port-group [group number] select [gigabitethernet]
CSCtb90328
•
Workaround: Manually re-enter all entries with new time settings.
CSCsy27389
•
ROM by abort at PC 0x0Workaround: None.
Downgrade to Cisco IOS Release 12.2(50)SG3 if needed.
CSCta49512
•
Workaround: Disable RSPAN.
CSCsu81046
•
Certain applications such as IP Source Guard and QoS enable ACL statistics by default. Configuring such features trigger the high CPU.
High CPU usage is observed through the show proc cpu command. The output of
the show platform health command reveals that the process using a high percentage of CPU is "K5AclCamStatsMan hw".This issue can occur in any release after Cisco IOS Release 12.2(40)SG.
This issue is resolved in Cisco IOS Release 12.2(53)SG1 and 12.2(50)SG6.
Workaround: Reduce the size of the ACL, IPSG, and QoS configurations. If statistics are enabled explicitly for ACLs, disable them with the CLI.
If the high CPU is due to ACLs and IPSG, upgrade to the new software.
If the high CPU is due to the QoS configuration, upgrade the IOS image and enter the
no qos statistics classification command.CSCta54369
•
Workaround: Change the VTP version from 3 to version 2 or 1 and then revert to version 3.
CSCsy66803
•
Workaround: None.
CSCsz38442
•
A syslog warning message "%SM-4-BADEVENT: Event 'forward' is invalid for the current state 'present': pm_vp .."A traceback error messageThis issue happens only on flexlink ports under the following two scenarios:
–
–
Workaround: None
The syslog and Traceback do not impact functionality. Flexlink states end up with correct states and there is no impact on traffic forwarding.
CSCta05317
•
The existing per-port error disable (that is, when a violation happens, the entire port will be error disabled) still works on flexlink.
Workaround: Use flexlink with VLAN load balancing.
If you do not want to use vlan load balancing, then enter the
switchport backup interface perfer vlan command on the Active interface, where vlan z is set to an unused vlan on the systemCSCta76320
•
Workaround: None. Functionality is unaffected.
CSCsy32312
Open Caveats in Cisco IOS Release 12.2(53)SG
This section lists the open caveats in Cisco IOS Release 12.2(53)SG:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876IP Router Option may not work with IGMP version 2.
Workaround: None. (CSCsv42869)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy72343
•
The errors can also occur with data traffic.
This issue is seen with the TenGigabit ports of the Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
The issue is seen with release 12.2(44)XO and later releases.
Workaround: Enter shut, then no shut.
You may need to do this multiple times until the issue is resolved.
CSCsx80612
•
To observe this issue, the following CLIs are configured with window size as the period for monitoring the errors and a low threshold equal to the number of CRC errored seconds seen/expected.
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value of low threshold such that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Disable RSPAN.
CSCsu81046
•
This issue is seen with the TenGigabit ports of a Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
Workaround: Enter the commands shut then no shut.
Occasionally, you need to re-enter the commands.
CSCsx80612
•
Workaround: None.
CSCsy38640
•
Workaround: None.
CSCsu35604
•
The statistics are displayed properly on the active supervisor.
Workaround: None.
CSCsx64308
•
Workaround: Re-authenticate the client.
CSCsx94066
•
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value for the low threshold so that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Change the VTP version from 3 to version 2 or 1 and then revert to version 3.
CSCsy66803
•
Workaround: Reload the active and standby supervisor engine.
While performing OIR of the supervisor engines, the engines must be removed completely before re-insertion.
CSCsy70428
•
Switch# call-home send alert-group diagnostic module 2Sending diagnostic info call-home message ...Please wait. This may take some time ...Switch#*Jan 3 01:54:24.471: %CALL_HOME-3-ONDEMAND_MESSAGE_FAILED: call-home on-demand message failed to send (ERR 18, The alert group is not subscribed)Workaround: Specify a profile name when you enter the diagnostic command.
You might want to avoid requesting on demand send for invalid modules. First, enter the
show module command to check for valid or present modules.CSCsz05888
•
No TCAM entries are available for the new access-list.
Workaround: Manually remove and reapply the ACL after freeing hardware TCAM resources by removing or shortening other classification policies on the switch.
CSCsy85006
•
show policy-map interface command are wrong.Workaround: None.
The queue transmit counters as well as the policing statistics (if any) are correct.
CSCsz20149
•
Workaround: None.
CSCsz38442
•
Workaround: Enter shut, then no shut on the port.
CSCsz63355
•
Workaround: Disable explicit host tracking in the affected VLANs.
CSCsz28612
•
Workaround: Manually re-enter all entries with new time settings.
CSCsy27389
•
This only happens when the switch is running network mobility service protocol (nmsp). It does not happen if the phone is CDP enabled.
Workaround: Use VLAN ID or name to differentiate the IP phone and the PC sitting behind the phone on the WCS. Specifically, the IP phone is detected on the voice VLAN, and the displayed information of serial number, model number, and software version is correct. However, a PC sitting behind the phone is detected on a data VLAN, and the displayed device information is wrong and should be ignored.
CSCsz34522
•
Entering shut/no shut on the port after deleting a secondary VLAN. (CSCsz73895)
Workarounds:
–
–
CSCsz73895
•
Workaround: None. Functionality is unaffected.
CSCsy32312
•
Assuming that you configured authentication open on the port and a host is authenticated on that port, if you unconfigure open auth (no authentication open), the STP state becomes blocked on an authenticated port.
The connected host is authenticated so it should be able to send traffic and the STP state should be Forwarding.
Workaround: Enter shut, then no shut on the port.
CSCta04665
•
A syslog warning message "%SM-4-BADEVENT: Event 'forward' is invalid for the current state 'present': pm_vp .."A traceback error messageThis issue happens only on flexlink ports under the following two scenarios:
–
–
Workaround: None
The syslog and Traceback do not impact functionality. Flexlink states end up with correct states and there is no impact on traffic forwarding.
CSCta05317
•
The existing per-port error disable (that is, when a violation happens, the entire port will be error disabled) still works on flexlink.
Workaround: Use flexlink with VLAN load balancing.
If you do not want to use vlan load balancing, then enter the
switchport backup interface perfer vlan command on the Active interface, where vlan z is set to an unused vlan on the systemCSCta76320
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
•
Workaround: Avoid lengthy bootflash operations, like copying large files in IOS.
CSCsw84727
•
–
–
–
This occurs when the time change for the next year occurs after the time change for the current year.
Before the time change occurs, use one of these workarounds:
–
–
–
CSCtc91312
•
%Error copying flash:/eem_pnt_2 (Invalid path)Workaround: Rename the flash device to the default name flash:.
CSCte05909
•
Workaround: None.
Despite the different default value, you can configure any value in the time range.
CSCte51948
•
Workaround: Disable the ip cef accounting non-recursive command.
(CSCtn68186)
Resolved Caveats in Cisco IOS Release 12.2(53)SG
This section lists the resolved caveats in Release 12.2(53)SG:
•
Workarounds: Disable RSPAN.
CSCsu81046
•
This issue is seen with the Ten-Gigabit ports of a Catalyst 4900M base board but not with the Ten-Gigabit ports of a WS-X4908-10GE line card.
Workaround: Enter shut, then no shut.
Sometimes you need to do this multiple times before the issue is resolved.
CSCsx80612
•
Workarounds:
–
–
–
(CSCsy80415)
•
Workaround: Reapply the identity policy on the interface with the permit icmp command. (CSCsu03507
Open Caveats in Cisco IOS Release 12.2(52)SG
This section lists the open caveats in Cisco IOS Release 12.2(52)SG:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876IP Router Option may not work with IGMP version 2.
Workaround: None. (CSCsv42869)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy72343
•
The errors can also occur with data traffic.
This issue is seen with the TenGigabit ports of the Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
The issue is seen with release 12.2(44)XO and later releases.
Workaround: Enter shut, then no shut.
You may need to do this multiple times until the issue is resolved.
CSCsx80612
•
To observe this issue, the following CLIs are configured with window size as the period for monitoring the errors and a low threshold equal to the number of CRC errored seconds seen/expected.
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value of low threshold such that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Disable RSPAN.
CSCsu81046
•
This issue is seen with the TenGigabit ports of a Catalyst 4900M base board. It is not seen with the TenGigabit ports of a WS-X4908-10GE line card.
Workaround: Enter the commands shut then no shut.
Occasionally, you need to re-enter the commands.
CSCsx80612
•
Workaround: None.
CSCsy38640
•
Workaround: None.
CSCsu35604
•
The statistics are displayed properly on the active supervisor.
Workaround: None.
CSCsx64308
•
Workaround: Re-authenticate the client.
CSCsx94066
•
ethernet oam link-monitor frame-seconds windowethernet oam link-monitor frame-seconds threshold lowWorkaround: Configure a lower value for the low threshold so that the frame errors are seen divided into the expected number of frame errored seconds.
CSCsy37181
•
Workaround: Change the VTP version from 3 to version 2 or 1 and then revert to version 3.
CSCsy66803
•
Workaround: Reload the active and standby supervisor engine.
While performing OIR of the supervisor engines, the engines must be removed completely before re-insertion.
CSCsy70428
•
Switch# call-home send alert-group diagnostic module 2Sending diagnostic info call-home message ...Please wait. This may take some time ...Switch#*Jan 3 01:54:24.471: %CALL_HOME-3-ONDEMAND_MESSAGE_FAILED: call-home on-demand message failed to send (ERR 18, The alert group is not subscribed)Workaround: Specify a profile name when you enter the diagnostic command.
You might want to avoid requesting on demand send for invalid modules. First, enter the
show module command to check for valid or present modules.CSCsz05888
•
No TCAM entries are available for the new access-list.
Workaround: Manually remove and reapply the ACL after freeing hardware TCAM resources by removing or shortening other classification policies on the switch.
CSCsy85006
•
show policy-map interface command are wrong.Workaround: None.
The queue transmit counters as well as the policing statistics (if any) are correct.
CSCsz20149
•
Workaround: None.
CSCsz38442
•
Workaround: Enter shut, then no shut on the port.
CSCsz63355
•
Workaround: Disable explicit host tracking in the affected VLANs.
CSCsz28612
•
Workaround: Manually re-enter all entries with new time settings.
CSCsy27389
•
This only happens when the switch is running network mobility service protocol (nmsp). It does not happen if the phone is CDP enabled.
Workaround: Use VLAN ID or name to differentiate the IP phone and the PC sitting behind the phone on the WCS. Specifically, the IP phone is detected on the voice VLAN, and the displayed information of serial number, model number, and software version is correct. However, a PC sitting behind the phone is detected on a data VLAN, and the displayed device information is wrong and should be ignored.
CSCsz34522
•
Entering shut/no shut on the port after deleting a secondary VLAN. (CSCsz73895)
Workarounds:
–
–
CSCsz73895
Entering shut/no shut on the port after configuring port-security vp err disable and a violation occurs. (CSCsz80415)
Workarounds:
–
–
–
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
•
Workaround: Avoid lengthy bootflash operations, like copying large files in IOS.
CSCsw84727
•
–
–
–
This occurs when the time change for the next year occurs after the time change for the current year.
Before the time change occurs, use one of these workarounds:
–
–
–
CSCtc91312
•
%Error copying flash:/eem_pnt_2 (Invalid path)Workaround: Rename the flash device to the default name flash:.
CSCte05909
•
Workaround: None.
Despite the different default value, you can configure any value in the time range.
CSCte51948
Resolved Caveats in Cisco IOS Release 12.2(52)SG
This section lists the resolved caveats in Release 12.2(52)SG:
•
001298: .Oct 8 01:38:50.968: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: flCam0aPErr interrupt. errAddr: 0x2947 dPErr: 1 mPErr: 0 valid: 1001299: .Oct 8 01:51:20.100: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: flCam0aPErr interrupt. errAddr: 0x2B59 dPErr: 1 mPErr: 0 valid: 1Workaround: None
CSCsv17545
•
macro global apply system-cpp command and use predefined ACLs to match traffic) increment both their packet and byte count. So, both counters are non-zero.In contrast, data plane classes (the classes that are configured manually by user written ACLs), the byte counter increments as expected, but the packet count remains 0.
Workaround: None.
CSCsw16557
•
This impacts Cisco IOS Releases 12.2(31)SGA08, 12.2(37)SG, 12.2(40)SG, 12.2(44)SG, 12.2(46)SG, 12.2(50)SG, and 12.2(50)SG1.
Workarounds:
For a Classic Series Supervisor Engine, disable and configure QoS on the port.
For example, to configure Gig 2/1 as an isolated private VLAN trunk port, do the following:
Switch# conf tEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# interface gigabitEthernet 2/1Switch(config-if)# no qosSwitch(config-if)# qosSwitch(config-if)# endSwitch#You can configure the following EEM script to automate this workaround. QoS will be disabled and re-enabled whenever a port flaps.
logging event link-status globalevent manager applet linkup-reqosevent syslog pattern "changed state to up"action 1 cli command "enable"action 2 cli command "conf t"action 3 cli command "interface gigabitEthernet 2/1"action 4 cli command "no qos"action 5 cli command "qos"CSCsw19087
•
Workaround: None, other than stopping the query.
CSCsw89720
•
Workaround: Disable the authentication control-direction in command.
If you require authentication control-direction in, configure the port for multi-authentication or Multi-Domain Authentication (MDA).
CSCsx98360
•
802.1X VVID and port security are configured on a port, CDP MAC from the non 802.1X capable Cisco IP phone might not be added to the port security table on the standby supervisor engine.Workaround: None.
This problem is fixed in Cisco IOS Releases 12.2(50)SG2 and 12.2(52)SG.
CSCsw29489
•
Workaround: Turn off LLDP (on the switch) and the phone (from Call Manager).
This problem is fixed in 12.2(50)SG2 and 12.2(52)SG.
CSCsy21167
•
Switch# show platform crashdumpVECTOR 0*** CRASH DUMP ***02/09/2009 10:10:30Last crash: 02/09/2009 10:10:30Build: 12.2(20090206:234053) IPBASEbuildversion addr: 13115584MCSR: 40000000 <--- non-zero value!.
The key pieces of data are "VECTOR 0" and a MCSR value of 40000000, 20000000, or 10000000.
Workaround: Enter the show platform cpu cache command to launch an IOS algorithm that detects and recovers from parity errors in the CPU's cache. You will obtain a running count of the number of CPU cache parity errors that have been successfully detected and corrected on a running system:
Switch# show platform cpu cacheL1 Instruction Cache: ENABLEDL1 Data Cache: ENABLEDL2 Cache: ENABLEDMachine Check Interrupts: 5L1 Instruction Cache Parity Errors: 3L1 Instruction Cache Parity Errors (CPU30): 1L1 Data Cache Parity Errors: 1CSCsx15372
•
Workaround: None. (CSCso50659)
•
Workaround: Upgrade to ROMMON version 1.2(31r)SGA4.
CSCsw91043
•
This problem occurs only when a port is configured with PVLAN and 802.1X multi-auth.
Workaround: Shut down then reopen the interface. (CSCsr58573)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsu42775)
•
Workaround: Remove the above debug command. (CSCsu67323)
•
'This problem is seen on all Catalyst 4500 or 4900 chassis running Cisco IOS Release 12.2.(50)SG. The problem occurs when the following conditions are present:
–
–
–
Workarounds: Do not configure the callback or callback-dialstring attribute for the user. If you use the callback-dialstring attribute in the TACACS+ profile, ensure that the NULL value is not configured. (CSCei62358)
•
Workaround: None. (CSCsw32519)
•
Port-channel functionality is not supported on the management interface.
This is a configuration error.
Workaround: None. (CSCsv91302)
•
Workaround: None. CSCsy29140
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Upgrade to ROMMON version 1.2(31r)SGA4.
CSCsw91043
•
Workaround: Reapply the identity policy on the interface with the permit icmp command. (CSCsu03507
This issue may occur on switches with Supervisor 6(L)-E and 4900M running Cisco IOS Releases 12.2(40)SG, 12.2(44)SG, 12.2(46)SG, 12.2(50)SG-SG5. This issue does not affect switches with Supervisor V-10GE.
Resolved in 12.2(52)SG and beyond and 12.2(50)SG6 and beyond.
•
This issue may occur on switches running Cisco IOS Releases 12.2(40)SG, 12.2(44)SG, 12.2(46)SG, 12.2(50)SG-SG5. This issue does not affect switches with Supervisor V-10GE.
This issue is resolved in 12.2(52)SG (and later) and12.2(50)SG6 (and later) releases.
Workaround: Do not use the nested policy-map feature in Cisco IOS Release 12.2(40)SG and 12.2(44)SG. (CSCsy80664)
•
Workaround: None.
Do not configure 802.1X with other per vp errdisable features.
CSCsx74871
Open Caveats in Cisco IOS Release 12.2(50)SG6
This section lists the open caveats in Cisco IOS Release 12.2(50)SG6:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
Workaround: None. (CSCsu42775)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876)
•
Workaround: Remove the above debug command. (CSCsu67323)
•
Workaround: None. (CSCsv42869)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy72343
•
Do not enter this command if port security is not configured on the interface.
Do not enter this command on fa1.
Workaround: None. CSCtb16586
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
Workaround: None. However, you cannot enter the switchport block unicast command on PVLAN trunk ports.
CSCtd49056
•
Workaround: None.
CSCtc79119
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
•
Workaround: None.
Despite the different default value, you can configure any value in the time range.
CSCte51948
Resolved Caveats in Cisco IOS Release 12.2(50)SG6
This section lists the resolved caveats in Release 12.2(50)SG6:
•
The show processes cpu command indicates that Cat4k Mgmt LoPri consumes a significant amount of CPU. The show platform health command indicates that K5L3FlcMan FwdEntry, K5L3Unciast IFE Review, and K5L3UnicastRpf IFE Review processes are running above their target utilization.
Note that large amounts of incomplete ARP entries may result from a scanning device or virus.
Workarounds:
–
–
CSCta77487
•
Certain applications such as IP Source Guard and QoS enable ACL statistics by default. Configuring such features trigger the high CPU.
High CPU usage is observed through the show proc cpu command. The output of
the show platform health command reveals that the process using a high percentage of CPU is "K5AclCamStatsMan hw".This issue can occur in any release after Cisco IOS Release 12.2(40)SG.
This issue is resolved in Cisco IOS Release 12.2(53)SG1 and 12.2(50)SG6.
Workaround: Reduce the size of the ACL, IPSG, and QoS configurations. If statistics are enabled explicitly for ACLs, disable them with the CLI.
If the high CPU is due to ACLs and IPSG, upgrade to the new software.
If the high CPU is due to the QoS configuration, upgrade the IOS image and enter the
no qos statistics classification command.CSCta54369
•
ROM by abort at PC 0x0Workaround: None.
Downgrade to Cisco IOS Release 12.2(50)SG3 if needed.
CSCta49512
•
Workaround: Avoid lengthy bootflash operations, like copying large files in IOS.
CSCsw84727
•
ARP entries learned on normal SVIs are unaffected.
Workaround: Clear these ARP entries with the clear ip arp command.
CSCtb37718
•
Workaround: Disable port security.
CSCtb40187
•
Workarounds: Configure identical policy-maps with different names so that each EtherChannel has its own policy. This action restricts the effect of this link flap to a limited number of EtherChannels.
CSCsz82795
•
Workaround: Configure an access-list to permit the CPU generated packets and apply the ACL to the class-map.
CSCsy43967
Open Caveats in Cisco IOS Release 12.2(50)SG5
This section lists the open caveats in Cisco IOS Release 12.2(50)SG5:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
Workaround: None. (CSCsu42775)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876)
•
Workaround: Remove the above debug command. (CSCsu67323)
•
Workaround: None. (CSCsv42869)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy72343
•
Do not enter this command if port security is not configured on the interface.
Do not enter this command on fa1.
Workaround: None. CSCtb16586
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
Resolved Caveats in Cisco IOS Release 12.2(50)SG5
This section lists the resolved caveats in Release 12.2(50)SG5:
•
This caveat occurs when a register value is corrupted and you subsequently enable a Layer 3 feature.
Workaround: None (CSCsz48273)
Open Caveats in Cisco IOS Release 12.2(50)SG4
This section lists the open caveats in Cisco IOS Release 12.2(50)SG4:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
Workaround: None. (CSCsu42775)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876)
•
Workaround: Remove the above debug command. (CSCsu67323)
•
Workaround: None. (CSCsv42869)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy72343
•
Do not enter this command if port security is not configured on the interface.
Do not enter this command on fa1.
Workaround: None. CSCtb16586
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
Resolved Caveats in Cisco IOS Release 12.2(50)SG4
This section lists the resolved caveats in Release 12.2(50)SG4:
•
'This problem is seen on all Catalyst 4500 or 4900 chassis running Cisco IOS Release 12.2.(50)SG. The problem occurs when the following conditions are present:
–
–
–
Workarounds: Do not configure the callback or callback-dialstring attribute for the user. If you use the callback-dialstring attribute in the TACACS+ profile, ensure that the NULL value is not configured. (CSCei62358)
•
This problem occurs only when a port is configured with PVLAN and 802.1X multi-auth.
Workaround: Shut down then reopen the interface. (CSCsr58573)
•
Workaround: Reapply the identity policy on the interface with the permit icmp command. (CSCsu03507
•
001298: .Oct 8 01:38:50.968: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: flCam0aPErr interrupt. errAddr: 0x2947 dPErr: 1 mPErr: 0 valid: 1001299: .Oct 8 01:51:20.100: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: flCam0aPErr interrupt. errAddr: 0x2B59 dPErr: 1 mPErr: 0 valid: 1They imply no impact to performance.
Workaround: None. (CSCsv17545)
•
Port-channel functionality is not supported on the management interface.
This is a configuration error.
Workaround: None. (CSCsv91302)
•
Workaround: None. (CSCsw32519)
•
Workaround: None. CSCsy29140
•
show int status | inc gi x/y command indicates notconnect.Similar behavior is observed with Supervisor Engine 6-E uplinks and the WS-X4706-10GE line card.
This behavior is seen in Cisco IOS Releases 12.2(50)SG thru 12.2(50)SG3 when the peer device sends a remote fault.
Workaround: Disable auto negotiation at both ends.
(CSCta02425)
Open Caveats in Cisco IOS Release 12.2(50)SG3
This section lists the open caveats in Cisco IOS Release 12.2(50)SG3:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFP+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+, SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
Workaround: Reapply the identity policy on the interface with the permit icmp command. (CSCsu03507
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
This problem occurs only when a port is configured with PVLAN and 802.1X multi-auth.
Workaround: Shut down then reopen the interface. (CSCsr58573)
•
Workaround: None. (CSCsu42775)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed, do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876)
•
Workaround: Remove the above debug command. (CSCsu67323)
•
Workaround: None. (CSCsv42869)
•
'This problem is seen on all Catalyst 4500 or 4900 chassis running Cisco IOS Release 12.2.(50)SG. The problem occurs when the following conditions are present:
–
–
–
Workarounds: Do not configure the callback or callback-dialstring attribute for the user. If you use the callback-dialstring attribute in the TACACS+ profile, ensure that the NULL value is not configured. (CSCei62358)
•
Workaround: None. (CSCsw32519)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
Port-channel functionality is not supported on the management interface.
This is a configuration error.
Workaround: None. (CSCsv91302)
•
001298: .Oct 8 01:38:50.968: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: flCam0aPErr interrupt. errAddr: 0x2947 dPErr: 1 mPErr: 0 valid: 1001299: .Oct 8 01:51:20.100: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: flCam0aPErr interrupt. errAddr: 0x2B59 dPErr: 1 mPErr: 0 valid: 1They imply no impact to performance.
Workaround: None. (CSCsv17545)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy29140
•
Workaround: None. CSCsy72343
•
show int status | inc gi x/y command indicates notconnect.Similar behavior is observed with Supervisor Engine 6-E uplinks and the WS-X4706-10GE line card.
This behavior is seen in Cisco IOS Releases 12.2(50)SG thru 12.2(50)SG3 when the peer device sends a remote fault.
Workaround: Disable auto negotiation at both ends.
(CSCta02425)
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
Resolved Caveats in Cisco IOS Release 12.2(50)SG3
This section lists the resolved caveats in Release 12.2(50)SG3:
•
TwinGig converters are only supported on E-series supervisors and line cards. This bug does not affect systems without installed converters.
Workaround: None.
Once the switch has booted successfully and has detected all installed TwinGig converters, it is unlikely to crash unless you insert a converter. CSCsz49331
Open Caveats in Cisco IOS Release 12.2(50)SG2
This section lists the open caveats in Cisco IOS Release 12.2(50)SG2:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds:Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFp+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+ , SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
Workaround: Reapply the identity policy on the interface with the permit icmp command. (CSCsu03507
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
This problem occurs only when a port is configured with PVLAN and 802.1X multi-auth.
Workaround: Shut down then reopen the interface. (CSCsr58573)
•
Workaround: None. (CSCsu42775)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed , do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876)
•
Workaround: Remove the above debug command. (CSCsu67323)
•
Workaround: None. (CSCsv42869)
•
'This problem is seen on all Catalyst 4500 or 4900 chassis running CiscoIOS Release 12.2.(50)SG. The problem occurs when the following conditions are present:
–
–
–
Workarounds: Do not configure the callback or callback-dialstring attribute for the user. If you use the callback-dialstring attribute in the TACACS+ profile, ensure that the NULL value is not configured. (CSCei62358)
•
Workaround: None. (CSCsw32519)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
Port-channel functionality is not supported on the management interface.
This is a configuration error.
Workaround: None. (CSCsv91302)
•
001298: .Oct 8 01:38:50.968: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: flCam0aPErr interrupt. errAddr: 0x2947 dPErr: 1 mPErr: 0 valid: 1001299: .Oct 8 01:51:20.100: %C4K_SWITCHINGENGINEMAN-4-TCAMINTERRUPT: flCam0aPErr interrupt. errAddr: 0x2B59 dPErr: 1 mPErr: 0 valid: 1They imply no impact to performance.
Workaround: None. (CSCsv17545)
•
If the switch were to run a supervisor switchover while in this state, the host's MAC address would not be present in the new active supervisor engine's MAC address table, causing possible connectivity interruption on the host.
Workaround: Enter the shutdown command, followed by the no shutdown command on the interface. This triggers relearning and synchronizing of the host's MAC to the standby supervisor engine. CSCsw91661
•
Workaround: None. CSCsy29140
•
Workaround: None. CSCsy72343
•
show int status | inc gi x/y command indicates notconnect.Similar behavior is observed with Supervisor Engine 6-E uplinks and the WS-X4706-10GE line card.
This behavior is seen in Cisco IOS Releases 12.2(50)SG thru 12.2(50)SG3 when the peer device sends a remote fault.
Workaround: Disable auto negotiation at both ends.
(CSCta02425)
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
Resolved Caveats in Cisco IOS Release 12.2(50)SG2
This section lists the resolved caveats in Release 12.2(50)SG2:
•
Workarounds:
1. Configure a static ARPA entry for host.
2. Upgrade to a future IOS release containing the fix.
CSCsu90780
•
Workaround: None. CSCsv63638
•
Workaround: None. CSCsv91297
•
Affected Cisco IOS releases include 12.2(31)SGA08, 12.2(37)SG, 12.2(40)SG, 12.2(46)SG, and 12.2(50)SG.
Workaround: Disable and configure QoS, as follows:
Switch# conf tEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# no qosSwitch(config)# qosSwitch(config)# endSwitch#CSCsw19087
•
Workaround: None. CSCsw29489
•
Workaround: None. CSCsw77413
•
authentication control-direction in command).Workarounds: Disable Wake-on-LAN with the no authentication control-direction in command.
CSCsx98360
•
Workaround: Turn off LLDP on the switch and Cisco IP phone from Call Manager.
CSCsy21167
Open Caveats in Cisco IOS Release 12.2(50)SG1
This section lists the open caveats in Cisco IOS Release 12.2(50)SG1:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds:Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFp+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+ , SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
Workaround: Reapply the identity policy on the interface with the permit icmp command. (CSCsu03507
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
This problem occurs only when a port is configured with PVLAN and 802.1X multi-auth.
Workaround: Shut down then reopen the interface. (CSCsr58573)
•
Workaround: None. (CSCsu42775)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed , do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876)
•
Workaround: Remove the above debug command. (CSCsu67323)
•
Workaround: None. (CSCsv42869)
•
'This problem is seen on all Catalyst 4500 or 4900 chassis running CiscoIOS Release 12.2.(50)SG. The problem occurs when the following conditions are present:
–
–
–
Workarounds: Do not configure the callback or callback-dialstring attribute for the user. If you use the callback-dialstring attribute in the TACACS+ profile, ensure that the NULL value is not configured. (CSCei62358)
•
Workaround: None. (CSCsw32519)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
Port-channel functionality is not supported on the management interface.
This is a configuration error.
Workaround: None. (CSCsv91302)
•
show int status | inc gi x/y command indicates notconnect.Similar behavior is observed with Supervisor Engine 6-E uplinks and the WS-X4706-10GE line card.
This behavior is seen in Cisco IOS Releases 12.2(50)SG thru 12.2(50)SG3 when the peer device sends a remote fault.
Workaround: Disable auto negotiation at both ends.
(CSCta02425)
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
Resolved Caveats in Cisco IOS Release 12.2(50)SG1
This section lists the resolved caveats in Release 12.2(50)SG1:
•
Workaround:To remove the host's MAC address from the port security MAC address table, unconfigure and reconfigure port security on the port. (CSCsr74097)
Open Caveats in Cisco IOS Release 12.2(50)SG
This section lists the open caveats in Cisco IOS Release 12.2(50)SG:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds:Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
Workaround: Before removing a linecard, delete the statically configured ip source binding entries on any of the interfaces on the line-card. (CSCsv54529)
•
Workaround: Clear the errors with the clear ethernet cfm errors command in EXEC mode. (CSCsv43819)
•
This problem impacts X2, OneX converters, and SFp+ on the Supervisor Engine 6-E, and linecards.
Workaround: Remove and reinsert the One X Convertor with SFP+ , SFP+ alone, or X2 after some perceivable delay. (CSCsu43461)
•
Workaround: Reapply the identity policy on the interface with the permit icmp command. (CSCsu03507
•
This problem occurs when an 802.1X client is authorized on a multi-auth port. After the access VLAN is deleted, then restored, the client is reauthorized but the spanning tree state of the access VLAN remains Disabled.
Workaround: Shut down then reopen the interface.
(CSCso50921)
•
This problem occurs only when a port is configured with PVLAN and 802.1X multi-auth.
Workaround: Shut down then reopen the interface. (CSCsr58573)
•
Workaround: None. (CSCsu42775)
•
Workaround: For VTP database propagation, configure ISL/dot1q trunk port. (CSCsu43445)
•
Workarounds: Do one of the following:
–
–
(CSCsv05205)
•
Workaround: When a log message appears indicating that the SFP+ has been removed , do one of the following:
–
–
–
(CSCsv90044)
•
Workaround: None. (CSCsr95941)
•
Workaround: None. (CSCsr95941)
•
Workaround: Do one of the following:
–
–
–
(CSCsu39009)
•
Workaround: Reconfigure tracking on the newly created interface. (CSCsr66876)
•
Workaround: Remove the above debug command. (CSCsu67323)
•
Workaround: None. (CSCsv42869)
•
'This problem is seen on all Catalyst 4500 or 4900 chassis running CiscoIOS Release 12.2.(50)SG. The problem occurs when the following conditions are present:
–
–
–
Workarounds: Do not configure the callback or callback-dialstring attribute for the user. If you use the callback-dialstring attribute in the TACACS+ profile, ensure that the NULL value is not configured. (CSCei62358)
•
Workaround: None. (CSCsw32519)
•
Workaround: To reconfigure VLAN Load Balancing with a different configuration, do the following:
a.
b.
c.
d.
(CSCsv69853)
•
%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.101 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8%SM-4-BADEVENT: Event 'eouAAAAuthor' is invalid for the current state 'eou_abort': eou_auth 4.1.0.102 Traceback= 101D9A88 10B76BB0 10B76FE0 10B7A114 10B7A340 1066A678 106617F8This applies to classic or E-series Catalyst 4500 supervisor engines running
Cisco IOS Release 12.2(50)SGWorkaround: None. (CSCsw14005)
•
Port-channel functionality is not supported on the management interface.
This is a configuration error.
Workaround: None. (CSCsv91302)
•
show int status | inc gi x/y command indicates notconnect.Similar behavior is observed with Supervisor Engine 6-E uplinks and the WS-X4706-10GE line card.
•
show int status | inc gi x/y command indicates notconnect.Similar behavior is observed with Supervisor Engine 6-E uplinks and the WS-X4706-10GE line card.
This behavior is seen in Cisco IOS Releases 12.2(50)SG thru 12.2(50)SG3 when the peer device sends a remote fault.
Workaround: Disable auto negotiation at both ends.
(CSCta02425)
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
•
This occurs only if the following conditions are satisfied:
–
–
–
Workaround: None.
CSCsz63739
Resolved Caveats in Cisco IOS Release 12.2(50)SG
This section lists the resolved caveats in Release 12.2(50)SG:
•
This behavior is only seen when VLAN is allocated after the IFM is configured.
Workaround: Unconfigure with the no ethernet cfm mep level mpid vlan command, then reconfigure the IFM with the ethernet cfm mep level mpid vlan command on the port after the VLAN is allocated. Verify that the C-Status of the IFM is Active with the
show ethernet cfm maintenance-points local command. (CSCsm85460)•
Workaround: Authenticate the phone before plugging a PC behind the phone. (CSCsq92724)
•
Workarounds: Do one of the following:
–
–
(CSCsq90598)
•
speed 10/100/1000 command, the applied policer or shape or shape value might correspond to the new forced speed.Service policy has to be configured with percentage police or shape or share values and the link speed is forced to a specific values. For example
Policy-map p1class-map c1police rate percent 10Workaround: Either use the speed auto 10/100/1000 command or the absolute policer, shape or shape values rather than percentage values. For example,
Policy-map p1class-map c1police rate 10 mbps(CSCsk56877
•
Workaround: None. You cannot explicitly check the trusted boundary state. However, you can indirectly determine this state:
The trusted boundary feature ensures whether the packet's COS/DSCP value will b e trusted or not. When the interface is not in a trusted state, the COS/DSCP fields are forced to zero on a received packet.
A QoS policy exists on that interface that uses that COS/DSCP value for classification. Therefore, if the packet classification is based on the packet value, you can infer that the interface is in a trusted state. (CSCsh72408)
•
Cisco has released free software updates that address this vulnerability.
Several mitigation strategies are outlined in the workarounds section of this advisory.
This advisory is posted at http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20090325-tcp
CSCsr29468
•
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available in the workarounds section of the advisory. This advisory is posted at the following link: http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20090325-udp
CSCsk64158
•
Conditions: A device configured for SSLVPN may stop accepting any new SSLVPN connections, due to a vulnerability in the processing of new TCP connections for SSLVPN services. If "debug ip tcp transactions" is enabled and this vulnerability is triggered, debug messages with connection queue limit reached will be observed. This vulnerability is documented in two separate Cisco bug IDs, both of which are required for a full fix: CSCso04657 and CSCsg00102.
CSCso04657
•
auto qos voip trust command on an interface with an attached service-policy, the standby supervisor engine reboots.Workaround: Remove all service-policies from the interface before entering the
auto qos voip trust command.CSCsq37471
•
In addition to these vulnerabilities, Cisco Nexus 5000 devices contain a TCP DoS vulnerability that may result in a system crash. This additional vulnerability was found as a result of testing the TCP state manipulation vulnerabilities.
Cisco has released free software updates for download from the Cisco website that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20090908-tcp24
CSCsv04836
Open Caveats in Cisco IOS Release 12.2(46)SG
This section lists the open caveats in Cisco IOS Release 12.2(46)SG:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
speed 10/100/1000 command, the applied policer or shape or shape value might correspond to the new forced speed.Service policy has to be configured with percentage police or shape or share values and the link speed is forced to a specific values. For example
Policy-map p1class-map c1police rate percent 10Workaround: Either use the speed auto 10/100/1000 command or the absolute policer, shape or shape values rather than percentage values. For example,
Policy-map p1class-map c1police rate 10 mbps(CSCsk56877
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: None. You cannot explicitly check the trusted boundary state. However, you can indirectly determine this state:
The trusted boundary feature ensures whether the packet's COS/DSCP value will b e trusted or not. When the interface is not in a trusted state, the COS/DSCP fields are forced to zero on a received packet.
A QoS policy exists on that interface that uses that COS/DSCP value for classification. Therefore, if the packet classification is based on the packet value, you can infer that the interface is in a trusted state. (CSCsh72408)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workarounds:Disable IGMP snooping on all the relevant VLANs before disabling it globally.
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Define the backup etherchannel before applying flexlink command. (CSCsq13477)
•
Workaround: None. (CSCsq99468)
•
config-if# auto qos voip cisco-phoneconfig# default interface interface-nameWorkaround: Replace the default interface command with the following:
config# interface interface-numberconfig-if# switchport(CSCsq47116)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
This behavior is only seen when VLAN is allocated after the IFM is configured.
Workaround: Unconfigure with the no ethernet cfm mep level mpid vlan command, then reconfigure the IFM with the ethernet cfm mep level mpid vlan command on the port after the VLAN is allocated. Verify that the C-Status of the IFM is Active with the
show ethernet cfm maintenance-points local command. (CSCsm85460)•
Workaround: Authenticate the phone before plugging a PC behind the phone. (CSCsq92724)
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
Workarounds: Do one of the following:
–
–
(CSCsq90598)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
Resolved Caveats in Cisco IOS Release 12.2(46)SG
This section lists the resolved caveats in Release 12.2(46)SG:
•
Workarounds: Before removing the service policy from a ether channel member, remove it from the channel. Then, return it to the channel. (CSCsk70568)
•
In a queuing QoS policy, there can be zero or more queuing classes that have an explicit, user specified, bandwidth share specified. There can be zero or more queuing classes that do not have such user specified bandwidth share. The system takes the unallocated bandwidth share and allocates it equally among the latter set of classes.
When using percentage-based bandwidth allocation, if the share comes to less than 1%, the queues corresponding to those classes do not get updated in hardware with the new bandwidth share. These queues get more than the expected share of bandwidth.
Workarounds: Ensure that the unallocated bandwidth percentage is at least equal to the number of queues that do not have the explicit bandwidth percentage command. This should include the default as well as priority queues. (CSCsk77757)
•
%C4K_HWACLMAN-4-ACLHWLABELERR: Path (in :50, 1006) label allocation failure: SignatureInconsistent - packets will be handled in software, QoS is disabled.One feature combination that can trigger this problem is the attempt to combine a QoS policy that matches on cos bits with IPv6 ACL configuration that matches on IPv6 source addresses that partially mask in the lower 48 bits of the address. (IPv6 subnets in the /81 to /127 range will also trigger this behavior if IPv6 multicast routing is enabled.)
Workaround: Do not configure feature combinations that conflict. Currently the above conflict between QoS policies matching on COS bits and IPv6 configuration with partial masking of the lower 48 bits of the source address is the only known conflicting feature combination. If matching on COS bits is required by the QoS policy, architect the IPv6 network using /80 subnets or larger. (CSCsk79791)
•
Workaround: Do the following:
1. Un-configure the interface(s) on which this policy-map is attached from the portchannel.
2. Modify the policy-map.
3. Configure the interface(s) in the portchannel.
(CSCsk77119)
•
Workaround: None. (CSCsh99124)
•
Workaround: Re-apply the policy-map. (CSCsk75793
•
Currently, if it is applied to a port that is already a member of a portchannel, the application is rejected with an error message. However, the reverse is not true. If auto-QoS is applied first and then the port joins a portchannel, the command is accepted.
The following example using port g2/1 shows the type of usage that should be avoided:
conf tint g2/1auto qos voice trustchannel-group 10 mode autoThis example applies auto-QoS on a port (g2/1) and subsequently makes the port a member of portchannel (10).
Workaround: Do not make a port with auto-QoS enabled a member of a portchannel. (CSCsi95018)
•
Workaround: Enter the show policy-map interface command. (CSCsj44237)
•
Queuing policy is supported on a physical interface in the output direction only.
Workaround: After bootup, reattach a queuing policy on a physical interface. (CSCsk87548)
•
Workaround: Before deleting the port-channel, do the following:
1. Remove any per-port per-VLAN QoS policies, if any.
2. Remove the VLAN configuration on the port-channel with the no vlan-range command.
(CSCsk91916)
•
Workaround: None. (CSCsk45940)
•
Workaround: None. (CSCsl26706)
•
Workaround: None. (CSCsl37599)
Open Caveats in Cisco IOS Release 12.2(40)XO
This section lists the open caveats in Cisco IOS Release 12.2(40)XO:
•
Workarounds: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
Workarounds: Before removing the service policy from a ether channel member, remove it from the channel. Then, return it to the channel. (CSCsk70568)
•
In a queuing QoS policy, there can be zero or more queuing classes that have an explicit, user specified, bandwidth share specified. There can be zero or more queuing classes that do not have such user specified bandwidth share. The system takes the unallocated bandwidth share and allocates it equally among the latter set of classes.
When using percentage-based bandwidth allocation, if the share comes to less than 1%, the queues corresponding to those classes do not get updated in hardware with the new bandwidth share. These queues get more than the expected share of bandwidth.
Workarounds: Ensure that the unallocated bandwidth percentage is at least equal to the number of queues that do not have the explicit bandwidth percentage command. This should include the default as well as priority queues. (CSCsk77757)
•
%C4K_HWACLMAN-4-ACLHWLABELERR: Path (in :50, 1006) label allocation failure: SignatureInconsistent - packets will be handled in software, QoS is disabled.One feature combination that can trigger this problem is the attempt to combine a QoS policy that matches on cos bits with IPv6 ACL configuration that matches on IPv6 source addresses that partially mask in the lower 48 bits of the address. (IPv6 subnets in the /81 to /127 range will also trigger this behavior if IPv6 multicast routing is enabled.)
Workaround: Do not configure feature combinations that conflict. Currently the above conflict between QoS policies matching on COS bits and IPv6 configuration with partial masking of the lower 48 bits of the source address is the only known conflicting feature combination. If matching on COS bits is required by the QoS policy, architect the IPv6 network using /80 subnets or larger. (CSCsk79791)
•
speed 10/100/1000 command, the applied policer or shape or shape value might correspond to the new forced speed.Service policy has to be configured with percentage police or shape or share values and the link speed is forced to a specific values. For example
Policy-map p1class-map c1police rate percent 10Workaround: Either use the speed auto 10/100/1000 command or the absolute policer, shape or shape values rather than percentage values. For example,
Policy-map p1class-map c1police rate 10 mbps(CSCsk56877
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
Workaround: Do the following:
1. Un-configure the interface(s) on which this policy-map is attached from the portchannel.
2. Modify the policy-map.
3. Configure the interface(s) in the portchannel.
(CSCsk77119)
•
Workaround: None. (CSCsh99124)
•
On a Catalyst 4900M running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
Workaround: Reinsert the X2. (CSCsk43618)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
Workaround: Re-apply the policy-map. (CSCsk75793
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: None. You cannot explicitly check the trusted boundary state. However, you can indirectly determine this state:
The trusted boundary feature ensures whether the packet's COS/DSCP value will b e trusted or not. When the interface is not in a trusted state, the COS/DSCP fields are forced to zero on a received packet.
A QoS policy exists on that interface that uses that COS/DSCP value for classification. Therefore, if the packet classification is based on the packet value, you can infer that the interface is in a trusted state. (CSCsh72408)
•
Currently, if is applied to a port that is already a member of a portchannel, the application is rejected with an error message. However, the reverse is not true. If auto-QoS is applied first and then the port joins a portchannel, the command is accepted.
The following example using port g2/1 shows the type of usage that should be avoided:
conf tint g2/1auto qos voice trustchannel-group 10 mode autoThis example applies auto-QoS on a port (g2/1) and subsequently makes the port a member of portchannel (10).
Workaround: Do not make a port with auto-QoS enabled a member of a portchannel. (CSCsi95018)
•
Workaround: If you plan to change a class-map action, such as exceed-action, you meed to remove the class-map with the no class c1 command under policy-map submode. Then, apply the new class-map with the updated changes.
CSCsk70826)
•
The switch supports two-level hierarchical policy-maps. Policing actions can be present at only one of the two levels (parent or child). If they are present at the child level, they are not applied.
Workaround: None. (CSCsl0631)
•
Workaround: Avoid creating a VLAN that has been allocated internally to a routed port. (CSCsh60244)
•
Workaround: Enter the show policy-map interface command. (CSCsj44237)
•
Workaround: Enter the show policy-map interface command. (CSCsi71036)
•
Queuing policy is supported on a physical interface in the output direction only.
Workaround: After bootup, reattach a queuing policy on a physical interface. (CSCsk87548)
•
Workaround: Before deleting the port-channel, do the following:
1. Remove any per-port per-VLAN QoS policies, if any.
2. Remove the VLAN configuration on the port-channel with the no vlan-range command.
(CSCsk91916)
•
Workaround: None. (CSCsk45940)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. (CSCsi94144)
•
Workaround: None. (CSCsl39767)
•
Workaround: None. (CSCsl26706)
•
Workaround: None. (CSCsl37599)
•
The following conditions may cause a RACL to malfunction:
–
–
Here are two examples of such non-functioning RACL:
IPv6 access list a1permit icmp any any nd-ns sequence 10deny ipv6 any any sequence 20IPv6 access list a2permit icmp 2020::/96 any nd-ns sequence 10deny ipv6 any any sequence 20Workaround: None.
CSCtc13297
Resolved Caveats in Cisco IOS Release 12.2(40)XO
This section lists the resolved caveats in Release 12.2(40)XO:
•
Troubleshooting
These sections provide troubleshooting guidelines for the Catalyst 4900M series switch running IOS supervisor engines:
•
Netbooting from the ROMMON
Netbooting using a boot loader image is not supported. Instead, use one of the following options to boot an image:
1.
rommon 1> boot slot0:<bootable_image>2.
The ROMMON TFTP boot is very similar to the BOOTLDR TFTP boot, except that:
–
–
To boot from ROMMON, perform the following tasks while in ROMMON mode:
a.
b.
c.
For example, to set the supervisor engine Ethernet port with an IP address 172.16.1.5 and IP mask 255.255.255.0, enter the following command:
rommon 2> set interface fa1 172.16.1.5 255.255.255.0d.
e.
f.
For example, to boot the image name cat4500-ipbase-mz located on the TFTP server 172.16.1.8, enter the following command:
rommon 3> boot tftp://172.16.1.8/tftpboot/cat4500-ipbase-mzTroubleshooting at the System Level
This section contains troubleshooting guidelines for system-level problems:
•
•
Troubleshooting Modules
This section contains troubleshooting guidelines for the Catalyst 4900M series switch:
•
Troubleshooting MIBs
For general information on MIBs, RMON groups, and traps, refer to the Cisco public MIB directory (http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml). For information on the specific MIBs supported by the Catalyst 4900M series switches, refer to the Catalyst 4000 MIB Support List located at ftp://ftp.cisco.com/pub/mibs/supportlists/cat4000/cat4000-supportlist.html.
Related Documentation
Although their Release Notes are unique, the 4 platforms (Catalyst 4500, Catalyst 4900, Catalyst ME 4900, and Catalyst 4900M) use the same Software Configuration Guide, Command Reference Guide, and System Message Guide. Refer to the following home pages for additional information:
•
http://www.cisco.com/go/cat4500/docs
•
http://www.cisco.com/go/cat4900/docs
•
http://www.cisco.com/en/US/products/ps7009/tsd_products_support_series_home.html
Hardware Documents
Installation guides and notes including specifications and relevant safety information are available at the following URLs:
•
•
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_installation_guides_list.html
•
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_installation_guides_list.html
•
http://www.cisco.com/en/US/products/ps6021/prod_installation_guides_list.html
•
http://www.cisco.com/en/US/products/ps7009/prod_installation_guides_list.html
Software Documentation
Software release notes, configuration guides, command references, and system message guides are available at the following URLs:
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_release_notes_list.html
•
http://www.cisco.com/en/US/products/ps6021/prod_release_notes_list.html
•
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/release/note/OL_11511.html
Software documents for the Catalyst 4500 Classic, Catalyst 4500 E-Series, Catalyst 4900, and
Cisco ME 4900 Series Ethernet Switches are available at the following URLs:•
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_command_reference_list.html
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_system_message_guides_list.html
Cisco IOS Documentation
Platform-independent Cisco IOS documentation may also apply to the Catalyst 4500 and 4900 switches. These documents are available at the following URLs:
•
http://www.cisco.com/en/US/products/ps6350/products_installation_and_configuration_guides_list.html
•
http://www.cisco.com/en/US/products/ps6350/prod_command_reference_list.html
You can also use the Command Lookup Tool at:
http://tools.cisco.com/Support/CLILookup/cltSearchAction.do
•
http://www.cisco.com/en/US/products/ps6350/products_system_message_guides_list.html
You can also use the Error Message Decoder tool at:
http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi
•
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Notices
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
4.
5.
6.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
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, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe 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 of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
Release Notes for the Catalyst 4900 Series Switch, Cisco IOS Release 12.2(53)SG
Copyright © 2008-2009, Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)