Example 14-1 IPX Routing Table on R3 | CCNA Practical Studies (Cisco Certification & Training)

Configuring IPX RIP

In Chapter 13, you enabled IPX routing on each router and then configured an IPX network for each interface on R1, R2, R3, R4, and R5. After that, you examined the IPX routing table of R3. Re-examine the IPX routing table of R3 as shown in Example 14-1.

 Termserver#3 [Resuming connection 3 to r3 ... ] R3#  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 8 Total IPX routes. Up to 1 parallel paths and 16 hops allowed. No default route known. C       1000 (FRAME-RELAY),   Se0 C       3000 (NOVELL-ETHER),  Et0 c       3001 (SAP),           Et0 C       3500 (HDLC),          Se1 R       2000 [07/01] via     1000.0000.0000.2222,   35s, Se0 R       2100 [07/01] via     1000.0000.0000.2222,   35s, Se0 R       4000 [07/01] via     1000.0000.0000.4444,   55s, Se0 R       5000 [07/01] via     3500.0000.0000.5555,   28s, Se1 R3#

Notice that R3 has a route to every IPX network and that all remote IPX networks have been learned through RIP. This is because, by default, when you enable IPX routing and then assign an IPX network to an interface, the network automatically is placed into IPX RIP. IPX RIP then advertises these IPX networks throughout the network. This requires no configuration on your part. The result is that R3 learns a route to every other IPX network through IPX RIP. RIP routes are denoted with the letter R preceding the route in the routing table, while a C denotes directly connected routes. Initially, this might lead you to believe that you do not need to configure a routing protocol for IPX because routes are being propagated as seen on R3. However, before making this assumption, examine the IPX routing tables of R4 and R2. Example 14-2 shows R4's IPX routing table.

Example 14-2 IPX Routing Table on R4

 Termserver#4 [Resuming connection 4 to r4 ... ] R4#  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 6 Total IPX routes. Up to 1 parallel paths and 16 hops allowed. No default route known. C       1000 (FRAME-RELAY),   Se0 C       4000 (NOVELL-ETHER),  Et0 R       3000 [07/01] via     1000.0000.0000.3333,   24s, Se0 R       3001 [07/01] via     1000.0000.0000.3333,   25s, Se0 R       3500 [07/01] via     1000.0000.0000.3333,   25s, Se0 R       5000 [13/02] via     1000.0000.0000.3333,   25s, Se0 R4#

R4 has learned all IPX networks through RIP except for networks 2000 and 2100. If you examine the IPX routing table on R2, you will find similar results, as shown in Example 14-3.

Example 14-3 IPX Routing Table on R2

 Termserver#  2  [Resuming connection 2 to r2 ... ] R2#  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 7 Total IPX routes. Up to 1 parallel paths and 16 hops allowed. No default route known. C       1000 (FRAME-RELAY),   Se0 C       2000 (NOVELL-ETHER),  Et1 C       2100 (NOVELL-ETHER),  Et0 R       3000 [07/01] via     1000.0000.0000.3333,   47s, Se0 R       3001 [07/01] via     1000.0000.0000.3333,   47s, Se0 R       3500 [07/01] via     1000.0000.0000.3333,   47s, Se0 R       5000 [13/02] via     1000.0000.0000.3333,   47s, Se0 R2#

R2 has learned all IPX networks through RIP except for the IPX network 4000. Because this route is lacking, full IPX connectivity does not exist between R2 and R4. To demonstrate this, initiate a ping from R2 to R4's Ethernet 0 IPX address of 4000.0010.7b7f.fa6e, and observe the results shown in Example 14-4.

Example 14-4 IPX ping to R4's Ethernet 0 IPX Address Fails

 Termserver#2 [Resuming connection 2 to r2 ... ] R2#  ping ipx 4000.0010.7b7f.fa6e  Translating "4000.0010.7b7f.fa6e" Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 4000.0010.7b7f.fa6e, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) R2#

You can see that R2 cannot ping R4's Ethernet 0 IPX network of 4000. Although not shown, R4 also would not be capable of ping ing to R2's Ethernet 0 and Ethernet 1 IPX networks of 2000 or 2001. The IPX ping fails as a result of the fact that R4 and R2 are not receiving all IPX routes through IPX RIP. How can this be? R3 received all IPX networks through IPX RIP, but R4 and R2 did not? The answer is revealed when examining the rule of split horizon.

