Configure the Silver Peak Remote Network
Configure the remote network between the Silver Peak SD-WAN and Prisma Access by completing the steps in the following workflows:
Configure the Remote Network Tunnel
Use this workflow to configure Silver Peak EdgeConnect with Prisma Access.
Silver Peak recommends that you configure two tunnels in an active-backup configuration between Silver Peak EdgeConnect and Prisma Access, because there are some restrictions for accessing resources at other network locations when you configure the tunnels in an active-active configuration because of the overlapping subnets.
Before you start this workflow, determine your remote tunnel capacity. Silver Peak bases the tunnel capacity on licensing and the capacity of the device model. For example, the base Silver Peak license supports up to 200 Mbps WAN uplink, and the EC-XS supports 200 Mbps. Prisma Access bases a location’s bandwidth on the bandwidth you specify for its compute location.
- Follow the steps to Connect a Remote Network Site to Prisma Access (Cloud Management).
- Choose aPrisma Access Locationthat is close to the remote network location that you want to onboard.
- When creating the IPSec tunnel, use aBranch Device TypeofSilverPeak.
- SelectIPSec Advanced Optionsand select an IPSec Crypto Profile ofSilverPeak-IPSec-Crypto-Default.
- SelectIKE Advanced Optionsand select an IKEv1 Crypto Profile ofSilverPeak-IKE-Crypto-Default.
- Set up routing for the remote network.Set UpRouting andAddthe IP subnets for Static Routing.
- Push your configuration changes.
- Return toand selectManageService SetupRemote Networks.Push ConfigPush
- SelectRemote Networks.
- Pushyour changes.
- Make a note of theService IPaddress of the Prisma Access side of the tunnel. To find this address in Cloud Managed Prisma Access, select, click theManageService SetupRemote NetworksRemote Networks, and look for theService IPfield corresponding to the remote network configuration you created.
- From the Silver Peak orchestrator, create a tunnel configuration.
- SelectAdd Tunnel.
- Select aName,Local IP,Remote IP, andMode.
- In theAdvanced Optionsarea, enter the IKE and IPSec parameters.The parameters must be the same as the parameters that you specified on Prisma Access. Silver Peak recommends the following IKE and IPSec encryption settings:
- IKE encryption settings:
- IKE Lifetime—8 hours
- Dead Peer Detection—Delay time:300 secondsRetry:3
- IKE Identifier—IP address (leave blank - public IP is auto-detected)
- DH—Group 14
- IPSec encryption settings:
- Lifetime—60 minutes
- PFS—DH - Group 14
- Create two tunnels to Prisma Access: one Active and the other Backup.The following example creates two tunnels namedGlobalProtect-1andGlobalProtect-2.Specify the Prisma AccessService IPaddress in theRemote IPfield.Select theLocal IPaddress from the list of WAN interface IP addresses.
- Use the 3rd party IPSec tunnels in a Business Intent overlay policy by selectingBusiness Intent Overlayand configuring thePeer/Servicein thePoliciesarea.
- Order theGlobalProtect-1GlobalProtect-2service to thePreferred Policy Orderfield in the Internet Traffic area.Defining the order in thePreferred Policy Orderconfigures the GlobalProtect-1 tunnel to automatically fail over to the GlobalProtect-2 if the GlobalProtect-1 goes down. When both tunnels from the branch to GPCS are down, Silver Peak uses any other defined path such as local breakout or backhaul using the Overlay.
Support for Two Active-Active Connections
Two connections from a branch as active-active on Prisma Access are implemented as two separate remote network connections. You must onboard the connections in two separate locations using one of the following methods:
- Configure two separate remote networks in two different compute locations and specify subnets that overlap (overlapping subnets) for each remote network.
- Onboard both remote networks to the same compute location, making sure that the bandwidth for that compute location is sufficient to support two tunnels.The Silver Peak SD-WAN manually injects branch subnets into Prisma Access, but return traffic might not travel through the same tunnel if you use the same branch subnets for both tunnels. To avoid asymmetric traffic paths, configure different branch subnets for each primary tunnel.
- To load balance between the two tunnels, use identical names under Peer/Service. For example, if you use a Peer/Service nameGlobalProtectfor the tunnels PrismaAccess-1 and PrismaAccess-2, traffic will load balance between the two tunnels.The following figure shows the different branch subnets configured in Prisma Access for the load-balanced tunnels.The following figure shows Prisma Access in two locations in theRemote IParea and the peer service configured asGlobalProtectin thePeer/Servicearea.The following figure showsSend to GlobalProtectconfigured in thePreferred Policy Orderfield.
Recommended For You
Recommended videos not found.