Information Technology Reference
In-Depth Information
Table10-4
RSRB: Host Cannot Connect to Server (Peers Open) (continued)
Possible Problem
Solution
End system that
does not support
RIF
1.
Place a network analyzer on the same ring to which the end
system is connected.
2.
Look for RIF frames sent from the end system (RIF frames
have the high-order bit of the source MAC address set to 1).
3.
If no RIF frames are seen, the end system does not support
RIF and cannot participate in source routing.
If the protocol is routable, you can route the protocol or configure
transparent bridging. If you use transparent bridging, be careful
not to create loops between the SRB and the transparent bridging
domains.
If your environment requires SRB, contact your workstation
or server vendor for SRB drivers or for information about
setting up your workstation or server to support SRB.
4.
Explorer traffic
that is not
reaching remote
ring
1.
Using a network analyzer or the
debug source-bridge
command, watch network traffic to see whether explorers
from the end system reach the remote ring.
2.
If traffic reaches the remote ring successfully, check the
configuration of the destination end system (for example, a
server) to see why that station does not reply to the explorer
traffic from the source.
If traffic does not reach the remote ring, use the
show
source-bridge
command to check ring lists. If information about
the ring has not been learned, check router configurations.
3.
If you are using NetBIOS, use the
show netbios
name-cache
exec command to see whether traffic is passing
through the network properly. If it is not, check router
configurations.
For detailed information about configuring routers for RSRB,
refer to the Cisco IOS
Bridging and IBM Networking
Configuration Guide
and
Bridging and IBM Networking
Command Reference.
1.
LNM=LAN Network Manager
RSRB: Periodic Communication Failures
Symptom:
Communication failures occur periodically over a router configured as an RSRB.
