OID reference

esPrivateVlanIfVlanMapEntry

1.3.6.1.4.1.171.17.69.1.3.1

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.171.17.69.1.3 (esPrivateVlanIfVlanMapTable)
Node code: 1
Node name: esPrivateVlanIfVlanMapEntry
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.171.17.69.1.3.1
URN notation: urn:oid:1.3.6.1.4.1.171.17.69.1.3.1

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 171 17 69 1 3 1}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dlink(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) d-link(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) company(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) my(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nms(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dlink(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) d-link(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) company(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) my(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nms(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dlink(171) dlinkCommon(17) dlinkEsPrivateVlanMIB(69) esPrivateVlanMIBObjects(1) esPrivateVlanIfVlanMapTable(3) esPrivateVlanIfVlanMapEntry(1)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/171/17/69/1/3/1
/ISO/Identified-Organization/6/1/4/1/171/17/69/1/3/1
/ISO/3/6/1/4/1/171/17/69/1/3/1

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/dlink/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprise/d-link/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprise/company/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprise/my/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprise/nms/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprises/dlink/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprises/d-link/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprises/company/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprises/my/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/enterprises/nms/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/dlink/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/d-link/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/company/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/my/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/ldap-enterprise/nms/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
/iso/identified-organization/dod/internet/private/vendor-objects/dlink/dlinkCommon/dlinkEsPrivateVlanMIB/esPrivateVlanMIBObjects/esPrivateVlanIfVlanMapTable/esPrivateVlanIfVlanMapEntry
Additional combinations skipped.

SNMP properties

Value type: EsPrivateVlanIfVlanMapEntry
Maximum access defined by MIB: not-accessible
Status in MIB: current

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.

esPrivateVlanIfVlanMapEntry OBJECT-TYPE
        SYNTAX          EsPrivateVlanIfVlanMapEntry
        MAX-ACCESS      not-accessible
        STATUS          current
        DESCRIPTION
            "An entry configures an association between a secondary VLAN and a 
            primary VLAN on a port/port-channel whose port mode is host, promiscuous, 
            trunk secondary or trunk promiscuous. If the port is private vlan host port, 
            at most one esPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID can be 
            created for a port/port-channel. In other words, a host port only can belong 
            to at most one secondary VLAN. 
            
            If the port is private vlan promiscuous port, it can be mapped to multiple secondary 
            VLANs in one private VLAN. But it cannot be mapped to multiple secondary VLANs in 
            different private VLANs. In other words, multiple esPrivateVlanIfVlanMapEntry with 
            different secondary VLAN IDs (esPrivateVlanIfVlanMapSecVlanId) in one private VLAN 
            (esPrivateVlanIfVlanMapPriVlan) can be created for a port/port-channel. But multiple 
            esPrivateVlanIfVlanMapEntry with different private VLAN IDs (esPrivateVlanIfVlanMapPriVlan) 
            cannot be created for a port/port-channel.
            
            If the port is private vlan trunk promiscuous port, it can be mapped to multiple 
            secondary VLANs in one private VLAN. It also can be mapped to multiple secondary VLANs 
            in different private VLANs. In other words, multiple esPrivateVlanIfVlanMapEntry with 
            different secondary VLAN IDs (esPrivateVlanIfVlanMapSecVlanId) can be created for 
            a port/port-channel, and multiple esPrivateVlanIfVlanMapEntry with different private VLAN 
            IDs (esPrivateVlanIfVlanMapPriVlan) also can be created for a port/port-channel.
              
            If the port is private vlan trunk secondary port, it only can be mapped to at most one 
            secondary VLAN in a private VLAN. But it can be mapped to multiple private VLANs. In 
            other words, a esPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID in a private 
            VLAN can be created for a port/port-channel. And the esPrivateVlanIfVlanMapEntry with 
            multiple private VLANs (esPrivateVlanIfVlanMapPriVlan)can also be created for a 
            port/port-channel.                     
            "
        INDEX {  
            esPrivateVlanMappingPortIndex,
            esPrivateVlanIfVlanMapSecVlanId
        }
        ::= { esPrivateVlanIfVlanMapTable 1}

Meaning

Descriptions

1 unique

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

An entry configures an association between a secondary VLAN and a primary VLAN on a port/port-channel whose port mode is host, promiscuous, trunk secondary or trunk promiscuous. If the port is private vlan host port, at most one esPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID can be created for a port/port-channel. In other words, a host port only can belong to at most one secondary VLAN. If the port is private vlan promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. But it cannot be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple esPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (esPrivateVlanIfVlanMapSecVlanId) in one private VLAN (esPrivateVlanIfVlanMapPriVlan) can be created for a port/port-channel. But multiple esPrivateVlanIfVlanMapEntry with different private VLAN IDs (esPrivateVlanIfVlanMapPriVlan) cannot be created for a port/port-channel. If the port is private vlan trunk promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. It also can be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple esPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (esPrivateVlanIfVlanMapSecVlanId) can be created for a port/port-channel, and multiple esPrivateVlanIfVlanMapEntry with different private VLAN IDs (esPrivateVlanIfVlanMapPriVlan) also can be created for a port/port-channel. If the port is private vlan trunk secondary port, it only can be mapped to at most one secondary VLAN in a private VLAN. But it can be mapped to multiple private VLANs. In other words, a esPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID in a private VLAN can be created for a port/port-channel. And the esPrivateVlanIfVlanMapEntry with multiple private VLANs (esPrivateVlanIfVlanMapPriVlan)can also be created for a port/port-channel.

Sources for this description

D-Link official switch 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 1D-Link official switch MIBs1 record · 1 source

Description 1

esPrivateVlanIfVlanMapEntry · currentD-Link official switch MIBs1 source

Status in source: current.

Names: esPrivateVlanIfVlanMapEntry

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "esPrivateVlanIfVlanMapEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "EsPrivateVlanIfVlanMapEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"An entry configures an association between a secondary VLAN and a primary VLAN on a port/port-channel whose port mode is host, promiscuous, trunk secondary or trunk promiscuous. If the port is private vlan host port, at most one esPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID can be created for a port/port-channel. In other words, a host port only can belong to at most one secondary VLAN. If the port is private vlan promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. But it cannot be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple esPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (esPrivateVlanIfVlanMapSecVlanId) in one private VLAN (esPrivateVlanIfVlanMapPriVlan) can be created for a port/port-channel. But multiple esPrivateVlanIfVlanMapEntry with different private VLAN IDs (esPrivateVlanIfVlanMapPriVlan) cannot be created for a port/port-channel. If the port is private vlan trunk promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. It also can be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple esPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (esPrivateVlanIfVlanMapSecVlanId) can be created for a port/port-channel, and multiple esPrivateVlanIfVlanMapEntry with different private VLAN IDs (esPrivateVlanIfVlanMapPriVlan) also can be created for a port/port-channel. If the port is private vlan trunk secondary port, it only can be mapped to at most one secondary VLAN in a private VLAN. But it can be mapped to multiple private VLANs. In other words, a esPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID in a private VLAN can be created for a port/port-channel. And the esPrivateVlanIfVlanMapEntry with multiple private VLANs (esPrivateVlanIfVlanMapPriVlan)can also be created for a port/port-channel. \"",
    "INDEX",
    "{",
    "esPrivateVlanMappingPortIndex",
    ",",
    "esPrivateVlanIfVlanMapSecVlanId",
    "}",
    "::=",
    "{",
    "esPrivateVlanIfVlanMapTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "EsPrivateVlanIfVlanMapEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "An entry configures an association between a secondary VLAN and a primary VLAN on a port/port-channel whose port mode is host, promiscuous, trunk secondary or trunk promiscuous. If the port is private vlan host port, at most one esPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID can be created for a port/port-channel. In other words, a host port only can belong to at most one secondary VLAN. If the port is private vlan promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. But it cannot be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple esPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (esPrivateVlanIfVlanMapSecVlanId) in one private VLAN (esPrivateVlanIfVlanMapPriVlan) can be created for a port/port-channel. But multiple esPrivateVlanIfVlanMapEntry with different private VLAN IDs (esPrivateVlanIfVlanMapPriVlan) cannot be created for a port/port-channel. If the port is private vlan trunk promiscuous port, it can be mapped to multiple secondary VLANs in one private VLAN. It also can be mapped to multiple secondary VLANs in different private VLANs. In other words, multiple esPrivateVlanIfVlanMapEntry with different secondary VLAN IDs (esPrivateVlanIfVlanMapSecVlanId) can be created for a port/port-channel, and multiple esPrivateVlanIfVlanMapEntry with different private VLAN IDs (esPrivateVlanIfVlanMapPriVlan) also can be created for a port/port-channel. If the port is private vlan trunk secondary port, it only can be mapped to at most one secondary VLAN in a private VLAN. But it can be mapped to multiple private VLANs. In other words, a esPrivateVlanIfVlanMapEntry with a unique secondary VLAN ID in a private VLAN can be created for a port/port-channel. And the esPrivateVlanIfVlanMapEntry with multiple private VLANs (esPrivateVlanIfVlanMapPriVlan)can also be created for a port/port-channel."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "esPrivateVlanMappingPortIndex"
        ],
        [
          0,
          "esPrivateVlanIfVlanMapSecVlanId"
        ]
      ]
    ],
    null
  ]
}

D-Link official switch MIBs · Publisher's source file: Source package: DGS3130_RUN_1.12.B002_mibs.tar.bz2
Module: DLINKES-PRIVATE-VLAN-MIB

See published definition above
Module imports
```
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'Q-BRIDGE-MIB': ['VlanId', 'VlanIdOrNone'], 'DLINK-ID-REC-MIB': ['dlinkCommon']}
```
· Download DLINKES-PRIVATE-VLAN-MIB.my
Related source files and packages:
Show all 26 related files and packages
Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.
Same file in DMS_DXS3130_RUN_1.20.003_mibs.tar.bz2.
Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.
Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.171)

Henry P. Nagai

Direct children (4)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.171.17.69.1.3.1.1	esPrivateVlanMappingPortIndex	0	0
1.3.6.1.4.1.171.17.69.1.3.1.2	esPrivateVlanIfVlanMapSecVlanId	0	0
1.3.6.1.4.1.171.17.69.1.3.1.3	esPrivateVlanIfVlanMapPriVlan	0	0
1.3.6.1.4.1.171.17.69.1.3.1.4	esPrivateVlanIfVlanMapRowStatus	0	0