
380
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(33)S6
Alternate Workaround: Configure primary and backup NFAS members on a PA-VXC port adapter
and do not configure NFAS members on the PA-MCX port adapter.
• CSCsa58277
Symptoms: All packets toward a specific adjacency get black-holed. The output of show controllers
rewrites command on the output E4 linecard indicates that a bad destination MAC is being used for
the rewrite.
For example:
LC-Slot1# show controllers rewrites | b 192.168.2.1
Port-channel2 192.168.2.1 0x0E0307CC GigabitEthernet1/2/1 00E0812B28E5000E393CF5010800
------------ incorrect
Conditions: This symptom is observed on a Cisco 12000 series Internet router that is running
Cisco IOS Release 12.0(30)S and that is connected via a link-bundling interface (E4 LC) through a
switch to numerous BGP peers, after one of the peers went down because of a long maintenance
window.
Workaround: Clearing the adjacencies does not help; the only workaround possible is to remove
link-bundling.
• CSCsd95545
Symptoms: Long unconfiguration times are seen for very large QoS configurations (in excess of
40,000 policy maps).
Conditions: This symptom is observed in Cisco IOS Releases 12.2SB and 12.4T.
Workaround: There is no workaround.
• CSCsi61988
Symptoms: On a Cisco 12000 series router that is running Cisco IOS Release 12.0(31)S6, a Malloc
failure is seen on “L3 Engine: 6 - Backbone 2P OC192/ 8P OC48 (20 Gbps)”:
SLOT 10:Mar 29 12:41:01: %SYS-2-MALLOCFAIL: Memory allocation of 65556 bytes failed
from 0x400DD7C8, alignment 32 Pool: Processor Free: 152456 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool
Conditions: Multicast should be enabled because the memory leak happens from “MDFS LC
Process.”
Workaround: Reload the linecard.
• CSCsk35688
Symptoms: Aggregate routes are not processed if all aggregated child routes are deleted
prematurely.
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,
Kommentare zu diesen Handbüchern