The possible causes are:

•  No RP is configured on the PIM-SM network. In this case, configure a static RP or configure C-RPs to implement dynamic RP election.

•  The multicast source or RP is route unreachable. In this case, configure a unicast routing protocol to enable the network devices to learn the routes to the multicast source or RP.

ps. static-rp (IPv4)

Function

Using the static-rp command, you can configure a static RP.

Using the undo static-rp command, you can restore the default configuration.

By default, no static RP is configured.

Format

static-rp rp-address basic-acl-number [ preferred ]

undo static-rp rp-address

good to know

Configuring a C-RP

To configure a C-RP, you need to configure the address of the loopback interface as the RP address on the device to be configured with anycast RP.

Context

http://127.0.0.1:52199/hedex/pages/DE107063/01%20(2010-06-28)/DE107063/01%20(2010-06-28)/resources/public_sys-resources/icon-note.gif NOTE:

• If the PIM-SM network uses a static RP, the configuration is not necessary.

• If the PIM-SM network uses a BSR-RP, the configuration is mandatory. Before configuring a C-RP, configure a BSR and BSP boundary. The BSR addresscannot be the same as the C-RP address.

Do as follows on multiple switchs on which an anycast RP is to be configured in the PIM-SM domain:

Procedure

1. Run:

   system-view

   The system view is displayed.

   
   

2. Run:

   pim [ vpn-instance vpn-instance-name ]

   The PIM view is displayed.

   
   

3. Run:

   c-rp loopback interface-number

   An interface is specified as RP.