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

NE20E-S2 V800R010C10SPC500 Feature Description - Network Reliability 01

This is NE20E-S2 V800R010C10SPC500 Feature Description - Network Reliability
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).
Board Selection Rules for BFD Sessions

Board Selection Rules for BFD Sessions

BFD can be deployed in either distributed or integrated mode.

  • Distributed mode

    By default, BFD works in distributed mode. In this mode:

    • If a single-hop BFD session is established and the session is bound to a board that is BFD-capable in hardware, BFD can work properly. If the session is bound to a BFD-incapable board, BFD cannot work.

    • If a single-hop BFD session is established and the session is bound to a board that is BFD-incapable in hardware but BFD-capable in software, the BFD session can be processed by this board.

  • Integrated mode

    If single-hop BFD sessions are established and the sessions are bound to boards that are BFD-incapable in hardware but BFD-capable in software, the sessions will be distributed to the two load-balancing integrated boards. The load-balancing integrated board with more available BFD resources will be preferentially selected.

NOTE:

Boards that are BFD-incapable in hardware but BFD-capable in software are selected in the following conditions:

  • Boards that are BFD-capable in hardware are unavailable.
  • The integrated mode is not configured, and BFD for IP sessions bound to a physical interface or its sub-interfaces are single-hops.

If boards that are BFD-incapable in hardware but BFD-capable in software are already selected and the integrated mode is configured, sessions will enter the AdminDown state and then be bound to an integrated board.

Table 2-4 describes the board selection rules for BFD sessions.

Table 2-4 Board selection rules for BFD sessions

Session Type

Board Selection Rule

Multi-hop session

The board with the interface that receives BFD negotiation packets is preferentially selected. If the board does not have available BFD resources, a load-balancing integrated board will be selected. If no load-balancing integrated board is available, board selection fails.

Single-hop session bound to a physical interface or its sub-interfaces

  • If the board on which the bound interface or sub-interfaces reside is BFD-capable in hardware, this board is selected. If the board does not have available BFD resources, board selection fails.

  • If the board on which the bound interface or sub-interfaces reside is BFD-incapable in hardware but BFD-capable in software and the integrated mode is configured, a load-balancing integrated board will be selected. If no load-balancing integrated board is available, board selection fails.
  • If the board on which the bound interface or sub-interfaces reside is BFD-incapable in hardware but BFD-capable in software, the board is still selected. If the board does not have available BFD resources, board selection fails.
Single-hop session bound to a trunk interface

A board is selected from the boards on which trunk member interfaces reside. If none of the boards has available BFD resources, board selection fails.

  • If none of these boards is BFD-incapable in hardware, a specified integrated board will be selected based on load balancing.
  • If any of these boards are BFD-capable in hardware, and the others are BFD-incapable in hardware, a specified integrated board will be selected. If board selection fails, a board is selected from those that are BFD-capable in hardware.
  • If all of these boards are BFD-capable in hardware, one will be selected based on load balancing.
BFD for LDP LSP session
  • If an outbound interface is configured for a BFD for LDP LSP session, the board on which the outbound interface resides is preferentially selected.

    • If the outbound interface is a tunnel interface, a board is selected based on multi-hop session rules because tunnel interfaces reside on the IPU that is BFD-incapable in hardware.
    • If the board on which the outbound interface resides is BFD-incapable in hardware, a specified integrated board is selected.

    • If the board on which the outbound interface resides is BFD-capable in hardware, this board is selected.
  • If a BFD session is not configured with an outbound interface, a board is selected for the BFD session based on multi-hop session rules.
BFD for TE session

Preferentially select the specified board. If no board is specified, select the board based on the multi-hop session principle.

BFD for VLANIF session

The board with the interface that receives BFD negotiation packets is selected. If the board does not have available BFD resources, board selection fails.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055473

Views: 12242

Downloads: 4

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