Page 536

504

Chapter 9

Troubleshooting Novell Connectivity

Router_C#show ipx routes

Codes: C - Connected primary network, c - Connected
secondary network, S - Static, F - Floating static, L -
Local (internal), W IPXWAN, R - RIP, E - EIGRP, N -
NLSP, X - External, A - Aggregate

s - seconds, u - uses

2 Total IPX routes. Up to 1 parallel paths and 16 hops
allowed.

No default route known.

C D (SAP), To0

E B [297728/0] via D.0000.30e8.6d0f, age 00:02:30, 1u, To0

In addition to network D, this routing table was populated via IPX EIGRP

with network B. Network D is connected to Token Ring 0, and network B
is accessible through router D.0000.30e8.6d0f. There is only one known
route to network B.

NLSP and IPXWAN

NLSP, or NetWare Link Services Protocol, affords network designers and
administrators some advantages over IPX RIP, in the same way that IP RIP
networks benefit by changing to IGRP and EIGRP.

Like IP RIP, IPX RIP supports networks of no more than 15 hops. NLSP

expands the routing diameter to 127 hops. In addition, NLSP's link state
packets, LSPs, are sent only when there are changes to the routing topol-
ogy--unlike IPX RIP packets, which are sent every 60 seconds. This greatly
reduces the impact of updates on slower WAN links. Cisco routers automat-
ically redistribute information learned from NLSP to IPX RIP on non-NLSP
segments. It is important to use care when using NLSP on a non-WAN point-
to-point link, because NLSP-only segments do not contain the IPX RIP infor-
mation needed for non-NLSP resources.

NLSP provides the capability to remove IPX SAP from a network segment

by handling updates via NLSP. The protocol reduces both IPX RIPs and
SAPs by sending updates on changes to the database, rather than updating
every 60 seconds. NLSP also requires use of the ipx internal-network
command, unlike IPX RIP and IPX EIGRP.

To enable NLSP, type the ipx nlsp enable command. This is configured

on each interface that will run NLSP. If there are routing problems and the

www.sybex.com