Split Horizon

Split horizon blocks information about routes from being advertised out the same interface from which the route originally was learned. By default, split horizon is enabled on all interfaces. Generally, this behavior optimizes communication among multiple routers, particularly when links are broken; however, with nonbroadcast networks such as Frame Relay, situations can arise for which this behavior is less than ideal. This is particularly evident in the case of a hub-and-spoke Frame Relay environment, as exists between R3, R2, and R4. By default, IPX split horizon is enabled on R3's Serial 0 interface. Because IPX split horizon is in effect, IPX routes that R3 receives from R2 (networks 2000 and 2100) are blocked from being advertised back out R3's Serial 0 interface to R4. In addition, the IPX route that R3 receives from R4 (network 4000) is blocked from being advertised back out R3's Serial 0 interface to R2. Thus, R4 and R2 never get these routes because split horizon prevents them from being advertised out R3's Serial 0 interface.

To ensure that R2 and R4 receive these routes, you must disable split horizon on R3's Serial 0 interface. It is important to note here that split horizon cannot be disabled for IPX RIP; it can be disabled only for IPX EIGRP. So, to disable split horizon, you must first configure IPX EIGRP.

Configuring IPX EIGRP and Disabling Split Horizon

To disable IPX split horizon, you must enable IPX EIGRP as the routing process for all interfaces in the Frame Relay cloud. When IPX EIGRP is enabled, you then will disable IPX EIGRP split horizon on the R3's Serial 0 interface. In addition, to fulfill the lab objective, you will configure R4's Ethernet 0 interface to be advertised through IPX EIGRP. To configure IPX EIGRP and disable split horizon on R3's Serial 0 interface, perform the following steps:

Step 1. Enable the IPX EIGRP routing process.

Step 2. Add the desired IPX network into the IPX EIGRP routing process.

Step 3. Remove the IPX network that was added to the IPX EIGRP routing process from the IPX RIP routing process.

Step 4.

Disable split horizon on R3's Serial 0 interface.

Follow these steps starting with R2, then R4, and finally R3. First, review each step and the commands necessary to accomplish them, as shown in Table 14-1.

Table 14-1. Steps to Configuring IPX EIGRP and Disabling IPX Split-Horizon

Step	Command
1. Enable the IPX EIGRP routing process from global configuration mode.	Router(config)# ipx router eigrp [ autonomous-system-number ]
2. Add the desired IPX network into the IPX EIGRP routing process in router configuration mode.	Router(config-ipx-router)# network [ ipx network-number ]
3. Remove the IPX EIGRP network from the IPX RIP routing process in router configuration mode.	Router(config)# ipx router rip Router(config-ipx-router)# no network [ ipx-network-number ]
4. Disable IPX split horizon on R3's Serial 0 interface from interface configuration mode.	Router(config-if)# no ipx split-horizon eigrp [ autonomous-system-number ]

Begin with R2. Enable the IPX EIGRP routing process and use the autonomous system 100. Next, place R2's Serial 0 IPX network of 1000 into the IPX EIGRP routing process and subsequently remove IPX network 1000 from the IPX RIP routing process. This forces network 1000 to be advertised through IPX EIGRP instead of through IPX RIP. In addition, because you are using EIGRP for IPX routing, R2 will go through the process of forming neighbor relationships, as was done with IP EIGRP. For a complete review of this process, refer to Chapter 10. Return to R2 and perform these steps as shown in Example 14-5.

Example 14-5 Configuring R2 for IPX EIGRP AS 100, Adding IPX Network 1000, and Removing IPX Network 1000 from IPX RIP

 Termserver#  2  [Resuming connection 2 to r2 ... ] R2#  conf t  Enter configuration commands, one per line.  End with CNTL/Z. R2(config)#  ipx router eigrp 100  R2(config-ipx-router)#  network 1000  R2(config-ipx-router)#  exit  R2(config)#  ipx router rip  R2(config-ipx-router)#  no network 1000  R2(config-ipx-router)#  end  R2# 20:33:12: %SYS-5-CONFIG_I: Configured from console by console R2#

If you examine the running config of R2, you can see how the IPX routing configuration appears, as shown in Example 14-6.

