zxAnPmLogMaxRecordRows
ZTE-AN-PERF-MGMT-MIB ·
.1.3.6.1.4.1.3902.1015.189.2.2
Object
Performance metric log record rows.More than the max record number,the log file will be re-writted circulatory. It means when reache max record number,some performance metric static records will be losted.
Context
- MIB
- ZTE-AN-PERF-MGMT-MIB
- OID
.1.3.6.1.4.1.3902.1015.189.2.2- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- zxAnPerfLogMgmtObjects
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'ZTE-AN-PERF-MGMT-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZTE-AN-PERF-MGMT-MIB::zxAnPmLogMaxRecordRows.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'ZTE-AN-PERF-MGMT-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZTE-AN-PERF-MGMT-MIB::zxAnPmLogMaxRecordRows'
Syntax
- Source
- SNMPv2-SMIInteger32
- Base type
Integer32
Values & Constraints
Type Constraints
range: -2147483648..2147483647