Information Technology Reference
In-Depth Information
CIP: Router Cannot ping Host, or Host Cannot ping Router
Symptom:
Attempts to
ping
are unsuccessful, either from the CIP card in a router to a host or from a
host to the CIP card in a router.
Table 10-16 outlines the problem that might cause this symptom and describes solutions to that problem.
Table10-1
CIP: Router Cannot ping Host, or Host Cannot ping Router
Possible Problem
Solution
Addressing
problem between
CIP and host
1.
Verify that the CLAW connection is up by checking the
output of the
show extended channel
slot/port
statistics
exec command on the router.
2.
If the output shows that CLAW connections are not up
(indicated by an N), refer to the section “CIP: CLAW
Connection Does Not Come Up,” earlier in this chapter.
3.
If the CLAW connections are up (indicated by a Y), issue the
clear counters
privileged exec command. Then attempt a
basic
ping
to the host from the router or to the router from
the host.
4.
When the ping is completed, use the
show extended
channel
slot/port
statistics
exec command on the router.
If you issued the
ping
from the router to the host, the host should
have read five 100-byte ICMP echos from the router. The Total
Blocks field in the
show
command output should indicate five
blocks read. If the host replied, the output should indicate five
blocks written.
If you issued the
ping
from the host to the router, the host should
have sent one 276-byte ICMP echo to the router. The Write field
should indicate one block written. If the router replied, the output
should indicate one block in the Read field.
If this is not the case, there could be an addressing problem
between the CIP and the host. Check all IP addresses on the
router and in the host TCP/IP profile, and make sure that they
are correct.
5.
CIP: Host Cannot Reach Remote Networks
Symptom:
Mainframe host cannot access networks across a router.
