Sun Microsystems 3U - Manual (Page 126)

104 SunATM 3U CompactPCI Adapter Installation and User’s Guide • February 2001
8. Verify that addresses are resolved and connections are made with the ping(1M)
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 ARP requests are being sent to the server.
Find the server_vci in the output of aarstat . Then run atmstat , and verify
that there are outgoing packets on that VC. If not, make sure that your interface is
up and configured properly.
2. Make sure that you are receiving ARP responses from the server.
In the atmstat output, check the output packets for the server VC (found in the
aarstat information). If none are being received, your server is not responding
to ARP requests from the client. If it is a SunATM server, verify its Classical IP
status with the suggestions given here. If not, verify that it is up and running as a
server.
3. Make sure the address is resolved correctly.
Run the atmarp command for the system you are trying to ping , and verify that
its IP address has been resolved to the correct ATM address. If not, make sure that
the remote system is registering the correct address with the ATM ARP server. If
the address has not been resolved at all, make sure that the remote system has a
connection to the server.
4. 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. You should have at least one connection to the server, and you
should also 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).
5. 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