146
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-scope zone.
c-bsr group
group-address
{
mask
|
mask-length
}
[
hash-length
hash-length
|
priority
priority
] *
No C-BSRs are configured for an
admin-scope zone by default.
The
group-address
{
mask
|
mask-length
} argument can
specify the multicast groups the
C-BSR serves, in the range of
239.0.0.0/8.
•
Configure C-BSRs for the global-scope zone:
The following rules apply to the hash mask length and C-BSR priority:
{
You can configure these parameters globally, for an admin-scope zone, and for the global
scope zone.
{
The values of these parameters configured for the global scope zone or an admin-scope
zone have preference over the global values.
{
If you do not configure these parameters for the global scope zone or an admin-scope zone,
the corresponding global values are used.
For configuration of global C-BSR parameters, see "
Configuring the global C-BSR parameters
Perform the following configuration on the routers that you want to configure as C-BSRs in the
global-scope zone.
To configure a C-BSR for the global-scope 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-scope zone.
c-bsr global
[
hash-length
hash-length
|
priority
priority
] *
No C-BSRs are configured for the
global-scope 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 serve specific multicast groups. If the filtering rule denies
an (S, G) entry, or if the filtering rule does not define the action for this entry, the RP sends a
register-stop message to the DR to stop the registration process for the multicast data.
In view of information integrity of register messages in the transmission process, you can configure
the device to calculate the checksum based on the entire register messages. However, to reduce the
workload of encapsulating data in register messages and for the sake of interoperability, do not use
this checksum calculation method.
When receivers stop receiving multicast data addressed to a certain multicast group through the RP
(which means that the RP stops serving the receivers of that multicast group), or when the RP starts
receiving multicast data from the multicast source along the SPT, the RP sends a register-stop
message to the source-side DR. After receiving this message, the DR stops sending register
messages encapsulated with multicast data and starts a register-stop timer. Before the register-stop
timer expires, the DR sends a null register message (a register message without encapsulated
