CPU utilization threshold alarm
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Affirmed Networks MIB copies (Observium Community)
OID reference
1.3.6.1.4.1.37963.7.3.1.16
CPU utilization threshold alarm
Identification
{1 3 6 1 4 1 37963 7 3 1 16}
The displayed source records contain one distinct definition. Compare its source records.
anSsfAlarmCpu NOTIFICATION-TYPE
OBJECTS {
affirmedSsfAlarmSeqId,
affirmedSsfAlarmDateTime,
affirmedSsfAlarmResource,
affirmedSsfAlarmSeverity,
affirmedSsfAlarmDetails
}
STATUS current
DESCRIPTION
"CPU utilization threshold alarm"
-- IMPACT
-- "CPU utilization threshold reached, please refer to the alarm details
-- string for specific reason. This alarm implies that average CPU usage on the SSF is
-- approaching certain threshold that requires attention. The severity of the alarm
-- can be minor, major, or critical depending on the percentage criteria defined in
-- /engineering/cpu. The alarm level evaluation is conducted every 1 minute.
-- When the usage percentage is increasing, the alarm onset value is used to
-- determine the severity level, and when the usage is decreasing, the abatement
-- value is used to determine the severity. The alarm is cleared when the usage
-- percentage falls below the minor abatement level."
--
-- REPAIR-ACTION
-- "Remedial actions for high CPU utilization may include: 1) scale-out the system
-- by adding another SSF instance, 2) scale-up the system by instantiating with
-- more virtual CPU (e.g. per Openstack Flavor), 3) adjust the configured alarm
-- thresholds to higher values. Please consult the deployment guide for recommended
-- system sizing. Other factors that can affect CPU utilization include number of
-- configured subscriber analyzers, type of EDR events enabled, and most importantly
-- the GTP traffic rate presented on the left side of the SSF. The current utilization
-- levels and quantity of cpu cores allocated can be checked with the command
-- 'show statistics platform resource'."
::= { affirmedSsfTraps 16}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
CPU utilization threshold alarm
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Affirmed Networks MIB copies (Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: anSsfAlarmCpu
{
"smi_kind": "NOTIFICATION-TYPE",
"definition": [
"anSsfAlarmCpu",
"NOTIFICATION-TYPE",
"OBJECTS",
"{",
"affirmedSsfAlarmSeqId",
",",
"affirmedSsfAlarmDateTime",
",",
"affirmedSsfAlarmResource",
",",
"affirmedSsfAlarmSeverity",
",",
"affirmedSsfAlarmDetails",
"}",
"STATUS",
"current",
"DESCRIPTION",
"\"CPU utilization threshold alarm\"",
"::=",
"{",
"affirmedSsfTraps",
"16",
"}"
],
"syntax_tree": [
[
"Objects",
[
"affirmedSsfAlarmSeqId",
"affirmedSsfAlarmDateTime",
"affirmedSsfAlarmResource",
"affirmedSsfAlarmSeverity",
"affirmedSsfAlarmDetails"
]
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"CPU utilization threshold alarm"
],
null
]
}Vendor MIB copy from the Observium Community archive. Affirmed Networks support.
Module: AFFIRMED-SSF-MIB
See published definition above
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'enterprises', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'ITU-ALARM-TC-MIB': ['ItuPerceivedSeverity']}Related source files and packages:
Vendor MIB copy from the Observium Community archive.
Module: AFFIRMED-SSF-MIB
{'SNMPv2-SMI': ['MODULE-IDENTITY', 'enterprises', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'ITU-ALARM-TC-MIB': ['ItuPerceivedSeverity']}Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.37963.7.3.1.1 | anSsfAlarmDnsServiceReachability | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.2 | anSsfAlarmGtpPathStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.3 | anSsfAlarmLdapPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.4 | anSsfAlarmNetworkKeepaliveStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.5 | anSsfAlarmLdapDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.6 | anSsfAlarmOperState | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.7 | anSsfAlarmRestPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.8 | anSsfAlarmRestDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.9 | anSsfAlarmPgwGxMapping | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.10 | anSsfAlarmDiameterPeerStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.11 | anSsfAlarmDiameterDbStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.12 | anSsfAlarmDnsNameError | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.13 | anSsfAlarmConfigSync | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.14 | anSsfAlarmLoginFailure | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.15 | anSsfAlarmFileSystem | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.17 | anSsfAlarmMemory | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.18 | anSsfAlarmNetworkNextHopStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.19 | anSsfAlarmNetworkStaticRouteStatus | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.20 | anSsfAlarmStatusSync | 0 | 0 | |
| 1.3.6.1.4.1.37963.7.3.1.21 | anSsfAlarmGatewaySnmpStatus | 0 | 0 |