IPX Configuration

Table 5-34 IPX and IPX RIP Configuration Commands

Command

Configuration Mode

ipx routing [node]

Global

ipx maximum-paths paths

Global

ipx network network [encapsulation type] Interface mode

[secondary]

Table 5-35 IPX EXEC Commands

Command

Function

show ipx interface

Gives detailed view of IPX parameter settings,

per interface

show ipx route [network]

Shows entire routing table, or one entry if

network is entered

show ipx servers

Shows SAP table

show ipx traffic

Shows IPX traffic statistics

debug ipx routing [events 1 activity]

Gives messages describing each routing update

debug ipx sap [events 1 activity]

Gives messages describing each SAP update

ping ipx-address

Sends IPX packets to verify connectivity

The first sample is a basic configuration for the network in Figure 5-37. Example 5-18, Example 5-19, and Example 5-20 provide the configuration.

NOTE The IPX samples also contain IP configuration. This is not required for correct operation of IPX. However, to Telnet to the routers to issue commands, IP must be configured. In fact, in almost every network with Cisco routers, IP is indeed configured. Therefore, the IPX examples generally include IP configuration.

Figure 5-37 IPX Network with Point-to-Point Serial Links

Bugs Daffy

Bugs Daffy

s0

Albuquerque s1

Albuquerque s1

s0

Sam Emma

Elmer Red

Sam Emma

Elmer Red

Example 5-18 Albuquerque Configuration for IPX, Sample 1

ipx routing !

interface serial0

ip address 10.1.12.

1 255.255.255.0

ipx network 1012

bandwidth 56

interface serial1

ip address 10.1.13.

1 255.255.255.0

ipx network 1013

interface ethernet

0

ip address 10.1.1.1

255.255.255.0

ipx network 1

Example 5-19 Yosemite Configuration for IPX, Sample 1

ipx routing 0200.bbbb.bbbb

interface serial0

ip address 10.1.12.2 255.255.255.0 ipx network 1012

bandwidth 56 !

interface serial1

ip address 10.1.23.2 255.255.255.0

ipx network 1023 !

interface ethernet 0

ip address 10.1.2.2 255.255.255.0

ipx network 2

Example 5-20 Seville Configuration for IPX, Sample 1

ipx routing 0200.cccc.cccc

interface serial0

ip address 10.1.13.3 255.255.255.0 ipx network 1013

interface serial1

ip address 10.1.23.3 255.255.255.0 ipx network 1023

interface ethernet 0

ip address 10.1.3.3 255.255.255.0

ipx network 3

Enabling IPX routing globally as well as on each interface is all that is required to route IPX in a Cisco router. The ipx routing command enables IPX in this router and initializes the RIP and SAP processes. The individual ipx network commands on each interface enable IPX routing into and out of each interface and enable RIP and SAP on each interface, respectively.

The IPX addresses are not completely defined, however. Only the network number is configured. The full IPX network number is created by adding the MAC address of each interface to the configured IPX network number. For non-LAN interfaces, the MAC address of a LAN interface is used by default. However, for easier troubleshooting, a MAC address to be used as the node part of the IPX address on non-LAN interfaces can be configured. Notice the difference in the two commands in Example 5-21. The first is on Albuquerque, and the second is on Seville:

Example 5-21 show ipx interface serial 0 on Albuquerque and Seville

Albuquerque#show ipx interface serial 0

Serial0 is up, line protocol is up

IPX address is 1012.0000.0ccf.21cd [up]

Delay of this IPX network, in ticks is 6 throughput 0 link

delay 0

IPXWAN processing not enabled on this interface.

IPX SAP update interval is 1 minute(s)

IPX type 20 propagation packet forwarding is disabled

Incoming access list is not set

Outgoing access list is not set

IPX helper access list is not set

SAP GNS processing enabled, delay 0 ms, output filter list

is not set

SAP Input filter list is not set

SAP Output filter list is not set

