Contents

BFD commands· 1

Basic BFD commands· 1

bfd authentication-mode· 1

bfd demand enable· 2

bfd detect-interface source-ip· 2

bfd detect-multiplier 4

bfd echo enable· 5

bfd echo-source-ip· 5

bfd echo-source-ipv6· 6

bfd init-fail timer 7

bfd min-echo-receive-interval 7

bfd min-receive-interval 8

bfd min-transmit-interval 9

bfd multi-hop authentication-mode· 10

bfd multi-hop destination-port 11

bfd multi-hop detect-multiplier 11

bfd multi-hop min-echo-receive-interval 12

bfd multi-hop min-receive-interval 13

bfd multi-hop min-transmit-interval 13

bfd session init-mode· 14

bfd template· 15

display bfd session· 15

reset bfd session statistics· 22

snmp-agent trap enable bfd· 22

 

BFD commands

Basic BFD commands

bfd authentication-mode

Use bfd authentication-mode to configure the BFD authentication mode for single-hop BFD control packets.

Use undo bfd authentication-mode to restore the default.

Syntax

bfd authentication-mode{ m-md5 | m-sha1 | md5 | sha1 | simple } key-id { cipher | plain } string

undo bfd authentication-mode

Default

Single-hop BFD control packets are not authenticated.

Views

Interface view

BFD template view

Predefined user roles

network-admin

Parameters

m-md5: Specifies the Meticulous MD5 algorithm.

m-sha1: Specifies the Meticulous SHA1 algorithm.

md5: Specifies the MD5 algorithm.

sha1: Specifies the SHA1 algorithm.

simple: Specifies the simple authentication mode.

key-id: Sets the authentication key ID in the range of 1 to 255.

cipher: Specifies a key in encrypted form.

plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.

string: Specifies the key. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 33 to 53 characters.

Usage guidelines

Use this command to enhance BFD session security.

BFD version 0 does not support this command. The configuration does not take effect.

Examples

# Configure GigabitEthernet 1/0 to perform simple authentication for single-hop BFD control packets, setting the authentication key ID to 1 and plaintext key to 123456.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] bfd authentication-mode simple 1 plain 123456

bfd demand enable

Use bfd demand enable to enable the Demand BFD session mode.

Use undo bfd demand enable to restore the default.

Syntax

bfd demand enable

undo bfd demand enable

Default

The BFD session is in Asynchronous mode.

Views

Interface view

Predefined user roles

network-admin

Usage guidelines

In Demand mode, the device periodically sends BFD control packets. If the peer end is operating in Asynchronous mode (default), the peer end stops sending BFD control packets. If the peer end is operating in Demand mode, both ends stop sending BFD control packets. As a best practice, configure the bfd echo enable command together with this command to detect connectivity by sending Echo packets. If the device does not receive any Echo packets from the peer end, it considers the session down.

In Asynchronous mode, the device periodically sends BFD control packets. The device considers that the session is down if it does not receive any BFD control packets within a specific interval.

BFD version 0 does not support this command. The configuration does not take effect.

Examples

# Enable the Demand BFD session mode on GigabitEthernet 1/0.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] bfd demand enable

bfd detect-interface source-ip

Use bfd detect-interface source-ip to associate the interface state with BFD and specify the source IP address for BFD control packets.

Use undo bfd detect-interface to remove the association between the interface state and BFD.

Syntax

bfd detect-interface source-ip ip-address [ discriminator local local-value remote remote-value ]

undo bfd detect-interface

Default

The interface state is not associated with BFD. BFD does not set the link layer protocol of the interface to DOWN(BFD) state when detecting a failure.

Views

Interface view

Predefined user roles

network-admin

Parameters

ip-address: Specifies the source IP address for BFD control packets, in dotted decimal notation.

discriminator: Specifies BFD session discriminators. If you do not specify discriminators, the device obtains BFD session discriminators through autonegotiation.

local local-value: Specifies the local discriminator. The value range for the local-value argument is 1 to 32768.

remote remote-value: Specifies the remote discriminator in the range of 1 to 4294967295.

Usage guidelines

By creating a BFD session for single-hop detection through exchange of BFD control packets, this feature implements fast link detection. When BFD detects a link fault, it sets the link layer protocol state to DOWN(BFD). This behavior helps applications relying on the link layer protocol state achieve fast convergence.

