Filter
Top Products
RIP Troubleshooting Troubleshooting IP Routing
page 12-18 OmniSwitch Troubleshooting Guide September 2005
tRip-: in ripRdbLookup for 10.0.0.0 (255.0.0.0)
tRip-: ripSupply: Adding tuple(4) dst=10.10.41.57 mask=0.0.0.0
gw=0.0.0.0 met=16
tRip-: ripSupply: Forcing metric for 10.10.42.57 to INFINITY (split horizon)
tRip-: in ripRdbLookup for 10.0.0.0 (255.0.0.0)
tRip-: ripSupply: Adding tuple(5) dst=10.10.42.57 mask=0.0.0.0
gw=0.0.0.0 met=16
tRip-: ripSupply: Forcing metric for 10.10.42.159 to INFINITY (split horizon)
tRip-: in ripRdbLookup for 10.0.0.0 (255.0.0.0)
tRip-: ripSupply: Adding tuple(6) dst=10.10.42.159 mask=0.0.0.0
gw=0.0.0.0 met=16
tRip-: ripSupply: Forcing metric for 11.40.1.0 to INFINITY (split horizon)
tRip-: ripSupply: Adding tuple(7) dst=11.40.1.0 mask=0.0.0.0 gw=0.0.0.0
met=16
tRip-: ripSupply: Forcing metric for 11.40.117.0 to INFINITY (split horizon)
tRip-: ripSupply: Adding tuple(8) dst=11.40.117.0 mask=0.0.0.0
gw=0.0.0.0 met=16
tRip-: ripSupply: Forcing metric for 11.40.150.0 to INFINITY (split horizon)
tRip-: ripSupply: Adding tuple(9) dst=11.40.150.0 mask=0.0.0.0
gw=0.0.0.0 met=16
tRip-: ripSupply: Forcing metric for 11.41.117.0 to INFINITY (split horizon)
tRip-: ripSupply: Adding tuple(10) dst=11.41.117.0 mask=0.0.0.0
gw=0.0.0.0 met=16
tRip-: ripSupply: Forcing metric for 11.41.211.0 to INFINITY (split horizon)
tRip-: ripSupply: Adding tuple(11) dst=11.41.211.0 mask=0.0.0.0
gw=0.0.0.0 met=16
tRip-: ripSupply: Forcing metric for 192.168.10.0 to INFINITY (split horizon)
Notice that the routes received on the same interfaces are being sent out with metric of 16, split horizon.
tRip-:ripSupply: Adding tuple(12) dst=192.168.10.0 mask=0.0.0.0 gw=0.0.0.0
met=16
tRip-:ripSupply: Tx RESP ver=v1 dest=11.40.211.255 OutIf=11.40.211.4 dport=520
routes=12 len=244
tRip-:ripPeerAgeout: Currtime=72
This command is useful in understanding the protocol as well as troubleshooting the problem If one has
thorough understanding of the protocol then looking at this capture will help to identify the cause of the
problem.
If the advanced troubleshooting does not help to identify the cause of the problem kindly contact tech-
support for further troubleshooting.