HP-STACK-MIB: View SNMP OID List / Download MIB

This MIB module describes objects for managing the stacking features.

This notification is generated when the state of a stack port has changed.

This notification is generated when a new commander first comes up. The notification is also sent when a failover happens, and the standby becomes commander or when the commander is down.

This notification is generated when a new member joins the stack or when it moves from a loose provisioned to strict provisioned.

This notification is generated when a member becomes active or inactive.

This notification is generated when a new member attempts to join the stack, but was denied. This could be because of: a. Merge policy of stack prevents the switch from joining b. Merge policy of switch prevents it from joining c. Stacking disabled on switch d. No available member ID's on stack e. Switch is incorrectly provisioned (wrong J-Number, correct MAC). hpStackId here is the other Stack Id.

This notification is generated when a new member attempts to join the stack and have successfully merged. This will be sent by each stack that got merged.

The stack ID uniquely identifies the stack; all members of the stack have the same stack ID. A switch is considered to be a part of a stack When it has the same stack ID as the stack commander. The stack ID is valid only when hpStackSwitchAdminStatus is true (1). This value is set by the first elected commander and stays with the stack until the user sets the hpStackSwitchAdminStatus to 'false (2)' or when hpStackSetStacking is set to 'true (1)' in an inactive fragment.

This is the current operational status of the stack. Enumeration: 'disabled': 1, 'active': 2, 'fragmentInactive': 3, 'unAvailable': 0, 'fragmentActive': 4.

This variable allows configuration of a stack fragment created by a stack split. When set to 'true (1)' in the greater fragment, the physically present members of the current stack become the only members, and the configuration of the missing members is converted to strict provisioned configuration. When set to 'true (1)' on a lesser fragment, the existing stack information is cleared and a new stack ID is created. The switches in the stack will become 'active' and retain their configuration. No action is taken when set to 'false (2)' in any stack.

This describes the physical topology of the current stack. Enumeration: 'unKnown': 0, 'ring': 2, 'mesh': 3, 'chain': 1, 'partialMesh': 4.

This enables or disables the hpStack traps. Enumeration: 'enable': 1, 'disable': 2.

This is to set the split policy for the current stack. When there is a stack split, setting hpStackSplitPolicy to OneFragmentUp results in only one active fragment and the rest of the fragments remains inactive. Setting hpStackSplitPolicy to AllFragmentsUp results in all the fragments to be active. Enumeration: 'allFragmentsUp': 2, 'oneFragmentUp': 1.

Table to configure basic stacking feature.

A row in the stack config table.

This is the sequence number to this table. At any instance of time only one entry exists.

The admin status of the stacking feature. When set to 'enable (1)', this will enable stacking on a standalone switch that had stacking disabled previously. Once stacking is enabled, the switch will not have a stack ID and merges automatically to any stack it is connected to and learns the stack ID of that stack. It has no effect on a switch where stacking is already enabled. An error will be returned when attempting to set the value to 'enable(1)' on a switch that has secure-mode set to enhanced. Setting this to 'disable (2)' will disable stacking on a standalone switch. Once stacking is disabled, the stack ports will be kept down. This will prevent the switch from ever joining or creating a stack. This is allowed only on a standalone switch, that is, a switch that is not connected over a stacking link to any other switch. It has no effect on a switch where stacking is already disabled. Enabling or disabling stacking will trigger a reboot of the switch. When hpStackSwitchAdminStatus is set to 'true (1)', and if the user wants to set the preferred priority and the member ID of the switch, then hpStackSwitchPreferredPriority and hpStackSwitchPreferredMemberId needs to be set along with hpStackSwitchAdminStatus. If the priority and member ID are not specified, then the default values will be used. Enumeration: 'enable': 1, 'disable': 2.

This allows the user to set the priority of a switch when stacking is enabled on it. hpStackSwitchPreferredPriority needs to be set along with hpStackSwitchAdminStatus being set to 'true (1)'. Note that this is to be used only when enabling stacking. To set the priority of a switch on which stacking is already enabled, use hpStackMemberTable. hpStackSwitchPreferredPriority is unused when hpStackSwitchAdminStatus is false (2).

This allows the user to set the preferred member ID of a switch when stacking is enabled on it. hpStackSwitchPreferredMemberId needs to be set along with setting hpStackSwitchAdminStatus being set to 'true (1)'. This entry is useful only at the time of setting hpStackSwitchAdminStatus to 'true (1)'. hpStackSwitchPreferredMemberId is unused when hpStackSwitchAdminStatus is set to false (2).

Table to configure stack members.

A row in the stack member table.

This is the member ID of the switch and index to this table. This identifies each member in the stack.

This is the product ID [J-number] of the switch. When a member is provisioned, this is a mandatory field. The product must be capable of stacking support.

The MAC address that identifies the member switch. The configuration of MAC address will not be allowed if another table exists with the same MAC address.

