OID reference

hmSec2VpnConnIkeAuthRemId

1.3.6.1.4.1.248.52.1.13.1.2.3.1.19

Description

Remote peer identifier to be compared with ID payload during negotiation. The ID payload is used to identify the initiator of the security association. The identity is used by the responder to determine the correct host system security policy requirement for the association (see RFC 2407, section 4.6.2 for details whe…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.248.52.1.13.1.2.3.1 (hmSec2VpnConnEntry)
Node code
19
Node name
hmSec2VpnConnIkeAuthRemId
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.248.52.1.13.1.2.3.1.19
URN notation
urn:oid:1.3.6.1.4.1.248.52.1.13.1.2.3.1.19
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 248 52 1 13 1 2 3 1 19}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hirschmann(248) hmSecurity2(52) hmSecurity2Objects(1) hmSec2Vpn(13) hmSec2VpnGroup(1) hmSec2VpnConnGroup(2) hmSec2VpnConnTable(3) hmSec2VpnConnEntry(1) hmSec2VpnConnIkeAuthRemId(19)}
OID-IRI notation
  • /1/3/6/1/4/1/248/52/1/13/1/2/3/1/19
  • /ISO/Identified-Organization/6/1/4/1/248/52/1/13/1/2/3/1/19
  • /ISO/3/6/1/4/1/248/52/1/13/1/2/3/1/19
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/identified-organization/dod/internet/private/enterprises/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/identified-organization/dod/internet/private/vendor-objects/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/org/dod/internet/private/enterprise/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/org/dod/internet/private/enterprises/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/org/dod/internet/private/ldap-enterprise/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/org/dod/internet/private/vendor-objects/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/iso-identified-organization/dod/internet/private/enterprise/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/iso-identified-organization/dod/internet/private/enterprises/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/iso-organization/dod/internet/private/enterprise/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/iso-organization/dod/internet/private/enterprises/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId
  • /iso/iso-organization/dod/internet/private/vendor-objects/hirschmann/hmSecurity2/hmSecurity2Objects/hmSec2Vpn/hmSec2VpnGroup/hmSec2VpnConnGroup/hmSec2VpnConnTable/hmSec2VpnConnEntry/hmSec2VpnConnIkeAuthRemId

SNMP properties

Value type
DisplayString
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
""
Allowed size (octets)
0–255

Using this OID with SNMP

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 HMSECURITY2-MIB, the row index hmSec2VpnConnIndex 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.52.1.13.1.2.3.1.19.<hmSec2VpnConnIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.248.52.1.13.1.2.3.1.19

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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

hmSec2VpnConnIkeAuthRemId · current

hmSec2VpnConnIkeAuthRemId   OBJECT-TYPE
                         SYNTAX                  DisplayString (SIZE (0..255))
                         MAX-ACCESS              read-write
                         STATUS                  current
                         DESCRIPTION
                             "Remote peer identifier to be compared with ID
                              payload during negotiation. The ID payload is
                              used to identify the initiator of the security
                              association. The identity is used by the
                              responder to determine the correct host system
                              security policy requirement for the association
                              (see RFC 2407, section 4.6.2 for details when
                              using IKEv1 and RFC 4306, section 3.5 for IKEv2).
                              Allowed formats for this entry depend on
                              'hmSec2VpnConnIkeAuthRemType':
                              o  any: don't care
                              o  ipaddr: IPv4 address
                              o  keyid: key identifier
                              o  fqdn: fully qualified domain name
                              o  email: fully qualified RFC 822 email address
                              o  asn1dn: X.500 distinguished name (DN)

                              If 'hmSec2VpnConnIkeAuthRemType' is 'asn1dn':
                              o and 'hmSec2VpnConnIkeAuthRemId' a character
                                string, then a typical X.500 distinguished name
                                syntax has to be used, e.g. CN=XY-D,C=DE,L=NT,
                                ST=BW,O=COMPANY,OU=DEV,E=testuser@company.com);
                              o and 'hmSec2VpnConnIkeAuthRemId' is a hex string with prefix 0x,
                                then the associated distinguished name must be
                                DER encoded (see RFC 2459);
                              o and 'hmSec2VpnConnIkeAuthRemId' is empty, then
                                the distinguished name from the certificate in
                                'hmSec2VpnConnIkeAuthCertRemote' is used here;
                              o then the subject from received certificate (remote
                                peer distinguished name) is compared against this
                                value."
                         DEFVAL  { "" }
                         ::= { hmSec2VpnConnEntry 19 }

