Configuration
These are the configuration limitations:
•
•
•
•
Ethernet
This is the Ethernet limitation:
•
OL-8918-03
A static IP address might be removed when the previously acquired DHCP IP address lease expires.
This problem occurs under these conditions:
When the switch is booted without a configuration (no config.text file in flash memory).
–
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 Mbps full duplex or 100 Mbps 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 Mbps 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)
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(35)SE and Later
Limitations and Restrictions
7
ページを印刷する