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

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document describes the principles and configurations of IP multicast, and provides 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 PIM-SM in the ASM Model

Configuring PIM-SM in the ASM Model

Context

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

Pre-configuration Tasks

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

Configuration Process

Mandatory procedures for configuring PIM-SM in the ASM model are as follows:

  1. Enable PIM-SM.
  2. Configure an RP.

Perform the optional configuration tasks as required.

Enabling PIM-SM

Context

PIM-DM and PIM-SM cannot be enabled simultaneously in the public network instance or VPN instance.

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.

If PIM-SM and IGMP need to be enabled on the same interface, enable PIM-SM, and then enable IGMP.

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. Run:

      pim sm

      PIM-SM is enabled.

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

      multicast routing-enable

      IP multicast routing is enabled.

    4. Run:

      quit

      Return to the system view.

    5. Run:

      interface interface-type interface-number

      The interface view is displayed.

    6. Run:

      ip binding vpn-instance vpn-instance-name

      The interface is associated with a specified VPN instance.

    7. Run:

      pim sm

      PIM-SM is enabled.

Configuring an RP

Context

A rendezvous point (RP) can be configured manually or elected from among multiple candidate rendezvous points (C-RPs) based on C-RP information collected and advertised by the bootstrap router (BSR). Manually configuring a static RP reduces bandwidth used for frequent information exchange between the C-RPs and BSR. RP election through the BSR mechanism simplifies configuration and improves reliability of multicast forwarding because multiple C-RPs are configured.

To allow the local device to receive Auto-RP Announcement or Discovery messages from other devices, enable the listening of Auto-RP messages.

You can configure a static RP and multiple candidate rendezvous points (C-RPs) for dynamic RP election. The static RP functions as a backup RP because it has a lower priority. Ensure that all the devices on the network have the same RP information. Inconsistent RP information may cause forwarding failures on the network.

Default Configuration

Table 4-10 lists the default configuration of the C-BSR and C-RP.

Table 4-10  Default configuration of the C-BSR and C-RP
Parameter Default Setting

C-BSR priority

0

C-BSR hash mask length

30

BSR message fragmentation

Disabled

Multicast group policy of a static RP

No multicast group policy configured (receiving multicast data with any group address)

Multicast group policy of a C-RP

No multicast group policy configured (receiving multicast data with any group address)

C-RP priority

0

Interval for sending C-RP Announcement messages

60s

Hold time of C-RP Announcement messages

150s

Procedure

  • Configure a static RP.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      static-rp rp-address [ basic-acl-number | acl-name acl-name ] [ preferred ]

      Address of a static RP is specified.

      preferred indicates that the static RP takes precedence over a dynamic RP.

      NOTE:

      All devices in the PIM-SM domain must be configured with the same static RP address.

  • Configure a dynamic RP.

    1. Configure a C-BSR.

      1. Run:

        system-view

        The system view is displayed.

      2. Run:

        pim [ vpn-instance vpn-instance-name ]

        The PIM view is displayed.

      3. Run:

        c-bsr interface-type interface-number [ hash-length [ priority ] ]

        A C-BSR is configured.

        It is recommended that you configure the C-BSR on the device that aggregates multicast data.

      4. (Optional) Run:

        bsm semantic fragmentation

        The BSR message fragmentation function is enabled.

        NOTE:

        BSR message fragmentation is recommended because it can solve the problem faced by IP fragmentation that all fragments become unavailable due to loss of fragment information. Enable BSR message fragmentation on all devices. Otherwise, devices that do not fragment BSR messages may receive incomplete RPs.

    2. Configure a C-RP.

      1. Run:

        system-view

        The system view is displayed.

      2. Run:

        pim [ vpn-instance vpn-instance-name ]

        The PIM view is displayed.

      3. Run:

        c-rp interface-type interface-number [ group-policy { basic-acl-number | acl-name acl-name } | priority priority | holdtime hold-interval | advertisement-interval adv-interval ]*

        A C-RP is configured.

        It is recommended that you configure the C-RP on the device that aggregates multicast data.

    3. (Optional) Configure a BSR boundary.

      1. Run:

        system-view

        The system view is displayed.

      2. Run:

        interface interface-type interface-number

        The interface view is displayed.

      3. Run:

        pim bsr-boundary

        A BSR service boundary is configured.

        The BSR messages cannot pass through the BSR boundary. Therefore, it is recommended that you configure the BSR service boundary on interfaces at the edge of a PIM-SM domain.

  • Enable listening of Auto-RP messages.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      auto-rp listening enable

      Listening of Auto-RP messages is enabled.

(Optional) Configuring a BSR Administrative Domain

Context