The source IP address of control packets is specified manually, and the destination IP address is fixed at 224.0.0.184. As a best practice, specify the IP address of the interface as the source IP address. If the interface does not have an IP address, specify a unicast IP address other than 0.0.0.0 as the source IP address.

You can associate the state of a Layer 3 Ethernet interface or VLAN interface with BFD.

If the peer device does not support obtaining BFD session discriminators through autonegotiation, you must specify the discriminators on both the local and peer devices. Without the discriminators, the BFD session cannot come up.

The BFD session discriminators must match on the local and peer devices. For example, if you configure bfd detect-interface source-ip 20.1.1.1 discriminator local 513 remote 514 on the local device, you must configure bfd detect-interface source-ip 20.1.1.2 discriminator local 514 remote 513 on the peer device.

The local discriminators of BFD sessions for interfaces on the same device must be different.

To modify your configuration, remove it by using the undo form of the command and then execute the bfd detect-interface source-ip command again.

The echo function does not take effect on BFD sessions associated with interface states.

Examples

# Associate GigabitEthernet 1/0 with BFD to detect the interface state, and specify the source IP address as 20.1.1.1.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] bfd detect-interface source-ip 20.1.1.1

Related commands

bfd demand enable

bfd echo enable

bfd template

bfd detect-multiplier

Use bfd detect-multiplier to set the single-hop detection time multiplier for control packet mode and echo packet mode.

Use undo bfd detect-multiplier to restore the default.

Syntax

bfd detect-multiplier value

undo bfd detect-multiplier

Default

The single-hop detection time multiplier is 5 for control packet mode and echo packet mode.

Views

Interface view

BFD template view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier. The value range for this argument is 3 to 200.

Usage guidelines

The detection time multiplier determines the maximum number of concurrent BFD packets (including control packets and echo packets) that can be discarded.

Table 1 Actual detection interval calculation method

Mode	Actual detection interval of the sender
Echo packet mode	Detection time multiplier of the sender × actual packet sending interval of the sender
Control packet mode BFD session in asynchronous mode	Detection time multiplier of the receiver × MAX (minimum receiving interval supported by the sender, minimum sending interval supported by the receiver)
Control packet mode BFD session in demand mode	Detection time multiplier of the sender × MAX (minimum sending interval supported by the sender, minimum receiving interval supported by the receiver)

 

Examples

# Set the single-hop detection time multiplier for control packet mode and the detection time multiplier for echo packet mode to 6 on GigabitEthernet 1/0.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] bfd detect-multiplier 6

bfd echo enable

Use bfd echo enable to enable the echo function.

Use undo bfd echo enable to disable the echo function.

Syntax

bfd echo [ receive | send ] enable

undo bfd echo [ receive | send ] enable

Default

The echo function is disabled.

Views

Interface view

Predefined user roles

network-admin

Parameters

receive: Specifies the echo packet receiving capability.

send: Specifies the echo packet sending capability.

Usage guidelines

If you enable the echo function for a BFD session in which control packets are sent and the session comes up, BFD performs the following operations:

·     Periodically sends echo packets to detect link connectivity.

·     Decreases the control packet receiving rate at the same time.

To enable only the echo packet receiving capability, use the bfd echo receive enable command.

To enable only the echo packet sending capability, use the bfd echo send enable command.

If you do not specify the receive or send keyword, the command enables both the echo packet receiving and sending capabilities.

The echo function does not take effect on BFD sessions associated with interface states.

BFD version 0 does not support this command. The configuration does not take effect.

Examples

# Enable the echo function on GigabitEthernet 1/0.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] bfd echo enable

bfd echo-source-ip

Use bfd echo-source-ip to configure the source IP address of BFD echo packets.

Use undo bfd echo-source-ip to remove the configured source IP address of BFD echo packets.

Syntax

bfd echo-source-ip ip-address

undo bfd echo-source-ip

Default

No source IP address is configured for BFD echo packets.

Views

System view

Predefined user roles

network-admin

Parameters

ip-address: Specifies the source IP address of BFD echo packets. The source IP address must be a valid unicast IPv4 address in dotted decimal notation.

Usage guidelines

