Reference record for OID 1.3.6.1.4.1.2011.10.2.120.1.1.2

Parent
1.3.6.1.4.1.2011.10.2.120.1.1 (h3cFCoEConfig)
Node code
2
Node name
h3cFCoEVLANTable
Numeric OID
1.3.6.1.4.1.2011.10.2.120.1.1.2
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.120.1.1.2
ASN.1 notation

{1 3 6 1 4 1 2011 10 2 120 1 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2011/10/2/120/1/1/2
  • /ISO/Identified-Organization/6/1/4/1/2011/10/2/120/1/1/2
  • /ISO/3/6/1/4/1/2011/10/2/120/1/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • Additional combinations skipped.

Descriptions

h3cFCoEVLANTable — H3C and HH3C MIB copies (Observium Community)

In fabrics in which VLANs are deployed, this table facilitates configuration of VLAN and Virtual Fabric associations in an FCoE network. In such fabrics, FCoE forwarding for a fabric is over a VLAN in a (Layer-2) Ethernet network. That is, reachability between the ENode/remote-FCF and an FCF for a given fabric is determined by the reachability provided by the Ethernet network on the corresponding VLAN. An active entry in this table indicates which VLAN is used to transport FCoE traffic for a particular Virtual Fabric. If VLANs are not deployed or not enabled, entries in this table are ignored by the bridge. Some implementations may allow traffic from only one Virtual Fabric to be transported over a given VLAN. Such implementations should prevent multiple entries with the same VLAN-ID from being created in this table. Modifying existing VLAN-Virtual Fabric associations is not possible. The specific row must first be deleted and then a new one created.

Source records

h3cFCoEVLANTable

Status in source: current.

Names: h3cFCoEVLANTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cFCoEVLANTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "H3cFCoEVLANEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"In fabrics in which VLANs are deployed, this table facilitates configuration of VLAN and Virtual Fabric associations in an FCoE network. In such fabrics, FCoE forwarding for a fabric is over a VLAN in a (Layer-2) Ethernet network. That is, reachability between the ENode/remote-FCF and an FCF for a given fabric is determined by the reachability provided by the Ethernet network on the corresponding VLAN. An active entry in this table indicates which VLAN is used to transport FCoE traffic for a particular Virtual Fabric. If VLANs are not deployed or not enabled, entries in this table are ignored by the bridge. Some implementations may allow traffic from only one Virtual Fabric to be transported over a given VLAN. Such implementations should prevent multiple entries with the same VLAN-ID from being created in this table. Modifying existing VLAN-Virtual Fabric associations is not possible. The specific row must first be deleted and then a new one created.\"",
    "::=",
    "{",
    "h3cFCoEConfig",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "H3cFCoEVLANEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "In fabrics in which VLANs are deployed, this table facilitates configuration of VLAN and Virtual Fabric associations in an FCoE network. In such fabrics, FCoE forwarding for a fabric is over a VLAN in a (Layer-2) Ethernet network. That is, reachability between the ENode/remote-FCF and an FCF for a given fabric is determined by the reachability provided by the Ethernet network on the corresponding VLAN. An active entry in this table indicates which VLAN is used to transport FCoE traffic for a particular Virtual Fabric. If VLANs are not deployed or not enabled, entries in this table are ignored by the bridge. Some implementations may allow traffic from only one Virtual Fabric to be transported over a given VLAN. Such implementations should prevent multiple entries with the same VLAN-ID from being created in this table. Modifying existing VLAN-Virtual Fabric associations is not possible. The specific row must first be deleted and then a new one created."
    ],
    null,
    null,
    null,
    null
  ]
}
  • H3C and HH3C MIB copies (Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. H3C and HH3C support.

    Module: H3C-FCOE-MIB

    Published definition
    h3cFCoEVLANTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF H3cFCoEVLANEntry
        MAX-ACCESS      not-accessible
        STATUS          current
        DESCRIPTION
            "In fabrics in which VLANs are deployed, this table facilitates
            configuration of VLAN and Virtual Fabric associations in an
            FCoE network.  In such fabrics, FCoE forwarding for a fabric
            is over a VLAN in a (Layer-2) Ethernet network.  That is,
            reachability between the ENode/remote-FCF and an FCF for a
            given fabric is determined by the reachability provided by the
            Ethernet network on the corresponding VLAN.
            An active entry in this table indicates which VLAN is used
            to transport FCoE traffic for a particular Virtual Fabric.
            If VLANs are not deployed or not enabled, entries in this table
            are ignored by the bridge.
            Some implementations may allow traffic from only one Virtual
            Fabric to be transported over a given VLAN.  Such
            implementations should prevent multiple entries with the same
            VLAN-ID from being created in this table.
            Modifying existing VLAN-Virtual Fabric associations is not
            possible.  The specific row must first be deleted and then
            a new one created."
        ::= { h3cFCoEConfig 2 }
    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['RowStatus', 'TimeStamp', 'TruthValue', 'MacAddress', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32'], 'T11-TC-MIB': ['T11FabricIndex'], 'FC-MGMT-MIB': ['fcmInstanceIndex'], 'Q-BRIDGE-MIB': ['VlanIndex'], 'H3C-FC-TC-MIB': ['H3cFcNameId'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'HUAWEI-3COM-OID-MIB': ['h3cCommon']}
    · Download H3C-FCOE-MIB

    Related source files and packages:


    Source location: H3C-FCOE-MIB::h3cFCoEVLANTable.
    Source version and references

    Downloaded: 2026-10-24T02:13:09.785163+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2011)

Lwu Zhao

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.120.1.1.2.1 h3cFCoEVLANEntry44

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.120.1.1.1 h3cFCoECfgTable16
1.3.6.1.4.1.2011.10.2.120.1.1.3 h3cFCoEStaticVfcTable110
1.3.6.1.4.1.2011.10.2.120.1.1.4 h3cFCoEFIPSnoopingTable14
1.3.6.1.4.1.2011.10.2.120.1.1.5 h3cFCoEVlanCfgTable15
1.3.6.1.4.1.2011.10.2.120.1.1.6 h3cFCoEFIPSnoopingFCFTable17
1.3.6.1.4.1.2011.10.2.120.1.1.7 h3cFCoEFIPSnoopingENodeTable15
1.3.6.1.4.1.2011.10.2.120.1.1.8 h3cFCoEFIPSnoopingVNTable18
1.3.6.1.4.1.2011.10.2.120.1.1.9 h3cFCoEFIPSnoopingIfCfgTable13