Tuesday, 10 March 2015

Advanced OSPF Configuration

Generating a Default Route

You can force an autonomous system boundary router to generate a default route into an OSPF routing domain. Whenever you specifically configure redistribution of routes into an OSPF routing domain, the router automatically becomes an autonomous system boundary router. However, an autonomous system boundary router does not by default generate a default route into the OSPF routing domain.
To generate a default route, perform the following steps:

Detailed Steps

 
Command
Purpose
Step 1 

router ospf process_id


Example:

hostname(config)# router ospf 2
This creates an OSPF routing process, and the user enters router configuration mode for this OSPF process.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 

default-information originate [always] 

[metric metric-value] [metric-type {1 | 

2}] [route-map map-name]


Example:

hostname(config-router)# 
default-information originate always

This step forces the autonomous system boundary router to generate a default route.

Configuring Route Summarization When Redistributing Routes into OSPF

When routes from other protocols are redistributed into OSPF, each route is advertised individually in an external LSA. However, you can configure the ASA to advertise a single route for all the redistributed routes that are covered by a specified network address and mask. This configuration decreases the size of the OSPF link-state database.
To configure the software advertisement on one summary route for all redistributed routes covered by a network address and mask, perform the following steps:

Detailed Steps

 
Command
Purpose
Step 1 

router ospf process_id


Example:

hostname(config)# router ospf 1
This creates an OSPF routing process, and the user enters router configuration mode for this OSPF process.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 

summary-address ip_address mask 
[not-advertise] [tag tag]


Example:

hostname(config)# router ospf 1

hostname(config-router)# summary-address 
10.1.0.0 255.255.0.0
This step sets the summary address.
In this example, the summary address 10.1.0.0 includes address 10.1.1.0, 10.1.2.0, 10.1.3.0, and so on. Only the address 10.1.0.0 is advertised in an external link-state advertisement


Configuring Route Summarization Between OSPF Areas

Route summarization is the consolidation of advertised addresses. This feature causes a single summary route to be advertised to other areas by an area boundary router. In OSPF, an area boundary router advertises networks in one area into another area. If the network numbers in an area are assigned in a way such that they are contiguous, you can configure the area boundary router to advertise a summary route that covers all the individual networks within the area that fall into the specified range.
To define an address range for route summarization, perform the following steps:

Detailed Steps

 
Command
Purpose
Step 1 

router ospf process_id


Example:

hostname(config)# router ospf 1
This creates an OSPF routing process, and the user enters router configuration mode for this OSPF process.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 

area area-id range ip-address mask 
advertise | not-advertise]


Example:

hostname(config)# router ospf 1

hostname(config-router)# area 17 range 
12.1.0.0 255.255.0.0
This step sets the address range.
In this example, the address range is set between OSPF areas.

Configuring OSPF Interface Parameters

You can alter some interface-specific OSPF parameters as necessary. You are not required to alter any of these parameters, but the following interface parameters must be consistent across all routers in an attached network: ospf hello-interval, ospf dead-interval, and ospf authentication-key. Be sure that if you configure any of these parameters, the configurations for all routers on your network have compatible values.
To configure OSPF interface parameters, perform the following steps:

Detailed Steps

 
Command
Purpose
Step 1 

router ospf process_id


Example:

hostname(config)# router ospf 2
This creates an OSPF routing process, and the user enters router configuration mode for tfor the OSPF process you want to redistribute.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 

network ip_address mask area area_id


Example:

hostname(config)# router ospf 2

hostname(config-router)# network 10.0.0.0 
255.0.0.0 area 0
This step defines the IP addresses on which OSPF runs and to define the area ID for that interface.
Step 3 

hostname(config)# interface interface_name


Example:

hostname(config)# interface my_interface

This allows you to enter interface configuration mode.
Step 4 
Do one of the following to configure optional OSPF interface parameters:
 
ospf authentication [message-digest |null]

Example:

hostname(config-interface)# ospf 

authentication message-digest

This specifies the authentication type for an interface.
 
ospf authentication-key key




Example:

hostname(config-interface)# ospf 

