www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / ROUTE / Module 3 / OSPF – OSPF Overview and Fundamentals

OSPF – OSPF Overview and Fundamentals

Several RFCs have been written for OSPF. In this section, we are going to learn about the history of OSPF based on some of the most common RFCs that pertain to OSPF. The OSPF working group was formed in 1987 and has released numerous Requests for Comments (RFCs). Some of the most common RFCs on OSPF are listed below and include:

  • RFC 1131 – OSPF Specification
  • RFC 1584 – Multicast Extensions to OSPF
  • RFC 1587 – The OSPF NSSA Option
  • RFC 1850 – OSPF Version 2 Management Information Base
  • RFC 2328 – OSPF Version 2
  • RFC 2740 – OSPF Version 3

RFC 1131 describes the first iteration of OSPF and was used in initial tests to determine whether the protocol worked. RFC 1584 provides extensions to OSPF for the support of IP Multicast traffic. This is commonly referred to as Multicast OSPF (MOSPF). However, this standard is seldom used and most importantly, it is not supported by Cisco.

RFC 1587 describes the operation of an OSPF Not-So-Stubby Area (NSSA). An NSSA allows for the injection of external routing knowledge by an ASBR using an NSSA External LSA. NSSAs are described in detail later in this chapter.

RFC 1850 allows network management of OSPF using the Simple Network Management Protocol (SNMP). SNMP is used in network management systems to monitor network-attached devices for conditions that warrant administrative attention. The implementation of this standard is beyond the scope of the ROUTE exam and is not described in this guide. RFC 2328 details the latest update to OSPF version 2 (OSPFv2), which is the default version of OSPF in use today. OSPFv2 was initially described in RFC 1247, which addressed a number of issues discovered during the initial rollout of OSPF version 1 and modified the protocol to allow for future modifications without generating backward-compatibility issues. Because of this, OSPFv2 is not compatible with OSPFv1.

And finally, RFC 2740 describes the modifications to OSPF to support version 6 of the Internet Protocol (IPv6). IP version 6 is described in detail later in this guide. It should be assumed that all references to OSPF in this chapter are for OSPF version 2.

Link State Fundamentals

When a Link State routing protocol is enabled for a particular link, information associated with that network is added to the local Link State Database (LSDB).  The local router then sends Hello messages on its operational links to determine whether other Link State routers are operating on the interfaces as well. The Hello messages are used for neighbor discovery as well as to maintain adjacencies between neighbor routers. These messages are described in detail later in this chapter.

When a neighbor router is located, the local router attempts to establish an adjacency, assuming both routers share the same common subnet, are in the same area, and other parameters, such as authentication, and timers, for example, are identical. This adjacency enables the two routers to advertise summary LSDB information to each other. This exchange is not the actual detailed database information, but an actual summary of the data.

Each individual router evaluates the summary information against its local LSDB to ensure that it has the most up-to-date information. If one side of the adjacency realizes that it requires an update, the router requests the new information from the adjacent router. The update from the neighbor includes the actual data contained in the LSDB. This exchange process continues until both routers have identical LSDBs. OSPF uses different types of messages to exchange the database information and ensure that all routers have a consistent view of the network. These different packet types are described in detail later in this chapter.

Following the database exchange, the SPF algorithm runs and creates a shortest-path tree to all hosts in an area or in the network backbone, with the router that is performing the calculation at the root of that tree. The SPF algorithm is described in detail in Chapter 1.

OSPF Fundamentals

Unlike EIGRP, which can support multiple Network Layer protocols, OSPF can only support the Internet Protocol (IP) and supports both versions 4 and 6 of the IP protocol. Like EIGRP, OSPF supports VLSM, authentication and utilizes IP Multicast when sending and receiving updates on multi-access networks, such as Ethernet.

OSPF is a hierarchical routing protocol that logically divides the network into sub-domains referred to as areas. This logical segmentation is used to limit the scope of Link State Advertisement (LSA) flooding throughout the OSPF domain. Link State Advertisements are special types of packets sent by routers running OSPF. Different types of Link State Advertisements are used within an area and between areas. By restricting the propagation of certain types of LSAs between areas, the OSPF hierarchical implementation effectively reduces the amount of routing protocol traffic within the OSPF network.

