- Support Forum
- Knowledge Base
- Customer Service
- Internal Article Nominations
- FortiGate
- FortiClient
- FortiADC
- FortiAIOps
- FortiAnalyzer
- FortiAP
- FortiAuthenticator
- FortiBridge
- FortiCache
- FortiCare Services
- FortiCarrier
- FortiCASB
- FortiConverter
- FortiCNP
- FortiDAST
- FortiData
- FortiDDoS
- FortiDB
- FortiDNS
- FortiDLP
- FortiDeceptor
- FortiDevice
- FortiDevSec
- FortiDirector
- FortiEdgeCloud
- FortiEDR
- FortiEndpoint
- FortiExtender
- FortiGate Cloud
- FortiGuard
- FortiGuest
- FortiHypervisor
- FortiInsight
- FortiIsolator
- FortiMail
- FortiManager
- FortiMonitor
- FortiNAC
- FortiNAC-F
- FortiNDR (on-premise)
- FortiNDRCloud
- FortiPAM
- FortiPhish
- FortiPortal
- FortiPresence
- FortiProxy
- FortiRecon
- FortiRecorder
- FortiSRA
- FortiSandbox
- FortiSASE
- FortiSASE Sovereign
- FortiScan
- FortiSIEM
- FortiSOAR
- FortiSwitch
- FortiTester
- FortiToken
- FortiVoice
- FortiWAN
- FortiWeb
- FortiAppSec Cloud
- Lacework
- Wireless Controller
- RMA Information and Announcements
- FortiCloud Products
- ZTNA
- 4D Documents
- Customer Service
- Community Groups
- Blogs
FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
- Fortinet Community
- Knowledge Base
- FortiGate
- Technical Tip: Clarification of 'Registered protoc...
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
| Description | This article describes the meaning of the different 'registered protocols' in the output of 'get router info bfd neighbor detail'. This helps to understand that the BFD neighborship is established based on which protocol. |
| Scope | FortiGate, BFD. |
| Solution |
Bidirectional Forwarding Detection (BFD) is a protocol that helps to quickly locate hardware failures in the network. Routers running BFD send packets to each other at a negotiated rate. If packets from a BFD-enabled router fail to arrive, that router is declared to be down. BFD communicates this information to the associated routing protocols, and the routing information is updated. It helps detect one-way device failure and is used for fast convergence of routing protocols.
BFD can be configured at the device level, interface level, or routing protocol level. Detailed information related to BFD can be found in below official document: Bidirectional Forwarding Detection (BFD)
The command 'get router info bfd neighbor detail' can be used to identify which level the BFD neighbor relationship is configured.
Example 1: device-level BFD neighbor. BFD neighbor on FortiGate-A can be configured at the device-level as follows:
config router bfd
The FortiGate-B on the remote end has the same BFD setting:
config router bfd
The BFD will come up once both ends can connect with each other to share the BFD packets. The output of BFD neighbor detail will be as follows. The Registered Protocol will be 'Static', which means a static BFD neighbor rather than a static route.
site1 (root) # get router info bfd neighbor detail OurAddress NeighAddress State Interface LDesc/RDesc
Example 2: BFD on a static route. Instead of configuring the static BFD neighbor, BFD can also be enabled on the static route as follows on FortiGate-A:
config router static
The FortiGate-B on the remote end still has a static BFD neighbor configured:
config router bfd
With this setup, FortiGate-A will try to establish the BFD neighbor with the gateway IP 10.56.242.129 in the static route. Since the port1 on FortiGate-B has this IP and is with the BFD enabled, the BFD will form as well. The neighbor's details will be as follows. The 'Registered Protocol' for the static route will be 'External' rather than 'Static'.
site1 (root) # get router info bfd neighbor detail OurAddress NeighAddress State Interface LDesc/RDesc
Example 3: BFD on BGP. The BFD can be enabled on the BGP neighbor as well as on FortiGate-A.
config router bgp
Assume the BFD setting on FortiGate-B is still the same as before. The BFD neighbor detail on FortiGate-A will be as follows. The Registered protocols are changed to BGP, which indicates the BFD neighbor is established for the BGP protocol.
site1 (root) # get router info bfd neighbor de OurAddress NeighAddress State Interface LDesc/RDesc
Example 4: BFD on OSPF. The BFD can be used in the OSPF setting as well to monitor the OSPF neighbor status. It needs to be enabled in both the global OSPF setting and the OSPF interface setting:
FortiGate-A configuration:
config router ospf end
Assume the configuration of FortiGate-B remains the same. The BFD neighbor detail on FortiGate-A will be as follows. The Registered protocols are changed to OSPF, which indicates the BFD neighbor is established for the OSPF protocol.
site1 (root) # get router info bfd neighbor detail OurAddress NeighAddress State Interface LDesc/RDesc
The same BFD neighbor can also be established for multiple protocols. Assume the FortiGate-A has a BFD configuration shown in example 1-4; at the same time, the BFD neighbor will be established for all these protocols. The neighbor detail will display all protocols as registered protocols as below:
site1 (root) # get router info bfd neighbor detail OurAddress NeighAddress State Interface LDesc/RDesc
Related articles: Technical Tip: Configuring Bidirectional Forwarding Detection (BFD) for static routes |
Broad. Integrated. Automated.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Security Research
Company
News & Articles
Copyright 2025 Fortinet, Inc. All Rights Reserved.