OSPF Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Release

PDF

OSPF Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Release

Enable OSPF routing

Want to summarize with AI?

Log in

Configure OSPF on Cisco 8000 Series Routers following a standard, repeatable workflow.


Enable OSPF routing by completing the essential configuration steps and preparing for result verification.

Perform this task after you have identified the OSPF process, area, relevant interfaces, and your deployment’s specific routing requirements.

Before you begin

  • Ensure at least one IP address is configured on the router (OSPF routing requires at least one active IP address).

  • Identify the OSPF process number, area IDs, and interfaces for OSPF participation.

Follow these steps to configure and verify OSPF areas and neighbours:

Procedure

1.

Configure the minimum OSPF requirements by defining an OSPF process with a router ID, assigning a backbone or non-backbone area, and enabling OSPF on the required interfaces.

Example:

Router# router ospf 1
Router (config-ospf)# router-id 192.168.4.3
Router(config-ospf)# area 0
Router(config-ospf-ar)# interface TenGigE 0/1/0/3
Router(config-ospf-ar-if)# log adjacency changes detail

Area IDs can be specified in decimal (e.g., area 1000) or dotted-decimal (e.g., area 0.0.3.232). Use a consistent format; IPv4 address notation is recommended.

2.

Verify OSPF configuration.

Example:


/* OSPF areas must be explicitly configured,
and interfaces configured under 
the area configuration mode are explicitly bound
 to that area. 
In this example, interface 10.1.2.0/24 is bound
 to area 0 and interface 10.1.3.0/24 is bound to area 1.
*/
Router# show running-config interface TenGigE 0/3/0/0
interface TenGigE 0/3/0/0
 ip address 10.1.2.1 255.255.255.0
 negotiation auto
!
interface TenGigE 0/3/0/1
 ip address 10.1.3.1 255.255.255.0
 negotiation auto
!
router ospf 1
 router-id 10.2.3.4
area 0
 interface TenGigE 0/3/0/0
!
area 1
 interface TenGigE 0/3/0/1
!
!

The OSPF process is configured to redistribute the specified routes, and the operational state reflects your intended deployment.