OID reference

pikePeerRemoteType

1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.3

Description

The type of remote peer identity. The remote peer may be identified by: 1. an IP address, or 2. or a fully qualified domain name. 3. or a distinguished name.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.119.2.3.84.3.1.2.2.1 (pikePeerEntry)
Node code: 3
Node name: pikePeerRemoteType
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.3
URN notation: urn:oid:1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.3

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 1 3}

{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}
{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) pikePeerEntry(1) pikePeerRemoteType(3)}

OID-IRI notation

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

Named path variants

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

SNMP properties

Value type: IkePeerType
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.

pikePeerRemoteType OBJECT-TYPE
    SYNTAX      IkePeerType
    ACCESS      not-accessible
    STATUS      mandatory
    DESCRIPTION 
        "The type of remote peer identity.  The remote peer
         may be identified by:
         1. an IP address, or
         2. or a fully qualified domain name.
         3. or a distinguished name."
    ::= { pikePeerEntry 3 }

Meaning

Descriptions

1 unique

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

The type of remote peer identity. The remote peer may be identified by: 1. an IP address, or 2. or a fully qualified domain name. 3. or a distinguished name.

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

pikePeerRemoteType · mandatoryNEC UNIVERGE IX official MIBs1 source

Status in source: mandatory.

Names: pikePeerRemoteType

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pikePeerRemoteType",
    "OBJECT-TYPE",
    "SYNTAX",
    "IkePeerType",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The type of remote peer identity. The remote peer may be identified by: 1. an IP address, or 2. or a fully qualified domain name. 3. or a distinguished name.\"",
    "::=",
    "{",
    "pikePeerEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "IkePeerType"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The type of remote peer identity. The remote peer may be identified by: 1. an IP address, or 2. or a fully qualified domain name. 3. or a distinguished name."
    ],
    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

Siblings (8)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.1	pikePeerLocalType	0	0
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.2	pikePeerLocalValue	0	0
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.4	pikePeerRemoteValue	0	0
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.5	pikePeerIntIndex	0	0
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.6	pikePeerLocalAddr	0	0
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.7	pikePeerRemoteAddr	0	0
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.8	pikePeerActiveTime	0	0
1.3.6.1.4.1.119.2.3.84.3.1.2.2.1.9	pikePeerActiveTunnelIndex	0	0