Configure OSPF
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
Configure OSPF
After you understand OSPF Concepts, perform
the following procedure to configure OSPF.
- Configure general virtual router settings.
- Enable OSPF.
- Select theOSPFtab.
- SelectEnableto enable the OSPF protocol.
- Enter theRouter ID.
- SelectReject Default Routeif you do not want to learn any default routes through OSPF. This is the recommended, default setting.ClearReject Default Routeif you want to permit redistribution of default routes through OSPF.
- Configure Areas - Type for the OSPF protocol.
- On theAreastab,AddanArea IDfor 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 theTypetab, select one of the following from the areaTypelist:
- 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, selectAccept SummaryandAdvertise Default Routeas described forStub. If you select this option, configure the following:
- Type—Select eitherExt 1orExt 2route type to advertise the default LSA.
- Ext Ranges—Addranges of external routes that you want toAdvertiseor for which you want toSuppressadvertising.
- ClickOK.
- Configure Areas - Range for the OSPF protocol
- On theRangetab,Addaggregate LSA destination addresses in the area into subnets.
- AdvertiseorSuppressadvertising LSAs that match the subnet, and clickOK. Repeat to add additional ranges.
- Configure Areas - Interfaces for the OSPF protocol
- On theInterfacetab,Addthe 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—ChooseBroadcastif you want all neighbors that are accessible through the interface to be discovered automatically by multicasting OSPF hello messages, such as an Ethernet interface. Choosep2p(point-to-point) to automatically discover the neighbor. Choosep2mp(point-to-multipoint) when neighbors must be defined manually andAddthe 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.
- ClickOK.
- Configure Areas - Virtual Links.
- On theVirtual Linktab,Addthe 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.
- ClickOKto save virtual links.
- ClickOKto 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 theAuth Profilestab andAdda name for the authentication profile to authenticate OSPF messages.
- SelectSimple Passwordas thePassword Type.
- Enter a simple password and then confirm.
MD5 OSPF authentication- Select theAuth Profilestab andAdda name for the authentication profile to authenticate OSPF messages.
- SelectMD5as thePassword TypeandAddone or more password entries, including:
- Key-ID (range is 0-255)
- Key
- Select thePreferredoption to specify that the key be used to authenticate outgoing messages.
- ClickOK.
- Configure Advanced OSPF options.
- On theAdvancedtab, selectRFC 1583 Compatibilityto ensure compatibility with RFC 1583.
- Specify a value for theSPF 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 theLSA 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.
- ClickOK.
- Commityour changes.