OID reference
1.3.6.1.4.1.2076.151.1.9.1.3
The key ID for this key. This configured KeyID will be sent in the RIP update packet. This object enables the configuration of more than one key for an interface.
Identification
{1 3 6 1 4 1 2076 151 1 9 1 3}
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: fsMIRipContextId, fsMIRipCryptoAuthIfIndex, fsMIRipCryptoAuthAddress, fsMIRipCryptoAuthKeyId.
A query example is omitted because the source variants do not establish compatible read access.
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.
fsMIRipCryptoAuthKeyId OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The key ID for this key. This configured KeyID will be
sent in the RIP update packet. This object enables the
configuration of more than one key for an interface."
::= { fsMIRipCryptoAuthEntry 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The key ID for this key. This configured KeyID will be sent in the RIP update packet. This object enables the configuration of more than one key for an interface.
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: fsMIRipCryptoAuthKeyId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsMIRipCryptoAuthKeyId",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"255",
")",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The key ID for this key. This configured KeyID will be sent in the RIP update packet. This object enables the configuration of more than one key for an interface.\"",
"::=",
"{",
"fsMIRipCryptoAuthEntry",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The key ID for this key. This configured KeyID will be sent in the RIP update packet. This object enables the configuration of more than one key for an interface."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-MIRIP2-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['TruthValue', 'RowStatus', 'DisplayString', 'DateAndTime'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'IpAddress', 'Counter32', 'Integer32', 'enterprises', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.151.1.9.1.1 | fsMIRipCryptoAuthIfIndex | 0 | 0 | |
| 1.3.6.1.4.1.2076.151.1.9.1.2 | fsMIRipCryptoAuthAddress | 0 | 0 | |
| 1.3.6.1.4.1.2076.151.1.9.1.4 | fsMIRipCryptoAuthKey | 0 | 0 | |
| 1.3.6.1.4.1.2076.151.1.9.1.5 | fsMIRipCryptoKeyStartAccept | 0 | 0 | |
| 1.3.6.1.4.1.2076.151.1.9.1.6 | fsMIRipCryptoKeyStartGenerate | 0 | 0 | |
| 1.3.6.1.4.1.2076.151.1.9.1.7 | fsMIRipCryptoKeyStopGenerate | 0 | 0 | |
| 1.3.6.1.4.1.2076.151.1.9.1.8 | fsMIRipCryptoKeyStopAccept | 0 | 0 | |
| 1.3.6.1.4.1.2076.151.1.9.1.9 | fsMIRipCryptoKeyStatus | 0 | 0 |