Page 477

432

Chapter 8

Configuring Novell IPX

sap IEEE 802.2 on Ethernet, FDDI, Token Ring

snap IEEE 802.2 SNAP on Ethernet, Token Ring,

and FDDI

RouterA(config-if)#ipx network 10a encap sap sec

After you configure the secondary address, you need to add two sub-

interfaces. If you were configuring this network for a real production
network and needed to support multiple frame types, you would use only
subinterfaces and no secondary networks because Cisco will not support
secondary

commands in the future (so they say). The secondary com-

mand is only included here so you understand what it is if you see it in a
configuration.

The subinterface numbers can be any number, as the help screen (int

f0/0.?)

shows below. The subinterface numbers are only locally significant

and have no bearing on how IPX runs on the internetwork.

2621A(config)#int f0/0.?

<0-4294967295> Ethernet interface number

2621A(config)#int f0/0.10

2621A(config-subif)#ipx network 10b encap arpa

2621A(config)#int f0/0.100

2621A(config-subif)#ipx network 10c encap snap

All four frame types are now configured on the FastEthernet 0/0 interface

of the 2621 router. For any device to communicate with the 2621A router
with IPX, they must support the same network numbers configured with
each frame type.

Configuring Multiple Frame Types on the 2501A Router

For the 2501A router to communicate to the 2621A router with IPX, it must
be configured with the same IPX network numbers for each frame type
configured.

Here is the configuration for the 2501A router:

2501A(config)#int e0

2501A(config-if)#ipx network 10a encap sap sec

2501A(config-if)#int e0.10

2501A(config-subif)#ipx network 10b encap arpa

2501A(config-subif)#int e0.100

2501A(config-subif)#ipx network 10c encap snap

www.sybex.com