Specifications

Caveats for Cisco IOS Release 12.0

78-6455-12

Resolved Caveats—Cisco IOS Release 12.0(7)

Protocol Translation

• CSCdm69108

TCP to X.25 permanent virtual circuit (PVC) translation might fail and cause the connection to be

lost. There is no workaround.

Wide-Area Networking

• CSCdj39383

A Cisco router with over 180 data-link connection identifiers (DLCIs) cannot boot properly

because of excessive console log messages related to the startup of Frame Relay PVCs. There is no

workaround.

• CSCdm28510

Adding the dialer isdn short-hold command to the map-class dialer command to optimize ISDN

costs based on AOC-D messages might break the “dialer idle-timeout” configuration. The idle

timer resets to 4294966 seconds when expiring, and does not disconnect the ISDN call. The

short-hold timer gets incremented on receipt of an AOC-D message, and never disconnects the

ISDN call.

Workaround: Remove the dialer isdn short-hold command from the map-class dialer command.

• CSCdm41493

A Cisco 2600 series router that is running Cisco IOS Release 11.3(9)T might reload during an

X.25-to-TCP translation.

Workaround: Disable the “pt-vty-logging” service by issuing the no service pt-vty-logging

command.

• CSCdm46082

Multilink PPP does not work if Context-Based Access Control (CBAC) and Network Address

Translation (NAT) configured on a Cisco 3600 series router.

Workaround: Turn off Multilink PPP.

• CSCdm46683

A Versatile Interface Processor (VIP) card might not respond to a RSP board’s request for a DBUS

transaction. The RSP will reset the VIP interface and perform a CBUS complex restart to reallocate

MEMD.

Workaround: Get in and out of the if-console for all the VIPs in the box.

• CSCdm49685

After you reload a Cisco router, the ATM interfaces might assume the default User-Network

Interface (UNI) value (3.0) despite the actual configuration.

Workaround: Reset the interface by entering the shutdown command followed by the no shutdown

command.

• CSCdm52953

If you enable interleaving on a multilink interface, packets may be reordered when they are

transmitted on the interface. The next packet to transmit might not be correctly selected from

multiple conversational streams on the interface, and packets from the same stream could be

rearranged. There is no workaround.