Configuring OSPF Using the Web UI

This section describes how to use the Web user interface (UI) to configure OSPF.

Adding an OSPF Process

Choose Network > Route > OSPF.
Click Add.

Enter or select the parameters.

**Table 1** Adding an OSPF process
Parameter	Description
Type	OSPF version: OSPF v2: OSPF for IPv4. In this example, OSPF v2 is used. OSPF v3: OSPF for IPv6.
Process ID	The system supports OSPF multi-process. If multiple OSPF processes are enabled on one device, different process IDs need to be specified. An OSPF process ID is a local concept. The devices with different process IDs can exchange packets in between.
Router ID	To ensure the OSPF running stability, during the network planning, router IDs need to be planned and manually configured. This ensures that each device in the autonomous system (AS) has a unique router ID. A common undertaking is to set the router ID to be the IP address of a certain interface on the device. If the router ID is not manually specified, the system automatically selects one from the configured interface IP addresses. The selection sequence is: The maximum IP address of the loopback interface IP addresses is preferentially selected as the route ID. If no loopback interface is available, the maximum IP address of interfaces is selected as the router ID.
Virtual Router	Specifies the public or VPN instance name. The VPN instance name indicates a common VPN or the VPN created for a virtual system. When you configure an OSPF route for a virtual system, the destination virtual router must be set to the VPN instance with the same name as the virtual system.
SPF Calculation Interval	The shortest path first (SPF) calculation period of an OSPF route. If the network topology keeps changing, the immediate calculation of the shortest path affects the efficiency of a router. By adjusting the minimum interval between two contiguous SPF calculations, the influence of network topology changes is reduced. You can change the value of this parameter based on the actual network condition.
Internal Priority	Indicates the default route priority of the OSPF routing protocol.
ASE Priority	Indicates the default route priority of the OSPF routing protocol outside the AS.
BFD Function	Enables the function of BFD for OSPF.
Local Detection Multiple	Indicates the local detection multiple.
Sending Interval	Indicates the interval for sending the BFD packets.
Receiving Interval	Indicates the interval for receiving the BFD packets.
Default Route	Advertises the default route in the OSPF route area. In this case, active default routes of other OSPF processes must exist in the routing table of the device. You can specify this parameter when you need to import the default route to the OSPF area.
Always	Generates and advertises the default route regardless of whether active default routes of other OSPF processes exist in the routing table of the device. You can configure this parameter only when Default Route is selected.

Click OK.
If the new OSPF process is displayed on the page, the operation succeeds.

Configuring an OSPF Area

The network expansion results in a huge link state database (LSDB). This adds the routers' workloads and reduces their performance.

This problem can be resolved by allocating OSPF areas, and performing route aggregation on area border routers. In this way, the number of LSAs advertised to other areas is reduced, network performance is enhanced, and adverse influence caused by network topology changes is minimized.

Choose Network > Route > OSPF.
Click corresponding to the OSPF process to be modified.
In the OSPF Process ID:ID navigation tree, choose Basic Configuration > Area Settings.
Click Add.

Enter or select the parameters.

