175
1: Vlan-interface100
Protocol: pim-sm, UpTime: 00:00:42, Expires: 00:03:06
The information on Switch B and Switch C is similar to that on Switch A.
# Display PIM routing table information on Switch D.
[SwitchD] display pim routing-table
VPN-Instance: public net
Total 0 (*, G) entry; 1 (S, G) entry
(10.110.5.100, 225.1.1.0)
RP: 192.168.9.2
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 00:00:42
Upstream interface: Vlan-interface300
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface105
Protocol: pim-sm, UpTime: 00:00:42, Expires: 00:02:26
# Display PIM routing table information on Switch E.
[SwitchE] display pim routing-table
VPN-Instance: public net
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: Vlan-interface102
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 zone. Switch B, Switch C, and
Switch D are ZBRs of these 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 only Source 1, and Host B receives the multicast
information from only Source 2. Source 3 sends multicast information to multicast group
224.1.1.1. Host C is a multicast receiver for this multicast group.
