
662
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
Symptoms: The SP crashes when the device receives an IP address from the DHCP server. The
following error message is displayed:
Signal = 11 Vector = 0x1400
Conditions: Occurs on a Cisco Catalyst 6500 with RSP720-3C-GE when the ip verify source vlan
dhcp-snooping is enabled.
Workaround: There is no workaround.
• CSCsv99716
Symptoms: A Cisco 10000 series router may crash at issu_print_memory while doing a loadversion.
Conditions: The symptom is observed on a Cisco platform, when enabling the debug command
debug issu all in the router and doing a loadversion.
Workaround: Do not turn on ISSU debug.
• CSCsw14845
Symptoms: An access-list with multiple ports in a single entry only programs the first port into
TCAM. All subsequent ports are are not processed according to the access-list entry.
For example, the following access-list should block both SSH (TCP port 22) and Telnet (TCP port
23), but Telnet is permitted.
ip access-list extended deny_ssh_and_telnet deny tcp any any eq 22 telnet permit ip any any
Conditions: Occurs when there is an extended named access-list with multiple ports in a single
access-list entry. This only applies to transit traffic since traffic destined to the router is
process-switched and processed in software.
Workaround: There is no workaround.
• CSCsw16698
Symptoms: New DHCP clients are not able to get IP address from DHCP server via DHCP relay on
the router. Existing clients are unable to renew their IP addresses
Other Symptoms:
1.1 When we’re trying to display DHCP bindings with "show ip dhcp binding" command the
following message is observed:
% The DHCP database could not be locked. Please retry the command later.
1.2 Command "ip dhcp database" dissapeared from the running configuration.
1.3 Output of "show run" is delayed.
1.4 Output of "debug ip dhcp events" show the following when a new DHCP packet is received:
DHCPD: dhcpd_receive_packet: unable to lock semaphore to check for pre-existing bindings could
not lock se. DHCPD: dhcpd_timer_process could not lock semaphore. DHCPD:
dhcp_server_receive could not lock semaphore.
2.1. This bug may also cause DHCP Snooping failure. In this case, the output of the show ip dhcp
snooping database command constantly shows these lines:
Agent Running : Yes Delay Timer Expiry : 0 (00:00:00) Abort Timer Expiry : Not Running
Conditions: Occurs when DHCP and/or DHCP Snooping database agent is configured to store
bindings on a TFTP server, and then the database files are not present or are read-only for some time
on TFTP server while the router tries to write to them.
Workaround: Before the issue occurs, there are three known alternatives to avoid this problem:
1. Either configure ’length 0’ for line console 0;
Komentáře k této Příručce