PH_Rule_Avail_40
Enabled
Detects that a critical network interface of a network device is staying down - that is didn't come up within 5 minutes of going down. An interface is critical if it appears in Critical Interface list in GUI
9
Availability
Network
No Technique Specified
Network
Any Device via SNMP
Correlation
Identify the root cause and solve the issue
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
IntfDownNetDev NOT_FOLLOWED_BY IntfUpNetDev
This defines how two or more distinct events are related in a time-series based action. e.g. An event occurs followed by another event if the source IP, user, and messageId are the same
IntfDownNetDev.hostIpAddr = IntfUpNetDev.hostIpAddr AND IntfDownNetDev.intfName = IntfUpNetDev.intfName AND IntfDownNetDev.hostName = IntfUpNetDev.hostName
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType IN (Group@PH_SYS_EVENT_NetIntfShutdown) AND hostIpAddr IN (Group@PH_SYS_DEVICE_Network) AND isHostIntfCritical = "Yes"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostIpAddr,hostName, intfName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
Operator Rank: 0 Operator Type: NOT_FOLLOWED_BY
This operator defines the logic condition relating to the prior event subpattern clause and the following event subpattern clause
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType IN (Group@PH_SYS_EVENT_NetIntfRestart) AND hostIpAddr IN (Group@PH_SYS_DEVICE_Network) AND isHostIntfCritical = "Yes"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
hostIpAddr,hostName, intfName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
hostIpAddr = IntfDownNetDev.hostIpAddr,
hostName = IntfDownNetDev.hostName,
intfName = IntfDownNetDev.intfName