Filter
Top Products
DVMRP Troubleshooting Troubleshooting DVMRP
page 15-4 OmniSwitch Troubleshooting Guide September 2005
192.168.10.1 1 No 1 Enabled Enabled
192.168.11.1 2 No 1 Enabled Enabled
192.168.12.1 3 No 1 Enabled Enabled
Remote routes will be seen if they are learned from another switch. Again be sure that the interfaces are
enabled. If that is the case it possible that the other switch is not configured correctly.
If the above commands look good in your switch and in the other switches you can use the following
command to see if the switch has a next hop. If it does the problem may not be this switch. It may be the
next switch on the VLAN indicated here.
-> show ip dvmrp nexthop
Src Address/Mask Vlan Hop Type
--------------------+-------+----------
192.168.10.25/24 2 branch
DVMRP Debug Commands
If you have looked at all the switches and you are sure you have configured correctly then it is time to use
the DVMRP Debug command.
-> show ip dvmrp debug
Debug Level = 1,
Error = on,
Flash = off,
Grafts = off,
IGMP = off,
Init = off,
IPMRM = off,
MIP = off,
Misc = off
Nbr = off,
Probes = off,
Prunes = off,
Routes = off,
Time = off,
TM = off,
Notice that by default the Debug Level is 1 and the only Debug Type configured is error messages. These
can be changed with the following commands.
-> ip dvmrp debug-type ?
^
TM TIME ROUTES PRUNES PROBES NBR MISC MIP IPMRM INIT
IGMP GRAFTS FLASH ERROR ALL
(IP Routing & Multicast Command Set)
-> no ip dvmrp debug-type ?
^
TM TIME ROUTES PRUNES PROBES NBR MISC MIP IPMRM INIT
IGMP GRAFTS FLASH ERROR ALL
(IP Routing & Multicast Command Set)
-> ip dvmrp debug-level 95
-> ip dvmrp debug-level 1
The first command turns on a debug-type while the second turns off a debug type.