Bypass Pair
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
Bypass Pair
Let us learn about bypass pairs.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
|
A Bypass Pair is a pair of ports where
one port is connected to a LAN network while the second port is
connected to a WAN network. Bypass pairs can be configured only
for branch ION devices.
Bypass pairs can be of the following types:
- Hardware Bypass Pair—A pair of ports or ethernet interfaces that can be associated with each other with underlying support for a hardware bypass relay. Hardware Bypass Pairs have strict pairing rules where only certain ports can be paired together.
- Virtual Bypass Pair—A pair of ports or ethernet interfaces that can be associated with each other without any hardware capabilities. A Virtual Interface (VI) cannot be created on a virtual bypass pair.
Both types of bypass pairs are not allowed on controller interfaces
or interfaces that are part of another logical interface. You can break
a bypass pair into two individual ports and use the individual ports
for configuring sub-interfaces.
Bypass pairs can be configured as per the following:
- Used for - Internet, Private WAN—One interface of the bypass pair is private WAN facing and can be assigned either a static or dynamic IP address. The other interface of the pair is connected to a LAN network.
- Used for - Private L2—One interface of the bypass pair is private WAN facing and connects to one or more routers - Core Edge or Peer Edge, and is capable of acting as an Layer 2 interface only. The other interface of the pair is connected to a LAN network. Static or dynamic IP addresses cannot be assigned to this bypass pair.
- Used for - LAN—The interface is LAN facing and can be connected only to a LAN network. A static or dynamic IP address can be assigned to this interface. The WAN part of the bypass pair is not used. This topology is used for configuring the branch ION device in a cluster for high availability.