
491
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
–
Then remove the interface via “no int loopback”.
• CSCsx20659
Symptoms: There is a ping failure on an ES-20 line card.
Conditions: The symptom is observed when booting while the ICC mechanism is busy.
Workaround: Perform a shut/no shut on the interface, after booting up.
• CSCsx27496
Symptoms: Router may crash with an address error in the BGP function.
Conditions: The symptom is observed when the router is configured for BGP and traffic is passing.
Workaround: There is no workaround.
• CSCsx39263
Symptoms: After an SSO, TCP Intercept entries in TCAM are not programmed correctly. As a
result, TCP packets are not punted to software and thus Netflow entries are not installed.
Conditions: The symptom is observed when TCP Intercept is already configured when the standby
comes up. Also, at least two switchport interfaces are present in the router.
Workaround: Remove the TCP Intercept configuration and then reconfigure it.
• CSCsx46854
Symptoms: Tracebacks are seen from the interrupt scheduler due to a process suspension.
Conditions: The symptom is observed when changing the IMA group and trying to remove the
ATM/IMA interface.
Workaround: There is no workaround.
• CSCsx55672
Symptoms: Client fails to get an IP address when it sends a subscription request to the UUT on
which a DHCP-initiated IP subscriber session is configured.
Conditions: The symptom is observed when the server is configured with a “Subscriber IP Address
Assignment Using DHCP” based ISG session. When the client requests an IP address by sending
the subscription request, it fails to negotiate a valid address from the DHCP pool configured on the
server.
Workaround: There is no workaround.
• CSCsx57711
Symptoms: On a router configured with BGP VPNs, VRF removal may not work properly. VRF can
remain in delete-pending state or BGP may crash at a later time.
Conditions: The symptom is observed when the router is configured with one or more VRFs and has
the BGP VPN address family enabled. The problem may be triggered by the deletion of a VRF from
the router configuration through the no ip vrf or the no vrf definition commands. The issue is a race
condition in the BGP code that deals with VRF net deletion and cleanup. Hitting the issue becomes
more likely in large scale setups in terms of the number of configured VRFs and the number of nets
in the BGP VPN table.
Workaround: Make sure that all the nets in the BGP VPN table belonging to the VRF are deleted
before issuing the VRF deletion command. To delete all the nets belonging to the VRF:
1. All BGP CE neighbor configuration for that VRF must be removed.
2. Any redistribution of routes into BGP for that VRF must be deconfigured.
3. The import route-targets for the VRF must be removed.
Komentarze do niniejszej Instrukcji