To enable EIGRP for IPX, perform the
following steps:
- Enable IPX routing.
router(config)#
ipx routing
- Define EIGRP as the IPX routing
protocol.
router(config-router)#
ipx
router {eigrp autonomous-system-number | rip}
If IPX EIGRP is selected, an autonomous system number must be
specified. This number must be the same for all IPX EIGRP routers in
the network. Figure
- 
- Indicate which networks are part of
the EIGRP autonomous system.
router(config- ipx-router)#
network
network-number
- (Optional) If IPX RIP is also
operating on the router, remove RIP from the networks using EIGRP by
going to the router rip configuration entry and doing the following:
router(config- ipx-router)#
no
network network-number
By default, Cisco routers redistribute
IPX RIP routes into IPX EIGRP, and vice versa. When routes are
redistributed, a RIP route to a destination with a hop count of 1 is
always preferred over an EIGRP route with a hop count of 1. This ensures
that the router always believes a Novell IPX server over a Cisco router
for internal IPX networks. (The only exception to this rule is if both
the RIP and EIGRP updates were received from the same router. In this
case, the EIGRP route always is preferred over the RIP route when the
hop counts are the same.)
Controlling IPX RIP
IPX RIP runs by default when IPX routing is enabled. If a legacy Novell
server is using IPX RIP, a router's LAN interface must also run IPX RIP
to exchange routing information with the server. Because the IPX RIP
routes are redistributed into EIGRP, the router does not need to run IPX
RIP on a serial link to another Cisco router. IPX EIGRP should be used
instead. An administrator can disable IPX RIP on a network-by-network
basis using the no network command, as shown in step 4, above.
EIGRP offers other advantages over IPX
WAN links, including controlling of SAP updates, which is discussed in
the following section.
|