Prisma SD-WAN
Incident and Alert Event Categories
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
Incident and Alert Event Categories
Lets see all the incident and alert event categories in Prisma SD-WAN.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
Different types of events trigger alerts and incidents generated in the
system. These events are categorized broadly as hardware and software issues, device
related issues, peering issues, site level issues, tunnel issues, application
performance issues, and secure fabric link issues. Based on the type of event, these
issues may originate from the ION device or the controller.
Hardware and Software Issues
Hardware Issues—Hardware issues are raised by the device and deals
with device hardware issues.
- Power supply unit failure (Incident—warning).
- Memory DIMM failure (Incident—critical).
- Disk SMART threshold exceeding (Alert).
- Disk failure (IO error) (Incident—critical).
Software Issues—Software issues are raised by the device and deals with device
software issues. For example:
- Software module fails to start or restart (Incident).
- High CPU usage (Alert).
- High disk usage (Alert).
- Corrupt database (Incident).
Device Related Issues
Device level issues include offline devices or devices with missing or incorrect
interface configurations, missing or incorrect routing configuration, DHCP, port or NAT
configurations, or devices with offline status.
For example, when a device is in an offline state for an extended period of time, it
impacts the VPNs connected to other sites. For device-to-controller connectivity issues,
troubleshoot the device through the device toolkit, using utilities such as Ping and
Curl. You may also check device reachability issues using Ping or SSH.
Device Interface Issues—Interface issues are raised by the device and deals with
device interface issues. For example:
- Interface down (Incident—warning).
- Excessive errors on the interfaces (Alert).
Device Registration Issues—Registration issues are raised by the device or the
controller depending on the incident and deals with device registration issues. For
example:
- Failure to establish CIC channel with the controller (Incident—warning).
- Failure to retrieve inventory after repeated attempts (Incident—warning).
BGP Peering Issues
Routing level issues include routing protocol configurations issues, BGP neighbor
establishment issues, static routing or misconfigured static routes, or issues with
prefix learning or advertisement.
- For BGP session establishment related issues, check if there is an incorrect AS# or global parameters, an incorrect BGP peer IP, or check if BGP multi-hop is required.
- For BGP peer type issues (data center only), check if the right peer type is selected, core, edge, or classic peer type. The edge peer only learns prefixes.
- For static routing related issues, check the configuration for administrative distance, next hop (interface, IP, self), local or global scope to block or allow the advertisement into the Prisma SD-WAN fabric.
- For prefix learning and advertisement issues, check the route map configurations on Prisma SD-WAN and BGP peer devices, check for interactions with other routing protocols in the enterprise network, and check for split or no-split prefix scenarios.
This category of events deals with Border Gateway Protocol (BGP) peering issues in the
data center. For example:
- Peering with a WAN edge router is down (Incident—warning).
- Peering with a core router is down (Incident—warning).
- Routes learned from WAN edge indicate private WAN is down for a branch site (Incident —warning).
Site Level Issues
Site level issues may impact a single site or all sites. Select a site with an issue and
quickly isolate site, link, or circuit issues. You can also isolate the issues through a
quick view of incidents for a site.
Site related issues include overall quality of a link, VPNs down or VPNs configured for
another site, connectivity issues, circuit issues, incorrect circuit definitions or
inaccurate characteristics for a circuit, bandwidth issues, device assignment for a
site, or issues with prefixes at a site.
A few other site level issues include scenarios where none of the applications are
prioritized. If no applications are prioritized, check QoS, and then check if LQM is
enabled or disabled. If the flow browser indicates that traffic is bridged, despite a
configured port and an existing policy, then the issue could be the result of an
interface without a circuit label.
The device or the controller, depending on incident specifics, raise site level category
of incidents and deals with site level connectivity issues. For example:
- Direct Internet path unavailable at a branch site (Incident—warning).
- Private WAN path unavailable at a branch site (Incident—warning).
- All paths unavailable at a branch site (Incident—critical), raised by the controller.
- Loss of connectivity with the device/site (Incident—critical), raised by the controller.
- Path labels specified in policies not available/assigned for the site.
From Release 5.5.1, two new incidents are generated for site connectivity issues.
SITE_CONNECTIVITY_DOWN
When the site has lost connectivity with the controller and all of the remote branches or
data center, an incident is raised. The behavior is different for a branch and data
center.
- At a data center site, this incident is raised when all the network secure fabric links are down.
- At a branch site, this incident is raised when all network secure fabric links are down and all devices at the site are disconnected from the controller for more than 10 minutes.
The incident is cleared when connectivity is re-established or if at least one of the
VPNs is up.
SITE_CONNECTIVITY_DEGRADED
The controller raises this incident when any one of the below conditions exist:
- The Direct Internet or Direct Private WAN is down.
- At least one of the secure fabric links at the site is down.
- At least one of the service links is down.
This incident is cleared when all WAN paths are up.
Secure Fabric Link Issues
A secure fabric link is between a branch site and a data center or between two branch
sites. Palo Alto Networks enables virtual private network (VPN) overlays on all public
and private circuits between a branch site and a data center. VPN overlays between Palo
Alto Networks branch sites are disabled by default. You can selectively enable or
disable these VPNs on the Prisma SD-WAN web interface.
This category of events deals with virtual private network (VPN) link connectivity
issues. For example:
- Warning incident is raised when all the VPN links from an active branch site for a given secure fabric link is down (Incident—warning).
- Informational incident is raised if there are more than one VPN links from the active branch site for a given secure fabric link and at least one of the many links is up and at least one is down. (Incident—informational).
- The following VPN link related incidents are aggregated as secure fabric link incidents (Incident—warning when secure fabric link is down and informational when secure fabric link is degraded):
- NETWORK_VPNBFD_DOWN
- NETWORK_VPNLINK_DOWN
- NETWORK_VPNPEER_ UNAVAILABLE
- NETWORK_VPNPEER_ UNREACHABLE
- NETWORK_VPNSS_ UNAVAILABLE
- NETWORK_VPNSS_MISMATCH
The following incidents indicate the underlay network connectivity for a given circuit is
down:
- DEVICEHW_INTERFACE_DOWN
- NETWORK_DIRECTINTERNET_DOWN
- NETWORK_DIRECTPRIVATE_DOWN
Incidents raised for the corresponding secure fabric links that use the underlay
connectivity are suppressed.
When an administrator configures Admin Down for an interface, this
condition suppresses all the corresponding raised secure fabric link incidents and this
is displayed in the Reason field of the incident.
Service Endpoint Level Issues
Service endpoint level issues occur when a service link to a single endpoint goes down,
DEVICEHW_INTERFACE_DOWN incident is raised by an ION device. From Release 5.6.1, when a
DEVICEHW_INTERFACE_DOWN incident is raised by an ION device for at least two standard
VPN interfaces to the same service endpoint, the NETWORK_STANDARD_VPN_ENDPOINT_DOWN
summary incident is raised by the controller.
This incident is raised only when it is associated with
Endpoint destinations and not Peer
destinations.
The NETWORK_STANDARD_VPN_ENDPOINT_DOWN incident is not raised when:
- The parent interface is in Admin Down state.
- There exists a DEVICEHW_INTERFACE_DOWN incident on the parent interface.
- The incident won't be raised when the parent interface does not have a WAN label attached.
- The parent interface is in operationally down state.
- The device is disconnected from the controller.
- There exists a Layer 3 reachability issue on the parent interface.
The NETWORK_STANDARD_VPN_ENDPOINT_DOWN incident is cleared when there exists only one
standard VPN interface down incident and all other incidents are cleared.
Logical Interface Level Issues
The controller raises an incident when a parent interface is down and
suppresses the interface down incident raised by its logical interfaces.
The controller clears the incident only when the parent interface is up but
does not suppress the interface down incident if any one of the child interfaces is
down.