HH3C-FAILOVER-MIB
The HH3C-FAILOVER-MIB manages High-availability failover groups on H3C devices, monitoring primary and secondary node states, CPU assignments, and service data synchronization status to enable automatic traffic failover and recovery.
Imported Objects
Objects
25 total| Object Name |
|---|
hh3cFailoverThis 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. MODULE-IDENTITY .1.3.6.1.4.1.25506.2.164 |
hh3cFailoverScalarObjects OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.164.1 |
hh3cFailoverMaxNumThe maximum number of Failover groups which the system supported to create, does not include the AutoBackup.ro Unsigned32 .1.3.6.1.4.1.25506.2.164.1.1 |
hh3cFailoverCurrentNumThe current number of Failover groups which the system has created, does not include the AutoBackup.ro Unsigned32 .1.3.6.1.4.1.25506.2.164.1.2 |
hh3cFailoverTables OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.164.2 |
hh3cFailoverCfgTableThis table is for configuration of backup group. SEQUENCE OF Hh3cFailoverCfgEntry .1.3.6.1.4.1.25506.2.164.2.1 |
hh3cFailoverCfgEntryAn entry of the hh3cFailoverGroupCfgTable. Hh3cFailoverCfgEntry .1.3.6.1.4.1.25506.2.164.2.1.1 |
hh3cFailoverIndexFailover group ID is used as group index, the value range of failover group ID depends on the device model. The failover GroupIndex cannot be modified after creation.ro Unsigned32 .1.3.6.1.4.1.25506.2.164.2.1.1.1 |
hh3cFailoverNameSpecifies the backup group name, a case-sensitive string of 1 to 63 characters. The failover group name cannot be modified after creation. The name can not include '?', and can not begin or end with ' '.rw DisplayString .1.3.6.1.4.1.25506.2.164.2.1.1.2 |
hh3cFailoverPrimaryChassisIDSpecifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. (Distributed devices In IRF mode.) On a centralized or distributed device, the value for this node is always zero. Note:The -1 for delete the node.rw Integer32 (-1..255) .1.3.6.1.4.1.25506.2.164.2.1.1.3 |
hh3cFailoverPrimarySlotIDSpecifies a card by its slot number. (Distributed devices In standalone mode.) Note:The -1 for delete the node.rw Integer32 (-1..255) .1.3.6.1.4.1.25506.2.164.2.1.1.4 |
hh3cFailoverPrimaryCpuIDSpecifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot. Note:The -1 for delete the node.rw Integer32 (-1..7) .1.3.6.1.4.1.25506.2.164.2.1.1.5 |
hh3cFailoverSecondaryChassisIDSpecifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. (Distributed devices In IRF mode.) On a centralized or distributed device, the value for this node is always zero. Note:The -1 for delete the node.rw Integer32 (-1..255) .1.3.6.1.4.1.25506.2.164.2.1.1.6 |
hh3cFailoverSecondarySlotIDSpecifies a card by its slot number. (Distributed devices In standalone mode.) Note:The -1 for delete the node.rw Integer32 (-1..255) .1.3.6.1.4.1.25506.2.164.2.1.1.7 |
hh3cFailoverSecondaryCpuIDSpecifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot. Note:The -1 for delete the node.rw Integer32 (-1..7) .1.3.6.1.4.1.25506.2.164.2.1.1.8 |
hh3cFailoverStateBackup group state: Initial: No node in the failover group is processing services. Normal: The primary node is processing services. Fault: The secondary node is processing services.ro Enumeration .1.3.6.1.4.1.25506.2.164.2.1.1.9 |
hh3cFailoverRowStatusThe status of this table entry. Only support active(1), createAndGo(4) and destroy(6).rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.164.2.1.1.10 |
hh3cFailoverNotification OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.164.3 |
hh3cFailoverTrap OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.164.3.0 |
hh3cFailoverCreateThe hh3cFailoverCreate trap indicates that the failover group has created. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.164.3.0.1 |
hh3cFailoverDeleteThe hh3cFailoverDelete trap indicates that the failover group has deleted. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.164.3.0.2 |
hh3cFailoverPrimaryNodeAddThe hh3cFailoverPrimaryNodeAdd trap indicates that the failover group has added the primary node. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.164.3.0.3 |
hh3cFailoverPrimaryNodeRemoveThe hh3cFailoverPrimaryNodeRemove trap indicates that the failover group has removed the primary node. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.164.3.0.4 |
hh3cFailoverSecondaryNodeAddThe hh3cFailoverSecondaryNodeAdd trap indicates that the failover group has added the secondary node. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.164.3.0.5 |
hh3cFailoverSecondaryNodeRemoveThe hh3cFailoverSecondaryNodeRemove trap indicates that the failover group has removed the secondary node. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.164.3.0.6 |
More MIBs from Hangzhou H3C
Browse all Hangzhou H3CMIBs →SNMP MIB module
SNMP MIB module
The HH3C-DOT11-APMT-MIB module enables monitoring of H3C wireless access points (both Fat and Fit modes) and their associated Access Controllers via CAPWAP tunnels, specifically tracking real-time AP operational states, association statistics, and BSS radio metrics.
The HH3C-ACL-MIB enables monitoring and configuration of Access Control List (ACL) entries, packet filtering rules, and associated hit counters on H3C network devices. It provides visibility into specific traffic matching statistics, rule hit counts, and policy enforcement status for ingress and egress filtering operations.
The HH3C-CBQOS2-MIB enables the configuration and real-time monitoring of Class-Based QoS policies on H3C network devices, specifically tracking classifier definitions, traffic matching rules, behavior actions (such as CAR, GTS, and WRED), and policy application status across interfaces, VLANs, and PVCs.
SNMP MIB module