Example 14-6 R2's Running Config After Configuration of IPX EIGRP

 R2#  show running-config  Building configuration... Current configuration: ! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname R2 ! enable password falcons ! username all ip subnet-zero no ip domain-lookup ip host R1 192.169.1.1 ip host R2 192.169.2.2 ip host R3 192.169.3.3 ip host R4 192.169.4.4 ip host R5 192.169.5.5 ip host R6 192.169.6.6 ipx routing 0000.0000.2222 ! ! ! interface Loopback0  ip address 192.169.2.2 255.255.255.0  no ip directed-broadcast ! interface Ethernet0  ip address 192.168.1.2 255.255.255.0  no ip directed-broadcast  ipx network 2100  ! interface Ethernet1  description This interface does not connect with another IP device  ip address 192.168.2.2 255.255.255.0  no ip directed-broadcast  ipx network 2000  ! interface Serial0  description This interface connects to R3's S0 (201)  ip address 192.168.100.2 255.255.255.0  no ip directed-broadcast  encapsulation frame-relay  no ip mroute-cache  ipx network 1000  no fair-queue  frame-relay map ip 192.168.100.3 201 broadcast  frame-relay map ip 192.168.100.4 201 broadcast  frame-relay map ipx 1000.0000.0000.4444 201 broadcast  frame-relay map ipx 1000.0000.0000.3333 201 broadcast  frame-relay lmi-type ansi ! router eigrp 100  redistribute rip metric 2000 200 255 1 1500  network 192.168.100.0 ! router rip  redistribute eigrp 100 metric 1  network 192.168.1.0  network 192.168.2.0  network 192.169.2.0 ! ip classless ! ! !  ipx router eigrp 100   network 1000   !   !   ipx router rip   no network 1000  ! ! ! banner motd ^C This is Router 2 ^C ! line con 0  exec-timeout 0 0  password falcons  logging synchronous  transport input none line vty 0 4  password falcons  login ! end R2#

The running config shows that IPX network 1000 has been added to IPX EIGRP autonomous system 100 and has been removed from IPX RIP. It is also worthy to note that IPX networks 2000 and 2001 do not show up explicitly under IPX RIP even though they are properly configured on R2's Ethernet 0 and Ethernet 1, as highlighted. You just have to remember that any IPX network configured on an interface is, by default, advertised through IPX RIP even without adding it to the IPX RIP routing process. In addition, it is for this very reason that you must explicitly remove IPX network 1000 from IPX RIP.

Continue by configuring R4 for IPX EIGRP, and assign IPX network 1000 to be advertised through IPX EIGRP, as shown in Example 14-7.

Example 14-7 Configuring R4 for IPX EIGRP AS 100, Adding IPX Network 1000, and Removing IPX Network 1000 from IPX RIP

 R4#  conf t  Enter configuration commands, one per line.  End with CNTL/Z. R4(config)#ipx router eigrp 100 R4(config-ipx-router)#  network 1000  R4(config-ipx-router)#  exit  R4(config)#  ipx router rip  R4(config-ipx-router)#  no network 1000  R4(config-ipx-router)#  end  R4# %SYS-5-CONFIG_I: Configured from console by console R4#

Next, configure R3 for IPX EIGRP, as shown in Example 14-8.

Example 14-8 Configuring R3 for IPX EIGRP AS 100, Adding IPX Network 1000, and Removing IPX Network 1000 from IPX RIP

 R3#  conf t  Enter configuration commands, one per line.  End with CNTL/Z. R3(config)#  ipx router eigrp 100  R3(config-ipx-router)#  network 1000  R3(config-ipx-router)#  exit  R3(config)#  ipx router rip  R3(config-ipx-router)#  no network 1000  R3(config-ipx-router)#  end  R3# %SYS-5-CONFIG_I: Configured from console by console R3#

Now that R3 has been configured for IPX EIGRP, display the IPX EIGRP neighbors, as demonstrated in Example 14-9.

Example 14-9 R3 Shows Established IPX EIGRP Neighbor Adjacencies with R2 and R4

 R3#  show ipx eigrp neighbors  IPX EIGRP Neighbors for process 100 H   Address                 Interface   Hold Uptime   SRTT   RTO  Q  Seq                                         (sec)         (ms)       Cnt Num 1   1000.0000.0000.2222     Se0          179 00:01:51  724  4344  0  2 0   1000.0000.0000.4444     Se0          165 00:02:06  553  3318  0  4 R3#

