Release Notes for Cisco Catalyst Blade Switch 3120 for HP Cisco IOS Release 12.2(40)EX

Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(40)EX1

OL-12250-01

Limitations and Restrictions

• If the ingress queue has low buffer settings and the switch sends multiple data streams of system

jumbo MTU frames at the same time at the line rate, the frames are dropped at the ingress.

There is no workaround. (CSCsd72001)

• When you use the srr-queue bandwidth limit interface configuration command to limit port

bandwidth, packets that are less than 256 bytes can cause inaccurate port bandwidth readings. The

accuracy is improved when the packet size is greater than 512 bytes. There is no workaround.

(CSCsg79627)

Routing

These are the routing limitations:

• The switch stack might reload if the switch runs with this configuration for several hours, depleting

the switch memory and causing the switch to fail:

–

The switch has 400 Open Shortest Path First (OSPF) neighbors.

–

The switch has thousands of OSPF routes.

The workaround is to reduce the number of OSPF neighbors to 200 or less. (CSCse65252)

• When the PBR is enabled and QoS is enabled with DSCP settings, the CPU utilization might be high

if traffic is sent to unknown destinations.

The workaround is to not send traffic to unknown destinations. (CSCse97660)

SPAN and RSPAN

These are the SPAN and Remote SPAN (RSPAN) limitations.

• When egress SPAN is running on a 10-Gigabit Ethernet port, only about 12 percent of the egress

traffic is monitored.

There is no workaround. This is a hardware limitation. (CSCei10129)

• When the logging event-spanning-tree interface configuration command is configured and logging

to the console is enabled, a topology change might generate a large number of logging messages,

causing high CPU utilization. CPU utilization can increase with the number of spanning-tree

instances and the number of interfaces configured with the logging event-spanning-tree interface

configuration command. This condition adversely affects how the switch operates and could cause

problems such as STP convergence delay.

High CPU utilization can also occur with other conditions, such as when debug messages are logged

at a high rate to the console.

Use one of these workarounds:

–

Disable logging to the console.

–

Rate-limit logging messages to the console. (CSCsg91027)

–

Remove the logging event spanning-tree interface configuration command from the interfaces.

• The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module.

The workaround is to configure aggressive UDLD. (CSCsh70244).