OID reference

dot1qFutureVlanPortType

1.3.6.1.4.1.2076.65.1.10.1.2

Description

The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing Vlans and also for any new vlan created. When configured as hybrid port, the port can send or accept both tagge…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2076.65.1.10.1 (dot1qFutureVlanPortEntry)
Node code
2
Node name
dot1qFutureVlanPortType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2076.65.1.10.1.2
URN notation
urn:oid:1.3.6.1.4.1.2076.65.1.10.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2076 65 1 10 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) 2076 futureVlanMIB(65) dot1qFutureVlan(1) dot1qFutureVlanPortTable(10) dot1qFutureVlanPortEntry(1) dot1qFutureVlanPortType(2)}
OID-IRI notation
  • /1/3/6/1/4/1/2076/65/1/10/1/2
  • /ISO/Identified-Organization/6/1/4/1/2076/65/1/10/1/2
  • /ISO/3/6/1/4/1/2076/65/1/10/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/identified-organization/dod/internet/private/enterprises/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/identified-organization/dod/internet/private/vendor-objects/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/org/dod/internet/private/enterprise/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/org/dod/internet/private/enterprises/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/org/dod/internet/private/ldap-enterprise/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/org/dod/internet/private/vendor-objects/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/iso-identified-organization/dod/internet/private/enterprise/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/iso-identified-organization/dod/internet/private/enterprises/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/iso-organization/dod/internet/private/enterprise/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/iso-organization/dod/internet/private/enterprises/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType
  • /iso/iso-organization/dod/internet/private/vendor-objects/2076/futureVlanMIB/dot1qFutureVlan/dot1qFutureVlanPortTable/dot1qFutureVlanPortEntry/dot1qFutureVlanPortType

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
hybridPort

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — Belden, GarrettCom and Hirschmann IT official standalone MIBs

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
hybridPort

Variant 2 — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
hybridPort

Enumerated values

Numbers refer to source variants above. Each value is shown only for variants that define it.

ValueNameSource variants
1accessPort1, 2
2trunkPort1, 2
3hybridPort1, 2
4hostPort1
5promiscuousPort1

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 ARICENT-VLAN-MIB, the row index dot1qFutureVlanPort is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.2076.65.1.10.1.2.<dot1qFutureVlanPort>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

Published row index: dot1qFutureVlanPort.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2076.65.1.10.1.2

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

dot1qFutureVlanPortType · current

dot1qFutureVlanPortType OBJECT-TYPE 
   SYNTAX      INTEGER { 
                  accessPort (1), 
                  trunkPort (2), 
                  hybridPort (3),
                  hostPort (4), 
                  promiscuousPort (5) 
               } 
   MAX-ACCESS  read-write 
   STATUS      current 
   DESCRIPTION 
      "The type of the port is by default hybrid port. 
       When configured as access port, the port can accept and send 
       only untagged frames.
       When configured as a trunk port, port is added as 
       member of all the existing Vlans and also for any new vlan
       created. 
       When configured as hybrid port, the port can send or accept both 
       tagged and untagged frames.  
       
       hostPort, promiscuousPort are types of port in PVLAN domain.
       Behaviour of host port varies based on the secondary vlan to which
       it is configured as member port.

       If a host port is a member port of an isolated VLAN, traffic from the 
       host port is sent only to the promiscuous port of the Private VLAN and 
       the trunk port.

       If a host port is a member port of the community VLAN, traffic from the 
       port can be sent only to other ports of the community VLAN , trunk port 
       and promiscuous port of the private VLAN. 
       
       A host port can be associated with only one secondary vlan and with
       the associated primary vlan.

       The PVID of host port will be set the ID of the secondary vlan
       to which it belongs to.If a host port is member port of primary vlan, 
       but is not member port of any secondary vlan, then its PVID will be 
       set to primary vlan id.

       When a port is configured as a hostPort or promiscuousPort, ingress
       filtering will be enabled on that port. Also ingress filtering
       cannot be disabled on hostPort and promiscuousPort.

       Promiscuous ports should be configured as member port of primary vlan 
       and member port of all secondary vlans associated with that 
       primary vlan.

       The PVID of promiscuous port will be set as the ID of the primary 
       vlan to which it belongs to.

       Host and  promiscuous ports should be configured as untagged members
       of primary/secondary vlans.

       When a access/hybrid port is configured as a member port of a
       primary/secondary vlan, it becomes a hostPort automatically.
       
       When the type of the port is changed from promiscuous/host to
       access/hybrid port, the port gets removed from the associated PVLAN
       domain."

   DEFVAL   { hybridPort } 
   ::= { dot1qFutureVlanPortEntry 2 }

