Specifications

101
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(5)
• CSCdm29693
The “cmCallDuration” variable returns wrong values for timeticks. When compared with system
up-time, this variable increases 10 times faster for a call that is in progress during a period of
50 timeticks. There is no workaround.
• CSCdm30609
Cisco routers that originate a L2F or L2TP packet over an ISL interface might reload.
Workaround: Turn off fast switching.
• CSCdm30788
Catalyst 5000 RSM modules that experience spurious error interrupts might cause a C5IP to take a
fatal error. The symptoms of this condition are a C5IP error message indicating no status in the
cause register and an exception dump. The RSM will recover the C5IP automatically within 30
seconds. There is no workaround.
• CSCdm31643
A Cisco 3620 or Cisco 3640 router running Cisco IOS Release 12.0(3) or Release 12.0(4) with
NM-1ATM-25 will output corrupt packets when the router is transmitting packets of various sizes
over an ATM PVC. When received at the other end of the PVC, the packets will generate cyclic
redundancy checks (CRC) errors for every packet received. The packet sizes that fail are multiples
of 48 bytes (ATM cell payload). All pings fail between the Cisco 3620 and other ATM attached
devices if either side initiates an extended ping with a size of 128, 176, or 204 bytes. For every ping,
a CRC error is seen on the ATM interface of the receiving device. When the router is pinged from
a SUN workstation with 100-, 148-, or 196-byte pings, all pings will fail. Pinging to and from the
router with any other ping packet size is successful. There is no workaround.
• CSCdm31647
If you reset a VIP card in slot 8 of a Cisco 7513 router, the VIP might reload. When the VIP comes
up, the ISL trunking to slot 4 (PA-2FEISL-TX) might drop large packets. Small packets go through
the interface properly.
Workaround: Reload the router.
• CSCdm31778
After a Cisco router reloads, or after CEF is enabled, the router might receive entries for the
interface IP address that are not in the CEF table. The CEF interface might be marked as “down”
even though the interface is “up.” This causes packets that are destined to the router to be dropped,
or transit packets to be dropped due to incomplete adjacency. There is no workaround.
Novell IPX, XNS, and Apollo Domain
• CSCdk44289
On rare occasions, a network can be active in the RIP table and be displayed in the show ipx route
display, but be unreachable. This condition occurs when most routes are learned through a specific
interface or neighbor that goes down long enough to occupy the majority of the route reach
hold-down time (4 minutes). If the neighbor or route comes back before the route is removed from
the table, there is a chance that some of the routes might be active but unreachable. A symptom of
this is a “uses” counter of zero on the output of the show ipx route detailed command, even though