The source IP address cannot be on the same network segment as any local interface's IP address. Otherwise, a large number of ICMP redirect packets might be sent from the peer, resulting in link congestion.

Examples

# Configure the source IP address of BFD echo packets as 8.8.8.8.

<Sysname> system-view

[Sysname] bfd echo-source-ip 8.8.8.8

bfd echo-source-ipv6

Use bfd echo-source-ipv6 to configure the source IPv6 address of BFD echo packets.

Use undo bfd echo-source-ipv6 to remove the configured source IPv6 address of BFD echo packets.

Syntax

bfd echo-source-ipv6 ipv6-address

undo bfd echo-source-ipv6

Default

No source IPv6 address is configured for BFD echo packets.

Views

System view

Predefined user roles

network-admin

Parameters

ipv6-address: Specifies the source IPv6 address for BFD echo packets.

Usage guidelines

The source IPv6 address of echo packets can only be a global unicast address.

The source IPv6 address cannot be on the same network segment as any local interface's IP address. Otherwise, a large number of ICMP redirect packets might be sent from the peer, resulting in link congestion.

Examples

# Configure the source IPv6 address of BFD echo packets as 80::2.

<Sysname> system-view

[Sysname] bfd echo-source-ipv6 80::2

bfd init-fail timer

Use bfd init-fail-timer to set the delay timer for BFD to notify upper-layer protocols of session establishment failures.

Use undo bfd init-fail-timer to restore the default.

Syntax

bfd init-fail-timer seconds

undo bfd init-fail-timer

Default

BFD does not notify upper-layer protocols of session establishment failures.

Views

System view

Predefined user roles

network-admin

Parameters

seconds: Specifies the delay time in the range of 5 to 600 seconds. After the delay time, BFD notifies the upper-layer protocol of session establishment failures.

Usage guidelines

This command takes effect only for control packet mode.

In some cases, for an upper-layer protocol to act correctly, BFD must notify the upper-layer protocol of session establishment failures. For example, with this command configured, the link aggregation module can promptly set the state of a member port from Selected to Unselected in the case of a link failure.

For session establishment failures caused by configuration mismatches at the two ends, this command can cause the upper-layer protocol to act incorrectly. Therefore, use this command with caution. BFD status mismatch and BFD authentication configuration mismatch are examples of configuration mismatches.

Examples

# Set the delay timer to 10 seconds for BFD to notify upper-layer protocols of session establishment failures.

<Sysname> system-view

[Sysname] bfd init-fail-timer 10

bfd min-echo-receive-interval

Use bfd min-echo-receive-interval to set the minimum interval for receiving BFD echo packets.

Use undo bfd min-echo-receive-interval to restore the default.

Syntax

bfd min-echo-receive-interval interval

undo bfd min-echo-receive-interval

Default

The minimum interval for receiving BFD echo packets is 500 milliseconds.

Views

Interface view

BFD template view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD echo packets, in milliseconds. The value takes 0 or is in the range of 10 to 2000.

Usage guidelines

This command sets the BFD echo packet receiving interval, which is the actual BFD echo packet sending interval.

The local end stops sending echo packets after autonegotiation with the remote end if the following conditions are met:

·     The echo function is enabled on the local end.

·     The minimum interval for receiving BFD echo packets is set to 0 milliseconds on the remote end.

Examples

# Set the minimum interval for receiving BFD echo packets to 500 milliseconds on GigabitEthernet 1/0.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] bfd min-echo-receive-interval 500

bfd min-receive-interval

Use bfd min-receive-interval to set the minimum interval for receiving single-hop BFD control packets.

Use undo bfd min-receive-interval to restore the default.

Syntax

bfd min-receive-interval interval

undo bfd min-receive-interval

Default

The minimum interval for receiving single-hop BFD control packets is 500 milliseconds.

Views

Interface view

BFD template view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving single-hop BFD control packets, in milliseconds. The value range for this argument is 10 to 2000.

Usage guidelines

Use this command to prevent the control packet sending rate of the peer end from exceeding the control packet receiving rate of the local end.

The actual control packet sending interval of the peer end takes the greater value between the following values:

·     Minimum interval for transmitting BFD control packets on the peer end.

·     Minimum interval for receiving BFD control packets on the local end.

Examples

# Set the minimum interval for receiving single-hop BFD control packets to 500 milliseconds on GigabitEthernet 1/0.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] bfd min-receive-interval 500