authentication-key cisco
This allows you to assign a password to be used by neighboring OSPF routers on a network segment that is using the OSPF simple password authentication.
The key can be any continuous string of characters up to 8 bytes in length.
The password created by this command is used as a key that is inserted directly into the OSPF header when the ASA software originates routing protocol packets. A separate password can be assigned to each network on a per-interface basis. All neighboring routers on the same network must have the same password to be able to exchange OSPF information.
 
ospf cost cost



Example:

hostname(config-interface)# ospf cost 20
This allows you to explicitly specify the cost of sending a packet on an OSPF interface. The cost is an integer from 1 to 65535.
In this example, the cost is set to 20.
 
ospf dead-interval seconds

Example:

hostname(config-interface)# ospf dead-interval 40
This allows you to set the number of seconds that a device must wait before it declares a neighbor OSPF router down because it has not received a hello packet. The value must be the same for all nodes on the network.
In this example, the dead-interval is set to 40.
 
ospf hello-interval seconds

Example:

hostname(config-interface)# ospf hello-interval 10
This allows you to specify the length of time between the hello packets that the ASA sends on an OSPF interface. The value must be the same for all nodes on the network.
In this example, the hello-interval is set to 10.
 
ospf message-digest-key key_id md5key

Example:

hostname(config-interface)# ospf 
message-digest-key 1 md5 cisco
This enables OSPF MD5 authentication.
The following values can be set:
•key_id—An identifier in the range from 1 to 255.
•key—Alphanumeric password of up to 16 bytes.
Usually, one key per interface is used to generate authentication information when sending packets and to authenticate incoming packets. The same key identifier on the neighbor router must have the same key value.
We recommend that you not keep more than one key per interface. Every time you add a new key, you should remove the old key to prevent the local system from continuing to communicate with a hostile system that knows the old key. Removing the old key also reduces overhead during rollover.
 
ospf priority number_value

Example:

hostname(config-interface)# ospf priority 
20
This allows you to set the priority to help determine the OSPF designated router for a network.
The number_value is between 0 to 255.
In this example, the priority number value is set to 20.
 
ospf retransmit-interval seconds







Example:

hostname(config-interface)# ospf 
retransmit-interval seconds
This allows you to specify the number of seconds between LSA retransmissions for adjacencies belonging to an OSPF interface.
The value for seconds must be greater than the expected round-trip delay between any two routers on the attached network. The range is from 1 to 65535 seconds. The default value is 5 seconds.
In this example, the retransmit-interval value is set to 15.
 

ospf transmit-delay seconds




Example:

hostname(config-interface)# ospf 
transmit-delay 5
Sets the estimated number of seconds required to send a link-state update packet on an OSPF interface. The secondsvalue is from 1 to 65535 seconds. The default value is 1 second.
In this example, the transmit-delay is 5 seconds.
 
ospf network point-to-point non-broadcast

Example:

hostname(config-interface)# ospf network 
point-to-point non-broadcast
Specifies the interface as a point-to-point, non-broadcast network.
When you designate an interface as point-to-point, non-broadcast, you must manually define the OSPF neighbor; dynamic neighbor discover is not possible. See Defining Static OSPF Neighbors, for more information. Additionally, you can only define one OSPF neighbor on that interface.

Configuring OSPF Area Parameters

You can configure several area parameters. These area parameters (shown in the following task table) include setting authentication, defining stub areas, and assigning specific costs to the default summary route. Authentication provides password-based protection against unauthorized access to an area.
Stub areas are areas into which information on external routes is not sent. Instead, there is a default external route generated by the ABR, into the stub area for destinations outside the autonomous system. To take advantage of the OSPF stub area support, default routing must be used in the stub area. To further reduce the number of LSAs sent into a stub area, you can configure the no-summary keyword of the area stub command on the ABR to prevent it from sending summary link advertisement (LSA Type 3) into the stub area.
To specify area parameters for your network, perform the following steps:

Detailed Steps

 
Command
Purpose
Step 1 

router ospf process_id


Example:

hostname(config)# router ospf 2
This creates an OSPF routing process, and the user enters router configuration mode for tfor the OSPF process you want to redistribute.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 
Do one of the following to configure optional OSPF area parameters:
 

area area-id authentication


Example:

hostname(config-router)# area 0 

authentication

This step enables authentication for an OSPF area.
 
area area-id authentication message-digest

Example:

hostname(config-router)# area 0 

