OID reference
1.3.6.1.4.1.3955.2.4.1.1.18
Authentication, determines a method to authenticate the ESP packets. Either MD5 or SHA may be selected. Notice that both sides must use the same Authentication method.
Identification
{1 3 6 1 4 1 3955 2 4 1 1 18}
| Value | Name |
|---|---|
| 0 | disable |
| 1 | md5 |
| 2 | sha |
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.
In LINKSYS-MODEL-MIB, the row index vpnTunnelIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.3955.2.4.1.1.18.<vpnTunnelIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
Published row index: vpnTunnelIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.3955.2.4.1.1.18
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.
vpnEspAuth OBJECT-TYPE
SYNTAX INTEGER { disable(0), md5(1), sha(2) }
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Authentication, determines a method to authenticate
the ESP packets. Either MD5 or SHA may be selected.
Notice that both sides must use the same Authentication
method."
::= { vpnIpsecEntry 18 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Authentication, determines a method to authenticate the ESP packets. Either MD5 or SHA may be selected. Notice that both sides must use the same Authentication method.
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: mandatory.
Names: vpnEspAuth
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vpnEspAuth",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"disable",
"(",
"0",
")",
",",
"md5",
"(",
"1",
")",
",",
"sha",
"(",
"2",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Authentication, determines a method to authenticate the ESP packets. Either MD5 or SHA may be selected. Notice that both sides must use the same Authentication method.\"",
"::=",
"{",
"vpnIpsecEntry",
"18",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"disable",
0
],
[
"md5",
1
],
[
"sha",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Authentication, determines a method to authenticate the ESP packets. Either MD5 or SHA may be selected. Notice that both sides must use the same Authentication method."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: LINKSYS-MODEL-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress'], 'RFC1213-MIB': ['DisplayString', 'PhysAddress']}Related source files and packages:
Registration