SAP Router filter list is not set

Input filter list is not set

Output filter list is not set

Router filter list is not set

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 39, RIP packets sent 44

SAP packets received 27, SAP packets sent 29

Albuquerque#

Seville#show ipx interface serial 0

Serial0 is up, line protocol is up

IPX address is 1013.0200.cccc.cccc [up]

Delay of this IPX network, in ticks is 6 throughput 0 link

delay 0

IPXWAN processing not enabled on this interface.

IPX SAP update interval is 1 minute(s)

IPX type 20 propagation packet forwarding is disabled

Incoming access list is not set

Outgoing access list is not set

IPX helper access list is not set

SAP GNS processing enabled, delay 0 ms, output filter list

is not set

SAP Input filter list is not set

SAP Output filter list is not set

SAP Router filter list is not set

Input filter list is not set

Output filter list is not set

Router filter list is not set

Example 5-21 show ipx interface serial 0 on Albuquerque and Seville (Continued)

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#

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.

Figure 5-38 IPX Network with Frame Relay and Point-to-Point Subinterfaces

Figure 5-38 IPX Network with Frame Relay and Point-to-Point Subinterfaces

Example 5-22 Atlanta Configuration ipx routing 0200.aaaa.aaaa !

interface serial0

encapsulation frame-relay !

interface serial 0.1 point-to-point ip address 140.1.1.1 255.255.255.0 ipx network 1

frame-relay interface-dlci 52 !

interface serial 0.2 point-to-point ip address 140.1.2.1 255.255.255.0 ipx network 2

Example 5-22 Atlanta Configuration (Continued)

frame-relay 1

interface

-dlci

53

interface serial

0.3

point

-to-point

ip address 1

40.1

3.1

255.255.255.0

ipx network

3

frame-relay ■

interface

-dlci

54

interface ethernet 0

ip address 1

40.1

11.1

255.

255.255.0

ipx network

11

Example 5-23 Charlotte Configuration ipx routing 0200.bbbb.bbbb

interface serial0

encapsulation frame-relay !

interface serial 0.1 point-to-point ip address 140.1.1.2 255.255.255.0 ipx network 1

frame-relay interface-dlci 51 !

interface ethernet 0

ip address 140.1.12.2 255.255.255.0

ipx network 12

Example 5-24 Nashville Configuration ipx routing 0200.cccc.cccc

interface serial0

encapsulation frame-relay !

interface serial 0.2 point-to-point ip address 140.1.2.3 255.255.255.0 ipx network 2

frame-relay interface-dlci 51 !

interface ethernet 0

ip address 140.1.13.3 255.255.255.0

ipx network 13

Example 5-25 Boston Configuration ipx routing 0200.dddd.dddd

interface serial0

encapsulation frame-relay !

interface serial 0.3 point-to-point

Example 5-25 Boston Configuration (Continued)

ip address 140.1.3.4 255.255.255.0 ipx network 3

frame-relay interface-dlci 51 !

interface ethernet 0

ip address 140.1.14.4 255.255.255.0

ipx network 14

The configuration is very similar to the point-to-point network of Figure 5-37. The biggest difference is that each point-to-point subinterface is a different IPX network, as seen in Figure 5-38. Otherwise, SAP and RIP are enabled globally with the ipx routing command; each is allowed to be broadcast on interfaces (or subinterfaces) with the ipx network interface subcommand. SAP and RIP updates are sent out each subinterface—this means that Atlanta will replicate and send three copies of the RIP update and three copies of the SAP update on its serialO interface, one per subinterface, every 60 seconds.

Configuration when using multiple Ethernet encapsulations is the final configuration option to be reviewed. In Figure 5-38, assume that Gary is an old NetWare client running NetWare version 3.11 client software and using the Ethernet_802.3 Novell encapsulation. Stephanie is newer and uses the Ethernet_802.2 encapsulation. Two IPX networks are used on Nashville's Ethernet 0 interface in this case.