Parameter	Description
Area	Indicates the area identifier.
IP Network	Indicates the IP address of the network segment to be added to the OSPF area. The OSPF protocol takes effect only on an interface that meets the following two requirements: The length of the interface IP address mask is not shorter than the length of the IP Network mask. The OSPF uses a reverse mask. For example, 0.0.0.255 indicates that the length of the mask is 24 bits. If the mask is 0.0.0.0, it indicates that all 32 bits of the address must be exactly matched without considering the IP address mask length of the interface. This method exactly controls the running of OSPF on interfaces. The primary IP address of the interface is in the specified network segment range.
Mask/Wildcard Mask	Indicates the mask or reverse mask of an IP address. The device supports both masks and inverse masks. For example, after mask 255.255.128.0 is entered, the system automatically identifies and displays the corresponding inverse mask 0.0.127.255.
Authentication Mode	Indicates the authentication mode towards packets in an OSPF area. NONE: indicates none-authentication. Simple: indicates simple authentication. MD5: indicates MD5 authentication. HMAC-MD5: indicates HMAC-MD5 authentication. HMAC-SHA256: indicates HMAC-SHA256 authentication. If authentication mode and password are configured both on an OSPF area and interface, the settings on the interface take precedence.
Password Type	Selects a method for configuring passwords. This parameter is required when Authentication Mode is Simple. Two methods, Plain and Cipher, are available.
Simple Password	Specifies the area authentication password. This parameter is required when Authentication Mode is Simple.
Confirm Password	The password needs to be confirmed when Password Type is Cipher.
MD5 Key	Configures the identifier of the MD5 authentication key. This parameter is required when Authentication Mode is MD5.
MD5 Password	Configures the MD5 authentication key. This parameter is required when Authentication Mode is MD5.
HMAC-MD5 Key	Configures the identifier of the HMAC-MD5 authentication key. This parameter is required when Authentication Mode is HMAC-MD5.
HMAC-MD5 Password	Configures the HMAC-MD5 authentication key. This parameter is required when Authentication Mode is HMAC-MD5.
HMAC-SHA256 Key	Configures the identifier of the HMAC-SHA256 authentication key. This parameter is required when Authentication Mode is HMAC-SHA256.
HMAC-SHA256 Password	Configures the HMAC-SHA256 authentication key. This parameter is required when Authentication Mode is HMAC-SHA256.
Area Type	Indicates the area type. NONE: indicates that the OSPF area is a common area. Other attributes are not set. Stub: indicates that the OSPF area is the stub area. The stub area is special. The ABR in this type of area does not advertise the received ASE routes. The scale of the routing table and the quantity of the routing information to be transmitted are greatly reduced. NSSA: Indicates that the OSPF area is the NSSA area, which is an extension of the Stub area. This type of area does not allow the import of the Type-5 LSA but allows the import of the Type-7 LSA. The Type7 LSA is generated by the ASBR in the NSSA area, and transmitted in the NSSA area. When the Type7 LAS reaches the ABR of the NSSA, the ABR changes the Type7 LSA to the Type5 LSA, and then transmits the Type5 LSA to other areas.
Default Cost	Indicates the cost of the default routes sent to the Stub area or the NSSA area through OSPF. This item is required when you set Area Type to Stub or NSSA.
Stub Area Setting	This parameter enables a stub area to be a totally stub area, and denies Type3 LSAs from entering the stub area that connects to the ABR. This reduces the number of LSAs sent to the stub area. This item is required when you set Area Type to Stub.
NSSA Settings	If the area is an NSSA, you can perform the following configurations: Advertise default route to NSSA: indicates that the default Type-7 LSA is generated. On the ABR, the default Type-7 LSA is generated no matter whether the route 0.0.0.0 exists in the routing table. On the ASBR, the default Type-7 LSA is generated when the route 0.0.0.0 exists in the routing table. Do not import external routes: indicates that the external routes imported to the ASBR are not advertised to the NSSA area. Totally NSSA: indicates that inter-area routes (Type-3 LSAs) are not imported to the totally NSSA. The ABR automatically generates a default Type-3 LSA and advertises it in the entire NSSA.

Click Confirm.
If the new OSPF area is displayed on the page, the operation succeeds.

Configuring an OSPF Network Segment

Choose Network > Route > OSPF.
Click corresponding to the OSPF process to be modified.
In the OSPF Process ID:ID navigation tree, choose Basic Configuration > Network Settings.
Click Add.
In the Area drop-down list, select an existed area.
Enter a network segment address and a mask to be added.

The device supports both masks and inverse masks. For example, after mask 255.255.128.0 is entered, the system automatically identifies and displays the corresponding inverse mask 0.0.127.255.
Click Confirm.
If the new network segment is displayed on the page, the operation succeeds.

Configuring an OSPF Interface

Choose Network > Route > OSPF.
Click corresponding to the OSPF process to be modified.
In the OSPF Process ID:ID navigation tree, choose Basic Configuration > Interface Settings.
Click corresponding to the interface to be configured.

