3Com S7902E, Configuration Manual

Page: 1050 / 2621

1-28
The group-address { mask | mask-length } parameter of the c-bsr group command can specify the
multicast groups the C-BSR serves, in the range of 239.0.0.0/8.
2) Configure C-BSRs for the global-scope zone
Perform the following configuration on the routers that will work as C-BSRs in the global-scope zone.
Follow these steps to configure a C-BSR for the global-scope zone:
To do… Use the command… Remarks
Enter system view system-view —
Enter public instance or VPN
instance PIM view pim [ vpn-instance
vpn-instance-name ]
—
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.
About the Hash mask length and C-BSR priority:
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