OID reference

h3cFCoEVLANTable

1.3.6.1.4.1.43.45.1.10.2.120.1.1.2

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 dete…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.120.1.1 (h3cFCoEConfig)
Node code
2
Node name
h3cFCoEVLANTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.120.1.1.2
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.120.1.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 120 1 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) 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) a3com(43) jv-mib(45) huawei(1) 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) a3Com(43) jv-mib(45) huawei(1) 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) a3com(43) jv-mib(45) huawei(1) 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) a3Com(43) jv-mib(45) huawei(1) 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) a3com(43) jv-mib(45) huawei(1) 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) a3Com(43) jv-mib(45) huawei(1) 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) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) 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) a3Com(43) jv-mib(45) huawei(1) 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) a3com(43) jv-mib(45) huawei(1) 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) a3Com(43) jv-mib(45) huawei(1) 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) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cFCoE(120) h3cFCoEObjects(1) h3cFCoEConfig(1) h3cFCoEVLANTable(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/120/1/1/2
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/120/1/1/2
  • /ISO/3/6/1/4/1/43/45/1/10/2/120/1/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cFCoE/h3cFCoEObjects/h3cFCoEConfig/h3cFCoEVLANTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF H3cFCoEVLANEntry
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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cFCoEVLANTable · current

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 implmentations 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 }

h3cFCoEVLANTable · current

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 implmentations 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 }

Meaning

Descriptions

1 unique

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

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 implmentations 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.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

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 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cFCoEVLANTable · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

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 implmentations 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 implmentations 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
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.120.1.1.2.1 h3cFCoEVLANEntry44

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.120.1.1.1 h3cFCoECfgTable16
1.3.6.1.4.1.43.45.1.10.2.120.1.1.3 h3cFCoEStaticVfcTable110