NetApp AltaVault AVA400 - Page 237

NetApp AltaVault Cloud Integrated Storage Administration Guide 237
SNMP traps AltaVault appliance MIB
This table summarizes the SNMP traps sent out from the system to configured trap receivers and their effect on
AltaVault health state.
Trap and OID AltaVault
Appliance
State
Text Description
procCrash
(1.3.6.1.4.1.17163.1.102.4.0.1)
A procCrash trap signifies
that a process managed by
PM has crashed and left a
core file. The variable
sent with the notification
indicates which process
crashed.
A process has crashed and subsequently
been restarted by the system. The trap
contains the name of the process that
crashed. A system snapshot associated
with this crash has been created on the
appliance and is accessible via the CLI or
the Management Console. NetApp Support
might need this information to determine
the cause of the crash. No other action is
required on the appliance because the
crashed process is automatically restarted.
procExit
(1.3.6.1.4.1.17163.1.102.4.0.2)
A procExit trap signifies
that a process managed by
PM has exited
unexpectedly, but not left
a core file. The variable
sent with the notification
indicates which process
exited.
A process has unexpectedly exited and
been restarted by the system. The trap
contains the name of the process. The
process might have exited automatically or
due to other process failures on the
appliance. Review the release notes for
known issues related to this process exit. If
none exist, Contact NetApp Support to
determine the cause of this event. No other
action is required on the appliance because
the crashed process is automatically
restarted.
configChange
((1.3.6.1.4.1.17163.1.102.4.0.3)
A change has been made
to the system’s
configuration.
A configuration change has been detected.
View the log files around the time of this
trap to determine what changes were made
and whether they were authorized.
cpuUtil
(1.3.6.1.4.1.17163.1.102.4.0.4)
Degraded The average CPU
utilization in the past
minute has gone above
the acceptable threshold.
Average CPU utilization has exceeded an
acceptable threshold. If CPU utilization
spikes are frequent, it might be because the
system is undersized. Sustained CPU load
can be symptomatic of more serious issues.
Consult the CPU Utilization report to
gauge how long the system has been
loaded and also monitor the amount of
traffic currently going through the
appliance. A one-time spike in CPU is
normal but NetApp recommends reporting
extended high CPU utilization to NetApp
Support. No other action is necessary
because the alarm clears automatically.
pagingActivity
(1.3.6.1.4.1.17163.1.102.4.0.5)
Degraded The system has been
paging excessively
(thrashing).
The system is running low on memory and
has begun swapping memory pages to
disk. This event can be triggered during a
software upgrade while the storage
optimization service is still running, but
there can be other causes. If this event
triggers at any other time, generate a debug
sysdump report and send it to NetApp
Support. No other action is required
because the alarm clears automatically.