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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of IP multicast, including IP multicast basics, IGMP, MLD, PIM (IPv4), PIM (IPv6), MSDP, multicast VPN, multicast route management (IPv4), multicast route management (IPv6), IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN, 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 IPv4 PIM-SM in the SSM Model

Configuring IPv4 PIM-SM in the SSM Model

Context

A PIM-SM network uses the Source-Specific Multicast (SSM) model to provide specified multicast services for user hosts. User hosts in a multicast group can receive multicast data sent from the specified multicast source to this group.

Pre-configuration Tasks

Before configuring PIM-SM in the SSM model, configure a unicast routing protocol to ensure that unicast routes on the network are reachable.

Configuration Procedure

Enabling PIM-SM is a mandatory procedure. Configuring an SSM group policy can control the address range of SSM groups. This operation is optional.

Enabling PIM-SM

Context

It is recommended that you enable PIM-SM on all interfaces in a PIM-SM domain to ensure that the interfaces can establish neighbor relationships with all connected PIM devices.

Procedure

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

      The system view is displayed.

    2. Run multicast routing-enable

      IP multicast routing is enabled.

    3. Run interface interface-type interface-number

      The interface view is displayed.

    4. 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.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    5. For a Layer 3 sub-interface, run the following commands to configure termination of single-tagged packets on it.

      1. Run quit

        Return to the system view.

      2. Run interface interface-type interface-number.subinterface-number

        The Layer 3 sub-interface view is displayed.

        The subinterface-number parameter must specify a Layer 3 sub-interface number on an Ethernet interface that has been switched to the Layer 3 mode.

      3. Run dot1q termination vid vid

        Termination of Dot1q packets is configured on the Layer 3 sub-interface.

        By default, the termination of Dot1q packets is not configured on a Layer 3 sub-interface.

    6. Run pim sm

      PIM-SM is enabled.

    7. Run commit

      The configuration is committed.

  • Enable PIM-SM for a VPN instance.

    A VPN instance must exist before you enable PIM-SM in the VPN instance.

    1. Run system-view

      The system view is displayed.

    2. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    3. Run ipv4-family

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

    4. Run route-distinguisher route-distinguisher

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

      A VPN instance IPv4 address family takes effect only after being configured with an RD. The RDs of different VPN instances on a PE must be different.

    5. Run multicast routing-enable

      IP multicast routing is enabled.

    6. Run quit

      Return to the VPN instance view.

    7. Run quit

      Return to the system view.

    8. Run interface interface-type interface-number

      The interface view is displayed.

    9. 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.

      The mode switching function takes effect when the interface only has attribute configurations (for example, shutdown and description configurations). Alternatively, if configuration information supported by both Layer 2 and Layer 3 interfaces exists (for example, mode lacp and lacp system-id configurations), no configuration that is not supported after the working mode of the interface is switched can exist. If unsupported configurations exist on the interface, delete the configurations first and then run the undo portswitch command.

      NOTE:

      If many Ethernet interfaces need to be switched to Layer 3 mode, run the undo portswitch batch interface-type { interface-number1 [ to interface-number2 ] } &<1-10> command in the system view to switch these interfaces to Layer 3 mode in batches.

    10. For a Layer 3 sub-interface, run the following commands to configure termination of single-tagged packets on it.

      1. Run quit

        Return to the system view.

      2. Run interface interface-type interface-number.subinterface-number

        The Layer 3 sub-interface view is displayed.

        The subinterface-number parameter must specify a Layer 3 sub-interface number on an Ethernet interface that has been switched to the Layer 3 mode.

      3. Run dot1q termination vid vid

        Termination of Dot1q packets is configured on the Layer 3 sub-interface.

        By default, the termination of Dot1q packets is not configured on a Layer 3 sub-interface.

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

      The interface is associated with a specified VPN instance.

    12. Run pim sm

      PIM-SM is enabled.

    13. Run commit

      The configuration is committed.

(Optional) Configuring an SSM Group Policy

Context

By default, the Source-Specific Multicast (SSM) group address range is 232.0.0.0/8. Sometimes, the address range of SSM groups must be limited to ensure security of multicast networks. If the addresses in the default range are insufficient, the SSM group address range needs to be expanded. You can configure an SSM group policy to control the address range of SSM groups.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run pim [ vpn-instance vpn-instance-name ]

    The PIM view is displayed.

  3. Run ssm-policy { basic-acl-number | acl-name acl-name }

    The SSM group address range is configured.

    NOTE:

    Ensure that the SSM group address range of all devices in the network are the same.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of IPv4 PIM-SM in the SSM Model

Prerequisites

After configuration of PIM-SM in SSM model is complete, you can check information about the PIM interface, PIM neighbor, and PIM routing table.

Procedure

  • 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.

    • 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 | register | none } | mode { sm | ssm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ]

    • 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 { ssm | sm } | 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 } ] *

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075361

Views: 20648

Downloads: 21

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