dot1qFutureVlanPortType · current

dot1qFutureVlanPortType OBJECT-TYPE 
   SYNTAX      INTEGER { 
                  accessPort (1), 
                  trunkPort (2), 
                  hybridPort (3)
               } 
   MAX-ACCESS  read-write 
   STATUS      current 
   DESCRIPTION 
      "The type of the port is by default hybrid port. 
       When configured as access port, the port can accept and send 
       only untagged frames.
       When configured as a trunk port, port is added as 
       member of all the existing VLANs and also for any new VLAN
       created. 
       When configured as hybrid port, the port can send or accept both 
       tagged and untagged frames." 

   DEFVAL   { hybridPort } 
   ::= { dot1qFutureVlanPortEntry 2 }

Meaning

Descriptions

2 unique

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

Description 1

The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing Vlans and also for any new vlan created. When configured as hybrid port, the port can send or accept both tagged and untagged frames. hostPort, promiscuousPort are types of port in PVLAN domain. Behaviour of host port varies based on the secondary vlan to which it is configured as member port. If a host port is a member port of an isolated VLAN, traffic from the host port is sent only to the promiscuous port of the Private VLAN and the trunk port. If a host port is a member port of the community VLAN, traffic from the port can be sent only to other ports of the community VLAN , trunk port and promiscuous port of the private VLAN. A host port can be associated with only one secondary vlan and with the associated primary vlan. The PVID of host port will be set the ID of the secondary vlan to which it belongs to.If a host port is member port of primary vlan, but is not member port of any secondary vlan, then its PVID will be set to primary vlan id. When a port is configured as a hostPort or promiscuousPort, ingress filtering will be enabled on that port. Also ingress filtering cannot be disabled on hostPort and promiscuousPort. Promiscuous ports should be configured as member port of primary vlan and member port of all secondary vlans associated with that primary vlan. The PVID of promiscuous port will be set as the ID of the primary vlan to which it belongs to. Host and promiscuous ports should be configured as untagged members of primary/secondary vlans. When a access/hybrid port is configured as a member port of a primary/secondary vlan, it becomes a hostPort automatically. When the type of the port is changed from promiscuous/host to access/hybrid port, the port gets removed from the associated PVLAN domain.

Sources for this description

Belden, GarrettCom and Hirschmann IT official standalone MIBs

See 1 matching source record

Description 2

The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing VLANs and also for any new VLAN created. When configured as hybrid port, the port can send or accept both tagged and untagged frames.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 1Belden, GarrettCom and Hirschmann IT official standalone MIBs1 record · 1 source

Description 1

dot1qFutureVlanPortType · currentBelden, GarrettCom and Hirschmann IT official standalone MIBs1 source

Status in source: current.

Names: dot1qFutureVlanPortType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dot1qFutureVlanPortType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "accessPort",
    "(",
    "1",
    ")",
    ",",
    "trunkPort",
    "(",
    "2",
    ")",
    ",",
    "hybridPort",
    "(",
    "3",
    ")",
    ",",
    "hostPort",
    "(",
    "4",
    ")",
    ",",
    "promiscuousPort",
    "(",
    "5",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing Vlans and also for any new vlan created. When configured as hybrid port, the port can send or accept both tagged and untagged frames. hostPort, promiscuousPort are types of port in PVLAN domain. Behaviour of host port varies based on the secondary vlan to which it is configured as member port. If a host port is a member port of an isolated VLAN, traffic from the host port is sent only to the promiscuous port of the Private VLAN and the trunk port. If a host port is a member port of the community VLAN, traffic from the port can be sent only to other ports of the community VLAN , trunk port and promiscuous port of the private VLAN. A host port can be associated with only one secondary vlan and with the associated primary vlan. The PVID of host port will be set the ID of the secondary vlan to which it belongs to.If a host port is member port of primary vlan, but is not member port of any secondary vlan, then its PVID will be set to primary vlan id. When a port is configured as a hostPort or promiscuousPort, ingress filtering will be enabled on that port. Also ingress filtering cannot be disabled on hostPort and promiscuousPort. Promiscuous ports should be configured as member port of primary vlan and member port of all secondary vlans associated with that primary vlan. The PVID of promiscuous port will be set as the ID of the primary vlan to which it belongs to. Host and promiscuous ports should be configured as untagged members of primary/secondary vlans. When a access/hybrid port is configured as a member port of a primary/secondary vlan, it becomes a hostPort automatically. When the type of the port is changed from promiscuous/host to access/hybrid port, the port gets removed from the associated PVLAN domain.\"",
    "DEFVAL",
    "{",
    "hybridPort",
    "}",
    "::=",
    "{",
    "dot1qFutureVlanPortEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "accessPort",
            1
          ],
          [
            "trunkPort",
            2
          ],
          [
            "hybridPort",
            3
          ],
          [
            "hostPort",
            4
          ],
          [
            "promiscuousPort",
            5
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing Vlans and also for any new vlan created. When configured as hybrid port, the port can send or accept both tagged and untagged frames. hostPort, promiscuousPort are types of port in PVLAN domain. Behaviour of host port varies based on the secondary vlan to which it is configured as member port. If a host port is a member port of an isolated VLAN, traffic from the host port is sent only to the promiscuous port of the Private VLAN and the trunk port. If a host port is a member port of the community VLAN, traffic from the port can be sent only to other ports of the community VLAN , trunk port and promiscuous port of the private VLAN. A host port can be associated with only one secondary vlan and with the associated primary vlan. The PVID of host port will be set the ID of the secondary vlan to which it belongs to.If a host port is member port of primary vlan, but is not member port of any secondary vlan, then its PVID will be set to primary vlan id. When a port is configured as a hostPort or promiscuousPort, ingress filtering will be enabled on that port. Also ingress filtering cannot be disabled on hostPort and promiscuousPort. Promiscuous ports should be configured as member port of primary vlan and member port of all secondary vlans associated with that primary vlan. The PVID of promiscuous port will be set as the ID of the primary vlan to which it belongs to. Host and promiscuous ports should be configured as untagged members of primary/secondary vlans. When a access/hybrid port is configured as a member port of a primary/secondary vlan, it becomes a hostPort automatically. When the type of the port is changed from promiscuous/host to access/hybrid port, the port gets removed from the associated PVLAN domain."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "hybridPort"
    ]
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

