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

CLI-based Configuration Guide - IP Multicast

AR500, AR510, AR531, AR550, AR1500, and AR2500 V200R010

This document describes the concepts and configuration procedures of IP Service features on the device, and provides the configuration examples.
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 a Multicast Boundary

Configuring a 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.

A multicast forwarding boundary can be defined in either of the follow modes:
  • Based on a multicast group address range: A multicast forwarding boundary is configured based on group addresses and mask lengths that are configured on an interface. The interface filters multicast data based only on multicast group addresses.
  • Based on a multicast boundary policy: A multicast forwarding boundary is configured based on an access control list (ACL) on an interface. The interface filters multicast information based on source addresses, group addresses, or multicast boundary policies.

Three types of multicast boundary policies can be configured based on the directions of packets to be filtered:

  • Inbound multicast boundary policy: controls multicast data importing and receiving on the protocol control plane and forwarding plane to control data that can be imported from other domains to the local domain.
  • Outbound multicast boundary policy: controls data packets that can be sent out of the local domain.
  • Inbound and outbound multicast boundary policy: has the functions of both an inbound multicast boundary policy and an outbound multicast boundary policy, and filters auto-RP packets that an interface can send and receive. Auto-RP packets are filtered based on multicast group information.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Configure a multicast forwarding boundary.

    Perform one or more of the following operations to configure filter criteria for multicast information on a multicast forwarding boundary (multicast information must match all the criteria):

    • Run the multicast boundary group-address { mask | mask-length } command to configure a multicast forwarding boundary based on a group address range.

    • Run the multicast boundary policy { acl-name acl-name | basic-acl-number | advanced-acl-number } in command to define an inbound multicast boundary policy that is used to create a multicast forwarding boundary.

    • Run the multicast boundary policy { acl-name acl-name | basic-acl-number | advanced-acl-number } out command to define an outbound multicast policy that is used to create a multicast forwarding boundary.

    • Run the multicast boundary policy basic-acl-number [ filter-autorp ] command to define an inbound and outbound multicast boundary policy that is used to create a multicast forwarding boundary.

    NOTE:

    If the AR530&AR550 connects to a third-party device and needs to receive Auto-RP messages from the third-party device, you must configure a rule to allow packets with destination addresses 224.0.1.39 and 224.0.1.40 to pass in the ACL specified in the multicast boundary policy.

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 display multicast [ vpn-instance vpn-instance-name | all-instance ] 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 following command to check the multicast boundary configuration on an interface:

    • display multicast [ vpn-instance vpn-instance-name | all-instance ] boundary [ group-address [ mask | mask-length ] ] [ interface interface-type interface-number ]

    • display multicast [ vpn-instance vpn-instance-name | all-instance ] boundary policy [ group-address source-address | interface interface-type interface-number ] *

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1100034230

Views: 123808

Downloads: 37

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