ZTE-BFD-MIB

        
    
Source file
ZTE-BFD-MIB
Last revised
Identity
zteBfdMib
Base OID
1.3.6.1.4.1.3902.3.322
Imported Objects
INET-ADDRESS-MIB InetAddress InetAddressType
SNMPv2-SMI Counter32 enterprises MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the zte 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 'ZTE-BFD-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZTE-BFD-MIB::zteBfdMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ZTE-BFD-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZTE-BFD-MIB::zteBfdMib'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (81)
zte
.1.3.6.1.4.1.3902
.1.3.6.1.4.1.3902.3
.1.3.6.1.4.1.3902.3.322
.1.3.6.1.4.1.3902.3.322.0
.1.3.6.1.4.1.3902.3.322.1
.1.3.6.1.4.1.3902.3.322.1.1
Enumeration
.1.3.6.1.4.1.3902.3.322.1.1.1
.1.3.6.1.4.1.3902.3.322.1.1.2
.1.3.6.1.4.1.3902.3.322.1.1.3
.1.3.6.1.4.1.3902.3.322.1.2
.1.3.6.1.4.1.3902.3.322.1.2.1
.1.3.6.1.4.1.3902.3.322.1.2.1.1
Enumeration
.1.3.6.1.4.1.3902.3.322.1.2.1.10
.1.3.6.1.4.1.3902.3.322.1.2.1.11
.1.3.6.1.4.1.3902.3.322.1.2.1.12
.1.3.6.1.4.1.3902.3.322.1.2.1.13
.1.3.6.1.4.1.3902.3.322.1.2.1.14
.1.3.6.1.4.1.3902.3.322.1.2.1.15
.1.3.6.1.4.1.3902.3.322.1.2.1.16
.1.3.6.1.4.1.3902.3.322.1.2.1.17
.1.3.6.1.4.1.3902.3.322.1.2.1.18
.1.3.6.1.4.1.3902.3.322.1.2.1.19
.1.3.6.1.4.1.3902.3.322.1.2.1.2
.1.3.6.1.4.1.3902.3.322.1.2.1.20
.1.3.6.1.4.1.3902.3.322.1.2.1.21
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.22
.1.3.6.1.4.1.3902.3.322.1.2.1.23
.1.3.6.1.4.1.3902.3.322.1.2.1.24
.1.3.6.1.4.1.3902.3.322.1.2.1.25
.1.3.6.1.4.1.3902.3.322.1.2.1.26
.1.3.6.1.4.1.3902.3.322.1.2.1.27
.1.3.6.1.4.1.3902.3.322.1.2.1.28
Enumeration
.1.3.6.1.4.1.3902.3.322.1.2.1.29
Enumeration
.1.3.6.1.4.1.3902.3.322.1.2.1.3
.1.3.6.1.4.1.3902.3.322.1.2.1.30
Enumeration
.1.3.6.1.4.1.3902.3.322.1.2.1.31
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.32
Enumeration
.1.3.6.1.4.1.3902.3.322.1.2.1.33
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.34
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.35
.1.3.6.1.4.1.3902.3.322.1.2.1.36
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.37
.1.3.6.1.4.1.3902.3.322.1.2.1.38
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.39
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.4
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.40
Enumeration
.1.3.6.1.4.1.3902.3.322.1.2.1.41
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.5
Unsigned32
.1.3.6.1.4.1.3902.3.322.1.2.1.6
Enumeration
.1.3.6.1.4.1.3902.3.322.1.2.1.7
.1.3.6.1.4.1.3902.3.322.1.2.1.8
.1.3.6.1.4.1.3902.3.322.1.2.1.9
.1.3.6.1.4.1.3902.3.322.1.3
.1.3.6.1.4.1.3902.3.322.1.3.1
.1.3.6.1.4.1.3902.3.322.1.3.1.1
.1.3.6.1.4.1.3902.3.322.1.3.1.10
.1.3.6.1.4.1.3902.3.322.1.3.1.11
.1.3.6.1.4.1.3902.3.322.1.3.1.2
.1.3.6.1.4.1.3902.3.322.1.3.1.3
.1.3.6.1.4.1.3902.3.322.1.3.1.4
.1.3.6.1.4.1.3902.3.322.1.3.1.5
.1.3.6.1.4.1.3902.3.322.1.3.1.6
.1.3.6.1.4.1.3902.3.322.1.3.1.7
.1.3.6.1.4.1.3902.3.322.1.3.1.8
.1.3.6.1.4.1.3902.3.322.1.3.1.9
.1.3.6.1.4.1.3902.3.322.1.4
.1.3.6.1.4.1.3902.3.322.1.4.1
.1.3.6.1.4.1.3902.3.322.1.4.1.1
.1.3.6.1.4.1.3902.3.322.1.4.1.10
.1.3.6.1.4.1.3902.3.322.1.4.1.11
Integer32
.1.3.6.1.4.1.3902.3.322.1.4.1.12
Integer32
.1.3.6.1.4.1.3902.3.322.1.4.1.13
Integer32
.1.3.6.1.4.1.3902.3.322.1.4.1.14
.1.3.6.1.4.1.3902.3.322.1.4.1.2
Enumeration
.1.3.6.1.4.1.3902.3.322.1.4.1.3
.1.3.6.1.4.1.3902.3.322.1.4.1.4
.1.3.6.1.4.1.3902.3.322.1.4.1.5
.1.3.6.1.4.1.3902.3.322.1.4.1.6
.1.3.6.1.4.1.3902.3.322.1.4.1.7
.1.3.6.1.4.1.3902.3.322.1.4.1.8
.1.3.6.1.4.1.3902.3.322.1.4.1.9
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. SNMPv2-TCrfc
  3. INET-ADDRESS-MIBrfc
  4. ZTE-BFD-MIBzteselected
