Pim-sm admin-scope zone configuration example, Network requirements – H3C Technologies H3C SecPath F1000-E User Manual
Page 140
44
Total 1 (*, G) entry; 0 (S, G) entry
(*, 225.1.1.0)
RP: 192.168.9.2 (local)
Protocol: pim-sm, Flag: WC
UpTime: 00:13:16
Upstream interface: Register
Upstream neighbor: 192.168.4.2
RPF prime neighbor: 192.168.4.2
Downstream interface(s) information:
Total number of downstreams: 1
1: GigabitEthernet3/2
Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22
PIM-SM Admin-Scope Zone Configuration Example
Network requirements
•
As shown in
, receivers receive VoD information through multicast. The entire PIM-SM
domain is divided into admin-scope zone 1, admin-scope zone 2, and the global scope zone.
Device B, Device C, and Device D are ZBRs of the three domains respectively.
•
Source 1 and Source 2 send different multicast information to multicast group 239.1.1.1. Host A
receives the multicast information from Source 1 only, while Host B receives the multicast
information from Source 2 only. Source 3 sends multicast information to multicast group 224.1.1.1.
Host C is a multicast receiver for this multicast group.
•
GigabitEthernet 2/1 of Device B acts as a C-BSR and C-RP of admin-scope zone 1, which serve the
multicast group range 239.0.0.0/8. GigabitEthernet 2/1 of Device D acts as a C-BSR and C-RP of
admin-scope zone 2, which also serve the multicast group range 239.0.0.0/8. GigabitEthernet
2/1 of Device F acts as a C-BSR and a C-RP of the global scope zone, which serve all the multicast
groups other than those in the 239.0.0.0/8 range.
•
IGMPv2 is required between Device A, Device E, Device I and their respective receivers.