Configuring the Maximum Number of Invalid IPv4 Multicast Protocol Packets That a Switch Can Store
Context
If multicast forwarding entries or Multicast Source Discovery Protocol (MSDP) peer relationships cannot be established on a network, you can configure the maximum number of invalid multicast protocol packets that the switch can store. Then check statistics and details about invalid multicast packets for troubleshooting.
Procedure
- Run the system-view command to enter the system view.
- Run the multicast invalid-packet { igmp | msdp | pim } max-count max-number command to set the maximum number of invalid
multicast protocol packets that the switch can store.
By default, a switch can store a maximum of 10 invalid packets for each multicast protocol.
Only the following versions and products support the mdt keyword.
Verifying the Configuration
After completing the configuration, run the following commands to check the maximum number of invalid IPv4 multicast protocol packets that can be saved and statistics about invalid multicast protocol packets:
Run the display current-configuration | include multicast invalid-packet command to check the maximum number of invalid multicast protocol packets that the switch can store.
- Run the following commands to check the statistics about various
invalid multicast protocol packets saved on the switch:
Run the display igmp [ vpn-instance vpn-instance-name | all-instance ] invalid-packet [ interface interface-type interface-number | message-type { leave | query | report } ] * command to check statistics about invalid Internet Group Management Protocol (IGMP) packets saved on the switch.
Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] invalid-packet [ peer peer-address | message-type { keepalive | notification | sa-request | sa-response | source-active } ] * command to check statistics about invalid MSDP packets saved on the switch.
Run the display pim [ vpn-instance vpn-instance-name | all-instance ] invalid-packet [ interface interface-type interface-number | message-type { assert | bsr | hello | join-prune | graft | graft-ack | state-refresh } ] * command or display pim invalid-packet message-type { crp | register | register-stop } command to check statistics about invalid Protocol Independent Multicast (PIM) packets saved on the switch.
- Run the following commands to check detailed information about
a specified number of latest invalid multicast protocol packets received
by the switch:
Run the display igmp invalid-packet [ packet-number ] verbose command to check details information about a specified number of latest invalid IGMP packets received by the switch.
Run the display msdp invalid-packet [ packet-number ] verbose command to check details information about a specified number of latest invalid MSDP packets received by the switch.
Run the display pim invalid-packet [ packet-number ] verbose command to check details information about a specified number of latest invalid PIM packets received by the switch.