Type Definitions (4)
OctetString
Enumeration
noDiagnostic(1)
controlDetectionTimeExpired(2)
echoFunctionFailed(3)
neighborSignaledSessionDown(4)
forwardingPlaneReset(5)
pathDown(6)
concatenatedPathDown(7)
administrativelyDown(8)
reverseConcatenatedPathDown(9)
Unsigned32 range: 1..4294967295
Unsigned32 range: 1..4294967295
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.3902.3.322.0.1
This notification is generated when the
zxr10BfdSessState object for one or more contiguous
entries in zxr10BfdSessTable are about to enter the up(4)
state from some other state. The included values of
zxr10BfdSessDiag MUST both be set equal to this
new state (i.e: up(4)). The two instances of
zxr10BfdSessDiag in this notification indicate the range
of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the
instance identifiers of these two objects. For the
cases where a contiguous range of sessions
have transitioned into the up(4) state at roughly
the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in
an effort to minimize the emission of a large number
of notifications. If a notification has to be
issued for just a single zxr10BfdSessEntry, then
the instance identifier (and values) of the two
Zxr10BfdSessIndexTC objects MUST be the identical.
.1.3.6.1.4.1.3902.3.322.0.2
This notification is generated when the
zxr10BfdSessState object for one or more contiguous
entries in zxr10BfdSessTable are about to enter the down(2)
or adminDown(1) states from some other state. The included
values of zxr10BfdSessDiag MUST both be set equal to this
new state (i.e: down(2) or adminDown(1)). The two instances
of zxr10BfdSessDiag in this notification indicate the range
of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the
instance identifiers of these two objects. For
cases where a contiguous range of sessions
have transitioned into the down(2) or adminDown(1) states
at roughly the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in
an effort to minimize the emission of a large number
of notifications. If a notification has to be
issued for just a single zxr10BfdSessEntry, then
the instance identifier (and values) of the two
Zxr10BfdSessIndexTC objects MUST be the identical.