OID reference
1.3.6.1.4.1.562.29.6.1.3.1.3
The local date and time when the message originated. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED.
Identification
{1 3 6 1 4 1 562 29 6 1 3 1 3}
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.
nnExtAlarmMessageDateAndTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The local date and time when the message originated.
Implementations MUST include the offset from UTC,
if available. Implementation in environments in which
the UTC offset is not available is NOT RECOMMENDED."
::= { nnExtAlarmMessageEntry 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The local date and time when the message originated. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED.
Nortel MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: nnExtAlarmMessageDateAndTime
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"nnExtAlarmMessageDateAndTime",
"OBJECT-TYPE",
"SYNTAX",
"DateAndTime",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The local date and time when the message originated. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED.\"",
"::=",
"{",
"nnExtAlarmMessageEntry",
"3",
"}"
],
"syntax_tree": [
[
"row",
"DateAndTime"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The local date and time when the message originated. Implementations MUST include the offset from UTC, if available. Implementation in environments in which the UTC offset is not available is NOT RECOMMENDED."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. Nortel support.
Module: NORTEL-ALARM-EXT-MIB
See published definition above
{'ALARM-MIB': ['ResourceId'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32'], 'NORTEL-GENERIC-MIB': ['nortelGenericMIBs'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'NOTIFICATION-LOG-MIB': ['nlmLogName', 'nlmLogIndex']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.562.29.6.1.3.1.1 | nnExtAlarmMessageResource | 0 | 0 | |
| 1.3.6.1.4.1.562.29.6.1.3.1.2 | nnExtAlarmMessageResourceDescription | 0 | 0 | |
| 1.3.6.1.4.1.562.29.6.1.3.1.4 | nnExtAlarmMessageDocumentationPointer | 0 | 0 | |
| 1.3.6.1.4.1.562.29.6.1.3.1.5 | nnExtAlarmMessageInfo | 0 | 0 |