No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Maintaining Multicast Routes

Maintaining Multicast Routes

You can monitor multicast routing and forwarding, and configuring the maximum number of invalid IPv4 multicast protocol packets that a device can store.

Monitoring Multicast Routing and Forwarding

Context

During routine maintenance, run the following commands in any view to check the running status of the multicast forwarding and routing table.

Procedure

  • Run the display multicast boundary [ group-address [ mask | mask-length ] ] [ interface interface-type interface-number ] command to check information about the multicast boundary configured on an interface.
  • Run the display multicast ip fib [ group group-address | source source-address | incoming-interface { interface-type interface-number | register } ]* command to check the multicast forwarding table.
  • Run the display multicast routing-table [ group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } ] * [ outgoing-interface-number [ number ] ] command to check the multicast routing table.
  • Run the display multicast routing-table static [ config ] [ source-address { mask-length | mask } ] command to check the multicast static routing table.
  • Run the display multicast rpf-info source-address [ group-address ] [ rpt | spt ] [ verbose ] command to check the Reverse Path Forwarding (RPF) route.

Configuring the Maximum Number of Invalid IPv4 Multicast Protocol Packets that a Device 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 devices can store. Then you can check statistics and details about invalid multicast packets using related commands for troubleshooting.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    multicast invalid-packet { igmp | msdp | pim } max-count max-number

    The maximum number of invalid multicast protocol packets that the device can store is configured.

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

  3. Run:

    commit

    The configuration is committed.

Checking the Configuration

After completing the preceding configuration, you can 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 device can store.

  • Run the following commands to check the statistics about various invalid multicast protocol packets saved on the device:
    • Run the display igmp 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 device.

    • Run the display msdp 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 device.

    • Run the display pim invalid-packet [ interface interface-type interface-number | message-type { assert | bsr | hello | join-prune | offer | backoff | win | pass } ] * 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 device.

  • Run the following commands to check detailed information about specified number of latest invalid multicast protocol packets received by the device:
    • Run the display igmp invalid-packet [ packet-number ] verbose command to check details information about specified number of latest invalid IGMP packets received by the device.

    • Run the display msdp invalid-packet [ packet-number ] verbose command to check details information about specified number of latest invalid MSDP packets received by the device.

    • Run the display pim invalid-packet [ packet-number ] verbose command to check details information about specified number of latest invalid PIM packets received by the device.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 57523

Downloads: 3619

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next