bfd min-transmit-interval

Use bfd min-transmit-interval to set the minimum interval for transmitting single-hop BFD control packets.

Use undo bfd min-transmit-interval to restore the default.

Syntax

bfd min-transmit-interval interval

undo bfd min-transmit-interval

Default

The minimum interval for transmitting single-hop BFD control packets is 500 milliseconds.

Views

Interface view

BFD template view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting single-hop BFD control packets, in milliseconds. The value range for this argument is 10 to 2000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the device capability.

The actual BFD control packet transmitting interval on the local end is the greater value between the following values:

·     Minimum interval for transmitting BFD control packets on the local end.

·     Minimum interval for receiving BFD control packets on the peer end.

Examples

# Set the minimum interval for transmitting single-hop BFD control packets to 500 milliseconds on GigabitEthernet 1/0.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0

[Sysname-GigabitEthernet1/0] bfd min-transmit-interval 500

bfd multi-hop authentication-mode

Use bfd multi-hop authentication-mode to configure the authentication mode for multihop BFD control packets.

Use undo bfd multi-hop authentication-mode to restore the default.

Syntax

bfd multi-hop authentication-mode{ m-md5 | m-sha1 | md5 | sha1 | simple } key-id { cipher | plain } string

undo bfd multi-hop authentication-mode

Default

No authentication is performed.

Views

System view

Predefined user roles

network-admin

Parameters

m-md5: Specifies the Meticulous MD5 algorithm.

m-sha1: Specifies the Meticulous SHA1 algorithm.

md5: Specifies the MD5 algorithm.

sha1: Specifies the SHA1 algorithm.

simple: Specifies the simple authentication mode.

key-id: Sets the authentication key ID in the range of 1 to 255.

cipher: Specifies a key in encrypted form.

plain: Specifies a key in plaintext form. For security purposes, the key specified in plaintext form will be stored in encrypted form.

string: Specifies the key. Its plaintext form is a case-sensitive string of 1 to 16 characters. Its encrypted form is a case-sensitive string of 33 to 53 characters.

Usage guidelines

Use this command to enhance BFD session security.

BFD version 0 does not support this command. The configuration does not take effect.

Examples

# Configure the simple authentication mode for multihop BFD control packets, setting the authentication key ID to 1 and key to 123456.

<Sysname> system-view

[Sysname] bfd multi-hop authentication-mode simple 1 plain 123456

bfd multi-hop destination-port

Use bfd multi-hop destination-port to configure the destination port number for multihop BFD control packets.

Use undo bfd multi-hop destination-port to restore the default.

Syntax

bfd multi-hop destination-port port-number

undo bfd multi-hop destination-port

Default

The destination port number for multihop BFD control packets is 4784.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies the destination port number of multihop BFD control packets, 3784 or 4784.

Examples

# Specify the destination port number for multihop BFD control packets as 3784.

<Sysname> system-view

[Sysname] bfd multi-hop destination-port 3784

bfd multi-hop detect-multiplier

Use bfd multi-hop detect-multiplier to set the multihop detection time multiplier for control packet mode and echo packet mode.

Use undo bfd multi-hop detect-multiplier to restore the default.

Syntax

bfd multi-hop detect-multiplier value

undo bfd multi-hop detect-multiplier

Default

The multihop detection time multiplier is 5 for control packet mode and echo packet mode.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies the multihop detection time multiplier in the range of 3 to 50.

Usage guidelines

The detection time multiplier determines the maximum number of concurrent BFD control packets that can be discarded.

Table 2 Actual detection interval calculation method

Mode	Actual detection interval of the sender
Echo packet mode	Detection time multiplier of the sender × actual packet sending interval of the sender
Control packet mode BFD session in asynchronous mode	Detection time multiplier of the receiver × MAX (minimum receiving interval supported by the sender, minimum sending interval supported by the receiver)
Control packet mode BFD session in demand mode	Detection time multiplier of the sender × MAX (minimum sending interval supported by the sender, minimum receiving interval supported by the receiver)

 

Examples

# Set the multihop detection time multiplier to 6.

<Sysname> system-view

[Sysname] bfd multi-hop detect-multiplier 6

bfd multi-hop min-echo-receive-interval