NOTE:  OSPF LSAs will be described in detail later in this chapter.
In a multi-area OSPF network, one area must be designated as the backbone area or area 0. The OSPF backbone is the logical center of the OSPF network. All other non-backbone areas must be physically connected to the backbone. However, because it is not always possible or feasible to have a physical connection between a non-backbone area and the backbone, the OSPF standard allows the use of virtual connections to the backbone. These virtual connections are described in detail later in this chapter.

Routers within each area store detailed topology information for the area in which they reside. Within each area one (or more) routers referred to Area Border Routers (ABRs) facilitate inter-area routing by advertising summarized routing information between the different areas. This functionality allows for the following within the OSPF network:

  • Reduces the scope of LSA flooding throughout the OSPF domain
  • Hides detailed topology information between areas
  • Allows for end-to-end connectivity within the OSPF domain
  • Creates logical boundaries within the OSPF domain

The OSPF backbone area receives summarized routing information from the ABRs.  The routing information is disseminated to all other non-backbone areas within the OSPF network. When a change to the network topology occurs, this information is disseminated throughout the entire OSPF domain, allowing all routers in all areas to have a consistent view of the network. The network topology illustrated in Figure 3-1 is an example of a multi-area OSPF implementation:

 

3-1

Fig. 3-1. A Multi-Area OSPF Network

Figure 3-1 illustrates a basic multi-area OSPF network. Areas 1 and 2 are connected to area 0, the OSPF backbone. Within area 1, routers R1, R2, and R3 exchange intra-area routing information and maintain detailed topology area for that area. R3, the Area Border Router, generates an inter-area summary route and advertises this to the OSPF backbone.

R4, the Area Border Router for area 2, receives the summary information from area 0 and floods it into its adjacent area. This allows routers R5 and R6 to know of the routes that reside outside of their local area, but within the OSPF domain. The same concept would also be applicable the routing information within area 2.

In summation, the ABRs maintain Link State Database information for all the areas that they are connected to. All routers within each area have detailed topology information pertaining to that specific area. These routers exchange intra-area routing information. The ABRs advertise summary information from each of their connected areas to other OSPF areas allowing for inter-area routing within the domain.

NOTE: OSPF ABRs and other OSPF router types are described in detail later in this chapter.

Network Types

OSPF uses different default network types for different media. These network types are:

  • Non-Broadcast
  • Point-to-Point
  • Broadcast
  • Point-to Multipoint

Non-Broadcast networks are network types that do not support natively Broadcast or Multicast traffic. The most common example of a non-Broadcast network type is Frame Relay. Non-Broadcast network types require additional configuration to allow for both Broadcast and Multicast support. On such networks, OSPF elects a Designated Router (DR) and/or a Backup Designated Router (DR). These two routers are described later in this chapter.

In Cisco IOS software, OSPF-enabled routers send Hello packets every 30 seconds on Non-Broadcast network types. If a Hello packet is not received in four times the Hello interval, or 120 seconds, the neighbor router is considered ‘dead’. The following shows the output of the show ip ospf interface command on a Frame Relay Serial interface:

R2#show ip ospf interface serial 0/0
Serial0/0 is up, line protocol is up
Internet Address 150.1.1.2/24, Area 0
Process ID 2, Router ID 2.2.2.2, Network Type NON_BROADCAST, Cost: 64
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 2.2.2.2, Interface address 150.1.1.2
  Backup Designated router (ID) 1.1.1.1, Interface address 150.1.1.1
  Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
oob-resync timeout 120
Hello due in 00:00:00
Supports Link-local Signaling (LLS)
Index 2/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 2, maximum is 2
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 1.1.1.1  (Backup Designated Router)
Suppress hello for 0 neighbor(s)

A point-to-point connection is simply a connection between only two endpoints. Examples of point-to-point connections include physical WAN interfaces using HDLC and PPP encapsulation, and Frame Relay and ATM point-to-point subinterfaces. No Designated Router (DR) or Backup Designated Router (BDR) is elected on OSPF point-to-point network types. By default, OSPF sends Hello packets out every 10 seconds on point-to-point network types. The ‘dead’ interval on these network types is four times the Hello interval, which is 40 seconds. The following shows the output of the show ip ospf interface command on a P2P link:

