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.
EtsysHauSystemStatus1 = hauDisabled2 = hauPending3 = hauRunning4 = hauHalted5 = hauSuccess6 = hauError7 = hauForceCompleteThe 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. · Integer32
The status of the high-availability upgrade for this managed entity.
etsysHauStatsOriginalImage
1.3.6.1.4.1.5624.1.2.84.1.1.2
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
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).
etsysHauStatsTargetImage
1.3.6.1.4.1.5624.1.2.84.1.1.3
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
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).
etsysHauStatsPendingSlotList
1.3.6.1.4.1.5624.1.2.84.1.1.4
HauSlotListEach 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'. · OCTET STRING
Set of slots which have yet to be upgraded.
etsysHauStatsInProgressSlotList
1.3.6.1.4.1.5624.1.2.84.1.1.5
HauSlotListEach 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'. · OCTET STRING
Set of slots which are currently being upgraded.
etsysHauStatsUpgradedSlotList
1.3.6.1.4.1.5624.1.2.84.1.1.6
HauSlotListEach 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'. · OCTET STRING
Set of slots which have been upgraded.
etsysHauStatsErrorSlotList
1.3.6.1.4.1.5624.1.2.84.1.1.7
HauSlotListEach 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'. · OCTET STRING
Set of slots which have failed to be upgraded.
etsysHauStatsStartTime
1.3.6.1.4.1.5624.1.2.84.1.1.8
DateAndTimeA date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time when the most recent high-availability upgrade was started.
etsysHauStatsDuration
1.3.6.1.4.1.5624.1.2.84.1.1.9
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
The duration of the most recent current high-availability upgrade, in centiseconds.
etsysHauSystemInterGroupDelay
1.3.6.1.4.1.5624.1.2.84.1.2.1
Unsigned32 · seconds
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.
etsysHauSystemHauMode
1.3.6.1.4.1.5624.1.2.84.1.2.2
EtsysHauMode1 = hauNever2 = hauIfPossible3 = hauAlwaysThe 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. · Integer32
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.
Table details
etsysHauModuleTable
1.3.6.1.4.1.5624.1.2.84.1.3.1
Index: etsysHauModuleSlot
A table of high-availability properties per module.
etsysHauModuleSlot
1.3.6.1.4.1.5624.1.2.84.1.3.1.1.1
HauSlotLogical slot number which aligns with HauSlotList. (1..128) · Integer32
Logical slot for a given module.
etsysHauModuleEntRef
1.3.6.1.4.1.5624.1.2.84.1.3.1.1.2
PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d
Entity Physical Index which corresponds to this slot.
etsysHauModuleGroupId
1.3.6.1.4.1.5624.1.2.84.1.3.1.1.3
Unsigned32 (1..128)
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.