Enterasys 6000 사용자 가이드
Chapter 13
Configuring Bridging
The Netlink FRX4000 and FRX6000 support transparent "Spanning Tree" bridging of
non-routable LAN traffic (e.g., NetBIOS, DECnet, AppleTalk) over frame relay
between 802.3/Ethernet or 802.5/Token Ring LANs. FRX4000/6000 also support
translational bridging between Ethernet and Token Ring LANs. (For more infor-
mation on bridging, refer to IEEE standard 802.1d.)
non-routable LAN traffic (e.g., NetBIOS, DECnet, AppleTalk) over frame relay
between 802.3/Ethernet or 802.5/Token Ring LANs. FRX4000/6000 also support
translational bridging between Ethernet and Token Ring LANs. (For more infor-
mation on bridging, refer to IEEE standard 802.1d.)
Routing transmits each packet based on its level-3 address, while bridging transmits
each frame based on its level-2 address. Athough some traffic can be either routed or
bridged, there is usually an advantage to doing one over the other. For instance,
bridging is generally easier to configure; however, routing can be more versatile.
each frame based on its level-2 address. Athough some traffic can be either routed or
bridged, there is usually an advantage to doing one over the other. For instance,
bridging is generally easier to configure; however, routing can be more versatile.
IP and IPX traffic can also be bridged. (Bridging can be enabled individually for IP or
IPX; if enabled for either, all traffic of that type will be bridged.)
IPX; if enabled for either, all traffic of that type will be bridged.)
Neither IP (because of its ARP frames) nor IPX (because of its MAC
addressing structure) can be bridged successfully between Ethernet and
Token Ring LANs. (However, they can be routed between different LAN
types.)
addressing structure) can be bridged successfully between Ethernet and
Token Ring LANs. (However, they can be routed between different LAN
types.)
Incoming LLC2 traffic that is destined for a terminated MAC address will be for-
warded to the node's internal LLC2 processes. Non-terminated LLC2 frames and all
other frames will be forwarded to the bridge.
warded to the node's internal LLC2 processes. Non-terminated LLC2 frames and all
other frames will be forwarded to the bridge.
Under the spanning tree concept, bridges automatically maintain forwarding tables via
exchange of messages with other bridges on the network, and determination of single
paths for traffic between endpoints (assuming there are multiple possible paths).
exchange of messages with other bridges on the network, and determination of single
paths for traffic between endpoints (assuming there are multiple possible paths).
Each Bridge is identified by a Bridge ID, which is made up of a two-octet Bridge Pri-
ority—configured in Bridge Node Defaults (see page 13-3) —followed by a unique
48-bit ID. If the node contains a LAN card, the 48-bit ID will be the MAC address of
the first LAN card to send its status (active/inactive). If there is no LAN card, an
address will be created automatically by the software.
ority—configured in Bridge Node Defaults (see page 13-3) —followed by a unique
48-bit ID. If the node contains a LAN card, the 48-bit ID will be the MAC address of
the first LAN card to send its status (active/inactive). If there is no LAN card, an
address will be created automatically by the software.
Bridging is supported on Ethernet, Token Ring, and frame relay interfaces.
The interfaces used for Bridging in the FRX4000 and FRX6000 are the
same as those used for LLC2. When referring to Bridging, however, these
interfaces will be called "Bridge ports," since the IEEE 802.1d standard
uses the term "port" to identify a connection to a bridge.
same as those used for LLC2. When referring to Bridging, however, these
interfaces will be called "Bridge ports," since the IEEE 802.1d standard
uses the term "port" to identify a connection to a bridge.