beautypg.com

Creating an rpf route, Network requirements – H3C Technologies H3C S7500E Series Switches User Manual

Page 101

background image

4-17

[SwitchA] interface vlan-interface 200

[SwitchA-Vlan-interface200] pim dm

[SwitchA-Vlan-interface200] quit

[SwitchA] interface vlan-interface 102

[SwitchA-Vlan-interface102] pim dm

[SwitchA-Vlan-interface102] quit

[SwitchA] interface vlan-interface 103

[SwitchA-Vlan-interface103] pim dm

[SwitchA-Vlan-interface103] quit

The configuration on Switch C is similar to the configuration on Switch A. The specific

configuration steps are omitted here.

# Use the display multicast rpf-info command to view the RPF route to Source on Switch B.

[SwitchB] display multicast rpf-info 50.1.1.100

RPF information about source 50.1.1.100:

RPF interface: Vlan-interface102, RPF neighbor: 30.1.1.2

Referenced route/mask: 50.1.1.0/24

Referenced route type: igp

Route selection rule: preference-preferred

Load splitting rule: disable

As shown above, the current RPF route on Switch B is contributed by a unicast routing protocol

and the RPF neighbor is Switch A.

3) Configure a multicast static route

# Configure a multicast static route on Switch B, specifying Switch C as its RPF neighbor on the

route to Source.

[SwitchB] ip rpf-route-static 50.1.1.100 24 20.1.1.2

4) Verify

the

configuration

# Use the display multicast rpf-info command to view the information about the RPF route to

Source on Switch B.

[SwitchB] display multicast rpf-info 50.1.1.100

RPF information about source 50.1.1.100:

RPF interface: Vlan-interface101, RPF neighbor: 20.1.1.2

Referenced route/mask: 50.1.1.0/24

Referenced route type: multicast static

Route selection rule: preference-preferred

Load splitting rule: disable

As shown above, the RPF route on Switch B has changed. It is now the configured multicast

static route, and the RPF neighbor is now Switch C.

Creating an RPF Route

Network requirements

z

PIM-DM runs in the network and all switches in the network support IP multicast.

z

Switch B and Switch C run OSPF, and have no unicast routes to Switch A.

z

Typically, Receiver can receive the multicast data from Source 1 in the OSPF domain.

z

Perform the following configuration so that Receiver can receive multicast data from

Source 2, which is outside the OSPF domain.