BFD for Static Routes
Table of Contents
10.1
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
BFD
for Static Routes
To use BFD on a static route, both the firewall and
the peer at the opposite end of the static route must support BFD
sessions. A static route can have a BFD profile only if the
Next
Hop
type is IP Address
.If an interface is configured with more than one static route
to a peer (the BFD session has the same source IP address and same
destination IP address), a single BFD session automatically handles
the multiple static routes. This behavior reduces BFD sessions.
If the static routes have different BFD profiles, the profile with
the smallest
Desired Minimum Tx Interval
takes
effect.In a deployment where you want to configure BFD for a static
route on a DHCP or PPPoE client interface, you must perform two
commits. Enabling BFD for a static route requires that the
Next
Hop
type must be IP Address
.
But at the time of a DHCP or PPPoE interface commit, the interface
IP address and next hop IP address (default gateway) are unknown.You must first enable a DHCP or PPPoE client for the interface,
perform a commit, and wait for the DHCP or PPPoE server to send
the firewall the client IP address and default gateway IP address.
Then you can configure the static route (using the default gateway
address of the DHCP or PPPoE client as the next hop), enable BFD, and
perform a second commit.