Gary will be in Network 13, and Stephanie will be in Network 23. Example 5-26 shows just the Ethernet configuration for the Nashville network, with a secondary IPX network on Ethernet 0. Example 5-26 also shows an alternative configuration using subinterfaces.

Example 5-26 Nashville Configuration with Secondary IPX Network on Ethernet 0

ipx routing 0200.cccc.cccc !

interface ethernet 0

ipx network 13 encapsulation ipx network 23 encapsulation ! Or instead of the previous interface ethernet 0.1 ipx network 13 encapsulation interface ethernet 0.2 ipx network 23 encapsulation novell-ether sap secondary

3 lines, use the following 4 lines:

novell-ether sap

Example 5-27 shows the output of the debug ipx sap events and debug ipx routing events commands. The network in Figure 5-39 was used to gather the sample output.

Figure 5-39 Sample Network Used for IPX debug Commands

SVR1 SVR2

Net1

Net1

Example 5-27 IPX debug Commands

Seville#show ipx route

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, U - Per-user static

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

No default route known.

C

3

(NOVELL-ETHER),

Et0

C

5

(FRAME-RELAY),

Se0

2

C

6

(FRAME-RELAY),

Se0

1

R

1

[07/01] via

6

0200

aaaa

aaaa,

51s,

Se0

1

R

2

[07/01] via

5

0200

bbbb

bbbb,

40s,

Se0

2

R

4

[07/01] via

5

0200

bbbb

bbbb,

40s,

Se0

2

R

11

[08/03] via

6

0200

aaaa

aaaa,

51s,

Se0

1

R

22

[08/03] via

6

0200

aaaa

aaaa,

51s,

Se0

1

R

200

[08/02] via

6

0200

aaaa

aaaa,

51s,

Se0

Seville#debug ipx routing events

IPX routing events debugging is on

01:04:03: IPXRIP: 5 FFFFFFFF not added, entry in table is static/connected/internal 01:04:12: IPXRIP: positing full update to 6.ffff.ffff.ffff via Serial0.1 (broadcast)

Example 5-27 IPX debug Commands (Continued)

01

04

14

IPXRIP: 6 FFFFFFFF not added,

entry in table

is static/connected/internal

01

04

14

IPXRIP: positing full update

to 5.ffff.ffff

.ffff via Serial0.2

(broadcast)

01

04

20

IPXRIP: positing full update

to 3.ffff.ffff

.ffff via Ethernet0

(broadcast)

01

05

03

IPXRIP: 5 FFFFFFFF not added,

entry in table

is static/connected/internal

01

05

11

IPXRIP: positing full update

to 6.ffff.ffff

.ffff via Serial0.1

(broadcast)

01

05

14

IPXRIP: 6 FFFFFFFF not added,

entry in table

is static/connected/internal

01

05

14

IPXRIP: positing full update

to 5.ffff.ffff

.ffff via Serial0.2

(broadcast)

01

05

20

IPXRIP: positing full update

to 3.ffff.ffff

.ffff via Ethernet0

(broadcast)

Seville#debug ipx routing activity

IPX routing debugging is on

Seville#

01

07

02

IPXRIP: update from 6.0200.aaaa.aaaa

01

07

02

IPXRIP: 5 FFFFFFFF not added,

entry in table

is static/connected/internal

01

07

02

5 in 2 hops, delay 13

01

07

02

200 in 2 hops, delay 8

01

07

02

11 in 3 hops, delay 8

01

07

02

22 in 3 hops, delay 8

01

07

02

1 in 1 hops, delay 7

01

07

02

2 in 2 hops, delay 13

01

07

02

4 in 1 hops, delay 7

01

07

10

IPXRIP: positing full update

to 6.ffff.ffff

.ffff via Serial0.1

(broadcast)

01

07

10

IPXRIP: Update len 64 src=6.

0200.cccc.cccc,

