bfd no-bypass

Function

The bfd no-bypass command enables BFD no-bypass for an SRv6 TE Policy.

The bfd bypass command enables BFD bypass for an SRv6 TE Policy.

The undo bfd no-bypass command deletes the BFD no-bypass configuration and allows a device to inherit the srv6-te-policy bfd no-bypass command configuration.

The undo bfd bypass command deletes the BFD bypass configuration and allows a device to inherit the srv6-te-policy bfd no-bypass command configuration.

By default, the srv6-te-policy bfd no-bypass configuration is inherited.

Format

bfd { no-bypass | bypass }

undo bfd { no-bypass | bypass }

Parameters

Parameter	Description	Value
no-bypass	Enables the BFD no-bypass function for an SRv6 TE Policy. If this parameter is selected, BFD packets of an SRv6 TE Policy do not pass through local protection paths such as TI-LFA and TE FRR. If the primary path fails, the BFD session directly goes Down, triggering an SRv6 TE Policy primary/backup switchover.	-
bypass	Enables BFD bypass for an SRv6 TE Policy. If this parameter is selected, BFD packets of an SRv6 TE Policy can be transmitted over a local protection path such as TI-LFA or TE FRR. If the primary path fails, the BFD session does not report a Down event. As a result, the actual status of the primary path of the SRv6 TE Policy cannot be detected.	-

Parameter

Description

Value

no-bypass

Enables the BFD no-bypass function for an SRv6 TE Policy.

If this parameter is selected, BFD packets of an SRv6 TE Policy do not pass through local protection paths such as TI-LFA and TE FRR. If the primary path fails, the BFD session directly goes Down, triggering an SRv6 TE Policy primary/backup switchover.

bypass

Enables BFD bypass for an SRv6 TE Policy.

If this parameter is selected, BFD packets of an SRv6 TE Policy can be transmitted over a local protection path such as TI-LFA or TE FRR. If the primary path fails, the BFD session does not report a Down event. As a result, the actual status of the primary path of the SRv6 TE Policy cannot be detected.

Views

SRv6 TE policy view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
srpolicy	write

Usage Guidelines

Usage Scenario

During BFD for SRv6 TE Policy deployment, if the segment list of the primary candidate path fails and a local protection path (for example, a TI-LFA or TE FRR path) exists, the BFD session remains Up, and data traffic is diverted to the TI-LFA or TE FRR path. However, the performance such as the bandwidth/latency of the TI-LFA or TE FRR path may be unstable, preventing the path from meeting the strict SLA requirements of high-value private line services. To resolve this problem, disable BFD from using the local protection path. If the segment list of the primary candidate path fails, the BFD session status changes to Down, and the candidate path status changes to Down, triggering traffic to be switched to the backup candidate path or another SRv6 TE Policy.

The srv6-te-policy bfd no-bypass command enables BFD no-bypass for all SRv6 TE Policies in the segment routing IPv6 view. The bfd { no-bypass | bypass } command can be used to configure BFD no-bypass or bypass for a single SRv6 TE Policy.

If both the srv6-te-policy bfd no-bypass and bfd { no-bypass | bypass } commands are run for an SRv6 TE Policy, the bfd { no-bypass | bypass } command takes precedence over the srv6-te-policy bfd no-bypass command.

Example

# Enable BFD no-bypass for an SRv6 TE Policy named policy1.

<HUAWEI> system-view
[~HUAWEI] segment-routing ipv6
[*HUAWEI-segment-routing-ipv6] srv6-te policy policy1 endpoint 2001:DB8:1::1 color 100
[*HUAWEI-segment-routing-ipv6-policy-policy1] bfd no-bypass