Configuring multicast source registration – H3C Technologies H3C S10500 Series Switches User Manual

Page 171

Advertising
background image

156

To do…

Use the command…

Remarks

Configure a C-BSR for the
global-scope zone

c-bsr global [ hash-length
hash-length | priority priority ] *

Required
No C-BSRs are configured for the

global-scope zone by default.

NOTE:

You can configure the hash mask length and C-BSR priority globally, in an admin-scope zone, and in the
global scope zone.

The values configured in the global scope zone or admin-scope zone have preference over the global
values.

If you do not configure these parameters in the global scope zone or admin-scope zone, the
corresponding global values will be used.

For configuration of global C-BSR parameters, see “

Configuring global C-BSR parameters

.”

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 will send 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

method of checksum calculation.
When receivers stop receiving multicast data addressed to a certain multicast group through the RP (that

is, 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 multicast data) to the RP. If the DR receives a register-stop

message during the register probe time, it will reset its register-stop timer. Otherwise, the DR starts

sending register messages with encapsulated data again when the register-stop timer expires.
The register-stop timer is set to a random value chosen uniformly from the interval (0.5 times

register_suppression_time, 1.5 times register_suppression_time) minus register_probe_time.
Configure a filtering rule for register messages on all C-RP routers and configure them to calculate the

checksum based on the entire register messages. Configure the register suppression time and the register

probe time on all routers that might become source-side DRs.
Follow these steps to configure register-related parameters:

To do...

Use the command...

Remarks

Enter system view

system-view

Enter public network PIM view or
VPN instance PIM view

pim [ vpn-instance
vpn-instance-name ]

Advertising