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 Control Parameters for DF Election in IPv4 Bidir-PIM

Adjusting Control Parameters for DF Election in IPv4 Bidir-PIM

Context

After PIM devices obtain rendezvous point (RP) information, they start a designated forwarder (DF) election on the shared network segment.

Configuration Procedure

You can configure the interval between Offer messages, interval between Backoff messages, and DF election robustness variable in any sequence.

NOTE:

Each DF election control parameter must be set to the same value on a shared network segment. Otherwise, the DF election may fail.

Configuring the Interval Between Offer Messages

Context

Devices on a Bidir-PIM shared network segment exchange Offer messages for designated forwarder (DF) election. When a device obtains rendezvous point (RP) information, it sends an Offer message to the shared network segment and starts a timer, with the value set to the configured interval between Offer messages. Before the timer expires:

  • If the device receives an Offer message carrying a better routing information to the RP, the device stops sending Offer messages.
  • If the device receives no Offer message or receives Offer messages carrying inferior routing information to the RP, the device resets the timer when the timer expires and continues sending Offer messages.
NOTE:

The interval between Offer messages can be configured in the PIM view or interface view. If you configure this parameter in both the PIM view and interface view, the configuration in the interface view takes effect.

Default Settings

Table 4-26 provides the default interval between Offer messages.

Table 4-26 Default interval between Offer messages
Parameter Default Setting

Interval between Offer messages

100 ms

Procedure

  • Global configuration
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run offer-interval interval

      The interval between Offer messages is set.

    4. Run commit

      The configuration is committed.

  • Interface configuration
    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 pim offer-interval interval

      The interval between Offer messages is set.

    6. Run commit

      The configuration is committed.

Configuring the Interval Between Backoff Messages

Context

On a Bidir-PIM network, the elected designated forwarder (DF) sends a Backoff message when it receives a superior Offer message. If the DF does not receive any Offer within the interval for sending the next Backoff message, it sends a Pass message to notify all the multicast devices that a new DF appears.

NOTE:

The interval between Backoff messages can be configured in the PIM view or interface view. If you configure this parameter in both the PIM view and interface view, the configuration in the interface view takes effect.

Default Settings

The default interval between Backoff messages is 1s.

Procedure

  • Global configuration
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run backoff-interval interval

      The interval between Backoff messages is configured.

    4. Run commit

      The configuration is committed.

  • Interface configuration
    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 pim backoff-interval interval

      The interval between Backoff messages is configured.

    6. Run commit

      The configuration is committed.

Configuring the DF Election Robustness Variable

Context

Devices on a Bidir-PIM shared network segment exchange Offer messages for designated forwarder (DF) election. The DF election robustness variable is used in a DF election in the following way:

  • If a device does not receive any Offer message from other devices after sending Offer messages robustness variable times, it considers itself as the DF.
  • If the device receives an Offer message from a neighbor with a smaller route metric to the RP, it stops participating in the DF election for a period (Time period = Robustness variable x Interval between Offer messages). This suppression period gives the neighbor a chance to be elected as the DF.
  • If the DF's route metric to the RP address increases, the DF sends Win messages at variable intervals to announce the new metric, for robustness variable times. If a device has a better route metric than the DF's, the device responds with an Offer message to trigger a new DF election.
NOTE:

The DF election robustness variable can be configured in the PIM view or interface view. If you configure this parameter in both the PIM view and interface view, the configuration in the interface view takes effect.

Default Settings

Table 4-27 provides the default DF election robustness variable.

Table 4-27 Default DF election robustness variable
Parameter Default Setting

DF election robustness variable

3

Procedure

  • Global configuration
    1. Run system-view

      The system view is displayed.

    2. Run pim

      The PIM view is displayed.

    3. Run election-robust-count robust-value

      The DF election robustness variable is configured.

    4. Run commit

      The configuration is committed.

  • Interface configuration
    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 pim election-robust-count robust-value

      The DF election robustness variable is configured.

    6. Run commit

      The configuration is committed.

Verifying the Configuration of Control Parameters for DF Election in IPv4 Bidir-PIM

Prerequisites

After configuring control parameters for DF election, you can run the following commands to check information about PIM interfaces, PIM neighbors, and DFs.

Procedure

  • Run the display pim interface [ interface-type interface-number | up | down ] [ verbose ] command to check PIM information on interfaces.
  • Run the display pim neighbor [ neighbor-address | interface interface-type interface-number | verbose ] * command to check information about PIM neighbors.
  • Run the display pim df-info [ rp rp-address | interface interface-type interface-number | verbose ] * command to check information about DFs for an RP.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075361

Views: 20189

Downloads: 21

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