OID reference
1.3.6.1.4.1.3902.1015.190.3.2
It is used to excute a process to report the specific events again. This object is like a style of OID.And each number of OID is the eventId. When this object is set,the agent should resend traps of these eventId.And these traps still need to be confirmed by a manager.
Identification
{1 3 6 1 4 1 3902 1015 190 3 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.190.3.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.
zxAnEventSyncSpecificEvents OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"It is used to excute a process to report the specific events
again.
This object is like a style of OID.And each number of OID is the
eventId.
When this object is set,the agent should resend traps of these
eventId.And these traps still need to be confirmed by a manager."
::= { zxAnEventSynchObjects 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
It is used to excute a process to report the specific events again. This object is like a style of OID.And each number of OID is the eventId. When this object is set,the agent should resend traps of these eventId.And these traps still need to be confirmed by a manager.
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: zxAnEventSyncSpecificEvents
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxAnEventSyncSpecificEvents",
"OBJECT-TYPE",
"SYNTAX",
"OBJECT",
"IDENTIFIER",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"It is used to excute a process to report the specific events again. This object is like a style of OID.And each number of OID is the eventId. When this object is set,the agent should resend traps of these eventId.And these traps still need to be confirmed by a manager.\"",
"::=",
"{",
"zxAnEventSynchObjects",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OBJECT IDENTIFIER",
null
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"It is used to excute a process to report the specific events again. This object is like a style of OID.And each number of OID is the eventId. When this object is set,the agent should resend traps of these eventId.And these traps still need to be confirmed by a manager."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. ZTE support.
Module: ZTE-AN-EVNET-MIB
See published definition above
{'SNMPv2-TC': ['RowStatus', 'DisplayString', 'TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'IpAddress', 'NOTIFICATION-TYPE', 'enterprises'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.3902.1015.190.3.1 | zxAnEventSyncUnconfirmedEvents | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.190.3.3 | zxAnEventSyncNextEventIdList | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.190.3.4 | zxAnEventSyncStartEventId | 0 | 0 |