ipsec perfect forward secrecy: no / all / modp1024 / modp1536 / modp2048 / modp3072 / modp4096
Sources for this description
Hirschmann MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.248.51.1.2.1.18
ipsec perfect forward secrecy: no / all / modp1024 / modp1536 / modp2048 / modp3072 / modp4096
Identification
{1 3 6 1 4 1 248 51 1 2 1 18}
| Value | Name |
|---|---|
| 1 | no |
| 2 | all |
| 3 | modp1024 |
| 4 | modp1536 |
| 5 | modp2048 |
| 6 | modp3072 |
| 7 | modp4096 |
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.18.<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.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.
hmSecVPNpfs OBJECT-TYPE
SYNTAX INTEGER {
no(1),
all(2),
modp1024(3),
modp1536(4),
modp2048(5),
modp3072(6),
modp4096(7)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"ipsec perfect forward secrecy: no / all / modp1024 / modp1536 / modp2048 / modp3072 / modp4096"
::= { hmSecVPNConnectionEntry 18 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
ipsec perfect forward secrecy: no / all / modp1024 / modp1536 / modp2048 / modp3072 / modp4096
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: hmSecVPNpfs
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hmSecVPNpfs",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"no",
"(",
"1",
")",
",",
"all",
"(",
"2",
")",
",",
"modp1024",
"(",
"3",
")",
",",
"modp1536",
"(",
"4",
")",
",",
"modp2048",
"(",
"5",
")",
",",
"modp3072",
"(",
"6",
")",
",",
"modp4096",
"(",
"7",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"ipsec perfect forward secrecy: no / all / modp1024 / modp1536 / modp2048 / modp3072 / modp4096\"",
"::=",
"{",
"hmSecVPNConnectionEntry",
"18",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"no",
1
],
[
"all",
2
],
[
"modp1024",
3
],
[
"modp1536",
4
],
[
"modp2048",
5
],
[
"modp3072",
6
],
[
"modp4096",
7
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"ipsec perfect forward secrecy: no / all / modp1024 / modp1536 / modp2048 / modp3072 / modp4096"
],
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