PDF(573.8 KB) View with Adobe Reader on a variety of devices
Updated:September 30, 2020
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Release Notes for Catalyst 4900M, Catalyst 4948E and Catalyst 4948E-F Series Switches, Cisco IOS Release 15.2(4)Ex
First Published: October 1, 2015
Last Updated:September 30, 2020
These release notes describe the features, modifications, and caveats for Cisco IOS Release 15.2(4)E on the Catalyst 4900M switch, the Catalyst 4948E Ethernet Switch, and the Catalyst 4948E-F Ethernet Switch.
Cisco Catalyst 4900M Series is 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 Gigabit Ethernet servers or all 10 Gigabit Ethernet 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.
With Cisco IOS Release 12.2(54)XO, Cisco introduced the Catalyst 4948E Ethernet Switch, which is the first Cisco Catalyst E-Series data center switch built from the start to deliver class-leading, full-featured server-access switching. The switch offers forty-eight 10/100/1000-Gbps RJ45 downlink ports and four 1/10 Gigabit Ethernet uplink ports and is designed to simplify data center architecture and operations by offering service provider-grade hardware and software in a one rack unit (1RU) form factor optimized for full-featured top-of-rack (ToR) data center deployments.
The Cisco Catalyst 4948E Ethernet Switch builds on the advanced technology of the Cisco Catalyst 4948 Switches, the most deployed ToR switch in the industry, with more than 10 million ports deployed worldwide. The Cisco Catalyst E-Series doubles the uplink bandwidth and offers true front-to-back airflow with no side or top venting. Stringent airflow management reduces data center operating costs by providing strict hot-aisle and cold-aisle isolation. Exceptional reliability and serviceability are delivered with optional internal AC and DC 1+1 hot-swappable power supplies and a hot-swappable fan tray with redundant fans.
With Cisco IOS Software Release 12.2(54)WO, Cisco extended the widely deployed Cisco Catalyst® 4948E Ethernet Switch to offer back-to-front airflow with the Cisco Catalyst 4948E-F Switch.
Note Although this release note and those for the Catalyst 4900M, Catalyst 4948E, Catalyst 4948E-F Series Switches, Catalyst 4500 Series Switches, and the Catalyst 4500-X Series Switches differ, each leverages the same Software Configuration Guide, Command Reference Guide, and System Message Guide.
The Enterprise Services image supports Cisco Catalyst 4948E, Catalyst 4948E-F and Catalyst 4900M Ethernet Switch Series software features based on Cisco IOS Software 15.1(2)SG, including enhanced routing. BGP capability is included in the Enterprises Services package.
The IP Base image supports Open Shortest Path First (OSPF) for Routed Access, Enhanced Interior Gateway Routing Protocol (EIGRP) “limited” Stub Routing, Nonstop Forwarding/Stateful Switchover (NSF/SSO), and RIPv1/v2. The IP Base image does not support enhanced routing features such as BGP, Intermediate System-to-Intermediate System (IS-IS), Full OSPF, Full Enhanced Interior Gateway Routing Protocol (EIGRP) & Virtual Routing Forwarding (VRF-lite).
The LAN Base image complements the existing IP Base and Enterprise Services images. It is focused on customer access and Layer 2 requirements and therefore many of the IP Base features are not required. The IP upgrade image is available if at a later date you require some of those features. The Cisco Catalyst 4900M Switch Series only supports the IP Base and Enterprise Services images.
Starting with Cisco IOS Release 15.0(2)SG, on Catalyst 4900M, Catalyst 4948E and Catalyst 4948E-F, support for NEAT feature has been extended from IP Base to LAN Base and support for HSRP v2 IPV6 has been extended from Enterprise Services to IP Base.
Starting with Cisco IOS Release 15.2(1)E, OSPF Routed Access in IP Base support rose to 1000 routes.
Note The default image for WS-4900M, WS-C4948E, and WS-C4948E-F is IP Base.
Cisco IOS Release Strategy
Customers with Catalyst 4948E, Catalyst 4948E-F and Catalyst 4900M series switches who need the latest hardware support and software features should migrate to Cisco IOS Release 15.2(4)E.
The Catalyst 4900M Series Switch have these maintenance trains: 15.0(2)SGx, 15.1(2)SGx,15.2(3)E, and 15.2(4)E. The Catalyst 4948E/E-F switches have these maintenance trains: 15.0(2)SGx, 15.1(2)SGx, 15.2(3)E, and 15.2(4)E.
Figure 1 displays the active trains, 12.2(53)SG, 15.0(2)SG, and 15.1(2)SG,.
Note Support for the Catalyst 4900M platform was introduced in Cisco IOS 12.2(40)XO. Support for the Catalyst 4948E platform was introduced in Cisco IOS 12.2(54)XO. Support for the Catalyst 4948E-F platform was introduced in Cisco IOS 12.2(54)SG1.
Figure 1 Software Release Strategy for the Catalyst 4900M, Catalyst 4948E, Catalyst 4948E-F Series Switches
The following table lists where you can find information about supported pluggable transceiver modules and the minimum Cisco IOS Software release required:
NoteThe default image for the Catalyst 4900M Series Switch is Cisco IOS Release 12.2(53)SG4. The default image for the Catalyst 4948E Ethernet Switch and the Catalyst 4948E-F Ethernet Switch is 12.2(54)SG1.
Table 5 lists the Cisco IOS software features for the Catalyst 4948E, Catalyst 4948E-F and Catalyst 4900M series switches. For the full list of supported features, check the Feature Navigator application:
Table 5 LAN Base, IP Base, and Enterprise Services Image Support on the Catalyst 4900M, Catalyst 4948E, and Catalyst 4948E-F Switches (The Cisco Catalyst 4900M Switch Series does not support the LAN Base license)
Feature
LAN Base
IP Base
Enterprise Services
2-way Community Private VLANs
Yes
Yes
Yes
8-Way CEF Load Balancing
Yes
Yes
Yes
10G Uplink Use
Yes
Yes
Yes
AAA Server Group
Yes
Yes
Yes
ACL Logging
Yes
Yes
Yes
ANCP Client
No
Yes
Yes
ANSI TIA-1057 LLDP - MED Location Extension
Yes
Yes
Yes
ANSI TIA-1057 LLDP - MED Support
Yes
Yes
Yes
AppleTalk 1 and 2 (not supported on Sup 6-E and 6L-E)
No
No
Yes
Auto Configuration
Yes
Yes
Yes
Auto SmartPorts
Yes
Yes
Yes
Auto-QoS
Yes
Yes
Yes
Auto-QoS Compact
Yes
Yes
Yes
Auto-QoS VoIP
Yes
Yes
Yes
Auto-MDIX
Yes
Yes
Yes
Auto-Voice VLAN (part of Auto QoS)
No
Yes
Yes
Bidirectional Forwarding Detection (BFD) Hardware Offload Support
No
Yes
Yes
BFD - EIGRP Support
No
Yes
Yes
BFD - Static Route Support over IPv4
No
Yes
Yes
BFD IPv6 Encapsulation Support
No
Yes
Yes
BGP Support for BFD
No
No
Yes
BGP
No
No
Yes
BGP 4
No
No
Yes
BGP 4 4Byte ASN (CnH)
No
No
Yes
BGP 4 Multipath Support
No
No
Yes
BGP 4 Prefix Filter and In-bound Route Maps
No
No
Yes
BGP Conditional Route Injection
No
No
Yes
BGP Link Bandwidth
No
No
Yes
BGP Neighbor Policy
No
No
Yes
BGP Prefix-Based Outbound Route Filtering
No
No
Yes
BGP Route-Map Continue
No
No
Yes
BGP Route-Map Continue Support for Outbound Policy
No
No
Yes
BGP Route-Map Policy List Support
No
No
Yes
BGP Soft Reset
No
No
Yes
BGP Wildcard
No
No
Yes
Bidirectional PIM (IPv4 only)
No
Yes
Yes
BOOTP
Yes
Yes
Yes
Bootup GOLD
No
Yes
Yes
Broadcast/Multicast Suppression
Yes
Yes
Yes
Call Home
No
Yes
Yes
CDP/CDPv2
Yes
Yes
Yes
CFM
Yes
Yes
Yes
CGMP - Cisco Group Management Protocol
Yes
Yes
Yes
Cisco IOS Scripting w/Tcl
Yes
Yes
Yes
CiscoView Autonomous Device Manager (ADP)
Yes
Yes
Yes
Cisco TrustSec—SGT/ SGA
No
Yes
Yes
Cisco TrustSec—SGACL Logging and Statistics
No
Yes
Yes
CNS
Yes
Yes
Yes
Command Scheduler (Kron)
Yes
Yes
Yes
Community PVLAN support
No
Yes
Yes
Config File
Yes
Yes
Yes
Configuration Replace and Configuration Rollback
Yes
Yes
Yes
Configuration Rollback Confirmed Change
Yes
Yes
Yes
Copy Command
Yes
Yes
Yes
Console Access
Yes
Yes
Yes
Control Plane Policing (CoPP)
Yes
Yes
Yes
CoS to DSCP Map
Yes
Yes
Yes
CPU Optimization for Layer 3 Multicast Control Packets
Vlan Switching and Selective QinQ on the Same Port
No
Yes
Yes
Voice VLAN
Yes
Yes
Yes
VRF-aware TACACS+
No
No
Yes
VRF-aware PBR
No
No
Yes
VRF-lite for IPv6 on OSPF/ BGP/ EIGRP
No
No
Yes
VTP (Virtual Trunking Protocol) Version 2
Yes
Yes
Yes
VTP version 3
Yes
Yes
Yes
WCCP Redirection on Inbound Interfaces
No
Yes
Yes
WCCP Version 2
No
Yes
Yes
WCCP Version 2 for IPv6
No
No
Yes
XML-PI
Yes
Yes
Yes
1.Supported only on Supervisor Engine 6-E and Supervisor Engine 6L-E
2.Starting with Cisco IOS Release 12.2(46)SG
3.When either Source or Prefix Guard for IPv6 is enabled, ICMPv6 packets are unrestricted on all Catalyst 4500 series switch platforms running IOS Cisco Release 15.2(1)E. All other traffic types are restricted.
4.IP Base supports only one OSPFv2 and one OSPFv3 instance with a maximum number of 200 dynamically learned routes.
5.OSPF for Routed Access supports only one OSPFv2 and one OSPFv3 instance with a maximum number of 1000 dynamically learned routes.
6.TDR is supported on 4948E(F) and WS-X4908-10GB-R.
7.WS-C4948E-10GE does not support VLAN mapping.
MIB Support
For information on MIB support, please refer to this URL:
The Cisco IOS Release 15.2(4)E Documentation Roadmap provides quick and easy access to all relevant documentation for specific platforms. Look for Quick Links to Platform Documentation on the respective platform documentation pages. For more information, see: http://www.cisco.com/c/en/us/support/ios-nx-os-software/ios-15-2e/tsd-products-support-series-home.html
These sections describe the new and changed information for the Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches running Cisco IOS software:
No new features were introduced in Cisco IOS Release 15.2(4)E10.
New Features in Cisco IOS Release 15.2(4)E9
No new features were introduced in Cisco IOS Release 15.2(4)E9.
New Features in Cisco IOS Release 15.2(4)E8
No new features were introduced in Cisco IOS Release 15.2(4)E8.
New Features in Cisco IOS Release 15.2(4)E7
No new features were introduced in Cisco IOS Release 15.2(4)E7.
New Features in Cisco IOS Release 15.2(4)E6
No new features were introduced in Cisco IOS Release 15.2(4)E6.
New Features in Cisco IOS Release 15.2(4)E5
No new features were introduced in Cisco IOS Release 15.2(4)E5.
New Features in Cisco IOS Release 15.2(4)E4
No new features were introduced in Cisco IOS Release 15.2(4)E4.
New Features in Cisco IOS Release 15.2(4)E3
No new features were introduced in Cisco IOS Release 15.2(4)E3.
New Features in Cisco IOS Release 15.2(4)E2
No new features were introduced in Cisco IOS Release 15.2(4)E2.
New Features in Cisco IOS Release 15.2(4)E1
Table 7 New Software Features in this Release
Feature Name
Description
Limiting Login
The Limiting Login feature helps network administrators to limit the login attempt of users to a network. When a user fails to successfully login to a network within a configurable number of attempts within a configurable time limit, the user can be blocked. This feature is enabled only for local users and not for remote users. You need to configure the aaa authentication rejected command in global configuration mode to enable this feature.
x.509v3 with SSH Authentication
This feature uses the public key algorithm (PKI) for server and user authentication, and allows the Secure Shell (SSH) protocol to verify the identity of the owner of a key pair via digital certificates, signed and issued by a Certificate Authority (CA).
New Features in Cisco IOS Release 15.2(4)E
New Hardware Features
Table 8 New Hardware Features in this Release
Feature Name
Description
Support for BX SFP and SFP+ Transceivers
The following new BX SFP and SFP+ transceivers are supported on the WS-X4908-10GE and WS-X4904-10GE modules on Cisco Catalyst 4900-M switches8, and on Cisco Catalyst 4948-E and Cisco Catalyst 4948-F switches on SFP and SFP+ ports:
SFP-10G-BXD-I
SFP-10G-BXU-I
SFP-10G-BX40D-I
SFP-10G-BX40U-I
GLC-BX40-D-I
GLC-BX80-D-I
GLC-BX40-U-I
GLC-BX80-U-I
GLC-BX40-DA-I
8.Using a Cisco TwinGig Converter Module for 1G and a Cisco OneX Converter Module for 10G.
New Software Features
Table 9 New Software Features in this Release
Feature Name
Description
Cisco TrustSec—SGACL Logging and Statistics
Option to enable logging of Security Group-Based Access Control (SGACL) information and Access Control Entry (ACE) statistics. The logged information includes the source and destination security group tag, the SGACL policy name, packet protocol type, the action performed on the packet, and ACE matches. For more information, see the Cisco TrustSec Switch Configuration Guide on cisco.com.
(IP Base and Enterprise Services)
LACP Min-Links
Allows you to specify the minimum number of active ports that must be in the link-up state and bundled in an EtherChannel for the port channel interface to transition to the link-up state.
(LAN Base, IP Base, and Enterprise Services)
Link State Group
The upper limit of the link state group number value is now increased (from 10) to 20. You can configure upto 20 link state groups per switch.
(IP Base, and Enterprise Services)
Named VLAN
Option to specify a VLAN name for access and voice VLAN.
(LAN Base, IP Base, and Enterprise Services)
Policy-Based Routing (PBR) with Object Tracking
Support for a new command set ip next-hop verify-availability, to use PBR with object tracking, to verify the reachability of the next-hop IP address to which to forward packets, using an Internet Control Message Protocol (ICMP) ping as the verification method. This feature is supported only on IPv4 PBR and is not supported on IPv6 PBR, and PBR on VSS and VRF.
(IP Base and Enterprise Services)
Private VLAN (PVLAN) Support on LAN Base
PVLAN is now supported on LAN Base images.
(LAN Base)
Rapid PVST+ as Default
Rapid PVST+ is now the default spanning-tree mode used on all Ethernet port-based VLANs.
(LAN Base, IP Base, and Enterprise Services)
Resilient Ethernet Protocol (REP) Enhancements
Option to configure an administrative VLAN for each segment.
(LAN Base, IP Base, Enterprise Services)
Spanning Tree Protocol (STP) Enhancements
Bridge Assurance—Protects the network from bridging loops that are caused by that are caused by unidirectional links, or a malfunctioning switch. Bridge Assurance is enabled only on PortFast network ports.
Detecting UniDirectional Link Failures (or the STP Dispute Mechanism)—The switch port detects unidirectional link failures by checking the consistency of the port role and state of the BPDUs received. When a conflict is detected, the designated port reverts to a blocking state. This feature does not require any user configuration.
PVST+ Simulation—This is now user-configurable. You can enable or disable this per port, or globally. PVST+ simulation is enabled by default. It allows seamless interoperability between MST and Rapid PVST+.
(LAN Base, IP Base, Enterprise Services - Yes)
Storm Control Enhancements
Option to specify the threshold level for broadcast traffic in bits per second (bps) and packets per second (pps).
(LAN Base, IP Base, and Enterprise Services)
Vlan Switching and Selective QinQ on the Same Port
Option to disable default behavior of dropping non-translated VLANs. When configuring VLAN mapping for selective Q-in-Q on a trunk port, you now have the option to specify that packets that do not match, should not be dropped (Enter the no switchport vlan mapping default drop command).
(IP Base, and Enterprise Services)
WCCP Version 2 for IPv6
WCCPv2 now supports IPv6 traffic.
(Enterprise Services)
Minimum and Recommended ROMMON Release
Table 10 lists the minimum and recommended ROMMON releases for the Catalyst 4900M Series Switch, Catalyst 4948E Ethernet Switch, and Catalyst 4948E-F Ethernet Switch.
Table 10 Minimum and Recommended ROMMON Release for Catalyst 4900M, Catalyst 4948E, and Catalyst 4948E-F
Minimum ROMMON Release
Recommended ROMMON Release
Catalyst 4900M Switch
12.2(40r)XO
12.2(44r)SG10
Catalyst 4948E Ethernet Switch
12.2(44r)SG8
12.2(44r)SG10
Catalyst 4948E-F Ethernet Switch
12.2(44r)SG9
12.2(44r)SG10
Note ROMMON Release 12.2(44r)SG5 is the minimum required to run Cisco IOS Release 15.0(2)SG and is recommended for other releases.
Limitations and Restrictions
Following limitations and restrictions apply to the Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches:
The maximum MTE supported on the device is 8000, per direction.
Supervisor 6-E, Supervisor 6L-E, Catalyst 4900M, and Catalyst 4948-E do not support hardware Control Plane Policing (CoPP) for all IPv6 First Hop Security Features on all ports.
Starting with Cisco IOS Release 15.1(1)SG, the seven RP restriction was removed.
The WS-X4920-GB-RJ45 card performs at wire speed until it operates at 99.6% utilization. Beyond this rate, the card will lose some packets.
Compact Flash is not supported on a Cisco Catalyst 4900M switch running Cisco IOS Release 12.2(40)XO. Attempting to use Compact Flash may corrupt your data.
IP classful routing is not supported; do not use the no ip classless command; it will have no effect, as only classless routing is supported. The command ip classless is not supported as classless routing is enabled by default.
A Layer 2 LACP channel cannot be configured with the spanning tree PortFast feature.
An unsupported default CLI for mobile IP is displayed in the HSRP configuration. Although this CLI will not harm your system, you might want to remove it to avoid confusion.
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/1
switch(config)# no standby 0 name (0 is hsrp group number)
For HSRP “preempt delay” to function consistently, you must use the standby delay minimum command. Be sure to set the delay to more than 1 hello interval, thereby ensuring that a hello is received before HSRP leaves the initiate state.
Use the standby delay reload option if the router is rebooting after reloading the image.
You can run only.1q-in-.1q packet pass-through with the Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches.
For PVST, on the Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches VLANs, Cisco IOS Release 12.2(54)SG supports a maximum of 3000 spanning tree port instances. If you want to use more than this number of instances, you should use MST rather than PVST.
Because the Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches support the FAT file system, the following restrictions apply:
– The verify and squeeze commands are not supported.
– The rename command is supported in FAT file system.
For the Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches, the rename command has been added for bootflash and slot0. For all other supervisor engines, the rename command is supported for nvram devices only.
– the fsck command is supported for slot0 device. It is not supported in the file systems on supervisor engines other than 6-E.
– In the FAT file system, the IOS format bootflash: command erases user files only. It does not erase system configuration.
– The FAT file system supports a maximum of 63 characters for file/directory name. The maximum for path length is 127 characters.
– The FAT file system does not support the following characters in file/directory names:{}#%^ and space characters.
– The FAT file system honors the Microsoft Windows file attribute of "read-only" and "read-write", but it does not support the Windows file "hidden" attribute.
– Supervisor Engine 6-E uses the FAT file system for compact flash (slot0). If a compact flash is not formatted in FAT file system (such as compact flash on a supervisor engine other than 6-E), the switch does not recognize it.
If an original packet is dropped due to transmit queue shaping and/or sharing configurations, a SPAN packet copy can still be transmitted on the SPAN port.
All software releases support a maximum of 32,768 IGMP snooping group entries.
Use the no ip unreachables command on all interfaces with ACLs configured for performance reasons.
The threshold for the Dynamic Arp Inspection err-disable function is set to 15 ARP packets per second per interface. You should adjust this threshold depending on the network configuration. The CPU should not receive DHCP packets at a sustained rate greater than 1000 pps.
If you first configure an IP address or IPv6 address on a Layer 3 port, then change the Layer 3 port to a Layer 2 port with the switchport command, and finally change it back to a Layer 3 port, the original IP/IPv6 address will be lost.
If the Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches request information from the Cisco Secure Access Control Server (ACS) and the message exchange times out because the server does not respond, a message similar to this appears:
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.
If this message appears, 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.
For IP Port Security (IPSG) for static hosts, the following apply:
– As IPSG learns the static hosts on each interface, the switch CPU may hit 100 per cent if there are a large number of hosts to learn. The CPU usage will drop once the hosts are learned.
– IPSG violations for static hosts are printed as they occur. If multiple violations occur simultaneously on different interfaces, the CLI displays the last violation. For example, if IPSG is configured for 10 ports and violations exist on ports 3,6 and 9, the violation messages are printed only for port 9.
– Inactive host bindings will appear in the device tracking table when either a VLAN is associated with another port or a port is removed from a VLAN. So, as hosts are moved across subnets, the hosts are displayed in the device tracking table as INACTIVE.
– Autostate SVI does not work on EtherChannel.
When ipv6 is enabled on an interface via any CLI, it is possible to see the following message:
% Hardware MTU table exhausted
In 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.
To stop IPSG with Static Hosts on an interface, use the following commands in interface configuration submode:
Switch(config-if)# no ip verify source
Switch(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 globally
Switch(config)# ip device tracking max <n> ***set an IP device tracking maximum on int
Switch(config-if)# ip verify source tracking [port-security] ****activate IPSG on port
Caution
If you only configure the ip verify source tracking [port-security] interface configuration command on a port without enabling IP device tracking globally or setting an IP device tracking maximum on that interface, IPSG with Static Hosts will reject all the IP traffic from that interface.
Note The issue above also applies to IPSG with Static Hosts on a PVLAN Host port.
Class-map match statements using match ip prec | dscp match only IPv4 packets whereas matches performed with match prec | dscp match both IPv4 and IPv6 packets.
IPv6 QoS hardware switching is disabled if the policy-map contains IPv6 ACL and match cos in the same class-map with the ipv6 access-list has any mask range between /81 and /127. It results in forwarding packets to software which efficiently disable the QoS.
Management port does not support non-VRF aware features.
A Span destination of fa1 is not supported.
The "keepalive" CLI is not supported in interface mode on the switch, although it will appear in the running configuration. This behavior has no impact on functionality.
TDR is only supported on interfaces Gi1/1 through Gi1/48, at 1000BaseT under open or shorted cable conditions. TDR length resolution is +/- 10 m. If the cable is less than 10 m or if the cable is properly terminated, the TDR result displays "0" m. If the interface speed is not 1000BaseT, an "unsupported" result status displays. TDR results will be unreliable for cables extended with the use of jack panels or patch panels.
Upstream ports on the Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches support flow control auto negotiation in 1G mode only, and flow control is forced in 10G mode. If the interface is configured to auto-negotiate the flow control, and the interface is operating in 10G mode, the system forces flow control to ON and does not auto-negotiate.
The following guidelines apply to Fast UDLD:
– Fast UDLD is disabled by default.
– Configure fast UDLD only on point-to-point links between network devices that support fast UDLD.
– You can configure fast UDLD in either normal or aggressive mode.
– Do not enter the link debounce command on fast UDLD ports.
– Configure fast UDLD on at least two links between each connected network device. This reduces the likelihood of fast UDLD incorrectly error disabling a link due to false positives.
– Fast UDLD does not report a unidirectional link if the same error occurs simultaneously on more than one link to the same neighbor device.
– The Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches support fast UDLD on a maximum of 32 ports.
A XML-PI specification file entry does not return the desired CLI output.
The outputs of certain commands, such as show ip route and show access-lists, contain non-deterministic text. While the output is easily understood, the output text does not contain strings that are consistently output. A general purpose specification file entry is unable to parse all possible output.
Workaround (1):
While a general purpose specification file entry may not be possible, a specification file entry might be created that returns the desired text by searching for text that is guaranteed to be in the output. If a string is guaranteed to be in the output, it can be used for parsing.
For example, the output of the show ip access-lists SecWiz_Gi3_17_out_ip command is this:
Extended IP access list SecWiz_Gi3_17_out_ip
10 deny ip 76.0.0.0 0.255.255.255 host 65.65.66.67
20 deny ip 76.0.0.0 0.255.255.255 host 44.45.46.47
30 permit ip 76.0.0.0 0.255.255.255 host 55.56.57.57
The first line is easily parsed because access list is guaranteed to be in the output:
The remaining lines all contain the term host. As a result, the specification file may report the desired values by specifying that string. For example, this line
will produce the following for the first and second rules
<rule>
deny
</rule>
and the following for the third statement
<rule>
permit
<rule>
Workaround (2):
Request the output of the show running-config command using NETCONF and parse that output for the desired strings. This is useful when the desired lines contain nothing in common. For example, the rules in this access list do not contain a common string and the order (three permits, then a deny, then another permit), prevent the spec file entry from using permit as a search string, as in the following example:
Although the Catalyst 4900M series switch still supports legacy 802.1X commands used in Cisco IOS Release 12.2(46)SG and earlier releases (that is, they are accepted on the CLI), they do not display in the CLI help menu.
Current IOS software cannot support filenames exceeding 64 characters.
Although you can configure subsecond PIM query intervals on Catalyst 4500 platforms, such an action represents a compromise between convergence (reaction time) and a number of other factors (number of mroutes, base line of CPU utilization, CPU speed, processing overhead per 1 m-route, etc.). You must account for those factors when configuring subsecond PIM timers. We recommend that you set the PIM query interval to a minimum of 2 seconds. By adjusting the available parameters, you can achieve flawless operation; that is, a top number of multicast routes per given convergence time on a specific setup.
With Cisco IOS Release 12.2(53)SG3 (and 12.2(54)SG), we changed the default behavior such that your single supervisor, RPR, or fixed configuration switch does not reload automatically. To configure automatic reload, you must enter the diagnostic fpga soft-error recover aggressive command. (CSCth16953)
The ROMMON version number column in the output of show module command is truncated.
Workaround: Use the show version command. CSCtr30294
IP SLA session creation fails randomly for various 4-tuples.
Workaround: Select an alternate destination or source port. CSCty05405
The system cannot scale to greater than 512 SIP flows with MSP and metadata enabled.
Workaround: None. CSCty79236
If a class-map is configured with exceed-action drop, re-configuring the same class-map with exceed-action transmit causes class-map configurations to conflict for the same class-map.
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)
When you enter the show policy-map vlan vlan command, unconditional marking actions that are configured on the VLAN are not shown.
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions are displayed. CSCsi94144
An IP unnumbered configuration is lost after a reload.
Workarounds: Do one of the following:
– After a reload, copy the startup-config to the running-config.
– Use a loopback interface as the target of the ip unnumbered command
– Change the CLI configuration such that during bootup, the router port is created first.
CSCsq63051
After posture validation succeeds, the following benign traceback messages may appear after you unconfigure the global RADIUS and IP device tracking commands:
%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 106617F8
This applies to classic or E-series Catalyst 4500 supervisor engines running Cisco IOS Release 12.2(50)SG
Workaround: None. CSCsw14005
On the Cisco Catalyst 4948E, Catalyst 4948E-F and the Catalyst 4900M series switches, the host's MAC address is not synchronized to the standby supervisor engine after you unconfigure 802.1X on the port and reconnect the host to a IP phone (with CDP port status TLV support) that is connected to the switch.
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
When multiple streams of CRC errors are encountered on a WS-C4900M configured with OAM Configuration of monitoring the errored frame seconds, OAM does not always report the value of errored frame seconds correctly.
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.
Workaround: Configure a lower value of low threshold such that the frame errors are seen divided into the expected number of frame errored seconds. CSCsy37181
If time is not specified in the link debounce command, the default value depends on the supervisor engine. The default is 10 mS for the Catalyst 4948E, Catalyst 4948E-F, Catalyst 4900M, Supervisor Engine 6-E, and Supervisor Engine 6L-E. The default is 100 mS for all other supervisor engines.
Workaround: None. CSCte51948
Fast UDLD in aggressive mode may incorrectly errdisable a link in the following scenarios:
– Fast UDLD peer switch performs SSO.
– Fast UDLD peer switch is reloaded.
– One or more interfaces on a fast UDLD peer switch are shut down (or the port mode changes from switchport to routed, and vice versa).
Note To reduce the likelihood of this event, connect at least two physical interfaces between fast UDLD peer switches. You must configure the interfaces with the same neighbor fast hello interval.
Workarounds:
– Reset the error disabled links with the udld reset command.
– Configure error disable recovery with the commands errdisable recovery cause udld and errdisable recovery interval value (between 30 and 86400 sec).
– Manually clear errdisable on the local interface with a shutdown then a no shutdown.
CSCtc99007
On a peer interface on a switch, if errdisabled mode flap detection is set to a very small number (such as 2 flaps in 10 sec), a 10GE link flap may cause the peer interface to enter the errdisabled state.
Workarounds: The Cisco switch default link-flap detection value is 5 flaps in 10 seconds. Use the default value or larger numbers. CSCtg07677
When you have enabled EPM logging and the client is authenticated via MAB or Webauth, the value of AUTHTYPE is DOT1X in EPM syslog messages irrespective of the authentication method.
Similarly, the show epm sessions command always displays the authentication method as DOT1X.
Workaround: To view the authentication method used for a client, enter the show authentication sessions command. CSCsx42157
With CFM enabled globally as well as on an ingress interface, CFM packets received on the interface are not policed with hardware control plane policing.
Workaround: None. CSCso93282
When either the RADIUS-server test feature is enabled or RADIUS-server dead-criteria is configured, and either RADIUS-server deadtime is set to 0 or not configured, the RADIUS-server status is not properly relayed to AAA.
Workaround: Configure both dead-criteria and deadtime.
radius-server dead-criteria
radius-server deadtime
CSCtl06706
If a large number of VLAN mappings are configured, a member port might fail to join a port channel and no warning is issued.
Workaround: Reduce the number of VLAN mappings. CSCtn56208
If an interface whose IP address is being used as the Router ID is deleted or shuts down and you configure a service group with a multicast group-address, packet redirection to CE stops and packets are forwarded directly to the destination.
Workaround: Unconfigure and reconfigure the service group. CSCtn88087
When a sampling monitor is configured on a routed port or on a VLAN (an SVI with just one port as a member) and bidir multicast is enabled, a packet sample may be exported even though the original multicast packet was not forwarded by the switch.
This issue only impacts Catalyst 4948E and Catalyst 4948E-F Ethernet Switches.
Workaround: None. CSCtk97612
Global WCCP service configuration fails to enable (WCCP global config is accepted but nvgen fails) on a newly deployed switch if the switch is not enabled for SVI or a Layer 3 interface.
Workaround: Enable a Layer 3 interface in the running config. CSCsc88636.
When you enter the ip pim register-rate-limit command, the following error message displays:
'Failed to configure service policy on register tunnel' and 'STANDBY:Failed to configure service policy on register tunnel'.
Workaround: None. The ip pim register-rate-limit command does not function. CSCub32679
For packets with the same ingress and egress Layer 3 interface, ingress QoS marking policy does not work.
Workaround: Turn off ICMP redirect through the ip redirect command. CSCua71929
While configuring an IPv6 access-list, if you specify hardware statistics as the first statement in v6 access-list mode (i.e. before issuing any other v6 ACE statement), it will not take effect. Similarly, your hardware statistics configuration will be missing from the output of the show running command.
You will not experience this behavior with IPv4 access lists.
Workaround: During IPv6 access-list configuration, configure at least one IPv6 ACE before the "hardware statistics" statement. CSCuc53234
When an IPv6 FHS policy is applied on a VLAN and an EtherChannel port is part of that VLAN, packets received by EtherChannel (from neighbors) are not bridged across the local switch.
Workaround: Apply FHS policies on a non EtherChannel port rather than a VLAN. CSCua53148
Memory allocation failures can occur if more than 16K IPv6 multicast snooping entries are present.
Workaround: None. CSCuc77376
For any configuration where the source-interface keyword is used, if you provide an SVI that is associated with a secondary private VLAN, configuration involving the secondary VLAN may be lost when the switch is reloaded. In such scenarios, always use the primary private VLAN.
When a logging discriminator is configured and applied to a device, memory leak is seen under heavy syslog or debug output. The rate of the leak is dependent on the quantity of logs produced. In extreme cases, the device may crash. As a workaround, disable the logging discriminator on the device (CSCur45606, CSCur28336).
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.
For the latest information on PSIRTS, refer to the Security Advisories on CCO at the following URL:
The Bug Search Tool (BST), which is the online successor to Bug Toolkit, is designed to improve the effectiveness in network risk management and device troubleshooting. The BST allows partners and customers to search for software bugs based on product, release, and keyword, and aggregates key data such as bug details, product, and version. The tool has a provision to filter bugs based on credentials to provide external and internal bug views for the search input.
To view the details of a caveat listed in this document:
Cisco Catalyst 4000 Series SwitvhesSUP8E VSS active crash due to signr 11 when OIR standby SUP8E.
Resolved Caveats for Cisco IOS Release 15.2(4)E
Bug ID
Headline
CSCus13924
Device crashes while configuring 'Identity' commands
CSCuu83085
Memory leaks @ AAA Account Response.
CSCuu92224
2960X - EPM vlan plugin crash
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:
Guides—The Catalyst 4900M, Catalyst 4948E, Catalyst 4948E-F Series Switches, Catalyst 4500 Series Switches, the Catalyst 4500-X Series Switches, and the Catalyst 4500-E Series Switches, leverage the same software configuration guide, command reference guide, and system message guide:
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.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)”.
4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
“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).
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. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
“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. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: “This product includes software written by Tim Hudson (tjh@cryptsoft.com)”.
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:
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.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0711R)