
642
Caveats for Cisco IOS Release 12.2(33)SRD through 12.2(33)SRD8
OL-10394-05 Rev. R0
Conditions: This issue is observed only for a large number of IP subscriber sessions. While the
traffic is flowing, if user manually requests to clear all the sessions and while that is processing the
line card reboots, then standby RP can get into a state there are dangling sessions. This does not
render the router useless, but increases the sync time from active to standby.
Workaround: There is no workaround.
• CSCsr80601
Symptoms: An ISAKMP SA is not deleted as expected after removing the RSA key.
Conditions: The issue is seen when the user tries to clear the ISAKMP SAs by issuing the clear
crypto session command on an IKE SA that has multiple IPSEC SAs.
Workaround: Use the clear crypto sa and clear crypto is commands.
• CSCsr81271
Symptoms: A Cisco 7600 router with PA-A3-T3 port adapter in flexwan module WS-X6582-2PA
could generate following error messages with tracebacks upon a mass ATM PVCs flap:
SLOT 2/0: %CWAN_ATM-3-VC_OR_PORT_ERR: Invalid VCD FF03 or Port: 0 -Traceback=
403E2200 403A8C1C 40344F88 40347FD0 403481B4 403C374C 401CD170
Slot 2/0 is the slot the port adapter is installed.
Conditions: This seems to only occur when a large number of ATM PVCs flap, most likely from the
service provider side.
Workaround: There is no workaround.
• CSCsr82785
Symptoms: If APS is configured on a large number of channelized sub-interfaces associated with a
single controller such that a single failure can cause all of these interfaces to failover at the same
time, and RIP is configured to run over these interfaces, high sustained CPU usage will be seen
following the failover and reconvergence time will be lengthy.
Conditions: Large number of APS protected interfaces fail over at the same time. RIP is the protocol
running on those interfaces. IP addresses on all interfaces are covered by the same network
statement.
Workaround: There is no workaround.
Further Problem Description: The length of the high CPU and reconvergence period will increase as
the number of impacted interfaces increases.
The length of the high CPU and reconvergence period will also increase as the number of network
statements which cover the IP addresses on the affected interfaces decreases i.e. it will be worst
when a single classful network (e.g. 10.0.0.0) covers all interfaces, somewhat better when multiple
classful networks are impacted.
• CSCsr84639
Symptoms: After 30 minutes, MIB synchronization failure messages appear on primary RP.
Secondary RP crashes.
Occurs under the following scenario:
1) Bringup 1 pppox session on the L2TP network server (LNS)
2) Pass bidirectional traffic through the LNS
3) After 30 minutes, MIB sync failures message appear on primary RP and secondary RP crashes.
Workaround: Enter the no snmp mib notification-log default command.
• CSCsr86515
Komentarze do niniejszej Instrukcji