JNCIP-ENT lab 10 of 19
SSM scoping and multicast policy
Take control of multicast: receive a channel with SSM and no RP, map an IGMPv2 host onto it, keep a group inside a scope, and refuse joins with IGMP and PIM policy.
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 10 - SSM scoping and multicast policy
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 15 vCPU, 18,432 MB
- Smallest plan
- Professional
The scenario
Now Northmere wants control. The video server should reach viewers with no RP at all, and viewers that can't speak IGMPv3 still need the stream. Some groups must stay inside the head office, a depot shouldn't be able to join certain groups, and one router should refuse joins for others. These are the multicast equivalents of routing policy. H1 is the source. H3 is behind R3, whose LAN runs IGMPv3, and H2 is behind R2, which runs the default IGMPv2. R2 is the 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 and PIM sparse mode are running, with R2 as the RP. R3's LAN starts at IGMPv3 so that H3 never falls back to version 2. A Linux host that hears a version 2 query stays in that mode for several minutes.
What you’ll practise
- Explain ASM and SSM, and use IGMPv3 channels
- Configure an SSM map
- Configure a multicast scope
- Filter with IGMP group policy and PIM import policy
The tasks
- Receive a channel with SSM
- Map an IGMPv2 host to a source
- Set a scope boundary
- Filter joins with IGMP and PIM policy
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
10 - SSM scoping and multicast policyand 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.