in a carrier that contains
more than one disk are failed by
Data ONTAP(R) and the carrier can be removed.
shelfFault
.1.3.6.1.4.1.789.0.103
rage shelf reported a fault, probably due
to a problem with drive placement, fans, power,
or temperature.
sasConnectorWarn
.1.3.6.1.4.1.789.0.1045
nnecting a SAS device to a disk shelf
has been removed or failed.
sasConnectorInfo
.1.3.6.1.4.1.789.0.1047
ly-existing error condition involving a SAS cable
has been corrected.
shelfWarning
.1.3.6.1.4.1.789.0.105
rage shelf reported a warning, probably due
to a problem with drive placement, fans, power,
or temperature.
sesShelfPowerSupplyError
.1.3.6.1.4.1.789.0.1054
A shelf power supply has failed or been removed.
sesShelfPowerSupplyWarn
.1.3.6.1.4.1.789.0.1055
A shelf power supply has indicated a warning condition.
sesShelfPowerSupplyInfo
.1.3.6.1.4.1.789.0.1057
ly reported error or warning condition
involving a shelf power supply has been corrected.
shelfRepaired
.1.3.6.1.4.1.789.0.106
A previously-reported shelf fault is now corrected.
volRehostFailed
.1.3.6.1.4.1.789.0.1064
ehost attempt has failed. The volume is available
under source Vserver.
sesShelfVoltageWarning
.1.3.6.1.4.1.789.0.1065
ge occurs when a warning condition is
detected in the indicated disk shelf voltage sensor.
The shelf might be able to continue operation.
volRehostSucceeded
.1.3.6.1.4.1.789.0.1067
A volume rehost attempt is successful.
offboxvscanVirusDetectedError
.1.3.6.1.4.1.789.0.1072
VScan: A possible virus has been detected
emergencyTrap
.1.3.6.1.4.1.789.0.11
ined trap indicating an extremely urgent
situation, usually indicating that the system has
failed and is shutting down.
snmpTestTraphost
.1.3.6.1.4.1.789.0.1103
SNMP test trap is generated.
globalStatusNonRecoverable
.1.3.6.1.4.1.789.0.111
nce's overall status changed to
'nonRecoverable', indicating a problem so severe
that the appliance is shutting down.
snmpFipsSupport
.1.3.6.1.4.1.789.0.1114
is operating in FIPS compliant mode but
SNMPv3 is configured with non-compliant ciphers or hash algorithms.
Hence SNMPv3 is disabled.
noNisServersAvailable
.1.3.6.1.4.1.789.0.1121
e configured NIS servers are
reachable at this point of time. The string
sent with the trap gives the name of the
affected Storage Virtual Machine.
globalStatusCritical
.1.3.6.1.4.1.789.0.113
nce's overall status changed to 'critical',
indicating a problem that needs immediate attention.
noLdapServersAvailable
.1.3.6.1.4.1.789.0.1131
e configured LDAP servers are
reachable at this point of time. The string
sent with the trap gives the name of the
affected Storage Virtual Machine.
noLsaServersAvailable
.1.3.6.1.4.1.789.0.1141
e configured LSA servers are
reachable at this point of time. The string
sent with the trap gives the name of the
affected Storage Virtual Machine.
globalStatusNonCritical
.1.3.6.1.4.1.789.0.115
nce's overall status changed to 'nonCritical',
indicating a problem that needs attention.
noNetlogonServersAvailable
.1.3.6.1.4.1.789.0.1151
e configured Netlogon servers are
reachable at this point of time. The string
sent with the trap gives the name of the
affected Storage Virtual Machine.
globalStatusOk
.1.3.6.1.4.1.789.0.116
The appliance's overall status returned to normal.
sesShelfDcmError
.1.3.6.1.4.1.789.0.1164
A shelf dcm is not installed or not supported.
sesShelfDcmWarn
.1.3.6.1.4.1.789.0.1165
A shelf dcm has indicated a warning condition.
sesShelfDcmInfo
.1.3.6.1.4.1.789.0.1167
ly reported error or warning condition
involving a shelf dcm has been corrected.
snmpSnmpv3Enable
.1.3.6.1.4.1.789.0.1194
ge occurs when SNMPv3 is disabled due to a cluster in FIPS
mode being upgraded to a version of ONTAP(R) software supporting the
SNMPv3 FIPS feature. FIPS compliance adds more stringent limitations
on SNMP users and SNMP traphosts, so SNMPv3 access has been disabled
to allow the current SNMP users and SNMP traphosts to be reevaluated.
If SNMPv3 functionality is required, you can reenable it; if cluster
is still in FIPS mode at that time, any existing SNMP users and SNMP
traphosts that are noncompliant to FIPS will be deleted. Until SNMPv3
is reenabled, SNMPv3 users cannot be created, SNMPv3 traphosts cannot
be added and SNMPv3 packets will not be processed.
alertTrap
.1.3.6.1.4.1.789.0.12
ined trap indicating a condition that
should be corrected immediately, such as a failed disk.
snmpFipsObjsDelFailed
.1.3.6.1.4.1.789.0.1204
failed to delete SNMP traphosts and users that were not
FIPS compliant. It tried to automatically delete them when FIPS was
configured in the cluster. The SNMP traphosts and users that are
left have become inoperable.
fcBridgeTempEmergency
.1.3.6.1.4.1.789.0.1211
SAS bridge has reached the critical temperature
threshold, and will shut down.
fcBridgeTempAlert
.1.3.6.1.4.1.789.0.1212
SAS bridge is operating at elevated temperature
levels and action should be taken to restore proper cooling.
fcBridgeTempNotice
.1.3.6.1.4.1.789.0.1216
The FC-to-SAS bridge has returned to normal operating temperature.
fcBridgeFcPortAlert
.1.3.6.1.4.1.789.0.1222
This message occurs when an FC port has gone offline.
fcBridgeFcPortNotice
.1.3.6.1.4.1.789.0.1226
This message occurs when an FC port has come back online
fcBridgeSASPortAlert
.1.3.6.1.4.1.789.0.1232
This message occurs when a SAS port has gone offline.
fcBridgeSASPortNotice
.1.3.6.1.4.1.789.0.1236
This message occurs when a SAS port has come back online
fcBridgeThroughputAlert
.1.3.6.1.4.1.789.0.1242
ge occurs when an FC-to-SAS bridge is experiencing
degraded throughput.
fcBridgeThroughputNotice
.1.3.6.1.4.1.789.0.1246
ge occurs when an FC-to-SAS bridge has recovered from
degraded throughput.
fcBridgePowerSupplyAlert
.1.3.6.1.4.1.789.0.1252
This message occurs when an FC-to-SAS bridge power supply has failed.
fcBridgePowerSupplyNotice
.1.3.6.1.4.1.789.0.1256
ge occurs when an FC-to-SAS bridge power supply has returned to
normal operation.
softQuotaExceeded
.1.3.6.1.4.1.789.0.126
A user has exceeded their soft quota limit.
fcBridgeSasPhyTransitionAlert
.1.3.6.1.4.1.789.0.1262
ge occurs when a SAS port on a bridge has transitioned
to offline.
fcBridgeSasPhyTransitionNotice
.1.3.6.1.4.1.789.0.1266
ge occurs when a SAS port on a bridge has transitioned
to online.
softQuotaNormal
.1.3.6.1.4.1.789.0.127
A user is safely back under their soft quota limit.
criticalTrap
.1.3.6.1.4.1.789.0.13
ined trap indicating a critical condition,
such as a hard device error.
vsaCloudProviderScheduledEventScheduled
.1.3.6.1.4.1.789.0.1302
ge occurs when a cloud-provider maintenance event has
been initially scheduled.
vsaCloudProviderScheduledEventUpdate
.1.3.6.1.4.1.789.0.1303
ge occurs when the status of a previously scheduled
cloud-provider maintenance event has been updated.
autosupportSendError
.1.3.6.1.4.1.789.0.134
send auto support.
The trap includes a string describing the reason for the failure.
autosupportConfigurationError
.1.3.6.1.4.1.789.0.135
rt may be configured incorrectly.
The trap includes a string describing the mis-configuration.
autosupportSent
.1.3.6.1.4.1.789.0.136
Auto support was sent successfully.
errorTrap
.1.3.6.1.4.1.789.0.14
ined trap indicating an error condition,
such as a mistake in a configuration file.
upsLinePowerOff
.1.3.6.1.4.1.789.0.142
UPS: Input line power has failed and UPS is now on battery.
upsBatteryCritical
.1.3.6.1.4.1.789.0.143
UPS: Battery is nearly exhausted, starting graceful shutdown.
upsShuttingDown
.1.3.6.1.4.1.789.0.144
UPS: Shutting down now: Time left on battery is exhausted.
upsBatteryWarning
.1.3.6.1.4.1.789.0.145
UPS: Warning: Time left on battery is getting critical.
upsLinePowerRestored
.1.3.6.1.4.1.789.0.146
UPS: Input line power has been restored and UPS is now off battery.
warningTrap
.1.3.6.1.4.1.789.0.15
ined trap indicating a condition which
is not an error, but which may require special handling.
appEmergency
.1.3.6.1.4.1.789.0.151
ation encountered an extremely urgent
situation and requires an immediate response.
appAlert
.1.3.6.1.4.1.789.0.152
ation is in a condition that should
be corrected immediately.
appCritical
.1.3.6.1.4.1.789.0.153
The application encountered a critical condition.
appError
.1.3.6.1.4.1.789.0.154
The application encountered an error condition.
appWarning
.1.3.6.1.4.1.789.0.155
ation is in a condition which is not an
error, but which may require special handling.
appNotice
.1.3.6.1.4.1.789.0.156
The application is notifying of a certain event.
appInfo
.1.3.6.1.4.1.789.0.157
ation's message is meant for informational
purposes.
appTrap
.1.3.6.1.4.1.789.0.158
The application requires to be debugged.
notificationTrap
.1.3.6.1.4.1.789.0.16
ined trap meant to provide notification,
such as an hourly uptime message.
alfFilewrap
.1.3.6.1.4.1.789.0.162
al audit file has wrapped. You are currently losing event
records. Warning the user.
alfFileSaved
.1.3.6.1.4.1.789.0.166
al audit log has been auto saved to an external evt file.
Notifying the user.
alfFileNearlyFull
.1.3.6.1.4.1.789.0.167
al audit log file is nearly full. The file is going to
wrap. Notifying the user.
informationalTrap
.1.3.6.1.4.1.789.0.17
A user-defined trap used for informational purposes.
quotaExceeded
.1.3.6.1.4.1.789.0.176
quota limits has been exceeded.
The trap includes a string describing the specific event
which triggered the trap. The string is structured
in the following form:
Quota Event: status=exceeded, type={hard|soft|threshold},
user={username}, volume={volume}, limit_item={files|disk},
limit_value={#files|#kilobytes}
[ , treeid={tree-id} ] [ , vfiler={vfiler} ]
An example of a complete message would be:
Quota Event: status=exceeded, type=soft,
user=admin, volume=vol1, limit_item=disk, limit_value=1000000,
treeid=8
Additional key=value items may, in the future, be appended
to this message.
quotaNormal
.1.3.6.1.4.1.789.0.177
quota limits has gone back down to a normal level.
The trap includes a string describing the specific event
which triggered the trap. The string is structured
in the following form:
Quota Event: status=normal, type={hard|soft|threshold},
user={username}, volume={volume}, limit_item={files|disk},
limit_value={#files|#kilobytes}
[ , treeid={tree-id} ] [ , vfiler={vfiler} ]
An example of a complete message would be:
Quota Event: status=normal, type=soft,
user=admin, volume=vol1, limit_item=disk, limit_value=1000000,
treeid=8
Additional key=value items may, in the future, be appended
to this message.
dbgTrap
.1.3.6.1.4.1.789.0.18
ined trap used for debugging purposes.
This trap was previously mis-documented as being trap
number 17, with the name debugTrap. It has always,
actually, been trap 18. The name change is to avoid
issues with environments that already have a record
for debugTrap.
waflDirFull
.1.3.6.1.4.1.789.0.187
The directory has been filled to its limit
eccSummary
.1.3.6.1.4.1.789.0.192
Memory ECC: number of new correctable ECC errors
eccMasked
.1.3.6.1.4.1.789.0.195
Memory ECC: High frequency of ECC errors
userDefined
.1.3.6.1.4.1.789.0.2
style trap built using the 'snmp traps'
command on the filer.
ftpdError
.1.3.6.1.4.1.789.0.204
Ftp daemon: service stopped
ftpdMaxConnNotice
.1.3.6.1.4.1.789.0.206
Ftp daemon: number of connections hits maximum number
diskFailedShutdown
.1.3.6.1.4.1.789.0.21
shutting down because the system has been
running in degraded mode for 24 hours.
The trap includes a string describing the failed disk.
ftpdMaxConnThresholdNotice
.1.3.6.1.4.1.789.0.216
Ftp daemon: number of connections nearly hits maximum number
diskFailed
.1.3.6.1.4.1.789.0.22
e disks failed.
The trap includes a string describing the failed disk(s).
scsitgtFCPLinkBreak
.1.3.6.1.4.1.789.0.222
SCSI Target: Link Break on FCP adapter
scsitgtPartnerPathMisconfigured
.1.3.6.1.4.1.789.0.224
SCSI Target: FCP Partner Path Misconfigured
scsitgtThrottleNotice
.1.3.6.1.4.1.789.0.226
SCSI Target: Throttle limit event notification
vifPrimaryLinkFailed
.1.3.6.1.4.1.789.0.237
Vif: The primary Interface on a Single mode vif has failed
vifAllLinksFailed
.1.3.6.1.4.1.789.0.238
Vif: All the links of the vif have failed
vfStopped
.1.3.6.1.4.1.789.0.245
A vFiler has stopped.
vfStarted
.1.3.6.1.4.1.789.0.246
A vFiler has started.
vscanVirusDetectedError
.1.3.6.1.4.1.789.0.254
VScan: A virus scanner has detected a virus on the Filer
vscanDisConnection
.1.3.6.1.4.1.789.0.255
VScan: A virus scanner has dropped its connection from the Filer
vscanConfigurationChange
.1.3.6.1.4.1.789.0.256
VScan: There has been a change to the vscan configuration
vscanConnection
.1.3.6.1.4.1.789.0.257
VScan: A virus scanner has made a connection to the Filer
diskRepaired
.1.3.6.1.4.1.789.0.26
disks have been repaired.
This trap is a placeholder -
it is not currently sent by Data ONTAP.
vscanServerUpgrade
.1.3.6.1.4.1.789.0.266
VScan: The Vscan server has been upgraded
volumeRestrictedByMirrorBigIo
.1.3.6.1.4.1.789.0.272
hat experienced a medium error during reconstruction
is restricted and marked wafl-inconsistent, but starting
wafliron has failed. This trap is issued to alert operator
that a volume is not accessible and wafliron must be started
to allow access to it.
volumeInconsistentUmount
.1.3.6.1.4.1.789.0.274
is issued when we unmount a volume due to an
inconsistency.
volumeStateChanged
.1.3.6.1.4.1.789.0.275
being taken offline or being restricted.
The string sent with trap specifies name of affected volume
and its state.
volumeOnline
.1.3.6.1.4.1.789.0.276
online now. The string sent with trap specifies
name of volume which is online now.
rmcCardNeedsReplacement
.1.3.6.1.4.1.789.0.283
agement Controller card needs replacement. The trap
includes a string specifying the reason for replacement
rmcCardMissingCables
.1.3.6.1.4.1.789.0.284
agement Controller card is missing its internal
cable, or LAN cable or power supply cable. The trap includes
a string specifying the missing component.
volumeRemoteUnreachable
.1.3.6.1.4.1.789.0.294
me encountered an error while communicating
to remote volume.
volumeRemoteOk
.1.3.6.1.4.1.789.0.296
ication between remote volume and local volume
returned to normal.
volumeRemoteRestored
.1.3.6.1.4.1.789.0.297
n remote volume has been fully restored to local
volume.
volumeRemoteRestoreBegin
.1.3.6.1.4.1.789.0.298
n remote volume has started being restored to local
volume by Restore-on-Demand.
volumeRestrictedRootConflict
.1.3.6.1.4.1.789.0.304
restricted due to a root volume conflict. The
string sent with trap specifies name of conflicting volume
which is being restricted.
fanFailureShutdown
.1.3.6.1.4.1.789.0.31
hassis or cpu fans have failed and the system
is shutting down.
volumeOfflineTooBig
.1.3.6.1.4.1.789.0.314
not be brought online because its raw size is
larger than maximum allowed size. The string sent with trap
specifies name of affected volume and its raw size, and
maximum allowed size.
volumeOffline
.1.3.6.1.4.1.789.0.324
being taken offline. The string sent with trap
specifies name of affected volume and reason for being
taken offline.
fanFailed
.1.3.6.1.4.1.789.0.33
e chassis fans failed.
The trap includes a string describing the failed fan(s).
volumeRestricted
.1.3.6.1.4.1.789.0.334
being restricted. The string sent with trap
specifies name of affected volume and reason for being
restricted.
volumeDegradedDirty
.1.3.6.1.4.1.789.0.344
degraded and has dirty parity. WAFL_check must be
run on this volume before it can be brought online. The string
sent with trap specifies name of affected volume.
fanWarning
.1.3.6.1.4.1.789.0.35
e chassis or cpu fans are in warning state.
The trap includes a string describing the fan(s) in
the warning state.
volumeError
.1.3.6.1.4.1.789.0.354
is issued when a volume cannot be brought online
due to an error. The string sent with trap specifies name of
affected volume and error description.
volumeSelectedRootConflict
.1.3.6.1.4.1.789.0.356
is issued when multiple root volumes are detected
at boot time and one is selected as the root by default. The
string sent with the trap specifies the name of the selected
volume and the reason.
fanRepaired
.1.3.6.1.4.1.789.0.36
All fans are repaired.
snapmirrorSyncFailed
.1.3.6.1.4.1.789.0.364
Synchronous SnapMirror failed and went into asynchronous mode.
snapmirrorSyncOk
.1.3.6.1.4.1.789.0.366
Synchronous SnapMirror went into synchronous mode.
chassisTemperatureShutdown
.1.3.6.1.4.1.789.0.371
s temperature is extreme. The appliance has
initiated a shutdown to protect itself. The operating
environment should be monitored and corrected before
restarting the appliance.
chassisTemperatureWarning
.1.3.6.1.4.1.789.0.372
s temperature is either too high or too low.
The temperature should be monitored and, if possible, corrected.
chassisTemperatureUnknown
.1.3.6.1.4.1.789.0.375
s temperature is unknown, because reading can't be
obtained from the chassis temperature sensor.
chassisTemperatureOk
.1.3.6.1.4.1.789.0.376
The chassis temperature is OK.
chassisCPUFanStopped
.1.3.6.1.4.1.789.0.381
e CPU fans have stopped. The appliance
has initiated a shutdown to protect itself. A new
motherboard may be required to correct the fan.
Contact customer support for direction.
chassisCPUFanSlow
.1.3.6.1.4.1.789.0.383
is spinning too slowly. A new motherboard
may be required to correct the fan. Contact customer
support for direction.
chassisCPUFanOk
.1.3.6.1.4.1.789.0.386
All CPU fan(s) are properly functioning.
chassisPowerSuppliesFailed
.1.3.6.1.4.1.789.0.391
Multiple chassis power supplies failed.
chassisPowerSupplyDegraded
.1.3.6.1.4.1.789.0.392
e chassis power supplies are degraded.
A description of the degraded state has been
logged to the console and message log file.
chassisPowerSupplyFailed
.1.3.6.1.4.1.789.0.393
One chassis power supply failed.
chassisPowerSupplyRemoved
.1.3.6.1.4.1.789.0.394
One or more chassis power supplies are removed.
chassisPowerSupplyOff
.1.3.6.1.4.1.789.0.395
One or more chassis power supplies are off.
chassisPowerSuppliesOk
.1.3.6.1.4.1.789.0.396
The chassis power supplies are all functioning properly.
chassisPowerSupplyOk
.1.3.6.1.4.1.789.0.397
This chassis power supply is functioning properly.
chassisPowerDegraded
.1.3.6.1.4.1.789.0.403
within the chassis is degraded.
A description of the degraded state has been
logged to the console and message log file.
chassisPowerOk
.1.3.6.1.4.1.789.0.406
The power within the chassis is functioning properly.
powerSupplyFailureShutdown
.1.3.6.1.4.1.789.0.41
ower supplies or power rails failed and
the system is shutting down.
chassisFanDegraded
.1.3.6.1.4.1.789.0.412
A chassis fan has been degraded.
chassisFanRemoved
.1.3.6.1.4.1.789.0.413
A chassis fan FRU has been removed.
chassisFanStopped
.1.3.6.1.4.1.789.0.414
One or more chassis fans have stopped.
chassisFanWarning
.1.3.6.1.4.1.789.0.415
One or more chassis fans is spinning slowly or too fast.
chassisFanOk
.1.3.6.1.4.1.789.0.416
All chassis fans are functioning properly.
writeVerificationFailed
.1.3.6.1.4.1.789.0.424
s failed a verification test
on a SnapValidator enabled volume.
powerSupplyFailed
.1.3.6.1.4.1.789.0.43
e redundant power supplies failed.
Include in the trap a string describing
the failed power supply(ies).
prefDCDisconnect
.1.3.6.1.4.1.789.0.434
tions to domain controllers in the preferred domain
controllers list have been lost.
domainControllerDisconnect
.1.3.6.1.4.1.789.0.435
A CIFS domain controller connection to the filer has failed.
dcPasswdChangeFailed
.1.3.6.1.4.1.789.0.436
to change the storage system's password with the domain
controller has failed.
domainControllerConnected
.1.3.6.1.4.1.789.0.437
ain controller connection to the filer has been
established.
plexFailed
.1.3.6.1.4.1.789.0.444
is issued when one plex of a mirrored
aggregate is failed. The string sent with
this trap specifies name of affected plex or
mirrored aggregate.
powerSupplyWarning
.1.3.6.1.4.1.789.0.45
e power supplies or power rails in
warning state. Include in the trap a string describing
the power supply(ies) or the power rail(s) in the
warning state.
plexOffline
.1.3.6.1.4.1.789.0.454
is issued when a plex becomes offline.
The string sent with this trap specifies name of
affected plex or mirrored aggregate.
powerSupplyRepaired
.1.3.6.1.4.1.789.0.46
-failed power supplies or power rails have been
repaired.
shelfSESElectronicsFailed
.1.3.6.1.4.1.789.0.464
e of the enclosure services devices in a
disk shelf has failed. Some shelf designs combine
the enclosure monitoring hardware function into the
module that provides the storage interface to
the shelf. A failure in the enclosure monitoring
section of these combined modules does not necessarily
indicate a failure in disk or loop or bus operation,
which may be able to continue.
shelfSESElectronicsWarning
.1.3.6.1.4.1.789.0.465
e of the enclosure services devices in a
disk shelf has reported a problem. Some shelf designs
combine the enclosure monitoring hardware function into
the module that provides the storage interface to
the shelf. A failure in the enclosure monitoring
section of these combined modules does not necessarily
indicate a failure in disk or loop or bus operation,
which may be able to continue.
shelfSESElectronicsInfo
.1.3.6.1.4.1.789.0.467
ly reported failure of an enclosure
services device in a disk shelf has been corrected,
or the device has reported information that does not
necessarily require customer action.
shelfIFModuleFailed
.1.3.6.1.4.1.789.0.473
e of the storage interface modules in a
disk shelf has failed. Some shelf designs combine the
enclosure monitoring hardware function into the module
that operates the fibre channel loop or SCSI in the
shelf. This failure is of the storage interface
itself, not a failure of the enclosure monitoring,
which may be able to continue. This failure may make
one or more disks in the shelf or in the loop or bus
unavailable.
shelfIFModuleWarning
.1.3.6.1.4.1.789.0.475
e of the storage interface modules in a
disk shelf has a warning condition. Some shelf designs combine the
enclosure monitoring hardware function into the module
that operates the fibre channel loop or SCSI in the
shelf. This warning condition is of the storage interface
itself, not a failure of the enclosure monitoring,
which may be able to continue.
shelfIFModuleInfo
.1.3.6.1.4.1.789.0.477
ly reported failure of a disk shelf
interface module has been corrected, or the module has
reported information that does not necessarily require
customer action.
maxDirSizeAlert
.1.3.6.1.4.1.789.0.482
y has reached its maxdirsize limit. Either
increase the maxdirsize or clean up the directory.
maxDirSizeWarning
.1.3.6.1.4.1.789.0.485
y is getting close to its maxdirsize limit. Either
increase the maxdirsize or clean up the directory.
cifsStatsExhaustMemCtrlBlk
.1.3.6.1.4.1.789.0.497
for a CIFS control block cannot be granted. All
control blocks are in use.
chassisPSRemovedxMinShutdown
.1.3.6.1.4.1.789.0.501
ly Unit is removed from the system. System will
be shutdown in x minutes if it is not put back.
chassisPSUsMismatch
.1.3.6.1.4.1.789.0.505
ly Units in the system are of different type.
Please replace them with correct Power Supply Units.
chassisFanFailxMinShutdown
.1.3.6.1.4.1.789.0.511
hassis fan failure. System will
shut down in a few minutes if not corrected.
chassisPSUwrongInput
.1.3.6.1.4.1.789.0.515
ly Unit (PSU) in the system is connected to an
incompatible external power source. Please change
the power source being used or replace the PSU
with one that matches the current power source.
powerSupplyFanFailxMinShutdown
.1.3.6.1.4.1.789.0.521
power supply fans failure.
System will shut down in a few minutes if not corrected.
ioCardFailed
.1.3.6.1.4.1.789.0.525
is degraded.
The trap includes a string describing
the degraded IO card.
ioCardOk
.1.3.6.1.4.1.789.0.526
d is functioning properly.
The trap includes a string containing the slot number
of the IO card.
remoteSystemMgtAlert
.1.3.6.1.4.1.789.0.532
ote management detected a system down event.
The trap includes a string describing the specific event
which triggered the trap. The string is structured in the
following form:
Remote Management Event: type={system_down|system_up|test|keep_alive},
severity={alert|warning|notice|normal|debug|info},
event={post_error|watchdog_reset|power_loss|abnormal_reboot},
key=value
An example of a complete message would be:
Remote Management Event: type=system_down, severity=alert,
event=watchdog_reset, ss=16bytes
Additional key=value items may, in the future, be appended
to this message.
The events that would generate this trap would be:
post_error: Fatal POST error on boot
power_loss: Loss of power to system
abnormal_reboot:
l2_watchdog_reset
remoteSystemMgmtWarning
.1.3.6.1.4.1.789.0.535
ote management detected a system down event.
The trap includes a string describing the specific event
which triggered the trap. The string is structured in the
following form:
Remote Management Event: type={system_down|system_up|test|keep_alive},
severity={alert|warning|notice|normal|debug|info},
event={loss-of-heartbeat},
key=value
An example of a complete message would be:
Remote Management Event: type=system_down, severity=warning,
event=loss_of_heartbeat, ss=16bytes
Additional key=value items may, in the future, be appended
to this message.
The events that would generate this trap would be:
loss_of_heartbeat: Loss of heartbeat to the RLM.
remoteSystemMgmtNotification
.1.3.6.1.4.1.789.0.536
ote management detected a system down event.
The trap includes a string describing the specific event
which triggered the trap. The string is structured in the
following form:
Remote Management Event: type={system_down|system_up|test|keep_alive},
severity={alert|warning|notice|normal|debug|info},
event={power_off_via_rlm,power_cycle_via_rlm,reset_via_rlm},
key=value
An example of a complete message would be:
Remote Management Event: type=system_down, severity=notice,
event=power_off_via_rlm, ss=16bytes
Additional key=value items may, in the future, be appended
to this message.
The events that would generate this trap would be:
power_off_via_rlm: This indicates system power off
power_cycle_via_rlm: This indicates system power cycle
reset_via_rlm: This indicates system reset.
remoteSystemMgmtPeriodic
.1.3.6.1.4.1.789.0.547
periodic keep alive from system remote management.
The trap includes a string describing the specific event
which triggered the trap. The string is structured in the
following form:
Remote Management Event: type={system_down|system_up|test|keep_alive},
severity={alert|warning|notice|normal|debug|info},
event={periodic_message}
An example of a complete message would be:
Remote Management Event: type=keep_alive, severity=info,
event=periodic_message
Additional key=value items may, in the future, be appended
to this message.
cpuTooBusy
.1.3.6.1.4.1.789.0.55
ation exceeds 90%.
This trap is not enabled by default.
To enable this trap set the registry
entry options.monitor.cpu.enable to on.
Note that as the threshold for this trap is
checked once a minute it is possible to receive
multiple instances of this trap in a short time.
remotesystemMgmtTest
.1.3.6.1.4.1.789.0.556
test trap from system remote management.
The trap includes a string describing the specific event
which triggered the trap. The string is structured in the
following form:
Remote Management Event: type={system_down|system_up|test|keep_alive},
severity={alert|warning|notice|normal|debug|info},
event={periodic_message}
An example of a complete message would be:
Remote Management Event: type=test, severity=notice, event=test
Additional key=value items may, in the future, be appended
to this message.
cpuOk
.1.3.6.1.4.1.789.0.56
CPU utilization has dropped back below 90%.
diskMultipathOneSwitch
.1.3.6.1.4.1.789.0.562
A multipathed disk is only connected to one switch.
diskMultipathNoTakeover
.1.3.6.1.4.1.789.0.563
disks or luns could not be detected for the partner.
The node will be unable to takeover correctly.
diskMultipathWarning
.1.3.6.1.4.1.789.0.565
s mirroring is enabled, even though disks are not
multipathed.
driveDisableErr
.1.3.6.1.4.1.789.0.574
s been disabled by the shelf module due to
hardware errors. If it is the only drive in the shelf
that is disabled, replace the drive.
hbaOfflineInformation
.1.3.6.1.4.1.789.0.587
adapter (HBA) port has been disabled.
This state may be caused either by user command or by
errors that make the interface unable to communicate
with attached devices.
fcOfflineError
.1.3.6.1.4.1.789.0.594
nnel adapter port has gone off-line due to
an error condition.
fcOnlineFailWarning
.1.3.6.1.4.1.789.0.595
nnel adapter has failed to come on-line due
to some error condition. Check the cables for proper
connections.
fcOffLineNotification
.1.3.6.1.4.1.789.0.596
nnel adapter has gone off line.
This state may be caused either by user command or by
errors that make the interface unable to communicate
with attached devices.
fcOnlineInformation
.1.3.6.1.4.1.789.0.597
A FibreChannel adapter port has come on-line.
dhmNoticeDegradedIO
.1.3.6.1.4.1.789.0.6
h Monitor -
Reported a Disk Degraded-I/O Event
lunSnapRestoreStatus
.1.3.6.1.4.1.789.0.606
Status of the Snap Restore
lunCloneCreate
.1.3.6.1.4.1.789.0.616
Created a LUN Clone
nvramBatteryDischarged
.1.3.6.1.4.1.789.0.62
The NVRAM battery is fully discharged.
lunCloneSplitStart
.1.3.6.1.4.1.789.0.626
LUN Clone Split started
lunCloneSplitComplete
.1.3.6.1.4.1.789.0.627
LUN Clone Split completed
nvramBatteryLow
.1.3.6.1.4.1.789.0.63
The charge in the NVRAM battery is low.
flexCloneSplitStart
.1.3.6.1.4.1.789.0.636
Flex Clone Split started
flexCloneSplitComplete
.1.3.6.1.4.1.789.0.637
Flex Clone Split completed
volumeCloneCreate
.1.3.6.1.4.1.789.0.646
Created a Volume Clone
snapAutoDelete
.1.3.6.1.4.1.789.0.656
Snapshot Auto Deleted
volumeAutogrow
.1.3.6.1.4.1.789.0.666
Volume is Auto Grown
timedTargetNotResponding
.1.3.6.1.4.1.789.0.674
NTP Time Daemon lost contact with the configured target
extcacheCardError
.1.3.6.1.4.1.789.0.676
External cache card failure
extcacheCardOffline
.1.3.6.1.4.1.789.0.686
External cache is taken offline
svBackupSnapWarningLimit
.1.3.6.1.4.1.789.0.695
ing number of Snapshot copies for a backup
schedule is below warning limit specified.
dhmNoticePFAEvent
.1.3.6.1.4.1.789.0.7
h Monitor -
Reported a Disk Predictive-Failure Event
avTrendLicenseExpired
.1.3.6.1.4.1.789.0.705
Trend Micro antivirus license has expired
avTrendLicenseExpiring
.1.3.6.1.4.1.789.0.706
Trend Micro antivirus license is about to expire
rebootAbnormal
.1.3.6.1.4.1.789.0.712
ooted abnormally after any of the following
events:
event = watchdog reset, agent watchdog reset, panic,
power-glitch.
rebootNormal
.1.3.6.1.4.1.789.0.716
ooted normally after any of the following
events:
event = giveback, revert, WAFL check, power-on,
internal reboot, internal halt, rlm system reset, operator
initiated halt and reboot.
clusterNodeFailed
.1.3.6.1.4.1.789.0.72
a Cluster FailOver configuration failed.
Its partner will assume service for the failed node.
volMoveCutoverDeferred
.1.3.6.1.4.1.789.0.724
ove job cannot be completed because cutover phase
has been deferred.
volMoveCutoverFailed
.1.3.6.1.4.1.789.0.734
ove job cannot be completed because the cutover
attempt resulted in failure.
volMoveDone
.1.3.6.1.4.1.789.0.736
A volume move job completed successfully.
volMoveCutoverDeferredWait
.1.3.6.1.4.1.789.0.737
ove has reached the cutover phase and is waiting
for the user to trigger cutover because the user specified
wait for cutover-action
scsibladeOutOfQuorum
.1.3.6.1.4.1.789.0.741
as lost connectivity with the other nodes
in the cluster. Both fcp and iscsi traffic have been disabled
on this node. The corrective action is to reboot the node, and
if the node is waiting for giveback then perform a giveback.
scsibladeInQuorum
.1.3.6.1.4.1.789.0.746
stablished connectivity with the other nodes
in the cluster.
clusterNodeTakenOver
.1.3.6.1.4.1.789.0.75
The partner has taken over for a failed cluster node.
qosMonitorMemoryMaxed
.1.3.6.1.4.1.789.0.755
c memory has reached its limit. Some QoS features
may operate in a limited capacity.
qosMonitorMemoryAbated
.1.3.6.1.4.1.789.0.757
c memory is no longer at its limit. All QoS features
will operate as normal.
clusterNodeRepaired
.1.3.6.1.4.1.789.0.76
A cluster node has resumed operation.
sfoAggregateRelocated
.1.3.6.1.4.1.789.0.767
is issued when an SFO aggregate is relocated permanently
from one node to another.
clusterNodeRepairing
.1.3.6.1.4.1.789.0.77
A cluster node has rebooted, and a giveback has started.
avUpdateFailed
.1.3.6.1.4.1.789.0.773
The anti-virus software update failed.
avLicenseCheckFailed
.1.3.6.1.4.1.789.0.774
The anti-virus software license validation failed.
avMcAfeeProductExpired
.1.3.6.1.4.1.789.0.775
McAfee product has expired.
avRemedy
.1.3.6.1.4.1.789.0.776
Remedy action taken. The file has been repaired, deleted or quarantined.
avLicenseCheck
.1.3.6.1.4.1.789.0.777
License validation was successful.
avRemedyFailure
.1.3.6.1.4.1.789.0.783
Remedy action failed. The file was not repaired, deleted or quarantined.
avMcAfeeEngineExpired
.1.3.6.1.4.1.789.0.785
McAfee product has expired.
avMcAfeeProductExpiring
.1.3.6.1.4.1.789.0.786
McAfee product is expiring.
av2gbFileNotScanned
.1.3.6.1.4.1.789.0.793
A file larger than 2GB is not scanned and marked as clean.
avMcAfeeEngineExpiring
.1.3.6.1.4.1.789.0.796
McAfee engine is expiring.
avVirusfound
.1.3.6.1.4.1.789.0.802
Virus found while scanning.
avMcAfeeLicenseFailed
.1.3.6.1.4.1.789.0.803
McAfee antivirus license activation failed.
avDisableFailed
.1.3.6.1.4.1.789.0.804
The anti-virus service disabling failed in the cluster.
avDisable
.1.3.6.1.4.1.789.0.805
The anti-virus service is disabled in the cluster.
avMcAfeeLicenseExpiring
.1.3.6.1.4.1.789.0.806
McAfee antivirus license is about to expire.
avEnable
.1.3.6.1.4.1.789.0.807
The anti-virus service is enabled in the cluster.
avSpywareFound
.1.3.6.1.4.1.789.0.812
Spyware found while scanning.
avEnableFailed
.1.3.6.1.4.1.789.0.813
The anti-virus service enabling failed in the cluster.
avRollbackFailed
.1.3.6.1.4.1.789.0.814
The anti-virus software rollback failed.
avRollback
.1.3.6.1.4.1.789.0.816
The anti-virus software is rolled back.
avUpdate
.1.3.6.1.4.1.789.0.817
The anti-virus software is updated.
volumeFull
.1.3.6.1.4.1.789.0.82
ne volume is more than 98% full.
The string sent with the trap gives the
name of the volume or volumes which exceed
the volumeFull or volumeNearlyFull thresholds
snmpBusy
.1.3.6.1.4.1.789.0.824
The SNMP server is too busy.
lunDestroy
.1.3.6.1.4.1.789.0.837
A LUN was destroyed.
volumeNearlyFull
.1.3.6.1.4.1.789.0.85
ne volume is more than 95% full.
The string sent with the trap gives the
name of the volume or volumes which exceed
the volumeFull or volumeNearlyFull thresholds
volumeRepaired
.1.3.6.1.4.1.789.0.86
All volumes are now under 95% full.
healthMonitorAlertRaised
.1.3.6.1.4.1.789.0.862
A Health Monitor has created an alert.
healthMonitorAlertCleared
.1.3.6.1.4.1.789.0.867
A Health Monitor has cleared an alert.
volumesStillFull
.1.3.6.1.4.1.789.0.87
ne volume that was full or nearly full is now OK,
but more volumes still exceed the volumeNearlyFull or
volumeFull thresholds. This trap is generally sent within
a short time of when a volume becomes OK, though if two
volumes become OK within this timeframe, only one trap is
sent. The string sent with the trap gives the name of the
volume or volumes which still exceed the volumeFull or
volumeNearlyFull thresholds. It does not send the name of
any volume that is OK.
volumeLogicalOverallocated
.1.3.6.1.4.1.789.0.873
has over allocated space and may not be able to
honor file reservations or the aggregate has over allocated
space and may not be able to honor volume guarantees.
If and when the reserved/guaranteed space is consumed
there will be insufficient physical space which can
cause the volume/aggregate to be taken offline.
volumeReserveGrew
.1.3.6.1.4.1.789.0.875
ne volume's WAFL reserve grew because it was
physically over allocated.
volumePhysicalOverallocated
.1.3.6.1.4.1.789.0.882
/aggregate is running dangerously low on
free blocks to write to.
smVaultSnapWarnLimit
.1.3.6.1.4.1.789.0.895
The snapshot count limit on the destination volume has been reached.
lunRelocationCompletion
.1.3.6.1.4.1.789.0.896
Lun relocation completed successfully
smSyncOutOfSyncWarn
.1.3.6.1.4.1.789.0.905
ous granular CG relationship has
transitioned from in-sync to out-of-sync and
remained out-of-sync for longer than expected.
overTempShutdown
.1.3.6.1.4.1.789.0.91
perature is too high to continue
operating. The system is shutting down.
overTemp
.1.3.6.1.4.1.789.0.95
perature is too high and in the
warning level.
overTempRepaired
.1.3.6.1.4.1.789.0.96
perature has returned to an
acceptable value.
clusterLinkDown
.1.3.6.1.4.1.789.0.973
A cluster link has been lost.
clusterL2ConnFail
.1.3.6.1.4.1.789.0.983
The l2ping command is currently failing between cluster ports.
clusterPingDropLarge
.1.3.6.1.4.1.789.0.993
Pings of large packets between cluster ports are currently failing.
Boolean
netapp 
productType 
productLicenseTable 
productLicenseEntry 
productLicenseIndex 
diskFailedRemoveCarrier