Specifications

Caveats for Cisco IOS Release 12.0

78-6455-12

Resolved Caveats—Cisco IOS Release 12.0(12)

Novell IPX, XNS, and Apollo Domain

• CSCdr46313

In Cisco IOS Release 12.0 and 12.1, but not in earlier releases, a Cisco router that is running

Internetwork Packet Exchange-Enhanced Interior Gateway Routing Protocol (IPX-EIGRP) Service

Advertising Protocol (SAP) on unstable WAN links might cause IPX EIGRP SAP packets to remain

in memory, eventually exhausting processor memory.

Workaround: Run Routing Information Protocol (RIP)/SAP instead of EIGRP/SAP on the WAN

links.

TCP/IP Host-Mode Services

• CSCdr18925

Remote source-route bridging (RSRB) data is corrupted when you use the ip tcp

path-mtu-discovery interface configuration command, the IP path changes because of a change in

the IP routing metric values, and the largest workable maximum transmission unit (MTU) changes

from a larger MTU to a smaller MTU given the path change.

Workaround: Disable the PATH MTU discovery algorithm by using the no ip tcp

path-mtu-discovery interface configuration command.

Wide-Area Networking

• CSCdp65239

The input queue on a Cisco 7500 series router might show 76/75, which can result on the line going

down on a High-Speed Serial Interface (HSSI) port adapter even though the VIP console shows that

the queue is empty and the line protocol is up. This condition only occurs when PPP encapsulation

is enabled.

Workaround: Move the card to a new slot, change to High-Level Data Link Control (HDLC), or

reload the router.

• CSCdr28255

A Cisco router might reload with the following error when the frame-relay qos-autosense and

frame-relay traffic-shaping interface configuration commands are configured:

System was restarted by error - an arithmetic exception.

Workaround: Disable frame-relay qos-autosense and configure the shaping parameters manually

instead.

• CSCdr32690

On an access platform, when dialer profiles and virtual profiles are used together with the callback

of some vendors, the virtual profile is not applied to the callback call. There is no workaround.