Prisma SD-WAN
Event Category-Network
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 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
-
-
-
-
- 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 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 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 switch mac-address-table
- inspect system arp
- inspect system ipv6-neighbor
- inspect system vrf
- 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
Event Category-Network
Incident and alert event codes based on the categories for troubleshooting in Prisma
SD-WAN. Learn about the event codes generated due to network-related events in Prisma SD-WAN.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
In Prisma SD-WAN, different types of events trigger alerts and incidents.
Prisma SD-WAN generates alerts and incidents on reaching
system-defined thresholds or if there is a fault in the system.
A network-related event that can trigger either an incident or an alert can be due to
issues related to site connectivity, secure fabric
links, service endpoints, or logical interfaces.
The following tables describe a list of event or incident codes, the event
origin, its severity, and a description of each event as per the event category.
For each incident raised on the web interface, you can troubleshoot the issue. If the issue persists,
select Go to Support to create a support ticket. A Palo Alto
Networks Support executive will contact you. You can also return the device to Palo Alto Networks.
INCIDENT CODE | EVENT ORIGIN | INCIDENT /ALERT | SEVERITY | EVENT TITLE | EVENT DESCRIPTION | RELEASE INTRODUCED |
---|---|---|---|---|---|---|
BRANCH_
GATEWAY
CLUSTER_SITE
COUNT_
THRESHOLD
_EXCEEDED
| Controller | Incident | Major | Spoke sites limit exceeded on Branch Gateway cluster | The maximum number of branch sites that can be associated with a Branch Gateway site has been exceeded. | 6.4.1 |
DEVICESW_
INITIATED_
CONNECTION
_ON_
EXCLUDED_
PATH
| Device | INCIDENT | Warning | Device Initiated Connection on excluded path. | Device Initiated Connection on excluded interface. | 5.4.3 |
HUB_CLUSTER
_SITE_COUNT_
THRESHIOLD_
EXCEEDED
| Controller | INCIDENT | Warning | Hub Cluster Branch Count Limit Exceeded | The maximum number of branches allowed on hub cluster have been exceeded. | 6.1.1 |
NETWORK_
SECUREFABRICLINK
_DEGRADED
| Controller | INCIDENT | Informational | Secure Fabric Link is degraded with atleast 1 VPN link UP from the active spoke and 1 or more VPN links DOWN from the active SPOKE. | Secure Fabric Link is degraded with atleast 1 VPN link up
from the active spoke and 1 or more VPN links down from the active
spoke. The incident also displays the reasons for the VPN failure and
the root cause incidents found. Following the controller upgrade to
5.4.1 there will be immediate changes to incidents, including
standing VPN related incidents that will no longer be visible, by
default. If you interact with the events API programmatically, you
must modify the scripts because the VPN incidents are replaced with
a new incident category. When querying for events using the API,
replace the code for NETWORK_ SECUREFABRICLINK_ DEGRADED
with NETWORK_ ANYNETLINK_ DEGRADED. Click
API Changes for Network Secure Fabric Link Event Codes to know more about
the API changes. | 5.4.1 |
NETWORK_
SECUREFABRICLINK
_DOWN
| Controller | INCIDENT | Warning | Secure Fabric Link is down with all VPN Links DOWN from the active spoke. | Secure Fabric Link is down with all VPN links down from
the active spoke. The incident also displays the reasons for the VPN
failure and the root cause incidents found. Following the controller
upgrade to 5.4.1 there will be immediate changes to incidents,
including standing VPN related incidents that will no longer be
visible, by default. If you interact with the events API
programmatically, you must modify the scripts because the VPN
incidents are replaced with a new incident category. When querying
for events using the API, replace the code for
NETWORK_ SECUREFABRICLINK _DOWN with
NETWORK_ ANYNETLINK _DOWN. Click API Changes for Network Secure Fabric Link Event Codes to know more about
the API changes. | 5.4.1 |
NETWORK_
DIRECTINTERNET
_DOWN
| Device | INCIDENT | Warning | Direct Internet Reachability Down. | For remote office or branch sites, reachability on an
internet circuit is down. If there are no alternate paths in application
policy, the incident indicates that traffic is impacted and must be
attended to immediately. Release 5.4.1 and later When
NETWORK_ DIRECTINTERNET _DOWN incident is raised,
it also shows related faults. These faults are caused due to this
incident which can be
NETWORK_ SECUREFABRICLINK _DEGRADED or
NETWORK_ SECUREFABRICLINK _DOWN . | 4.5.1 |
NETWORK_
DIRECTPRIVATE
_DOWN
| Device | INCIDENT | Warning | Private WAN Reachability Down. | For remote office or branch sites, all data center sites
with the ION 7000 deployed are unreachable on the private WAN. If there
are no alternate paths configured in application policy, the incident
indicates that traffic is impacted and must be attended to immediately.
Release 5.4.1 and later When
NETWORK_ DIRECTINTERNET _DOWN incident is raised,
it also shows related faults. These faults are caused due to this
incident which can
beNETWORK_ SECUREFABRICLINK _DEGRADED or
NETWORK_ SECUREFABRICLINK _DOWN . | 4.5.1 |
NETWORK_
PRIVATEWAN_
DEGRADED
| Device | INCIDENT | Warning | Private WAN Degraded. | For data center sites, a subset of IP prefixes from one or more remote sites are determined to be unreachable over the private WAN based on routing updates received from the network. | 4.5.1 |
NETWORK_
PRIVATEWAN_
UNREACHABLE
| Device | INCIDENT | Warning | Private WAN Unreachable. | For data center sites, one or more remote offices
declared unreachable over the private WAN based on routing updates
received from the network. If this incident occurred due to WAN edge
peering failure PEERING _EDGE_ DOWN incident(s) is
also raised. | 4.5.1 |
PEERING
_BGP_
DOWN
| Device | INCIDENT | Critical | BGP Peer Down. | Routing peer session is down. If alternate paths are available traffic is not affected; else the fault is critical. | 5.0.3 |
NETWORK_
STANDARD_
VPN_
ENDPOINT
_DOWN
| Controller | INCIDENT | Warning | Standard VPN Endpoint Down. | Multiple service link interfaces connecting to a service endpoint are down. | 5.6.1 |
NETWORK_
VPNKEK_
UNAVAILABLE
| Device | INCIDENT | Informational | Key Encryption Key(KEK) is not available | This fault is generated when Key Encryption Key(KEK) required to decrypt shared secrets for VPN Link is not available. The controller issues a KEK along with shared secrets. If the communication between the controller and the device is down for 3 days or more, then this can happen. | 6.2.1 |
NETWORK_
VPNKEK_
UNAVAILABLE
| Device | INCIDENT | Informational | Key Encryption Key (KEK) is not available. | This fault is generated when Key Encryption Key (KEK) required to decrypt shared secrets for VPN link is not available. The controller issues a KEK along with shared secrets. If the communication between the controller and the device is down for more than three days, this can happen. | |
NETWORK_
VPNLINK_
DOWN
| Device | INCIDENT | Warning | VPN Link Down | A VPN Link connecting two sites is down. If the VPN Link is the only link between the two sites, VPN based connectivity between those sites has been impacted. If alternate VPN Links exist between the two sites, connectivity and capacity is available between the sites; however additional VPN Link failures between the two sites may impact traffic. | |
NETWORK_
VPNPEER_
UNAVAILABLE
| Device | INCIDENT | Informational | VPN Peer Down | A peer instance on other side of a VPN Link of a remote
office (branch) has been declared to be down. This fault will typically
be seen along with one of [NETWORK_ VPNLINK _DOWN,
PEERING_ CORE_ DOWN,
DEVICESW_ GENERAL_ PROCESSSTOP] faults that
identify the likely root cause. | |
NETWORK_
VPNSS_
UNAVAILABLE
| Device | INCIDENT | Informational | VPN Shared Secret Unavailable | Shared secret required to establish a VPN Link is not available. The Prisma SD-WAN controller pre-issues a certain number of shared secrets (3 days worth by default). If the communication between the Prisma SD-WAN Controller and the device is down for 3 days or more, then this fault is raised. | |
NETWORK_
VPNPEER_
UNREACHABLE
| Device | INCIDENT | Informational | VPN Peer Unreachable | Control communication could not be established with the VPN Peer. Common reasons include (a) IP Address mis-configuration, (b) NAT misconfiguration or (c) a firewall which is blocking port 4500 traffic as UDP port 4500 is used for control communication between the two VPN Peers. | |
NETWORK_
VPNSS_
MISMATCH
| Device | INCIDENT | Informational | VPN Shared Secret Mismatch | VPN Peers could not agree on a shared secret. Usually happens when (a) one of the devices is not able to contact the Prisma SD-WAN Controller and retrieve the shared secret corresponding to the time window when the fault was raised or (b) the clocks on the VPN Peer devices are out of sync. | |
NETWORK
VPNBFD_
DOWN
| Device | INCIDENT | Informational | VPN Liveliness Down | VPN Link liveliness is monitored through BFD heartbeats. This fault indicates that the VPN Link went down because the BFD heartbeats failed. If this is a temporary network failure then the VPN Link will come back up once the network is restored. If the fault continues to stay on then check for network availability. | |
SITE_
CONNECTIVITY_
DOWN
| Controller | INCIDENT | Critical | Site Connectivity Down | At the Branch, incident is raised when the site cannot
connect to controller or any remote branch or data center. Suppressed
Incidents at the Branch site:
DEVICESW_ DISCONNECTED _FROM_ CONTROLLER NETWORK_ SECUREFABRICLINK _DOWN
The following incidents are suppressed only if they were received by the
controller before the site connectivity was lost:
DEVICEHW_ INTERFACE _DOWN NETWORK_ DIRECTINTERNET _DOWN NETWORK_ DIRECTPRIVATE _DOWN
At the Data Center, incident is raised when all the remote sites are
unreachable. Suppressed Incidents at the Data Center site:
DEVICESW_ DISCONNECTED _FROM_ CONTROLLER NETWORK_ SECUREFABRICLINK _DOWN | 5.5.1 |
SITE_
CIRCUIT_
ABSENT_
FOR_POLICY
| Controller | INCIDENT | Warning | Path label used in policy is missing on site. | One or more path labels (public-*, private-*, public-[1-32], private-[1-32]) used in policy not assigned to any site WAN interface at the site. | 4.5.1 |
SITE_
NETWORK_
SERVICE
_ABSENT_
FOR_POLICY
| Controller | INCIDENT | Warning | Policy DC Group Missing Service Endpoint. | One or more DC groups used in the policy has not been assigned a valid service endpoint for the domain bound to the identified site. | 5.4.1 |
SITE_
CONNECTIVITY_
DEGRADED
| Controller | INCIDENT | Warning | Site connectivity degraded | Branch site connectivity is degraded due to one or more secure fabric links down, Layer 3 reachability is down or service link is down. Suppressed Incidents: NETWORK_DIRECTINTERNET_DOWNNETWORK_DIRECTPRIVATE_DOWNNETWORK_SECUREFABRICLINK_DOWNNETWORK_SECUREFABRICLINK_DEGRADEDDEVICEHW_INTERFACE_DOWN | 5.5.1 |
SASE_
SERVICEEND
POINT_
BANDWIDTH_
LIMIT_
EXCEEDED
| Controller | INCIDENT | Warning | Configured circuit bandwidth for sites exceeds allocated bandwidth for region. | 6.0.1 | |
SASE_
SERVICEEND
POINT_
BANDWIDTH_
SOFT_LIMIT_
EXCEEDED
| Controller | INCIDENT | Informational | Total estimated bandwidth for sites exceeds allocated bandwidth for the region. | 6.0.1 | |
VION_
BANDWIDTH_
LIMIT_
EXCEEDED
| Controller | INCIDENT | Warning | Configured circuit bandwidth for sites exceeds maximum capacity of the virtual ION. | 6.0.1 | |
VION_
BANDWIDTH_
SOFT_LIMIT_
EXCEEDED
| Controller | INCIDENT | Informational | Total estimated bandwidth for sites exceeds maximum capacity of the virtual ION. | 6.0.1 | |
SPN_
BANDWIDTH_
LIMIT_
EXCEEDED
| Controller | INCIDENT | Warning | Configured circuit bandwidth for sites exceeds maximum capacity of the security service endpoint connected to virtual ION. | 6.0.1 | |
SPN_
BANDWIDTH_
SOFT_LIMIT_
EXCEEDED
| Controller | INCIDENT | Informational | Total estimated bandwidth for sites exceeds maximum capacity of the security service endpoint connected to virtual ION. | 6.0.1 |