HCIP-Datacom Core lab 9 of 14
Multicast with IGMP and PIM-SM
Stream to a group across three routers: PIM-SM with a static RP, IGMP on the receiver LAN, the shared tree, the switch to the shortest-path tree, then a dynamic RP with BSR. A real sender and receiver prove it.
Run this lab
It needs Standard: its 5 nodes are set to 5 vCPU and 8,192 MB in total. That fits the free demo too.
In your workspace: Shared, then HCIP-Datacom Core H12-821 guided labs, then 09 - Multicast with IGMP and PIM-SM
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 5 vCPU, 8,192 MB
- Smallest plan
- Standard
The scenario
Northwind's head office streams its all-hands to every site, one copy per viewer, and the Leeds link is full by the second speaker. Multicast sends one copy and branches it only where it's wanted. H1 is the streaming server, H2 stands for the Leeds viewers, and R2 sits in the middle of the network as the natural meeting point. OSPF is running. Your job is the multicast layer.
| Device | Addresses |
|---|---|
| R1 | LoopBack0 1.1.1.1, GE0/0/0 10.0.12.1/24, GE0/0/1 10.0.13.1/24, GE0/0/2 10.1.1.1/24 (H1) |
| R2 | LoopBack0 2.2.2.2, GE0/0/0 10.0.12.2/24, GE0/0/1 10.0.23.2/24 |
| R3 | LoopBack0 3.3.3.3, GE0/0/0 10.0.13.3/24, GE0/0/1 10.0.23.3/24, GE0/0/2 10.3.3.1/24 (H2) |
| H1 | 10.1.1.10, sends to 239.1.1.1 with /root/mcsend.py |
| H2 | 10.3.3.10, joins 239.1.1.1 with /root/mcrecv.py |
Both scripts are ordinary Python sockets, already on the hosts. The receiver shows each frame as it arrives.
What you’ll practise
- Explain groups, IGMP, RPF, the RP and the two kinds of tree
- Enable multicast routing and PIM-SM
- Configure a static RP and then a dynamic one with BSR
- Read (*,G) and (S,G) entries, and the upstream neighbour in each
- See the shared tree give way to the shortest-path tree
The tasks
- Task 0: Load the starting configuration
- Concept: how multicast finds its way
- Task 1: Turn on multicast and PIM-SM
- Task 2: Set a static RP
- Concept: IGMP
- Task 3: Join the group from H2
- Concept: the shortest-path tree
- Task 4: Start the stream
- Concept: finding the RP automatically
- Task 5: Replace the static RP with BSR
- Task 6: Finish the move
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
GE0/0/0to R2GE0/0/0 - R1
GE0/0/1to R3GE0/0/0 - R2
GE0/0/1to R3GE0/0/1 - R1
GE0/0/2to H1eth0 - R3
GE0/0/2to H2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| R2 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| R3 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 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 |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
HCIP-Datacom Core H12-821 guided labs.Open
09 - Multicast with IGMP and PIM-SMand 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 HCIP-Datacom Core labs
Related labs in other courses
CloudLabBox is independent of Huawei. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.