OID reference

h3cFCoEStaticVfcTable

1.3.6.1.4.1.43.45.1.10.2.120.1.1.3

Description

This table facilitates the creation and deletion of static VFC interfaces. While VFCs can be dynamically created based on FIP FLOGI/ELP requests, operators may want to associate certain pre-configured policy for a particular ENode or a remote-FCF. In such cases static VFC creation becomes necessary. In addition to bei…

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
3
Node name
h3cFCoEStaticVfcTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.120.1.1.3
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.120.1.1.3
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 3}

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

SNMP properties

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

h3cFCoEStaticVfcTable · current

h3cFCoEStaticVfcTable OBJECT-TYPE
    SYNTAX          SEQUENCE OF H3cFCoEStaticVfcEntry
    MAX-ACCESS      not-accessible
    STATUS          current
    DESCRIPTION
        "This table facilitates the creation and deletion of static
        VFC interfaces.  While VFCs can be dynamically created based on
        FIP FLOGI/ELP requests, operators may want to associate certain
        pre-configured policy for a particular ENode or a remote-FCF.
        In such cases static VFC creation becomes necessary.  In addition
        to being creating, a static VFC also needs to be associated to
        an ENode or remote-FCF.  The VFC binding provides such an
        associaton.  The binding does not need to be specified when
        the row for a VFC is created, but may be specified later."
    ::= { h3cFCoEConfig 3 }

h3cFCoEStaticVfcTable · current

h3cFCoEStaticVfcTable OBJECT-TYPE
    SYNTAX          SEQUENCE OF H3cFCoEStaticVfcEntry
    MAX-ACCESS      not-accessible
    STATUS          current
    DESCRIPTION
        "This table facilitates the creation and deletion of static
        VFC interfaces.  While VFCs can be dynamically created based on
        FIP FLOGI/ELP requests, operators may want to associate certain
        pre-configured policy for a particular ENode or a remote-FCF.
        In such cases static VFC creation becomes necessary.  In addition
        to being creating, a static VFC also needs to be associated to
        an ENode or remote-FCF.  The VFC binding provides such an
        associaton.  The binding does not need to be specified when
        the row for a VFC is created, but may be specified later."
    ::= { h3cFCoEConfig 3 }

Meaning

Descriptions

1 unique

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

This table facilitates the creation and deletion of static VFC interfaces. While VFCs can be dynamically created based on FIP FLOGI/ELP requests, operators may want to associate certain pre-configured policy for a particular ENode or a remote-FCF. In such cases static VFC creation becomes necessary. In addition to being creating, a static VFC also needs to be associated to an ENode or remote-FCF. The VFC binding provides such an associaton. The binding does not need to be specified when the row for a VFC is created, but may be specified later.

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

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

Status in source: current.

Names: h3cFCoEStaticVfcTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cFCoEStaticVfcTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "H3cFCoEStaticVfcEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table facilitates the creation and deletion of static VFC interfaces. While VFCs can be dynamically created based on FIP FLOGI/ELP requests, operators may want to associate certain pre-configured policy for a particular ENode or a remote-FCF. In such cases static VFC creation becomes necessary. In addition to being creating, a static VFC also needs to be associated to an ENode or remote-FCF. The VFC binding provides such an associaton. The binding does not need to be specified when the row for a VFC is created, but may be specified later.\"",
    "::=",
    "{",
    "h3cFCoEConfig",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "H3cFCoEStaticVfcEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table facilitates the creation and deletion of static VFC interfaces. While VFCs can be dynamically created based on FIP FLOGI/ELP requests, operators may want to associate certain pre-configured policy for a particular ENode or a remote-FCF. In such cases static VFC creation becomes necessary. In addition to being creating, a static VFC also needs to be associated to an ENode or remote-FCF. The VFC binding provides such an associaton. The binding does not need to be specified when the row for a VFC is created, but may be specified later."
    ],
    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.3.1 h3cFCoEStaticVfcEntry99

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