OID reference
1.3.6.1.4.1.3902.1004.37.1.2
It is used to indicate the current EventId. When the agent start,this object is 0 and the agent should send a trap to manager to request which eventId should be used by this agent.After time out,the agent begin to use it to manage the event.
Identification
{1 3 6 1 4 1 3902 1004 37 1 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.1004.37.1.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.
zxDslEventCurrentEventId OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"It is used to indicate the current EventId.
When the agent start,this object is 0 and the agent should send a
trap to manager to request which eventId should be used by this
agent.After time out,the agent begin to use it to manage the event."
DEFVAL { 0 }
::= { zxDslEventObjects 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
It is used to indicate the current EventId. When the agent start,this object is 0 and the agent should send a trap to manager to request which eventId should be used by this agent.After time out,the agent begin to use it to manage the event.
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: zxDslEventCurrentEventId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxDslEventCurrentEventId",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"It is used to indicate the current EventId. When the agent start,this object is 0 and the agent should send a trap to manager to request which eventId should be used by this agent.After time out,the agent begin to use it to manage the event.\"",
"DEFVAL",
"{",
"0",
"}",
"::=",
"{",
"zxDslEventObjects",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"It is used to indicate the current EventId. When the agent start,this object is 0 and the agent should send a trap to manager to request which eventId should be used by this agent.After time out,the agent begin to use it to manage the event."
],
null,
null,
null,
[
"DEFVAL",
0
]
]
}Vendor MIB copy from the Observium Community archive. ZTE support.
Module: ZTE-DSL-EVENT-MIB
See published definition above
{'SNMPv2-TC': ['RowStatus', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'IpAddress', 'TimeTicks', 'Counter32', 'Gauge32', 'Integer32', 'Unsigned32'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'ZTE-DSL-MIB': ['zte', 'zxDsl'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3902.1004.37.1.1 | zxDslTrapSendEnable | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.37.1.3 | zxDslEventConfirmEventId | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.37.1.4 | zxDslEventSynchUnconfirmedEvents | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.37.1.5 | zxDslEventCurrUnconfirmedEventCounter | 0 | 0 | |
| 1.3.6.1.4.1.3902.1004.37.1.6 | zxDslEventNmsHelloTrapMgmt | 2 | 2 |