User`s guide

Introduction
1-21
The ATX uses a standardized internal format called canonical
format, for packet translation. (Refer to Appendix B, Packet
Translation Procedure for an explanation of the packet translation
procedure.) The ATX converts all incoming packets into its internal
format and then converts each packet from its internal format to
either FDDI, Ethernet, or Token Ring format, depending on the
packet's destination.
The ATX can interoperate with other vendors' translating bridges.
Translation allows end-nodes to reach destinations on the FDDI
ring as well as destinations attached to other vendors' translating
bridges and routers. In Figure 1-5 for example, ATX A or ATX B
could be bridge products from other vendors.
1.8 ROUTING FUNCTIONS
The ATX can route packets that use the IP and IPX, and Appletalk
protocols. A brief overview of these follows. For more in-depth
discussions, refer to the books listed in the section, Related
Documentation.
Note: When the ATX is not configured for routing, it’s necessary to
establish a default gateway so that management can take place
using a SNMP agent. To establish a default gateway connection,
apply the route add command through LCM using the following
format: route add IPaddr Gwaddr PORT# [hops]
[IPmask].For example: route add 0.0.0.0
176.16.107.19 3 This command establishes port 3 as the
default gateway to the router at 176.16.107.19. Any port (2 to 41)
can be the default gateway. The IPaddr 0.0.0.0 signals that this is
the default gateway specification. Other addresses can be used to
explicitly and statically route some IP trafic while remaining in
bridging (rather than routing) mode. SNMP management stations
are now able to poll the ATX locally and remotely, but this does not
permit the ATX to send SNMP traps to multiple SNMP
management stations. To identify a specific SNMP management
station where traps are sent, change the [configNMSAddress] MIB
located in the MIB tree at: