Configure Additional Tunnels on EdgeConnect

Configure Additional Tunnels on EdgeConnect

To enable the active – active breakout scenario, you will create two additional IPSec tunnels to the same primary POP and the same failover POP from a secondary internet interface on your EdgeConnect appliance.

Create a Tunnel to a Primary POP

  1. Log in to Silver Peak Unity Orchestrator.
  2. In the device tree on the left, select the EdgeConnect appliance where you want to configure the tunnel to Netskope.
  3. Open the Tunnels tab (click Configuration > Networking > Tunnels > Tunnels).
  4. image6.pngClick the edit icon to the left of any row in the table of tunnels.
  5. On the tunnels detail page, click the Passthrough button at the top of the table, and then click the Add Tunnel button. The Add Passthrough Tunnel dialog appears.
    image7.jpeg
  6. Enter or select the new tunnel parameters as follows:
    ParameterDescription
    AliasEnter a descriptive name for the tunnel.
    ModeSelect IPSec.
    AdminThe administrative state of the tunnel. You can leave this at the default value of up.
    Local IPThe IP address of the WAN interface that will originate the IPSec tunnel. This should be the WAN interface associated with your second ISP.
    Remote IPEnter the IP address of the primary Netskope POP that you configured in Netskope.
    NATThis should be set to none.
    Peer/ServiceEnter the same service that was used for the first EdgeConnect tunnel.
    Auto Max BW EnabledLeave this checkbox selected to let the appliance auto-negotiate the maximum tunnel bandwidth.
    Max

    BW Kbps

    This field is not available when auto bandwidth is enabled.
    image15.png
  7. Click IKE in the Add Passthrough Tunnel dialog.
  8. Enter or select the new tunnel parameters as follows:

    Set the IKE Version to IKE v2 first as it will change some of the other fields available.

    ParameterDescription
    IKE VersionSet this to IKE v2.
    Preshared KeyEnter the same preshared key that you created on Netskope.
    Authentication AlgorithmSelect SHA1.
    Encryption AlgorithmSelect the same algorithm as on Netskope (AES-128 or AES-256).
    Diffie-Hellman GroupSelect 14.
    Rekey Interval/LifetimeLeave this at the default value of 480.
    Dead Peer DetectionYou can leave the delay time at its default value, and retry count cannot be changed.
    Local IKE IdentifierEnter the Source Identity that you assigned to the second tunnel on Netskope.
    Remote

    IKE Identifier

    Enter the IP address of the primary Netskope POP that you configured in Netskope.
    Phase 1 ModeThis value cannot be changed.
    image9.jpeg
  9. Click IPSec in the Add Passthrough Tunnel dialog.
  10. Enter or select the new tunnel parameters as follows:
    ParameterDescription
    Authentication AlgorithmSelect SHA1.
    Encryption AlgorithmSelect AES-128.
    Enable IPsec Anti-Replay WindowLeave this checkbox selected.
    Rekey Interval/LifetimeYou can leave these values at their defaults.
    Perfect Forward Secrecy GroupThis can be left at the default value of 14.
    image10.jpeg
  11. When the settings for General, IKE, and IPsec are complete, click Save to create the new tunnel.

Create Tunnel to Failover POP

  1. Click Add Tunnel to create a second tunnel to the failover POP.
  2. Use the same values that you used for the first tunnel except for the following:
    • Alias: Use a different name for the second Silver Peak tunnel.
    • Remote IP: Enter the IP address of the failover POP that you configured in Netskope.
    • Peer/Service: Enter the same service name to direct traffic to the failover POP (same as the second EdgeConnect tunnel).
    • Remote IKE Identifier: Use the IP address of the failover POP.

After creating the IPsec tunnels from the EdgeConnect appliance to the primary and failover POPs using ISP1 and ISP2, there are no additional changes to be made to the existing BIO. Proceed to, Configure Business Intent Overlay Policies if needed.

Share this Doc

Configure Additional Tunnels on EdgeConnect

Or copy link

In this topic ...