HPICFHIGHAVAILABILITY-MIB :: hpicfHAMgmtModuleRedundancyState

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HPICFHIGHAVAILABILITY-MIB › hpicfHAMgmtModuleRedundancyState

hpicfHAMgmtModuleRedundancyState

Module: HPICFHIGHAVAILABILITY-MIB

OID (symbolic): HPICFHIGHAVAILABILITY-MIB::hpicfHAMgmtModuleRedundancyState

OID (numeric): 1.3.6.1.4.1.11.2.14.11.1.11.2.5.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This object describes the management module's redundancy state. 'unavailable' indicates the redundancy module is not available due to error or absence of the module. 'active' indicates the redundancy module is currently active and is providing service. 'disabled' indicates the redundancy module is disabled. 'syncing' indicates the redundancy module is in syncing state and after successful syncing it will enter active state else it will report error. 'warmStandby' indicates the redundancy module is in warmstandby mode and is not providing service, but it will be immediately able to take over the role of the resource to be backed up, without the need for initialization activity, and will contain the same information as the resource to be backed up but the Layer2 information will not be synced. 'hitless'indicates the redundancy module is in hitless mode and is not providing service, but it will be immediately able to take over the role of the resource to be backed up, without the need for initialization activity, and will contain the same information as the resource to be backed up.

What is hpicfHAMgmtModuleRedundancyState?

This object reports the detailed redundancy state of a management module: unavailable, active, disabled, syncing, warm standby, or hitless. Admins use this to confirm that a standby module has fully finished syncing (moved from syncing to warmStandby or hitless) and is truly ready to take over before relying on it for redundancy. If this object shows syncing(4) for an extended period instead of progressing to hitless(6), an admin would suspect the synchronization between modules is stuck or failing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.1.11.2.5.1.4
snmpwalk -v2c -c public <target> HPICFHIGHAVAILABILITY-MIB::hpicfHAMgmtModuleRedundancyState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.1.11.2.5.1.4.1
snmpget -v2c -c public <target> HPICFHIGHAVAILABILITY-MIB::hpicfHAMgmtModuleRedundancyState.1

Start monitoring HP ProCurve modular chassis switch (dual-supervisor high availability) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HPICFHIGHAVAILABILITY-MIB::hpicfHAMgmtModuleRedundancyState OID value, configure state conditions and alerts, and monitor any HP ProCurve modular chassis switch (dual-supervisor high availability) from a single console.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.11hpCLJ8500-MIB
1.3.6.1.4.1.11.2nmCLJ8500-MIB
1.3.6.1.4.1.11.2.14icfCONFIG-MIB
1.3.6.1.4.1.11.2.14.11hpicfObjectsCONFIG-MIB
1.3.6.1.4.1.11.2.14.11.1hpicfCommonHP-ICF
Numeric OIDNameModule
1.3.6.1.4.1.11.2.14.11.1.11hpicfHighAvailabilityHPICFHIGHAVAILABILITY-MIB
1.3.6.1.4.1.11.2.14.11.1.11.2hpicfHAStatusObjectsHPICFHIGHAVAILABILITY-MIB
1.3.6.1.4.1.11.2.14.11.1.11.2.5hpicfHAMgmtModuleTableHPICFHIGHAVAILABILITY-MIB
1.3.6.1.4.1.11.2.14.11.1.11.2.5.1hpicfHAMgmtModuleEntryHPICFHIGHAVAILABILITY-MIB
1.3.6.1.4.1.11.2.14.11.1.11.2.5.1.4hpicfHAMgmtModuleRedundancyStateHPICFHIGHAVAILABILITY-MIB