authentication message-digest

This step enables MD5 authentication for an OSPF area.
 
area area-id stub [no-summary]

Example:

hostname(config-router)# area 17 stub

This defines an area to be a stub area.
 
area area-id default-cost cost

Example:

hostname(config-router)# area 17 
default-cost 20
This step assigns a specific cost to the default summary route used for the stub area.
The cost is an integer from 1 to 65535. The default value is 1.

Configuring OSPF NSSA

The OSPF implementation of an NSSA is similar to an OSPF stub area. NSSA does not flood type 5 external LSAs from the core into the area, but it can import autonomous system external routes in a limited way within the area.
NSSA importsType 7 autonomous system external routes within an NSSA area by redistribution. These Type 7 LSAs are translated into Type 5 LSAs by NSSA ABRs, which are flooded throughout the whole routing domain. Summarization and filtering are supported during the translation.
You can simplify administration if you are an ISP or a network administrator that must connect a central site using OSPF to a remote site that is using a different routing protocol using NSSA.
Before the implementation of NSSA, the connection between the corporate site border router and the remote router could not be run as an OSPF stub area because routes for the remote site could not be redistributed into the stub area, and two routing protocols needed to be maintained. A simple protocol such as RIP was usually run and handled the redistribution. With NSSA, you can extend OSPF to cover the remote connection by defining the area between the corporate router and the remote router as an NSSA.
Before you use this feature, consider these guidelines:
–You can set a Type 7 default route that can be used to reach external destinations. When configured, the router generates a Type 7 default into the NSSA or the NSSA area boundary router.
–Every router within the same area must agree that the area is NSSA; otherwise, the routers will not be able to communicate.
To specify area parameters for your network as needed to configure OSPF NSSA, perform the following steps:

Detailed Steps

 
Command
Purpose
Step 1 

router ospf process_id


Example:

hostname(config)# router ospf 2
This creates an OSPF routing process, and the user enters router configuration mode for tfor the OSPF process you want to redistribute.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 
Do one of the following to configure optional OSPF NSSA parameters:
 

area area-id nssa [no-redistribution] 

[default-information-originate]


Example:

hostname(config-router)# area 0 nssa
 
This step defines an NSSA area.
 

summary-address ip_address mask 
[not-advertise] [tag tag]


Example:

hostname(config)# router ospf 1

hostname(config-router)# summary-address 
10.1.0.0 255.255.0.0
This step sets the summary address and helps reduce the size of the routing table. Using this command for OSPF causes an OSPF ASBR to advertise one external route as an aggregate for all redistributed routes that are covered by the address.
In this example, the summary address 10.1.0.0 includes address 10.1.1.0, 10.1.2.0, 10.1.3.0, and so on. Only the address 10.1.0.0 is advertised in an external link-state advertisement


Defining Static OSPF Neighbors

