Prisma SD-WAN
Configure a Loopback Interface
Table of Contents
Expand All
|
Collapse All
Prisma SD-WAN Docs
-
-
- Prisma SD-WAN Key Elements
- Prisma SD-WAN Releases and Upgrades
- Use Copilot in Prisma SD-WAN
- Prisma SD-WAN Summary
- Prisma SD-WAN Application Insights
- Device Activity Charts
- Site Summary Dashboard
- Prisma SD-WAN Predictive Analytics Dashboard
- Prisma SD-WAN Link Quality Dashboard
- Prisma SD-WAN Subscription Usage
-
-
- Add a Branch
- Add a Data Center
- Add a Branch Gateway
- Secure Group Tags (SGT) Propagation
- 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 Secure SD-WAN Fabric Tunnels between Data Centers
- Configure Secure SD-WAN Fabric Tunnels between Branch Sites
- Configure a Site Prefix
- Configure Ciphers
- 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 Sub-Interface
- Configure a Loopback Interface
- Add and Configure Port Channel 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 an OSPF in Prisma SD-WAN
- Enable BGP for Private WAN and LAN
- Configure BGP Global Parameters
- Global or Local Scope for BGP Peers
- Configure a Route Map
- Configure a Prefix List
- Configure an AS Path List
- Configure an IP Community List
- View Routing Status and Statistics
- Distribution to Fabric
- Host Tracking
-
- Configure Multicast
- Create, Assign, and Configure a WAN Multicast Configuration Profile
- 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 Branch HA Key Concepts
-
- 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
- Configure HA Groups
- Add ION Devices to HA Groups
- Edit HA Groups and Group Membership
- Prisma SD-WAN Clarity Reports
-
-
CloudBlade Integrations
- CloudBlade Integrations
- CloudBlades Integration with Prisma Access
-
- Plan the Zscaler CloudBlade Deployment
- Acquire the Zscaler Information
- Create Security Zone and Security Policy for GRE Tunnels Creation
- Assign Tags to Objects in Prisma SD-WAN
- Validate the Zscaler Configuration
- Troubleshoot Installation Scenarios
- Troubleshoot Standard VPNs
- Enable, Pause, Disable, and Uninstall the CloudBlade
-
-
-
-
- clear app-engine
- clear app-map dynamic
- clear app-probe prefix
- clear connection
- clear device account-login
- clear dhcplease
- clear dhcprelay stat
- clear flow and clear flows
- clear flow-arp
- clear qos-bwc queue-snapshot
- clear routing
- clear routing multicast statistics
- clear routing ospf
- clear routing peer-ip
- clear switch mac-address-entries
- clear user-id agent statistics
-
- arping interface
- curl
- ping
- ping6
- debug bounce interface
- debug bw-test src-interface
- debug cellular stats
- debug controller reachability
- debug flow
- debug ipfix
- debug log agent eal file log
- debug logging facility
- debug logs dump
- debug logs follow
- debug logs tail
- debug performance-policy
- debug poe interface
- debug process
- debug reboot
- debug routing multicast log
- debug routing multicast pimd
- debug servicelink logging
- debug tcpproxy
- debug time sync
- dig dns
- dig6
- file export
- file remove
- file space available
- file tailf log
- file view log
- ssh6 interface
- ssh interface
- tcpdump
- tcpping
- traceroute
- traceroute6
-
- dump appaccel keys
- dump appaccel status
- dump appdef config
- dump appdef version
- dump app-engine
- dump app-l4-prefix table
- dump app-probe config
- dump app-probe flow
- dump app-probe prefix
- dump app-probe status
- dump auth config
- dump auth status
- dump banner config
- dump bfd status
- dump bypass-pair config
- dump cellular config
- dump cellular stats
- dump cellular status
- dump cgnxinfra status
- dump cgnxinfra status live
- dump cgnxinfra status store
- dump config network
- dump config security
- dump controller cipher
- dump controller status
- dump device accessconfig
- dump device conntrack count
- dump device date
- dump device info
- dump device status
- dump dhcp-relay config
- dump dhcprelay stat
- dump dhcp-server config
- dump dhcp-server status
- dump dhcpstat
- dump dnsservice config all
- dump dpdk cpu
- dump dpdk interface
- dump dpdk port status
- dump dpdk stats
- dump flow
- dump flow count-summary
- dump interface config
- dump interface status
- dump interface status interface details
- dump interface status interface module
- dump intra cluster tunnel
- dump ipfix config collector-contexts
- dump ipfix config derived-exporters
- dump ipfix config filter-contexts
- dump ipfix config ipfix-overrides
- dump ipfix config prefix-filters
- dump ipfix config profiles
- dump ipfix config templates
- dump lldp
- dump lldp config
- dump lldp info
- dump lldp stats
- dump lldp status
- dump log-agent eal conn
- dump log-agent eal response-time
- dump log-agent eal stats
- dump log-agent config
- dump log-agent iot snmp config
- dump log-agent iot snmp device discovery stats
- dump log-agent ip mac bindings
- dump log-agent neighbor discovery stats
- dump log-agent status
- dump ml7 mctd counters
- dump ml7 mctd session
- dump ml7 mctd version
- dump nat counters
- dump nat6 counters
- dump nat summary
- dump network-policy config policy-rules
- dump network-policy config policy-sets
- dump network-policy config policy-stacks
- dump network-policy config prefix-filters
- dump overview
- dump performance-policy config policy-rules
- dump performance-policy config policy-sets
- dump performance-policy config policy-set-stacks
- dump performance-policy config threshold-profile
- dump poe system config
- dump poe system status
- dump priority-policy config policy-rules
- dump priority-policy config policy-sets
- dump priority-policy config policy-stacks
- dump priority-policy config prefix-filters
- dump probe config
- dump probe profile
- dump radius config
- dump radius statistics
- dump radius status
- dump reachability-probe config
- dump qos-bwc config
- dump reachability-probe status
- dump routing aspath-list
- dump routing cache
- dump routing communitylist
- dump routing multicast config
- dump routing multicast igmp
- dump routing multicast interface
- dump routing multicast internal vif-entries
- dump routing multicast mroute
- dump routing multicast pim
- dump routing multicast sources
- dump routing multicast statistics
- dump routing multicast status
- dump routing ospf
- dump routing peer advertised routes
- dump routing peer config
- dump routing peer neighbor
- dump routing peer received-routes
- dump routing peer routes
- dump routing peer route-via
- dump routing peer status
- dump routing peer route-json
- dump routing prefixlist
- dump routing prefix-reachability
- dump routing route
- dump routing routemap
- dump routing running-config
- dump routing summary
- dump routing static-route reachability-status
- dump routing static-route config
- dump routing vpn host tracker
- dump security-policy config policy-rules
- dump security-policy config policy-set
- dump security-policy config policy-set-stack
- dump security-policy config prefix-filters
- dump security-policy config zones
- dump sensor type
- dump sensor type summary
- dump serviceendpoints
- dump servicelink summary
- dump servicelink stats
- dump servicelink status
- dump site config
- dump snmpagent config
- dump snmpagent status
- dump software status
- dump spoke-ha config
- dump spoke-ha status
- dump standingalarms
- dump static-arp config
- dump static host config
- dump static routes
- dump support details
- dump-support
- dump switch fdb vlan-id
- dump switch port status
- dump switch vlan-db
- dump syslog config
- dump syslog-rtr stats
- dump syslog status
- dump time config
- dump time log
- dump time status
- dump troubleshoot message
- dump user-id agent config
- dump user-id agent statistics
- dump user-id agent status
- dump user-id agent summary
- dump user-id groupidx
- dump user-id group-mapping
- dump user-id ip-user-mapping
- dump user-id statistics
- dump user-id status
- dump user-id summary
- dump user-id useridx
- dump vlan member
- dump vpn count
- dump vpn ka all
- dump vpn ka summary
- dump vpn ka VpnID
- dump vpn status
- dump vpn summary
- dump vrf
- dump waninterface config
- dump waninterface summary
-
- inspect app-flow-table
- inspect app-l4-prefix lookup
- inspect app-map
- inspect certificate
- inspect certificate device
- inspect cgnxinfra role
- inspect connection
- inspect dhcplease
- inspect dhcp6lease
- inspect dpdk ip-rules
- inspect dpdk vrf
- inspect fib
- inspect fib-leak
- inspect flow-arp
- inspect flow brief
- inspect flow-detail
- inspect flow internal
- inspect interface stats
- inspect ipfix exporter-stats
- inspect ipfix collector-stats
- inspect ipfix app-table
- inspect ipfix wan-path-info
- inspect ipfix interface-info
- inspect ip-rules
- inspect ipv6-rules
- inspect lqm stats
- inspect memory summary
- inspect network-policy conflicts
- inspect network-policy dropped
- inspect network-policy hits policy-rules
- inspect network-policy lookup
- inspect performance-policy fec status
- inspect performance-policy hits analytics
- inspect performance-policy incidents
- inspect performance-policy lookup
- inspect policy-manager status
- inspect policy-mix lookup-flow
- inspect priority-policy conflicts
- inspect priority-policy dropped
- inspect priority-policy hits default-rule-dscp
- inspect priority-policy hits policy-rules
- inspect priority-policy lookup
- inspect performance-policy incidents
- inspect performance-policy lookup
- inspect performance-policy hits analytics
- inspect process status
- inspect qos-bwc debug-state
- inspect qos-bwc queue-history
- inspect qos-bwc queue-snapshot
- inspect routing multicast fc site-iface
- inspect routing multicast interface
- inspect routing multicast mroute
- inspect security-policy lookup
- inspect security-policy size
- inspect servicelink conn
- inspect servicelink SA
- inspect switch mac-address-table
- inspect system arp
- inspect system ipv6-neighbor
- inspect system vrf
- inspect vpn status
- inspect vrf
- inspect wanpaths
-
-
5.6
- 5.6
- 6.1
- 6.2
- 6.3
- 6.4
- 6.5
- New Features Guide
- On-Premises Controller
- Prisma SD-WAN CloudBlades
- Prisma Access CloudBlade Cloud Managed
- Prisma Access CloudBlade Panorama Managed
-
- Features Introduced in Prisma SD-WAN ION Release 5.6
- Changes to Default Behavior in Prisma SD-WAN ION Release 5.6
- Upgrade ION 9000 Firmware for Device Version 5.6.x
- CLI Commands in Prisma SD-WAN ION Release 5.6
- Addressed Issues in Prisma SD-WAN ION Release 5.6
- Known Issues in Prisma SD-WAN ION Release 5.6
Configure a Loopback Interface
Let us learn to configure a loopback interface.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
Loopback is a logical, virtual interface used
to emulate a WAN port to provide LAN functionality. You can free up
a physical port previously used for LAN/WAN configuration by designating
a loopback interface. You can configure a maximum of four loopback
interfaces per device.
ION devices on versions 4.5.3 or
later at a site, support loopback interface. A loopback interface
can only be used as a WAN port on interfaces with no hardware bypass
circuitry. Interfaces with no hardware bypass circuitry per device
are as follows:
- ION 1000—All ports.
- ION 1200—All ports.
- ION 2000—Ports 1–3.
- ION 7000—Ports 1–4, 9–14.
- Virtual IONs—All non-controller ports.
A loopback
interface may be brought up or down administratively and may not
contain any sub-interfaces or IP configurations.
- You can update or delete a loopback interface. However, you cannot delete if it is part of a bypass pair.
- Decouple a port coupled with another port before a loopback interface can be coupled to create a bypass pair.
- The only valid option in the Use These Ports For drop-down is Private Layer 2 for a bypass pair that is made up of a physical LAN port and a loopback interface as the WAN port.
- The network policy rules assigned to such a site must not have any rules using the Direct on private WAN path. Valid paths are Direct on public or VPN on public. Traffic is dropped if a direct on private path is used.
Prisma SD-WAN supports layer 2 and layer 3 loopback interfaces:
- Configure a Layer 2 Loopback interface
- Configure a Layer 3 Loopback Interface
Configure a Layer 2 Loopback Interface
- Select WorkflowsDevicesClaimed Devices, select the device you want to configure.
- Select the Interfaces tab.
- On the interface configuration page for a device, click the + add icon to add a loopback interface and select Add.
- In the General section, select L2 as the Loopback Interface.
- Enter a Nameand Description.
- Next, select a port to be configured with a loopback interface.
- For Admin Up, select Yes or No to administratively bring the interface up or down. The default is Yes.
- From the Interface Type drop-down, select Bypass Pair.
- From the Pair With drop-down, select the Loopback Interface.A confirmation message displays.
- Select Done to create a bypass pair with the loopback interface successfully.A confirmation message displays the port's successful creation and the loopback interface.
- For Use These Ports For, select Private L2 from the drop-down.This is the only valid option for a bypass pair that is made of a physical LAN port and a loopback interface for the WAN port.
- Select the Circuit Label from the drop-down.
- Optional If you choose Copy Settings from Another Port, select the bypass pair to copy the settings. If not, you may leave it blank.
- Similar to configuring bypass pairs, for Attached Networks, enter a VLAN ID, IP Address at Router, optional Network Context, and toggle the scope tp Local or Global scope.
- Save Bypass Pair.The system assigns a default loopback ID to the interface. A confirmation message displays that the loopback interface is successfully created.The port and the loopback interface are displayed under Interfaces.
Configure a Layer 3 Loopback Interface
Prisma SD-WAN supports layer 3 capabilities on loopback interfaces
for SSH and Syslog services on branch and data center ION devices.
Prisma SD-WAN supports a maximum of 12 loopback
interfaces per ION device on all ION devices and virtual ION platforms.
L3 Loopback Interfaces for Management and Troubleshooting
Service Providers use L3 loopback interfaces on managed network devices
for troubleshooting tasks and management operations. As an example a loopback IP
interface can be used for SSH to the device or for Syslog services. An L3
loopback interface on the ION device allows management operations via the
overlay. As a result, you do not have to rely on LAN interfaces, which are part
of the infrastructure, or on WAN interfaces which involve using the underlay
leading to potential security considerations.