R2#show ip ospf interface serial 0/0
Serial0/0 is up, line protocol is up
Internet Address 150.1.1.2/24, Area 0
Process ID 2, Router ID 2.2.2.2, Network Type POINT_TO_POINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:03
Supports Link-local Signaling (LLS)
Index 2/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 1.1.1.1
Suppress hello for 0 neighbor(s)

Broadcast network types are those that natively support Broadcast and Multicast traffic; the most common example being Ethernet. As is the case with non-Broadcast networks, OSPF also elects a Designated Router (DR) and/or a Backup Designated Router (DR) on Broadcast networks. By default, OSPF sends Hello packets every 10 seconds on these network types and a neighbor is declared ‘dead’ if no Hello packets are received within four times the Hello interval, which is 40 seconds. The following shows the output of the show ip ospf interfacecommand on a FastEthernet interface:

R2#show ip ospf interface fastethernet 0/0
FastEthernet0/0 is up, line protocol is up
Internet Address 192.168.1.2/24, Area 0
Process ID 2, Router ID 2.2.2.2, Network Type BROADCAST, Cost: 64
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 192.168.1.3, Interface address 192.168.1.3
  Backup Designated router (ID) 2.2.2.2, Interface address 192.168.1.2
Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:04
Supports Link-local Signaling (LLS)
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 192.168.1.3  (Designated Router)
Suppress hello for 0 neighbor(s)

The point-to-multipoint network type is a non-default OSPF network type. In other words, this network type must be manually configured using the ip ospf network point-to-multipoint [non-broadcast] interface configuration command.  By default, the command defaults to a Broadcast point-to-multipoint network type. This default network type allows OSPF to use Multicast packets to dynamically discover neighbor routers. In addition to this, there is no DR/BDR election held on Broadcast point-to-multipoint network types.

The [non-broadcast] keyword configures the point-to-multipoint network type as a non-Broadcast point-to-multipoint network. This requires static OSPF neighbor configuration as OSPF will not use Multicast to dynamically discover neighbor routers. Additionally, this network type does not require the election of a DR and/or BDR router for the designated segment. The primary use of this network type is to allow neighbor costs to be assigned to neighbors instead of using the interface assigned cost for routes received from all neighbors. This concept will be described in detail later in this chapter.

The point-to-multipoint network type is typically used in partial-mesh hub-and-spoke NBMA networks. However, it should also be noted that this network type can also be specified for other network types, such as Broadcast Multi-Access networks, such as Ethernet. By default, OSPF sends Hello packets every 30 seconds on point-to-multipoint networks. The default dead interval is four times the Hello interval, or 120 seconds.

The following shows the output of the show ip ospf interface command on a Frame Relay Serial interface that has been manually configured as a point-to-multipoint network:

R2#show ip ospf interface serial 0/0
Serial0/0 is up, line protocol is up
Internet Address 150.1.1.2/24, Area 0
Process ID 2, Router ID 2.2.2.2, Network Type POINT_TO_MULTIPOINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5
oob-resync timeout 120
Hello due in 00:00:04
Supports Link-local Signaling (LLS)
Index 2/2, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 2
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 1.1.1.1
Suppress hello for 0 neighbor(s)

The primary reason that OSPF requires that the network type be the same on both routers is because of the timer values. As illustrated in the examples above, different network types use different Hello and Dead timer intervals. In order for an OSPF adjacency to be successfully established, these values must match on both routers.

Cisco IOS software allows the default OSPF Hello and Dead timers to be changed using the ip ospf hello-interval <1-65535> and the ip ospf dead-interval [<1-65535>|minimal] interface configuration commands. The ip ospf hello-interval <1-65535> command is used to specify the Hello interval in seconds. When issued, the software automatically configures the Dead interval to a value four times the configured Hello interval. For example, assume that a router was configured as follows:

R2(config)#interface serial 0/0
R2(config-if)#ip ospf hello-interval 1
R2(config-if)#exit

By setting the Hello interval to 1 on R2 above, Cisco IOS software automatically adjusts the default Dead timer to four times the Hello interval, which is 4 seconds:

