OID reference
1.3.6.1.4.1.2076.10.20.1.1
Crypto authentication type to be used on the interface This object should be used to set SHA authentication along with ospfVirtIfAuthType in stdospf.mib
Identification
{1 3 6 1 4 1 2076 10 20 1 1}
| Value | Name |
|---|---|
| 1 | md5 |
| 2 | sha1 |
| 3 | sha224 |
| 4 | sha256 |
| 5 | sha384 |
| 6 | sha512 |
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 AUGMENTS row: ospfVirtIfEntry. Check that row's index definition for the instance suffix.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2076.10.20.1.1
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.
futOspfVirtIfCryptoAuthType OBJECT-TYPE
SYNTAX INTEGER {
md5(1),
sha1(2),
sha224(3),
sha256(4),
sha384(5),
sha512(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Crypto authentication type to be used on the interface This object
should be used to set SHA authentication along with ospfVirtIfAuthType
in stdospf.mib"
::= { futOspfVirtIfCryptoAuthEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Crypto authentication type to be used on the interface This object should be used to set SHA authentication along with ospfVirtIfAuthType in stdospf.mib
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: futOspfVirtIfCryptoAuthType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"futOspfVirtIfCryptoAuthType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"md5",
"(",
"1",
")",
",",
"sha1",
"(",
"2",
")",
",",
"sha224",
"(",
"3",
")",
",",
"sha256",
"(",
"4",
")",
",",
"sha384",
"(",
"5",
")",
",",
"sha512",
"(",
"6",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Crypto authentication type to be used on the interface This object should be used to set SHA authentication along with ospfVirtIfAuthType in stdospf.mib\"",
"::=",
"{",
"futOspfVirtIfCryptoAuthEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"md5",
1
],
[
"sha1",
2
],
[
"sha224",
3
],
[
"sha256",
4
],
[
"sha384",
5
],
[
"sha512",
6
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Crypto authentication type to be used on the interface This object should be used to set SHA authentication along with ospfVirtIfAuthType in stdospf.mib"
],
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