OID reference
1.3.6.1.4.1.119.2.3.69.501.2.1.6.3
the ip address which triggered the control event. The ip address is normally recognized by source ip address of SET-REQUEST. But when 'ipeAccessFrom' is set in the SET-REQUEST, this object reports same value of 'ipeAccessFrom'.
Identification
{1 3 6 1 4 1 119 2 3 69 501 2 1 6 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.119.2.3.69.501.2.1.6.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.
eventRecordAccessFrom OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"the ip address which triggered the control event. The ip address
is normally recognized by source ip address of SET-REQUEST. But
when 'ipeAccessFrom' is set in the SET-REQUEST, this object
reports same value of 'ipeAccessFrom'."
::= { ipeTrapControlVars 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
the ip address which triggered the control event. The ip address is normally recognized by source ip address of SET-REQUEST. But when 'ipeAccessFrom' is set in the SET-REQUEST, this object reports same value of 'ipeAccessFrom'.
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: current.
Names: eventRecordAccessFrom
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"eventRecordAccessFrom",
"OBJECT-TYPE",
"SYNTAX",
"IpAddress",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"the ip address which triggered the control event. The ip address is normally recognized by source ip address of SET-REQUEST. But when 'ipeAccessFrom' is set in the SET-REQUEST, this object reports same value of 'ipeAccessFrom'.\"",
"::=",
"{",
"ipeTrapControlVars",
"3",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"IpAddress",
null
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"the ip address which triggered the control event. The ip address is normally recognized by source ip address of SET-REQUEST. But when 'ipeAccessFrom' is set in the SET-REQUEST, this object reports same value of 'ipeAccessFrom'."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: IPE-COMMON-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['DateAndTime', 'DisplayString', 'MacAddress', 'RowStatus', 'TEXTUAL-CONVENTION', 'TruthValue'], 'BRIDGE-MIB': ['BridgeId'], 'SNMPv2-SMI': ['Counter32', 'Counter64', 'enterprises', 'Gauge32', 'Integer32', 'IpAddress', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Opaque', 'Unsigned32']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.119.2.3.69.501.2.1.6.1 | eventRecordUserName | 0 | 0 | |
| 1.3.6.1.4.1.119.2.3.69.501.2.1.6.2 | eventRecordAccessType | 0 | 0 |