Specifications

118
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(4)
• CSCdm06225
Connectivity problems occur in Virtual Profile situations with a combination of V.120 and native
sync-ISDN calls on a Cisco AS5800 access server. A dial-up interface, which last had an incoming
V.120 call, can a have problem getting packets across on subsequent calls. This condition occurs if
a AAA per-user configuration containing downloaded interface packet filter (access lists) is
applied. There is no workaround.
• CSCdm06448
A PA-A2 port adapter CES part microcode download might fail during bootup. The result is that
the port adapter is invisible to the Cisco IOS software.
Workaround: Reboot the router.
Novell IPX, XNS, and Apollo Domain
• CSCdk81350
If ipx down is configured at the command prompt and ipx down is read out of the configuration
file at bootup, an IPX route to a directly connected network appears in the routing table. In this
situation, new routes to the directly connected network will not be learned, and the network might
appear as “down” in the routing table.
Workaround: Bring up the interface by removing the ipx down command, then reissue the
ipx down command.
• CSCdk86872
If an interface is administratively down with an IPX network configured, and you proceed to add
that network to the IPX EIGRP router, that network (route) gets propagated through EIGRP even
though that interface is “down.” The route does not go away.
Workaround: To remove the network (route) from EIGRP, issue the no shut command follow by
the shut command. Alternatively, remove the network from within the IPX EIGRP router (for
example, issue the ipx router eigrp as and no network net commands).
• CSCdm00033
If IPX NLSP RIP OFF is configured and therefore NLSP RIP compatibility mode is off, a reply is
not sent to a client who sends a RIP general query, a request for all networks.
Workaround: Do not to configure IPX NSLP RIP OFF, but leave compatibility mode enabled.
VINES
• CSCdm09771
A VINES “proxy” memory leak can occur in a router environment where a VINES client
application causes a router to act as a proxy server when the client sends service requests directly
to a router that it does not support. The router becomes a proxy server when it forwards these same
service requests to the nearest Banyan VINES server. The leak can be detected by observing the
persistent “Vines Proxy” lines from the output of the show mem sum command:
0x60433E38 24 2807 67368 Vines Proxy 0x60433E38 28 5246 146888 Vines Proxy
There is no workaround.