Installation guide

Release Notes for the Cisco ME 3400 Ethernet Access Switch, Cisco IOS Release 12.2(44)SE

OL-14632-01

Limitations and Restrictions

The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)

• The DHCP snooping binding database is not written to flash memory or a remote file in any of these

situations:

–

When the Network Time Protocol (NTP) is configured, but the NTP clock is not synchronized.

You can check the clock status by entering the show NTP status privileged EXEC command

and verifying that the network connection to the NTP server and the peer work correctly.

–

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; these are the designed behaviors. (CSCed50819)

• When dynamic ARP inspection is enabled on a switch, ARP and RARP packets greater than 2016

bytes are dropped by the switch or switch stack. This is a hardware limitation.

However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and

RARP packets are correctly bridged in hardware. (CSCed79734)

• Dynamic ARP inspection log entries might be lost after a switch failure. Any log entries that are still

in the log buffer (have not been output as a system message) on a switch that fails are lost.

When you enter the show ip arp inspection log privileged EXEC command, the log entries from all

switches in the stack are moved to the switch on which you entered the command.

There is no workaround. (CSCed95822)

• 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)

EtherChannel

This is the EtherChannel limitation:

• The switch might display tracebacks similar to this example when an EtherChannel interface

port-channel type changes from Layer 2 to Layer 3 or the reverse:

15:50:11: %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Port-channel1

(ifindex 1632) -Traceback= A585C B881B8 B891CC 2F4F70 5550E8 564EAC 851338 84AF0C

4CEB50 859DF4 A7BF28 A98260 882658 879A58

There is no workaround. (CSCsh12472)