Enter or select the parameters.

Parameter	Description
Interface Name	Indicates the name of an OSPF interface.
Network Type	Indicates the network type of an OSPF interface. Broadcast: indicates that the network type of the interface is broadcast. NBMA: indicates that the network type of the interface is nonbroadcast multiaccess (NBMA). P2MP: indicates that the network type of the interface is point-to-multipoint (P2MP). P2P: indicates that the network type of the interface is point-to-point (P2P).
Cost	Indicates the cost of running the OSPF protocol on the interface.
MTU	Enables the interface to use the actual MTU value when it sends DD packets. Usually, the establishment of a peer relationship requires that the Hello and Dead timers at the two ends of a link have same values respectively and do not compare the MTU values of the ports. The MTU negotiation can be enabled for this function. Then if the MTU values of the ports are different, a peer relationship cannot be established.
Authentication Mode	Indicates the mode in which the OSPF interface authenticates packets. NONE: indicates that interface authentication is not configured. Simple: indicates simple authentication. MD5: indicates MD5 authentication. HMAC-MD5: indicates HMAC-MD5 authentication. HMAC-SHA256: indicates HMAC-SHA256 authentication. If authentication mode and password are configured both on an OSPF area and interface, the settings on the interface take precedence.
Password Type	Selects a method for configuring passwords. This parameter is required when Authentication Mode is Simple. Two methods, Plain and Cipher, are available.
Simple Password	Indicates the authentication password of the interface. This parameter is required when Authentication Mode is Simple.
Confirm Password	The password needs to be confirmed when Password Type is Cipher.
MD5 Key	Configures the identifier of the MD5 authentication key. This parameter is required when Authentication Mode is MD5.
MD5 Password	Configures the MD5 authentication key. This parameter is required when Authentication Mode is MD5.
HMAC-MD5 Key	Configures the identifier of the HMAC-MD5 authentication key. This parameter is required when Authentication Mode is HMAC-MD5.
HMAC-MD5 Password	Configures the HMAC-MD5 authentication key. This parameter is required when Authentication Mode is HMAC-MD5.
HMAC-SHA256 Key	Configures the identifier of the HMAC-SHA256 authentication key. This parameter is required when Authentication Mode is HMAC-SHA256.
HMAC-SHA256 Password	Configures the HMAC-SHA256 authentication key. This parameter is required when Authentication Mode is HMAC-SHA256.
Advanced Settings
DR Priority	When the network type is broadcast or NBMA, you can configure the interface DR priority to affect the DR/BDR selection on the network. This parameter is required when Network Type is Broadcast or NBMA. The DR priority value is in direct proportion to the priority. If the priority is set to 0, the interface is unavailable for the DR selection.
Transmission Delay	Indicates the delay of transmitting the LSA on the interface. The LSA in the local router LSDB is aging with time (its value is increased by 1 every second); however, the network transmission process does not age with time; therefore, you are advised to add the latency to the LSA aging period before sending the LSA. This is especially important for a low-speed network.
Peer Timeout	Indicates the timeout period. The intervals for sending Hello packets and the peer timeout periods of interfaces on the same network segment must have same values respectively. The poll interval or the peer timeout interval of the same interface is at least four times longer than the interval for sending Hello packets.
Hello Packet Interval	Indicates the interval for sending Hello packets. A shorter interval for sending Hello packets results in a faster speed in detecting network topology changes and larger cost on system resources.
Polling Interval	Indicates the interval for sending polling Hello packets. This parameter defines the interval for sending polling Hello packets from an NBMA interface to peer routers with a Down state.
Retransmission Interval	After a router sends an LSA to its peer router, it waits for a confirmation packet sent by the peer router. If no confirmation packet is received within this interval, the router resends the LSA. This parameter defines the interval for resending an LSA.
BFD Block	Indicates whether to configure BFD block: Select Block, indicating to enable the function of blocking to prevent the dynamic creation of BFD sessions on an interface. Select Enable, indicating to enable the BFD function. And you need to further configure Sending Interval, Local Detection Multiple and Receiving Interval. Select Inherit, indicating to enable the BFD function and inherit the BFD configuration in the OSPF process.
Sending Interval	Indicates the interval for sending the BFD packets.
Local Detection Multiple	Indicates the local detection multiple.
Receiving Interval	Indicates the interval for receiving the BFD packets.

