OID reference

pikePeerTable

1.3.6.1.4.1.119.2.3.84.3.1.2.2

Description

The IPsec Phase-1 Internet Key Exchange Peer Table. There is one entry in this table for each IPsec Phase-1 IKE peer association which is currently associated with an active IPsec Phase-1 Tunnel. A peer has an entry in this stable, if and only if thjere is at least one Phase-1 or Phase-2 tunnel terminating on the mana…

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.119.2.3.84.3.1.2 (pipSecPhaseOne)
Node code: 2
Node name: pikePeerTable
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.119.2.3.84.3.1.2.2
URN notation: urn:oid:1.3.6.1.4.1.119.2.3.84.3.1.2.2

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 119 2 3 84 3 1 2 2}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nec(119) nec-mib(2) necProductDepend(3) pico-mib(84) picoIpSecFlowMonitorMIB(3) pipSecMIBObjects(1) pipSecPhaseOne(2) pikePeerTable(2)}

OID-IRI notation

/1/3/6/1/4/1/119/2/3/84/3/1/2/2
/ISO/Identified-Organization/6/1/4/1/119/2/3/84/3/1/2/2
/ISO/3/6/1/4/1/119/2/3/84/3/1/2/2

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/identified-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/identified-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/org/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/org/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/org/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/org/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/iso-identified-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/iso-identified-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/iso-identified-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/iso-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/iso-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/iso-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable
/iso/iso-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikePeerTable

SNMP properties

Value type: SEQUENCE OF PikePeerEntry
Maximum access defined by MIB: not-accessible
Status in MIB: mandatory

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Published definition

The displayed source records contain one distinct definition. Compare its source records.

pikePeerTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF PikePeerEntry
    ACCESS      not-accessible
    STATUS      mandatory
    DESCRIPTION 
        "The IPsec Phase-1 Internet Key Exchange Peer Table.
         There is one entry in this table for each IPsec
         Phase-1 IKE peer association which is currently
         associated with an active IPsec Phase-1 Tunnel.
         A peer has an entry in this stable, if and only if
         thjere is at least one Phase-1 or Phase-2 tunnel
         terminating on the managed entity from the peer.
         When all Phase-1 and Phase-2 tunnels to a peer have
         expired, the entry for the peer is deleted off this
         table."
    ::= { pipSecPhaseOne 2 }

Meaning

Descriptions

1 unique

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

Sources for this description

NEC UNIVERGE IX official MIBs

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 1NEC UNIVERGE IX official MIBs1 record · 1 source

Description 1

pikePeerTable · mandatoryNEC UNIVERGE IX official MIBs1 source

Status in source: mandatory.

Names: pikePeerTable

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pikePeerTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "PikePeerEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The IPsec Phase-1 Internet Key Exchange Peer Table. There is one entry in this table for each IPsec Phase-1 IKE peer association which is currently associated with an active IPsec Phase-1 Tunnel. A peer has an entry in this stable, if and only if thjere is at least one Phase-1 or Phase-2 tunnel terminating on the managed entity from the peer. When all Phase-1 and Phase-2 tunnels to a peer have expired, the entry for the peer is deleted off this table.\"",
    "::=",
    "{",
    "pipSecPhaseOne",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "PikePeerEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The IPsec Phase-1 Internet Key Exchange Peer Table. There is one entry in this table for each IPsec Phase-1 IKE peer association which is currently associated with an active IPsec Phase-1 Tunnel. A peer has an entry in this stable, if and only if thjere is at least one Phase-1 or Phase-2 tunnel terminating on the managed entity from the peer. When all Phase-1 and Phase-2 tunnels to a peer have expired, the entry for the peer is deleted off this table."
    ],
    null,
    null,
    null,
    null
  ]
}

NEC UNIVERGE IX official MIBs · Publisher's source file: NEC UNIVERGE IX — PICO-IPSEC-FLOW-MONITOR-MIB.txt
Module: PICO-IPSEC-FLOW-MONITOR-MIB

See published definition above
Module imports
```
{'PICO-SMI': ['picoIpSecFlowMonitorMIB'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'SNMPv2-TC': ['DisplayString', 'TimeInterval', 'TimeStamp', 'TruthValue'], 'RFC1155-SMI': ['Counter', 'Gauge', 'enterprises']}
```
· Download NEC UNIVERGE IX — PICO-IPSEC-FLOW-MONITOR-MIB.txt
Related source files and packages:
- NEC UNIVERGE IX — PICO-SMI root MIB for this saved snapshot

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.119)

Akiyama Yoshiyuki

Direct children (1)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1	pikePeerEntry	9	9

Siblings (2)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.119.2.3.84.3.1.2.1	pikeGlobalStats	20	20
1.3.6.1.4.1.119.2.3.84.3.1.2.3	pikeTunnelTable	1	27