Configure Branch HA with Gen-2 Platforms (3200, 5200, and 9200)
Table of Contents
Expand all | Collapse all
-
-
- Add a Branch
- Add a Data Center
- Add a Branch Gateway
- Configure Circuits
- Configure Internet Circuit Underlay Link Aggregation
- Configure Private WAN Underlay Link Quality Aggregation
- Configure Circuit Categories
- Configure Device Initiated Connections for Circuits
- Add Public IP LAN Address to Enterprise Prefixes
- Manage Data Center Clusters
- Configure a Site Prefix
- Configure a DHCP Server
- Configure NTP for Prisma SD-WAN
- Configure the ION Device at a Branch Site
- Configure the ION Device at a Data Center
- Switch a Site to Control Mode
- Allow IP Addresses in Firewall Configuration
-
- Configure a Controller Port
- Configure Internet Ports
- Configure WAN/LAN Ports
- Configure a Loopback Interface
- Configure a PoE Port
- Configure and Monitor LLDP Activity and Status
- Configure a PPPoE Interface
- Configure a Layer 3 LAN Interface
- Configure Application Reachability Probes
- Configure a Secondary IP Address
- Configure a Static ARP
- Configure a DHCP Relay
- Configure IP Directed Broadcast
- VPN Keep-Alives
-
- Configure Prisma SD-WAN IPFIX
- Configure IPFIX Profiles and Templates
- Configure and Attach a Collector Context to a Device Interface in IPFIX
- Configure and Attach a Filter Context to a Device Interface in IPFIX
- Configure Global and Local IPFIX Prefixes
- Flow Information Elements
- Options Information Elements
- Configure the DNS Service on the Prisma SD-WAN Interface
- Configure SNMP
-
-
- Prisma SD-WAN Branch Routing
- Prisma SD-WAN Data Center Routing
-
- Configure Multicast
- Create a WAN Multicast Configuration Profile
- Assign WAN Multicast Configuration Profiles to Branch Sites
- Configure a Multicast Source at a Branch Site
- Configure Global Multicast Parameters
- Configure a Multicast Static Rendezvous Point (RP)
- Learn Rendezvous Points (RPs) Dynamically
- View LAN Statistics for Multicast
- View WAN Statistics for Multicast
- View IGMP Membership
- View the Multicast Route Table
- View Multicast Flow Statistics
- View Routing Statistics
- Prisma SD-WAN Incident Policies
-
- Prisma SD-WAN Branch HA Key Concepts
- Configure Branch HA
- Configure HA Groups
- Add ION Devices to HA Groups
- View Device Configuration of HA Groups
- Edit HA Groups and Group Membership
-
- Configure Branch HA with Gen-1 Platforms (2000, 3000, 7000, and 9000)
- Configure Branch HA with Gen-2 Platforms (3200, 5200, and 9200)
- Configure Branch HA with Gen-2 Embedded Switch Platforms (1200-S or 3200-L2)
- Configure Branch HA for Devices with Software Cellular Bypass (1200-S-C-5G)
- Configure Branch HA for Platforms without Bypass Pairs
- Prisma SD-WAN Clarity Reports
- Prisma SD-WAN Incidents and Alerts
Configure Branch HA with Gen-2 Platforms (3200, 5200, and 9200)
Learn how to configure branch HA with Gen-2 platforms in
Prisma SD-WAN
.Where Can I Use
This? | What Do I
Need? |
---|---|
|
|
The example showcases two ION 5200 devices equipped with two pairs of
hardware bypass functionality. Furthermore, it accommodates the integration of 3200
models with one pair of hardware bypass, as well as 9200 models equipped with four
pairs of hardware bypass capability. These ION devices mark a significant
advancement in software-defined enterprise technology, leveraging software bypass to
enable elastic WAN network connectivity, enhancing both performance and
adaptability.
![](/content/dam/techdocs/en_US/dita/_graphics/uv/prisma/prisma-sd-wan/prisma-sd-wan-admin/branch-ha-gen2-topology-new.png)
The topology has the following features:
- The active device has two Internet connections.
- The backup device has one MPLS/Private connection.
- The ION devices operate in an active/backup configuration, and through fail-to-wire functionality, the active ION constantly maintains complete control and utilizes the full capacity of all the WAN circuits.
- The devices establish a connection through a trunk, facilitating both data connectivity and enabling High Availability (HA) via device heartbeat monitoring.The High Availability (HA) connection needs to be established with a south-bound switch, the devices cannot be directly connected to each other.
- The LAN addressing is identical on both devices, permitting only the active device to use Address Resolution Protocol (ARP) and communicate with hosts and network devices in the LAN.
- The High Availability (HA) addressing is unique, enabling the backup device to communicate with the controller through the active device for connectivity.
- Prisma SD-WANfacilitates the utilization of both the fabric overlay and the underlay (private MPLS). If you opt for the underlay, it's imperative to configure the necessary routing exchange between the ION device and the PE (peer edge) router.
![](/content/dam/techdocs/en_US/dita/_graphics/uv/prisma/prisma-sd-wan/prisma-sd-wan-admin/branch-ha-ion-5200-gen2-configuration.png)
- Create physical connections between the interfaces of the active and backup ION device.
- Connect Port 4 of ION 1 to Port 1 of ION 2. (Internet 1).
- Connect Port 4 of ION 2 to Port 1 of ION 1. (MPLS).
- Connect Port 6 of ION 1 to Port 3 of ION 2. (Internet 2).
This ensures that the Internet and MPLS circuits are available to both the ION devices. - Configure bypass pairs for each ION device.
- Between Ports 3 and 4 of the active ION device. (Port 3—WAN (Internet-1), Port 4—LAN)
- Between Ports 3 and 4 of the standby ION device. (Port 3—WAN (MPLS), Port 4—LAN)
- Between Ports 5 and 6 of the active ION device. (Port 5—WAN (Internet-2), Port 6—LAN)
Prisma SD-WANfacilitates the utilization of both the fabric overlay and the underlay (private MPLS). If you opt for the underlay, it's imperative to configure the necessary routing exchange between the ION device and the PE router. - In this example, we are configuring a subinterface onport 7 with VLAN tag 130as theUsed-for-HAinterface for heartbeat exchange between the devices.The interface designated for handling High Availability (HA) will be responsible for establishing connections between the devices and the controller. Consequently, it is crucial that these interfaces possess external reachability (direct or via overlay) and are configured with DNS servers capable of resolving public addresses.
- Configure an interface for LAN connectivity.In this example, we are configuringport 7 with VLAN tag 150for LAN connectivity to enable data exchange between devices.This can involve a single subinterface used as a transit to a layer 3 switch below, or alternatively, you can create multiple LAN subinterfaces and ports to communicate directly with different host subnets.If using a transit LAN to a layer 3 switch, you must also set up routing accordingly.The LAN addressing is identical on both devices, permitting only the active device to use Address Resolution Protocol (ARP) and communicate with hosts and network devices below.