Configure OSPF
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
Cloud Management of NGFWs
- Cloud Management of NGFWs
- PAN-OS 10.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0 (EoL)
- PAN-OS 11.1 & Later
- PAN-OS 9.1 (EoL)
-
-
-
- Configure a Filter Access List
- Configure a Filter Prefix List
- Configure a Filter Community List
- Configure a BGP Filter Route Map
- Configure a Filter Route Maps Redistribution List
- Configure a Filter AS Path Access List
- Configure an Address Family Profile
- Configure a BGP Authentication Profile
- Configure a BGP Redistribution Profile
- Configure a BGP Filtering Profile
- Configure an OSPF Authentication Profile
- Configure a Logical Router
- Configure a Static Route
- Configure OSPF
- Configure BGP
- Configure an IPSec Tunnel
- Web Proxy
- Cheat Sheet: GlobalProtect for Cloud Management of NGFWs
-
PAN-OS 11.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0 (EoL)
- PAN-OS 11.1 & Later
-
- 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 a PPPoE Client on a Subinterface
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DHCP Overview
- Firewall as a DHCP Server and Client
- Firewall as a DHCPv6 Client
- DHCP Messages
- Configure an Interface as a DHCP Server
- Configure an Interface as a DHCPv4 Client
- Configure an Interface as a DHCPv6 Client with Prefix Delegation
- Configure the Management Interface as a DHCP Client
- Configure an Interface as a DHCP Relay Agent
-
- 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
- Configure MSDP
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
-
-
Cloud Management and AIOps for NGFW
- Cloud Management and AIOps for NGFW
- PAN-OS 10.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0 (EoL)
- PAN-OS 11.1
- PAN-OS 11.2
- PAN-OS 8.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 9.1 (EoL)
End-of-Life (EoL)
Configure OSPF
After you understand OSPF Concepts, perform
the following procedure to configure OSPF.
- Configure general virtual router settings.
- Enable OSPF.
- Select the OSPF tab.
- Select Enable to enable the OSPF protocol.
- Enter the Router ID.
- Select Reject Default Route if you do not want to learn any default routes through OSPF. This is the recommended, default setting.Clear Reject Default Route if you want to permit redistribution of default routes through OSPF.
- Configure Areas - Type for the OSPF protocol.
- On the Areas tab, Add an Area ID for the area in x.x.x.x format. This is the identifier that each neighbor must accept to be part of the same area.
- On the Type tab, select one of the following from the area Type list:
- Normal—There are no restrictions; the area can carry all types of routes.
- Stub—There is no outlet from the area. To reach a destination outside of the area, it is necessary to go through the border, which connects to other areas. If you select this option, configure the following:
- Accept Summary—Link state advertisements (LSA) are accepted from other areas. If this option on a stub area Area Border Router (ABR) interface is disabled, the OSPF area will behave as a Totally Stubby Area (TSA) and the ABR will not propagate any summary LSAs.
- Advertise Default Route—Default route LSAs will be included in advertisements to the stub area along with a configured metric value in the configured range 1-255.
- NSSA (Not-So-Stubby Area)—The firewall can leave the area only by routes other than OSPF routes. If you select NSSA, select Accept Summary and Advertise Default Route as described for Stub. If you select this option, configure the following:
- Type—Select either Ext 1 or Ext 2 route type to advertise the default LSA.
- Ext Ranges—Add ranges of external routes that you want to Advertise or for which you want to Suppress advertising.
- Click OK.
- Configure Areas - Range for the OSPF protocol
- On the Range tab, Add aggregate LSA destination addresses in the area into subnets.
- Advertise or Suppress advertising LSAs that match the subnet, and click OK. Repeat to add additional ranges.
- Configure Areas - Interfaces for the OSPF protocol
- On the Interface tab, Add the following information for each interface to be included in the area:
- Interface—Select an interface.
- Enable—Selecting this option causes the OSPF interface settings to take effect.
- Passive—Select if you do not want the OSPF interface to send or receive OSPF packets. Although OSPF packets are not sent or received if you choose this option, the interface is included in the LSA database.
- Link type—Choose Broadcast if you want all neighbors that are accessible through the interface to be discovered automatically by multicasting OSPF hello messages, such as an Ethernet interface. Choose p2p (point-to-point) to automatically discover the neighbor. Choose p2mp (point-to-multipoint) when neighbors must be defined manually and Add the neighbor IP addresses for all neighbors that are reachable through this interface.
- Metric—Enter an OSPF metric for this interface (range is 0-65,535; default is 10).
- Priority—Enter an OSPF priority for this interface. This is the priority for the router to be elected as a designated router (DR) or as a backup DR (BDR) (range is 0-255; default is 1). If zero is configured, the router will not be elected as a DR or BDR.
- Auth Profile—Select a previously-defined authentication profile.
- Timing—Modify the timing settings if desired (not recommended). For details on these settings, refer to the online help.
- Click OK.
- Configure Areas - Virtual Links.
- On the Virtual Link tab, Add the following information for each virtual link to be included in the backbone area:
- Name—Enter a name for the virtual link.
- Enable—Select to enable the virtual link.
- Neighbor ID—Enter the router ID of the router (neighbor) on the other side of the virtual link.
- Transit Area—Enter the area ID of the transit area that physically contains the virtual link.
- Timing—It is recommended that you keep the default timing settings.
- Auth Profile—Select a previously-defined authentication profile.
- Click OK to save virtual links.
- Click OK to save area.
- (Optional) Configure Auth Profiles.By default, the firewall does not use OSPF authentication for the exchange between OSPF neighbors. Optionally, you can configure OSPF authentication between OSPF neighbors by either a simple password or using MD5 authentication. MD5 authentication is recommended; it is more secure than a simple password.Simple Password OSPF authentication
- Select the Auth Profiles tab and Add a name for the authentication profile to authenticate OSPF messages.
- Select Simple Password as the Password Type.
- Enter a simple password and then confirm.
MD5 OSPF authentication- Select the Auth Profiles tab and Add a name for the authentication profile to authenticate OSPF messages.
- Select MD5 as the Password Type and Add one or more password entries, including:
- Key-ID (range is 0-255)
- Key
- Select the Preferred option to specify that the key be used to authenticate outgoing messages.
- Click OK.
- Configure Advanced OSPF options.
- On the Advanced tab, select RFC 1583 Compatibility to ensure compatibility with RFC 1583.
- Specify a value for the SPF Calculation Delay (sec) timer, which allows you to tune the delay time (in seconds) between receiving new topology information and performing an SPF calculation. Lower values enable faster OSPF re-convergence. Routers peering with the firewall should use the same delay value to optimize convergence times.
- Specify a value for the LSA Interval (sec) timer, which is the minimum time between transmissions of two instances of the same LSA (same router, same type, same LSA ID). This is equivalent to MinLSInterval in RFC 2328. Lower values can be used to reduce re-convergence times when topology changes occur.
- Click OK.
- Commit your changes.