Use bfd multi-hop min-echo-receive-interval to set the minimum interval for receiving multihop BFD echo packets.

Use undo bfd multi-hop min-echo-receive-interval to restore the default.

Syntax

bfd multi-hop min-echo-receive-interval interval

undo bfd multi-hop min-echo-receive-interval

Default

The minimum interval for receiving multihop BFD echo packets is 500 milliseconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving multihop BFD echo packets, in milliseconds. The value takes 0 or is in the range of 10 to 2000.

Usage guidelines

The interval for receiving multihop BFD echo packets is also the interval for sending multihop BFD echo packets. By executing this command, you can control both the receiving interval and sending interval for multihop BFD echo packets.

This command takes effect only on static BFD sessions for multihop detection with echo packets.

Examples

# Set the minimum interval for receiving multihop BFD echo packets to 500 milliseconds.

<Sysname> system-view

[Sysname] bfd multi-hop min-echo-receive-interval 500

Related commands

bfd static

bfd multi-hop min-receive-interval

Use bfd multi-hop min-receive-interval to set the minimum interval for receiving multihop BFD control packets.

Use undo bfd multi-hop min-receive-interval to restore the default.

Syntax

bfd multi-hop min-receive-interval interval

undo bfd multi-hop min-receive-interval

Default

The minimum interval for receiving multihop BFD control packets is 500 milliseconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving multihop BFD control packets, in milliseconds. The value range for this argument is 10 to 2000.

Usage guidelines

Use this command to prevent the packet sending rate of the peer end from exceeding the packet receiving capability (minimum control packet receiving interval) of the local end. If the receiving capability is exceeded, the peer end dynamically adjusts the BFD control packet sending interval to the minimum control packet receiving interval of the local end.

Examples

# Set the minimum interval for receiving multihop BFD control packets to 500 milliseconds.

<Sysname> system-view

[Sysname] bfd multi-hop min-receive-interval 500

bfd multi-hop min-transmit-interval

Use bfd multi-hop min-transmit-interval to set the minimum interval for transmitting multihop BFD control packets.

Use undo bfd multi-hop min-transmit-interval to restore the default.

Syntax

bfd multi-hop min-transmit-interval interval

undo bfd multi-hop min-transmit-interval

Default

The minimum interval for transmitting multihop BFD control packets is 500 milliseconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting multihop BFD control packets, in milliseconds. The value range for this argument is 10 to 2000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the device capability.

The actual BFD control packet transmitting interval on the local end is the greater value between the following values:

·     Minimum interval for transmitting BFD control packets on the local end.

·     Minimum interval for receiving BFD control packets on the peer end.

Examples

# Set the minimum interval for transmitting multihop BFD control packets to 500 milliseconds.

<Sysname> system-view

[Sysname] bfd multi-hop min-transmit-interval 500

bfd session init-mode

Use bfd session init-mode to configure the mode for establishing a BFD session.

Use undo bfd session init-mode to restore the default.

Syntax

bfd session init-mode { active | passive }

undo bfd session init-mode

Default

BFD uses the active mode.

Views

System view

Predefined user roles

network-admin

Parameters

active: Specifies the active mode. In active mode, BFD actively transmits BFD control packets to the remote device, regardless of whether it receives a BFD control packet from the remote device.

passive: Specifies the passive mode. In passive mode, BFD does not actively transmit a BFD control packet to the remote end; it transmits a BFD control packet only after receiving a BFD control packet from the remote end.

Usage guidelines

A minimum of one end must operate in active mode for a BFD session to be established.

BFD version 0 does not support this command. The configuration does not take effect.

Examples

# Configure the session establishment mode as passive.

<Sysname> system-view

[Sysname] bfd session init-mode passive

bfd template

Use bfd template to create a BFD template and enter its view, or enter the view of an existing BFD template.

Use undo bfd template to delete the BFD template.

Syntax

bfd template template-name

undo bfd template template-name

Default

No BFD templates exist.

Views

System view

Predefined user roles

network-admin

Parameters

template-name: Specifies the template name, a case-sensitive string of 1 to 63 characters.

Examples

# Create BFD template bfd1 and enter BFD template view.

<Sysname> system-view

[Sysname] bfd template bfd1

[Sysname-bfd-template-bfd1]