To facilitate PIM domain management, a PIM network is divided into multiple bootstrap router (BSR) administrative domains and a global domain. Each BSR administrative domain maintains only one BSR that serves specified multicast groups. Multicast groups that do not belong to any BSR administrative domain are served by the global domain. A device can join only one administrative domain, so devices in each administrative domain can forward multicast data independently. Data of multicast groups in the global domain can be forwarded through devices in any administrative domain.

The maximum range of multicast groups that a BSR administrative domain can serve is 239.0.0.0 to 239.255.255.255. Multicast addresses in this range are used as private group addresses.

Procedure

  1. Enable BSR administrative domain on all devices in the PIM domain.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      c-bsr admin-scope

      The BSR administrative domain is enabled.

  2. Configure a BSR administrative domain boundary on an edge interface.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The interface view is displayed.

    3. Run:

      multicast boundary group-address { mask | mask-length }

      The boundary of the BSR administrative domain is configured.

      Multicast packets that belong to the BSR administrative domain cannot traverse the boundary.

  3. Configure a group address range for the C-BSR in each BSR administrative domain.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      c-bsr group group-address { mask | mask-length } [ hash-length hash-length | priority priority ] *

      A group address range is configured for the C-BSR in each BSR administrative domain.

  4. Configure a C-BSR in the global domain.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      c-bsr global [ hash-length hash-length | priority priority ] *

      A C-BSR is configured for the global administrative domain.

(Optional) Configuring the SPT Switchover Condition

Context

A high volume of multicast data traffic increases the load of a rendezvous point (RP) and may result in a fault. The designated router (DR) at the group member side triggers SPT switchover to reduce the burden of the RP.

By default, a DR at the group member side immediately triggers shortest path tree (SPT) switchover after receiving the first multicast data packet. You can configure a traffic rate threshold on a DR at the group member side to trigger an SPT switchover or prevent the DR from triggering an SPT switchover.

Default Configuration

Table 4-11 lists the default configuration of SPT switchover conditions.

Table 4-11  Default configuration of SPT switchover conditions
Parameter Default Setting

Group policy that specifies the groups to which the SPT switchover conditions apply

No group policy configured (The SPT switchover conditions apply to all multicast groups.)

Interval for checking the forwarding rate of multicast data

15s

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:

    spt-switch-threshold { traffic-rate | infinity } [ group-policy { basic-acl-number | acl-name acl-name } [ order order-value ] ]

    The SPT switchover condition is configured.

    traffic-rate specifies the rate threshold that triggers an SPT switchover. infinity indicates that the SPT switchover is never triggered.

  4. Run:

    timer spt-switch interval

    The interval for checking the forwarding rate of multicast data is configured.

(Optional) Adjusting Control Parameters for Source Registering

Context

After receiving multicast data from a multicast source, the source DR encapsulates multicast data in a Register message and forwards the message to the RP. Therefore, you can adjust control parameters for source registering on the RP and source DR.

You can perform the following operations on the source DR.

  • Configure the register message suppression time. After receiving a Register-Stop message, the source DR stops sending Register messages to the RP during register suppression. The source DR forwards packets again when the register suppression time expires and it receives no more Register-Stop messages.
  • Configure the interval at which null Register messages are sent. When the timeout period for keeping the register suppression state is too long or too short, multicast data cannot be forwarded normally. Sending null Register messages during register suppression can relieve this problem.
  • Configure the RP to calculate checksums only based on information in Register message headers. This reduces the time used for calculating the checksums and improves efficiency of encapsulating multicast data in Register messages.
  • Configure the source address for Register messages. The RP cannot receive Register messages from a source DR if the source address of the Register messages is not a unique IP address on the network or if the source address is filtered out by a policy configured on the RP. To enable the RP to receive Register messages from the source DR, configure a new source address for the Register messages.

You can perform the following operations on the RP.

  • Configure a policy to filter Register messages. You can specify the address range of Register messages to improve network security.
Default Configuration

Table 4-12 lists default configuration of control parameters for source registering.

Table 4-12  Default configuration of control parameters for source registering
Parameter Default Setting

Filter policy for Register messages

No filter policy configured (receiving Register messages with any group address)

Way to calculate the checksum

Based on the entire message

Register message suppression time

60s

Interval for sending null Register messages

5s

Procedure

  • Configure control parameters for source registering on the source DR.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      register-suppression-timeout interval

      Register message suppression time is configured.

    4. Run:

      probe-interval interval

      The interval for sending null Register messages is configured.

      NOTE:

      The value of probe-interval must be smaller than half of register-suppression-timeout.

    5. Run:

      register-header-checksum

      The checksum is calculated only based on the header of a Register message. Packets that fail the check are discarded.

    6. Run:

      register-source interface-type interface-number

      The source address of Register messages sent from the source DR is configured.

      It is recommended that you use the IP address of a loopback interface on the source DR as the source address of Register messages.

  • Configure control parameters for source registering on the RP.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      register-policy { advanced-acl-number | acl-name acl-name }

      A policy for filtering Register messages is configured.

