Reference record for OID 1.3.6.1.4.1.2011.10.2.120.1.1.4

Parent
1.3.6.1.4.1.2011.10.2.120.1.1 (h3cFCoEConfig)
Node code
4
Node name
h3cFCoEFIPSnoopingTable
Numeric OID
1.3.6.1.4.1.2011.10.2.120.1.1.4
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.120.1.1.4
ASN.1 notation

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

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

Descriptions

h3cFCoEFIPSnoopingTable — H3C and HH3C MIB copies (Observium Community)

FCoE provides increased flexibility, but with this flexibility new challenges arise in assuring highly robust Fabrics. The FCF does not have the complete control that a Fibre Channel switch has. Ethernet bridges commonly provide a feature called Access Control Lists (ACLs). Properly configured ACLs may emulate a point-to-point link by providing the traffic enforcement previously discussed. Furthermore, the FIP protocol has been designed to enable Ethernet bridges to efficiently monitor FIP frames passing through them. This data facilitates the automatic configuration of these ACLs. In addition, the automatic configuration is possible independent of any other ACLs that may be in use in the network for other applications. And FIP Snooping is to maintain these ACLs.

Source records

h3cFCoEFIPSnoopingTable

Status in source: current.

Names: h3cFCoEFIPSnoopingTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cFCoEFIPSnoopingTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "H3cFCoEFIPSnoopingEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"FCoE provides increased flexibility, but with this flexibility new challenges arise in assuring highly robust Fabrics. The FCF does not have the complete control that a Fibre Channel switch has. Ethernet bridges commonly provide a feature called Access Control Lists (ACLs). Properly configured ACLs may emulate a point-to-point link by providing the traffic enforcement previously discussed. Furthermore, the FIP protocol has been designed to enable Ethernet bridges to efficiently monitor FIP frames passing through them. This data facilitates the automatic configuration of these ACLs. In addition, the automatic configuration is possible independent of any other ACLs that may be in use in the network for other applications. And FIP Snooping is to maintain these ACLs.\"",
    "::=",
    "{",
    "h3cFCoEConfig",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "H3cFCoEFIPSnoopingEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "FCoE provides increased flexibility, but with this flexibility new challenges arise in assuring highly robust Fabrics. The FCF does not have the complete control that a Fibre Channel switch has. Ethernet bridges commonly provide a feature called Access Control Lists (ACLs). Properly configured ACLs may emulate a point-to-point link by providing the traffic enforcement previously discussed. Furthermore, the FIP protocol has been designed to enable Ethernet bridges to efficiently monitor FIP frames passing through them. This data facilitates the automatic configuration of these ACLs. In addition, the automatic configuration is possible independent of any other ACLs that may be in use in the network for other applications. And FIP Snooping is to maintain these ACLs."
    ],
    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
    h3cFCoEFIPSnoopingTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF H3cFCoEFIPSnoopingEntry
        MAX-ACCESS      not-accessible
        STATUS          current
        DESCRIPTION
            "FCoE provides increased flexibility, but with this flexibility
            new challenges arise in assuring highly robust Fabrics.  The FCF
            does not have the complete control that a Fibre Channel switch
            has.
            Ethernet bridges commonly provide a feature called Access Control
            Lists (ACLs).  Properly configured ACLs may emulate a point-to-point
            link by providing the traffic enforcement previously discussed.
            Furthermore, the FIP protocol has been designed to enable Ethernet
            bridges to efficiently monitor FIP frames passing through them.  This
            data facilitates the automatic configuration of these ACLs.  In
            addition, the automatic configuration is possible independent of
            any other ACLs that may be in use in the network for other
            applications.  And FIP Snooping is to maintain these ACLs."
        ::= { h3cFCoEConfig 4 }
    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::h3cFCoEFIPSnoopingTable.
    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.4.1 h3cFCoEFIPSnoopingEntry33

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.2 h3cFCoEVLANTable15
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.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