Sun Microsystems 3U - Manual (Page 129)

Appendix D Troubleshooting and SunATM Error Messages 107
7. Verify that addresses are resolved and connections are made with the ping
command.
Once you have two systems configured and running to this point, they should be
able to
ping each other. To ping client2 from client1:
If the ping is not successful:
1. Check that the IP hostname or address is resolved to a MAC address.
LAN Emulation requires two address resolution steps to make a call. The first is
to resolve an IP address to a MAC address. From the perspective of IP and ARP,
this works exactly as it does on an Ethernet interface; using the
arp command,
you can verify that this resolution has been made correctly. If it has not, verify the
connections to the BUS, and make sure data is being transmitted and received on
the connection(s) to the BUS by finding the VC in the output of
qccstat , and
looking at the statistics for that VC in atmstat .
2. Check that the MAC address has been resolved to an ATM address.
This is the second address resolution step, and is accomplished by the LAN
Emulation software and communication with the LES. You can use the
lanearp
command to verify that MAC addresses have been properly resolved to ATM
addresses. If they have not, verify the connections to the LES, and make sure data
is being transmitted and received on the connection(s) to the LES by finding the
VC in the output of
qccstat and looking at the statistics for that VC in atmstat .
3. Verify that a connection has been established between the two systems.
The output of qccstat lists the source and destination addresses of all open
connections. There you should see a connection to the remote host you are trying
to
ping . If not, make sure both interfaces are up and registered with the switch,
and that both interfaces and the switch are running UNI signalling (Q.2931 or
Q.93b).
4. Check for IP problems.
If the address has been resolved correctly, and a connection has been established
between the two systems, but they still cannot
ping , the problem is likely outside
the scope of ATM.
% ping client2
client2 is alive