Reference record for OID 1.3.6.1.4.1.2011.10.2.127.1.1.1.5

Parent
1.3.6.1.4.1.2011.10.2.127.1.1.1 (h3cVsanDmConfiguration)
Node code
5
Node name
h3cVsanFcIdPersistencyTable
Numeric OID
1.3.6.1.4.1.2011.10.2.127.1.1.1.5
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.127.1.1.1.5
ASN.1 notation

{1 3 6 1 4 1 2011 10 2 127 1 1 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cSan(127) h3cVsan(1) h3cVsanMibObjects(1) h3cVsanDmConfiguration(1) h3cVsanFcIdPersistencyTable(5)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2011/10/2/127/1/1/1/5
  • /ISO/Identified-Organization/6/1/4/1/2011/10/2/127/1/1/1/5
  • /ISO/3/6/1/4/1/2011/10/2/127/1/1/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/org/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/org/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/org/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/org/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/org/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/org/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/org/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • /iso/org/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cSan/h3cVsan/h3cVsanMibObjects/h3cVsanDmConfiguration/h3cVsanFcIdPersistencyTable
  • Additional combinations skipped.

Descriptions

h3cVsanFcIdPersistencyTable — H3C and HH3C MIB copies (Observium Community)

This table contains the FC IDs which are in the FC ID persistency database of each VSAN. If the FC ID persistency is enabled, FC devices would get the same FC IDs even if they disappear and appear again. The FC ID persistency database contains information about the FC IDs which are assigned to FC devices either statically (configured) or dynamically. An entry is automatically created when a FC ID is assigned and h3cVsanFcIdPersistency is 'true' on this VSAN. The entries can also be created and deleted via the h3cVsanFcIdPersistencyRowStatus object. If the object h3cVsanFcIdPurge is set to 'enable', an entry is deleted if its h3cVsanFcIdPersistencyType is 'dynamic' and h3cVsanFcIdPersistencyUsed is 'false'. If the h3cVsanFcIdPersistency is 'false', no entry can be created. If the h3cVsanDmDomainIdAssigned is changed on a VSAN, then all the entries on that VSAN in this table are deleted.

Source records

h3cVsanFcIdPersistencyTable

Status in source: current.

Names: h3cVsanFcIdPersistencyTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cVsanFcIdPersistencyTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "H3cVsanFcIdPersistencyEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table contains the FC IDs which are in the FC ID persistency database of each VSAN. If the FC ID persistency is enabled, FC devices would get the same FC IDs even if they disappear and appear again. The FC ID persistency database contains information about the FC IDs which are assigned to FC devices either statically (configured) or dynamically. An entry is automatically created when a FC ID is assigned and h3cVsanFcIdPersistency is 'true' on this VSAN. The entries can also be created and deleted via the h3cVsanFcIdPersistencyRowStatus object. If the object h3cVsanFcIdPurge is set to 'enable', an entry is deleted if its h3cVsanFcIdPersistencyType is 'dynamic' and h3cVsanFcIdPersistencyUsed is 'false'. If the h3cVsanFcIdPersistency is 'false', no entry can be created. If the h3cVsanDmDomainIdAssigned is changed on a VSAN, then all the entries on that VSAN in this table are deleted.\"",
    "::=",
    "{",
    "h3cVsanDmConfiguration",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "H3cVsanFcIdPersistencyEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table contains the FC IDs which are in the FC ID persistency database of each VSAN. If the FC ID persistency is enabled, FC devices would get the same FC IDs even if they disappear and appear again. The FC ID persistency database contains information about the FC IDs which are assigned to FC devices either statically (configured) or dynamically. An entry is automatically created when a FC ID is assigned and h3cVsanFcIdPersistency is 'true' on this VSAN. The entries can also be created and deleted via the h3cVsanFcIdPersistencyRowStatus object. If the object h3cVsanFcIdPurge is set to 'enable', an entry is deleted if its h3cVsanFcIdPersistencyType is 'dynamic' and h3cVsanFcIdPersistencyUsed is 'false'. If the h3cVsanFcIdPersistency is 'false', no entry can be created. If the h3cVsanDmDomainIdAssigned is changed on a VSAN, then all the entries on that VSAN in this table are deleted."
    ],
    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-VSAN-MIB

    Published definition
    h3cVsanFcIdPersistencyTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF H3cVsanFcIdPersistencyEntry
        MAX-ACCESS      not-accessible
        STATUS          current
        DESCRIPTION
               "This table contains the FC IDs which are in the FC ID
               persistency database of each VSAN.
    
               If the FC ID persistency is enabled, FC devices would get
               the same FC IDs even if they disappear and appear again.
    
               The FC ID persistency database contains information
               about the FC IDs which are assigned to FC devices
               either statically (configured) or dynamically.
    
               An entry is automatically created when a FC ID is
               assigned and h3cVsanFcIdPersistency is 'true' on this VSAN.
    
               The entries can also be created and deleted via
               the h3cVsanFcIdPersistencyRowStatus object.
    
               If the object h3cVsanFcIdPurge is set to 'enable', an entry is
               deleted if its h3cVsanFcIdPersistencyType is 'dynamic' and
               h3cVsanFcIdPersistencyUsed is 'false'.
    
               If the h3cVsanFcIdPersistency is 'false', no
               entry can be created.
    
               If the h3cVsanDmDomainIdAssigned is changed on a VSAN, then all the
               entries on that VSAN in this table are deleted."
        ::= { h3cVsanDmConfiguration 5 }
    Module imports
    {'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'Counter32', 'Integer32'], 'H3C-FC-TC-MIB': ['H3cFcVsanIndex', 'H3cFcNameIdOrZero', 'H3cFcDomainPriority', 'H3cFcDomainId', 'H3cFcNameId', 'H3cFcAddressId', 'H3cFcDomainIdOrZero', 'H3cFcDmState', 'H3cFcDomainIdList'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'HUAWEI-3COM-OID-MIB': ['h3cCommon']}
    · Download H3C-VSAN-MIB

    Related source files and packages:


    Source location: H3C-VSAN-MIB::h3cVsanFcIdPersistencyTable.
    Source version and references

    Downloaded: 2026-10-24T02:13:09.838162+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.127.1.1.1.5.1 h3cVsanFcIdPersistencyEntry55

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.127.1.1.1.1 h3cVsanTable16
1.3.6.1.4.1.2011.10.2.127.1.1.1.2 h3cVsanDmTable119
1.3.6.1.4.1.2011.10.2.127.1.1.1.3 h3cVsanDmIfConfigTable12
1.3.6.1.4.1.2011.10.2.127.1.1.1.4 h3cVsanFcIdTable15