Reference: BFD Details
Table of Contents
Expand all | Collapse all
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
Reference: BFD Details
To see the following BFD information
for a virtual router, refer to Step 12 of Configure BFD, View BFD
summary and details.
Name | Value (Example) | Description |
|---|---|---|
Session ID | 1 | ID number of the BFD session. |
Interface | ethernet1/12 | Interface you selected where BFD is running. |
Protocol | STATIC(IPV4) OSPF | Static route (IP address family of static
route) and/or dynamic routing protocol that is running BFD on the
interface. |
Local IP Address | 10.55.55.2 | IP address of interface. |
Neighbor IP Address | 10.55.55.1 | IP address of BFD neighbor. |
BFD Profile | default *(This BFD session has multiple
BFD profiles. Lowest ‘Desired Minimum Tx Interval (ms)’ is used
to select the effective profile.) | Name of BFD profile applied to the interface. Because
the sample interface has both a static route and OSPF running BFD
with different profiles, the firewall uses the profile with the
lowest Desired Minimum Tx Interval . In this
example, the profile used is the default profile. |
State (local/remote) | up/up | BFD states of the local and remote BFD peers. Possible
states are admin down, down, init, and up. |
Up Time | 2h 36m 21s 419ms | Length of time BFD has been up (hours, minutes,
seconds, and milliseconds). |
Discriminator (local/remote) | 1391591427/1 | Discriminators for local and remote BFD peers. |
Mode | Active | Mode in which BFD is configured on the interface:
Active or Passive. |
Demand Mode | Disabled | PAN-OS does not support BFD Demand Mode, so
it is always in Disabled state. |
Multihop | Disabled | BFD multihop: Enabled or Disabled. |
Multihop TTL | TTL of multihop; range is 1-254. Field is
empty if Multihop is disabled. | |
Local Diag Code | 0 (No Diagnostic) | Diagnostic codes indicating the reason for
the local system’s last change in state: 0—No Diagnostic 1—Control
Detection Time Expired 2—Echo Function Failed 3—Neighbor
Signaled Session Down 4—Forwarding Plane Reset 5—Path
Down 6—Concatenated Path Down 7—Administratively Down 8—Reverse
Concatenated Path Down |
Last Received Remote Diag Code | 0 (No Diagnostic) | Diagnostic code last received from BFD peer. |
Transmit Hold Time | 0ms | Hold time (in milliseconds) after a link
comes up before BFD transmits BFD control packets. A hold time of
0ms means to transmit immediately. Range is 0-120000ms. |
Received Min Rx Interval | 1000ms | Minimum Rx interval received from the peer; the
interval at which the BFD peer can receive control packets. Maximum
is 2000ms. |
Negotiated Transmit Interval | 1000ms | Transmit interval (in milliseconds) that
the BFD peers have agreed to send BFD control packets to each other.
Maximum is 2000ms. |
Received Multiplier | 3 | Detection time multiplier value received
from the BFD peer. The Transmit Time multiplied by the Multiplier
equals the detection time. If BFD does not receive a BFD control
packet from its peer before the detection time expires, a failure
has occurred. Range is 2-50. |
Detect Time (exceeded) | 3000ms (0) | Calculated detection time (Negotiated Transmit Interval
multiplied by Multiplier) and the number of milliseconds the detection
time is exceeded. |
Tx Control Packets (last) | 9383 (420ms ago) | Number of BFD control packets transmitted (and
length of time since BFD transmitted the most recent control packet). |
Rx Control Packets (last) | 9384 (407ms ago) | Number of BFD control packets received (and length
of time since BFD received the most recent control packet). |
Agent Data Plane | Slot 1 - DP 0 | On PA-7000 Series firewalls, the dataplane CPU
that is assigned to handle packets for this BFD session. |
Errors | 0 | Number of BFD errors. |
Last Packet Causing State
Change | ||
Version | 1 | BFD version. |
Poll Bit | 0 | BFD poll bit; 0 indicates not set. |
Desired Min Tx Interval | 1000ms | Desired minimum transmit interval of last packet
causing state change. |
Required Min Rx Interval | 1000ms | Required minimum receive interval of last packet
causing state change. |
Detect Multiplier | 3 | Detect Multiplier of last packet causing
state change. |
My Discriminator | 1 | Remote discriminator. A discriminator is
a unique, nonzero value the peers use to distinguish multiple BFD
sessions between them. |
Your Discriminator | 1391591427 | Local discriminator. A discriminator is
a unique, nonzero value the peers use to distinguish multiple BFD
sessions between them. |
Diagnostic Code | 0 (No Diagnostic) | Diagnostic code of last packet causing state change. |
Length | 24 | Length of BFD control packet in bytes. |
Demand Bit | 0 | PAN-OS does not support BFD Demand mode, so
Demand Bit is always set to 0 (disabled). |
Final Bit | 0 | PAN-OS does not support the Poll Sequence, so
Final Bit is always set to 0 (disabled). |
Multipoint Bit | 0 | This bit is reserved for future point-to-multipoint
extensions to BFD. It must be zero on both transmit and receipt. |
Control Plane Independent Bit | 1 |
|
Authentication Present Bit | 0 | PAN-OS does not support BFD Authentication, so
the Authentication Present Bit is always set to 0. |
Required Min Echo Rx Interval | 0ms | PAN-OS does not support the BFD Echo function,
so this will always be 0ms. |