Analyzing routing failures
Routing problems are the result of outages in a network and there are no alternative routing paths available for recovery. They can also be the result of incorrect configurations in the channel-attached and network-attached routers, as well as incorrect ARP entries, when applicable. PING and Traceroute commands to and from a z/OS® host are useful diagnosis aids for problem determination.
In this topic, unless otherwise specified, the following
command terms are used as described in Table 1.
| Term | Description |
|---|---|
| PING | Refers to z/OS UNIX oping, TSO PING, and the ping commands used on other platforms. |
| Traceroute | Refers to z/OS UNIX otracert|traceroute, TSO TRACERTE, and the traceroute commands used on other platforms. |
| NETSTAT ROUTE | Refers to the z/OS UNIX onetstat -r, TSO NETSTAT ROUTE, and the netstat route commands used on other platforms. |
| NETSTAT GATE | Refers to the z/OS UNIX onetstat -g and TSO NETSTAT GATE commands. This command is available only on the z/OS platform. |
| NETSTAT ARP | Refers to the z/OS UNIX onetstat -R ALL, TSO NETSTAT ALL, and the netstat arp commands used on other platforms. |
NCPROUTE routing failures are reported when a client is unable to get a positive response to a PING or Traceroute command for a remote host where there are NCPs acting as RIP servers along the routing paths.