display bfd session

Use display bfd session to display BFD session information.

Syntax

display bfd session [ discriminator local local-value | verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

discriminator local local-value: Specifies a BFD session by its local discriminator in the range of 1 to 4294967295.

static session-name: Specifies a static BFD session by its name, a case-sensitive string of 1 to 15 characters.

verbose: Displays detailed BFD session information.

Examples

# Display brief information about all BFD sessions.

<Sysname> display bfd session

 Total sessions: 9        Up sessions: 9        Init mode: Active

 

 IPv4 session working in control packet mode:

 

 LD/RD           SourceIP        DestinationIP   State   Holdtime    Interface

 513/513         1.1.1.1         1.1.1.2         Up      2297ms      GE1/0

 

 IPv6 session working in control packet mode:

 

       Local discr: 513                  Remote discr: 513

         Source IP: FE80::20C:29FF:FED4:7171

    Destination IP: FE80::20C:29FF:FE72:AC4D

     Session state: Up                      Interface: GE1/0

         Hold time: 2142ms

 

IPv4 static session working in echo mode:

 

 LD              SourceIP        DestinationIP   State   Holdtime    Interface

 1226            192.168.51.1    192.168.51.5    Up      4238ms      GE1/0

 

 IPv6 static session working in echo mode:

 

       Local discr: 2012

         Source IP: 15::1

    Destination IP: 15::5

     Session state: Up                      Interface: GE1/0

         Hold time: 4626ms

 

 MPLS LSP session working in control packet mode:

 

 LD/RD           SourceIP        DestinationIP   State   Holdtime    Interface

 32769/32769     2.2.2.9         127.0.0.1       Up      4990ms      N/A

 

 MPLS TE session working in echo mode:

 

 LD              SourceIP        DestinationIP   State   Holdtime    Interface

 32777           1.1.1.1         3.3.3.3         Up      4430ms      Tun0

 

 MPLS PW session working in control packet mode:

 

 LD/RD           SourceIP        DestinationIP   State   Holdtime    Interface

 20481/20481     2.2.2.2         127.0.0.1       Up      2489ms      N/A

Table 3 Command output

Field	Description
Total sessions	Total number of BFD sessions.
Up sessions	Total number of active BFD sessions.
Init mode	BFD operating mode: Active or Passive.
IPv4 session working in control packet mode	BFD session type and operating mode: ·     IPv4 session working in control packet mode. ·     IPv4 session working in echo mode. ·     IPv6 session working in control packet mode. ·     IPv6 session working in echo mode. ·     IPv4 static session working in echo mode. ·     IPv6 static session working in echo mode. ·     MPLS LSP session working in control packet mode—BFD session in control mode used to detect failures in an LSP. ·     MPLS LSP session working in echo mode—BFD session in echo mode used to detect failures in an LSP. ·     MPLS TE session working in control packet mode. ·     MPLS TE session working in echo mode. ·     MPLS PW session working in control packet mode.
LD/RD	Local discriminator/Remote discriminator of the session.
Source IP	Source IPv4 address of the session.
Destination IP	Destination IPv4 address of the session.
State	Session state: Down, Init, Adown, or Up.
Holdtime	Length of time before session detection timer expires. For a BFD session in Down state, this field displays 0ms.
Interface	Name of the interface of the session.
Local discr	Local discriminator of the session.
Remote discr	Remote discriminator of the session.
Session state	Session state: Down, Adown, Init, or Up.
Hold time	Length of time before session detection timer expires. For a BFD session in Down state, this field displays 0ms.

‌

# Display detailed information about all BFD sessions.

<Sysname> display bfd session verbose

 Total sessions: 9        Up sessions: 9        Init mode: Active

 

 IPv4 session working in control packet mode:

          Local discr: 33793                      Remote discr: 33793

            Source IP: 23.1.1.2                 Destination IP: 23.1.1.3

        Session state: Up

            Interface: GigabitEthernet1/0

      Min Tx interval: 1000ms               Actual Tx interval: 1000ms

      Min Rx interval: 1000ms                   Detection time: 5000ms

             Rx count: 133                            Tx count: 142

      Connection type: Direct                      Up duration: 00:02:01

            Hold time: 4571ms                        Auth mode: None

       Detection mode: Async                              Slot: 0

             Protocol: OSPF

              Version: 1

            Diag info: No Diagnostic

 

 

 IPv6 session working in control packet mode:

          Local discr: 33794                      Remote discr: 33794

            Source IP: FE80::5457:A5FF:FE0F:306

       Destination IP: FE80::5457:A1FF:FEB5:206

        Session state: Up

            Interface: GigabitEthernet1/0

      Min Tx interval: 1000ms               Actual Tx interval: 1000ms

      Min Rx interval: 1000ms                   Detection time: 5000ms

             Rx count: 3262                           Tx count: 3048

      Connection type: Direct                      Up duration: 00:44:26

            Hold time: 4409ms                        Auth mode: None

       Detection mode: Async                              Slot: 0

             Protocol: OSPFv3

              Version: 1

            Diag info: No Diagnostic

 

 

 IPv4 static session working in echo mode:

         Session name: aa

          Local discr: 1226

            Source IP: 192.168.51.1             Destination IP: 192.168.51.5

        Session state: Up

            Interface: GigabitEthernet1/0

            Hold time: 4965ms               Actual Tx interval: 1000ms

      Min Rx interval: 1000ms                   Detection time: 5000ms

             Rx count: 308                            Tx count: 308

      Connection type: Direct                      Up duration: 00:04:28

       Detection mode: Async                              Slot: 0

             Protocol: STATIC_IPv4

              Version: 1

            Diag info: No Diagnostic

 

 

 IPv6 static session working in echo mode:

         Session name: bb

          Local discr: 2012

            Source IP: 15::1                    Destination IP: 15::5

        Session state: Up

            Interface: GigabitEthernet1/0

            Hold time: 4426ms               Actual Tx interval: 1000ms

      Min Rx interval: 1000ms                   Detection time: 5000ms

             Rx count: 193                            Tx count: 193

      Connection type: Direct                      Up duration: 00:02:46

       Detection mode: Async                              Slot: 0

             Protocol: STATIC_IPv6

              Version: 1

            Diag info: No Diagnostic

 

 

 MPLS LSP session working in control packet mode:

          Local discr: 32769                      Remote discr: 32769

            Source IP: 3.3.3.9                  Destination IP: 2.2.2.9

        Session state: Up

            Interface: N/A

      Min Tx interval: 1000ms               Actual Tx interval: 1000ms

      Min Rx interval: 1000ms                   Detection time: 5000ms

             Rx count: 1778                           Tx count: 1669

      Connection type: Indirect                    Up duration: 00:24:14

            Hold time: 4248ms                        Auth mode: None

       Detection mode: Async                              Slot: 0

             Protocol: MPLS_LSPV

              Version: 1

            Diag info: No Diagnostic

 

 

 MPLS TE session working in echo mode:

          Local discr: 32777

            Source IP: 1.1.1.1                  Destination IP: 3.3.3.3

        Session state: Up

            Interface: Tunnel0

            Hold time: 4450ms               Actual Tx interval: 1000ms

      Min Rx interval: 1000ms                   Detection time: 5000ms

             Rx count: 320                            Tx count: 320

      Connection type: Indirect                    Up duration: 00:04:35

       Detection mode: Async                              Slot: 0

             Protocol: MPLS_LSPV

              Version: 1

            Diag info: No Diagnostic

 

 

 MPLS PW session working in control packet mode:

          Local discr: 20481                      Remote discr: 20481

            Source IP: 2.2.2.2                  Destination IP: 127.0.0.1

        Session state: Up

            Interface: N/A

      Min Tx interval: 500ms                Actual Tx interval: 500ms

      Min Rx interval: 500ms                    Detection time: 2500ms

             Rx count: 72                             Tx count: 73

      Connection type: Indirect                    Up duration: 00:00:30

            Hold time: 2489ms                        Auth mode: None

       Detection mode: Async                              Slot: 0

             Protocol: MPLS_LSPV

              Version: 1

            Diag info: No Diagnostic

Table 4 Command output

Field	Description
Total sessions	Total number of BFD sessions.
Up sessions	Total number of active BFD sessions.
Init mode	BFD operating mode: Active or Passive.
IPv4 session working in control packet mode	BFD session type and operating mode: ·     IPv4 session working in control packet mode. ·     IPv4 session working in echo mode. ·     IPv6 session working in control packet mode. ·     IPv6 session working in echo mode. ·     IPv4 static session working in echo mode. ·     IPv6 static session working in echo mode. ·     MPLS LSP session working in control packet mode—BFD session in control mode used to detect failures in an LSP. ·     MPLS LSP session working in echo mode—BFD session in echo mode used to detect failures in an LSP. ·     MPLS TE session working in control packet mode. ·     MPLS TE session working in echo mode. ·     MPLS PW session working in control packet mode.
Local discr	Local ID of the session.
Remote discr	Remote ID of the session.
Source IP	Source IP address of the session.
Destination IP	Destination IP address of the session.
Session state	Session state: Down, Init, or Up.
Interface	Name of the interface of the session.
Min Tx interval	Minimum transmit interval.
Min Rx interval	Minimum receive interval.
Actual Tx interval	Actual transmit interval.
Detection time	Actual session detection timer.
Rx count	Number of packets received.
Tx count	Number of packets sent.
Connection type	Connection type of the interface: Direct or indirect.
Up duration	Time period for which the session has been up.
Hold time	Length of time before session detection timer expires. For a BFD session in down state, this field displays 0ms.
Auth mode	Session authentication mode.
Connect type	Connection type of the interface: Direct or indirect.
Up duration	Time period for which the session has been up.
Detection mode	Detection mode: ·     Async—Asynchronous mode. ·     Demand—Demand mode. ·     Async/Echo—Asynchronous mode with echo function enabled. ·     Demand/Echo—Demand mode with echo function enabled.
Slot	(In standalone mode.) Slot number of the device. (In IRF mode.) Slot number of the card where the BFD session resides.
Protocol	Protocol associated with BFD: ·     OSPF. ·     ISIS_BR_L1—IS-IS with the network type as broadcast and the router type as Level 1. ·     ISIS_BR_L2—IS-IS with the network type as broadcast and the router type as Level 2. ·     ISIS_P2P—IS-IS with the network type as P2P. ·     ISIS6_BR_L1—IPv6 IS-IS with the network type as broadcast and the router type as Level 1. ·     ISIS6_BR_L2—IPv6 IS-IS with the network type as broadcast and the router type as Level 2. ·     ISIS6_P2P—IPv6 IS-IS with the network type as P2P. ·     BGP. ·     MPLS_RSVP. ·     STATIC4—IPv4 static routing. ·     TRACK—Track. ·     RIP. ·     IPFRR—FIB IP FRR. ·     MAD. ·     MPLS_LSPV. ·     OSPFv3. ·     BGP4+. ·     PIM. ·     PIM6—IPv6 PIM. ·     STATIC6—IPv6 static routing. ·     RIPNG—RIPng. ·     Interface—Interface state. ·     TUNNEL. ·     VTEP—BFD session used to detect VTEPs. ·     LAGG—Link aggregation.
Diag info	Diagnostic information about the session: ·     No Diagnostic. ·     Control Detection Time Expired—A control-mode BFD session goes down because local detection times out. ·     Echo Function Failed—An echo-mode BFD session goes down, because local detection times out or the source IP address of echo packets is deleted. ·     Neighbor Signaled Session Down—The remote end notifies the local end of BFD session down. ·     Administratively Down—The local system prevents a BFD session from being established.

‌

reset bfd session statistics

Use reset bfd session statistics to clear the BFD session statistics.

Syntax

reset bfd session statistics

Views

User view

Predefined user roles

network-admin

Examples

# Clear the BFD session statistics.

<Sysname> reset bfd session statistics

snmp-agent trap enable bfd

Use snmp-agent trap enable bfd to enable SNMP notifications for BFD.

Use undo snmp-agent trap enable bfd to disable SNMP notifications for BFD.

Syntax

snmp-agent trap enable bfd

undo snmp-agent trap enable bfd

Default

All SNMP notifications are enabled for BFD.

Views

System view

Predefined user roles

network-admin

Usage guidelines

To report critical BFD events to an NMS, enable SNMP notifications for BFD. For BFD event notifications to be sent correctly, you must also configure SNMP as described in the network management and monitoring configuration guide for the device.

Examples

# Disable SNMP notifications for BFD.

<Sysname> system-view

[Sysname] undo snmp-agent trap enable bfd