Ip Fragmentation; Ipx Snap Translation - 3Com corebuilder 3500 Implementation Manual

IP Fragmentation

IPX SNAP
Translation
A statically configured address is never aged and it cannot be learned
dynamically on a different port until it is removed from the port on
which it is configured.
The number of static MAC addresses that you can configure depends
on the availability of system resources.
If a station whose address is statically configured on one port is moved
to a different port, the system discards all received packets as a
security measure and increments a statistical counter. (From the
bridge display
rxSecurityDiscs
Management interface, see the Received Security Discards column.)
Standard FDDI allows larger maximum packet sizes than standard
Ethernet. FDDI stations that transmit IP packet sizes larger than
approximately 1500 bytes wish cannot communicate with stations on an
Ethernet LAN. If the system receives such packets and they are destined
for one or more Ethernet LANs, it filters them — except when IP
fragmentation is enabled.
When you enable IP fragmentation, the system breaks up large FDDI
packets into smaller packets before bridging them to Ethernet.
IPX SNAP Translation allows an alternative method of translating IPX
packets from Ethernet to FDDI and vice-versa.
When IPX SNAP translation is enabled, any 802.3_RAW IPX packets
that are forwarded from Ethernet to FDDI are translated to
FDDI_SNAP. Likewise, SNAP IPX packets that are forwarded from FDDI
to Ethernet are translated to 802.3_RAW packets.
When IPX SNAP translation is disabled, the system uses standard IEEE
802.1H bridging to translate 802.3_RAW packets to FDDI_RAW
packets.
of the Administration Console, see the
field. From the Bridge Display option on the Web
IP Fragmentation 139