JNCIP-ENT lab 9 of 19
Anycast RP and MSDP
Make the rendezvous point redundant: give two routers one RP address, share sources between them with anycast-pim, then do the same job with MSDP, while a real stream runs.
Run this lab
It needs Professional: its 6 nodes are set to 15 vCPU and 18,432 MB in total.
In your workspace: Shared, then JNCIP-ENT JN0-650 guided labs, then 09 - Anycast RP and MSDP
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 15 vCPU, 18,432 MB
- Smallest plan
- Professional
The scenario
The stream now works, but one RP is one point of failure, and a new source can't be found while that RP is down. Northmere wants two RPs that back each other up with no change on any other router. The answer is anycast RP: both RPs share one address, and unicast routing sends each router to the nearest. You'll build it two ways, with PIM's own anycast feature and then with MSDP, the protocol that joins RPs in separate domains. This time the source, H3, is behind R3, which isn't an RP, and the viewers are H1 and H2, one behind each RP.
| Device | Interface | Address | Link |
|---|---|---|---|
| R1 | ge-0/0/0, ge-0/0/1 | 10.0.12.1/30, 10.0.13.1/30 | To R2, to R3 |
| R1 | ge-0/0/2, lo0 | 10.1.1.1/24, 10.255.0.1/32 | H1's LAN |
| R2 | ge-0/0/0, ge-0/0/1 | 10.0.12.2/30, 10.0.23.1/30 | To R1, to R3 |
| R2 | ge-0/0/2, lo0 | 10.2.2.1/24, 10.255.0.2/32 | H2's LAN |
| R3 | ge-0/0/0, ge-0/0/1 | 10.0.13.2/30, 10.0.23.2/30 | To R1, to R2 |
| R3 | ge-0/0/2, lo0 | 10.3.3.1/24, 10.255.0.3/32 | H3's LAN |
| H1, H2, H3 | eth0 | 10.1.1.10, 10.2.2.10, 10.3.3.10 | Gateway is .1 on each LAN |
OSPF runs on all three routers, and PIM sparse mode runs on all interfaces. There's no RP yet.
What you’ll practise
- Configure a shared anycast address with a primary loopback
- Configure anycast RP with PIM
- Explain why RPs must share sources
- Peer RPs with MSDP and read Source-Active state
The tasks
- Give both RPs one address
- Share sources with anycast-pim
- Use MSDP in place of anycast-pim
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- R1
ge-0/0/0to R2ge-0/0/0 - R1
ge-0/0/1to R3ge-0/0/0 - R2
ge-0/0/1to R3ge-0/0/1 - R1
ge-0/0/2to H1eth0 - R2
ge-0/0/2to H2eth0 - R3
ge-0/0/2to H3eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| R2 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| R3 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| H1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| H2 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| H3 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIP-ENT JN0-650 guided labs.Open
09 - Anycast RP and MSDPand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More JNCIP-ENT labs
Related labs in other courses
CloudLabBox is independent of Cisco and Juniper Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.