Configure Device Initiated Connections for Circuits
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 Device Initiated Connections for Circuits
ION devices can connect to the controller for various services such as MRL service,
statistics, flows, logs, and remote access of device toolkit.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
Prisma SD-WAN ION devices initiate multiple
connections to the controller for various services such as Message
Routing Layer (MRL) service, statistics, flows, logs, and remote
access of device toolkit. For services connecting to the controller
using random paths or interfaces, you can exclude certain interfaces
or paths from being used for these services. For example, an expensive
metered LTE circuit is used as a last resort interface to maintain
connectivity to the controller.
In addition, ION devices
generate application reachability probes when an application or
prefix is unreachable for a particular path. However, if a particular
circuit is to be used as a path of last resort only, then the amount
of non end-user traffic going over that specific circuit should
be minimized. You can exclude certain circuits and circuit categories
from being used for device initiated connections by using the Use for controller
connections and Use for application
probes options.
You can prioritize ION device interfaces
use for device initiated connections in the order of first controller
port interface, LAN port, any interface which does not have a label
attached, but has an IP address, and then interfaces with circuit
labels attached. The order of preference is based on the cost of
a circuit. A circuit with a higher cost has a lower preference for
device to controller connections.
- Select WorkflowsSites/Data CentersConfiguration.Click Change Circuits for either Internet Circuits or Private WAN Circuits.Click Edit below the circuit name.On the Circuit Information screen, select Yes for Controller Connections, only if using the circuit for connecting to the controller for device related services.Select No, if this circuit is to be excluded from connecting to the controller for device related services such as metered LTE circuits.Select Use Circuit Category Setting for selecting the configuration from the Circuit Category.Select Yes for App Reachability Probes, only if using the circuit for checking the reachability of an application for a given path.Select No, if this circuit is to be excluded from checking the reachability of an application for a given path such as metered LTE circuits. Select Use Circuit Category Setting for selecting the configuration from the Circuit Category.Click Done.A DEVICESW_INITIATED_CONNECTION_ON_EXCLUDED_PATH alarm is generated when a device initiated controller connection is established using an excluded interface or path. The lack of an available interface or path has forced the connection on an excluded path or interface as a last resort.