Mld proxying configuration example, Network requirements – H3C Technologies H3C S7500E Series Switches User Manual

Page 348

Advertising
background image

12-28

Total 1 MLD SSM-mapping Group(s).

Interface group report information

Vlan-interface400 (4001::2):

Total 1 MLD SSM-mapping Group reported

Group Address: FF3E::101

Last Reporter: 4001::1

Uptime: 00:02:04

Expires: off

Use the display pim ipv6 routing-table command to view the IPv6 PIM routing table information on

each switch.

# Display the IPv6 PIM routing table information on Switch D.

[SwitchD] display pim ipv6 routing-table

Total 0 (*, G) entry; 2 (S, G) entry

(1001::1, FF3E::101)

Protocol: pim-ssm, Flag:

UpTime: 00:13:25

Upstream interface: Vlan-interface104

Upstream neighbor: 1003::1

RPF prime neighbor: 1003::1

Downstream interface(s) information:

Total number of downstreams: 1

1: Vlan-interface400

Protocol: mld, UpTime: 00:13:25, Expires: -

(3001::1, FF3E::101)

Protocol: pim-ssm, Flag:

UpTime: 00:13:25

Upstream interface: Vlan-interface103

Upstream neighbor: 3002::1

RPF prime neighbor: 3002::1

Downstream interface(s) information:

Total number of downstreams: 1

1: Vlan-interface400

Protocol: mld, UpTime: 00:13:25, Expires: -

MLD Proxying Configuration Example

Network requirements

z

IPv6 PIM-DM is required to run on the core network. Host A and Host C in the stub network

receive VOD information destined to multicast group FF3E::101.

z

It is required to configure the MLD proxying feature on Switch B so that Switch B can maintain

group memberships and forward IPv6 multicast traffic without running IPv6 PIM-DM.

Advertising