Configuring an RP

Context

A rendezvous point (RP) can be configured manually or elected through the bootstrap router (BSR) mechanism. Manually configuring a static RP reduces bandwidth use for information exchange between the C-RPs and BSR. RP election through the BSR mechanism simplifies configuration and improves reliability of multicast forwarding because multiple C-RPs are configured.

You can configure a static RP and multiple candidate rendezvous points (C-RPs) for dynamic RP election. The static RP functions as a backup RP because it has a lower priority. Ensure that all the devices on the network have the same RP information. Inconsistent RP information may cause forwarding failures on the network.

Default Settings

Table 1 lists the default settings of the C-BSR and C-RP.

**Table 1** Default settings of the C-BSR and C-RP
Parameter	Default Setting
C-BSR priority	0
C-BSR hash mask length	30
BSR message fragmentation	Disabled
Multicast group policy of a static RP	No multicast group policy configured (accepts multicast data with any group address)
Multicast group policy of a C-RP	No multicast group policy configured (accepts multicast data with any group address)
C-RP priority	0
Interval for sending C-RP Announcement messages	60s
Hold time of C-RP Announcement messages	150s

Procedure

Configure a static RP.
1. Run system-view
  The system view is displayed.
2. Run pim [ vpn-instance vpn-instance-name | all-instance ]
  The PIM view is displayed.
3. Run static-rp rp-address [ basic-acl-number ] [ preferred ]
  Address of a static RP is specified.
  - All devices in the PIM-SM domain must be configured with the same static RP address.
  - If the preferred keyword is not used when you configure the static RP, the switch prefers the dynamic RP elected through the BSR mechanism. The switch prefers the static RP only when you specify the preferred keyword in the static-rp command.
  - If multiple static RPs are available for a multicast group, the RP with the largest IP address serves the group.
  - If an ACL is specified in the command, the static RP serves only the groups permitted by the ACL.
Configure a dynamic RP.
1. Configure a C-BSR.
  1. Run system-view
    
    The system view is displayed.
  2. Run pim [ vpn-instance vpn-instance-name | all-instance ]
    
    The PIM view is displayed.
  3. Run c-bsr interface-type interface-number [ hash-length [ priority ] ]
    
    A C-BSR is configured.
    
    It is recommended that you configure the C-BSR on the device that aggregates multicast data.
    
    To avoid frequent protocol changes caused by interface flapping, using loopback interfaces is recommended.
  4. (Optional) Run bsm semantic fragmentation
    
    The BSR message fragmentation function is enabled.
    
    BSR message fragmentation solves the problem in IP fragmentation, where all fragments become unavailable due to loss of fragment information. Enable BSR message fragmentation on all devices. Otherwise, devices that do not fragment BSR messages may receive incomplete RP information.
2. Configure a C-RP.
  1. Run system-view
    
    The system view is displayed.
  2. Run pim [ vpn-instance vpn-instance-name | all-instance ]
    
    The PIM view is displayed.
  3. Run c-rp interface-type interface-number [ group-policy basic-acl-number | priority priority | holdtime hold-interval | advertisement-interval adv-interval ]^*
    
    A C-RP is configured.
    
    It is recommended that you configure the C-RP on the device that aggregates multicast data.
    
    To avoid frequent protocol changes caused by interface flapping, using loopback interfaces is recommended.
3. (Optional) Configure a BSR boundary.
  1. Run system-view
    
    The system view is displayed.
  2. Run interface interface-type interface-number
    
    The interface view is displayed.
  3. (Optional) On an Ethernet interface, run undo portswitch
    
    The interface is switched to Layer 3 mode.
    
    By default, an Ethernet interface works in Layer 2 mode.
  4. Run pim bsr-boundary
    
    A BSR service boundary is configured.
    
    The BSR messages cannot pass through the BSR boundary. Therefore, it is recommended that you configure the BSR service boundary on interfaces at the edge of a PIM-SM domain.