[Top] [Prev] [Next] [Bottom]

Chapter 6

Using Adaptive Source Route Transparent (ASRT) Bridging


This chapter describes Proteon's Adaptive Source Route Transparent (ASRT) bridge. It includes the following sections:

About ASRT

Transparent-Source Routing Compatibility - Issues and Solutions

About ASRT

The ASRT bridge is a software collection of several bridging options. ASRT combines transparent bridging and source route bridging so that they can either function separately or be combined as a single ASRT bridge. This extended functionality allows communication between a strict source-routing end station and a transparent end station. Depending on the configuration commands used, the ASRT bridge provides the following bridging options:

ASRT is modeled after the Source Route Transparent Bridging described in IEEE 802.5M/Draft 6 (1991) of SRT. Modifications built into ASRT provide extended functionality that goes beyond compliance with the SRT standard. ASRT allows compatibility with the installed base of source-routing bridges, while enabling them to link Ethernet and Token Ring LANs. ASRT also enhances basic SRT functionality in some additional, critical ways described below.

Transparent-Source Routing Compatibility - Issues and Solutions

ASRT provides transparent bridge compatibility with source route bridges through source route bridge conversion (SR-TB). SR-TB was originally proposed as part of the 802.5 specification. The ASRT implementation is similar to and can interoperate with IBM's 8209 conversion bridge.

ASRT converts transparent bridging frames to source route frames and vice versa. In other words, instead of just checking to see whether a RIF is present in a packet and forwarding it to a like destination, the ASRT bridge can translate the packet into either format. This means it functions as either a transparent bridge or a source route bridge by inserting or removing the RIF as necessary. With this functionality, packets can move between Ethernet and SRT Token Ring LANs and still be compatible with an installed base of source route Token Ring LANs.

Elimination of Packet Size Problems

ASRT also eliminates packet sizing problems in Token Rings bridged across an Ethernet domain. End stations use the source- routing protocol, which allows them to determine dynamically that there is a network with a 1518-byte maximum frame size between them. The end station automatically honors this limit without a manual reconfiguration. In the reverse situation, bridging Ethernets across a Token Ring domain, packet size is not an issue since the Token Ring packet size allowance is much larger.

Hardware Address Filtering

Another feature provided by ASRT is hardware address filtering on Token Ring. Hardware address filtering solves the conflict in packet acknowledgement methods that exist in the Ethernet and Token Ring LAN technologies. It occurs in the MAC layer and is the only technique that accurately sets acknowledgment bits based on the destination MAC address. ASRT uses Content Addressable Memory (CAMs) to implement hardware address filtering. This technology effectively gives the bridge a higher level of intelligence by providing instantaneous lookup of MAC addresses without creating any performance penalty.

Bit Ordering in STB (802.3) and SRB (802.5) Bridges

As bridges are continually being built to connect LANs with different MAC address types, bit ordering during data transmission affects the interoperability of these technologies.

In administering MAC addresses, IEEE assigns addresses known as 48-bit IEEE globally assigned unique MAC addresses. These addresses are supported by 802.3, 802.4, 802.5, and FDDI LANs. Due to the lack of standards at the time this addressing scheme was developed, two different situations have arisen:

Note: For simplicity's sake, let us call 802.3 and 802.4 bridges and LANs as LSB bridges and LANs. Similarly, let us call 802.5 and FDDI bridges and LANs as MSB bridges and LANs.

The difference in the bit transmission standard means that a bridge from LSB to MSB LANs has to reverse the bit order of the destination and source MAC addresses at the start of the MAC frame. This is because the different LAN types use the same bit order for the MAC address (i.e., group bit first) and yet use a different bit order for the user data: either LSB or MSB first.

The misinterpretation of addresses due to reversed bit ordering is compounded by the fact that some of the high-level communications protocols misinterpret MAC addresses altogether. Protocols like IP, IPX, and VINES misinterpret bridging addresses because at the time of their initial development, there was no standard representation of MAC addresses.

The bit order differential is best resolved by combining bridging technology (data link layer technology) with routing technology (network layer technology). Rather than asking the user to reverse engineer today's communications protocols and configure each bridge to flip or reverse addresses on a case-by-case basis, the problem is more easily solved by routing these protocols.

Routing eliminates the bit-order and protocol-addressing problems by accessing the detailed packet addresses running at the higher layer. Routing alone is not a complete solution, since other protocols such as IBM Frames and NetBIOS cannot be routed, and SNA routing is limited. Therefore, it is important to implement SRT in a device where bridging and routing work hand-in-hand. ASRT, the Proteon implementation of SRT, resides in all of its routers.

ASRT Configuration Considerations

ASRT uses the spanning tree protocol and algorithm described in the IEEE 802.1D bridge standard over all interfaces. It also uses IBM 8209 Spanning Tree on source routing ports. It is possible for more than one spanning tree to form in an environment where different types of bridges exist. For example a spanning tree of all bridges practicing IEEE802.1D protocol (e.g., STB and SRT) existing with another tree of IBM SRB bridges. The loops forming from this configuration require you to correct the situation.

ASRT Configuration Matrix

The collection of configuration parameters for ASRT and all connected interfaces produce a bridge personality for that bridge.

The following matrix provides a guide to the configuration settings needed for each interface type to produce the desired bridge personality to handle your network.

Interface Type & Bridging Method Setting
Bridge
Personality
SR <--> TB
Conversion Enabled?
Token
Ring 1
Token
Ring 2
Ethernet FDDI Serial Line or Tunnel
STB NO TB TB TB TB TB
SRB NO SR SR -- -- SR
STB & SRB NO SR SR TB TB TB or SR
SR <--> TB YES SR SR TB TB TB
SR <--> TB YES SR TB TB TB SR
SRT NO SR & TB SR & TB TB TB SR & TB
ASRT YES SR & TB SR TB TB SR & TB
ASRT YES SR SR & TB TB TB SR & TB
ASRT YES SR or TB SR or TB TB TB SR & TB
BRIDGE PERSONALITY KEY

STB = Transparent (Spanning Tree) Bridge SRB = Source Routing Bridge
SR <--> TB = Source Routing-Transparent Conversion Bridge
SRT = Source Routing Transparent Bridge
ASRT = Adaptive Source Routing Transparent Bridge

BRIDGING METHOD KEY

SR = Source Routing TB = Transparent Bridging



[Top] [Prev] [Next] [Bottom]

docs@openroute.com
Copyright © 1997, OpenROUTE Networks, Inc. All rights reserved. OpenROUTE 2.1