R3 has successfully formed an IPX EIGRP neighbor adjacency with both R2 (1000.0000.0000.2222) and R4 (1000.0000.0000.4444). Now return to R4 and display the IPX routing table, to see how IPX routes are being learned. Example 14-10 shows the IPX routing table after EIGRP has been configured.

Example 14-10 IPX Routing Table on R4 After EIGRP Configuration

 R4#  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 6 Total IPX routes. Up to 1 parallel paths and 16 hops allowed. No default route known. C       1000 (FRAME-RELAY),   Se0 C       4000 (NOVELL-ETHER),  Et0 E       3000 [2195456/1] via     1000.0000.0000.3333, age 00:09:28,                          1u, Se0 E       3001 [2195456/1] via     1000.0000.0000.3333, age 00:09:29,                          1u, Se0 E       3500 [2681856/1] via     1000.0000.0000.3333, age 00:09:29,                          1u, Se0 E       5000 [276864000/2] via     1000.0000.0000.3333, age 00:09:29,                          1u, Se0 R4#

The output in Example 14-10 shows that R4 is learning all remote IPX routes through IPX EIGRP. Notice that R4 has learned networks 3001, 3500, and 5000 through EIGRP, even though these networks were configured on R3 and R5 to be advertised through IPX RIP. This occurs because of IPX route redistribution and will be covered in more detail later in the chapter. Also notice that R4 still has not learned about networks 2000 and 2001, as desired. To remedy this, disable IPX EIGRP split horizon on R3's Serial 0 interface, as demonstrated in Example 14-11.

Example 14-11 Disabling IPX EIGRP Split Horizon on R3's Serial 0 Interface

 R3#  conf t  %SYS-5-CONFIG_I: Configured from console by console Enter configuration commands, one per line.  End with CNTL/Z. R3(config)#  int s0  R3(config-if)#  no ipx split-horizon eigrp 100  R3(config-if)#  end  R3# %SYS-5-CONFIG_I: Configured from console by console R3#

Now that split horizon has been disabled on R3's Serial 0 interface, when you return to R4 and display the IPX routing table, you will see the results in Example 14-12.

Example 14-12 R4's IPX Routing Table After Split Horizon Is Disabled on R3

 R4#  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 8 Total IPX routes. Up to 1 parallel paths and 16 hops allowed. No default route known. C       1000 (FRAME-RELAY),   Se0 C       4000 (NOVELL-ETHER),  Et0  E       2000 [2707456/1] via     1000.0000.0000.3333, age 00:05:16,   1u, Se0   E       2100 [2707456/1] via     1000.0000.0000.3333, age 00:05:16,   1u, Se0  E       3000 [2195456/1] via     1000.0000.0000.3333, age 00:05:16,                          1u, Se0 E       3001 [2195456/1] via     1000.0000.0000.3333, age 00:05:16,                          1u, Se0 E       3500 [2681856/1] via     1000.0000.0000.3333, age 00:05:16,                          1u, Se0 E       5000 [276864000/2] via     1000.0000.0000.3333, age 00:05:16,                          1u, Se0 R4#

R4 has learned the IPX networks 2000 and 2001 that previously were being blocked because of split horizon. Next, examine R2's IPX routing table, as shown in Example 14-13.

Example 14-13 R2's IPX Routing Table After Split Horizon Is Disabled on R3

 R2#  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 8 Total IPX routes. Up to 1 parallel paths and 16 hops allowed. No default route known. C       1000 (FRAME-RELAY),   Se0 C       2000 (NOVELL-ETHER),  Et1 C       2100 (NOVELL-ETHER),  Et0 E       3000 [2195456/1] via     1000.0000.0000.3333, age 00:02:10,                          1u, Se0 E       3001 [2195456/1] via     1000.0000.0000.3333, age 00:02:10,                          1u, Se0 E       3500 [2681856/1] via     1000.0000.0000.3333, age 00:02:10,                          1u, Se0  E       4000 [2707456/1] via     1000.0000.0000.3333, age 00:02:10,   1u, Se0  E       5000 [276864000/2] via     1000.0000.0000.3333, age 00:02:10,                          1u, Se0 R2#

The IPX route table shows that R2 now has received IPX network 4000 through IPX EIGRP.

