Example 13-1 Enabling IPX on R1
Configuring IPX on Cisco Routers
Several step exist for configuring IPX on a Cisco router. Knowing the steps and the proper order in which to proceed will help in configuring IPX correctly the first time. The list that follows outlines the configuration steps needed for successfully enabling IPX on a Cisco router:
- Step 1. Enable IPX.
- Step 2. Configure the IPX interface.
- Step 3. Configure IPX routing (covered in Chapter 14).
- Step 4. Verify IPX configuration.
Configuring IPX is similar to configuring IP. Each needs network and node addresses and a way to share routing information. IPX accomplishes these goals with different Cisco IOS Software commands than IP, but the end result is the same: Interfaces get assigned network and node addresses, and disparate IPX networks can communicate through Cisco routers.
Before IPX interface or IPX routing commands can be initiated, IPX must be enabled first. So let's start there.
Enable IPX Routing
Before you can configure any IPX networks on the router interfaces, you need to enable the IPX routing process. At the same time, you can manually specify a node address for the serial interfaces (remember, serial interfaces do not have a MAC address). It is very helpful during troubleshooting to have a standard for serial link node addresses. This will ease the issue of having to look up the Ethernet or Token Ring MAC address to verify connectivity to the serial links. The naming standard for this lab is 0000.0000.1111 for R1, 0000.0000.2222 for R2, 0000.0000.3333 for R3, and so on. Go through all the routers (starting with R1), enable the IPX routing process, and manually set the node address for all the routers. Then go back and configure the individual interfaces according to the type: Frame Relay first, Ethernet second, and finally the Token Ring interfaces.
The syntax for enabling IPX on the routers, under global configuration mode, is as follows:
Router(config)# ipx routing [ node-address ]
The only option in this command is to specify the node address. The node address is given in hexadecimal format with a period (.) separating every 4 digits. Enable IPX routing on R1 and give it the node address of 0000.0000.1111 or 0.0.1111. Example 13-1 shows the command executed on R1.
Termserver# 1 [Resuming connection 1 to r1 ... ] R1# config t Enter configuration commands, one per line. End with CNTL/Z. R1(config)# ipx routing 0000.0000.1111 R1(config)# R1(config)# end R1# 2w4d: %SYS-5-CONFIG_I: Configured from console by console R1# copy run start Building configuration...
The command is pretty simple, but it must be entered before Cisco IOS Software will accept IPX network numbers on the interfaces. Start the IPX routing process and specify the node address. When this is completed, you can configure IPX networks on the routers' interfaces. Go through all the routers and enable IPX. Before leaving the routers, though, be sure to save the configuration, a habit that you have hopefully acquired since starting the lab. Example 13-2 displays the commands issued on the remaining routers.
Example 13-2 Enable IPX on All Routers
Termserver# 2 [Resuming connection 2 to r2 ... ] R2# config t Enter configuration commands, one per line. End with CNTL/Z. R2(config)# ipx routing 0000.0000.2222 R2(config)# end R2# 2w4d: %SYS-5-CONFIG_I: Configured from console by console R2# copy run start Building configuration... Termserver# 3 [Resuming connection 3 to r3 ... ] _______________________________________________________________________ R3# config t Enter configuration commands, one per line. End with CNTL/Z. R3(config)# ipx routing 0000.0000.3333 R3(config)# end R3# copy run start Building configuration... Termserver# 4 [Resuming connection 4 to r4 ... ] _______________________________________________________________________ R4# config t Enter configuration commands, one per line. End with CNTL/Z. R4(config)# ipx routing 0000.0000.4444 R4(config)# end R4# copy run start Building configuration... Termserver# 5 [Resuming connection 5 to r5 ... ] _______________________________________________________________________ R5# config t Enter configuration commands, one per line. End with CNTL/Z. R5(config)# ipx routing 0000.0000.5555 R5(config)# end R5# copy run start Building configuration...
With IPX enabled on all the routers, you can configure the separate interfaces beginning with the Frame Relay interfaces.
Configure IPX on Frame Relay Interfaces
Configuring IPX on Frame Relay interfaces is similar to configuring IP on Frame Relay. The first two steps already are completed: changing the encapsulation to Frame Relay on the interface and configuring the Frame Relay LMI type to be ANSI. Now you need to assign an IPX network to the interface. Because there is no such thing as Frame Relay Inverse-ARP for IPX, all IPX addresses must be manually mapped to their appropriate DLCIs on all routers.
To configure an IPX network address on an interface, under the interface configuration mode for that interface, issue this command:
Router(config-if)# ipx network network-address [ encapsulation encapsulation-type ]
The required field that you need to assign is the network-address in hexadecimal form. If there are any preceding zeros, they may be dropped. The only option here is to specify an encapsulation type. If you are using the default, there is no need to use the encapsulation option. If you are setting a secondary IPX network for that interface, the encapsulation option must be issued, and the encapsulation type must be different than the primary network address encapsulation type. Example 13-3 illustrates this command on R3's Serial 0.
Example 13-3 Configuring IPX Network on R3's Serial 0
Termserver# 3 [Resuming connection 3 to r3 ... ] R3# config t Enter configuration commands, one per line. End with CNTL/Z. R3(config)# int s0 R3(config-if)# ipx network 1000 R3(config-if)#
Now that an IPX network is configured on an interface, you can see whether is correctly configured by issuing this command:
Router# show ipx interfaces [ brief ]
This command lists all the interfaces that have IPX configured. Using the brief option results in less information about the interfaces. Example 13-4 shows output from this command without the brief option.
Example 13-4 show ipx interface Command Output
R3# show ipx interface Serial0 is up, line protocol is up IPX address is 1000.0000.0000.3333 [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 0, RIP packets sent 1 SAP packets received 0, SAP packets sent 0 R3#
The highlighted portion illustrates where the IPX address can be seen to verify that the correct IPX network was configured on the correct interface. As you notice, the IPX address is 1000.0000.0000.3333. The 1000 is the IPX network number that you just configured, and the 0000.0000.3333 is the node address that you configured earlier in the chapter when you enabled IPX for the router. Issue the same command with the brief option to compare the differences in the commands. Example 13-5 demonstrates the command.
Example 13-5 show ipx interface brief Command Output
R3# show ipx interface brief Interface IPX Network Encapsulation Status IPX State Ethernet0 unassigned not config'd up n/a Loopback0 unassigned not config'd up n/a Serial0 1000 FRAME-RELAY up [up] Serial1 unassigned not config'd up n/a
As the highlighted output shows, only the IPX network address is revealed, not the complete IPX address with both the network address and the node address. The output also shows the encapsulation type and the status of the interface. This is a quick way to see which interfaces have IPX and what state they are in. This command is revisited later in the chapter when all the interfaces are configured for IPX. Because this is the first interface to be configured for IPX, you won't be able to IPX ping any other routers, so go to R2 and configure its Frame Relay interface (serial 0) for IPX and test the IPX connectivity to R3.
To configure IPX on R2's serial 0, issue the same command that you did for R3. Example 13-6 displays the commands on R2.
Example 13-6 Configuring IPX Network on R2's Serial 0
Termserver# 2 [Resuming connection 2 to r2 ... ] R2# config t Enter configuration commands, one per line. End with CNTL/Z. R2(config)# int s0 R2(config-if)# ipx network 1000 R2(config-if)#
Now you need to manually map the IPX address for R3 and R4 to the DLCI (201). If you have forgotten the DLCI number, you can refer back to the network diagram or you can use the show frame-relay pvc command. This command is the same Frame Relay map command issued in Chapter 7, "Router Interface Configuration Methodology," except that you specify the IPX protocol and the IPX address instead of the IP protocol and the IP address. Example 13-7 illustrates this command. Manually map both R3 and R4's IPX addresses, even though R4 has not yet been configured. You do know the IPX network address (1000) and the node address (0000.0000.4444) of R4 to complete the IPX address needed for the frame-relay map statement.
Example 13-7 frame-relay map Statements on R2
R2(config-if)# frame-relay map ipx 1000.0000.0000.3333 201 broadcast R2(config-if)# frame-relay map ipx 1000.0000.0000.4444 201 broadcast
With R2 having the frame-relay map statements, R2 should be capable of ping ing R3. Example 13-8 shows the results.
Example 13-8 R2 IPX ping to R3
R2(config-if)# end R2# ping 1000.0000.0000.3333 (or R2# ping IPX 1000.0000.0000.3333 ) Type escape sequence to abort. Sending 5, 100-byte IPXcisco Echoes to 1000.0000.0000.3333, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5) , round-trip min/avg/max = 32/33/36 ms R2#
This results in 100 percent success. It is important to note that the IPX address that was ping ed was that of the serial 0 interface. When IPX is configured on the Ethernet interfaces, the IPX address no longer uses the 0000.0000.3333 node address. It uses the MAC address of the Ethernet interface. The ping command is smart enough to understand which protocol you want to ping by the address format typed in after the command. Configure R4's S0 interface and verify its connectivity to R3 and R2. Example 13-9 demonstrates the configuration commands on R4.
Example 13-9 IPX Configuration Commands on R4's Serial 0
Termserver# 4 [Resuming connection 4 to r4 ... ] R4# config t Enter configuration commands, one per line. End with CNTL/Z. R4(config)# int s0 R4(config-if)# ipx network 1000 R4(config-if)# frame-relay map ipx 1000.0000.0000.3333 101 broadcast R4(config-if)# frame-relay map ipx 1000.0000.0000.2222 101 broadcast R4(config-if)#
With the configuration commands complete, verify connectivity to R3 and R2. Example 13-10 displays the results of the IPX ping.
Example 13-10 IPX ping Result from R4 to R3 and R2
R4(config-if)# end R4# ping 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 = 60/60/64 ms R4# ping 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: !!!!! Succes s rate is 100 percent (5/5), round-trip min/avg/max = 92/94/96 ms R4#
Great! IPX connectivity exists on all the Frame Relay interfaces. Take a look at what the frame-relay map statements now look like on R4. Example 13-11 displays the output.
Example 13-11 frame-relay map Entries on R3
Termserver# 3 [Resuming connection 3 to r3 ... ] R3# show frame-relay map Serial0 (up): ip 192.168.100.2 dlci 200(0xC8,0x3080), dynamic, broadcast,, status defined, active Serial0 (up): ip 192.168.100.4 dlci 100(0x64,0x1840), dynamic, broadcast,, status defined, active Serial0 (up): ipx 1000.0000.0000.2222 dlci 200(0xC8,0x3080), dynamic, broadcast,, status defined, active Serial0 (up): ipx 1000.0000.0000.4444 dlci 100(0x64,0x1840), dynamic, broadcast,, status defined, active R3#
Highlighted in Example 13-11 are the new Frame Relay map entries for the IPX address for R2 and R4. This is important because, without IPX Frame Relay map entries, R3 would not be capable of IPX ping ing R2 or R4.
In the next section, you will configure the Ethernet and Token Ring interfaces on all routers.
Configure IPX on Ethernet and Token Ring Interfaces
IPX configurations are nearly the same as IP address configurations on Ethernet and Token Ring. You only need to configure the IPX network number, and the router will automatically place the MAC address of the interface in the node address portion of the IPX address. You already know how to configure an IPX network on a Frame Relay interface. The command to configure an IPX network on Ethernet and Token Ring interfaces is the same. Configure R1's Ethernet 0 and R2's Ethernet 0 interfaces for IPX. Revisiting the lab objectives, you can see that you need to assign an IPX network address of 2100. Example 13-12 illustrates the command to accomplish this.
Example 13-12 IPX Network Configuration on R1's Ethernet 0 and R2's Ethernet 0
Termserver# 1 [Resuming connection 1 to r1 ... ] R1# config t Enter configuration commands, one per line. End with CNTL/Z. R1(config)# int e0 R1(config-if)# ipx network 2100 R1(config-if)# end R1# copy running-config startup-config Building configuration... Termserver# 2 [Resuming connection 2 to r2 ... ] _______________________________________________________________________ R2# config t Enter configuration commands, one per line. End with CNTL/Z. R2(config)# int e0 R2(config-if)# ipx network 2100 R2(config-if)#
Now that you have IPX network addresses on the interfaces, try to ping from R2 to R1's Ethernet 0 IPX address. To do this, you need to find the MAC address of R1's Ethernet 0. The easiest way to do this is to issue the show interface ethernet 0 command, as demonstrated in Example 13-13.
Example 13-13 Output of show int ethernet 0 Command on R1
Termserver#1 [Resuming connection 1 to r1 ... ] R1# show interface ethernet 0 Ethernet0 is up, line protocol is up Hardware is Lance, address is 00e0.1e3e.9a69 (bia 00e0.1e3e.9a69) Description: This interface connects to R2's E0 Internet address is 192.168.1.1/24 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec) ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:03, output 00:00:00, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 98863 packets input, 10335188 bytes, 0 no buffer Received 98659 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 input packets with dribble condition detected 247589 packets output, 21575438 bytes, 0 underruns 0 output errors, 0 collisions, 2 interface resets 0 babbles, 0 late collision, 7 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out R1#
The highlighted line in Example 13-13 indicates where the MAC address is shown in the output. Go back to R2 and ping the interface 2100.00e0.1e3e.9a69. Example 13-14 shows the results of the ping to this interface.
Example 13-14 ping Result from R2 to R1's Ethernet 0 Interface
Termserver# 2 [Resuming connection 2 to r2 ... ] R2# ping 2100.00e0.1e3e.9a69 Translating "2100.00e0.1e3e.9a69" Type escape sequence to abort. Sending 5, 100-byte IPXcisco Echoes to 2100.00e0.1e3e.9a69, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5) , round-trip min/avg/max = 4/4/4 ms R2#
Again, this results in 100 percent success. Next, configure R2's Ethernet 1 (IPX network 2000), R3's Ethernet 0 (IPX network 3000), R3's Serial 1 (IPX network 3500), R4's Ethernet 0 (IPX network 4000), R5's Serial 0 (IPX network 3500), and R5's Serial 0 (IPX network 3500) and Token Ring 0 (IPX network 5000). For Token Ring, the command is the same. Example 13-15 shows the configuration for these routers.
Example 13-15 IPX Configurations on the Remaining Routers
R2# config t Enter configuration commands, one per line. End with CNTL/Z. R2(config)# int e1 R2(config-if)# ipx network 2000 R2(config-if)# end R2# copy running-config startup-config Destination filename [startup-config]? Building configuration... Termserver# 3 [Resuming connection 3 to r3 ... ] _______________________________________________________________________ R3# config t Enter configuration commands, one per line. End with CNTL/Z. R3(config)# int e0 R3(config-if)# ipx network 3000 R3(config-if)# exit R3(config)# int s1 R3(config-if)# ipx network 3500 R3(config-if)# end R3# copy running-config startup-config Building configuration... Termserver# 4 [Resuming connection 4 to r4 ... ] _______________________________________________________________________ R4# config t Enter configuration commands, one per line. End with CNTL/Z. R4(config)# int e0 R4(config-if)# ipx network 4000 R4(config-if)# end R4# copy running-config startup-config Building configuration... Termserver# 5 [Resuming connection 5 to r5 ... ] _______________________________________________________________________ R5# config t Enter configuration commands, one per line. End with CNTL/Z. R5(config)# int s0 R5(config-if)# ipx network 3500 R5(config-if)# exit R5(config)# int tokenRing 0 R5(config-if)# ipx network 5000 R5(config-if)# end R5#
Now try to ping between R3's Serial 1 and R5's Serial 0 interfaces. These are the only two interfaces that are connected to another IPX device. Example 13-16 displays the results.
Example 13-16 ping Result from R5 to R3's Serial 1
R5(config-if)# end R5# ping 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 = 4/5/8 ms R5#
It worked. It is interesting to notice that the same node address for R3's Serial 1 interface was used as when you did the ping to R3's Serial 0 interface. When you manually set the node address, all serial interfaces assumed that address. The only thing that you needed to change in the ping command was the IPX network address that pertained to R3's Serial 1 interface (IPX network 3500).
The final lab objective is to configure a secondary IPX network number on R3's Ethernet 0 with an encapsulation type of SAP. Use the same command that you did for the primary IPX network configuration, but use the encapsulation option and the secondary option. Example 13-17 demonstrates the command on R3.
Example 13-17 Secondary IPX Network Configuration on R3
Termserver# 3 [Resuming connection 3 to r3 ... ] R3# config t Enter configuration commands, one per line. End with CNTL/Z. R3(config)# interface ethernet 0 R3(config-if)# ipx network 3001 encapsulation sap secondary
Verifying IPX Configuration
Now that all the lab objectives are completed, take a look again at the output from the show ipx interface brief command, as displayed in Example 13-18.
Example 13-18 show ipx interfaces brief Command Output
R3(config-if)# end R3# show ipx int 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#
From the output, you can see all the configured IPX interfaces and their status. This is a nice way to review the IPX configuration on the router.
Before moving on to IPX routing, take a look at the IPX routing table for R3. To see the IPX routing table, you need to issue this command:
Router# show ipx route Example 13-19 displays the IPX routing table.
Example 13-19 IPX Routing Table for 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, 28s, Se0 R 2100 [07/01] via 1000.0000.0000.2222, 28s, Se0 R 4000 [07/01] via 1000.0000.0000.4444, 32s, Se0 R 5000 [07/01] via 3500.0000.0000.5555, 41s, Se1 R3# Surprised? You can see all the IPX networks in the IPX routing table. How can this be if you have not yet configured a routing protocol for IPX? By default, IPX propagates all IPX networks with IPX RIP, as discussed in the next chapter.
 |
| Top |
EAN: 2147483647
Pages: 127