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 V200R005C00

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).
Configuring IPv4 PIM BFD

Configuring IPv4 PIM BFD

Pre-configuration Tasks

Before configuring PIM BFD, complete the following tasks:

  • Configuring a unicast routing protocol to ensure normal unicast routing on the network
  • Enabling BFD globally using the bfd command
  • Enabling PIM-SM

Context

On a PIM network, changes of link status between PIM neighbors will restart some PIM mechanisms, such as DR election or Assert winner election. For example, when the designated router (DR) on a shared network segment fails, PIM neighbors on the network segment trigger DR re-election only when the PIM neighbor relationships time out. Multicast data transmission is interrupted before a new DR is elected. The multicast service interruption time is longer than or equal to the neighbor relationship timeout interval, and is usually several seconds.

PIM Bidirectional Forwarding Detection (BFD) can detect link status changes on a shared network segment in milliseconds, enabling PIM devices to rapidly respond to failures of PIM neighbors. If a PIM BFD-capable interface does not receive any BFD packets from the DR within the detection interval, it considers that the DR has failed. Then BFD rapidly reports the session status to the route management (RM) module, which then reports the link status change to the PIM module. After receiving the notification, the PIM module triggers DR re-election immediately, without waiting for timeout of the neighbor relationship. This mechanism reduces the multicast service interruption time and improves reliability of multicast data transmission.

PIM BFD is applicable to the assert election on the shared network segment. In addition, it quickly responds to faults on the assert winner interface.

Default Settings

Table 4-21 lists default settings of control parameters for PIM BFD messages.

Table 4-21 Default settings of control parameters for PIM BFD messages
Parameter Default Setting

Minimum sending interval

1000 ms

Minimum receiving interval

1000 ms

Local detection multiplier

3

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 pim bfd enable

    PIM BFD is enabled.

  6. (Optional)Run pim bfd { min-tx-interval tx-value | min-rx-interval rx-value | detect-multiplier multiplier-value } *

    The parameters of PIM BFD are set.

    This operation is performed to set the minimum interval for sending the PIM BFD messages, the minimum interval for receiving the PIM BFD messages, and the local detection multiplier.

  7. Run commit

    The configuration is committed.

Verifying the Configuration

After PIM BFD is configured, you can run the following commands to check information about the PIM BFD session.

  • display pim [ vpn-instance vpn-instance-name | all-instance ] bfd session statistics

  • display pim [ vpn-instance vpn-instance-name | all-instance ] bfd session [ interface interface-type interface-number | neighbor neighbor-address ] *

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039595

Views: 49392

Downloads: 87

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