Configuring multicast source registration – H3C Technologies H3C S12500 Series Switches User Manual
Page 153

137
•
The values configured in the global-scoped zone or admin-scoped zone have preference over the
global values.
•
If you do not configure these parameters in the global-scoped zone or admin-scoped zone, the
corresponding global values will be used.
For configuration of global C-BSR parameters, see "
Configuring global C-BSR parameters
Configure C-BSRs for each admin-scoped zone and the global-scoped zone.
•
Configure C-BSRs for each admin-scoped zone:
Perform the following configuration on the routers that you want to configure as C-BSRs in
admin-scoped zones.
To configure a C-BSR for an admin-scoped zone:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter public network PIM
view or VPN instance PIM
view.
pim [ vpn-instance
vpn-instance-name ]
N/A
3.
Configure a C-BSR for an
admin-scoped zone.
c-bsr group group-address { mask
| mask-length } [ hash-length
hash-length | priority priority ] *
No C-BSRs are configured for an
admin-scoped zone by default.
The group-address { mask |
mask-length } argument of the
c-bsr group command can
specify the multicast groups to
which the C-BSR is designated,
in the range of 239.0.0.0/8.
•
Configure C-BSRs for the global-scoped zone:
Perform the following configuration on the routers that you want to configure as C-BSRs in the
global-scoped zone.
To configure a C-BSR for the global-scoped zone:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter public network PIM
view or VPN instance PIM
view.
pim [ vpn-instance
vpn-instance-name ]
N/A
3.
Configure a C-BSR for the
global-scoped zone.
c-bsr global [ hash-length
hash-length | priority priority ] *
No C-BSRs are configured for
the global-scoped zone by
default.
Configuring multicast source registration
Within a PIM-SM domain, the source-side DR sends register messages to the RP, and these register
messages have different multicast source or group addresses. You can configure a filtering rule to filter
register messages so that the RP can provide services for specific multicast groups. If the filtering rule
denies an (S, G) entry, or the filtering rule does not define the action for this entry, the RP will send a
register-stop message to the DR to stop the registration process for the multicast data.