Click Confirm.

Configuring Route Importing for an OSPF Process

If a router runs the OSPF and other routing protocols, you can configure the OSPF to import routes generated by other protocols, such as RIP, ISIS, BGP, static route, or direct route. These route information is advertised by using Type5 LSAs or Type7 LSAs.

Choose Network > Route > OSPF.
Click corresponding to the OSPF process to be modified.
In the OSPF Process ID:ID navigation tree, choose Advanced > Route Import.
Click Add.

Enter or select the parameters.

Parameter	Description
Route Type	Indicates the imported source routing protocol.
Process ID	The routing protocol process number needs to be specified when the Route Type is set to OSPF, RIP, or ISIS.
Route Policy	Indicates the configured routing policy.
Cost	Indicates the cost of an imported route.
Tag	Indicates the tag of an imported route.
Type	Indicates the type of an imported route.

Click Confirm.
If the new route import configuration is displayed on the page, the operation succeeds.

Configuring a Virtual Link

You can establish a logical channel between two ABRs through a non-backbone area by configuring OSPF virtual links.

Note the following when you configure a virtual link:

A virtual link must be configured between two ABRs.
The transmit area that the virtual link goes through must have the complete route selection information.
The transmit area cannot be a Stub area or NSSA area.

Choose Network > Route > OSPF.
Click corresponding to the OSPF process to be modified.
In the OSPF Process ID:ID navigation tree, choose Advanced > Virtual Link.
Click Add.

Enter or select the parameters.

Parameter	Description
Peer Router ID	Indicates the ID of the peer router of the virtual link.
Transit Area	Indicates the OSPF area which the virtual link goes through.
Advanced Settings
Transmission Delay	Indicates the delay of transmitting the LSA on the interface. The LSA in the local router LSDB is aging with time (its value is increased by 1 every second); however, the network transmission process does not age with time; therefore, you are advised to add the latency to the LSA aging period before sending the LSA. This is especially important for a low-speed network.
Peer Timeout	Indicates the timeout period. The intervals for sending Hello packets and the peer timeout periods of interfaces on the same network segment must have same values respectively. The poll interval or the peer timeout interval of the same interface is at least four times longer than the interval for sending Hello packets.
Hello Packet Interval	Indicates the interval for sending Hello packets. A shorter interval for sending Hello packets results in a faster speed in detecting network topology changes and larger cost on system resources.
Retransmission Interval	After a router sends an LSA to its peer router, it waits for a confirmation packet sent by the peer router. If no confirmation packet is received within this interval, the router resends the LSA. This parameter defines the interval for resending an LSA.
Authentication Mode	Indicates the authentication mode towards packets in an OSPF area. NONE: indicates none-authentication. Simple: indicates simple authentication. MD5: indicates MD5 authentication. HMAC-MD5: indicates HMAC-MD5 authentication. HMAC-SHA256: indicates HMAC-SHA256 authentication. If authentication mode and password are configured both on an OSPF area and interface, the settings on the interface take precedence.
Password Type	Selects a method for configuring passwords. This parameter is required when Authentication Mode is Simple. Two methods, Plain and Cipher, are available.
Simple Password	Specifies the area authentication password. This parameter is required when Authentication Mode is Simple.
Confirm Password	The password needs to be confirmed when Password Type is Cipher.
MD5 Key	Configures the identifier of the MD5 authentication key. This parameter is required when Authentication Mode is MD5.
MD5 Password	Configures the MD5 authentication key. This parameter is required when Authentication Mode is MD5.
HMAC-MD5 Key	Configures the identifier of the HMAC-MD5 authentication key. This parameter is required when Authentication Mode is HMAC-MD5.
HMAC-MD5 Password	Configures the HMAC-MD5 authentication key. This parameter is required when Authentication Mode is HMAC-MD5.
HMAC-SHA256 Key	Configures the identifier of the HMAC-SHA256 authentication key. This parameter is required when Authentication Mode is HMAC-SHA256.
HMAC-SHA256 Password	Configures the HMAC-SHA256 authentication key. This parameter is required when Authentication Mode is HMAC-SHA256.