R2#show ip ospf interface serial 0/0
Serial0/0 is up, line protocol is up
Internet Address 10.0.2.4/24, Area 2
Process ID 4, Router ID 4.4.4.4, Network Type POINT_TO_POINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 1, Dead 4, Wait 4, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:00[Truncated Output]

While setting the Hello interval results in an automatic adjustment of the Dead timer, setting the Dead timer does not result in an automatic adjustment of the Hello interval. As an example, consider the following Dead timer configuration on the router:

R2(config)#interface serial 0/0
R2(config-if)#ip ospf dead-interval 60
R2(config-if)#exit

Despite this configuration, the Hello interval remains the same at 10 seconds (this is a P2P link) and is not affected by this configuration. This is illustrated in the following output:

R4#show ip ospf interface serial 0/0
Serial0/0 is up, line protocol is up
Internet Address 10.0.2.4/24, Area 2
Process ID 4, Router ID 4.4.4.4, Network Type POINT_TO_POINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 10, Dead 60, Wait 60, Retransmit 5
oob-resync timeout 60
Hello due in 00:00:09[Truncated Output]

NOTE: If the Dead interval is changed on one side of the link, or one of the routers on a multi-access segment, the same value should be configured on all routers. Otherwise, OSPF adjacencies will not be established by the routers.

Going back to the OSPF network types, it should be noted that different network types can be configured on either side of the link as long as the timer values are the same. However, when doing so, ensure that you configure like network types.

For example, you could adjust the OSPF timers to ensure that two routers, one configured with a Broadcast network type and the other a Non-Broadcast network type (because they both use DR and BDR routers) and successfully establish an adjacency. The same could be applied to two routers, one using a point-to-point network type and the other configured with the point-to-multipoint network type, because neither elects a DR or BDR. The timers need only be changed on one of the routers.

For example, to establish an OSPF adjacency between point-to-point and point-to-multipoint network types, change the point-to-point Hello and Dead timer values to match those of the point-to-multipoint network type, or change those of the point-to-multipoint network type to match those of the point-to-point network type. Once the timers match, and assuming all other configuration is correct, the routers will establish an adjacency.

NOTE: While it is technically possible to establish an adjacency between non-like network types with the same timer values, e.g. between a Broadcast and a point-to-multipoint network type, for reasons beyond the scope of the ROUTE exam, this is not recommended and could result in unexpected behavior within the OSPF network.

In addition to adjusting timer values to allow adjacencies to be established on different network types, OSPF timers can also be adjusted to reduce protocol convergence time. However, be cautious when setting aggressive timers as this may cause more problems than are addressed.

Designated and Backup Designated Routers

As stated in the previous section, OSPF elects a Designated Router and/or Backup Designated Router on Broadcast and Non-Broadcast network types. It is important to understand that the BDR is not a mandatory component on these network types. In fact, OSPF will work just as well if only a DR is elected and there is no BDR; however, there will be no redundancy if the DR fails and the OSPF routers will need to go through the election process again to elect a new DR.

On the segment, each individual non DR/BDR router establishes an adjacency with the DR and, if one has also been elected, the BDR; but not with any other non-DR/BDR routers on the segment. The DR and BDR routers are fully adjacent with each other and all other routers on the segment. The non-DR/BDR routers send messages and updates to the AllDRRouters Multicast group address 224.0.0.6. Only the DR/BDR routers listen to Multicast messages sent to this group address. The DR then advertises messages to the AllSPFRouters Multicast group address 224.0.0.5. This allows all other OSPF routers on the segment to receive the updates.

It is important to understand the sequence of message exchanges when a DR and/or BDR router has been elected. As an example, imagine a Broadcast network with four routers, which are R1, R2, R3, and R4. Let us assume that R4 has been elected DR, and R3 has been elected BDR. R2 and R1 are neither DR nor BDR and are therefore referred to as DROther routers in Cisco OSPF terminology. A configuration change is made on R1. R1 sends an update to the AllDRRouters Multicast group address 224.0.0.6. R4, the DR, receives this update and sends an acknowledgement back to the AllSPFRouters Multicast group address 224.0.0.5. R4 then turns around and sends this update to all other non-DR/BDR routers using the AllSPFRouters Multicast group address. This update is received by the other DROther router, R2. R2 sends an acknowledgement to the AllDRRouters Multicast group 224.0.0.6. This is shown in Figure 3-2:

