What to do in case DPD found out that the connection is dead: 'hold': renegotiate connection. 'clear': clear connection and don't renegotiate.
Sources for this description
Hirschmann MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.248.51.1.2.1.39
What to do in case DPD found out that the connection is dead: 'hold': renegotiate connection. 'clear': clear connection and don't renegotiate.
Identification
{1 3 6 1 4 1 248 51 1 2 1 39}
| Value | Name |
|---|---|
| 1 | hold |
| 2 | clear |
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 HmSecurityGateway-MIB, the row index hmSecVPNconIndex 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.248.51.1.2.1.39.<hmSecVPNconIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
Published row index: hmSecVPNconIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.248.51.1.2.1.39
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.
hmSecVPNDPDAction OBJECT-TYPE
SYNTAX INTEGER{
hold(1),
clear(2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"What to do in case DPD found out that the connection is dead:
'hold': renegotiate connection.
'clear': clear connection and don't renegotiate."
::= { hmSecVPNConnectionEntry 39 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
What to do in case DPD found out that the connection is dead: 'hold': renegotiate connection. 'clear': clear connection and don't renegotiate.
Hirschmann MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: hmSecVPNDPDAction
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hmSecVPNDPDAction",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"hold",
"(",
"1",
")",
",",
"clear",
"(",
"2",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"What to do in case DPD found out that the connection is dead: 'hold': renegotiate connection. 'clear': clear connection and don't renegotiate.\"",
"::=",
"{",
"hmSecVPNConnectionEntry",
"39",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"hold",
1
],
[
"clear",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"What to do in case DPD found out that the connection is dead: 'hold': renegotiate connection. 'clear': clear connection and don't renegotiate."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive. Hirschmann support.
Module: HmSecurityGateway-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'MacAddress'], 'RFC1155-SMI': ['enterprises'], 'RFC1213-MIB': ['DisplayString']}Related source files and packages:
Registration