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).
Adjusting State Refresh Control Parameters in IPv4 PIM-DM

Adjusting State Refresh Control Parameters in IPv4 PIM-DM

Context

PIM-DM provides a state refresh mechanism to prevent pruned interfaces from resuming multicast forwarding due to prune state timeout. The first-hop device directly connected to a multicast source sends State-Refresh messages at intervals to reset the prune timers on pruned interfaces and maintain the SPT.

Configuration Procedure

You can disable forwarding of State-Refresh messages, set time parameters of State-Refresh messages, and set the TTL value of State-Refresh messages at any sequence as required.

Disabling Forwarding of State-Refresh Messages

Context

Pruned interfaces can resume multicast forwarding when the prune timer expires, even though no downstream devices need to receive multicast data. To prevent this problem, the PIM device directly connected to a multicast source sends State-Refresh messages at intervals to update state of (S, G) entries. A State-Refresh message is propagated to downstream devices hop by hop to reset prune timers on all the PIM devices. In this way, interfaces that do not need to forward multicast data retain in prune state.

By default, all PIM devices can forward State-Refresh messages. If you want multicast data to be flooded on the entire network in every flood-prune process and do not want to prevent pruned interface from resume multicast forwarding, disable forwarding of State-Refresh messages on device interfaces.

NOTE:

Disabling forwarding of State-Refresh messages is not recommended because State-Refresh messages can conserve network resources.

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 undo pim state-refresh-capable

    Forwarding of State-Refresh messages is disabled on the interface.

    By default, forwarding of State-Refresh messages is enabled on the interface.

    To enable the interface to forward State-Refresh messages again, run the pim state-refresh-capable command on the interface.

  6. Run commit

    The configuration is committed.

Adjusting Time Parameters for State-Refresh Messages

Context

The PIM device directly connected to a multicast source sends State-Refresh messages at intervals to downstream devices. State-Refresh messages are flooded on the entire network, so a device may receive duplicate State-Refresh messages within a short time. To prevent this problem, a device starts a timer when receiving a State-Refresh message for an (S, G) entry. The timer value is the suppression time of the State-Refresh message. If the device receives the same State-Refresh messages before the timer expires, it drops the received State-Refresh messages.

Default Settings

Table 4-12 lists the default settings of time parameters for State-Refresh messages.

Table 4-12 Default settings of time parameters for State-Refresh messages
Parameter Default Setting

Interval for sending State-Refresh messages

60s

Suppression time of duplicate State-Refresh messages

30s

Procedure

  • Set the interval for sending State-Refresh messages on the device directly connected to a multicast source.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run state-refresh-interval interval

      The interval for sending State-Refresh messages is set.

    4. Run commit

      The configuration is committed.

  • Set the suppression time of duplicate State-Refresh messages on all the PIM devices.
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run state-refresh-rate-limit interval

      The suppression time of duplicate State-Refresh messages is set.

    4. Run commit

      The configuration is committed.

Setting the TTL Value of State-Refresh Messages

Context

When a device receives a State-Refresh message, it reduces the time-to-live (TTL) value of the message by 1 and forwards the message to downstream devices. The State-Refresh message is transmitted on the network until its TTL value reduces to 0. On a small-scale network, State-Refresh messages with a large TTL value are transmitted circularly. To control the transmission range of State-Refresh messages, set a proper TTL value for State-Refresh messages according to the network scale.

NOTE:

Because State-Refresh messages are originated from the first-hop device connected to a multicast source, the TTL value of State-Refresh messages must be configured on the first-hop device.

Default Settings

The default TTL value of State-Refresh messages is 255.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run pim

    The PIM view is displayed.

  3. Run state-refresh-ttl ttl-value

    The TTL value of State-Refresh messages is set.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of State Refresh Control Parameters in IPv4 PIM-DM

Prerequisites

After adjusting state refresh control parameters, you can check information about the PIM interface, statistics about PIM control messages, and PIM routing table.

Procedure

  • Run the display pim interface [ interface-type interface-number | up | down ] [ verbose ] command to check PIM information on an interface.
  • Run the display pim control-message counters [ message-type { assert | hello | join-prune | graft | graft-ack | state-refresh } | interface interface-type interface-number ] * command to check the number of PIM control messages sent and received from an interface.
  • Run the following commands to check 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 | register | none } | mode dm | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ] command to check detailed information about the PIM routing table.

    • Run the display pim 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-04-20

Document ID: EDOC1100075361

Views: 28799

Downloads: 34

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