430
Chapter 8
Configuring Novell IPX
Here is an example of adding a secondary network to 2501A's Ethernet
connection:
2501A#config t
Enter configuration commands, one per line. End with CNTL/Z.
2501A(config)#int e0
2501A(config-if)#ipx network 10a encap sap sec
If you don't use the secondary command at the end of the line, the
ipx
network command will replace the existing entry. (The shortcut com-
mands encap and sec were used here instead of the whole command
encapsulation
and secondary.)
The important thing to understand is that each frame type must have a
different IPX network number. Notice the 10a in the above example. The
802.3 frame type is using 10 so that you cannot configure the 802.2 frame
type with that number.
Subinterfaces
To define IPX network numbers to router interfaces that support multiple
networks, you can use a subinterface instead of the secondary command.
This allows one physical interface to support multiple logical IPX networks.
Each subinterface, like a secondary, must have a unique IPX network num-
ber and a unique encapsulation type.
To define subinterfaces, use the interface ethernet port.number com-
mand. You can use numbers between e0.0 and e0.4292967295--that's a lot
of subinterfaces! An example of adding the 802.2 frame type is shown below:
2621A(config)#int e0.10
2621A(config-subif)#ipx network 10a encap sap
2621A(config-subif)#^Z
2621A#
As I have mentioned before, there is no functional difference between sub-
interfaces and the secondary command on the IPX internetwork; it is
merely an administrative difference. You create subinterfaces instead of a
secondary for administrative control because you can place commands
under the subinterface that allow more granular control over the subinter-
face and associated networks. If you use the secondary command instead,
the network is placed under the physical interface and any change you make
to the physical interface affects that network.
Copyright ©2002 SYBEX, Inc., Alameda, CA
www.sybex.com