- The ION loopback interface is configured with the IP address 192.168.1.1/32.
- BGP sessions are running between ION eth1 and R1 and ION eth1 and R2. Both the BGP sessions advertise the loopback interface IP address to the routers R1 and R2.
- Users can configure the loopback interface as a source interface in services such as Syslog.
- The Syslog packet generated in the ION device will use the loopback IP address which will go out through eth1 to R1 and then to the Syslog server.
- Using a loopback interface masks the physical interface IP address and status.
Loopback Interface for establishing VPN Tunnels
You can establish Prisma SD-WAN tunnels using the loopback
interface when the MPLS WAN IP interfaces cannot be routed through the network.

In the example above, the Internet Service Provider (ISP) has provided an IP
address to an interface (the associate interface) and the Prisma SD-WAN VPN tunnel is formed over the loopback interface.
- You can configure an L3 Loopback interface with used for = public or private for branch ION devices, and used for = public and peer with network for data center ION devices.
- To associate the interface, see the steps for configuring a Layer 3 loopback interface.
- The VPN is formed over the loopback interface IP address.
- The peer should be able to reach the loopback IP address via the associated interface to form a VPN tunnel.
- You cannot use a loopback Interface to establish a Standard VPN tunnel.
Configure a Layer 3 Loopback Interface
- Select WorkflowsDevicesClaimed Devices, select the device you want to configure.
- Select the Interfaces tab.
- On the interface configuration page for a device, click the + add icon to add a loopback interface and select Add.
- In the General section, select L3 as the Loopback Interface.
- Enter a Name for the loopback interface.
- Optional Enter Description and Tags.
- For Admin Up, select Yes or No to administratively bring the interface up or down. The default is Yes.
- In Network Settings, select either Internet, Private WAN, or LAN for Use this port for.For Data Center ION devices, select Public as Use this port for.
- Attach a Circuit Label.
- For Associate Interface, enter the interface through which the loopback interface can send traffic.Note that:
- You can use a port or a sub-interface as an Associate interface.
- You can use an interface as an Associate Interface only if it does not have a circuit label already attached.
- Ensure that you advertise the loopback IP Address only on the Associate Interface.
- VPN tunnels will be established only over the Associate Interface on the underlay.
- If NAT is configured on the associated interface, the loopback IP address will be NATted to the associated interface IP address.
- Set Scope to Global for advertising the Loopback Interface IP address to BGP peers.When configured as global, the loopback prefix will be advertised to all BGP peers.
- For IP Address Mask, enter the /32 IP address.
- Loopback supports only the /32 subnet mask.
- Loopback does not support IPv6.
- Click Create loopback.
Advertise L3 Loopback IP Address to BGP Peers
- Advertise L3 Loopback IP address to BGP Peers for branch ION devices.
- Set Scope to Global for advertising the loopback interface prefix to BGP peers and to the fabric.Note that VPN tunnels will be established only over the Associate Interface on the underlay.
- Advertise L3 Loopback IP address to BGP Peers for data center ION devices.For Core, Edge, and Classic Peers
- Create a new route map based on default route map and attach the loopback IP prefix list.
- For edge peers, allow only the loopback IP prefix list.
- For core peers, allow the loopback IP prefix list along with the existing prefix list.
- For classic peers, advertisement happens by default if Scope is set to Global.