ASYNCOS-MAIL-MIB

Monitored by Observium
        MIB for Cisco IronPort Mail Gateway/Email Security Appliances
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Memory Polling Processors Sensors
Explore Observium network monitoring
Source file
ASYNCOS-MAIL-MIB
Last revised
Identity
asyncOSMailObjects
Base OID
1.3.6.1.4.1.15497.1.1.1
Imported Objects
IRONPORT-SMI asyncOSMail
SNMPv2-SMI Counter32 Gauge32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC DisplayString TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'ASYNCOS-MAIL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ASYNCOS-MAIL-MIB::asyncOSMailObjects'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ASYNCOS-MAIL-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ASYNCOS-MAIL-MIB::asyncOSMailObjects'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (52)
5 directly used by Observium
.1.3.6.1.4.1.15497.1.1.1
Integer32
.1.3.6.1.4.1.15497.1.1.1.1
.1.3.6.1.4.1.15497.1.1.1.10
.1.3.6.1.4.1.15497.1.1.1.10.1
Integer32
.1.3.6.1.4.1.15497.1.1.1.10.1.1
fanRPMs OBS ✓
.1.3.6.1.4.1.15497.1.1.1.10.1.2
fanName OBS ✓
.1.3.6.1.4.1.15497.1.1.1.10.1.3
.1.3.6.1.4.1.15497.1.1.1.11
.1.3.6.1.4.1.15497.1.1.1.12
.1.3.6.1.4.1.15497.1.1.1.12.1
Integer32
.1.3.6.1.4.1.15497.1.1.1.12.1.1
.1.3.6.1.4.1.15497.1.1.1.12.1.2
.1.3.6.1.4.1.15497.1.1.1.12.1.3
.1.3.6.1.4.1.15497.1.1.1.12.1.4
.1.3.6.1.4.1.15497.1.1.1.13
.1.3.6.1.4.1.15497.1.1.1.13.1
Integer32
.1.3.6.1.4.1.15497.1.1.1.13.1.1
.1.3.6.1.4.1.15497.1.1.1.13.1.2
.1.3.6.1.4.1.15497.1.1.1.13.1.3
.1.3.6.1.4.1.15497.1.1.1.13.1.4
.1.3.6.1.4.1.15497.1.1.1.14
.1.3.6.1.4.1.15497.1.1.1.15
.1.3.6.1.4.1.15497.1.1.1.16
.1.3.6.1.4.1.15497.1.1.1.17
.1.3.6.1.4.1.15497.1.1.1.18
.1.3.6.1.4.1.15497.1.1.1.18.1
Integer32
.1.3.6.1.4.1.15497.1.1.1.18.1.1
Enumeration
.1.3.6.1.4.1.15497.1.1.1.18.1.2
.1.3.6.1.4.1.15497.1.1.1.18.1.3
.1.3.6.1.4.1.15497.1.1.1.18.1.4
.1.3.6.1.4.1.15497.1.1.1.19
Integer32
.1.3.6.1.4.1.15497.1.1.1.2
.1.3.6.1.4.1.15497.1.1.1.20
.1.3.6.1.4.1.15497.1.1.1.21
.1.3.6.1.4.1.15497.1.1.1.22
Integer32
.1.3.6.1.4.1.15497.1.1.1.3
Integer32
.1.3.6.1.4.1.15497.1.1.1.4
Enumeration
.1.3.6.1.4.1.15497.1.1.1.5
Enumeration
.1.3.6.1.4.1.15497.1.1.1.6
Enumeration
.1.3.6.1.4.1.15497.1.1.1.7
.1.3.6.1.4.1.15497.1.1.1.8
.1.3.6.1.4.1.15497.1.1.1.8.1
Integer32
.1.3.6.1.4.1.15497.1.1.1.8.1.1
Enumeration
.1.3.6.1.4.1.15497.1.1.1.8.1.2
Enumeration
.1.3.6.1.4.1.15497.1.1.1.8.1.3
.1.3.6.1.4.1.15497.1.1.1.8.1.4
.1.3.6.1.4.1.15497.1.1.1.9
.1.3.6.1.4.1.15497.1.1.1.9.1
Integer32
.1.3.6.1.4.1.15497.1.1.1.9.1.1
.1.3.6.1.4.1.15497.1.1.1.9.1.2
temperatureName OBS ✓
.1.3.6.1.4.1.15497.1.1.1.9.1.3
.1.3.6.1.4.1.15497.1.1.2
Dependencies (3) 3 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. IRONPORT-SMIcisco
  3. SNMPv2-TCrfc
  4. ASYNCOS-MAIL-MIBciscoselected
Notifications / Traps (12)
NameOIDDescription
.1.3.6.1.4.1.15497.1.1.2.1
Memory or queue utilization caused system to enter resource
conservation mode.
.1.3.6.1.4.1.15497.1.1.2.10
A cpuUtilizationExceeded notification is sent when the
value in perCentCPUUtilization has exceeded the configured
CPU usage threshold. The percentage that exceeded the
threshold in perCentCPUUtilization is returned via the
notification.
.1.3.6.1.4.1.15497.1.1.2.11
A hsmInitializationFailure notification is sent when the
Hardware Security Module card cannot be initialized. The
initialization error in hsmErrorReason is returned via
the notification.
.1.3.6.1.4.1.15497.1.1.2.12
A hsmResetLoginFailure notification is sent when the
Hardware Security Module card is reset due to multiple
Crypto Officer login failures. The reset login error in
hsmErrorReason is returned via the notification.
.1.3.6.1.4.1.15497.1.1.2.2
A powerSupplyStatusChange notification is sent when power
supply with powerSupplyName changes states, as per one of
the states available in powerSupplyStatus. This
notification contains the opaque type for powerSupplyName
of the power supply which has changed state.
.1.3.6.1.4.1.15497.1.1.2.3
A highTemperature notification is sent when the temperature
of an instrumented sensor in the chassis has exceeded vendor
defined specifications. This notification contains the
opaque type for the temperatureName of the sensor which has
failed.
.1.3.6.1.4.1.15497.1.1.2.4
A fanFailure notification is sent when the speed of the fan
is not operating per the vendor defined specifications, as
discussed in fanRPMs. This notification contains the opaque
type for the fanName of the fan which has failed.
.1.3.6.1.4.1.15497.1.1.2.5
A keyExpiration notification is sent when the corresponding
Feature Key is pending expiration or has expired. This
notification contains the opaque type for the keyDescription
of the Feature Key that is pending expiration or has
expired.
.1.3.6.1.4.1.15497.1.1.2.6
An updateFailure notification is sent when a service fails
to update properly. This notification contains the opaque
type for the updateServiceName of the update service that
has failed.
.1.3.6.1.4.1.15497.1.1.2.7
A raidStatusChange notification is sent when drive with
raidID changes states, as per one of the states available
in raidStatus. This notification contains the opaque type
for raidID of the drive which has changed state.
.1.3.6.1.4.1.15497.1.1.2.8
A connectivityFailure notification is sent when the URL
denoted by configured connectionURL is unreachable, or the
request returned an HTTP code was not between 200,
inclusive, and 300, exclusive. The connectionURL configured
is returned when the notification is triggered.
.1.3.6.1.4.1.15497.1.1.2.9
A memoryUtilizationExceeded notification is sent when the
value in perCentMemoryUtilization has exceeded the
configured memory usage threshold. The percentage that
exceeded the threshold in perCentMemoryUtilization is
returned via the notification.