Reference record for OID 1.3.6.1.4.1.2011.10.2.164

Parent
1.3.6.1.4.1.2011.10.2 (h3cCommon)
Node code
164
Node name
h3cFailover
Numeric OID
1.3.6.1.4.1.2011.10.2.164
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.164
ASN.1 notation

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

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

Descriptions

h3cFailover — H3C and HH3C MIB copies (Observium Community)

This MIB file is to provide the definition of failover group. Such as: 1. Configure Failover Groups for a device and display Failover Groups and their status. 2. Assign CPU to the Failover Group, and display their status. Failover Group: A failover group contains a primary node and a secondary node. When a failover group is referenced by a service module, the primary node processes services and backs up service data to the secondary node. The secondary node does not process services, but it takes over the services when the primary node fails. When the primary node is recovered, traffic is switched to the primary node again.

Source records

h3cFailover

Status in source: unspecified.

Names: h3cFailover

Technical details
{
  "smi_kind": "OBJECT IDENTIFIER",
  "definition": [
    "h3cFailover",
    "OBJECT",
    "IDENTIFIER",
    "::=",
    "{",
    "h3cCommon",
    "164",
    "}"
  ]
}

h3cFailover

Status in source: unspecified.

Names: h3cFailover

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "h3cFailover",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230313531303237313034305a22"
    ],
    "ORGANIZATION",
    "\"Hangzhou H3C Tech. Co., Ltd.\"",
    "CONTACT-INFO",
    "\"Platform Team Hangzhou H3C Tech. Co., Ltd. Hai-Dian District Beijing P.R. China http://www.h3c.com Zip:100085\"",
    "DESCRIPTION",
    "\"This MIB file is to provide the definition of failover group. Such as: 1. Configure Failover Groups for a device and display Failover Groups and their status. 2. Assign CPU to the Failover Group, and display their status. Failover Group: A failover group contains a primary node and a secondary node. When a failover group is referenced by a service module, the primary node processes services and backs up service data to the secondary node. The secondary node does not process services, but it takes over the services when the primary node fails. When the primary node is recovered, traffic is switched to the primary node again.\"",
    "REVISION",
    [
      "literal",
      "223230313531303237313034305a22"
    ],
    "DESCRIPTION",
    "\"The initial revision of this MIB module.\"",
    "::=",
    "{",
    "h3cCommon",
    "164",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "201510271040Z"
    ],
    [
      "ORGANIZATION",
      "Hangzhou H3C Tech. Co., Ltd."
    ],
    [
      "CONTACT-INFO",
      "Platform Team Hangzhou H3C Tech. Co., Ltd. Hai-Dian District Beijing P.R. China http://www.h3c.com Zip:100085"
    ],
    [
      "DESCRIPTION",
      "This MIB file is to provide the definition of failover group. Such as: 1. Configure Failover Groups for a device and display Failover Groups and their status. 2. Assign CPU to the Failover Group, and display their status. Failover Group: A failover group contains a primary node and a secondary node. When a failover group is referenced by a service module, the primary node processes services and backs up service data to the secondary node. The secondary node does not process services, but it takes over the services when the primary node fails. When the primary node is recovered, traffic is switched to the primary node again."
    ],
    [
      "Revisions",
      [
        [
          "201510271040Z",
          [
            "DESCRIPTION",
            "The initial revision of this MIB module."
          ]
        ]
      ]
    ]
  ]
}
  • 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-FAILOVER-MIB

    Published definition
    h3cFailover MODULE-IDENTITY
        LAST-UPDATED "201510271040Z"
        ORGANIZATION
            "Hangzhou H3C Tech. Co., Ltd."
        CONTACT-INFO
            "Platform Team Hangzhou H3C Tech. Co., Ltd.
            Hai-Dian District Beijing P.R. China
            http://www.h3c.com
            Zip:100085"
        DESCRIPTION
            "This MIB file is to provide the definition of failover group.
    
            Such as:
            1. Configure Failover Groups for a device and display Failover Groups
               and their status.
            2. Assign CPU to the Failover Group, and display their status.
    
            Failover Group: A failover group contains a primary node and a secondary node.
            When a failover group is referenced by a service module, the primary node
            processes services and backs up service data to the secondary node.
            The secondary node does not process services, but it takes over the services
            when the primary node fails.
            When the primary node is recovered, traffic is switched to the primary node again."
        REVISION "201510271040Z"
        DESCRIPTION
            "The initial revision of this MIB module."
        ::= { h3cCommon 164 }
    Module imports
    {'SNMPv2-TC': ['DisplayString', 'RowStatus'], 'SNMPv2-SMI': ['Integer32', 'Unsigned32', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'HUAWEI-3COM-OID-MIB': ['h3cCommon']}
    · Download H3C-FAILOVER-MIB
    Source location: H3C-FAILOVER-MIB::h3cFailover.
    Source version and references

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

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2011)

