ZHONE-FS-ALARM

        MIB module to define a trap, that will be used to forward alarms generated Fault Service.
    
Source file
ZHONE-FS-ALARM
Last revised
Identity
faultServiceAlarm
Base OID
1.3.6.1.4.1.5504.2.7.1
Imported Objects
SNMPv2-CONF NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-IDENTITY (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC TruthValue
Zhone zhoneZmsProduct
ZHONE-SYSTEM-MIB zhoneTrapsSequenceNumber zhoneTrapsSeverity zhoneTrapVersion
Net-SNMP examples using the zhone 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 'ZHONE-FS-ALARM' -M '/opt/observium/mibs/zhone:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZHONE-FS-ALARM::faultServiceAlarm'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ZHONE-FS-ALARM' -M '/opt/observium/mibs/zhone:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZHONE-FS-ALARM::faultServiceAlarm'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (21)
.1.3.6.1.4.1.5504.2.7.1
.1.3.6.1.4.1.5504.2.7.1.1
OctetString
.1.3.6.1.4.1.5504.2.7.1.1.1
.1.3.6.1.4.1.5504.2.7.1.1.10
OctetString
.1.3.6.1.4.1.5504.2.7.1.1.11
.1.3.6.1.4.1.5504.2.7.1.1.12
.1.3.6.1.4.1.5504.2.7.1.1.13
.1.3.6.1.4.1.5504.2.7.1.1.14
OctetString
.1.3.6.1.4.1.5504.2.7.1.1.2
OctetString
.1.3.6.1.4.1.5504.2.7.1.1.3
Enumeration
.1.3.6.1.4.1.5504.2.7.1.1.4
OctetString
.1.3.6.1.4.1.5504.2.7.1.1.5
.1.3.6.1.4.1.5504.2.7.1.1.6
Integer32
.1.3.6.1.4.1.5504.2.7.1.1.7
Integer32
.1.3.6.1.4.1.5504.2.7.1.1.8
.1.3.6.1.4.1.5504.2.7.1.1.9
.1.3.6.1.4.1.5504.2.7.1.2
.1.3.6.1.4.1.5504.2.7.1.2.0
.1.3.6.1.4.1.5504.2.7.1.3
.1.3.6.1.4.1.5504.2.7.1.3.1
.1.3.6.1.4.1.5504.2.7.1.4
Dependencies (14) 5 direct · 9 transitive 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