(Optional) Adjusting C-RP Control Parameters

Context

When a candidate rendezvous point (C-RP) is configured on the device, the C-RP periodically sends Advertisement messages to a bootstrap router (BSR). The Advertisement messages carry the C-RP priority and the holdtime of Advertisement messages. After receiving Advertisement messages, the BSR starts the C-RP timeout timer. The timer value is set to the holdtime of Advertisement messages. Before the timer expires, the BSR collects the C-RP information in Advertisement messages into an RP-set, encapsulates the RP-set into a Bootstrap message, and advertises the Bootstrap message to all PIM devices in the PIM domain. If the BSR does not receive any Advertisement message from the C-RP after the timer expires, the BSR considers the C-RP invalid or unreachable on the network. The interval for sending Advertisement messages must be smaller than the holdtime of Advertisement messages.

You can manually configure the interval for sending Advertisement messages, C-RP priority and holdtime of Advertisement messages. To prevent C-RP spoofing, set the range of valid C-RP addresses on the BSR. Then the BSR accepts only the Advertisement messages with the source addresses in the specified range.

NOTE:

For the default values of the parameters carried in Advertisement messages, see Configuring an RP.

Procedure

  • Configure parameters on Advertisement messages on the C-RP.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      c-rp priority priority

      The C-RP priority is configured.

    4. Run:

      c-rp advertisement-interval interval

      The interval for sending Advertisement messages is configured.

    5. Run:

      c-rp holdtime interval

      The time period to hold the Advertisement messages received from the C-RP is configured.

  • Configure the valid C-RP address range on the BSR.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      crp-policy { advanced-acl-number | acl-name acl-name }

      The range of valid C-RP addresses and the range of groups that C-RPs serve are configured.

(Optional) Adjusting C-BSR Control Parameters

Context

Candidate bootstrap routers (C-BSRs) automatically elect a BSR in a PIM domain. At first, each C-BSR considers itself as a BSR and sends Bootstrap messages to all devices in the domain. When a C-BSR receives a Bootstrap message from another C-BSR, it compares the priority in the received Bootstrap message with its own priority. The C-BSR with a higher priority wins. If the two BSRs have the same priority, the BSR with a larger IP address is preferred. After a C-BSR is elected as the BSR, it encapsulates its own IP address and the RP-Set information into a Bootstrap message and sends the Bootstrap message in the PIM domain. The Bootstrap message contains a hash mask which is used for hash calculation in C-RP election.

The BSR periodically sends a Bootstrap message to the network. When the other C-BSRs receive the Bootstrap message, they start the holdtime timer. If they do not receive any Bootstrap message from the BSR when the holdtime timer expires, they consider that the BSR fails and initiate the election of a new BSR. The interval for sending Bootstrap messages must be smaller than the holdtime of a Bootstrap message.

You can configure the C-BSR priority, the BSR hash mask length, the interval for sending Bootstrap messages, and the holdtime of Bootstrap messages. To prevent BSR spoofing, set a range of valid BSR addresses on devices, so that the devices receive messages only from the BSRs within the address range.

Default Configuration

Table 4-13 lists the default configuration of the C-BSR.

Table 4-13  Default configuration of the C-BSR
Parameter Default Setting

Interval for sending Bootstrap messages

60s

Holdtime of Bootstrap messages

130s

NOTE:

For the default values of other C-BSR parameters, see Configuring an RP.

Procedure

  • Configure parameters contained in a Bootstrap message for a C-BSR.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      c-bsr priority priority

      The priority of the C-BSR is configured.

    4. Run:

      c-bsr hash-length priority

      The hash mask length of the C-BSR is configured.

    5. Run:

      c-bsr interval interval

      The interval for the BSR to send Bootstrap messages is configured.

    6. Run:

      c-bsr holdtime interval

      The holdtime of the Bootstrap message received from the BSR is configured.

  • Configure a valid BSR address range on a PIM device.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      bsr-policy { basic-acl-number | acl-name acl-name }

      The range of valid BSR addresses is configured.

Checking the Configuration

Prerequisites

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

Procedure

  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] bsr-info command to check the BSR configuration.
  • Run the display pim [ vpn-instance vpn-instance-name | all-instance ] rp-info [ group-address ] command to check the RP configuration.
  • 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 [ 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 [ 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-06-12

Document ID: EDOC1000097181

Views: 17799

Downloads: 399

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