659
Switch(Config-if-Vlan1)# ip address 12.1.1.2 255.255.255.0
Switch(Config-if-Vlan1)# ip dvmrp
Switch(Config-if-Vlan1)#exit
Switch (Config)#interface vlan 2
Switch(Config-if-Vlan2)# ip address 20.1.1.1 255.255.255.0
Switch(Config-if-Vlan2)# ip dvmrp
Since DVMRP itself does not rely on Unicast Routing Protocol, it is not necessary to
configure Unicast Routing Protocol. This is the difference from PIM-DM and PIM-SM.
17.4.5 DVMRP TroubleShooting
In configuring and using DVMRP Protocol, DVMRP Protocol might not operate
normally caused by physical connection or incorrect configuration. Therefore, the user
should pay attention to the following issues:
Firstly to assure that physical connection is correct.
Next, to assure the Protocol of Interface and Link is UP (use show interface
command);
Please check if the correct IP address is configured on the interface (use
ip address
command)
Afterwards,
enable
DVMRP
Protocol on the interface (use
ip dvmrp
command and
ip dv multicast-routing
command)
Multicast Protocol requires RPF Check using unicast routing; therefore the
correctness of unicast routing must be assured beforehand.(DVMRP uses its own
unicast table, please use show ip dvmrp route command to look up);
If all attempts including Check are made but the problems on DVMRP can’t be
solved yet, then please use commands such as debug dvmrp, and then copy DEBUG
information in 3 minutes and send to Technology Service Center.
17.4.5.1 Monitor And Debug Command
17.4.5.1.1 debug dvmrp
Command: debug dvmrp [events[neighbor|packet|igmp|kernel|prune [detail]
|route]| nsm|mfc|mib
|
timer [probe[probe-timer|neigbor-expiry-timer]|
prune[prune-expiry-timer|prune-retx-timer|graft-retx-timer]|route[report-t
imer|flash-upd-timer|route-expirytimer|route-holdown-timer|route-burst-t
imer]]|packet[[probe [in|out] | report [in|out | prune [in|out] raft [in|out] |
graft-ack [in|out] |in|out]]|all]
no debug dvmrp [events[neighbor|packet|igmp|kernel|prune [detail]