background image
308 Chapter 5: Network Protocols
The show ipx interface command provides a lot of information about IPX, including the
complete IPX address. In this case, you can see that the node part of Seville's IPX address is
easily recognizable, whereas Albuquerque's is not. Seville's node address is 0200.cccc.cccc
based on its ipx routing 0200.cccc.cccc configuration command (refer to Example 5-20).
However, because the node parameter was omitted from the ipx routing command on
Albuquerque (refer to Example 5-18), the router chooses a MAC on one of the LAN interfaces
to use as the node portion of the IPX addresses on non-LAN interfaces.
NOTE
After the ipx routing command is entered, the router saves the command with the node value.
In other words, even if Albuquerque's configuration were typed as in Example 5-18, the node
number chosen from a LAN interface would be shown at the end of the ipx routing command
when viewing the configuration in the future.
Several nuances are involved in how the node parts of the addresses are assigned. The first is
that if the node part of the IPX address on WAN interfaces is derived from the MAC of a LAN
interface, and if there is more than one LAN interface, then the IOS must choose one MAC
address to use. The algorithm uses the MAC address of the "first" Ethernet interface--or the
first Token Ring interface, if no Ethernet exists, or the first FDDI interface, if no Ethernet or
Token Ring exists. The lowest numbered interface number is considered to be "first." The next
nuance is that if no LAN interfaces exist, the node parameter on the ipx routing command must
be configured, or IPX routing will not work on a WAN interface. The final nuance is that the
node part of IPX addresses on router LAN interfaces ignores the node parameter of the ipx
routing
command, and uses its specific MAC address as the node part of the address.
The second sample network (illustrated in Figure 5-38) uses Frame Relay with point-to-point
subinterfaces. Example 5-22, Example 5-23, Example 5-24, and Example 5-25 show the
configuration for this network.
Netbios Input host access list is not set
Netbios Input bytes access list is not set
Netbios Output host access list is not set
Netbios Output bytes access list is not set
Updates each 60 seconds, aging multiples RIP: 3 SAP: 3
SAP interpacket delay is 55 ms, maximum size is 480 bytes
RIP interpacket delay is 55 ms, maximum size is 432 bytes
Watchdog processing is disabled, SPX spoofing is disabled, idle time 60
IPX accounting is disabled
IPX fast switching is configured (enabled)
RIP packets received 51, RIP packets sent 51
SAP packets received 2, SAP packets sent 28
Seville#
Example 5-21
show ipx interface serial 0 on Albuquerque and Seville (Continued)
ch05.fm Page 308 Monday, March 20, 2000 5:06 PM