HP StoreAll OS 6.5.1 Release Notes

• Setting a standby NIC for a user VLAN parent device results in a FAILED status when executing
the ibrix_haconfig -l command.
To avoid the FAILED status when configuring VLAN user NICs with standby NICs, create a parent
device (for example, bond0.vlan) with two VIF devices: bond0.vlan:2 and bond0.vlan:3.
In this instance, bond0.vlan:2 is the user NIC IP and bond0.vlan:3 is the standby VIF.
• When creating a user NIC with a VLAN tag on a bond, running the ibrix_nic -c command
causes the parent bond to become degraded. The workaround is to determine the device that is
down and then bring up that device manually. For example, if bond0 consists of eth4 and eth5,
use ifconfig to determine which device is down. Then use ifup to bring up the device, such
as ifup eth4.
• If StoreAll does not discover a node in your cluster, verify that the ibrix_discovery service
is running by entering the following command on the node that was not discovered:
service ibrix_discovery status
If the ibrix_discovery service is not running, enter the following command to start the service:
service ibrix_discovery start
Object Store
• When creating an Object Store share, if the port being used to create the share is being used by
another process, the Object Store share creation will fail. To resolve this issue, verify that the port
being used is not currently in use by another process and then retry the share creation.
Additionally, when this issue occurs, the message that displays may appear misleading (indicating
the share creation was successful even though it was not):
Object Store created successfully on <node name>, <node name>
Object Store service(s) failed to start.
Reason: Error from remote Fusion Manager:
400:The request could not be understood by the server due to malformed syntax
The message about Object Store creation covers the status of the share creation and the status of
the Object Store services. In this situation, the initial status of Object Store share creation is
successful. However, because the services failed to start (as noted in the second part of the
message), the end result is that the Object Store share creation is rolled back (the share is not
created). This allows you to re-create the Object Store share successfully.
• When creating an Object Store share, the default administrator group for Local Users
(IbrixSwGroup, Group ID 2001) must be created, if it does not already exist. If another Local
User group exists that uses Group ID (GID) 2001, then creating the IbrixSwGroup group may
fail, which causes the Object Store creation to fail. If this issue occurs, you must manually create
the group and update the Object Store Keystone configuration file with the new Group ID (GID).
1. View the list of existing Local User groups to determine if the issue exists. Execute the following
command:
ibrix_localgroups –L
Command output example:
Group Name Group ID Group RID
------------- -------- ---------
NonOwnerGroup 2003 2003
OwnerGroup 2002 2002
group1 2001 2001
2. If the output indicates a group is using GID 2001 (group1, in the example output in step 1),
you must create the IbrixSwGroup group manually by executing the following command:
NOTE: When creating the group, either assign an unused GID or allow the StoreAll OS
Software to select one.
Workarounds 27