HP A5500 EI Switch Series, Configuration Manual

Page: 368 / 443

356
admin-scope zone. All the routers use the same hash algorithm to get the RP address corresponding to
the specific IPv6 multicast group.
Perform the following configuration on the routers that will work as C-BSRs in IPv6 admin-scope zones.
Follow these steps to configure a C-BSR for an IPv6 admin-scope zone:
To do… Use the command… Remarks
Enter system view system-view —
Enter IPv6 PIM view pim ipv6 —
Configure a C-BSR for an IPv6
admin-scope zone
c-bsr scope { scope-id | admin-
local | global | organization-local
| site-local } [ hash-length hash-
length | priority priority ] *
Required
No C-BSRs are configured for an
IPv6 admin-scope zone by
default.
NOTE:
The following points apply to the hash mask length and C-BSR priority:
•
You can configure these parameters at global configuration level and IPv6 admin-scope zone level.
•
Values configured at the IPv6 admin-scope zone level take preference.
•
If no parameters are configured at the IPv6 admin-scope zone level, the corresponding global values
will be used.
For configuration of global C-BSR parameters, see “ Configuring C-BSR parameters globally .”
Configuring IPv6 multicast source registration
Within an IPv6 PIM-SM domain, the source-side DR sends register messages to the RP, and these register
messages have different IPv6 multicast source or IPv6 multicast group addresses. You can configure a
filtering rule to filter register messages so that the RP can serve specific IPv6 multicast groups. If the
filtering rule denies an (S, G) entry, or if the filtering rule does not define an action for this entry, the RP
will send a register-stop message to the DR to stop the registration process for the IPv6 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, HP does not
recommend this method of checksum calculation.
When receivers stop receiving data addressed to a certain IPv6 multicast group through the RP—that is,
the RP stops serving the receivers of that IPv6 multicast group, or when the RP formally starts receiving
register messages with IPv6 multicast data encapsulated from the IPv6 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 IPv6 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.