Specifications

57
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(8)
• CSCdm40972
When an X.25 interface initially comes up, IP route entries for its subinterfaces (if any) are not
added to the IP routing table.
Workaround: Restart X.25 to cause the subinterface routes to appear.
• CSCdm71463
When “chassisType” is polled on a Cisco 7200 series router, the chassisType OID is returned as
“Unknown.” There is no workaround.
• CSCdp13010
A Cisco router that is running Cisco IOS Release 11.1(28.1)CC and later releases with maximum
transmission unit (MTU) configuration statements might see an unwanted cbus switching complex
restart five minutes after booting. The switching complex restart only occurs if the MTU interface
reconfiguration causes a MEMD recard because of a change in the MEMD buffer size used by the
interface. There is no workaround.
• CSCdp17575
If more than one channel or clock rate is larger than 64kbps, a Cisco MC3810 series multiservice
access concentrator might not set the parity bit for the pointer field in the ATM adaptation layer 1
(AAL1) and generate bit errors. This situation occurs when the Cisco MC3810 series multiservice
access concentrator is supporting T1 circuit emulation service (CES) and is connected to a device
that is not a Cisco MC3810, but does not occur if both devices are Cisco MC3810 series
multiservice access concentrators or if the circuit units are equal to or greater than six timeslots.
There is no workaround.
• CSCdp23703
A Cisco router might reload with a SegV error if you try to log in while the debug callback EXEC
command is enabled.
Workaround: Disable the debug callback EXEC command.
DECnet
• CSCdp00940
If a Cisco router is running a Cisco IOS release earlier than Cisco IOS Release 11.3 and is using
the DECnet Phase IV routing protocol, the DECnet network might experience routing loops for
periods of time up to the value of the argument given in the decnet routing-timer seconds interface
configuration command. These routing loops might start when a network link goes up or down, and
DECnet traffic will be discarded while these loops occur.
Workaround: Reduce the value given in the decnet routing-timer seconds interface configuration
command.
• CSCdp25634
If a Cisco router recognizes a Phase IV VAX cluster, the router will install a route to the cluster
alias and advertise reachability to it across a Phase V attached network. It is possible for a routing
loop to form if cluster aliases stop being advertised and if the two routers are connected in parallel
between Phase IV and Phase V. If the router is the Phase IV designated router for the interface to
which the VAX cluster is attached, there might be some connectivity issues between the VAX
clients and the VAX cluster alias, but individual VAX machines can still be reached.
Workaround: Set another router to be the Phase IV designated router for the LAN.