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.
admissionMemError
.1.3.6.1.4.1.17163.1.51.4.0.10
Memory pressure is high. No additional connections will be
optimized
graniteLunError
.1.3.6.1.4.1.17163.1.51.4.0.10000
LUN module encountered error.
graniteISCSIError
.1.3.6.1.4.1.17163.1.51.4.0.10001
iSCSI module encountered error.
graniteISNSError
.1.3.6.1.4.1.17163.1.51.4.0.10002
iSNS module encountered error.
graniteSnapshotError
.1.3.6.1.4.1.17163.1.51.4.0.10003
Snapshot module encountered error.
graniteBlockstoreError
.1.3.6.1.4.1.17163.1.51.4.0.10004
Blockstore module encountered error.
graniteCoreError
.1.3.6.1.4.1.17163.1.51.4.0.10005
SteelFusion Core module encountered error.
graniteUncommittedDataError
.1.3.6.1.4.1.17163.1.51.4.0.10006
The level of uncommitted data is too high.
graniteHighAvailabilityError
.1.3.6.1.4.1.17163.1.51.4.0.10007
High availability module encountered error.
graniteApplianceUnlicensedError
.1.3.6.1.4.1.17163.1.51.4.0.10009
Appliance license expired/invalid.
cpuUtilClear
.1.3.6.1.4.1.17163.1.51.4.0.1003
The average CPU utilization has fallen back
within the acceptable threshold
pagingActivityClear
.1.3.6.1.4.1.17163.1.51.4.0.1004
The system has stopped paging excessively (thrashing)
peerVersionMismatchClear
.1.3.6.1.4.1.17163.1.51.4.0.1006
All peers are compatible
bypassModeClear
.1.3.6.1.4.1.17163.1.51.4.0.1007
Traffic is now being optimized
raidErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1008
A RAID error has been cleared
storeCorruptionClear
.1.3.6.1.4.1.17163.1.51.4.0.1009
The data store is normal
admissionMemErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1010
Admission control memory alarm has been cleared,
and the optimization service is running normally
admissionConnErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1011
Admission control connections alarm has been cleared,
and the service is running normally
haltErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1012
The service is now running normally
serviceErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1013
The service is now running normally
linkErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1017
An interface on the appliance has regained its link
nfsV2V4Clear
.1.3.6.1.4.1.17163.1.51.4.0.1018
NFS v2/v4 alarm has been cleared
powerSupplyErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1019
All power supplies are now functioning normally
asymRouteErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1020
All asymmetric routes have expired or have been cleared
fanErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1021
All system fans are now functioning normally
memoryErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1022
A memory error has been rectified on the appliance
ipmiClear
.1.3.6.1.4.1.17163.1.51.4.0.1023
An IPMI event has been rectified on the appliance
temperatureNormal
.1.3.6.1.4.1.17163.1.51.4.0.1026
The system temperature is back within the threshold
temperatureNonCritical
.1.3.6.1.4.1.17163.1.51.4.0.1027
The system temperature is no longer in a critical stage
cfConnRestored
.1.3.6.1.4.1.17163.1.51.4.0.1028
Connection reestablished with the specified neighbor
cfConnLostEosClear
.1.3.6.1.4.1.17163.1.51.4.0.1029
Connection reestablished after a prior termination due to
receiving end of stream from the specified neighbor
cfConnLostErrClear
.1.3.6.1.4.1.17163.1.51.4.0.1030
Connection restablished after a prior termination due to
an error communicating with the specified neighbor
cfKeepaliveTimeoutClear
.1.3.6.1.4.1.17163.1.51.4.0.1031
Keepalive restored after a prior timeout with the specified neighbor
cfAckTimeoutClear
.1.3.6.1.4.1.17163.1.51.4.0.1032
Ack restored after a prior timeout with the specified neighbor
cfReadInfoTimeoutClear
.1.3.6.1.4.1.17163.1.51.4.0.1033
Successfully read info from the specified neighbor after a prior
timeout
cfLatencyExceededClear
.1.3.6.1.4.1.17163.1.51.4.0.1034
Connection forwarding latency with the specified neighbor
is back within the threshold
sslPeeringSCEPAutoReenrollClear
.1.3.6.1.4.1.17163.1.51.4.0.1035
Automatic re-enrollment of SSL peering certificate is OK or is disabled
crlClear
.1.3.6.1.4.1.17163.1.51.4.0.1036
crl polling is running normally
datastoreSyncFailureClear
.1.3.6.1.4.1.17163.1.51.4.0.1037
Data store sync restored
secureVaultClear
.1.3.6.1.4.1.17163.1.51.4.0.1040
Secure vault has been unlocked and is healthy
diskErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1045
All disks are back online
admissionCpuErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1052
Admission control CPU alarm has been cleared,
and the service is running normally
admissionTcpErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1053
Admission control TCP alarm has been cleared,
and the service is running normally
systemDiskFullErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1054
The system partitions are below usage thresholds
domainJoinErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1055
A domain error on the appliance has been cleared
certsExpiringErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1056
There are no expiring certificates
licenseErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1057
The main appliance license error has been cleared
hardwareErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1058
Hardware Error has been cleared
sysdetailErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1059
Overall status of System Detail Report is back to OK
admissionMapiErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1060
System will resume to optimize new MAPI connections since connection count has fallen below the threshold
neighborIncompatibilityClear
.1.3.6.1.4.1.17163.1.51.4.0.1061
Serial cascade misconfiguration issue is now resolved.
flashErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1062
Flash is back to OK.
lanWanLoopClear
.1.3.6.1.4.1.17163.1.51.4.0.1063
LAN-WAN loop error cleared. System will resume to optimize connect
ions.
optimizationServiceStatusClear
.1.3.6.1.4.1.17163.1.51.4.0.1064
Optimization Service error cleared. System will resume to optimize
connections.
upgradeFailureClear
.1.3.6.1.4.1.17163.1.51.4.0.1065
Upgrade failure cleared and the system is still running
the previous image
clusterDisconnectedSHAlertClear
.1.3.6.1.4.1.17163.1.51.4.0.1068
All cluster Steelheads are currently connected
smbAlertClear
.1.3.6.1.4.1.17163.1.51.4.0.1069
Domain authentication alert has been cleared
linkDuplexClear
.1.3.6.1.4.1.17163.1.51.4.0.1070
An interface on the appliance has cleared the half-duplex error
linkIoErrorsClear
.1.3.6.1.4.1.17163.1.51.4.0.1071
An interface on the appliance has cleared the I/O errors state
clusterIpv6IncompatiblePeerClear
.1.3.6.1.4.1.17163.1.51.4.0.1074
All cluster Steelheads are IPv6 compatible
pathSelectionPathDownClear
.1.3.6.1.4.1.17163.1.51.4.0.1077
Path Selection - A path came back up
clusterNeighborIncompatibleClear
.1.3.6.1.4.1.17163.1.51.4.0.1080
All cluster Steelheads are compatible
secureTransportControllerConnected
.1.3.6.1.4.1.17163.1.51.4.0.1081
Steelhead successfully connected to Secure Transport controller
secureTransportRegistrationSucceeded
.1.3.6.1.4.1.17163.1.51.4.0.1082
Steelhead successfully registered with Secure Transport controller
pathSelectionPathProbingErrorClear
.1.3.6.1.4.1.17163.1.51.4.0.1083
Path Selection - No paths have probing errors
webProxyConfigAlarmClear
.1.3.6.1.4.1.17163.1.51.4.0.1084
Web Proxy Service Configuration Alarm cleared
webProxyServiceAlarmClear
.1.3.6.1.4.1.17163.1.51.4.0.1085
Web Proxy Service Status Alarm cleared
admissionConnError
.1.3.6.1.4.1.17163.1.51.4.0.11
Connection limit reached. No additional connections will be
optimized
graniteLunClear
.1.3.6.1.4.1.17163.1.51.4.0.11000
LUN module error cleared.
graniteISCSIClear
.1.3.6.1.4.1.17163.1.51.4.0.11001
iSCSI module error cleared.
graniteISNSClear
.1.3.6.1.4.1.17163.1.51.4.0.11002
iSNS module error cleared.
graniteSnapshotClear
.1.3.6.1.4.1.17163.1.51.4.0.11003
Snapshot module error cleared.
graniteBlockstoreClear
.1.3.6.1.4.1.17163.1.51.4.0.11004
Blockstore module error cleared.
graniteCoreClear
.1.3.6.1.4.1.17163.1.51.4.0.11005
SteelFusion Core module error cleared.
graniteUncommittedDataClear
.1.3.6.1.4.1.17163.1.51.4.0.11006
The level of uncommitted data has returned to normal.
graniteHighAvailabilityClear
.1.3.6.1.4.1.17163.1.51.4.0.11007
High availability module error cleared.
graniteApplianceUnlicensedClear
.1.3.6.1.4.1.17163.1.51.4.0.11009
Appliance license active.
haltError
.1.3.6.1.4.1.17163.1.51.4.0.12
The service is halted due to a software error
serviceError
.1.3.6.1.4.1.17163.1.51.4.0.13
There has been a non-fatal optimization service error.
Please consult the log file
scheduledJobError
.1.3.6.1.4.1.17163.1.51.4.0.14
A scheduled job has failed during execution
confModeEnter
.1.3.6.1.4.1.17163.1.51.4.0.15
A user has entered configuration mode
confModeExit
.1.3.6.1.4.1.17163.1.51.4.0.16
A user has exited configuration mode
linkError
.1.3.6.1.4.1.17163.1.51.4.0.17
An interface on the appliance has lost its link
nfsV2V4
.1.3.6.1.4.1.17163.1.51.4.0.18
NFS v2/v4 alarm notification
powerSupplyError
.1.3.6.1.4.1.17163.1.51.4.0.19
A power supply on the appliance has failed
procExit
.1.3.6.1.4.1.17163.1.51.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.
asymRouteError
.1.3.6.1.4.1.17163.1.51.4.0.20
Asymmetric routes have been detected,certain connections might
not have been optimized because of this.
vspServiceNotRunningError
.1.3.6.1.4.1.17163.1.51.4.0.20002
VSP service alarm is triggered.
virtCpuError
.1.3.6.1.4.1.17163.1.51.4.0.20003
Virtualization CPU alarm is triggered.
esxiVersionUnsupportedError
.1.3.6.1.4.1.17163.1.51.4.0.20004
ESXi version unsupported alarm is triggered.
esxiCommunicationFailedError
.1.3.6.1.4.1.17163.1.51.4.0.20005
ESXi communication failed alarm is triggered.
esxiNotSetUpError
.1.3.6.1.4.1.17163.1.51.4.0.20006
ESXi not set up alarm is triggered.
esxiDiskCreationFailedError
.1.3.6.1.4.1.17163.1.51.4.0.20007
ESXi disk creation failed alarm is triggered.
vspUnsupportedVmCountError
.1.3.6.1.4.1.17163.1.51.4.0.20008
VSP unsupported VM count alarm is triggered.
esxiMemoryOvercommittedError
.1.3.6.1.4.1.17163.1.51.4.0.20009
ESXi memory overcommitted alarm is triggered.
esxiLicenseExpiredError
.1.3.6.1.4.1.17163.1.51.4.0.20010
ESXi license expired alarm is triggered.
esxiLicenseExpiringError
.1.3.6.1.4.1.17163.1.51.4.0.20011
ESXi license expiring alarm is triggered.
esxiTrialLicenseError
.1.3.6.1.4.1.17163.1.51.4.0.20012
ESXi trial license alarm is triggered.
esxiVswitchMtuUnsupportedError
.1.3.6.1.4.1.17163.1.51.4.0.20013
ESXi unsupported vSwitch MTU alarm is triggered.
esxiInitialConfigFailedError
.1.3.6.1.4.1.17163.1.51.4.0.20014
ESXi initial config failed alarm is triggered.
fanError
.1.3.6.1.4.1.17163.1.51.4.0.21
A fan has failed on this appliance
vspServiceNotRunningClear
.1.3.6.1.4.1.17163.1.51.4.0.21002
VSP service alarm cleared.
virtCpuClear
.1.3.6.1.4.1.17163.1.51.4.0.21003
Virtualization CPU alarm cleared.
esxiVersionUnsupportedClear
.1.3.6.1.4.1.17163.1.51.4.0.21004
ESXi version unsupported alarm cleared.
esxiCommunicationFailedClear
.1.3.6.1.4.1.17163.1.51.4.0.21005
ESXi communication failed alarm cleared.
esxiNotSetUpClear
.1.3.6.1.4.1.17163.1.51.4.0.21006
ESXi not set up alarm cleared.
esxiDiskCreationFailedClear
.1.3.6.1.4.1.17163.1.51.4.0.21007
ESXi disk creation failed alarm cleared.
vspUnsupportedVmCountClear
.1.3.6.1.4.1.17163.1.51.4.0.21008
VSP unsupported VM count alarm cleared.
esxiMemoryOvercommittedClear
.1.3.6.1.4.1.17163.1.51.4.0.21009
ESXi memory overcommitted alarm cleared.
esxiLicenseExpiredClear
.1.3.6.1.4.1.17163.1.51.4.0.21010
ESXi license expired alarm cleared.
esxiLicenseExpiringClear
.1.3.6.1.4.1.17163.1.51.4.0.21011
ESXi license expiring alarm cleared.
esxiTrialLicenseClear
.1.3.6.1.4.1.17163.1.51.4.0.21012
ESXi trial license alarm cleared.
esxiVswitchMtuUnsupportedClear
.1.3.6.1.4.1.17163.1.51.4.0.21013
ESXi unsupported vSwitch MTU alarm cleared.
esxiInitialConfigFailedClear
.1.3.6.1.4.1.17163.1.51.4.0.21014
ESXi initial config failed alarm cleared.
memoryError
.1.3.6.1.4.1.17163.1.51.4.0.22
A memory error has been detected on the appliance
ipmi
.1.3.6.1.4.1.17163.1.51.4.0.23
An IPMI event has been detected on the appliance. Please check
the details in the alarm report on the web UI
configChange
.1.3.6.1.4.1.17163.1.51.4.0.24
A change has been made to the system's configuration
datastoreWrapped
.1.3.6.1.4.1.17163.1.51.4.0.25
The datastore has wrapped around
temperatureWarning
.1.3.6.1.4.1.17163.1.51.4.0.26
The system temperature has exceeded the threshold
temperatureCritical
.1.3.6.1.4.1.17163.1.51.4.0.27
The system temperature has reached a critical stage
cfConnFailure
.1.3.6.1.4.1.17163.1.51.4.0.28
Unable to establish connection with the specified neighbor
cfConnLostEos
.1.3.6.1.4.1.17163.1.51.4.0.29
Connection lost since end of stream was received from the
specified neighbor
cpuUtil
.1.3.6.1.4.1.17163.1.51.4.0.3
The average CPU utilization in the past minute has gone
above the acceptable threshold
cfConnLostErr
.1.3.6.1.4.1.17163.1.51.4.0.30
Connection lost due to an error communicating with the
specified neighbor
cfKeepaliveTimeout
.1.3.6.1.4.1.17163.1.51.4.0.31
Connection lost due to lack of keepalives from the specified
neighbor
cfAckTimeout
.1.3.6.1.4.1.17163.1.51.4.0.32
Connection lost due to lack of acks from the specified
neighbor
cfReadInfoTimeout
.1.3.6.1.4.1.17163.1.51.4.0.33
Timeout reading info from the specified neighbor
cfLatencyExceeded
.1.3.6.1.4.1.17163.1.51.4.0.34
Connection forwarding latency with the specified neighbor
has exceeded the threshold
sslPeeringSCEPAutoReenrollError
.1.3.6.1.4.1.17163.1.51.4.0.35
There is an error in the automatic re-enrollment of the SSL peering certificate
crlError
.1.3.6.1.4.1.17163.1.51.4.0.36
crl polling fails
datastoreSyncFailure
.1.3.6.1.4.1.17163.1.51.4.0.37
Data store sync has failed
secureVaultNeedsUnlock
.1.3.6.1.4.1.17163.1.51.4.0.38
SSL acceleration and the secure data store cannot be used until
the secure vault has been unlocked.
secureVaultNeedsRekey
.1.3.6.1.4.1.17163.1.51.4.0.39
If you wish to use a non-default password for the secure
vault, the password must be rekeyed. Please see
Knowledge Base article 5592 for more details.
pagingActivity
.1.3.6.1.4.1.17163.1.51.4.0.4
The system has been paging excessively (thrashing)
secureVaultInitError
.1.3.6.1.4.1.17163.1.51.4.0.40
An error was detected while initializing
the secure vault. Please contact customer support.
configSave
.1.3.6.1.4.1.17163.1.51.4.0.41
The current appliance configuration has been saved