Study guide
2.2 Static Routing, BGP, and OSPF Configuration & Failover
Palo Alto Networks Certified Next-Generation Firewall Engineer Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Device Deployment & Architecture
1.1 Platform Selection & Sizing: Hardware, VM-Series, and Cloud NGFW Form Factors 1.2 Base PAN-OS 11.x System Settings, Management Interfaces, and Service Routes 1.3 Interface Types, Zone Topologies, and Virtual Wire Configurations 1.4 Site-to-Site VPN Tunnels: IPSec, GRE, and Quantum-Resistant Cryptography
2 Chapter 2: Routing, VRFs, and Virtual Routers
2.1 Virtual Routers and VRF Architecture in PAN-OS 11.x 2.2 Static Routing, BGP, and OSPF Configuration & Failover 2.3 Policy-Based Forwarding (PBF) and Path Monitoring
3 Chapter 3: NAT and High Availability Designs
3.1 Source, Destination, and Twice-NAT Policy Configurations 3.2 High Availability Active/Passive Architecture and State Synchronization 3.3 High Availability Active/Active Architecture and HA Clustering
4 Chapter 4: Panorama Management & Policy Hierarchy
4.1 Panorama Architecture: Collector Groups, Log Collectors, and Device Registration 4.2 Templates and Template Stacks Configuration 4.3 Device Groups, Shared Rulestacks, and Policy Hierarchy
5 Chapter 5: Strata Cloud Manager and AIOps
5.1 Strata Cloud Manager (SCM) Architecture and Cloud-Delivered Management 5.2 SCM Rulestacks, Folder Hierarchies, and Unified Policy Management 5.3 AIOps for NGFW: Telemetry, Proactive Best-Practice Audits, and Operational Insights
6 Chapter 6: Security Profiles and Content Inspection
6.1 Antivirus, Anti-Spyware, and DNS Security Profiles 6.2 Vulnerability Protection, Custom Signatures, and Threat Exceptions 6.3 URL Filtering, Advanced WildFire Analysis, and Inline Deep Learning
7 Chapter 7: Decryption Inspection & Policy
7.1 SSL Forward Proxy Architecture and Internal Certificate Authority Trust 7.2 SSL Inbound Inspection for Internal Web Servers 7.3 Decryption Exclusions, HSM Integration, and Troubleshooting Decryption Failures
8 Chapter 8: User Identity and GlobalProtect Remote Access
8.1 User-ID Architecture, Agentless/Agent Deployment, and Cloud Identity Engine (CIE) 8.2 GlobalProtect Portals, Gateways, and Authentication Methods (SAML, MFA) 8.3 Host Information Profile (HIP) Checks and Endpoint Security Enforcement
9 Chapter 9: Cloud NGFW, Automation, and API Integration
9.1 Cloud NGFW for AWS and Azure Architectures (GWLB and VWAN) 9.2 XML and REST API Automation with Palo Alto Networks Firewalls 9.3 Infrastructure as Code: Terraform and Ansible Automation for PAN-OS 9.4 CN-Series, AI Runtime Security, and Edge Deployment Options
10 Chapter 10: Virtual Systems, Logging, and Operational Monitoring
10.1 Virtual Systems (VSYS), Logical Routers, and Inter-VSYS Routing 10.2 Logging Architecture: Strata Logging Service, Log Forwarding, and Collectors 10.3 Application Command Center (ACC), Dashboards, and Custom Reporting 10.4 Explicit and Transparent Web Proxy on PAN-OS
2.2 Static Routing, BGP, and OSPF Configuration & Failover
Key Takeaways Explain This Topic AI
Static routes require defining a destination prefix, egress interface, next-hop type, metric, and administrative distance; floating static routes use elevated AD for backup path redundancy.
Equal-Cost Multi-Path (ECMP) load balances traffic across up to 4 or 8 equal-cost routes using algorithms such as IP Hash or Balanced Round-Robin.
OSPF implementation in PAN-OS supports OSPFv2 (IPv4) and OSPFv3 (IPv6/IPv4), multiple area types (Backbone, Stub, Totally Stubby, NSSA), and MD5/HMAC authentication.
BGP peer groups simplify configuration by grouping neighbors that share common Autonomous System (AS) settings, import/export policies, and timers.
Bidirectional Forwarding Detection (BFD) provides sub-second failure detection (50ms–300ms) for static routes, OSPF, and BGP, triggering rapid failover far faster than standard protocol keepalives.
Last updated: July 2026
2.2 Static Routing, BGP, and OSPF Configuration & Failover
Palo Alto Networks Next-Generation Firewalls support robust static and dynamic routing protocol suites within Virtual Routers. Network engineers must configure static routes, Open Shortest Path First (OSPF), and Border Gateway Protocol (BGP) to ensure optimal traffic forwarding, high availability, and rapid convergence during link or node failures.
This section covers static route configuration, default route design patterns, OSPF area topologies, BGP autonomous system peering, route redistribution profiles, and Bidirectional Forwarding Detection (BFD) integration.
Static Routes and Default Route Architecture
Static routes are manually configured routing entries used for fixed topology paths, default gateways, and out-of-band management. In PAN-OS, a static route configuration consists of five key attributes:
Destination : The target IPv4 or IPv6 network prefix (e.g., 0.0.0.0/0 for default route, or 10.250.0.0/16 ).
Interface : The egress Layer 3 interface (e.g., ethernet1/1 ).
Next Hop : Specifies the forwarder address type:
IP Address : Next-hop gateway IP.
Next VR : Target Virtual Router for inter-VR routing.
Discard : Drops matching traffic (useful for blackholing summary routes).
None : Used for point-to-point interface types.
Metric : Cost value used to compare routes from the same protocol (default = 10 10 10 ).
Administrative Distance (AD) : Trustworthiness ranking (default = 10 10 10 ).
Floating Static Routes for ISP Redundancy
To implement automatic Internet Service Provider (ISP) failover without dynamic routing:
Primary Static Route : Destination 0.0.0.0/0 , Egress ethernet1/1 (ISP-1), AD = 10 10 10 .
Backup (Floating) Static Route : Destination 0.0.0.0/0 , Egress ethernet1/2 (ISP-2), AD = 20 20 20 .
Because the primary route has a lower AD ( 10 10 10 ), it is installed into the FIB. If ethernet1/1 goes down (or Path Monitoring fails), the primary route is removed, and the floating backup route ( A D = 20 AD = 20 A D = 20 ) is immediately promoted into the FIB.
Equal-Cost Multi-Path (ECMP)
When multiple static or dynamic routes to the same destination have identical AD and Metric values, PAN-OS can distribute traffic across up to 4 or 8 parallel paths (depending on firewall model) using ECMP .
IP Hash : Hashes source and destination IP addresses to ensure session stickiness.
Balanced Round-Robin : Symmetric distribution across active paths.
Symmetric Return : Ensures return flow for a session exits out the exact interface on which the ingress packet arrived.
OSPFv2 and OSPFv3 Implementation
PAN-OS supports OSPFv2 (IPv4 routing) and OSPFv3 (IPv6 and IPv4 routing). OSPF operates within a Virtual Router and requires a unique 32-bit Router ID (formatted as an IP address, e.g., 1.1.1.1 ).
OSPF Area Types in PAN-OS
OSPF networks are hierarchically divided into Areas to constrain Link-State Advertisement (LSA) flooding:
- Area Type Allowed LSAs Default Route Injection Primary Use Case
- Backbone (Area 0.0.0.0) Types 1, 2, 3, 4, 5 Optional Core transit area connecting all other OSPF areas
- Standard Area Types 1, 2, 3, 4, 5 Optional General internal enterprise branch networks
Stub Area Types 1, 2, 3 (No Type 4/5) Automatic (Type 3 LSA) Resource-constrained remote offices blocking external ASBR routes
Totally Stubby Area Types 1, 2 (No Type 3/4/5) Automatic (Type 3 LSA) Branch offices blocking external and inter-area routes
Not-So-Stubby Area (NSSA) Types 1, 2, 3, 7 (No Type 4/5) Configurable (Type 7 LSA) Branches with local external connections (translates Type 7 to Type 5 at ABR)
Totally NSSA Types 1, 2, 7 (No Type 3/4/5) Automatic (Type 3 LSA) NSSA branches blocking inter-area summary LSAs
OSPF Authentication & Timers
OSPFv2 Authentication : Supports Simple Password, MD5, and HMAC-SHA-256 cryptographic keys.
Timers : Hello Interval (default 10s broadcast/point-to-point) and Dead Interval (default 40s). If dead timers expire without receiving a Hello packet, the neighbor adjacency is torn down.
Border Gateway Protocol (BGP) Architecture
BGP is the standard path-vector routing protocol used for internet edge peering, multi-cloud interconnects, and large enterprise cores.
Autonomous System Numbers (ASN)
PAN-OS supports both 16-bit (1–65535) and 32-bit ASNs (expressed in plain number format up to 4,294,967,295 or dot notation ASN.subASN ). Private AS ranges include 64512–65535 and 4200000000–4294967294 .
eBGP vs. iBGP
External BGP (eBGP) : Peering between different ASNs. Default IP TTL is 1 1 1 (requires eBGP Multihop if peers are not directly connected).
Internal BGP (iBGP) : Peering within the same ASN. Enforces the iBGP split-horizon rule (routes learned via iBGP are not advertised to other iBGP peers unless Route Reflectors are configured).
BGP Peer Groups
To scale BGP configurations, PAN-OS utilizes Peer Groups . A Peer Group pools multiple BGP neighbors that share identical policies:
Export / Import Policies : Match criteria (prefix lists, community strings, AS-path regex) and actions (set Local Preference, MED, AS-path prepending).
Keepalive and Hold Timers : Default Keepalive = 30s, Hold Time = 90s.
Soft Reconfiguration & Route Refresh : Allows policy updates without resetting TCP sessions.
Route Redistribution Profiles
Route Redistribution allows a Virtual Router to take routes learned from one protocol (e.g., Connected or Static) and advertise them into another protocol (e.g., OSPF or BGP).
Create a Redistribution Profile : Define name, priority, source protocol (Connected, Static, OSPF, BGP), and match conditions (destination subnets, interface, metric, tag).
Apply to Target Protocol : Under OSPF Export or BGP Export, bind the Redistribution Profile and set egress metrics/origin attributes.
Bidirectional Forwarding Detection (BFD) for Sub-Second Failover
Standard dynamic routing timers can take anywhere from 30 30 30 seconds (BGP keepalives) to 40 40 40 seconds (OSPF dead timer) to detect a physical link failure over an intermediate Ethernet switch or dark fiber circuit.
BFD (Bidirectional Forwarding Detection) provides protocol-independent, low-overhead, sub-second failure detection :
Operation : Microsecond/millisecond hello timers (e.g., 50ms–300ms intervals with a detection multiplier of 3).
Integration : BFD can be enabled on Static Routes, OSPF Interfaces, and BGP Peer Groups.
Failover Action : When BFD detects packet loss exceeding the threshold, it immediately signals the Virtual Router to tear down the routing adjacency and remove associated routes from the FIB in under 100–300 milliseconds .