Release Notes

Release Notes for the Catalyst 4500E Series Switch, Cisco IOS XE Release 3.3.xSG

OL-26675-02

Limitations and Restrictions

These sections list the limitations and restrictions for the current release of Cisco IOS software on the

Catalyst 4500E series switch.

• Starting with Release IOS XE 3.3.0SG and IOS 15.1(1)SG, the seven RP restriction was removed.

• The WS-X4712-SFP+E module is not supported in the WS-C4507R-E or WS-C4510R-E chassis

and does not boot. This module is supported in the WS-C4503-E, WS-C4506-E, WS-C4507R+E,

and WS-C4510R+E chassis.

• More than 16K QoS policies can be configured in software. Only the first 16K are installed in

hardware.

• Adjacency learning (through ARP response frames) is restricted to roughly 1000 new adjacencies

per second, depending on CPU utilization. This should only impact large networks on the first

bootup. After adjacencies are learned they are installed in hardware.

• Multicast fastdrop entries are not created when RPF failure occurs with IPv6 multicast traffic. In a

topology where reverse path check failure occurs with IPv6 multicast, this may cause high CPU

utilization on the switch.

• The SNMP ceImageFeature object returns a similar feature list for all the three license levels (LAN

Base, IP Base, and EntServices). Although the activated feature set for a universal image varies

based on the installed feature license, the value displayed by this object is fixed and is not based on

the feature license level.

• Standard TFTP implementation limits the maximum size of a file that can be transferred to 32 MB.

If ROMMON is used to boot an IOS image that is larger than 32 MB, the TFTP transfer fails at the

65,xxx datagram.

TFTP numbers its datagrams with a 16 bit field, resulting in a maximum of 65,536 datagrams.

Because each TFTP datagram is 512 bytes long, the maximum transferable file is 65536 x 512 = 32

MB. If both the TFTP client (ROMMON) and the TFTP server support block number wraparound,

no size limitation exists.

Cisco has modified the TFTP client to support block number wraparound. So, if you encounter a

transfer failure, use a TFTP server that supports TFTP block number wraparound. Because most

implementations of TFTP support block number wraparound, updating the TFTP daemon should fix

the issue.

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