Configuring the Maximum Number of Invalid IPv6 Multicast Protocol Packets That a Device Can Store

Context

If multicast forwarding entries cannot be established on a network, you can configure the maximum number of invalid IPv6 multicast protocol packets that the devices can store. Then you can check statistics and detailed information about invalid multicast protocol packets using related commands to troubleshoot problems.

Procedure

Run system-view
The system view is displayed.
Run multicast ipv6 invalid-packet { mld | pim } max-count max-number
The maximum number of invalid IPv6 multicast protocol packets that the device can store is configured.

By default, a device can store a maximum of 10 invalid IPv6 packets for each multicast protocol.

Verifying the Configuration

To check statistics about invalid IPv6 multicast protocol packets that the device stores, perform the following operations:

Run the display mld invalid-packet [ interface interface-type interface-number | message-type { done | query | report } ] ^* command to check statistics about invalid multicast listener discovery (MLD) packets that the device stores.
Run the display mld invalid-packet [ packet-number ] verbose command to check details about invalid MLD packets that the device stores.
Run the following commands in any view to check statistics about invalid IPv6 Protocol Independent Multicast (PIM) packets that the device stores.
- display pim ipv6 invalid-packet [ interface interface-type interface-number | message-type { assert | bsr | hello | join-prune | graft | graft-ack | state-refresh } ] ^*
- display pim ipv6 invalid-packet message-type { crp | register | register-stop }
Run the display pim ipv6 invalid-packet [ packet-number ] verbose command to check details about invalid IPv6 PIM packets that the device stores.