Configure Branch HA for Platforms without Bypass Pairs
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 for Platforms without Bypass Pairs
Learn how to configure branch HA for platforms without bypass pairs in
Prisma SD-WAN
.Where Can I Use
This? | What Do I
Need? |
---|---|
|
|
The example features two ION 1000 devices that do not natively provide
hardware bypass capabilities. To ensure high availability (HA), we opt to terminate
the circuits into both the ION devices. Although connecting these circuits via a
northbound switch is the most likely physical design, for the sake of simplicity, we
illustrate the circuits going directly into both devices. It's important to note
that this design is flexible and can be adapted to accommodate any model ION, not
solely limited to the ION 1000 platform. These ION devices represent a significant
leap in software-defined enterprise technology.
![](/content/dam/techdocs/en_US/dita/_graphics/uv/prisma/prisma-sd-wan/prisma-sd-wan-admin/branch-ha-no-bypass-northbound-switch.png)
The topology has the following features:
- Both the active and backup devices are connected to circuits, each necessitating its own unique IP address.
- The ION devices function in an active/backup configuration, but the WAN interfaces will consistently remain active, necessitating their own unique addressing.
- The devices establish a connection with the LAN switch through a trunk, facilitating both data connectivity and enabling High Availability (HA) via device heartbeat monitoring.
- 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. In contrast, 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-no-bypass-pairs-config.png)
- ConfigurePort 1as theinternetport on both the ION devices.The ION devices function in an active/backup configuration, but the WAN interfaces will consistently remain active, necessitating their own unique addressing.
- configurePort 2forPrivate WAN(MPLS) on both the ION devices.The ION devices function in an active/backup configuration, but the WAN interfaces will consistently remain active, necessitating their own unique addressing.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.
- Configure High Availability (HA) (Used-for-HA)interface.In this example, we are configuring a subinterface onas theport 3 with VLAN tag 130Used-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.
- In this example, we are configuring a subinterface onport 3 with VLAN tag 100for LAN connectivity to enable data exchange between the devices.You can use a single interface to 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 the hosts and network devices in the LAN.