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

Configuration Guide - IP Multicast

S7700 and S9700 V200R010C00

This document describes IP multicast basics and how to configure IP multicast features, including IGMP/MLD, PIM (IPv4&IPv6), MSDP, multicast VPN, Layer 3 multicast CAC, Layer 2 multicast CAC, IGMP/MLD snooping, and multicast VLAN, IPv4&IPv6 multicast route management, static multicast MAC address, multicast network.
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 PIM-SM

Maintaining PIM-SM

Clearing Statistics About PIM Control Packets

Context

To recollect statistics about PIM control packets, clear the existing statistics. The statistics cannot be restored after you clear them. This operation does not affect normal running of PIM.

Statistics about PIM control packets on an interface cannot be restored after you clear them. Exercise caution when clearing the statistics.

Procedure

  • Run the reset pim [ vpn-instance vpn-instance-name | all-instance ] control-message counters [ interface interface-type interface-number ] command in the user view to clear statistics about PIM control packets on an interface.

Clearing the PIM Status of the Specified Downstream Interfaces in PIM Entries

Context

You can clear the PIM status on the specified downstream interface in a PIM entry. IGMP status and static groups on this interface are not affected.

Clearing the PIM status of downstream interfaces will trigger the sending of Join/Prune packets, which affects multicast services.

Procedure

  • To clear the PIM status of specified downstream interfaces in specified PIM entries, run the reset pim [ vpn-instance vpn-instance-name ] routing-table group group-address mask { group-mask-length | group-mask } source source-address interface interface-type interface-number command in the user view.

Monitoring the Running Status of PIM

Context

During routine maintenance, you can run the following commands in any view to monitor the running status of PIM.

Procedure

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] claimed-route [ source-address ] command to check unicast routes used by PIM.
  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] bfd session [ interface interface-type interface-number | neighbor neighbor-address ] * command to check the PIM BFD session.
  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] bsr-info command in any view to check information about the BSR in the PIM-SM domain.
  • Run the following commands to check the number of sent and received PIM control packets.

    • display pim [ vpn-instance vpn-instance-name | all-instance ] control-message counters message-type { probe | register | register-stop | crp }

    • display pim [ vpn-instance vpn-instance-name | all-instance ] control-message counters [ message-type { assert | graft | graft-ack | hello | join-prune | state-refresh | bsr } | interface interface-type interface-number ] *

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface [ interface-type interface-number | up | down ] [ verbose ] command in any view to check PIM information on an interface.
  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] neighbor [ neighbor-address | interface interface-type interface-number | verbose ] * command to check information about the PIM neighbor.
  • Run the following commands to check the PIM routing table.

    • display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ]

    • display pim routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | vpn-instance vpn-instance-name | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ]

    • display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table brief [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type interface-number | register } ] *

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] rp-info [ group-address ] command to check information about RPs of the multicast group.
  • 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 to check the statistics about the invalid PIM packets received by the device.
Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000141903

Views: 152023

Downloads: 111

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