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 V200R010C00

This document describes IP multicast basics and how to configure IP multicast features, including IGMP/MLD, PIM (IPv4&IPv6), MSDP, multicast VPN, Layer 3 multicast CAC, Layer 2 multicast CAC, IGMP/MLD snooping, and multicast VLAN, IPv4&IPv6 multicast route management, static multicast MAC address, multicast network.
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).
Adjusting Assert Control Parameters

Adjusting Assert Control Parameters

Pre-configuration Tasks

Configuring Basic PIM-DM Functions

Context

When multiple PIM devices on a network segment pass reverse path forwarding (RPF) checks and forward multicast data to this network segment, an assert election is required. When a device receives multicast data through a downstream interface, it knows that other upstream devices exist on this network segment. The device then sends an Assert message to participate in the election of the unique upstream device.

PIM devices that lose the assert election disable their downstream interfaces from forwarding multicast data to this network segment. The assert loser state lasts for a period of time, which is called the holdtime of Assert messages. After the holdtime expires, the assert losers restore pruned interfaces to the forwarding state to trigger a new Assert election.

NOTE:

The holdtime of Assert messages can be configured globally or on an interface. If this parameter is configured in both the global PIM view and interface view, the configuration in the interface view takes effect.

Default Configuration

The default holdtime of Assert messages is 180s.

Procedure

  • Global configuration
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      pim [ vpn-instance vpn-instance-name ]

      The PIM view is displayed.

    3. Run:

      holdtime assert interval

      The holdtime of Assert messages is configured.

  • Configuration on an interface
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The interface view is displayed.

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

    4. Run:

      pim holdtime assert interval

      The holdtime of Assert messages is configured.

Checking the Configuration

After assert control parameters are configured, you can check information about the PIM interface, PIM neighbors, and PIM routing table using the following commands:

  • 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-08-21

Document ID: EDOC1000141903

Views: 145715

Downloads: 111

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