3-2Fig. 3-2. OSPF DR and BDR Advertisements

NOTE: The BDR simply listens to the packets sent to both Multicast groups.

In order for a router to be the Designated Router, or Backup Designated Router, for the segment, the router must be elected. This election is based on the following:

  • The highest router priority value
  • The highest router ID

By default, all routers have a default priority value of 1. This value can be adjusted using the ip ospf priority <0-255> interface configuration command. The higher the priority, the greater the likelihood the router will be elected DR for the segment. The router with the second highest priority will then be elected BDR. If a priority value of 0 is configured, the router will not participate in the DR/BDR election process.
When determining the OSPF router ID, Cisco IOS selects the highest IP address of configured Loopback interfaces. If no Loopback interfaces are configured, the software uses the highest IP address of all configured physical interfaces as the OSPF router ID. Cisco IOS software also allows administrators to manually specify the router ID using the router-id [address] router configuration command.

It is important to remember that with OSPF, once the DR and BDR have been elected, they will remain as DR/BDR routers until a new election is held. For example, if a DR and BDR exist on a multi-access network and a router with a higher priority or IP address is added to the same segment, the existing DR and BDR routers will not change. If the DR fails, the BDR will assume the role of the DR, not the new router with the higher priority or IP address. Instead, a new election will be held and that router will most likely be elected BDR. In order for that router to become the DR, the BDR must be removed or the OSPF process reset forcing a new DR/BDR election. Once elected, OSPF uses the DR and BDR routers as follows:

  • To reduce the number of adjacencies required on the segment
  • To advertise the routers on the multi-access segment
  • To ensure that updates are sent to all routers on the segment

To better understand these fundamental concepts, let us reference the basic OSPF network topology illustrated in Figure 3-3:

3-3Fig. 3-3. OSPF DR and BDR Fundamentals

Referencing Figure 3-3, each router on the segment establishes an adjacency with the DR and BDR, but not with each other. In other words, non-DR/BDR routers do not establish an adjacency with each other. This prevents the routers on the segment from forming N(N-1) adjacencies with each other, which reduces excessive OSPF packet flooding on the segment.

For example, without the concept of a DR/BDR on the segment, each individual router would need to establish an adjacency with every other router on the segment. This would result in a total of 4(4-1) or 12 adjacencies on the segment. However, with the DR/BDR, each individual router need only establish an adjacency with these two routers and no other non-DR and BDR routers. The DR and BDR also establish an adjacency between themselves. This reduces the number of adjacencies required on the segment and on each individual OSPF router, which in turn reduces resources consumption, e.g. memory and processor utilization, on the routers.

In regards to the second point made, OSPF views a link as a connection between two routers or nodes. In multi-access networks, such as Ethernet, multiple routers can reside on the same segment, as illustrated in Figure 3-2.  On such networks, OSPF uses the Network Link State Advertisement (Type 2 LSA) to advertise the routers on the multi-access segment. This LSA is generated by the DR and is flooded only within the area. Because the other non-DR/BDR routers do not establish adjacencies with each other, this LSA allows those routers to know about the other routers on the multi-access segment.

To further clarify this point, referencing Figure 3-2, assuming that all routers on the segment have the default OSPF priority value of 1, R4 is elected as the Designated Router for the segment because it has the highest router ID. R3 is elected as Backup Designated Router for the segment because it has the second highest router ID. Because R2 and R1 are neither the DR nor the BDR, they are referred to as DROther routers in Cisco terminology. This can be validated using the show ip ospf neighbor command on all routers as follows:

R1#show ip ospf neighborNeighbor ID   Pri   State           Dead Time   Address         Interface
2.2.2.2         1   2WAY/DROTHER    00:00:38    192.168.1.2     Ethernet0/0
3.3.3.3         1   FULL/BDR        00:00:39    192.168.1.3     Ethernet0/0
4.4.4.4         1   FULL/DR         00:00:38    192.168.1.4     Ethernet0/0

 

R2#show ip ospf neighborNeighbor ID  Pri   State         Dead Time   Address     Interface
1.1.1.1        1   2WAY/DROTHER  00:00:32    192.168.1.1     FastEthernet0/0
3.3.3.3        1   FULL/BDR      00:00:33    192.168.1.3     FastEthernet0/0
4.4.4.4        1   FULL/DR       00:00:32    192.168.1.4     FastEthernet0/0

 

