
486
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S14
Conditions: The symptom is observed when all aggregated child routes are marked for deletion and
the periodic function which processes the routes to be deleted deletes the route before the aggregate
processing function gets a chance to process them and the aggregate route to which they belong.
Workaround: Configuring “/jointfilesconvert/415844/bgp aggregate-timer” to 0 or the lowest value would considerably reduce
the chances of hitting this problem. In case this problem does occur, in order to delete the stale
aggregate route, configure a temporary local BGP route (say, redistribute a static route or network
a loopback) with its address being a subnet of the stale aggregate address and then remove the
aggregate address and the added route. This should delete the route from table and send withdraws
to the other routes also.
Further Problem Description: The periodic function is by default called at 60 second intervals. The
aggregate processing is normally done based on the CPU load. If there is no CPU load, then the
aggregate processing function would be triggered within one second. As the CPU load increases,
this function call will be triggered at higher intervals and if the CPU load is very high it could go as
high as the maximum aggregate timer value configured via command. By default this maximum
value is 30 seconds and is configurable with a range of 6-60 seconds and in some trains 0. So, if
default values are configured, then as the CPU load increases, the chances of hitting this defect is
higher.
• CSCsu24425
Symptoms: Standby RP can crash upon boot up.
Conditions: The symptom is observed under the following conditions:
1. “clock timezone ..” is configured.
2. config-register = 0x2142.
3. The router is running Cisco IOS Release 12.0S based code.
Workaround: Use config-register 0x2102 and unconfigure the clock timezone.
• CSCsv27607
Symptoms: BGP router filters outbound routes to the peers when doing soft reset with specifying
peer address using the clear ip /jointfilesconvert/415844/bgp ip-addr soft out command. However, the routes to be filtered
are not deleted from the routing table on the BGP peer router.
Conditions: The symptom happens when removing and then reapplying an outbound route-map.
When issuing the clear ip /jointfilesconvert/415844/bgp neighbor-address soft out command for each peer in an update-group
after applying the outbound route-map filtering policy. The withdraw for filtered prefixes is sent to
the first peer specified in soft reset, but the next peers in the same update-group do not withdraw the
routes.
Workaround: Perform a hard BGP reset using the clear ip /jointfilesconvert/415844/bgp ip-addr command.
• CSCsw50410
Symptoms: The following traceback is seen on the console, and all the channelized serial links on
the E3 LC flap.
SLOT 5:1d00h: %EE48-3-INVALID_CFG_DATA: Channel 4: Invalid configuration
data. Channel type= 5
-Traceback= 40030F00 40417F44 40418208 40418444 404184B4 40418588
SLOT 5:1d00h: %EE48-3-INVALID_CFG_DATA: Channel 5: Invalid configuration
data. Channel type= 5
-Traceback= 40030F00 40417F44 40418208 40418444 404184B4 40418588
Comentarios a estos manuales