Enable GRE keepalive for a Route-Based VPN Tunnel element
You can enable GRE keepalive for individual route-based VPN tunnels to override the default settings defined for tunnel interfaces on the Secure SD-WAN Engine.
For more details about the product and how to configure features, click Help or press F1.
Steps
- Select Configuration, then browse to Secure SD-WAN.
- Browse to Route-Based SD-WAN Tunnels.
- Right-click a Route-Based SD-WAN Tunnelelement, then select Properties.
-
Enable GRE keepalive.
- Make sure that No Encryption is selected from the Encryption drop-down list.
- In the Tunnel options section, select Use GRE Keepalive.
- Configure the settings.
- Click OK.
Route-Based SD-WAN Tunnel Properties dialog box
Use this dialog box to define the properties of a Route-Based VPN Tunnel.
Option | Definition |
---|---|
Name | The name of the element. |
Enabled | When selected, the tunnel is enabled. |
Tunnel Type | Specifies the protocol used in the tunnel.
|
Encryption
(Not when Tunnel Type is VPN) |
The encryption mode for the tunnel.
|
SD-WAN Profile
(Optional) (When Tunnel Type is VPN) (When Encryption is Transport Mode) |
The VPN Profile element that defines the settings for authentication, integrity checking, and encryption for the tunnel. Note: Settings in the VPN Profile that do not apply
to route-based VPN tunnels, such as IPsec Client settings, are ignored.
Examples of available profiles:
|
Edit
(Optional) (When Tunnel Type is VPN) (When Encryption is Transport Mode) |
Allows you to use pre-shared key authentication for the gateways involved in the tunnel. Note: The pre-shared key must be long and random to provide a secure VPN. Change the
pre-shared key periodically (for example, monthly). Make sure that it is not possible for outsiders to obtain the key while you transfer it to other devices.
|
VPN
(When Encryption is Tunnel Mode) |
The policy-based VPN that provides the encryption for the tunnel. Click Select to select an element, or click New to create an element. |
Option | Definition |
---|---|
Local section | |
Gateway or Engine | The local gateway for the tunnel. Click Select to select an element. |
Endpoint (Not when Tunnel Type is VPN) |
Allows you to select the endpoint IP addresses for the tunnel. If loopback IP addresses are defined for a VPN Gateway, you can select a loopback IP address as the endpoint IP address. Note: You cannot use the same endpoint pair in a route-based VPN tunnel and a policy-based VPN tunnel.
|
Interface | The tunnel interface though which route-based VPN traffic is routed. |
Option | Definition |
---|---|
Remote section | |
Internal
(Not when Tunnel Type is VPN) (Not when Encryption is Transport Mode) |
When selected, specifies that the remote gateway is an Secure SD-WAN Engine that is managed by the same Management Server to which you are currently connected. |
External (Not when Tunnel Type is VPN) (Not when Encryption is Transport Mode) |
When selected, specifies that the remote gateway is a third-party device or an Secure SD-WAN Engine that is managed by a different Management Server. |
IP Address
(External only) |
The IP address of the remote gateway. |
Gateway or
Engine
(Internal only) |
The remote gateway in the tunnel. Click Select to select an element. |
Endpoint (Not when Tunnel Type is VPN) |
Allows you to select the endpoint IP addresses for the tunnel. If loopback IP addresses are defined for a VPN Gateway, you can select a loopback IP address as the endpoint IP address. Note: You cannot use the same endpoint pair in a route-based VPN tunnel and a policy-based VPN tunnel.
|
Interface
(SD-WAN Gateway elements only) |
The tunnel interface though which route-based VPN traffic is routed. |
Tunnels table (When Tunnel Type is VPN) |
|
Option | Definition |
---|---|
Tunnel Options section | |
PMTU Discovery
(All tunnel types except VPN) |
When selected, enables path MTU (PMTU) discovery. Select this option if you use dynamic routing and want to automatically determine the Maximum Transmission Unit (MTU) size on the network path to avoid IP fragmentation. |
TTL
(Optional) (All tunnel types except VPN) |
Specifies the initial time-to-live (TTL) value that is inserted into the encapsulation header of packets that enter the tunnel. This setting is needed when dynamic routing is used. You can usually use the default value. The default TTL value is 64. |
MTU
(Optional) |
Specifies the maximum transmission unit (MTU) value that defines the largest unit of data that can be transmitted without fragmenting a packet. Set the MTU size as large as possible, but not so large that it causes packets to be fragmented. You can usually use the default value. |
Tunnel Group (When Tunnel Type is VPN) (When Encryption is Transport Mode) |
Select the Tunnel Group to put the tunnel in. You can monitor the status of grouped tunnels in the Home view. By default, new tunnels are included in the Uncategorized group, which is a system Tunnel Group element. |
Use GRE Keepalive (When Tunnel Type is GRE and Encryption is No Encryption) |
When selected, the Secure SD-WAN Engine sends keepalive packets at the specified interval to check that the GRE tunnel is still functioning. If no reply is received after the specified number of packets, the GRE tunnel is considered to be down.
Note: To use GRE keep alive, the router to which the Secure SD-WAN Engine is connected must support GRE keep alive.
|
Comment (Optional) |
A comment for your own reference. |