HP Cisco Catalyst Blade Switch 3020 Release Notes for the Cisco Catalyst Blade - Page 11

Trunking, VLAN, Device Manager Limitations, Caveats

Page 11 highlights

Limitations and Restrictions Trunking VLAN • The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link [ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber. This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the frame to an IEEE 802.1Q trunk interface. There is no workaround. (CSCdz33708) • IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the output interface for the multicast route entry assigned to the multicast group and an interface in VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no workaround. (CSCdz42909). • For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not counted on the interface statistics. There is no workaround. (CSCec35100). • If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000, the switch can fail. The workaround is to reduce the number of VLANs or trunks. (CSCeb31087) • When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN is within the configured rate limit, the port might go into an error-disabled state. The workaround is to configure the burst interval to more than 1 second. (CSCse06827) Device Manager Limitations • When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not start. The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718) • When the physical UID LED of the switch is on, it is blue. However, when the image of this LED on the device manager Front Panel view is on, it is green. There is no workaround (CSCsd98457). Caveats The following limitations are reported as caveats: • CSCta72141 The bootloader label is incorrect and displays "CISCO DEVELOPMENT TEST VERSION." However, the actual bootloader software is the correct version with the correct functionality. There is no workaround. It does not impact functionality. OL-22861-04 Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(55)SE and Later 11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34

11
Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(55)SE and Later
OL-22861-04
Limitations and Restrictions
Trunking
The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link
[ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber.
This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the
frame to an IEEE 802.1Q trunk interface. There is no workaround. (CSCdz33708)
IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a
member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the
output interface for the multicast route entry assigned to the multicast group and an interface in
VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN
interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is
forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no
workaround. (CSCdz42909).
For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might
appear in the
show interfaces counters
privileged EXEC command output. Valid IEEE 802.1Q
frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the
frames are not counted on the interface statistics. There is no workaround. (CSCec35100).
VLAN
If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000,
the switch can fail.
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN
is within the configured rate limit, the port might go into an error-disabled state. The workaround is
to configure the burst interval to more than 1 second. (CSCse06827)
Device Manager Limitations
When you are prompted to accept the security certificate and you click
No
, you only see a blank
screen, and the device manager does not start.
The workaround is to click
Yes
when you are prompted to accept the certificate. (CSCef45718)
When the physical UID LED of the switch is on, it is blue. However, when the image of this LED
on the device manager Front Panel view is on, it is green.
There is no workaround (CSCsd98457).
Caveats
The following limitations are reported as caveats:
CSCta72141
The bootloader label is incorrect and displays “CISCO DEVELOPMENT TEST VERSION.”
However, the actual bootloader software is the correct version with the correct functionality.
There is no workaround. It does not impact functionality.