OID reference
1.3.6.1.4.1.2076.10.17.1.5
The time the router will start accepting packets that have been created with this key.If the value is not set, then it will be taken as infinite and displayed as 9999-12-31,23:59:59.0. For example, Tuesday May 26, 1992 at 1:30:15 PM should be configured as, 1992-5-26,13:30:15.0
Identification
{1 3 6 1 4 1 2076 10 17 1 5}
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.
futOspfIfAuthKeyStartAccept OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The time the router will start accepting packets that have
been created with this key.If the value is not set, then it
will be taken as infinite and displayed as 9999-12-31,23:59:59.0.
For example, Tuesday May 26, 1992 at 1:30:15 PM should be
configured as, 1992-5-26,13:30:15.0"
::= { futOspfIfAuthEntry 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The time the router will start accepting packets that have been created with this key.If the value is not set, then it will be taken as infinite and displayed as 9999-12-31,23:59:59.0. For example, Tuesday May 26, 1992 at 1:30:15 PM should be configured as, 1992-5-26,13:30:15.0
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: futOspfIfAuthKeyStartAccept
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"futOspfIfAuthKeyStartAccept",
"OBJECT-TYPE",
"SYNTAX",
"DateAndTime",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The time the router will start accepting packets that have been created with this key.If the value is not set, then it will be taken as infinite and displayed as 9999-12-31,23:59:59.0. For example, Tuesday May 26, 1992 at 1:30:15 PM should be configured as, 1992-5-26,13:30:15.0\"",
"::=",
"{",
"futOspfIfAuthEntry",
"5",
"}"
],
"syntax_tree": [
[
"row",
"DateAndTime"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The time the router will start accepting packets that have been created with this key.If the value is not set, then it will be taken as infinite and displayed as 9999-12-31,23:59:59.0. For example, Tuesday May 26, 1992 at 1:30:15 PM should be configured as, 1992-5-26,13:30:15.0"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: FUTURESOFT-OSPF-MIB
See published definition above
{'OSPF-MIB': ['ospfVirtNbrEntry', 'AreaID', 'RouterID', 'BigMetric', 'Status', 'PositiveInteger', 'InterfaceIndex', 'TOSType', 'ospfRouterId', 'ospfNbrRtrId', 'ospfVirtIfEntry', 'ospfIfEntry'], 'SNMPv2-TC': ['TruthValue', 'RowStatus', 'DateAndTime', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'Gauge32', 'Integer32', 'IpAddress', 'enterprises', 'Unsigned32', 'NOTIFICATION-TYPE', 'TimeTicks']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.10.17.1.1 | futOspfIfAuthIpAddress | 0 | 0 | |
| 1.3.6.1.4.1.2076.10.17.1.2 | futOspfIfAuthAddressLessIf | 0 | 0 | |
| 1.3.6.1.4.1.2076.10.17.1.3 | futOspfIfAuthKeyId | 0 | 0 | |
| 1.3.6.1.4.1.2076.10.17.1.4 | futOspfIfAuthKey | 0 | 0 | |
| 1.3.6.1.4.1.2076.10.17.1.6 | futOspfIfAuthKeyStartGenerate | 0 | 0 | |
| 1.3.6.1.4.1.2076.10.17.1.7 | futOspfIfAuthKeyStopGenerate | 0 | 0 | |
| 1.3.6.1.4.1.2076.10.17.1.8 | futOspfIfAuthKeyStopAccept | 0 | 0 | |
| 1.3.6.1.4.1.2076.10.17.1.9 | futOspfIfAuthKeyStatus | 0 | 0 |