Before configuring assert control parameters, complete the following tasks:
When multiple PIM devices on a network segment pass the reverse path forwarding (RPF) check and forward multicast data to this network segment, assert election is required. When a device receives multicast data through a downstream interface, it knows that other upstream devices exist on this network segment. The device then sends an Assert message to compete with other upstream devices to forward multicast data.
PIM devices that fail the assert election disable their downstream interfaces from forwarding multicast data to this network segment. The assert loser state lasts for a period, which is called the holdtime of Assert messages. After the assert state timer times out, the devices that lost the Assert election restore pruned interfaces to the forwarding state to trigger a new round of Assert election.
The holdtime of Assert messages is configured globally or on an interface. If you configure the holdtime of Assert messages in the global PIM-IPv6 view and in the interface view simultaneously, the configuration in the interface view takes effect.
After assert control parameters are configured, check information about the IPv6 PIM interface, statistics about IPv6 PIM control messages, and IPv6 PIM routing table using the following commands:
Run the display pim ipv6 interface [ interface-type interface-number | up | down ] [ verbose ] command to check IPv6 PIM information on an interface.
Run the following commands in any view to check the number of sent and received IPv6 PIM control packets.
display pim ipv6 control-message counters message-type { probe | register | register-stop | crp }
display pim ipv6 control-message counters [ message-type { assert | graft | graft-ack | hello | join-prune | state-refresh | bsr } | interface interface-type interface-number ] *
Run the following commands to check the IPv6 PIM routing table.
display pim ipv6 routing-table brief [ ipv6-source-address [ mask mask-length ] | ipv6-group-address [ mask mask-length ] | incoming-interface { interface-type interface-number | register } ] *