ZXR10-CLI-MIB

        
    
Source file
ZXR10-CLI-MIB
Last revised
Identity
zxr10CLIMIB
Base OID
1.3.6.1.4.1.3902.3.6000.52
Imported Objects
IPV6-TC Ipv6Address
SNMPv2-SMI enterprises Integer32 IpAddress MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DateAndTime DisplayString TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the zte-ng 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 'ZXR10-CLI-MIB' -M '/opt/observium/mibs/zte-ng:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZXR10-CLI-MIB::zxr10CLIMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ZXR10-CLI-MIB' -M '/opt/observium/mibs/zte-ng:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZXR10-CLI-MIB::zxr10CLIMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (32)
zte
.1.3.6.1.4.1.3902
.1.3.6.1.4.1.3902.3
.1.3.6.1.4.1.3902.3.6000
.1.3.6.1.4.1.3902.3.6000.52
.1.3.6.1.4.1.3902.3.6000.52.1
Enumeration
.1.3.6.1.4.1.3902.3.6000.52.1.1
.1.3.6.1.4.1.3902.3.6000.52.1.2
.1.3.6.1.4.1.3902.3.6000.52.1.2.1
.1.3.6.1.4.1.3902.3.6000.52.1.2.2
.1.3.6.1.4.1.3902.3.6000.52.1.2.3
.1.3.6.1.4.1.3902.3.6000.52.1.2.4
percentInteger32
.1.3.6.1.4.1.3902.3.6000.52.1.2.5
.1.3.6.1.4.1.3902.3.6000.52.1.3
MinutesInteger32
.1.3.6.1.4.1.3902.3.6000.52.1.3.1
SecondsInteger32
.1.3.6.1.4.1.3902.3.6000.52.1.3.2
percentInteger32
.1.3.6.1.4.1.3902.3.6000.52.1.3.3
MinutesInteger32
.1.3.6.1.4.1.3902.3.6000.52.1.3.4
.1.3.6.1.4.1.3902.3.6000.52.1.4
.1.3.6.1.4.1.3902.3.6000.52.1.4.1
Enumeration
.1.3.6.1.4.1.3902.3.6000.52.1.4.10
Enumeration
.1.3.6.1.4.1.3902.3.6000.52.1.4.11
.1.3.6.1.4.1.3902.3.6000.52.1.4.12
.1.3.6.1.4.1.3902.3.6000.52.1.4.13
.1.3.6.1.4.1.3902.3.6000.52.1.4.2
Enumeration
.1.3.6.1.4.1.3902.3.6000.52.1.4.3
.1.3.6.1.4.1.3902.3.6000.52.1.4.4
.1.3.6.1.4.1.3902.3.6000.52.1.4.5
Unsigned32
.1.3.6.1.4.1.3902.3.6000.52.1.4.6
.1.3.6.1.4.1.3902.3.6000.52.1.4.7
.1.3.6.1.4.1.3902.3.6000.52.1.4.8
.1.3.6.1.4.1.3902.3.6000.52.1.4.9
.1.3.6.1.4.1.3902.3.6000.52.1.5
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. IPV6-TCrfc
  4. ZXR10-CLI-MIBzte-ngselected
Type Definitions (2)
Enumeration
noError(1)
commonError(2)
openFileFailed(3)
writeFileFailed(4)
queryConfilict(5)
invalidFileName(6)
pathForbidden(7)
invalidPathLevel(8)
createDirectoryFailed(9)
moduleUnloaded(10)
The reason of a saving configuration operation failed.
The description of each reason is given below:
noError: this status signifies that saving
configuration operation is never done, or
the reason data has been aging.
commonError: this status signifies that the common error
happened during saving configuration operation.
openFileFailed: opening configuration file failed.
writeFileFailed: writing configuration file failed.
queryConflict: the configuration is changed during saving.
invalidFileName: the saving configuration file name
is invalid.
pathForbidden: the path of saving configuration file
is forbidden for write.
invalidPathLevel: the path is deeper than 10 levels.
createDirectoryFailed: creating destination directory failed.
moduleUnloaded: the module has been unloaded
during the execution.
Enumeration
doWrite(1)
idle(2)
running(3)
success(4)
failed(5)
The CLISaveConfigStatus textual convention is
used to save configuration, and is used as
the status of a saving configuration operation.
After saving configuration finished for five minutes,
status data will be aging.

The description of each status is given below:
doWrite: this value is supplied to save configuration.
This value may be written, but is never be read.
idle: this status signifies that saving
configuration operation is never done, or
the status data has been aging.
This value may be read, but is never be written.
running: this status signifies that the saving
configuration operation is running.
This value may be read, but is never be written.
success: the status signifies that the saving
configuration operation is successfully completed.
This value may be read, but is never be written.
failed: the saving configuration operation is failed.
This value may be read, but is never be written.