Link Search Menu Expand Document


Configuration > Networking > Routing > OSPF

This tab manages OSPF (Open Shortest Path First) on LAN and WAN interfaces.

OSPF learns routes from routing peers, and then subnet shares them with EdgeConnect peers and/or BGP neighbors.

A route tag is applied to a route to better identify the source of the network it originated from. It is primarily used to filter routes from being redistributed in a routing loop.

Appliance NameName of the appliance.
Enable[Route Metric] Cost associated with a route. The higher the value, the less preferred.
Router IDThis router identifier is the IPv4 address by which the remote peer can identify this appliance for purposes of OSPF.
Redistribute Routes to OSPFRedistribution map being used to redistribute routes to OSPF.
DetailsAny additional details about your route.

Select the edit icon in the OSPF table to edit and enable OSPF.

OSPF Edit Row

Use this page to manage OSPF (Open Shortest Path First) on LAN and WAN interfaces.

OSPF learns routes from routing peers, and then subnet shares them with EdgeConnect peers and/or BGP neighbors.

Enable OSPFWhen enabled, the appliance has access to use the OSPF protocol.
Router IDIPv4 address of the router that the remote peer uses to identify the appliance for purposes of OSPF.
Redistribute routes to OSPFRedistributing routes into OSPF from other routing protocols or from static will cause these routes to become OSPF external routes. Select the edit icon to the left of this field and select the OSPF route redistribution maps you would like to select.

To add an additional interface to an OSPF route, click Add in the Interfaces section.

To configure or modify an OSPF route map, select the edit icon next to the Redistribute routes to OSPF field.

Add Interface

Complete the following fields to add an interface to OSPF.

InterfaceIndicates whether a Backup Designated Router (BDR) is specified for the Designated Router (DR). Options are Yes or No.
Area IDNumber of the area in which to locate the interface. The Area ID is the same for all interfaces.

It can be an integer between 0 and 4294967295, or it can take a form similar to an IP address, A.B.C.D.
CostThe cost of an interface in OSPF is an indication of the overhead required to send packets across a certain interface. It is used in the OSPF path calculation to determine link preference.
PriorityRouter priority. (If two or more best routes are subnet shared, peer priority is used as the tie-breaker.)
Admin StatusIndicates whether the interface is set to admin UP or DOWN.
Hello IntervalSpecifies the length of time, in seconds, between the hello packets that a router sends on an OSPF interface.
Dead IntervalNumber of seconds that a router’s Hello packets have not been seen before its neighbors declare the OSPF router down.
Transmit DelayNumber of seconds required to transmit a link state update packet. Valid values are 1 to 65535.
Retransmit IntervalAmount of time (in seconds) the router will wait to send retransmissions if the router receives no acknowledgment.
AuthenticationNone – No authentication.

Text – Simple password authentication allows a password (key) to be configured per area.

MD5 – Message Digest authentication is a cryptographic authentication. A key (password) and key-id are configured on each router. The router uses an algorithm based on the OSPF packet, the key, and the key-id to generate a “message digest” that gets appended to the packet.
CommentAny information you want to include for your own use.

OSPF Route Redistribution Maps

Route Maps are policies that can be applied to static, OSPF, BGP, and SD-WAN fabric learned routes. These policies have match and set criteria. A route map is applied to routes during route redistribution between routing protocols and allows for filtering routes or modifying route attributes.

Maximum allowed amounts for OSPF route maps and rules per route map:

  • You can specify up to 20 OSPF route maps.

  • You can apply up to 128 rules per route map.

You can add, delete, rename, or clone route maps using this window. You can add rules to your route map to further specify routing protocols by clicking Add Rule. Use rules to allow or deny routes based on numerous matching criteria.

NOTE: Prefix match criteria is ‘exact match + less than’. Both the prefix specified and any subnets of that prefix will be matched. This behavior will be updated in a future release to allow for selection of ‘exact,’ ‘greater than,’ or ‘less than’ criteria.

To permit a default-route, deny, deny, and then permit any.

You can specify the following fields in each rule for the selected route map.


PriorityIf you are using Orchestrator templates to add rules, Orchestrator will delete all entries from 1000 – 9999 before applying its policies.

You can create rules with higher priority than Orchestrator rules (1 – 999) and rules with lower priority (10000 – 19999 and 25000 – 65534).

NOTE: The priority range from 20000 to 24999 is reserved for Orchestrator.

When adding a rule, the priority is incremented by 10 from the previous rule. The priority can be changed, but this default behavior helps to ensure you can insert new rules without having to change subsequent priorities.

Select Match Criteria

Source ProtocolComplete the Following Fields (based on protocol selected)

BGP Communities
SD-WAN RoutesPrefix

BGP Communities


NOTE: The above fields in the right column will change depending on the source protocol chosen.

Set Actions

PermitEnable or disable. This setting allows or denies the route map.
OSPF TagValue of OSPF tag to set in routing information sent to destination.
OSPF Metric TypeFilters redistributed routes to OSPF.
MetricMetric for the route.
CommentComment you want to include.

Back to top

© Copyright 2022 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Aruba Networks and the Aruba logo are registered trademarks of Aruba Networks, Inc. Third-party trademarks mentioned are the property of their respective owners. To view the end-user software agreement, go to Aruba EULA.