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

Ethernet, switchport block unicast, interface, boot host retry timeout, src-dst-ip, src-ip, dst-ip

Page 8 highlights

Limitations and Restrictions Ethernet - When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1). - When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires. The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708) • When connected to some third-party devices that send early preambles, a switch port operating at 100 Mp/s full duplex or 100 Mp/s half duplex might bounce the line protocol up and down. The problem is observed only when the switch is receiving frames. The workaround is to configure the port for 10 Mp/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091) • When port security is enabled on an interface in restricted mode and the switchport block unicast interface command has been entered on that interface, MAC addresses are incorrectly forwarded when they should be blocked The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822) • A traceback error occurs if a crypto key is generated after an SSL client session. There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331) • When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration. The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command. (CSCsk65142) • Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address. More than one traffic stream might map to same member ports, based on hashing results calculated by the ASIC. If this happens, traffic distribution is uneven on EtherChannel ports. Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing: - for random source-ip and dest-ip traffic, configure load balance method as src-dst-ip - for incrementing source-ip traffic, configure load balance method as src-ip - for incrementing dest-ip traffic, configure load balance method as dst-ip - Configure the number of ports in the EtherChannel so that the number is equal to a power of 2 (for example, 2, 4, or 8) For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal. (CSCeh81991) Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(55)SE and Later 8 OL-22861-04

  • 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

8
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
When the switch is connected to a DHCP server that is configured to give an address to it (the
dynamic IP address is assigned to VLAN 1).
When an IP address is configured on VLAN 1 before the dynamic address lease assigned to
VLAN 1 expires.
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
When connected to some third-party devices that send early preambles, a switch port operating at
100 Mp/s full duplex or 100 Mp/s half duplex might bounce the line protocol up and down. The
problem is observed only when the switch is receiving frames.
The workaround is to configure the port for 10 Mp/s and half duplex or to connect a hub or a
nonaffected device to the switch. (CSCed39091)
When port security is enabled on an interface in restricted mode and the
switchport block unicast
interface
command has been entered on that interface, MAC addresses are incorrectly forwarded
when they should be blocked
The workaround is to enter the
no switchport block unicast
interface configuration command on
that specific interface. (CSCee93822)
A traceback error occurs if a crypto key is generated after an SSL client session.
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch.
(CSCef59331)
When you enter the
boot host retry timeout
global configuration command to specify the amount
of time that the client should keep trying to download the configuration and you do not enter a
timeout value, the default value is zero, which should mean that the client keeps trying indefinitely.
However, the client does not keep trying to download the configuration.
The workaround is to always enter a non zero value for the timeout value when you enter the
boot
host retry timeout
timeout-value
command. (CSCsk65142)
Ethernet
Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports
are distributed to member ports on load balance configuration and traffic characteristics like MAC
or IP address. More than one traffic stream might map to same member ports, based on hashing
results calculated by the ASIC.
If this happens, traffic distribution is uneven on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel
can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:
for random source-ip and dest-ip traffic, configure load balance method as
src-dst-ip
for incrementing source-ip traffic, configure load balance method as
src-ip
for incrementing dest-ip traffic, configure load balance method as
dst-ip
Configure the number of ports in the EtherChannel so that the number is equal to a power of 2
(for example, 2, 4, or 8)
For example, with load balance configured as
dst-ip
with 150 distinct incrementing destination
IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load
distribution is optimal. (CSCeh81991)