IPX Route Redistribution

As pointed out earlier, R4 learned networks 3001, 3500, and 5000 through EIGRP, even though these networks are configured by default to be advertised through IPX RIP on R3 and R5. This occurs because, by default, Cisco IOS Software automatically redistributes IPX RIP routes into EIGRP, and vice versa. IPX route redistribution occurs at routing domain boundaries. For this lab, IPX route redistribution occurs at R3 and R2 where both IPX RIP and IPX EIGRP are configured. On R2 and R3, IPX RIP routes are redistributed into EIGRP, and vice versa. You can see this further by displaying the IPX routes on R1, as shown in Example 14-14.

Example 14-14 R1's IPX Routing Table Reveals That IPX Route Redistribution Is Occurring in the Network

 R1#  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 8 Total IPX routes. Up to 1 parallel paths and 16 hops allowed. No default route known. C       2100 (NOVELL-ETHER),  Et0 R       1000 [02/01] via     2100.0010.7bf9.4912,   48s, Et0 R       2000 [02/01] via     2100.0010.7bf9.4912,   48s, Et0 R       3000 [08/02] via     2100.0010.7bf9.4912,   49s, Et0 R       3001 [08/02] via     2100.0010.7bf9.4912,   49s, Et0 R       3500 [08/02] via     2100.0010.7bf9.4912,   49s, Et0 R       4000 [14/02] via     2100.0010.7bf9.4912,   49s, Et0 R       5000 [14/03] via     2100.0010.7bf9.4912,   49s, Et0 R1#

R1 has a route to all IPX networks. In addition, every remote network was learned through IPX RIP, as denoted by the preceding letter R. This is because IPX EIGRP routes are being redistributed on R3 and R2 from IPX RIP into EIGRP and from EIGRP into IPX RIP; then they subsequently are passed on through IPX RIP to R1. In this way, R1 receives all IPX routes to the rest of the network.

Verifying IPX Configuration, Operation, and Connectivity

To verify the IPX configuration and ensure full IPX connectivity, review those IPX commands that can assist you in this task. You already have seen how the running config appears after IPX has been configured with IPX RIP and IPX EIGRP. You also have seen the usefulness of examining the IPX routing table using the show ipx route command, from which you verified which IPX routes have been received and from which routing protocol they were advertisedIPX RIP or IPX EIGRP. In addition, you also saw how the show ipx eigrp neighbors command verifies IPX EIGRP neighbor adjacencies. In addition to these commands, which have been demonstrated throughout the chapter, review the following commands used to verify the IPX configuration and ensure full IPX connectivity:

  show ipx interface brief   show ipx interface   show ipx traffic   show ipx servers   ping ipx

show ipx interface brief Command

Begin by returning to R3 and examining the IPX interfaces with the show ipx interface brief command, as shown in Example 14-15.

Example 14-15 show ipx interface brief Command Output on R3 Displays IPX Summary Information for Each Interface

 R3#  show ipx interface brief  Interface            IPX Network Encapsulation Status     IPX State  Ethernet0            3000   NOVELL-ETHER  up         [up]  Ethernet0            3001   SAP  up         [up] Loopback0            unassigned  not config'd  up         n/a Serial0              1000        FRAME-RELAY   up         [up] Serial1              3500        HDLC          up         [up] R3#

This command is similar to the IP version of the command show ip interface brief but for IPX. This command provides a summary of each interface in the router, its associated IPX network (if assigned), the encapsulation type used on the interface, the status of the interface, and the IPX state. This is helpful when you want to review IPX networks and their encapsulation types. For example, you see that R3's Ethernet0 interface has two networks assigned3000 and 3001and that IPX network 3000 is using the NOVELL-ETHER encapsulation while IPX network 3001 is using Service Advertising Protocol (SAP). This information could be used to ensure that neighboring routers have been set to the same encapsulation type, enabling them to share routing information. In this lab, a neighboring IPX router attached to R3's Ethernet 0 segment does not exist. However, if it did exist, you would need to assign the same IPX network and encapsulation type to both neighboring interfaces to advertise IPX routes to each other.

show ipx interface Command

Next, take a look at the extended version of this command show ipx interface. This command provides the IPX details for all IPX interfaces on the router. You could narrow the amount of information that is displayed by specifying the interface that you want to see the details forthat is, show ipx interface Ethernet 0. Examine the IPX details of Ethernet 0 on R3, as shown in Example 14-16.

