Example: Configuring Multiple RPs in a Domain with Anycast RP

This example shows how to configure anycast RP on each RP router in the PIM-SM domain. With this configuration you can deploy more than one RP for a single group range. This enables load balancing and redundancy.

Requirements

Before you begin:

Overview

Anycast RP uses a shared anycast address across all the RP routers in the PIM-SM domain. This example uses 10.0.1.1/32 as the shared anycast address. Anycast RP works in conjunction with MSDP and an RP selection method, such as static, auto-RP, or bootstrap RP. This example uses static RP configuration. MSDP enables the RPs in the domain to maintain a consistent view of the active sources.

Configuration

CLI Quick Configuration

To quickly configure anycast RP on the RP routers, copy the following commands and paste them into the CLI.

[edit]set interfaces lo0 unit 0 family inet address 192.168.13.1/32 primary set interfaces lo0 unit 0 family inet address 10.0.1.1/32 set protocols msdp local-address 192.168.13.1 set protocols msdp peer 192.168.12.1 set protocols pim rp local address 10.0.1.1 set routing-options router-id 192.168.13.1

To configure anycast RP on the non-RP routers:

[edit]set protocols pim rp static address 10.0.0.1

Step-by-Step Procedure

To configure anycast RP:

  1. On each RP router in the domain, configure the shared anycast address on the router’s loopback address.

    [edit]user@host# edit interfaces[edit interfaces]user@host# set lo0 unit 0 family inet address 10.0.1.1/32
  2. On each RP router in the domain, make sure that the router’s regular loopback address is the primary address for the interface and set the router ID. This example shows only one RP router configuration.

    [edit interfaces]user@host# set lo0 unit 0 family inet address 192.168.13.1/32 primary[edit interfaces]user@host# exit[edit interfaces]user@host# edit routing-options[edit routing-options]user@host# set router-id 192.168.13.1[edit routing-options]user@host# exit
  3. On each RP router in the domain, configure the local RP address, using the shared address.

    [edit]user@host# edit protocols pim[edit protocols pim]user@host# set rp local address 10.0.1.1[edit protocols pim]user@host# exit
  4. On each RP router in the domain, create MSDP sessions to the other RPs in the domain.

    [edit]user@host# edit protocols msdp[edit protocols msdp]user@host# set local-address 192.168.13.1[edit protocols msdp]user@host# set peer 192.168.12.1[edit protocols msdp]user@host# exit
  5. On each non-RP router in the domain, configure a static RP address using the shared address.

    [edit]user@host# edit protocols pim[edit protocols pim]user@host# set rp static address 10.0.1.1[edit protocols pim]
  6. If you are done configuring the devices, commit the configuration.

    [edit protocols pim]user@host# commit

Results

From configuration mode, confirm your configuration by entering the show interfaces, show protocols, and show routing-options commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

user@host# show interfaceslo0 {unit 0 {family inet {address 192.168.13.1/32 {primary;}address 10.0.1.1/32;}}}

On the RP routers:

user@host# show protocolsmsdp {local-address 192.168.13.1;peer 192.168.12.1;}pim {rp {local {address 10.0.1.1;}}}

On the non-RP routers:

user@host# show protocolspim {rp {static {address 10.0.0.1;}}}
user@host# show routing-optionsrouter-id 192.168.13.1;

Verification

To verify the configuration, run the show pim rps extensive inet command.

Related Topics