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 string. 3. or a distinguished name string.
OID reference
pikeTunRemoteType
1.3.6.1.4.1.119.2.3.84.3.1.2.3.1.6
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 string. 3. or a distinguished name string.
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.119.2.3.84.3.1.2.3.1 (pikeTunnelEntry)
- Node code
- 6
- Node name
- pikeTunRemoteType
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.119.2.3.84.3.1.2.3.1.6
- URN notation
- urn:oid:1.3.6.1.4.1.119.2.3.84.3.1.2.3.1.6
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 119 2 3 84 3 1 2 3 1 6}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- {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) pikeTunnelTable(3) pikeTunnelEntry(1) pikeTunRemoteType(6)}
- OID-IRI notation
- /1/3/6/1/4/1/119/2/3/84/3/1/2/3/1/6
- /ISO/Identified-Organization/6/1/4/1/119/2/3/84/3/1/2/3/1/6
- /ISO/3/6/1/4/1/119/2/3/84/3/1/2/3/1/6
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/identified-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/identified-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/identified-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/org/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/org/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/org/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/org/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/iso-identified-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/iso-identified-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/iso-identified-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/iso-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/iso-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/iso-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
- /iso/iso-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/pico-mib/picoIpSecFlowMonitorMIB/pipSecMIBObjects/pipSecPhaseOne/pikeTunnelTable/pikeTunnelEntry/pikeTunRemoteType
SNMP properties
- Value type
- IkePeerType
- Maximum access defined by MIB
- read-only
- 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.
pikeTunRemoteType OBJECT-TYPE
SYNTAX IkePeerType
ACCESS read-only
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 string.
3. or a distinguished name string."
::= { pikeTunnelEntry 6 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1NEC UNIVERGE IX official MIBs
pikeTunRemoteType · mandatoryNEC UNIVERGE IX official MIBs
Status in source: mandatory.
Names: pikeTunRemoteType
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"pikeTunRemoteType",
"OBJECT-TYPE",
"SYNTAX",
"IkePeerType",
"ACCESS",
"read-only",
"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 string. 3. or a distinguished name string.\"",
"::=",
"{",
"pikeTunnelEntry",
"6",
"}"
],
"syntax_tree": [
[
"row",
"IkePeerType"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"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 string. 3. or a distinguished name string."
],
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
· Download NEC UNIVERGE IX — PICO-IPSEC-FLOW-MONITOR-MIB.txtModule imports
{'PICO-SMI': ['picoIpSecFlowMonitorMIB'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'SNMPv2-TC': ['DisplayString', 'TimeInterval', 'TimeStamp', 'TruthValue'], 'RFC1155-SMI': ['Counter', 'Gauge', 'enterprises']}Related source files and packages:
Registration