Describes how to configure a Non SD-WAN Destination of type Generic IKEv1 Router (Route Based VPN) through SD-WAN Gateway in SD-WAN Orchestrator.

Note: To configure a Generic IKEv1 Router (Route Based VPN) via Edge, see Configure a Non-VMware SD-WAN Site of Type Generic IKEv1 Router via Edge.

Procedure

  1. From the navigation panel in the SD-WAN Orchestrator, go to Configure > Network Services.
    The Services screen appears.
  2. In the Non SD-WAN Destinations via Gateway area, click the New button.
    The New Non SD-WAN Destinations via Gateway dialog box appears.
  3. In the Name text box, enter the name for the Non SD-WAN Destination.
  4. From the Type drop-down menu, select Generic IKEv1 Router (Route Based VPN).
  5. Enter the IP address for the Primary VPN Gateway (and the Secondary VPN Gateway if necessary), and click Next.
    A route-based Non SD-WAN Destination of type IKEv1 is created and a dialog box for your Non SD-WAN Destination appears.
  6. To configure tunnel settings for the Non SD-WAN Destination’s Primary VPN Gateway, click the Advanced button.
  7. In the Primary VPN Gateway area, you can configure the following tunnel settings:
    Field Description
    Tunnel Mode Active-Hot-Standby is supported on the SD-WAN Gateway. Active/Hot-Standby automatically displays indicating that if the Active tunnel goes down, the Standby (Hot-Standby) tunnel takes over and becomes the Active tunnel.
    PSK The Pre-Shared Key (PSK), which is the security key for authentication across the tunnel. The Orchestrator generates a PSK by default. If you want to use your own PSK or password then you can enter it in the textbox.
    Note: Starting from the 4.5 release, the use of the special character "<" in the password is no longer supported. In cases where users have already used "<" in their passwords in previous releases, they must remove it to save any changes on the page.
    Encryption Select either AES 128 or AES 256 as the AES algorithms key size to encrypt data. The default value is AES 128.
    DH Group Select the Diffie-Hellman (DH) Group algorithm to be used when exchanging a pre-shared key. The DH Group sets the strength of the algorithm in bits. The supported DH Groups are 2, 5, and 14. It is recommended to use DH Group 14.
    PFS Select the Perfect Forward Secrecy (PFS) level for additional security. The supported PFS levels are 2 and 5. The default value is 2.
  8. If you want to create a Secondary VPN Gateway for this site, then click the Add button next to Secondary VPN Gateway. In the pop-up window, enter the IP address of the Secondary VPN Gateway and click Save Changes.

    The Secondary VPN Gateway will be created immediately for this site and will provision a VMware VPN tunnel to this Gateway.

  9. Select the Redundant VeloCloud Cloud VPN checkbox to add redundant tunnels for each VPN Gateway.
    Any changes made to Encryption, DH Group, or PFS of Primary VPN Gateway will also be applied to the redundant VPN tunnels, if configured. After modifying the tunnel settings of the Primary VPN Gateway, save the changes and then click View IKE/IPsec Template to view the updated tunnel configuration.
  10. Click the Update location link to set the location for the configured Non SD-WAN Destination. The latitude and longitude details are used to determine the best Edge or Gateway to connect to in the network.
  11. Local authentication ID defines the format and identification of the local gateway. From the Local Auth Id drop-down menu, choose from the following types and enter a value that you determine:
    • FQDN - The Fully Qualified Domain Name or hostname. For example, google.com.
    • User FQDN - The User Fully Qualified Domain Name in the form of email address. For example, [email protected].
    • IPv4 - The IP address used to communicate with the local gateway.
    Note:

    For Generic route based VPN, if the user does not specify a value, Default is used as the local authentication ID. The default local authentication ID value will be the SD-WAN Gateway Interface Public IP.

  12. Under Site Subnets, you can add subnets for the Non SD-WAN Destination by clicking the + button. If you do not need subnets for the site, select the Deactivate Site Subnets checkbox.
  13. Check the Enable Tunnel(s) checkbox once you are ready to initiate the tunnel from the SD-WAN Gateway to the Generic IKEv1 VPN Gateways.
  14. Click Save Changes.
  15. Assign the newly created Non SD-WAN Site Network Service to a Profile by navigating to Configure >Profiles in the SD-WAN Orchestrator. See Configure a Tunnel Between a Branch and a Non SD-WAN Destinations via Gateway.
  16. Return to the Non SD-WAN Destinations via Gateway area in the SD-WAN Orchestrator by going to Configure > Network Services.
  17. In the Non SD-WAN Destinations via Gateway area, scroll to the name of your Non SD-WAN Site, and then click the Edit link in the BGP column.
  18. Configure the BGP values for the following mandatory fields: Local ASN, Tunnel Type, Neighbor IP, and Local IP (from the Advanced Options section). For more information, see Configure BGP over IPsec from Gateways.
    Note: The VTI IP (private IP) assigned by the SD-WAN Orchestrator can be used for peer ship in Single-Hop BGP.
  19. Click OK to save your changes.
  20. In the Non SD-WAN Destinations via Gateway area, click the Edit link in the BFD column for a Non SD-WAN Destination, to configure the BFD settings. For more information, see Configure BFD for Gateways.

What to do next

You can check the overall status of the Non SD-WAN Sites in the monitoring tab. See: