Mld proxying configuration example, Network requirements, Configuration procedure – H3C Technologies H3C SecPath F1000-E User Manual

Page 939

Advertising
background image

914

1: GigabitEthernet0/1

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

(3001::1, FF3E::101)

Protocol: pim-ssm, Flag:

UpTime: 00:13:25

Upstream interface: GigabitEthernet0/2

Upstream neighbor: 3002::1

RPF prime neighbor: 3002::1

Downstream interface(s) information:

Total number of downstreams: 1

1: GigabitEthernet0/1

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

MLD proxying configuration example

Network requirements

As shown in

Figure 404

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

stub network receive VOD information sent to multicast group FF3E::101.
Configure the MLD proxying feature on SecPath so that SecPath can maintain group memberships and
forward IPv6 multicast traffic without running IPv6 PIM-DM.

Figure 404 Network diagram

Configuration procedure

1.

Enable IPv6 forwarding and configure the IPv6 addresses:
Enable IPv6 forwarding on the router and the firewall, and configure the IPv6 address and prefix
length of each interface as per

Figure 404

. (Details not shown.)

2.

Enable IPv6 multicast routing, IPv6 PIM-DM, MLD, and MLD proxying respectively:
# Enable IPv6 multicast routing on the Router, IPv6 PIM-DM on Serial 2/1, and MLD on
GigabitEthernet 1/1.

<Router> system-view

[Router] multicast ipv6 routing-enable

[Router] interface serial 2/1

Proxy & Querier

SecPath

Querier

Router

Host B

Receiver

Host A

Receiver

Host C

GE1/1

2001::1/64

GE0/1
2001::2/64

GE0/2

3001::1/64

S2/1
1001::1/64

IPv6 PIM-DM

Advertising