Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    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

    When you configure anycast RP, the RP routers in the PIM-SM domain use a shared address. In this example, the shared address is 10.1.1.2/32. Anycast RP uses Multicast Source Discovery Protocol (MSDP) to discover and maintain a consistent view of the active sources. Anycast RP also requires an RP selection method, such as static, auto-RP, or bootstrap RP. This example uses static RP and shows only one RP router configuration.

    Configuration

    CLI Quick Configuration

    To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

    RP Routers

    set interfaces lo0 unit 0 family inet address 192.168.132.1/32 primary set interfaces lo0 unit 0 family inet address 10.1.1.2/32 set protocols msdp local-address 192.168.132.1 set protocols msdp peer 192.168.12.1 set protocols pim rp local address 10.1.1.2 set routing-options router-id 192.168.132.1

    Non-RP Routers

    set protocols pim rp static address 10.1.1.2

    Step-by-Step Procedure

    The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.

    To configure anycast RP:

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

      [edit interfaces]user@host# set lo0 unit 0 family inet address 10.1.1.2/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.

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

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

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

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

      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 instructions in this example to correct the configuration.

    user@host# show interfaces
    lo0 {unit 0 {family inet {address 192.168.132.1/32 {primary;}address 10.1.1.2/32;}}}

    On the RP routers:

    user@host# show protocols
    msdp {local-address 192.168.132.1;peer 192.168.12.1;}
    pim {rp {local {address 10.1.1.2;}}}

    On the non-RP routers:

    user@host# show protocols
    pim {rp {static {address 10.1.1.2;}}}
    user@host# show routing-optionsrouter-id 192.168.132.1;

    Verification

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

    Modified: 2012-03-21