Information Technology Reference
In-Depth Information
Table10-3
CIP: Host Running Routed Has No Routes (continued)
Possible Problem
Solution
RIP not properly
configured on the
router
(continued)
4.
If the command is present, remove it using the
no
passive-interface
router configuration command.
5.
Make sure there are no
distribute-list
statements filtering
RIP routing updates.
6.
Check the router configuration to be sure that the
broadcast
keyword has been specified in the
claw
interface
configuration command. The following is the
claw
command syntax:
claw
path device-address ip-address host-name device-name
host-app device-app
[
broadcast
]
Example:
The following example shows how to enable IBM channel-attach
routing on the CIP port 0, which is supporting a directly
connected ESCON channel:
interface channel 3/0
ip address 198.92.0.1 255.255.255.0
claw 0100 00 198.92.0.21 CISCOVM EVAL TCPIP TCPIP
If there is no
broadcast
keyword specified, add it to the
configuration.
7.
Host
misconfiguration
1.
Use the
netstat gate
command on the host. Check whether
there are routes learned from RIP updates.
2.
If you do not see RIP routes, verify that the host connection
is active by pinging the host IP address from the router.
3.
If the
ping
is unsuccessful, see the section “CIP: Router
Cannot
ping
Host, or Host Cannot
ping
Router,” earlier in
this chapter.
4.
Verify that the
routed
daemon is running on the host.
5.
Use the
show extended channel
slot/port
stat
exec
command to see whether RIP routing updates are
incrementing the counters.
6.
Check the TCP/IP profile on the host to be sure that there are
BSDROUTINGPARMS instead of GATEWAY statements.
