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 12800 and 12800E 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 an IPv4 Multicast Boundary

Configuring an IPv4 Multicast Boundary

Pre-configuration Tasks

Before configuring the multicast boundary, complete the following tasks:

  • Configure a unicast routing protocol to ensure normal unicast routing on the network.
  • Run the multicast routing-enable command in the system view to enable Layer 3 multicast routing globally.

Context

To restrict forwarding of multicast packets sent to a multicast group within a range, configure a multicast boundary on interfaces. Once the multicast boundary is configured on an interface, multicast packets sent to the group cannot be forwarded through the interface.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

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

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

  5. Run multicast boundary group-address { mask | mask-length }

    A multicast boundary is configured on the interface.

  6. Run commit

    The configuration is committed.

Verifying the Configuration

After configuring a multicast boundary on interfaces, check the multicast routing table and information about the multicast boundary on the interfaces to verify that the multicast network can operate normally.

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

    • display multicast routing-table [ group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length } ] | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } | incoming-interface { interface-type interface-number | register | mcast-extranet } | outgoing-interface { include | exclude | match } { interface-type interface-number | vpn-instance vpn-instance-name | register | none } ] * [ outgoing-interface-number [ number ] ]

    • display multicast { 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 } ] | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } | incoming-interface { interface-type interface-number | register | mcast-extranet } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } ] * [ outgoing-interface-number [ number ] ]

  • Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] boundary [ group-address [ mask | mask-length ] ] [ interface interface-type interface-number ] command to check information about the multicast boundary configured on an interface.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074724

Views: 40205

Downloads: 13

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