Cisco Cisco IOS Software Release 12.2(35)SE 릴리즈 노트

The DHCP snooping database file is manually removed from the file system. After enabling the 
DHCP snooping database by configuring a database URL, a database file is created. If the file 
is manually removed from the file system, the DHCP snooping database does not create another 
database file. You need to disable the DHCP snooping database and enable it again to create the 
database file. 

The URL for the configured DHCP snooping database was replaced because the original URL 
was not accessible. The new URL might not take effect after the timeout of the old URL.

No workaround is necessary. (CSCed50819)

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)

These are the Ethernet limitations:

Traffic on EtherChannel ports is not perfectly load-balanced. Outgoing traffic on EtherChannel ports 
is distributed to member ports based on the load balancing configuration and traffic characteristics 
such as the MAC or the IP address. More than one traffic stream might map to same member ports, 
based on hashing results calculated by the ASIC.

If this happens, uneven traffic distribution happens 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 
(i.e. 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)

This is the IP limitation: