ENTERASYS-HIGH-AVAILABILITY-MIB
File:
ENTERASYS-HIGH-AVAILABILITY-MIB.mib (14975 bytes)
Imported modules
Imported symbols
Defined Types
| EtsysHauSystemStatus |
|
| The status of high-availability upgrade for this entity.
hauDisabled(1) HA Upgrade is not enabled.
hauPending(2) HA Upgrade is enabled and will be initiated
by the next system reset.
hauRunning(3) HA Upgrade is in progress.
hauHalted(4) HA Upgrade was halted.
hauSuccess(5) HA Upgrade completed successfully and entity
is running the target version of firmware.
hauError(6) A failure occurred during HA Upgrade.
hauForceComplete(7) HA Upgrade was forced to early completion.
Entity is running the target version of
firmware, but high-availability nature of the
upgrade may have been compromised. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
hauDisabled(1), hauPending(2), hauRunning(3), hauHalted(4), hauSuccess(5), hauError(6), hauForceComplete(7) |
|
| EtsysHauMode |
|
| The default mode of high-availability upgrade for this entity.
hauNever(1) Never perform a HA Upgrade.
hauIfPossible(2) Perform an HA Upgrade whenever possible.
hauAlways(3) Always attempt to perform a HA Upgrade. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
hauNever(1), hauIfPossible(2), hauAlways(3) |
|
| HauSlotList |
|
| Each octet within this value specifies a set of eight
slots, with the first octet specifying slots 1 through 8,
the second octet specifying slots 9 through 16, etc.
Within each octet, the most significant bit represents
the lowest numbered slot, and the least significant bit
represents the highest numbered slot. Thus, each slot
of the virtual switch is represented by a single bit
within the value of this object. If that bit has a value
of '1' then that slot is included in the set of slots;
the slot is not included if its bit has a value of '0'. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
|
|
| HauSlot |
|
| Logical slot number which aligns with HauSlotList. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Integer32 |
1..128 |
|
| EtsysHauModuleEntry |
|
| SEQUENCE |
|
|
|
| |
etsysHauModuleSlot |
HauSlot |
|
| |
etsysHauModuleEntRef |
PhysicalIndex |
|
| |
etsysHauModuleGroupId |
Unsigned32 |
|
Defined Values
| etsysHighAvailabilityUpgradeMIB |
1.3.6.1.4.1.5624.1.2.84 |
| This MIB module defines a portion of the SNMP MIB under
the Enterasys Networks enterprise OID pertaining to
configuration and monitoring of high-availability
upgrades. |
| MODULE-IDENTITY |
|
|
|
| etsysHauStatsOriginalImage |
1.3.6.1.4.1.5624.1.2.84.1.1.2 |
| The release and version of firmware the managed entity is
upgrading from (i.e, firmware that is running at the start
of high-availability upgrade). |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
|
|
| etsysHauStatsTargetImage |
1.3.6.1.4.1.5624.1.2.84.1.1.3 |
| The release and version of firmware the managed entity is
upgrading to (i.e, firmware that will be running after
successful completion of high-availability upgrade). |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
|
|
| etsysHauStatsStartTime |
1.3.6.1.4.1.5624.1.2.84.1.1.8 |
| The date and time when the most recent high-availability upgrade
was started. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DateAndTime |
|
|
| etsysHauStatsDuration |
1.3.6.1.4.1.5624.1.2.84.1.1.9 |
| The duration of the most recent current high-availability
upgrade, in centiseconds. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TimeInterval |
|
|
| etsysHauSystemInterGroupDelay |
1.3.6.1.4.1.5624.1.2.84.1.2.1 |
| The duration, in seconds, the high-availability upgrade
process will delay between the successful upgrade of one
upgrade group and the start of the next upgrade group's
upgrade.
When an upgrade group is upgraded, all modules which
are a member of the group are reset. If these resets
cause instability in higher-layer networking protocols,
then this delay may help those protocols stabilize
during the course of the high-availability upgrade.
Note that this delay will increase the overall length
of the high-availability upgrade process. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| etsysHauSystemHauMode |
1.3.6.1.4.1.5624.1.2.84.1.2.2 |
| The desired mode of operation to attempt to use when
performing a reset.
When set to hauNever(1) a high-availability upgrade
will never be performed. Instead a standard upgrade
will be performed.
When set to hauIfPossible(2) a high-availability upgrade
will be performed if the current and target images are
compatible, otherwise a standard upgrade will be performed.
When set to hauAlways(3) a high-availability upgrade
will always be performed. If the current and target
images are incompatible then no upgrade will occur. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
EtsysHauMode |
|
|
| etsysHauModuleEntry |
1.3.6.1.4.1.5624.1.2.84.1.3.1.1 |
| An entry containing high-availability properties per module. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
EtsysHauModuleEntry |
|
|
| etsysHauModuleSlot |
1.3.6.1.4.1.5624.1.2.84.1.3.1.1.1 |
| Logical slot for a given module. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
HauSlot |
|
|
| etsysHauModuleEntRef |
1.3.6.1.4.1.5624.1.2.84.1.3.1.1.2 |
| Entity Physical Index which corresponds to this slot. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
PhysicalIndex |
|
|
| etsysHauModuleGroupId |
1.3.6.1.4.1.5624.1.2.84.1.3.1.1.3 |
| This object is a user-assigned value used to assign individual
modules to a High-Availability Upgrade Group. All slots
within an upgrade group will be upgraded simultaneously.
The purpose of assigning multiple slots to the same upgrade
group is to reduce the overall time it takes to perform an
HA upgrade.
By default, each module is assigned to its own upgrade
group, with GroupId equal to the module's HAU Slot. Although
this default configuration is completely valid, it may not
be optimal for situations where a timely HA upgrade is
desirable.
The network architecture, specifically LAGs, must be taken
into consideration when assigning slots to an upgrade group.
LAGs which span multiple modules should not have all of their
modules placed into the same upgrade group, as this would
defeat the LAG's inherent redundancy.
IMPORTANT:
If a LAG is to remain available during a High-Availability
Upgrade, then it must comprised of multiple single-port links
which reside on separate modules. Furthermore, at least two
of those modules must reside in separate upgrade groups. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..128 |
|
| etsysHauSystemGroup |
1.3.6.1.4.1.5624.1.2.84.2.1.1 |
| The system-wide configuration group for all devices
supporting High-Availability Upgrade. |
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| etsysHauModuleGroup |
1.3.6.1.4.1.5624.1.2.84.2.1.2 |
| The module specific configuration group for all devices
supporting High-Availability Upgrade. |
| Status: current |
Access: read-write |
| OBJECT-GROUP |
|
|
|
| etsysHauCompliance |
1.3.6.1.4.1.5624.1.2.84.2.2.1 |
| The compliance statement for entities which implement
the Enterasys High-Availability Upgrade MIB. |
| Status: current |
Access: read-write |
| MODULE-COMPLIANCE |
|
|
|