Example 14-16 show ipx interface on R3 Displays Detailed IPX Information for R3's Ethernet 0 Interface

 R3#  show ipx interface   Ethernet0 is up, line protocol is up   IPX address is 3000.0000.0c38.9306, NOVELL-ETHER [up]  Delay of this IPX network, in ticks is 1 throughput 0 link delay 0   IPXWAN processing not enabled on this interface.  Secondary address is 3001.0000.0c38.9306, SAP [up]  Delay of this Novell network, in ticks is 1   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   IPX accounting is disabled   IPX fast switching is configured (enabled)   RIP packets received 0, RIP packets sent 8207   SAP packets received 0, SAP packets sent 8202 R3#

This command reveals the primary and secondary IPX addressing information, the encapsulation type, and the complete IPX network and node address. In addition, you can see various other IPX parameters, such as IPX access lists, SAP filters, and NetBIOS access, to name a few. These are outside the scope of this book and have not been covered within the chapter. However, be aware that this is where you could view such information if it were configured.

show ipx traffic Command

Another useful command that displays IPX traffic statistics such as SAP, RIP, and EIGRP information is show ipx traffic, as demonstrated on R3 in Example 14-17.

Example 14-17 show ipx traffic Command Output on R3 Displays IPX Packet Information

 R3#  show ipx traffic  System Traffic for 0.0000.0000.0001 System-Name: R3  Rcvd:  22595 total, 0 format errors, 0 checksum errors, 0 bad hop count,         0 packets pitched, 22550 local destination, 0 multicast Bcast:  21761 received, 29533 sent  Sent:  30159 generated, 45 forwarded         0 encapsulation failed, 0 no route SAP:    0 SAP requests, 0 ignored, 0 SAP replies,  1 servers  0 SAP Nearest Name requests, 0 replies         0 SAP General Name requests, 0 replies         26 SAP advertisements received, 12330 sent         219 SAP flash updates sent, 0 SAP format errors RIP:    0 RIP requests, 0 ignored, 0 RIP replies,  8 routes  4113 RIP advertisements received, 12333 sent         223 RIP flash updates sent, 0 RIP format errors Echo:   Rcvd 30 requests, 0 replies         Sent 0 requests, 30 replies         0 unknown: 0 no socket, 0 filtered, 0 no helper         0 SAPs throttled, freed NDB len 0 Watchdog:         0 packets received, 0 replies spoofed Queue lengths:         IPX input: 0, SAP 0, RIP 0, GNS 0         SAP throttling length: 0/(no limit), 0 nets pending lost route reply         Delayed process creation: 0 EIGRP:  Total received 18381, sent 4995  Updates received 116, sent 152   Queries received 9, sent 54   Replies received 54, sent 9  SAPs received 111, sent 146 NLSP:   Level-1 Hellos received 0, sent 0         PTP Hello received 0, sent 0         Level-1 LSPs received 0, sent 0         LSP Retransmissions: 0         LSP checksum errors received: 0         LSP HT=0 checksum errors received: 0         Level-1 CSNPs received 0, sent 0         Level-1 PSNPs received 0, sent 0         Level-1 DR Elections: 0         Level-1 SPF Calculations: 0         Level-1 Partial Route Calculations: 0 R3#

The show ipx traffic command displays information about the number and type of IPX packets transmitted and received. This command displays the number of broadcasts, SAPs, routing packets received, and a total of all packets received. A few of theses were highlighted in the previous example for emphasis. First, notice the fields for sent and received rows. The packet count in these fields should increment steadily. If these are not incrementing or show 0, IPX routing might not be configured properly. You should check the individual RIP, EIGRP, or SAP details for additional clues and also check your IPX routing configuration. Next, notice the SAP row. SAP is used in IPX networks to advertise available services in an IPX environment. The output in Example 14-17 shows that R3 has learned of one server through SAP. The RIP row shows that R3 has learned eight routes. The number of routes shown here should correspond to the number of routes displayed in the IPX routing table. Finally, you can see that IPX EIGRP is sending and receiving updates, queries, and replies.

show ipx servers Command

Another useful command in verifying that IPX services are being propagated throughout the network is the show ipx servers command. A Novell file server is located on IPX network 2100. Verify that this server is being advertised through SAP by examining R3's SAP table, as shown in Example 14-18.

