Filter
Top Products
Troubleshooting IP Routing RIP Troubleshooting
OmniSwitch Troubleshooting Guide September 2005 page 12-15
10.10.42.159 255.255.255.255 11.41.211.1 2
11.40.117.0 255.255.255.0 11.40.211.1 2
11.40.150.0 255.255.255.0 11.40.150.1 1
11.40.211.0 255.255.255.0 11.40.211.4 1
11.41.117.0 255.255.255.0 11.41.211.1 2
11.41.211.0 255.255.255.0 11.41.211.4 1
192.168.10.0 255.255.255.0 11.40.150.100 2
Notice, that route 6.0.0.0 and 8.0.0.0 appears with the natural subnet mask, even though it is configured to
be class C mask. This is because RIP v1 does not advertise the mask and router always assume the natural
mask.
9.9.1.0 appears with a class C mask because it is locally defined network on the switch. If the protocol
used was RIP v2 then the routing tables will be as follows:
-> show ip rip routes
Destination Mask Gateway Metric
------------------+------------------+------------------+-------
0.0.0.0 0.0.0.0 11.41.211.1 2
6.0.0.0 255.255.255.0 9.9.1.2 2
8.0.0.0 255.255.255.0 11.40.150.100 2
9.9.1.0 255.255.255.0 9.9.1.1 1
10.10.41.57 255.255.255.255 11.40.211.1 2
10.10.42.57 255.255.255.255 11.41.211.1 2
10.10.42.159 255.255.255.255 11.41.211.1 2
11.40.117.0 255.255.255.0 11.40.211.1 2
11.40.150.0 255.255.255.0 11.40.150.1 1
11.40.211.0 255.255.255.0 11.40.211.4 1
11.41.117.0 255.255.255.0 11.41.211.1 2
11.41.211.0 255.255.255.0 11.41.211.4 1
192.168.10.0 255.255.255.0 11.40.150.100 2
At this point the route tables should be coherent and the end users should be able to reach any portion of
the network.
In case of any RIP problems debug CLI commands can be used to troubleshoot the protocol. By default,
debug of RIP is disabled with the debug-level of 0. The debug levels set by default can be seen by the
following command:
-> show ip rip debug
Debug Level = 0
Types/Sections
error = on
warning = off
recv = off
send = off
rdb = off
age = off
config = off
redist = off
info = off
setup = off
time = off
In case of any problems with protocol operation of RIP different kinds of debug messages can be turned
on to look at the protocol operations being performed by the switch. Debug level 255 is the highest.
Following is the details of the different debug-types: