Troubleshooting IBM - Internetworking Troubleshooting - page 304

Table 10-17 outlines the problem that might cause this symptom and describes solutions to that problem.

Table10-2 CIP: Host Cannot Reach Remote Networks

Possible Problem Solution

Missing or
misconfigured IP
routes

1. If the mainframe host is incapable of communicating with
networks on the other side of the router, try to ping the
remote network from the router.
If the ping succeeds, proceed to Step 4.

If the ping fails, use the show ip route privileged exec
command to verify that the network is accessible by the
router.

2.

If there is no route to the network, check the network and
router configuration for problems.

3.

Verify that the host connection is active by pinging the host
IP address from the router. If the ping is unsuccessful, see
the section “CIP: Router Cannot ping Host, or Host Cannot
ping Router,” earlier in this chapter.

4.

Issue the netstat gate command on the host, and check for a
route to the network.

5.

If a route does not exist, make sure that the host is using the
address of the CIP in the router as the default route. If it is
not, add a GATEWAY statement in the TCP/IP profile that
points to the network, or set the CIP in the router as the
default route using a DEFAULTNET statement in the
TCP/IP profile.

6.

CIP: Host Running Routed Has No Routes

Symptom: A host running routed has no routes to remote networks.