zNetLaB › Guided labs › Enterprise
PIM sparse mode through a Junos RP
Enterprise Advanced 3 devices 2 checked tasks 100 points Plan lab
An IOS source and an IOS receiver sit on either side of a vMX. Make the vMX the rendezvous point and run PIM sparse mode so the receiver joined to 239.1.1.1 answers the source. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
An IOS source and an IOS receiver sit on either side of a vMX. Make the vMX the rendezvous point and run PIM sparse mode so the receiver joined to 239.1.1.1 answers the source.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 2 goals show as passed (100 points).
Network status
Devices: 3 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. S, M, O start with an empty configuration.
Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure.
Goals
M routes between the source and the receiver (20 pts) A ping from S to group 239.1.1.1 is answered by O (80 pts)
The activity, in order
M routes between the source and the receiver Address M on both links (10.1.0.2/24 towards S, 10.2.0.2/24 towards O); S and O point their default at M.Why: Each goal is a state the lab can check on the running device. Verify with: ping 10.2.0.1 A ping from S to group 239.1.1.1 is answered by O On M: set protocols pim rp local address 10.1.0.2 and both interfaces mode sparse. On S and O: multicast routing, PIM sparse mode on the link and the RP at 10.1.0.2; O joins 239.1.1.1.Why: Each goal is a state the lab can check on the running device. Verify with: ping 239.1.1.1 repeat 1
Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong.
Why this matters
An IOS source and an IOS receiver sit on either side of a vMX. Make the vMX the rendezvous point and run PIM sparse mode so the receiver joined to 239.1.1.1 answers the source.
What you will be able to do
M routes between the source and the receiver
A ping from S to group 239.1.1.1 is answered by O
The network
Catalyst 8000V, vMX — 3 devices in all, already cabled.
Gi1 ge-0/0/0 ge-0/0/1 Gi1 S M O Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
S Catalyst 8000V configure it
M vMX configure it
O Catalyst 8000V configure it
Cabling
S Gi1 ↔ M ge-0/0/0
M ge-0/0/1 ↔ O Gi1
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 M routes between the source and the receiver 20 On S: ping 10.2.0.1 must succeed.
2 A ping from S to group 239.1.1.1 is answered by O 80 On S: ping 239.1.1.1 repeat 1 output matches Reply to request \d+ from 10\.2\.0\.1.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
S ip multicast-routing distributed
ip pim rp-address 10.1.0.2
interface GigabitEthernet1
ip address 10.1.0.1 255.255.255.0
ip pim sparse-mode
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 10.1.0.2
O ip multicast-routing distributed
ip pim rp-address 10.1.0.2
interface GigabitEthernet1
ip address 10.2.0.1 255.255.255.0
ip pim sparse-mode
ip igmp join-group 239.1.1.1
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 10.2.0.2
M configure
set interfaces ge-0/0/0 unit 0 family inet address 10.1.0.2/24
set interfaces ge-0/0/1 unit 0 family inet address 10.2.0.2/24
set protocols pim rp local address 10.1.0.2
set protocols pim interface ge-0/0/0.0 mode sparse
set protocols pim interface ge-0/0/1.0 mode sparse
commit
exit
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.
Try the simulator in your browser, no sign-up