After an OSPF process is created, a router ID is configured for the router, an interface on which OSPF runs and the area to which the interface belongs are specified, routes can be discovered and calculated in the AS.
OSPF on the router requires a router ID. The router ID is a 32-bit unsigned integer, which uniquely identifies the router in the AS. To ensure the stability of OSPF, manually set the router ID of each router during network planning.
OSPF prevents the link state database (LSDB) size from unexpectedly growing by partitioning an AS into different areas. An area is regarded as a logical group, and each group is identified by an area ID. At the border of an area resides the router instead of a link. A network segment (or a link) belongs to only one area. The area to which each OSPF interface belongs must be specified.
The system view is displayed.
An OSPF process is started, and the OSPF view is displayed.
The NetEngine 8000 F supports OSPF multi-instance. To run OSPF in a VPN instance, run the ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * command.
The NetEngine 8000 F supports OSPF multi-process. Processes can be classified by service type. The routers exchange packets regardless of process IDs.
router-id router-id specifies the router ID of the router.
By default, the router automatically selects the IP address of an interface as the router ID. When configuring the router ID, ensure that the router ID is unique in an AS. You can configure the IP address of an interface as the router ID.
Each router ID in an OSPF process must be unique. Otherwise, no OSPF neighbor relationships can be established, and routing information is incorrect.
If a router ID conflict occurs, perform either of the following operations:
After a router ID is replaced, the reset ospf [ process-id ] process command needs to be run to validate the new router ID.
If a VPN instance is specified, the OSPF process belongs to this VPN instance. If a VPN instance is not specified, the OSPF process belongs to the public-network instance.
You can run the description command to configure a description for the OSPF process for easier identification.
The OSPF area view is displayed.
OSPF areas are classified as a backbone area (with area ID 0) or non-backbone areas. The backbone area forwards inter-area routing information. The routing information exchanged between non-backbone areas must be forwarded through the backbone area.
You can run the description command to configure a description for the OSPF area for easier identification.
To configure the network segments included in an area, run the network address wildcard-mask [ description text ] command, in which description specifies the description of the area.
OSPF runs on an interface only when both of the following conditions are met:
The mask length of the interface's IP address is greater than or equal to that specified in the network command.
The interface's primary IP address belongs to the network segment specified in the network command.
By default, OSPF uses a host route with a 32-bit mask to advertise the IP address of a loopback interface, regardless of the mask length configured for the IP address. To allow a loopback interface to advertise network-segment routes, its network type must be set to NBMA or broadcast in the interface view. For details on how to set the network type, see Configuring Network Types for OSPF Interfaces.
The configuration is committed.