Configure Branch HA in a Hybrid Topology with Gen-1 (3000) and Gen-2 (3200) Platforms
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
- Configure Branch HA in a Hybrid Topology with Gen-1 (3000) and Gen-2 (3200) Platforms
- Prisma SD-WAN Incidents and Alerts
Configure Branch HA in a Hybrid Topology with Gen-1 (3000) and Gen-2 (3200) Platforms
Learn how to configure branch HA in a hybrid topology with Gen-1 and Gen-2 platforms in
Prisma SD-WAN.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
The example showcases an ION 3000 device and an ION 3200 device connected in an HA configuration
equipped with a single pair of hardware bypass functionality.
The topology has the following features:
- The active device has one Internet connection.
- 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 controller interface serves the purpose of monitoring device heartbeats. To achieve this, it's essential to establish a connection with a southbound switch.
- 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.
- The Controller addressing is unique, enabling the backup device to communicate with the controller through the active device for connectivity.
- Prisma SD-WAN facilitates 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.
In this topology, we consider ION 3000 to be the active device and ION 3200
to be the backup device.
- Create physical connections between the interfaces of the active and backup ION device.
- Connect ION 1 Internet Bypass Port 2 to Port 1 of ION 2. (Internet)Connect Port 4 of ION 2 to Internet Port 1 of ION 1. (MPLS)This ensures that the Internet and MPLS circuits are available to both the ION devices.Configure bypass pairs for each ION device.Creating a bypass pair will disrupt the interface's connectivity. Ensure that you have an alternative connection to the cloud controller before proceeding with this configuration.
- Between Internet Port 2 and Internet Bypass 2 of the active ION device.(Port Internet 2 - WAN (Internet), Port Internet Bypass 2 - LAN)
- Between Ports 3 and 4 of the standby ION device.(Port 3 - WAN (MPLS), Port 4 - LAN)
Prisma SD-WAN facilitates 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 the controller interface.- Configure Controller 1 of ION 1 (ION 3000).Configure Port 5 as the controller for ION 2 (ION 3200).The controller interface, used for handling High Availability (HA), is 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 configuring Port LAN 1 (ION 1) and Port 7 (ION 2) to enable data exchange.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.