dst=6.ffff.ffff.ffff(453)

01

07

10

network 3, hops 1, delay 7

01

07

10

network 4, hops 2, delay 13

01

07

10

network 2, hops 2, delay 13

01

07

10

network 5, hops 1, delay 7

01

07

13

IPXRIP: positing full update

to 5.ffff.ffff

.ffff via Serial0.2

(broadcast)

01

07

13

IPXRIP: Update len 80 src=5.

0200.cccc.cccc,

dst=5.ffff.ffff.ffff(453)

01

07

13

network 1, hops 2, delay 13

01

07

13

network 22, hops 4, delay 14

01

07

13

network 11, hops 4, delay 14

01

07

13

network 200, hops 3, delay 14

01

07

13

network 3, hops 1, delay 7

01

07

13

network 6, hops 1, delay 7

01

07

13

IPXRIP: update from 5.0200.bbbb.bbbb

01

07

13

IPXRIP: 6 FFFFFFFF not added,

entry in table

is static/connected/internal

01

07

13

6 in 2 hops, delay 13

01

07

13

22 in 4 hops, delay 14

01

07

13

11 in 4 hops, delay 14

01

07

13

200 in 3 hops, delay 14

01

07

13

1 in 2 hops, delay 13

01

07

13

2 in 1 hops, delay 7

01

07

13

4 in 1 hops, delay 7

Example 5-27 IPX debug Commands (Continued)

Seville#undebug all

All possible debugging has been turned off Seville#show ipx servers

Codes: S - Static, P - Periodic, E - EIGRP, N U - Per-user static 4 Total IPX Servers

Table ordering is based on routing and server info

Type

Name

Net

Address

Port

Route

Hops

Itf

P

4

SVR1

200.

0000.0000.0001

:0452

8/02

3

Se0.

1

P

4

SVR2

200.

0000.0000.0001

:0452

8/02

3

Se0.

1

P

7

SVR1

200.

0000.0000.0001

:0452

8/02

3

Se0.

1

P

7

SVR2

200.

0000.0000.0001

:0452

8/02

3

Se0.

1

Seville#debug ipx sap activity

IPX service debugging is on Seville#

00:13:21: IPXSAP: Response (in) type 0x2 len 288 src:6.0200.aaaa.aaaa dest:6.ffff.ffff.ffff(452)

Seville#debug ipx sap activity

IPX service debugging is on Seville#

00:13:21: IPXSAP: Response (in) type 0x2 len 288 src:6.0200.aaaa.aaaa dest:6.ffff.ffff.ffff(452)

Seville#

Seville#

type 0x4, "SVR2", 200.0000.0000.0001(452), type 0X4, "SVR1", 200.0000.0000.0001(452), type 0x7, "SVR2", 200.0000.0000.0001(452), type 0X7, "SVR1", 200.0000.0000.0001(452),

3 hops 3 hops 3 hops 3 hops via Serial0.1

IPXSAP: positing update to 6.ffff.ffff.ffff IPXSAP: suppressing null update to 6.ffff.ffff.ffff

(broadcast)

IPXSAP:

Response (in) type 0x2 len 288 src:5.0200.bbbb.bbbb dest:5.ffff.ffff.ffff(452) 0x7, "SVR1" 0x7, "SVR2" 0x4, "SVR1" 0x4, "SVR2"

undebug all

All possible debugging has been turned off Seville#

type type type type

200.0000.0000.0001(452), 200.0000.0000.0001(452), 200.0000.0000.0001(452), 200.0000.0000.0001(452),

4 hops 4 hops 4 hops 4 hops

The debug ipx SAP events command lists the details of each sent and received SAP update. Notice that the number of hops to the server is shown, as is the type of service and the server name. The source and destination of the update packets are also listed. The debug ipx routing events command lists just summary information about routing updates, whereas the debug ipx routing activity command gives the details.

Was this article helpful?

0 0

Post a comment