Igmp proxying configuration example, Network requirements – H3C Technologies H3C S12500 Series Switches User Manual
Page 121

105
Group: 232.1.1.1
Source list:
133.133.1.1
133.133.3.1
# Display the IGMP group information created based on the IGMP SSM mappings on Switch D.
[SwitchD] display igmp ssm-mapping group
Total 1 IGMP SSM-mapping Group(s).
Interface group report information of VPN-Instance: public net
Vlan-interface400(133.133.4.2):
Total 1 IGMP SSM-mapping Group reported
Group Address Last Reporter Uptime Expires
232.1.1.1 133.133.4.1 00:02:04 off
# Display PIM routing table information on Switch D.
[SwitchD] display pim routing-table
Vpn-instance: public net
Total 0 (*, G) entry; 2 (S, G) entry
(133.133.1.1, 232.1.1.1)
Protocol: pim-ssm, Flag:
UpTime: 00:13:25
Upstream interface: Vlan-interface104
Upstream neighbor: 192.168.4.2
RPF prime neighbor: 192.168.4.2
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface400
Protocol: igmp, UpTime: 00:13:25, Expires: -
(133.133.3.1, 232.1.1.1)
Protocol: pim-ssm, Flag:
UpTime: 00:13:25
Upstream interface: Vlan-interface103
Upstream neighbor: 192.168.3.1
RPF prime neighbor: 192.168.3.1
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface400
Protocol: igmp, UpTime: 00:13:25, Expires: -
IGMP proxying configuration example
Network requirements
As shown in
, PIM-DM runs on the core network. Host A and Host C in the stub network receive
VOD information destined to multicast group 224.1.1.1.
Configure the IGMP proxying feature on Switch B so that Switch B can maintain group memberships and
forward multicast traffic without running PIM-DM.