R3#show ip ospf neighborNeighbor ID  Pri   State         Dead Time   Address         Interface
1.1.1.1        1   FULL/DROTHER  00:00:36    192.168.1.1     FastEthernet0/0
2.2.2.2        1   FULL/DROTHER  00:00:36    192.168.1.2     FastEthernet0/0
4.4.4.4        1   FULL/DR       00:00:35    192.168.1.4     FastEthernet0/0

 

R4#show ip ospf neighborNeighbor ID  Pri   State         Dead Time   Address         Interface
1.1.1.1        1   FULL/DROTHER  00:00:39    192.168.1.1     FastEthernet0/0
2.2.2.2        1   FULL/DROTHER  00:00:39    192.168.1.2     FastEthernet0/0
3.3.3.3        1   FULL/BDR      00:00:30    192.168.1.3     FastEthernet0/0

NOTE: The DROther routers remain in the 2WAY/DROTHER state because they only exchange their databases with the DR and BDR routers. Therefore, because there is no full database exchange between the DROther routers, they will never reach the OSPF Full adjacency state.

Because R4 has been elected DR, it generates the Network LSA which advertises the other routers on the multi-access segment. This LSA advertises the routers on the multi-access segment. This can be verified using theshow ip ospf database network [link state ID] command on any router on the segment or the show ip ospf database network self-originate command on the DR only. The following shows the output of the show ip ospf database network self-originate command on the DR (R4):

R4#show ip ospf database network self-originateOSPF Router with ID (4.4.4.4) (Process ID 4)

                Net Link States (Area 0)

Routing Bit Set on this LSA
LS age: 429
Options: (No TOS-capability, DC)
LS Type: Network Links
Link State ID: 192.168.1.4 (address of Designated Router)
Advertising Router: 4.4.4.4
LS Seq Number: 80000006
Checksum: 0x7E08
Length: 40
Network Mask: /24
        Attached Router: 4.4.4.4
        Attached Router: 1.1.1.1
        Attached Router: 2.2.2.2
        Attached Router: 3.3.3.3

Referencing the output above, the DR (R4) originates the Type 2 (Network LSA) representing the 192.168.1.0/24 subnet. Because multiple routers exist on this subnet, this 192.168.1.0/24 subnet is referred to as a transit link in OSPF terminology. The advertising router field shows the router that originated this LSA. The network mask field shows the subnet mask of the transit network, which is 24-bit or 255.255.255.0.

The attached router fields list the router IDs of all routers that are on the network segment. This allows all of the routers on the segment to know what other routers also reside on the segment. The output of the show ip ospf database network [link state ID] command on R1, R2, and R3 reflects the same information as is illustrated in the output that follows:

R2#show ip ospf database networkOSPF Router with ID (2.2.2.2) (Process ID 2)

Net Link States (Area 0)

Routing Bit Set on this LSA
LS age: 923
Options: (No TOS-capability, DC)
LS Type: Network Links
Link State ID: 192.168.1.4 (address of Designated Router)
  Advertising Router: 4.4.4.4
LS Seq Number: 80000006
Checksum: 0x7E08
Length: 40
Network Mask: /24
        Attached Router: 4.4.4.4
        Attached Router: 1.1.1.1
        Attached Router: 2.2.2.2
        Attached Router: 3.3.3.3

 

R1#show ip ospf database networkOSPF Router with ID (1.1.1.1) (Process ID 1)

Net Link States (Area 0)

Routing Bit Set on this LSA
LS age: 951
Options: (No TOS-capability, DC)
LS Type: Network Links
Link State ID: 192.168.1.4 (address of Designated Router)
  Advertising Router: 4.4.4.4
LS Seq Number: 80000006
Checksum: 0x7E08
Length: 40
Network Mask: /24
        Attached Router: 4.4.4.4
        Attached Router: 1.1.1.1
        Attached Router: 2.2.2.2
        Attached Router: 3.3.3.3

 

OSPF Router with ID (4.4.4.4) (Process ID 4)

 

R3#show ip ospf database networkOSPF Router with ID (3.3.3.3) (Process ID 3)

