Specifications

Caveats for Cisco IOS Release 12.0

78-6455-12

Resolved Caveats—Cisco IOS Release 12.0(5)

• CSCdm11467

When utilizing Network Time Protocol (NTP) private mode and control type messages for remote

query, a router might reload or you might see traceback messages. There is no workaround.

• CSCdm13269

If you configure the 128-kbps leased line on a Cisco 1003 router, and the router runs Cisco IOS

Release 12.0(3), the following message might appear when the router boots:

ASSERTION FAILED: file “../src-36/quicc_driver_lib.c”, line 215

In this situation, the feature does not work. There is no workaround.

• CSCdm13937

A router might reload with a software-forced error if syslog SNMP traps are enabled and no

additional dynamic memory is available on the router. The following message is displayed:

%SYS-2-FREEBAD: Attempted to free memory at DEADBEEF, not part of buffer pool

%SYS-2-FREEFREE: Attempted to free unassigned memory at 61955EE4, alloc 60655D14,

dealloc 60650288 %SYS-6-BLKINFO: Attempt to free a block that is in use blk 61955EBC,

words 62, alloc 60655D14, Free, dealloc 60650288, rfcnt 0

There is no workaround.

• CSCdm16625

The write network command does not work if you issue the tftp-source interface command first.

There is no workaround.

• CSCdm17336

The Hewlett-Packard (HP) Probe subsystem is not included in any Cisco 1600 series images in any

Cisco IOS releases. There is no workaround.

• CSCdm21161

If you use a VIP CE1/TE1 interface you might see “RSP-3-INVRTN” or “RSP-3-NORESTART”

errors, followed by the logging of much debugging information and a switching complex restart.

There is no workaround.

• CSCdm32905

A Cisco MC3810 multiservice access concentrator running Cisco IOS Release 12.0(3)T1 fails to

remove a directly connected route from the routing table when the interface for the network goes

into a “line protocol down” state. This should not be an issue unless you have another route to the

network. There is no workaround.

DECnet

• CSCdk62414

Under certain conditions, DECnet does not send triggered routing updates after an adjacency comes

up. If periodic routing updates are sent out frequently (the default frequency being 40 seconds), this

is not an issue because an update gets sent out in a short time and routes are learned. However, if

the routing update timer has been configured to be a large value, routes might not be learned for a

long time.

Workaround: Configure a smaller value for the routing update timer.