3Com CoreBuilder 3500, Implementation Manual, Page: 429 / 592

IPX Interfaces 429
■
Before you define the IPX (routing) interface, you must define a VLAN
and select IPX, IPX-II, IPX-802.2, IPX-802.2 LLC, or IPX-802.3-SNAP as
the protocol to be supported by the VLAN. See Chapter 9.
■
Unless your network has special requirements, such as the need for
redundant paths, assign a cost of 1 to each interface and do not
modify this setting.
■
The three FDDI encapsulation formats correspond to the Ethernet
802.2 LLC, 802.3 SNAP, and RAW encapsulation formats. If you select
either of these Ethernet encapsulation formats, the corresponding
FDDI encapsulation format is automatically selected for shared
Ethernet and FDDI ports.
■
When you modify an IPX interface, you define the interface’s:
■
IPX address.
■
Cost.
■
Format.
■
Associated IPX VLAN index.
■
If you use the OddLengthPadding feature, make sure that you select
only those interfaces that require odd-length padding. If you enable
this option for every interface, network performance slows.
To create an IPX interface, see the Administering IPX Routing chapter in
the
Command Reference Guide .
Per-Interface Options You set the NetBIOS and OddLengthPadding options on each interface.
NetBIOS Option
This option determines whether the system handles IPX Type 20 packet
forwarding on each interface. For details about how to use this option,
see the Administering IPX Routing chapter in the
Command Reference
Guide
.
OddLengthPadding Option
This option provides compatibility with older network interface cards
(NICs). This option enables an interface to pad IPX packets that have an
odd number of bytes, so that older NICs do not discard the packets. To
use this option, see the chapter about IPX routing in the
Command
Reference Guide
.