Lwu Zhao

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.164.1 h3cFailoverScalarObjects22
1.3.6.1.4.1.2011.10.2.164.2 h3cFailoverTables112
1.3.6.1.4.1.2011.10.2.164.3 h3cFailoverNotification17

Siblings (174)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.1 h3cFtm122
1.3.6.1.4.1.2011.10.2.2 h3cUIMgt230
1.3.6.1.4.1.2011.10.2.3 h3cSystemMan3157 This MIB contains objects to manage the system.
It focuses on the display of current configure file and image
file,and the defini…
1.3.6.1.4.1.2011.10.2.4 h3cConfig394 This MIB contains objects to manage the system configuration. It contains the
model used to represent configuration data that ex…
1.3.6.1.4.1.2011.10.2.5 h3cFlash291 This MIB contains objects to manage the Quidway series router flash cards and flash
card operations.
There are no constraints on …
1.3.6.1.4.1.2011.10.2.6 h3cEntityExtend3128 The private mib file includes the general extent
information of the device.
1.3.6.1.4.1.2011.10.2.7 h3cIPSecMonitor2133
1.3.6.1.4.1.2011.10.2.8 h3cAcl7542 Description
1.3.6.1.4.1.2011.10.2.9 h3cVoiceVlan717
1.3.6.1.4.1.2011.10.2.10 h3cL4Redirect722
1.3.6.1.4.1.2011.10.2.11 h3cIpPBX00
1.3.6.1.4.1.2011.10.2.12 h3cUser246
1.3.6.1.4.1.2011.10.2.13 h3cRadius7136
1.3.6.1.4.1.2011.10.2.14 h3cPowerEthernetExt10148 Description.
1.3.6.1.4.1.2011.10.2.15 h3cEntityRelation212
1.3.6.1.4.1.2011.10.2.16 h3cProtocolVlan235 This MIB contains the objects for managing the protocol-based vlan configurations.
1.3.6.1.4.1.2011.10.2.17 h3cQosProfile399
1.3.6.1.4.1.2011.10.2.18 h3cNat2132
1.3.6.1.4.1.2011.10.2.19 h3cPos250
1.3.6.1.4.1.2011.10.2.20 h3cNS149
1.3.6.1.4.1.2011.10.2.21 h3cAAL5119
1.3.6.1.4.1.2011.10.2.22 h3cSSH148
1.3.6.1.4.1.2011.10.2.23 h3cRSA224
1.3.6.1.4.1.2011.10.2.24 h3cVrrpExt16
1.3.6.1.4.1.2011.10.2.25 h3cIpa647
1.3.6.1.4.1.2011.10.2.26 h3cPortSecurity155
1.3.6.1.4.1.2011.10.2.27 h3cVpls00
1.3.6.1.4.1.2011.10.2.28 h3cE1435
1.3.6.1.4.1.2011.10.2.29 h3cT1328
1.3.6.1.4.1.2011.10.2.30 h3cIKEMonitor2139
1.3.6.1.4.1.2011.10.2.31 h3cWebSwitch00
1.3.6.1.4.1.2011.10.2.32 h3cAutoDetect00
1.3.6.1.4.1.2011.10.2.33 h3cIpBroadcast36
1.3.6.1.4.1.2011.10.2.34 h3cIpx4132
1.3.6.1.4.1.2011.10.2.35 h3cIPS00
1.3.6.1.4.1.2011.10.2.36 h3cDhcpSnoop225
1.3.6.1.4.1.2011.10.2.37 h3cProtocolPriority18
1.3.6.1.4.1.2011.10.2.38 h3cTrap174
1.3.6.1.4.1.2011.10.2.39 h3cVoice15612
1.3.6.1.4.1.2011.10.2.40 h3cIfExt6189
1.3.6.1.4.1.2011.10.2.41 h3cCfCard129
1.3.6.1.4.1.2011.10.2.42 h3cEpon6963
1.3.6.1.4.1.2011.10.2.43 h3cDldp226
1.3.6.1.4.1.2011.10.2.44 h3cUnicast18
1.3.6.1.4.1.2011.10.2.45 h3cRrpp353
1.3.6.1.4.1.2011.10.2.46 h3cDomain376
1.3.6.1.4.1.2011.10.2.47 h3cIds132
1.3.6.1.4.1.2011.10.2.48 h3cRcr257
1.3.6.1.4.1.2011.10.2.49 h3cAtmDxi327
1.3.6.1.4.1.2011.10.2.50 h3cMulticast12