OID reference
1.3.6.1.4.1.2076.143.1.1.1.41
This object is used for configuring the IKE version - IKev1 (1) or IKEv2 (2) protocol to be used for key negotiation
Identification
{1 3 6 1 4 1 2076 143 1 1 1 41}
| Value | Name |
|---|---|
| 1 | ikev1 |
| 2 | ikev2 |
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: fsVpnPolicyName.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2076.143.1.1.1.41
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.
fsVpnIkeVersion OBJECT-TYPE
SYNTAX INTEGER {
ikev1 (1),
ikev2 (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object is used for configuring the IKE version - IKev1 (1)
or IKEv2 (2) protocol to be used for key negotiation"
::= { fsVpnEntry 41 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This object is used for configuring the IKE version - IKev1 (1) or IKEv2 (2) protocol to be used for key negotiation
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: fsVpnIkeVersion
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsVpnIkeVersion",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"ikev1",
"(",
"1",
")",
",",
"ikev2",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This object is used for configuring the IKE version - IKev1 (1) or IKEv2 (2) protocol to be used for key negotiation\"",
"::=",
"{",
"fsVpnEntry",
"41",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"ikev1",
1
],
[
"ikev2",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object is used for configuring the IKE version - IKev1 (1) or IKEv2 (2) protocol to be used for key negotiation"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: FS-VPNPOLICY-MIB
See published definition above
{'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['RowStatus', 'DisplayString'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength']}Related source files and packages:
Module: FS-VPNPOLICY-MIB
{'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['RowStatus', 'DisplayString'], 'SNMPv2-SMI': ['enterprises', 'MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength']}Related source files and packages:
Registration