OID reference

logAlarmEventReqId

1.3.6.1.4.1.2865.1.7.3.1.5

Description

This variable contains either the alarm, event or user request identifier associated with the log entry. For alarms or events, this identifier is the same identifier used in the notifEventIdTable or notifActiveAlarmTable, respectively. This identifier is always the same as that which is sent in the enterprise-specific…

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.2865.1.7.3.1 (logTableEntry)
Node code: 5
Node name: logAlarmEventReqId
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.2865.1.7.3.1.5
URN notation: urn:oid:1.3.6.1.4.1.2865.1.7.3.1.5
Type: OBJECT-TYPE

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 2865 1 7 3 1 5}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) optera-solutions(2865) optera-80(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) optera-solutions(2865) optical-metro-5000(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) optical-metro(2865) optera-80(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) optical-metro(2865) optical-metro-5000(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) optera-solutions(2865) optera-80(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) optera-solutions(2865) optical-metro-5000(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) optical-metro(2865) optera-80(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) optical-metro(2865) optical-metro-5000(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) optera-solutions(2865) optera-80(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) optera-solutions(2865) optical-metro-5000(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) optical-metro(2865) optera-80(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) optical-metro(2865) optical-metro-5000(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) optera-solutions(2865) optera-80(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) optera-solutions(2865) optical-metro-5000(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) optical-metro(2865) optera-80(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) optical-metro(2865) optical-metro-5000(1) log(7) logTable(3) logTableEntry(1) logAlarmEventReqId(5)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/2865/1/7/3/1/5
/ISO/Identified-Organization/6/1/4/1/2865/1/7/3/1/5
/ISO/3/6/1/4/1/2865/1/7/3/1/5

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/optera-solutions/optera-80/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/enterprise/optera-solutions/optical-metro-5000/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/enterprise/optical-metro/optera-80/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/enterprise/optical-metro/optical-metro-5000/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/enterprises/optera-solutions/optera-80/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/enterprises/optera-solutions/optical-metro-5000/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/enterprises/optical-metro/optera-80/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/enterprises/optical-metro/optical-metro-5000/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/ldap-enterprise/optera-solutions/optera-80/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/ldap-enterprise/optera-solutions/optical-metro-5000/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/ldap-enterprise/optical-metro/optera-80/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/ldap-enterprise/optical-metro/optical-metro-5000/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/vendor-objects/optera-solutions/optera-80/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/vendor-objects/optera-solutions/optical-metro-5000/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/vendor-objects/optical-metro/optera-80/log/logTable/logTableEntry/logAlarmEventReqId
/iso/identified-organization/dod/internet/private/vendor-objects/optical-metro/optical-metro-5000/log/logTable/logTableEntry/logAlarmEventReqId
Additional combinations skipped.

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-only
Status in MIB: mandatory

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition. The index encoding is not inferred here.

Published row index: logIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2865.1.7.3.1.5

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.

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This variable contains either the alarm, event or user
request identifier associated with the log entry. For
alarms or events, this identifier is the same identifier
used in the notifEventIdTable or notifActiveAlarmTable,
respectively. This identifier is always the same as that
which is sent in the enterprise-specific trap for the
logged event.

Sources for this description

MIBdepot

Parsed from nortel-optera-pub.mib.txt · nortel · NORTEL-OPTERA-PUB-MIB

Source file: Download nortel-optical-metro-pub.mib.txt

Source file: Download nortel-optera-pub.mib.txt

Browse all files from MIBdepot

Historical records

Additional source information

Information from OID Repository

Vendor: Nortel Networks
Module: NORTEL-OPTERA-PUB-MIB (nortel-optera-pub.mib)
Type: TABULAR
Access: read-only
Syntax: INTEGER

Automatically extracted from www.mibdepot.com

Information from MIBdepot

logAlarmEventReqId OBJECT-TYPE
    SYNTAX    INTEGER
    ACCESS    read-only
    STATUS    mandatory
    DESCRIPTION
              "This variable contains either the alarm, event or user
              request identifier associated with the log entry.  For
              alarms or events, this identifier is the same identifier
              used in the notifEventIdTable or notifActiveAlarmTable,
              respectively.  This identifier is always the same as that
              which is sent in the enterprise-specific trap for the
              logged event."
    ::= { logTableEntry 5 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2865)

MacLeod Kyle

Siblings (12)

OID	Name	Description
1.3.6.1.4.1.2865.1.7.3.1.1	logIndex	A unique entry in the log table. As new entries are added to the log, this index will increase to the maximum size of Counter, t…
1.3.6.1.4.1.2865.1.7.3.1.2	logTimeStamp	The time and date this log entry was created. This timestamp matches the timestamp sent out in the trap which occurred to inform…
1.3.6.1.4.1.2865.1.7.3.1.3	logClass	This variable identifies the class of log entry, i.e., whether this log entry is for an alarm, an event, or a user provisioning r…
1.3.6.1.4.1.2865.1.7.3.1.4	logSlotNum	The slot number related to this log entry, if applicable. This variable is only applicable if the event is an alarm state change …
1.3.6.1.4.1.2865.1.7.3.1.6	logAlarmState	This variable contains the alarm state which caused the notification to occur. This column is only applicable in the case where …
1.3.6.1.4.1.2865.1.7.3.1.7	logAlarmSeverity	This variable contains the alarm severity associated with the alarm which caused the notification to occur. This column is only …
1.3.6.1.4.1.2865.1.7.3.1.8	logDescr	A textual description of the logged event. This description is set according to the logClass, as follows: alarm: the descriptio…
1.3.6.1.4.1.2865.1.7.3.1.9	logUserRequestRc	The return code from the user request, if applicable. The manager can consult this log entry to find out why a set request failed…
1.3.6.1.4.1.2865.1.7.3.1.10	logCardType	The provisioned card type related to this log entry, if applicable. This variable is only applicable if the event is an alarm sta…
1.3.6.1.4.1.2865.1.7.3.1.11	logLocationDescr	A comma-separated string describing the location information about this alarm. It will be in the following format: slot:<>, port:<…
1.3.6.1.4.1.2865.1.7.3.1.12	logOptSysId	Optical System Id descriptor.
1.3.6.1.4.1.2865.1.7.3.1.13	logUpsnNum	This shall be applicable if the log was generated while the UPSN feature was turned on the shelf; otherwise, it shall be zero.