dot1qFutureVlanPortType · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: dot1qFutureVlanPortType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dot1qFutureVlanPortType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "accessPort",
    "(",
    "1",
    ")",
    ",",
    "trunkPort",
    "(",
    "2",
    ")",
    ",",
    "hybridPort",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing VLANs and also for any new VLAN created. When configured as hybrid port, the port can send or accept both tagged and untagged frames.\"",
    "DEFVAL",
    "{",
    "hybridPort",
    "}",
    "::=",
    "{",
    "dot1qFutureVlanPortEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "accessPort",
            1
          ],
          [
            "trunkPort",
            2
          ],
          [
            "hybridPort",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The type of the port is by default hybrid port. When configured as access port, the port can accept and send only untagged frames. When configured as a trunk port, port is added as member of all the existing VLANs and also for any new VLAN created. When configured as hybrid port, the port can send or accept both tagged and untagged frames."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "hybridPort"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2076)

Division Products

Siblings (16)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2076.65.1.10.1.1 dot1qFutureVlanPort00
1.3.6.1.4.1.2076.65.1.10.1.3 dot1qFutureVlanPortMacBasedClassification00
1.3.6.1.4.1.2076.65.1.10.1.4 dot1qFutureVlanPortPortProtoBasedClassification00
1.3.6.1.4.1.2076.65.1.10.1.5 dot1qFutureVlanFilteringUtilityCriteria00
1.3.6.1.4.1.2076.65.1.10.1.6 dot1qFutureVlanPortProtected00
1.3.6.1.4.1.2076.65.1.10.1.7 dot1qFutureVlanPortSubnetBasedClassification00
1.3.6.1.4.1.2076.65.1.10.1.8 dot1qFutureVlanPortUnicastMacLearning00
1.3.6.1.4.1.2076.65.1.10.1.9 dot1qFutureVlanPortIngressEtherType00
1.3.6.1.4.1.2076.65.1.10.1.10 dot1qFutureVlanPortEgressEtherType00
1.3.6.1.4.1.2076.65.1.10.1.11 dot1qFutureVlanPortEgressTPIDType00
1.3.6.1.4.1.2076.65.1.10.1.12 dot1qFutureVlanPortAllowableTPID100
1.3.6.1.4.1.2076.65.1.10.1.13 dot1qFutureVlanPortAllowableTPID200
1.3.6.1.4.1.2076.65.1.10.1.14 dot1qFutureVlanPortAllowableTPID300
1.3.6.1.4.1.2076.65.1.10.1.15 dot1qFutureVlanPortUnicastMacSecType00
1.3.6.1.4.1.2076.65.1.10.1.16 dot1qFuturePortPacketReflectionStatus00
1.3.6.1.4.1.2076.65.1.10.1.17 dot1qFutureVlanPortProtectedStatic00