Specifications

43
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(10)
Interfaces and Bridging
• CSCdp40908
A Cisco PA-A1 port adapter does not automatically switch to the internal clock during LOS (Loss
of Signal) condition. There is no workaround.
• CSCdp40929
A Cisco PA-A1 port adapter does not detect the Loss of Cell Alignment (LOCA) error. There is no
workaround.
• CSCdp51752
In Cisco 7100 and 7200 series routers, transparent bridging using the PA-DTR Token Ring Port
Adapter does not operate properly. The show bridge command fails to indicate any of the
end-stations in the bridge table.
Workaround: On the Cisco 7200 series routers, use alternative token ring port adapters. There are
no known workarounds for the Cisco 7100 series routers.
IP Routing Protocols
• CSCdm80672
A Cisco router may experience a bus error and reload when you enter the ip accounting
output-packets command. There is no workaround.
• CSCdp30454
The dataless header register does not work properly in Cisco IOS Release 12.0(7)S. There is no
workaround.
• CSCdp49682
A Cisco 827 router might reload or experience spurious access in iprouting_destination_valid. The
spurious access is caused by reading an invalid location, so memory is not corrupted. There is no
workaround.
• CSCdp68820
Sources of multicast packets that send at a low frequency might have their (S,G) expire in the
first-hop designated router (DR). The corresponding (S,G) might also expire in the rendezvous
point (RP).
If the (S,G) state is later created from a Protocol Independent Multicast (PIM) Join packet from
downstream, then the register flag is not set for this (S,G) in this router. If a packet is then received
from the source, the register packet will not be sent to the RP so the A-flag for the (S,G) will not
be set in the RP, which would prevent the subject source from being advertised to the Multicast
Source Discovery Protocol (MSDP) peers. There is no workaround.
• CSCdp72071
When the Protocol Independent Multicast (PIM) designated router (DR) changes, the F flag is not
changed. This situation might then cause header registers either not to be sent to the Route
Processor (RP) or to be duplicated.
Workaround: If the router is configured for multicast and the group is sparse mode, use the clear
ip mroute {s, g} EXEC command to fix the F flag.