6.3.2 HP StoreAll OS Release Notes

server. If the NTP and AD servers are not in sync, this causes the cluster nodes to receive conflicting
time updates, which can lead to errors such as file system creation failures.
To avoid this issue, ensure the AD server and the NTP server are synchronized so they have the
same time. Or, ensure that the AD server and the StoreAll cluster are configured to synchronize
the time from the same NTP server.
• After an upgrade or a new installation, the default value for the
clearSegmentUnavailableUponFailover parameter of the ibrix_fm_tune command
is incorrectly set to false (the correct default is true). To resolve this issue, run the following command
to reset the default value to true:
ibrix_fm_tune –S –o clearSegmentUnavailableUponFailover=true
• 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.
• On X9720 systems with G6 blades, the Quick Restore installation reports that the G6 Ethernet
firmware must be upgraded. The Ethernet device (eth0) must be up when you upgrade the
firmware. Use the following command to bring up eth0 and then upgrade the firmware:
# ifup eth0
The following document provides additional detail for HP Support personnel:
http://saw.cce.hp.com/km/saw/view.do?docId=emr_na-c03466768
• 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 is made up 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
Upgrades
• A large events database may cause the upgrade to fail during the “Upgrading Embedded
databases” stage. To prevent this issue, HP recommends that you archive and purge the events
database before starting an upgrade. To do so, enter the following commands:
#> ibrix_event –l >> /tmp/dbevents.log
#> ibrix_event –p –o -1
• After an upgrade or a new installation, the default value for the
clearSegmentUnavailableUponFailover parameter of the ibrix_fm_tune command
is incorrectly set to false (the correct default is true). To resolve this issue, run the following command
to reset the default value to true:
ibrix_fm_tune –S –o clearSegmentUnavailableUponFailover=true
• While running the Auto Online Upgrade process on a cluster with an Express Query enabled file
system, similar output might appear:
Warning: filesystem fs_bug is still open by some user access into the
mountpoint on this File Serving node.
Workarounds 13