42
SunFDDI/P 1.0 Adapter User’s Guide—May 1997
5
The local station cannot reach FDDI stations located
on a remote Ethernet network.
Check that the IP address and host name of the remote station
is entered in the NIS map or NIS+ tables (or in
/etc/hosts
on each remote station if you are not running NIS or NIS+).
If you are operating in a Solaris 2.x environment, which uses
MTU path discovery, check that packets are being transmitted
across the bridge between the networks. Many bridges do not
yet support MTU path discovery and do not fragment the
large packets sent by the FDDI stations. In this case you may
need to disable this feature on your station by typing:
# ndd —set /dev/ip ip_path_mtu_discovery 0
Check that the routing tables are using
netstat —r
. Check
for an
pf
interface that shows a route to a gateway with the
UG
flags set. If you can reach the local gateway, then the problem
probably lies with the IP routing.
Try to confirm that the remote station is configured and
running, and if possible try to reach the local station from the
remote station. If you can, it indicates that the problem lies
with the local IP routing.
Try to reach the router nearest the remote station. If you can, it
indicates that the fault lies between the remote station and the
router. If you cannot, try to reach a router that is closer to the
local station. Continue in this way until you have isolated the
router that is dropping or misrouting packets.
If the dynamic routing protocol is not adding routes, try
adding a static route to the remote station. This method is not
recommended for large networks with a large number of
nodes.
Running
pf_stat
with the
—m
option (to display
information about the neighboring stations) shows
frequent
error
frames and
lost
frames.
This could indicate a noisy network. For fiber connections,
noise is probably caused by dirt or grease on the optical
surface or by a damaged cable. Unshielded twisted-pair is
sensitive to electrical and electromagnetic interference. Note
that the receipt of
error
frames and
lost
frames does not
give any indication of where the problem is occurring on the
ring.
Table 5-2
Problems Running SunFDDI/P (Continued)
Problem
Action
Summary of Contents for 1.0
Page 13: ...Contents xiii Glossary 141 Index 147 ...
Page 14: ...xiv SunFDDI P 1 0 Adapter User s Guide May 1997 ...
Page 18: ...xviii SunFDDI P 1 0 Adapter User s Guide May 1997 ...
Page 25: ...Part1 InstallingandConfiguring SunFDDI P ...
Page 26: ......
Page 36: ...10 SunFDDI P 1 0 Adapter User s Guide May 1997 2 ...
Page 58: ...32 SunFDDI P 1 0 Adapter User s Guide May 1997 4 ...
Page 73: ...Part2 PlanningandImplementing SunFDDINetworks ...
Page 74: ......
Page 94: ...68 SunFDDI P 1 0 Adapter User s Guide May 1997 6 ...
Page 110: ...84 SunFDDI P 1 0 Adapter User s Guide May 1997 7 ...
Page 128: ...102 SunFDDI P 1 0 Adapter User s Guide May 1997 8 ...
Page 144: ...118 SunFDDI P 1 0 Adapter User s Guide May 1997 9 ...
Page 150: ...124 SunFDDI P 1 0 Adapter User s Guide May 1997 10 ...
Page 166: ...140 SunFDDI P 1 0 Adapter User s Guide May 1997 A ...
Page 172: ...146 SunFDDI P 1 0 Adapter User s Guide May 1997 ...
Page 182: ......