Troubleshooting
Diagnostic Flowcharts
Flowchart 1 ProceduresA. | Execute: ping to remote host.Using ping(1M), send |
| a message to the remote host to which you are having |
| problems connecting. For example: |
| ping spiff |
B. | ping successful? A message is printed to stdout for |
| each ping packet returned by the remote host. If |
| packets are being returned, your system has network |
| level connectivity to the remote host. Note what |
| percentage of the total packets are lost, if any. Losing |
| ten percent or more may indicate the network or |
| remote host is extremely busy. You may also find it |
| useful to note the |
| Periodically high transmission times may indicate that |
| the network or remote host is extremely busy. |
| Consistently high transmission times may indicate the |
| local host is extremely busy. If a message is not |
| returned after executing ping, ping is not successful. |
| Do Cntrl C to stop the ping output. |
C. | Network unreachable? If yes, go to flowchart 3 to |
| display connection status using the lanscan(1M) |
| command. |
D. | Command hangs. If a message is not returned after |
| executing ping, go to flowcharts 2 through 7, referring |
| back to flowchart 1 (ping) until you have corrected the |
| problem. |
E. | Unknown host? If you receive this message, go to step |
| F. |
F. | Correct BIND, YP or hosts configuration. Add the |
| missing host name and start again with flowchart 1. |
G. | No route to host? If Error= Sendto: No route to |
| host, go to Step H. Otherwise, call your HP |
| representative for help. |
H.Add route table entry. Using route, add a route table entry for that host. Refer to the route(1M) online man page for more details. Start again with flowchart 1.
Chapter 4 | 59 |