6.3.3 HP StoreAll OS Release Notes (AW549-96082, January 2014)

Correct firmware versionDrive descriptionDrive model
HPD7 or laterHP 2TB 6Gb/sec SAS 7.2K RPM 3.5-inch (LFF) Hard DriveMB2000FBUCL
HPD7 or laterHP 3TB 6Gb/sec SAS 7.2K RPM 3.5-inch (LFF) Hard DriveMB3000FBUCN
• Obtaining a crash dump on an X9720 with ProLiant G6 servers may occasionally be unsuccessful.
The X9720 platform use two bond devices and the crash kernel attempts to use both bond devices,
but an error in the NIC driver results in a failure when starting the second bond. To work around
this issue, you can disable bond0 as follows:
1. In the following files, change ONBOOT=yes to ONBOOT=no:
- /etc/sysconfig/network-scripts/ifcfg-bond0
- /etc/sysconfig/network-scripts/ifcfg-eth0
- /etc/sysconfig/network-scripts/ifcfg-eth3
2. Enter the following command:
touch /etc/kdump.conf
3. Enter the following command:
/etc/init.d/kdump restart
Once the crash dump is created, you can re-edit these files and change the setting back to
ONBOOT=yes.
• On 9730 systems, the iLO can fail to power up a server when directed to do so from the iLO web
page or the iLO's Integrated Remote Console. To correct this condition, reset the iLO processor.
This can be done from the iLO web UI; select Reset on the Diagnostics page.
• Incorrect status reporting the storage is degraded when it is not occurs because the monitoring
software did not know that the credentials to the storage array had been changed and could not
communicate with the array and became confused. A future release will correct the events and
make them more useful.
Remote replication
• The NIC status reported by the CRR health check may be outdated compared to the status reported
by the ibrix_nic –l command. This is due to the CRR health check reporting on stale data.
This issue will be fixed in a future release.
• When data is being copied to the target file system during a remote replication job (either
continuous or run-once), on rare occasions, a synchronization issue may occur while the
domain_scan phase is in progress as part of the replication job. As a result, some files may be
missing from the target file system. To resolve the issue, restart the replication job (note that it is
possible the issue could occur again). This will be fixed in a future StoreAll release.
• Remote replication might fail to transfer Windows Access Control Lists (ACLs) if cross-protocol
ACL synchronization is enabled on the source cluster nodes, but not on the target cluster nodes.
Before starting the replication, ensure that cross-protocol ACL synchronization is enabled on all
source and target cluster nodes.
• When remote replication is running, if the target file system is unexported, the replication of data
will stop. To ensure that replication takes place, do not unexport a file system that is the target
for a replication (for example, with ibrix_crr_export -U).
• Remote replication will fail if the target file system is unmounted. To ensure that replication takes
place, do not unmount the target file system.
• When continuous remote replication is used and file serving nodes are configured for High
Availability, you will need to take the following steps following failure of a node:
28 Workarounds