For the members that physically exist, this will cause the switch to shutdown. If the switch is a standby, a new standby switch will be chosen. To shutdown, it needs to be set to 'true (1)'. A write operation of 'false (2)' leads to no operation. This can be set to 'true (1)' only if the member physically exists and is an active member of the stack. This variable cannot be set to 'true (1)' if the member ID corresponds to a commander. This object will always return 'false (2)'.

Setting this variable to 'true (1)' will reboot the switch. A write operation of 'false (2)' leads to no operation. This object will always return 'false (2)' Reboot is allowed only when a member exist physically.

This assigns the priority to the member. If the stack is rebooted and the members are assigned with priorities, then commander will be the one with the highest priority and the standby will be the one with the next highest priority. The following rules apply for assigning the priority: 1. In the existing stack, if the priority is increased, the member is likely to become commander only the next time the stack is rebooted, it will not be immediately elected as commander. 2. A switch with the highest priority will not be elected as commander if it is a new member of the stack even when the stack is rebooted as it will not have the latest configurations. 3. If a commander switch with highest priority fails over to standby, it will not become commander again in the subsequent reboot. The stack itself needs to be booted or the failover to this commander should happen. 4. A switch that joins an already active stack will not become the commander even if it has the highest priority. 5. If the priority is assigned to the member when it is in standalone state and when it joins the stack, if the stack configuration has an existing pre-provisioned priority for this member, then the pre-provisioned value preempts the standalone value. To assign priority to a member, the member can either be provisioned or physically present.

The status of a stack member entry. The member entry is created with the row status value as createAndGo (4) and the hpStackMemberProductId. The createAndWait(5) is not supported by this mib table. To remove the switch from the stack, row status is set to destroy (6). Setting it to 'destory (6)' is not allowed if the member ID corresponds to a commander switch. For the physically existing switch, if hpStackMemberReboot is set to 'true (1)' along with the row status to 'destroy (6), the switch will come up with a blank configuration and will acquire a new hpStackMemberId.

This gives the index of this member in the entPhysicalTable (rfc2737).

This gives the status of the switch in the stack. unusedId (0) - The member ID does not exist. missing (1) - A member switch in the stack when it becomes Non responsive, it is marked as the missing member. Either the stack link goes down or the stack member crashed. Note that it is possible to remove even the missing member from the stack. In this case, the missing members configuration is removed from the stack config file. provision (2) - A member switch whose config is provisioned and that does not exist physically. commander (3) - One physical switch whose master CPU takes up the role that the active management module in the 8200 switch would take. standby (4) - One physical switch whose master CPU takes up the role that the standby management module in the 8200 switch would take. member (5) - A switch that is part of the stack. shutdown (6) - The switch is in the shutdown state. booting (7) - The switch is in the booting state. communicationFailure (8) - This is an error condition. The switch cannot be reached. incompatibleOs (9) - This is an error condition. The member switch runs with a different OS image. unknownState (10) - The member switch's state cannot be determined. This is an error condition. standbyBooting (11) - The standby switch is currently booting up. When boot is completed, the state will be 'standby (4)'. Enumeration: 'communicationFailure': 8, 'missing': 1, 'standby': 4, 'unknownState': 10, 'incompatibleOs': 9, 'unusedId': 0, 'commander': 3, 'member': 5, 'shutdown': 6, 'booting': 7, 'standbyBooting': 11, 'provision': 2.

This gives the product name of the switch.

This provides the uptime of this specific member. This is different from the stack uptime.

This provides the sysObjectId of this specific member.

This is same as hpStackMemberId. This is useful only for the notifications.

This is the serial number of the member switch.

This is the percantage of CPU utilization of the member the switch.

This is the total memory usage in bytes of the member switch.

This is the free memory available, in bytes, on the member switch.

This is the boot ROM version in the member switch.

This is the switch operating system version on the member switch.

This is the boot image information of the member. Enumeration: 'primary': 1, 'secondary': 2.

Table of info about the stack ports.

A row in the stack port table.

This is the stack port ID.

This is the stack port type. Enumeration: 'backPlane': 1, 'frontPlane': 2.

This gives the stack port state. Enumeration: 'down': 2, 'disabled': 3, 'up': 1, 'blocked': 4.

This contains the value of the hpStackMemberId and hpStackPortId of the switch's chassis to which this stack port is connected. If the stack port is not connected, it returns a value of zero.

This gives the stack port cost.

This is same as hpStackPortId. This is useful only for the notifications.

This is same as hpStackPortType. This is useful only for the notifications. Enumeration: 'backPlane': 1, 'frontPlane': 2.

Setting this variable to 'enable(1)' is allowed only when hpStackPortOperStatus is in 'disabled(3)' state. A set operation of disable(2) is not allowed. A get operation on this returns 'enabled' only when the hpStackPortOperStatus is up. Enumeration: 'enable': 1, 'disable': 2.

The compliance statement for the hpStack mib.

A collection of objects for the basic stack configuration.

A collection of objects for the configuring a member switch of the stack.

A collection of objects providing information about the stack ports.

A collection of objects providing information about the stack ports.