Specifications
125
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(3)
DECnet
• CSCdk65997
This problem is specific to the Route Switch Module (RSM) platform and for DECnet over VLANs.
The code for DECnet support over VLANs uses a cache to store VLAN-header information, and
this cache is used in the fast-switch path. When there is a routing topology change, the
fast-switching code continues to look at the stale cache entry, and as a result, packets destined by
way of the new route are black-holed.
Workaround: Disable DECnet fast switching on the relevant interface.
IBM Connectivity
• CSCdk30352
Cross-domain session drops might occur when you configure stun-tg on Cisco routers to connect
two FEPs. At the time the session drop happens, the following error might be reported by the router:
%SYS-2-BADSHARE: Bad refcount in datagram_done may be reported by the router
There is no workaround.
• CSCdk35420
APPN HPR over an ISDN backup line is losing sessions. There is no workaround.
• CSCdk36470
The input queue on the Token Ring interfaces might overflow and accept no additional packets.
Workaround: Increase the input queue of the interfaces (for example, issue the hold-queue 200 in
command), or reload the router.
• CSCdk53603
When running DSPU, certain downstream connections might fail to become active.
Workaround: To get the clients to become active, you need to clear the logical unit (LU) on the host
that has the “PBIND” status. Once this is cleared, the session comes up.
• CSCdk67010
There might be an SDLC DLSw performance problem when you use simultaneous full-datamode
or simultaneous half-datamode. There is no workaround.
• CSCdk68763
The ABM bit is not set on the transmitting DLSw peer during XID exchange. There is no
workaround.
• CSCdk69202
APPN builds fail because of an outdated compiler in the “dlurdepends” make file
(dlurdepend.mak). All APPN images are affected. There is no workaround.
• CSCdk69510
A DLSw router using priority peers might reload when the TCP peer connections fail under heavy
load conditions.
Workaround: Remove the Priority keyword until the issue is resolved.