Net Link States (Area 0)

Routing Bit Set on this LSA
LS age: 988
Options: (No TOS-capability, DC)
LS Type: Network Links
Link State ID: 192.168.1.4 (address of Designated Router)
  Advertising Router: 4.4.4.4
LS Seq Number: 80000006
Checksum: 0x7E08
Length: 40
Network Mask: /24
        Attached Router: 4.4.4.4
        Attached Router: 1.1.1.1
        Attached Router: 2.2.2.2
        Attached Router: 3.3.3.3

The functionality of the Network LSA and how it is correlated to another LSA, specifically the Router LSA (Type 1), will be described in detail later in this chapter. For this section, primary emphasis should be placed on understanding that the DR generates and advertises the Network LSA on the multi-access segment to advertise other routers that reside on the same segment. This is because routers on the segment establish an adjacency only with the DR and BDR routers and not with each other. Without an adjacency with each other, the routers would never know about other non-DR/BDR routers on the multi-access segment.

And finally, in regards to the third point made on DR/BDR routers, the DR/BDR routers ensure that all routers on the segment have complete databases. Non-DR/BDR routers send updates to the Multicast group address 224.0.0.6 (AllDRRouters). The DR then advertises these updates to other non-DR/BDR routers by sending the update to the Multicast group address 224.0.0.5 (AllSPFRouters).  Figure 3-4 illustrates an update from R1 (a DROther) to the DR group address referencing the routers illustrated in Figure 3-3:

3-4

Fig. 3-4. DROther Update To DR/BDR Group Address

R4 (DR) receives this update and in turn sends the same to Multicast group address 224.0.0.5. This group address is used by all OSPF routers. This ensures that all other routers on the segment receive this update. This update from the DR (R4) is illustrated in Figure 3-5.

3-5

Fig. 3-5. DR Update To OSPF Group Address

NOTE: We can determine this is the Update from R1 because the Advertising Router field in both Figures 3-4 and 3-5 contains the router ID (RID) of R1, which is 1.1.1.1.

NOTE: The other LSAs used by OSPF will be described in detail later in this chapter.

Additional Router Types

In addition to the Designated Router and Backup Designated routers on multi-access segments, OSPF routers are also described based on their location and function within the OSPF network. The additional router types that are commonly found within the OSPF network include:

  • Area Border Routers
  • Autonomous System Boundary Routers
  • Internal Routers
  • Backbone Routers

Figure 3-6 illustrates a basic OSPF network comprised of two areas, the OSPF backbone and an additional normal OSPF area (area 2). R2 has an external BGP neighbor relationship with R1. This diagram will be used to describe the different OSPF router types within this network.
3-6

Fig. 3-6. Additional OSPF Router Types

An Area Border Router (ABR) is an OSPF router that connects one or more OSPF areas to the OSPF backbone. This means that it must have at least one interface in area 0 and another interface, or interfaces, within a different OSPF area. ABRs are members of all areas to which they belong, and keep a separate Link State Database for every area that they belong to.  Referencing Figure 3-6, R3 would be considered an ABR as it connects Area 2 to the OSPF backbone, or area 0.

An Autonomous System Boundary Router (ASBR), in the traditional sense, is resides at the edge of the routing domain and defines the boundary between the internal and external networks. Referencing Figure 3-6, R2 would be considered an ASBR. In addition to injecting routing information from other protocols, e.g. BGP, a router can also be classified as an ASBR if it injects static routes, connected subnets, or even no external routes at all, into the OSPF domain.

Internal routers maintain all operational interfaces within a single OSPF area. Based on the network topology illustrated in Figure 3-6, R4 would be considered as an internal router because its only interface resides within a single OSPF area.

Backbone routers are routers that have an interface in the OSPF backbone. Backbone routers can include routers that only have interfaces in the OSPF backbone or routers that have an interface in the OSPF backbone, as well as interfaces in other areas (ABRs). Based on the topology illustrated in Figure 3-6, both R2 and R3 would be considered backbone routers.

NOTE: OSPF routers can have multiple roles. For example, R2 is both an ASBR and a backbone router while R3 is both a backbone router and an ABR. Throughout this chapter, we will take a detailed look at these types of router and their roles and functions within the OSPF domain.

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.