H3C Technologies H3C S7500E Series Switches - Manual (Page 168)

6-31
z You can configure these parameters at three levels: global configuration level, global scope
zone level, and admin-scope zone level.
z The value of these parameters configured at the global scope zone level or admin-scope
zone level have preference over the global values.
z
If you do not configure these parameters at the global scope zone level or admin-scope
zone level, 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 an
(S, G) entry is denied by the filtering rule, or the action for this entry is not defined in the filtering
rule, 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, this method of checksum calculation is not recommended.
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
formally starts receiving register messages with multicast data encapsulated from the multicast
source, the RP sends a register-stop message to the source-side DR. Upon receiving this
message, the DR stops sending register messages encapsulated with multicast data and starts
a register-stop timer. When 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 may 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 instance PIM view
or VPN instance PIM view
pim [ vpn-instance
vpn-instance-name ]
—