OID reference
1.3.6.1.4.1.34751.2.9.5
Interval between reissuing message in milliseconds. Minimum non-zero setting is 10000. 0 will cause the routine to choose its own intervals becoming more frequent as MessageDuration gets close to expiring. 2hr, 1hr, 30min, 5min, 1min
Identification
{1 3 6 1 4 1 34751 2 9 5}
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.34751.2.9.5.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.
nmstsMsgIntervaltim OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Interval between reissuing message in
milliseconds. Minimum non-zero setting is
10000. 0 will cause the routine to choose its
own intervals becoming more frequent as
MessageDuration gets close to expiring. 2hr,
1hr, 30min, 5min, 1min"
::= { nmslts 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Interval between reissuing message in milliseconds. Minimum non-zero setting is 10000. 0 will cause the routine to choose its own intervals becoming more frequent as MessageDuration gets close to expiring. 2hr, 1hr, 30min, 5min, 1min
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: nmstsMsgIntervaltim
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"nmstsMsgIntervaltim",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Interval between reissuing message in milliseconds. Minimum non-zero setting is 10000. 0 will cause the routine to choose its own intervals becoming more frequent as MessageDuration gets close to expiring. 2hr, 1hr, 30min, 5min, 1min\"",
"::=",
"{",
"nmslts",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Interval between reissuing message in milliseconds. Minimum non-zero setting is 10000. 0 will cause the routine to choose its own intervals becoming more frequent as MessageDuration gets close to expiring. 2hr, 1hr, 30min, 5min, 1min"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: QTECH-NMS-TS
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress'], 'RFC1213-MIB': ['DisplayString'], 'QTECH-NMS-SMI': ['nmslocal']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.34751.2.9.1 | nmstsLines | 0 | 0 | |
| 1.3.6.1.4.1.34751.2.9.2 | nmsltsLineTable | 1 | 22 | |
| 1.3.6.1.4.1.34751.2.9.3 | nmsltsLineSessionTable | 1 | 9 | |
| 1.3.6.1.4.1.34751.2.9.4 | nmstsMsgTtyLine | 0 | 0 | |
| 1.3.6.1.4.1.34751.2.9.6 | nmstsMsgDuration | 0 | 0 | |
| 1.3.6.1.4.1.34751.2.9.7 | nmstsMsgText | 0 | 0 | |
| 1.3.6.1.4.1.34751.2.9.8 | nmstsMsgTmpBanner | 0 | 0 | |
| 1.3.6.1.4.1.34751.2.9.9 | nmstsMsgSend | 0 | 0 | |
| 1.3.6.1.4.1.34751.2.9.10 | nmstsClrTtyLine | 0 | 0 |