OID reference
1.3.6.1.4.1.3902.1015.189.2.2
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.
Identification
{1 3 6 1 4 1 3902 1015 189 2 2}
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.3902.1015.189.2.2.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
zxAnPmLogMaxRecordRows OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"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."
::= { zxAnPerfLogMgmtObjects 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
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.
ZTE MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: zxAnPmLogMaxRecordRows
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxAnPmLogMaxRecordRows",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"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.\"",
"::=",
"{",
"zxAnPerfLogMgmtObjects",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"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."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. ZTE support.
Module: ZTE-AN-PERF-MGMT-MIB
See published definition above
{'SNMPv2-TC': ['RowStatus', 'DisplayString', 'TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter64'], 'ZTE-AN-TC-MIB': ['zxAn']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3902.1015.189.2.1 | zxAnPmLogAdminStatus | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.3 | zxAnPmLogManualReportAction | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.4 | zxAnPmLogManualReportStatus | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.5 | zxAnPmLogAutoReportMetric | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.6 | zxAnPmLogAutoReportInterval | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.7 | zxAnPmLogReportFtpHost | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.8 | zxAnPmLogReportFtpPath | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.9 | zxAnPmLogReportFtpUser | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.10 | zxAnPmLogReportFtpPassword | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.189.2.31 | zxAnPmLogCtrlTable | 1 | 5 |