Specifications

Release Notes for Cisco IOS Release 12.0 S

78-7130-11 Rev. B0

Caveats

• CSCdr59243

A Cisco 7500 series router with a PA-CT3 port adapter that has been channelized down to a T1

might exhibit the following error messages on any of the channelized interfaces:

%RSP-3-RESTART: cbus complex

%RSP-3-RESTART: interface Serial5/0/0:1, output stuck

In this condition, the channelized interfaces might enter a down/down state.

Workaround: Reload the router.

• CSCdr77460

When an online insertion and removal (OIR) is performed, the IF-MIB ifTable, ifStackTable, and

ifNumber retains the old entries even though the associated interface layers have been removed.

There is no workaround.

Interfaces and Bridging

• CSCdr16853

A single Packet-over-SONET (POS) port adapter in a Cisco 7500/RSP series router with a Versatile

Interface Processor 4 (VIP4) might stop transmitting and cause an “output stuck” condition. A POS

port adapter that is a coresident with another port adapter in a Versatile Interface Processor 2 (VIP2)

might also cause an “output stuck” condition for itself or the coresident port adapter. There is no

workaround, but disabling distributed Cisco Express Forwarding (dCEF) globally, or in some

conditions on the POS interface, will stop this condition from appearing.

IP Routing Protocols

• CSCdr45483

A Cisco router with multicast configured might reload with a bus error if there are severe unicast

route updates. There is no workaround.

• CSCdr88511

A Cisco router that is running Cisco IOS 12.0(10.6)S2 or later releases might not install default

routes that are advertised though type 5 link-state advertisements (LSAs) by other routers. This

condition occurs when the Cisco router has only type 5 default LSAs and no nondefault type 5

LSAs are present in the database.

Workaround: Add a nondefault external LSA to the database.

Miscellaneous

• CSCdm87756

In a network where there are multiple paths between two networks and the paths travel through

different sets of routers between these networks, per-destination load balancing will not be effective

in any router after the first router where the load balancing paths diverge.

Workaround: Use per-packet load balancing.