Specifications

Caveats for Cisco IOS Release 12.0

78-6455-12

IP Routing Protocols

%STANDBY-6-STATECHANGE: Standby: 1: Ethernet3/5 state Standby - > Active

%CBUS-4-RSETFAIL: Interface Ethernet3/5 failed to reset properl y in

cbus_mci_record_ether_address(), code 0x8010

There is no workaround.

• CSCds37758

On a Cisco router that is running Cisco IOS Release 12.1(4.2) or a later release, Intermediate

System-to-Intermediate System (IS-IS) will fail to form an adjacency over a 16 MB Token Ring

link.

Workaround: Set the Connectionless Network Service (CLNS) maximum transmission unit (MTU)

size to 4461 on the Token Ring interfaces by entering the clns mtu 4461 interface configuration

command.

• CSCds44777

On a Cisco 7500 series router running Cisco IOS Release 12.0(7)T or 12.0(10) with Port Adapter

4T+ (PA-4T+), Fast Serial Interface Processor (FSIP), or Port Adapter 8T (PA-8T), Dedicated

Token Ring (DTR) Port Adapter does not drop and continuously pulses according to the configured

pulse-time x interface configuration command time intervals. Also, on FSIP and PA-4T+ the

RSP-3-RESTART message appears right before a router has to be rebooted to recover a serial

interface from a circuit outage that was configured for pulse-time x interface configuration

command. There is no workaround.

• CSCds45168

After a development engineer (DE) special is applied on Cisco IOS Release 12.0 (12) that

integrated CSCds07197, problems occur with Tip/Ring (T/R) network applications. End-to-End

Systems Network Architecture (SNA) applications fail with link failures. Sniffer traces show a

frame larger than 4472. There is no workaround.

• CSCds51651

A Cisco 7500 series router may fail due to a software-forced reload if both FRF.9 hardware

compression and weighted fair queuing are configured on the same serial link. There is no

workaround.

IP Routing Protocols

• CSCdp02880

A Route Processor running Cisco IOS Release 12.0 prevents (S,G,RP) “prune” messages from

keeping the (S,G) state alive. This situation occurs when edge routers are running Protocol

Independent Multicast version 1 (PIMv1) and do not perform periodic data-header-registers to the

Route Processor. Interoperability between PIMv2 and PIMv1 may be affected by this problem.

There is no workaround.

• CSCdp05523

If the address range defined in a Network Address Translation (NAT) pool is large, CPU utilization

may rise to 100 percent. If a large number of translations are still in the NAT table showing large

expiration timeout values, then the entries were not exited properly.

Workaround: Specifically putting a reduced TCP translation timeout (20 to 30 minutes) has shown

improvement. Apparently there are a lot of TCP translations that were not exited properly and the

default timeout of 24 hours would leave these translations hanging. Reducing the translation

timeout clears the entries earlier. Split the address range into smaller ranges, and define more NAT

pools.