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 V200R013C00

This document describes the configurations of IP multicast, including IP multicast basics, IGMP, MLD, IPv4 PIM, IPv6 PIM, MSDP, multicast VPN, layer 3 multicast CAC, IPv4 multicast route management, IPv6 multicast route management, IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN replication, layer 2 multicast CAC, multicast network management.
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).
Configuring Basic IPv4 PIM-DM Functions

Configuring Basic IPv4 PIM-DM Functions

Pre-configuration Tasks

Before configuring basic PIM-DM functions, configure a unicast routing protocol to ensure normal unicast routing on the network. Because multicast devices do not maintain unicast routing information independently on the network, the devices must perform the RPF check on the received packets according to the unicast routing information on the network before creating PIM routing entries.

Context

PIM-DM and PIM-SM cannot be enabled simultaneously in the public network instance or VPN instances. Since PIM Hello packets do not carry messages in PIM mode, a PIM switch cannot know the mode of the PIM protocol that its PIM neighbor runs. If the RPF interface and the RPF neighbor run PIM protocols of different modes, two neighboring devices cannot learn PIM routing information from each other. As a result, related multicast forwarding entries cannot be correctly created.

It is recommended that you enable PIM-DM on all interfaces on a PIM-DM network, so that the interfaces can establish neighbor relationships with all connected PIM devices.

If PIM-DM and Internet Group Management Protocol (IGMP) need to be enabled on the same interface, enable PIM-DM before IGMP.

Procedure

  • Enable PIM-DM for a public network instance.
    1. Run system-view

      The system view is displayed.

    2. (Optional) Run set multicast forwarding-table super-mode

      The high specification mode is configured for multicast forwarding.

      In large-scale multicast applications, the switch generates a large number of PIM routing entries. When the number of PIM routing entries reaches the default limit, new PIM routing entries cannot be generated. The high specification mode increases the number of PIM routing entries supported on the switch to the maximum.

      NOTE:
      • The configuration of high specification mode takes effect after a restart.

      • Configuring the high specification mode increases the default interval for sending PIM-DM State-Refresh messages from 60s to 255s, and the default interval for sending PIM-DM Join/Prune messages from 210s to 300s.

    3. (Optional) Run assign multicast-resource-mode optimize

      The multicast replication capability of LPUs is improved.

      If the switch needs to replicate a huge number of multicast packets, run this command to improve the multicast replication capability before enabling IP multicast routing.

    4. Run multicast routing-enable

      IP multicast routing is enabled.

    5. Run interface interface-type interface-number

      The interface view is displayed.

    6. (Optional) On an Ethernet interface, run undo portswitch

      The interface is switched to Layer 3 mode.

      By default, an Ethernet interface works in Layer 2 mode.

    7. Run pim dm

      PIM-DM is enabled.

  • Enable PIM-DM for a VPN instance.

    A VPN instance must exist before you enable PIM-DM in it.

    1. Run system-view

      The system view is displayed.

    2. (Optional) Run set multicast forwarding-table super-mode

      The high specification mode is configured for multicast forwarding.

    3. (Optional) Run assign multicast-resource-mode optimize

      The multicast replication capability of LPUs is improved.

    4. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    5. Run ipv4-family

      The IPv4 address family is enabled for the VPN instance, and the VPN instance IPv4 address family view is displayed.

    6. Run route-distinguisher route-distinguisher

      An RD is configured for the VPN instance IPv4 address family.

    7. Run multicast routing-enable

      IP multicast routing is enabled.

    8. Run quit

      Return to the VPN instance view.

    9. Run quit

      Return to the system view.

    10. Run interface interface-type interface-number

      The interface view is displayed.

    11. Run ip binding vpn-instance vpn-instance-name

      The interface is associated with a specified VPN instance.

    12. Run pim dm

      PIM-DM is enabled.

Verifying the Configuration

After PIM-DM is enabled on all the interfaces in a PIM domain, use the following commands to check information about PIM interfaces, PIM neighbors, and PIM routing entries.

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface [ interface-type interface-number | up | down ] [ verbose ] command 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 PIM neighbors.

  • Run the following commands to check the PIM routing table:

    • Run the 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 ] ] command to check detailed information about the PIM routing table.

    • Run the 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 ] ] command to check detailed information about the PIM routing table.

    • Run the 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 } ] * command to check brief information about the PIM routing table.

Translation
Download
Updated: 2019-04-08

Document ID: EDOC1100065742

Views: 43421

Downloads: 40

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