OSPF Areas
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
OSPF
Areas
OSPF operates within a single autonomous system (AS).
Networks within this single AS, however, can be divided into a number
of areas. By default, Area 0 is created. Area 0 can either function
alone or act as the OSPF backbone for a larger number of areas.
Each OSPF area is named using a 32-bit identifier which in most
cases is written in the same dotted-decimal notation as an IP4 address.
For example, Area 0 is usually written as 0.0.0.0.
The topology of an area is maintained in its own link state database
and is hidden from other areas, which reduces the amount of traffic
routing required by OSPF. The topology is then shared in a summarized
form between areas by a connecting router.
OSPF Area Type | Description |
---|---|
Backbone Area | The backbone area (Area 0) is the core of
an OSPF network. All other areas are connected to it and all traffic
between areas must traverse it. All routing between areas is distributed
through the backbone area. While all other OSPF areas must connect
to the backbone area, this connection doesn’t need to be direct
and can be made through a virtual link. |
Normal OSPF Area | In a normal OSPF area there are no restrictions;
the area can carry all types of routes. |
Stub OSPF Area | A stub area does not receive routes from
other autonomous systems. Routing from the stub area is performed
through the default route to the backbone area. |
NSSA Area | The Not So Stubby Area (NSSA) is a type
of stub area that can import external routes, with some limited
exceptions. |