ES4710BD 10 Slots L2/L3/L4 Chassis Switch
DVMRP pruning debug is on
02:22:20:26: DVMRP: Received prune on vlan2 from 105.1.1.2, len 20
02:22:20:26: DVMRP: Prune Vers: majorv 3, minorv 255
02:22:20:26: DVMRP: Prune source 192.168.1.105, group 224.1.1.1
02:22:20:40: DVMRP: Received graft on vlan1 from 105.1.1.2, len 16
02:22:20:40: DVMRP: Graft Vers: majorv 3, minorv 255
02:22:20:40: DVMRP: Graft source 192.168.1.105, group 224.1.1.1
02:22:20:40: DVMRP: Send
02:22:20:40: DVMRP:
02:22:20:40: DVMRP:
19.5.4.2DVMRP Troubleshooting
In configuring and using DVMRP protocol, the DVMRP protocol may fail to run properly due to reasons such as physical connection failure or wrong configurations. The user should ensure the following:
Good condition of the physical connection.
All interface and link protocols are in the UP state (use “show interface” command).
Ensure the interface has an IP address properly configured (use “ip address” command).
Next, enable DVMRP on the interface (use the “ip dvmrp enable” command).
Multicast protocols use unicast routes to perform RPF check, for this reason, the unicast route correctness must be ensured. (DVMRP uses its own unicast route table, use the “show ip dvmrp route” command to view that table.)
If connectivity with CISCO is required, make sure the CISCO connex command is configured (use “ip dvmrp
If DVMRP problems persist after the abovementioned procedures, please run debug commands like “debug ip dvmrp detail/pruning”, and copy the debug information in 3 minute and send the information to
19.6IGMP
19.6.1Introduction to IGMP
IGMP (Internet Group Management Protocol) is a TCP/IP protocol responsible for IP multicast member management. It is used to establish and maintain multicast group membership between IP hosts and direct neighbor multicast switches. IGMP does not include the populating and maintenance of membership between multicast switches, which is covered by multicast routing protocols. All hosts participate in multicast must implement IGMP.
Hosts participate in IP multicast can join/quit multicast groups at any position, any time, and of any number. The multicast switches do not save all host memberships, which is also impractical. They just obtain information about whether receivers of a multicast group (group member) exist in
491