OID reference
1.3.6.1.4.1.3902.1015.190.3.3
The next EventIdList is used to synchronize events by a manager. Before the synchronization,a manager will get all the eventId via this mib object,and then to judge which event has not been in manager's database so as to tell the agent to resend the missing events.
Identification
{1 3 6 1 4 1 3902 1015 190 3 3}
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.3.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.
zxAnEventSyncNextEventIdList OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The next EventIdList is used to synchronize events by a manager.
Before the synchronization,a manager will get all the eventId via
this mib object,and then to judge which event has not been in
manager's database so as to tell the agent to resend the missing
events.
"
::= { zxAnEventSynchObjects 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The next EventIdList is used to synchronize events by a manager. Before the synchronization,a manager will get all the eventId via this mib object,and then to judge which event has not been in manager's database so as to tell the agent to resend the missing events.
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: zxAnEventSyncNextEventIdList
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"zxAnEventSyncNextEventIdList",
"OBJECT-TYPE",
"SYNTAX",
"OBJECT",
"IDENTIFIER",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The next EventIdList is used to synchronize events by a manager. Before the synchronization,a manager will get all the eventId via this mib object,and then to judge which event has not been in manager's database so as to tell the agent to resend the missing events. \"",
"::=",
"{",
"zxAnEventSynchObjects",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OBJECT IDENTIFIER",
null
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The next EventIdList is used to synchronize events by a manager. Before the synchronization,a manager will get all the eventId via this mib object,and then to judge which event has not been in manager's database so as to tell the agent to resend the missing events."
],
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.2 | zxAnEventSyncSpecificEvents | 0 | 0 | |
| 1.3.6.1.4.1.3902.1015.190.3.4 | zxAnEventSyncStartEventId | 0 | 0 |