Cisco Cisco IOS Software Release 12.2(58)SE
9
Release Notes for the Cisco IE 3000 Switch, Cisco IOS Release 12.2(58)SE1 and Later
OL-24335-02
Limitations and Restrictions
•
When connected to some third-party devices that send early preambles, a switch port operating at
100 Mb/s full duplex or 100 Mb/s half duplex might bounce the line protocol up and down. The
problem is observed only when the switch is receiving frames.
100 Mb/s full duplex or 100 Mb/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 Mb/s and half duplex or to connect a hub or a
nonaffected device to the switch. (CSCed39091)
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
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)
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)
(CSCef59331)
•
The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module.
The workaround is to configure aggressive UDLD. (CSCsh70244)
•
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.
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)
host retry timeout timeout-value command. (CSCsk65142)
•
On a switch running both Resilient Ethernet Protocol (REP) and Bidirectional Forwarding Detection
(BFD), when the REP link status layer (LSL) age-out value is less than 1 second, the REP link flaps
if the BFD interface is shut down and then brought back up.
(BFD), when the REP link status layer (LSL) age-out value is less than 1 second, the REP link flaps
if the BFD interface is shut down and then brought back up.
The workaround is to use the rep lsl-age-out timer interface configuration command to configure
the REP LSL age timer for more than 1000 milliseconds (1 second). (CSCsz40613)
the REP LSL age timer for more than 1000 milliseconds (1 second). (CSCsz40613)
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 may map to same member ports based on hashing results
calculated by the ASIC.
are distributed to member ports on load balance configuration and traffic characteristics like MAC
or IP address. More than one traffic stream may map to same member ports based on hashing results
calculated by the ASIC.
If this happens, uneven traffic distribution will happen on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel
can resolve this problem.
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
(i.e. 2, 4, or 8)
(i.e. 2, 4, or 8)