Specifications

106
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(5)
• CSCdm19619
PPP is put into an “AUTHENTICATING” phase if virtual private dialup network (VPDN)
authorization fails. This condition did not exist prior to Cisco IOS Release 12.0(3)T when VPDN
is entered only if PPP is in “AUTHENTICATING” phase.
Workaround: Restore the PPP phase after the VPDN authorization failure.
• CSCdm22162
STAC compression LZS DCP gets stuck in an “R-Req” loop. This problem occurs with Cisco IOS
Release 11.1 or Release 11.2 hardware compression with an RSP on one end of a connection and
Release 11.3 or Release 12.0 software compression on the other.
Workaround: Disable compression if you are using a Cisco 7500 series router. If you are using a
router without an RSP, use software instead of hardware compression on both sides of the
connection, or disable compression.
• CSCdm26875
Deconfiguring an ISDN interface can result in a bus error or spurious access. There is no
workaround.
• CSCdm31907
A LANE subinterface that is shut down might be reported as “Active” from an HSRP perspective.
There is no workaround.
• CSCdm32526
A Cisco router might not be able to pass traffic while using HDLC encapsulation or if STAC
compression is enabled. This problem is caused by board encapsulation when setting the
compression notification bit in the HDLC header. This is only a problem with high-end routers.
Workaround: Disable compression.
• CSCdm33448
If you have a Telematics router connected to one serial interface of a Cisco 7513 router running
Cisco IOS Release 12.0(4.0.2)T1, with a second Cisco 7513 router running Release 11.2 connected
to the first router’s other serial interface by way of an X.25 hunt-group, the Cisco 7513 router
running Release 12.0(4.0.2)T1 will act as an X.25 switch. If the Cisco 7513 router running
Release 11.2 is reloaded, the Cisco 7513 router running Cisco IOS Release 12.0(4.0.2)T1 will also
reload. There is no workaround.
• CSCdm38212
Outgoing calls fail on Cisco routers with PRI interfaces when the switch is NI2. There is no
workaround.