Scenario 9-2 661
2
The second planning item requires remembering the four encapsulations for IPX on
Ethernet. The important item here is to correlate the headers used by the devices to the
correct name used by Cisco in the encapsulation command. Table 9-8 summarizes the
encapsulations for the four PCs.
3
Choosing IPX network numbers does not pose a particularly challenging task. However,
realizing that two network numbers are needed on R1's E0 and on R2's E0 is the hidden
part of the objective. As long as your network numbers are not duplicated, and as long as
you planned for two IPX networks for the two aforementioned Ethernet interfaces, any
network numbers are fine. Table 9-9 lists the network numbers that will be used as the
basis of the configuration in Scenario 9-2, Part B.
R1 S0
168.11.123.201
168.11.123.192
168.11.123.255
193 to 254 in last octet
R2 S0
168.11.123.202
168.11.123.192
168.11.123.255
193 to 254 in last octet
R3 S0
168.11.123.203
168.11.123.192
168.11.123.255
193 to 254 in last octet
Table 9-8
Scenario 9-2, Part A--IPX Encapsulations
PC
Cisco IOS's Encapsulation
PC11
ARPA
PC12
Novell-ether
PC21
SAP
PC22
SNAP
Table 9-9
Scenario 9-2, Part A--IPX Network Number Planning Chart Completed
Host
Address
R1 E0
110 (ARPA)
R1 E0
111 (Novell-ether)
R2 E0
120 (SAP)
R2 E0
121 (SNAP)
R3 E0
130
Frame Relay
123
Server 1 internal
101
Server 2 internal
102
Server 3 internal
103
Table 9-7
Scenario 9-2, Part A--IP Subnet and IPX Network Planning Chart Completed (Continued)
Router
Interface
IP Address
Subnet
Number
Subnet
Broadcast
Address
Range of Valid
Addresses
ch09.fm Page 661 Monday, March 20, 2000 5:23 PM