hmSec2VpnConnIkeAuthRemId · current

hmSec2VpnConnIkeAuthRemId   OBJECT-TYPE
                         SYNTAX                  DisplayString (SIZE (0..255))
                         MAX-ACCESS              read-write
                         STATUS                  current
                         DESCRIPTION
                             "Remote peer identifier to be compared with ID
                              payload during negotiation. The ID payload is
                              used to identify the initiator of the security
                              association. The identity is used by the
                              responder to determine the correct host system
                              security policy requirement for the association
                              (see RFC 2407, section 4.6.2 for details when
                              using IKEv1 and RFC 4306, section 3.5 for IKEv2).
                              Allowed formats for this entry depend on
                              'hmSec2VpnConnIkeAuthRemType':
                              o  any: don't care
                              o  ipaddr: IPv4 address
                              o  keyid: key identifier
                              o  fqdn: fully qualified domain name
                              o  email: fully qualified RFC 822 email address
                              o  asn1dn: X.500 distinguished name (DN)

                              If 'hmSec2VpnConnIkeAuthRemType' is 'asn1dn':
                              o and 'hmSec2VpnConnIkeAuthRemId' a character
                                string, then a typical X.500 distinguished name
                                syntax has to be used, e.g. CN=XY-D,C=DE,L=NT,
                                ST=BW,O=COMPANY,OU=DEV,E=testuser@company.com);
                              o and 'hmSec2VpnConnIkeAuthRemId' is a hex string with prefix 0x,
                                then the associated distinguished name must be
                                DER encoded (see RFC 2459);
                              o and 'hmSec2VpnConnIkeAuthRemId' is empty, then
                                the distinguished name from the certificate in
                                'hmSec2VpnConnIkeAuthCertRemote' is used here;
                              o then the subject from received certificate (remote
                                peer distinguished name) is compared against this
                                value."
                         DEFVAL  { "" }
                         ::= { hmSec2VpnConnEntry 19 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Remote peer identifier to be compared with ID payload during negotiation. The ID payload is used to identify the initiator of the security association. The identity is used by the responder to determine the correct host system security policy requirement for the association (see RFC 2407, section 4.6.2 for details when using IKEv1 and RFC 4306, section 3.5 for IKEv2). Allowed formats for this entry depend on 'hmSec2VpnConnIkeAuthRemType': o any: don't care o ipaddr: IPv4 address o keyid: key identifier o fqdn: fully qualified domain name o email: fully qualified RFC 822 email address o asn1dn: X.500 distinguished name (DN) If 'hmSec2VpnConnIkeAuthRemType' is 'asn1dn': o and 'hmSec2VpnConnIkeAuthRemId' a character string, then a typical X.500 distinguished name syntax has to be used, e.g. CN=XY-D,C=DE,L=NT, ST=BW,O=COMPANY,OU=DEV,E=testuser@company.com); o and 'hmSec2VpnConnIkeAuthRemId' is a hex string with prefix 0x, then the associated distinguished name must be DER encoded (see RFC 2459); o and 'hmSec2VpnConnIkeAuthRemId' is empty, then the distinguished name from the certificate in 'hmSec2VpnConnIkeAuthCertRemote' is used here; o then the subject from received certificate (remote peer distinguished name) is compared against this value.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBsHirschmann MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Belden, GarrettCom and Hirschmann IT official standalone MIBs, Hirschmann MIB copies (LibreNMS/Observium Community)1 record · 2 sources

Description 1

hmSec2VpnConnIkeAuthRemId · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs, Hirschmann MIB copies (LibreNMS/Observium Community)2 sources

Status in source: current.

Names: hmSec2VpnConnIkeAuthRemId

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hmSec2VpnConnIkeAuthRemId",
    "OBJECT-TYPE",
    "SYNTAX",
    "DisplayString",
    "(",
    "SIZE",
    "(",
    "0",
    ".",
    ".",
    "255",
    ")",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Remote peer identifier to be compared with ID payload during negotiation. The ID payload is used to identify the initiator of the security association. The identity is used by the responder to determine the correct host system security policy requirement for the association (see RFC 2407, section 4.6.2 for details when using IKEv1 and RFC 4306, section 3.5 for IKEv2). Allowed formats for this entry depend on 'hmSec2VpnConnIkeAuthRemType': o any: don't care o ipaddr: IPv4 address o keyid: key identifier o fqdn: fully qualified domain name o email: fully qualified RFC 822 email address o asn1dn: X.500 distinguished name (DN) If 'hmSec2VpnConnIkeAuthRemType' is 'asn1dn': o and 'hmSec2VpnConnIkeAuthRemId' a character string, then a typical X.500 distinguished name syntax has to be used, e.g. CN=XY-D,C=DE,L=NT, ST=BW,O=COMPANY,OU=DEV,E=testuser@company.com); o and 'hmSec2VpnConnIkeAuthRemId' is a hex string with prefix 0x, then the associated distinguished name must be DER encoded (see RFC 2459); o and 'hmSec2VpnConnIkeAuthRemId' is empty, then the distinguished name from the certificate in 'hmSec2VpnConnIkeAuthCertRemote' is used here; o then the subject from received certificate (remote peer distinguished name) is compared against this value.\"",
    "DEFVAL",
    "{",
    [
      "literal",
      "2222"
    ],
    "}",
    "::=",
    "{",
    "hmSec2VpnConnEntry",
    "19",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "DisplayString",
      [
        "octetStringSubType",
        [
          [
            0,
            255
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Remote peer identifier to be compared with ID payload during negotiation. The ID payload is used to identify the initiator of the security association. The identity is used by the responder to determine the correct host system security policy requirement for the association (see RFC 2407, section 4.6.2 for details when using IKEv1 and RFC 4306, section 3.5 for IKEv2). Allowed formats for this entry depend on 'hmSec2VpnConnIkeAuthRemType': o any: don't care o ipaddr: IPv4 address o keyid: key identifier o fqdn: fully qualified domain name o email: fully qualified RFC 822 email address o asn1dn: X.500 distinguished name (DN) If 'hmSec2VpnConnIkeAuthRemType' is 'asn1dn': o and 'hmSec2VpnConnIkeAuthRemId' a character string, then a typical X.500 distinguished name syntax has to be used, e.g. CN=XY-D,C=DE,L=NT, ST=BW,O=COMPANY,OU=DEV,E=testuser@company.com); o and 'hmSec2VpnConnIkeAuthRemId' is a hex string with prefix 0x, then the associated distinguished name must be DER encoded (see RFC 2459); o and 'hmSec2VpnConnIkeAuthRemId' is empty, then the distinguished name from the certificate in 'hmSec2VpnConnIkeAuthCertRemote' is used here; o then the subject from received certificate (remote peer distinguished name) is compared against this value."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "\"\""
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.248)

Nisi Heinz

Siblings (33)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.248.52.1.13.1.2.3.1.1 hmSec2VpnConnIndex00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.2 hmSec2VpnConnIkeVersion00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.3 hmSec2VpnConnIkeStartup00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.4 hmSec2VpnConnIkeCompat00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.5 hmSec2VpnConnIkeLifetime00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.6 hmSec2VpnConnIkeDpdTimeout00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.7 hmSec2VpnConnIkeLocalAddr00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.8 hmSec2VpnConnIkeRemoteAddr00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.9 hmSec2VpnConnIkeAuthType00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.10 hmSec2VpnConnIkeAuthMode00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.11 hmSec2VpnConnIkeAuthCertCA00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.12 hmSec2VpnConnIkeAuthCertRemote00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.13 hmSec2VpnConnIkeAuthCertLocal00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.14 hmSec2VpnConnIkeAuthPrivKey00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.15 hmSec2VpnConnIkeAuthPasswd00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.16 hmSec2VpnConnIkeAuthPsk00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.17 hmSec2VpnConnIkeAuthLocId00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.18 hmSec2VpnConnIkeAuthLocType00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.20 hmSec2VpnConnIkeAuthRemType00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.21 hmSec2VpnConnIkeAlgDh00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.22 hmSec2VpnConnIkeAlgHash00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.23 hmSec2VpnConnIkeAlgMac00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.24 hmSec2VpnConnIkeAlgEncr00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.25 hmSec2VpnConnIpsecMode00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.26 hmSec2VpnConnIpsecNatTraversal00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.27 hmSec2VpnConnIpsecLifetime00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.28 hmSec2VpnConnIpsecAlgDh00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.29 hmSec2VpnConnIpsecAlgMac00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.30 hmSec2VpnConnIpsecAlgEncr00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.31 hmSec2VpnConnOperStatus00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.32 hmSec2VpnConnDesc00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.33 hmSec2VpnConnRowStatus00
1.3.6.1.4.1.248.52.1.13.1.2.3.1.34 hmSec2VpnConnServiceMode00