You need to define static OSPF neighbors to advertise OSPF routes over a point-to-point, non-broadcast network. This lets you broadcast OSPF advertisements across an existing VPN connection without having to encapsulate the advertisements in a GRE tunnel.
Before you begin, you must create a static route to the OSPF neighbor. See the chapter, `Configuring Static and Default Routes' for more information about creating static routes.
To define a static OSPF neighbor, perform the following tasks:

Detailed Steps

 
Command
Purpose
Step 1 

router ospf process_id


Example:

hostname(config)# router ospf 2
This creates an OSPF routing process, and the user enters router configuration mode for this OSPF process.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 

neighbor addr [interface if_name]


Example:

hostname(config-router)# neighbor 
255.255.0.0 [interface my_interface]
This step defines the OSPF neighborhood.
The addr argument is the IP address of the OSPF neighbor. The if_name is the interface used to communicate with the neighbor. If the OSPF neighbor is not on the same network as any of the directly-connected interfaces, you must specify theinterface.


Monday, 9 March 2015

Basic OSPF configuration

Configuring OSPF

This section explains how to enable and restart the OSPF process on your system. After enabling see the section, to learn how to customize the OSPF process on your system.

Enabling OSPF

To enable OSPF, you need to create an OSPF routing process, specify the range of IP addresses associated with the routing process, then assign area IDs associated with that range of IP addresses.
To enable OSPF, perform the following detailed steps:

Detailed Steps

 
Command
Purpose
Step 1 

router ospf process_id

Example:

hostname(config)# router ospf 2
This creates an OSPF routing process, and the user enters router configuration mode for this OSPF process.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 

network ip_address mask area area_id


Example:

hostname(config)# router ospf 2

hostname(config-router)# network 10.0.0.0 
255.0.0.0 area 0
This step defines the IP addresses on which OSPF runs and to define the area ID for that interface.

Restarting the OSPF Process

This step allows you to remove the entire OSPF configuration you have enabled. Once this is cleared, you must reconfigure OSPF again using the router ospf command, perform the following step:
Command
Purpose

clear ospf pid {process | redistribution | 
counters [neighbor [neighbor-interface] 

[neighbor-id]]} 


Example:

hostname(config)# clear ospf 
This remove entire OSPF configuration you have enabled. Once this is cleared, you must reconfigure OSPF again using the router ospf command.

Customizing OSPF

This section explains how to customize the OSPF process and includes the following topics:
•Redistributing Routes Into OSPF
•Generating a Default Route
•Configuring OSPF Interface Parameters
•Configuring Route Summarization Between OSPF Areas
•Configuring OSPF Interface Parameters
•Configuring OSPF Area Parameters
•Configuring OSPF NSSA
•Configuring Route Calculation Timers
•Defining Static OSPF Neighbors
•Logging Neighbors Going Up or Down

Redistributing Routes Into OSPF

The ASA can control the redistribution of routes between OSPF routing processes. The ASA matches and changes routes according to settings in the redistribute command or by using a route map.
If you want to redistribute a route by defining which of the routes from the specified routing protocol are allowed to be redistributed into the target routing process, you must firstgenerate a default map and then define a route map.

To redistribute static, connected, RIP, or OSPF routes into an OSPF process, perform the following steps:

Detailed Steps


 
Command
Purpose
Step 1 

router ospf process_id


Example:

hostname(config)# router ospf 2
This creates an OSPF routing process, and the user enters router configuration mode for tfor the OSPF process you want to redistribute.
The process_id is an internally used identifier for this routing process. It can be any positive integer. This ID does not have to match the ID on any other device; it is for internal use only. You can use a maximum of two processes.
Step 2 
Do one of the following to redistribute the selected route type into the OSPF routing process:
 

redistribute connected 
[metric metric-value] 
metric-type {type-1 | type-2}] 
tag tag_value] [subnets] [route-map 

map_name]


Example:

hostname(config)# redistribute connected
This step redistributes connected routes into the OSPF routing process
 

redistribute static [metric metric-value] 

[metric-type {type-1 | type-2}] 

[tag tag_value] [subnets] [route-map 

map_name


Example:

hostname(config)# redistribute static

This step redistribute static routes into the OSPF routing process.
 

redistribute ospf pid [match {internal | 
external [1 | 2] | nssa-external [1 | 2]}] 

[metric metric-value] 

[metric-type {type-1 | type-2}] 

[tag tag_value] [subnets] [route-map 

map_name]






Example:

hostname(config)# route-map 1-to-2 permit

hostname(config-route-map)# match metric 1

hostname(config-route-map)# set metric 5

hostname(config-route-map)# set 

metric-type type-1

hostname(config-route-map)# router ospf 2

hostname(config-router)# redistribute ospf 
1 route-map 1-to-2
This step allows you to redistribute routes from an OSPF routing process into another OSPF routing process.
You can either use the match options in this command to match and set route properties, or you can use a route map. The subnet option does not have equivalents in the route-map command. If you use both a route map and match options in theredistribute command, then they must match.
This example shows route redistribution from OSPF process 1 into OSPF process 2 by matching routes with a metric equal to 1. The ASA redistributes these routes as external LSAs with a metric of 5, metric type of Type 1.
 

redistribute rip [metric metric-value] 
[metric-type {type-1 | type-2}] 

[tag tag_value] [subnets] [route-map 

map_name]


Example:


hostname(config)# redistribute rip 25
This step allows you to redistribute routes from a RIP routing process into the OSPF routing process.
 

redistribute eigrp as-num 
[metric metric-value] 

[metric-type {type-1 | type-2}] 

[tag tag_value] [subnets] [route-map 

map_name]


Example:

hostname(config)# redistribute eigrp 2
This step allows you to redistribute routes from an EIGRP routing process into the OSPF routing process.

Friday, 6 March 2015

OSPF (Cont.)

SPF algorithm: - The Shortest Path First (SPF) routing algorithm is the basis for OSPF operations. When an SPF router is powered up, it initializes its routing-protocol data structures and then waits for indications from lower-layer protocols that its interfaces are functional.
After a router is assured that its interfaces are functioning, it uses the OSPF Hello protocol to acquire neighbors, which are routers with interfaces to a common network. The router sends hello packets to its neighbors and receives their hello packets. In addition to helping acquire neighbors, hello packets also act as keepalives to let routers know that other routers are still functional.
On multiaccess networks (networks supporting more than two routers), the Hello protocol elects a designated router and a backup designated router. Among other things, the designated router is responsible for generating LSAs for the entire multiaccess network. Designated routers allow a reduction in network traffic and in the size of the topological database.
When the link-state databases of two neighboring routers are synchronized, the routers are said to be adjacent. On multiaccess networks, the designated router determines which routers should become adjacent. Topological databases are synchronized between pairs of adjacent routers. Adjacencies control the distribution of routing-protocol packets, which are sent and received only on adjacencies.
Each router periodically sends an LSA to provide information on a router's adjacencies or to inform others when a router's state changes. By comparing established adjacencies to link states, failed routers can be detected quickly, and the network's topology can be altered appropriately. From the topological database generated from LSAs, each router calculates a shortest-path tree, with itself as root. The shortest-path tree, in turn, yields a routing table.
Packet Format:- All OSPF packets begin with a 24-byte header, as illustrated in Figure: OSPF Packets Consist of Nine Fields.
Figure: OSPF Packets Consist of Nine Fields
CT844602.jpg
The following descriptions summarize the header fields:
  • Version number - Identifies the OSPF version used.
  • Type - Identifies the OSPF packet type as one of the following:
    • Hello - Establishes and maintains neighbor relationships.
    • Database description - Describes the contents of the topological database. These messages are exchanged when an adjacency is initialized.
    • Link-state request - Requests pieces of the topological database from neighbor routers. These messages are exchanged after a router discovers (by examining database-description packets) that parts of its topological database are outdated.
    • Link-state update - Responds to a link-state request packet. These messages also are used for the regular dispersal of LSAs. Several LSAs can be included within a single link-state update packet.
    • Link-state acknowledgment - Acknowledges link-state update packets.
  • Packet length - Specifies the packet length, including the OSPF header, in bytes.
  • Router ID - Identifies the source of the packet.
  • Area ID - Identifies the area to which the packet belongs. All OSPF packets are associated with a single area.
  • Checksum - Checks the entire packet contents for any damage suffered in transit.
  • Authentication type - Contains the authentication type. All OSPF protocol exchanges are authenticated. The authentication type is configurable on per-area basis.
  • Authentication - Contains authentication information.
  • Data - Contains encapsulated upper-layer information


Additional Features: - Additional OSPF features include equal-cost, multipath routing, and routing based on upper-layer type-of-service (TOS) requests. TOS-based routing supports those upper-layer protocols that can specify particular types of service. An application, for example, might specify that certain data is urgent. If OSPF has high-priority links at its disposal, these can be used to transport the urgent datagram.

OSPF supports one or more metrics. If only one metric is used, it is considered to be arbitrary, and TOS is not supported. If more than one metric is used, TOS is optionally supported through the use of a separate metric (and, therefore, a separate routing table) for each of the eight combinations created by the three IP TOS bits (the delay, throughput, and reliability bits). For example, if the IP TOS bits specify low delay, low throughput, and high reliability, OSPF calculates routes to all destinations based on this TOS designation.
IP subnet masks are included with each advertised destination, enabling variable-length subnet masks. With variable-length subnet masks, an IP network can be broken into many subnets of various sizes. This provides network administrators with extra network-configuration flexibility.

Wednesday, 4 March 2015

Open Shortest Path First (OSPF)

Open Shortest Path First (OSPF) is a routing protocol developed for Internet Protocol (IP) networks by the Interior Gateway Protocol (IGP) working group of the Internet Engineering Task Force (IETF). The working group was formed in 1988 to design an IGP based on the Shortest Path First (SPF) algorithm for use in the Internet. Similar to the Interior Gateway Routing Protocol (IGRP), OSPF was created because in the mid-1980s, the Routing Information Protocol (RIP) was increasingly incapable of serving large, heterogeneous internetworks. This chapter examines the OSPF routing environment, underlying routing algorithm, and general protocol components.

Background: - OSPF was derived from several research efforts, including Bolt, Beranek, and Newman's (BBN's) SPF algorithm developed in 1978 for the ARPANET (a landmark packet-switching network developed in the early 1970s by BBN), Dr. Radia Perlman's research on fault-tolerant broadcasting of routing information (1988), BBN's work on area routing (1986), and an early version of OSI's Intermediate System-to-Intermediate System (IS-IS) routing protocol.
OSPF has two primary characteristics. The first is that the protocol is open, which means that its specification is in the public domain. The OSPF specification is published as Request For Comments (RFC) 1247. The second principal characteristic is that OSPF is based on the SPF algorithm, which sometimes is referred to as the Dijkstra algorithm, named for the person credited with its creation.
OSPF is a link-state routing protocol that calls for the sending of link-state advertisements (LSAs) to all other routers within the same hierarchical area. Information on attached interfaces, metrics used, and other variables is included in OSPF LSAs. As OSPF routers accumulate link-state information, they use the SPF algorithm to calculate the shortest path to each node.
As a link-state routing protocol, OSPF contrasts with RIP and IGRP, which are distance-vector routing protocols. Routers running the distance-vector algorithm send all or a portion of their routing tables in routing-update messages to their neighbors.
Routing Process: - Unlike RIP, OSPF can operate within a hierarchy. The largest entity within the hierarchy is the autonomous system (AS), which is a collection of networks under a common administration that share a common routing strategy. OSPF is an intra-AS (interior gateway) routing protocol, although it is capable of receiving routes from and sending routes to other ASs.
An AS can be divided into a number of areas, which are groups of contiguous networks and attached hosts. Routers with multiple interfaces can participate in multiple areas. These routers, which are called Area Border Routers, maintain separate topological databases for each area.
A topological database is essentially an overall picture of networks in relationship to routers. The topological database contains the collection of LSAs received from all routers in the same area. Because routers within the same area share the same information, they have identical topological databases.
The term domain sometimes is used to describe a portion of the network in which all routers have identical topological databases. Domain is frequently used interchangeably with AS.
An area's topology is invisible to entities outside the area. By keeping area topologies separate, OSPF passes less routing traffic than it would if the AS were not partitioned.
Area partitioning creates two different types of OSPF routing, depending on whether the source and the destination are in the same or different areas. Intra-area routing occurs when the source and destination are in the same area; interarea routing occurs when they are in different areas.
An OSPF backbone is responsible for distributing routing information between areas. It consists of all Area Border Routers, networks not wholly contained in any area, and their attached routers.
In the figure, routers 4, 5, 6, 10, 11, and 12 make up the backbone. If Host H1 in Area 3 wants to send a packet to Host H2 in Area 2, the packet is sent to Router 13, which forwards the packet to Router 12, which sends the packet to Router 11. Router 11 then forwards the packet along the backbone to Area Border Router 10, which sends the packet through two intra-area routers (Router 9 and Router 7) to be forwarded to Host H2.
The backbone itself is an OSPF area, so all backbone routers use the same procedures and algorithms to maintain routing information within the backbone that any area router would. The backbone topology is invisible to all intra-area routers, as are individual area topologies to the backbone.
Areas can be defined in such a way that the backbone is not contiguous. In this case, backbone connectivity must be restored through virtual links. Virtual links are configured between any backbone routers that share a link to a nonbackbone area and function as if they were direct links.
Figure: An OSPF AS Consists of Multiple Areas Linked by Routers shows an example of an internetwork with several areas.
Figure: An OSPF AS Consists of Multiple Areas Linked by Routers
CT844601.jpg
AS border routers running OSPF learn about exterior routes through exterior gateway protocols (EGPs), such as Exterior Gateway Protocol (EGP) or Border Gateway Protocol (BGP), or through configuration information. For more information about these protocols.