Example 14-18 show ipx servers Command Output on R3 Displays R3's SAP Table

 R3#  show ipx servers  Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail 1 Total IPX Servers Table ordering is based on routing and server info    Type Name                 Net     Address    Port     Route Hops Itf E   640 NOVELLSERVER         2100.5254.00da.ee56:E885 2195456/01   2  Se0 R3#

NetWare nodes such as NetWare file servers and printer servers use SAP broadcasts to advertise their services and addresses every 60 seconds. SAP broadcasts are essential to a NetWare environment. Cisco routers do not forward each SAP broadcast that they receive. Instead, each router maintains a SAP table and broadcasts this table every 60 seconds. By listing the IPX servers discovered through SAP, you can see that R3 has learned about this Novell server as well as its network and node address. In addition, this command shows the port number and the number of hops to the server. In this demonstration, you are dealing with only one server. In large IPX environments, however, SAP broadcasts can consume a large portion of network bandwidth and should be managed using SAP filtering.

ping ipx Command

Finally, assemble a table of IPX network and node address within the topology for the lab. This table will be used to test IPX connectivity throughout the network. You could gather this information either from the lab diagram (because it has been documented as you've gone along) or by going to each router and using the command show ipx interface brief followed by show ipx interface. This table should include the router name, the IPX interface, and IPX network and node information. When completed, the table should look like Table 14-2.

NOTE

Your table will appear slightly different as the IPX node portion will correspond to the unique MAC addresses of your hardware. Serial IPX network and node information will appear the same.

Table 14-2. IPX Network, Node, and Interface Information for R1 Through R5

Router	IPX Interface	IPX Network.Node
R1	Ethernet 0	2100.00e0.1e3e.9a69
R2	Ethernet 0	2100.0010.7bf9.4912
	Ethernet 1	2000.0010.7bf9.4913
	Serial 0	1000.0000.0000.2222
R3	Ethernet 0	3000.0000.0c38.9306
	Ethernet 0 (secondary)	3001.0000.0c38.9306
	Serial 0	1000.0000.0000.3333
	Serial 1	3500.0000.0000.3333
R4	Ethernet 0	4000.0010.7b7f.fa6e
R4	Serial 0	1000.0000.0000.4444
R5	Serial 0	3500.0000.0000.5555
R5	TokenRing 0	5000.0000.30b1.523b

Using this table, you can test IPX connectivity using the ping ipx command followed by the appropriate IPX network address and node. Do this from R1. From R1, begin by testing IPX connectivity to each interface in R2, then R3, and so on. Example 14-19 shows how this is done.

Example 14-19 IPX ping on R1 Demonstrates Full IPX Connectivity from R1 to R2, R3, R4, and R5

 Termserver#  1  [Resuming connection 1 to r1 ... ] R1#  ping ipx 2100.0010.7bf9.4912  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 2100.0010.7bf9.4912, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms R1#  ping ipx 2000.0010.7bf9.4913  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 2000.0010.7bf9.4913, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms R1#  ping ipx 1000.0000.0000.2222  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 1000.0000.0000.2222, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/8/16 ms R1#  ping ipx 3000.0000.0c38.9306  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 3000.0000.0c38.9306, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 32/35/36 ms R1#  ping ipx 3001.0000.0c38.9306  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 3001.0000.0c38.9306, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 32/57/148 ms R1#  ping ipx 1000.0000.0000.3333  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 1000.0000.0000.3333, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 32/36/40 ms R1#  ping ipx 3500.0000.0000.3333  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 3500.0000.0000.3333, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 32/34/36 ms R1#  ping ipx 4000.0010.7b7f.fa6e  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 4000.0010.7b7f.fa6e, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 92/95/96 ms R1#  ping ipx 1000.0000.0000.4444  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 1000.0000.0000.4444, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 92/96/100 ms R1#  ping ipx 3500.0000.0000.5555  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 3500.0000.0000.5555, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 32/36/40 ms R1#  ping ipx 5000.0000.30b1.523b  Type escape sequence to abort. Sending 5, 100-byte IPX cisco Echoes to 5000.0000.30b1.523b, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 36/36/40 ms R1#

R1 has full IPX connectivity to every other IPX network within the network.

Top