OSPF
You can use the OSPF template for all vEdge Cloud and vEdge router devices.
To configure OSPF on vEdge routers using vManage templates:
- Create an OSPF feature template to configure OSPF parameters, as described in this article. OSPF can be used for service-side routing, to provide reachability to networks at the local site, and it can be used for transport-side routing, to enable communication between the vEdge router and other Viptela devices when the router is not directly connected to the WAN cloud. Create separate OSPF templates for the two OSPF routing types.
- Create a VPN feature template to configure VPN parameters for either service-side OSPF routing (in any VPN other than VPN 0 or VPN 512) or transport-side OSPF routing (in VPN 0). See the Configuration ► Templates ► VPN help topic.
- Create a device template that incorporates both the OSPF and VPN feature templates. See the Configuration ► Templates help topic.
Navigate to the Template Screen
- In vManage NMS, select the Configuration ► Templates screen.
- From the Templates title bar, select Feature.
- Click Add Template.
- In the left pane, select one or more devices. The right pane displays the available templates for the selected devices.
- Select the OSPF template.
The right pane displays the OSPF template form.
- The top of the form contains fields for naming the template.
- The bottom contains fields for defining parameters applicable to that template.
- A drop-down menu to the left of each parameter field defines the scope of the parameter. When you first open a feature template form, for each parameter that has a default value, the scope is set to Default. To edit a parameter field, change the scope to Global or Device Specific. Note that if a parameter's scope is Device Specific, you cannot enter a value for it in the feature template. Instead, you enter a value when you attach the template to a device.
- A plus sign (+) is displayed to the right when you can add multiple entries for the same parameter.
Minimum OSPF Configuration
The following parameters are required (unless otherwise indicated) to configure OSPF on a vEdge router:
Step | Parameter Name | Description |
---|---|---|
1. | Template Name | Enter a name for the template. It can be up to 128 characters and can contain only alphanumeric characters. |
2. | Description (Template) | Enter a description for the template. It can be up to 2048 characters and can contain only alphanumeric characters. |
3. | Router ID (optional) | Enter the OSPF router ID, in decimal four-part dotted notation. This is the IP address associated with the router for OSPF adjacencies. |
4. | Distance for External Routes (optional) | Specify the OSPF route administration distance for routes learned from other domains. Range: 0 through 255 |
5. | Distance for Inter-Area Routes (optional) | Specify the OSPF route administration distance for routes coming from one area into another. Range: 0 through 255 |
6. | Distance for intra-area routes (optional) | Specify the OSPF route administration distance for routes within an area. Range: 0 through 255 |
7. | Save | Click Save to save the feature template. |
You must also configure OSPF area 0, as described below.
CLI equivalent:
vpn vpn-id router distance external number inter-area number intra-area number router-id
Redistribute Routes into OSPF
To redistribute routes learned from other protocols into OSPF on vEdge routers, select the Redistribute tab and click the plus sign (+):
Parameter Name | Description |
---|---|
Protocol | Select the protocol from which to redistribute routes into OSPF. Select from BGP, Connected, NAT, OMP, and Static. |
Route Policy | Enter the name of a localized control policy to apply to routes before they are redistributed into OSPF. |
To add another OSPF route redistribution policy, click the plus sign (+).
To remove an OSPF route redistribution policy from the template configuration, click the trash icon to the right of the entry.
CLI equivalent:
vpn vpn-id router ospf redistribute (bgp | connected | nat | omp | static) route-policy policy-name
Configure OSPF To Advertise a Maximum Metric
To configure OSPF to advertise a maximum metric so that other routers do not prefer this vEdge router as an intermediate hop in their Shortest Path First (SPF) calculation, select the Max Metric (Router LSA) tab and click the plus sign (+):
Parameter Name | Description |
---|---|
Type | Select a type:
|
Time | Specify the number of seconds to advertise the maximum metric after the router starts up, to use if you specified On-Startup. Range: 0, 5 through 86400 seconds |
CLI equivalent:
vpn vpn-id router ospf max-metric router-lsa (administrative | on-startup seconds)
Configure OSPF Areas
To configure an OSPF area within a VPN on a vEdge router, select the Area tab and click the plus sign (+). An a minimum, you must configure area 0.
Parameter Name | Description |
---|---|
Number | Enter the number of the OSPF area. Range: 32-bit number |
Area Type | Select the type of OSPF area, Stub or NSSA. |
No Summary | Select On to not inject OSPF summary routes into the area. |
Translate | If you configured the area type as NSSA, select when to allow vEdge routers that are ABRs (area border routers) to translate Type 7 LSAs to Type 5 LSAs: always—Router always acts as the translator for Type 7 LSAs. That is, no other router, even if it is an ABR, can be the translator. If two ABRs are configured to always be the translator, only one of them actually ends up doing the translation.candidate—Router offers translation services, but does not insist on being the translator. never—Translate no Type 7 LSAs |
CLI equivalent:
vpn vpn-id router ospf area number nssa no-summary translate (always | candidate | never) stub no-summary
Configure Interfaces in an OSPF Area
To configure the properties of an interface in an OSPF area:
- Select the Area tab.
- Scroll to the right and click the Interface link for the area. An Interface section appears under the area.
- Click Add. The Interface window opens:
Parameter Name | Description |
---|---|
Interface Name | Enter the name of the interface, in the format geslot/port or loopbacknumber. |
Hello Interval |
Specify how often the router sends OSPF hello packets. Range: 1 through 65535 seconds |
Dead Interval |
Specify how often the vEdge router must receive an OSPF hello packet from its neighbor. If no packet is received, the vEdge router assumes that the neighbor is down. Range: 1 through 65535 seconds |
LSA Retransmission Interval |
Specify how often the OSPF protocol retransmits LSAs to its neighbors. Range: 1 through 65535 seconds |
Interface Cost |
Specify the cost of the OSPF interface. Range: 1 through 65535 |
Save, or Advanced Options | Click Save to save the settings for the interface, or click Advanced Options to configure additional options for the interface as described below. |
To configure advanced options for an interface in an OSPF area:
Parameter name | Description |
---|---|
Designated Router Priority | Set the priority of the router to be elected as the designated router (DR). The router with the highest priority becomes the DR. If the priorities are equal, the node with the highest router ID becomes the DR or the backup DR. Range: 0 through 255 Default: 1 |
OSPF Network Type |
Select the OSPF network type to which the interface is to connect:
Default: Broadcast |
Passive Interface | Select On or Off to specify whether to set the OSPF interface to be passive. A passive interface advertises its address, but does not actively run the OSPF protocol. Default: Off |
Authentication | Specify the authentication and authentication key on the interface, to allow OSPF to exchange routing update information securely. |
• Authentication Type |
Select the authentication type:
|
• Authentication Key | Enter the authentication key. Plain text authentication is used when devices within an area cannot support the more secure MD5 authentication. The key can be 1 to 32 characters. |
Message Digest | Specify the key ID and authentication key if you are using message digest (MD5). |
• Message Digest Key ID | Enter the key ID for message digest (MD5 authentication). It can be 1 to 32 characters. |
• Message Digest Key | Enter the MD5 authentication key, in clear text or as an AES-encrypted key. It can be from 1 to 255 characters. |
Save | Click Save to save the settings for the interface and return to the OSPF template screen. |
CLI equivalent:
vpn vpn-id router ospf area number interface interface-name authentication authentication-key key message-digest key type (message-digest | simple) cost number dead-interval seconds hello-interval seconds network (broadcast | point-to-point) passive-interface priority number retransmit-interval seconds
Configure an Interface Range for Summary LSAs
To summarize OSPF routes at an area boundary so that only a single summary route is advertised to other areas by an ABR:
- Select the Area tab
- Scroll to the right and click Range at the right side. A Range section appears under the area.
- Click the plus sign (+) on the right side:
Parameter Name | Description |
---|---|
Address | Enter the IP address and subnet mask, in the format prefix/length, for the IP addresses to be consolidated and advertised. |
Cost | Specify a number for the Type 3 summary LSA. OSPF uses this metric during its SPF calculation to determine the shortest path to a destination. Range: 0 through 16777215 |
No Advertise | Select On to not advertise the Type 3 summary LSAs or Off to advertise them. |
CLI equivalent:
vpn vpn-id router ospf area number range prefix/length cost number no-advertise
Configure Other OSPF Properties
To configure other OSPF properties, select the Advanced tab:
Parameter Name | Description |
---|---|
Reference Bandwidth | Specify the reference bandwidth for the OSPF auto-cost calculation for the interface. Range: 1 through 4294967 Mbps |
RFC 1538 Compatible | By default, the OSPF calculation is done per RFC 1583. Select Off to calculate the cost of summary routes based on RFC 2328. |
Originate | Click On to generate a default external route into an OSPF routing domain:
|
SPF Calculation Delay | Specify the amount of time between when the first change to a topology is received until performing the SPF calculation. Range: 0 through 600000 milliseconds (60 seconds) |
Initial Hold Time | Specify the amount of time between consecutive SPF calculations. Range: 0 through 600000 milliseconds (60 seconds) |
Maximum Hold Time | Specify the longest time between consecutive SPF calculations. Range: 0 through 600000 |
Policy Name | Enter the name of a localized control policy to apply to routes coming from OSPF neighbors. |
CLI equivalent:
vpn vpn-id router ospf auto-cost reference-bandwidth mbps compatible rfc1583 default-information originate (always | metric metric | metric-type type) route-policy policy-name in timers spf delay initial-hold-time maximum-hold-time
Release Information
Introduced in vManage NMS in Release 15.2.