Information Technology Reference
In-Depth Information
Table10-6
Translational Bridging: Client Cannot Connect to Server (continued)
Possible Problem
Solution
Vendor code
mismatch
(continued)
cisco —OUI used 00000C, which provided for compatibility
with future equipment.
Example:
The following example specifies Cisco's OUI form:
interface tokenring 0
ethernet-transit-oui cisco
Cisco and
non-Cisco
translational
bridges in parallel
1.
Check for translational bridges in parallel with the Cisco
translational bridge. If there are any parallel non-Cisco
translational bridges, loops will probably be created.
2.
Because implementing translational bridging defeats the
spanning-tree mechanism of both transparent bridging and
SRB environments, you must eliminate all loops caused by
inserting the translational bridge. A transparent spanning
tree and a source-bridge spanning tree cannot communicate
with one another.
Trying to bridge
protocols that
embed MAC
addresses in the
Information field
of the MAC frame
(such as IP ARP, 3
Novell IPX, or
AARP 4 )
If MAC addresses are embedded in the Information field of the
MAC frame, bridges will be incapable of reading the address.
Bridges will therefore be incapable of forwarding the traffic.
If you are attempting to bridge this type of protocol, route
the protocol instead.
1.
If you still cannot communicate over the router, contact your
technical support representative.
2.
1.
OUI=organizationally unique identifier
2.
SNAP=Subnetwork Access Protocol
3.
ARP=Address Resolution Protocol
4.
AARP=AppleTalk Address Resolution Protocol
SRT Bridging: Client Cannot Connect to Server
Symptom: Clients cannot communicate over a router configured to perform SRT bridging. Packets are
not forwarded by the SRT bridge.
SRT bridging enables you to implement transparent bridging in Token Ring environments. It is not a
means of translating between SRB on a Token Ring and transparent bridging on Ethernet (or other)
media.
Search WWH ::




Custom Search