HpicfHighAvailability-MIB
AI MIB Summary
The HpicfHighAvailability-MIB enables configuration and monitoring of the Redundant Management module on Hewlett-Packard network devices, specifically tracking failover states, synchronization status, and redundancy link health to ensure continuous management plane availability.
Management information for configuring Redundant Management module on Hewlett-Packard network devices.
Main OID:
hpicfHighAvailability.1.3.6.1.4.1.11.2.14.11.1.11
30
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
30 total| Object Name |
|---|
hpicfHighAvailabilityManagement information for configuring Redundant Management module on Hewlett-Packard network devices. MODULE-IDENTITY .1.3.6.1.4.1.11.2.14.11.1.11 |
hpicfHAConfigObjects OBJECT IDENTIFIER .1.3.6.1.4.1.11.2.14.11.1.11.1 |
hpicfHARedundancyManagementModuleModeSpecify to enable/disable this feature. Enabling allows for management module redundancy when there are two management modules in the switch and does a hitless failover. Disabling prevents redundancy except due to fatal hardware errors on one management module. warmStandby option does a non-hitless failover.rw Enumeration .1.3.6.1.4.1.11.2.14.11.1.11.1.1 |
hpicfHAContinuousFwdingTimeThis is a configurable timer. After the failover, on the new AMM, the route and neighbor table entries are marked as stale in the FIB. As routing protocols begin to re-add routes, this stale flag will be reset. When this timer expires, all route and neighbor table entries still marked stale [not yet re-added] will be removed. A value of 0 means that no layer 3 hitless behavior is desired, and in this configuration, upon failover all FIB entries are flushed and corresponding hardware entries are removed. A default value of 5 minutes is chosen with the assumption that the routing protocols can finish re-adding the routes to the equivalent state within this time.rw Unsigned32 -- .1.3.6.1.4.1.11.2.14.11.1.11.1.2 |
hpicfHAStatusObjects OBJECT IDENTIFIER .1.3.6.1.4.1.11.2.14.11.1.11.2 |
hpicfHAMgmtRedundancyFailureReasonSpecifies the reason a redundant management module failed to become a standby module.ro Enumeration .1.3.6.1.4.1.11.2.14.11.1.11.2.1 |
hpicfHAMgmtFailoversSpecifies the number of management module failovers since last chassis boot.ro Counter32 .1.3.6.1.4.1.11.2.14.11.1.11.2.2 |
hpicfHALastFailoverTimeSpecifies the time (in hundredths of a second) of the last management module failover.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.11.2.14.11.1.11.2.3 |
hpicfHAFailOverLogTableThis table contains High Availability(HA) failover log specific information. SEQUENCE OF HpicfHAFailOverLogEntry .1.3.6.1.4.1.11.2.14.11.1.11.2.4 |
hpicfHAFailOverLogEntryFailover log information maintained for HA. HpicfHAFailOverLogEntry .1.3.6.1.4.1.11.2.14.11.1.11.2.4.1 |
hpicfHAFailOverIndexThis object uniquely identifies the entries in the failover log table. This table contains maximum of recent 10 entries. Integer32 .1.3.6.1.4.1.11.2.14.11.1.11.2.4.1.1 |
hpicfHAFailOverMgmtModuleThis object displays the management module information.It is similar to entPhysicalIndex.ro PhysicalIndex (ENTITY-MIB) .1.3.6.1.4.1.11.2.14.11.1.11.2.4.1.2 |
hpicfHAFailOverStateThis object indicates the failover state. 'unknown' indicates the state of the management module is undefined and this resource is unable to report standby state. 'active' indicates the state of the management module as active module and it means the resource is providing service. 'standby' indicates that the management module 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.ro Enumeration .1.3.6.1.4.1.11.2.14.11.1.11.2.4.1.3 |
hpicfHAFailOverTimeThis object indicates the failover time in seconds since 1/1/1990 0:0:0.ro Integer32 .1.3.6.1.4.1.11.2.14.11.1.11.2.4.1.4 |
hpicfHAFailOverReasonThis object define the reason for failover. 'switchoverReq' indicates failover as a result of switchover command issued by the user. 'buttonReq' indicates failover as a result of manual boot done by the user via reboot button. 'crashReq' indicates failover as a result of crash that happened to the active module. 'activeReset' indicates failover as a result of reset command issued by the user at active module. 'altReset' indicates failover as a result of reset command issued by the user at the alternate module.ro Enumeration .1.3.6.1.4.1.11.2.14.11.1.11.2.4.1.5 |
hpicfHAMgmtModuleTableThis table contains High Availability (HA) management module specific information. SEQUENCE OF HpicfHAMgmtModuleEntry .1.3.6.1.4.1.11.2.14.11.1.11.2.5 |
hpicfHAMgmtModuleEntryManagement module information maintained for HA. HpicfHAMgmtModuleEntry .1.3.6.1.4.1.11.2.14.11.1.11.2.5.1 |
hpicfHAMgmtModuleStateThis object displays the state of the the management module.This object is similar to entStateStandby object.ro EntityStandbyStatus .1.3.6.1.4.1.11.2.14.11.1.11.2.5.1.1 |
hpicfHAMgmtModuleCardUpSinceThis object displays the card uptime in seconds since this module state.ro Integer32 .1.3.6.1.4.1.11.2.14.11.1.11.2.5.1.2 |
hpicfHAMgmtModuleStateSinceThis object displays time in seconds from which the current state is valid.ro Integer32 .1.3.6.1.4.1.11.2.14.11.1.11.2.5.1.3 |
hpicfHAMgmtModuleRedundancyStateThis 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.ro Enumeration .1.3.6.1.4.1.11.2.14.11.1.11.2.5.1.4 |
hpicfHAConformance OBJECT IDENTIFIER .1.3.6.1.4.1.11.2.14.11.1.11.3 |
hpicfHACompliances OBJECT IDENTIFIER .1.3.6.1.4.1.11.2.14.11.1.11.3.1 |
hpicfHAComplianceThe compliance statement for SNMP entities which implement the hpicfHighAvailability MIB. Unknown .1.3.6.1.4.1.11.2.14.11.1.11.3.1.1 |
hpicfHACompliance1The compliance statement for SNMP entities which implement the hpicfHighAvailability MIB. Unknown .1.3.6.1.4.1.11.2.14.11.1.11.3.1.2 |
hpicfHAGroups OBJECT IDENTIFIER .1.3.6.1.4.1.11.2.14.11.1.11.3.2 |
hpicfHAConfigGroupThe collection of objects which are used to configure the Redundancy Management Module. Unknown .1.3.6.1.4.1.11.2.14.11.1.11.3.2.1 |
hpicfHAStatusGroupThe collection of objects which are used to represent Management Module statistics information. Unknown .1.3.6.1.4.1.11.2.14.11.1.11.3.2.2 |
hpicfHAFailOverGroupThe collection of objects which are used to represent failover log statistics information. Unknown .1.3.6.1.4.1.11.2.14.11.1.11.3.2.3 |
hpicfHAMgmtModuleGroupThe collection of objects which are used to represent management module specific information. Unknown .1.3.6.1.4.1.11.2.14.11.1.11.3.2.4 |