Click Confirm.
If the new virtual link is displayed on the page, the operation succeeds.

Configuring OSPF Route Aggregation

Route aggregation refers to aggregating the routes that share the same prefix and releasing only one route to other areas.

Choose Network > Route > OSPF.
Click corresponding to the OSPF process to be modified.
In the OSPF Process ID:ID navigation tree, choose Advanced > Route Summary.
Click Add.

Enter or select the parameters.

Parameter	Description
Aggregation Type	Indicates the type of route aggregation. ABR: indicates that the route aggregation is configured on the devices locating at the border of an area. ASBR: indicates that the route aggregation is configured for the ASE routes.
Area	Indicates the area where the local device to be configured with the route aggregation resides. This parameter is available when Summary Type is ABR.
IP Address	Configure an aggregated route.
Mask	Configure the mask of an aggregated route.
Cost	Configure the cost of an aggregated route.
Aggregation Control	Do not advertise routes that match the designated IP address/mask. indicates that the aggregated route is not advertised.
Tag	Tags the aggregated ASEs. This parameter is available when Summary Type is ASBR.

Click Confirm.
If the new route aggregation configuration is displayed on the page, the operation succeeds.

Prohibiting an Interface from Receiving and Sending OSPF Packets

You can prohibit some interfaces from receiving and sending OSPF packets. This does not affect the advertisement of directly connected routes, but blocks the Hello packets, reduces the consumption of system resources, and increases the OSPF network flexibility.

Choose Network > Route > OSPF.
Click corresponding to the OSPF process to be modified.
In the OSPF Process ID:ID navigation tree, choose Advanced > Passive Interface.
Click Add.
In the Interface Name drop-down list, select the interface to be configured.
Click Confirm.
If the new disabled interface is displayed on the page, the operation succeeds.

Configuring Route Filtering

A router provides a routing information filtering function. By specifying an ACL, you can configure an ingress or egress filtering policy to filter the received and released routes.

Choose Network > Route > OSPF.
Click corresponding to the OSPF process to be modified.
In the OSPF Process ID:ID navigation tree, choose Advanced > Route Filter.
Click Add.

Enter or select the parameters.

Parameter	Description
Filter Type	Indicate the route filter type of the OSPF. After this parameter is set, it cannot be changed. Import: indicates the filtering of the routes calculated by OSPF. Only the routes that match the filtering rules are added to the routing table. Export: indicates the filtering of the routes imported by OSPF. Only the routes that match the filtering rules are advertised.
Route Type	Advertise routes based on the route type based filtering. This parameter is required when the Filter Type is Export. After this parameter is set, it cannot be changed. If NONE is selected, OSPF filters all the imported routing information.
Process ID	Specifies the process ID for OSPF, RIP, and ISIS. After this parameter is set, it cannot be changed.
ACL	Sets a matching rule based on the ACL. It is used for filtering routes according to destination IP addresses. Indicates the basic ACL number. You can select an existed ACL or select Basic ACL to create a new ACL. Source Address, Schedule, and Action are available when ACL is Basic ACL. NOTE: When deleting route filtering configurations, you can delete the referenced ACL or delete only route filtering configurations.
Source Address	Indicates the source IP address for filtering routes or the name of the source address/address group. You can select an existed address/address group or create a new address/address group.
Schedule	Indicates the time range during which route filtering takes effect. You can select an existed time range or create a new time range.
Action	Indicates the action taken by the device towards the route. permit: indicates the action configured by the policy is performed on the route. deny: indicates that the action configured by the policy is not performed on the route.

Click Confirm.
If the new route filtering policy is displayed on the page, the operation succeeds.