Specifications

102
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(5)
devices are trying to reach this network. If services are associated with this network, they time out
of the service table, and SAP entries received for these services are rejected due to the “no network
found” as seen with debug ipx sap event.
Workaround: Clear the specific route entry using the
clear ipx route {network[network-mask]|default|*} command, or clear the entire route table using
clear ipx route.
• CSCdk44520
IPX EIGRP will not see its neighbor when running over virtual templates. If you configure an IPX
numbered interface and ipx ppp-client lo x, IPXCP comes up but not the IPX EIGRP adjacency.
Workaround: Use the interface multilink command, which is in Cisco IOS Release 12.0 T.
• CSCdm12190
In redundantly connected networks that run IPX-EIGRP, some obsolete IPX services might not age
out and cause a “SAP loop” when ipx maximum-paths is set to a value greater than one. This is
seen primarily with network connected IPX printers whose SAP service hopcount is one more than
that of the route (network) to the service.
Workaround: Temporarily “down” the network to the service. Also, set ipx maximum-paths to
one, which is the default to prevent future recurrences. Another potential workaround is to issue the
ipx server-split-horizon-on-server-paths command. By default, split horizon blocks a router
from advertising periodic SAP information to the interface on which the best route to that SAP is
learned. But in the case where the SAP might be learned from interfaces other than (or in addition
to) the interface on which the best route to that SAP is learned, enabling ipx
server-split-horizon-on-server-paths will reduce unnecessary periodic SAP updates. SAP will
not be advertised to the interface from which it was learned. This will also prevent a potential “SAP
loop” in the network.
• CSCdm21357
Under certain conditions, IPX-EIGRP is leaking memory by way of “IPX USV” and “IPX SAP
PH.” The condition is likely to occur when there are slow or congested WAN links with a large
number of IPX services (SAPs) being advertised, and where IPX-EIGRP neighbors are flapping.
This is evident by the constant short “Uptime” and constant non-zero “Q Cnt” from the
show ipx eigrp neighbors command.
Workaround: Increase the interface bandwidth with the bandwidth n command, or increase the
EIGRP bandwidth for that interface with the ipx bandwidth-percent eigrp as-number percent
command. By default, EIGRP gets the maximum of 50 percent of the interface bandwidth.
Protocol Translation
• CSCdk67438
When you run Cisco IOS Release 11.3, and use TCP to X.25 PVC protocol translation, it is possible
that the PVC will close too quickly. This could potentially cause the PVC to be taken down
prematurely causing some data to be lost. When you print over TCP to X.25 PVC protocol, the
translation might experience a loss of the last data blocks. There is no workaround.