HP X9000 Series 6.0.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Version: 6.0.1 (build 6.0.340) Description This release contains updates to HP X9000 File Serving Software, HP X9320 and X9720 Network Storage Systems, and HP X9300 Network Storage Gateway systems. The X9000 Software features a highly scalable file system, CIFS, NFS, FTP, and HTTP file services, high availability, remote replication, data validation, snapshots, data tiering, and CLI and GUI management interfaces, and is installed on HP Network Storage System and Network Storage Gateway servers.
Software Supported versions CIFS clients • Windows 7 • Windows Vista • Windows XP • Windows 2008 • Windows 2003 • MAC 10.5 and 10.6 Internet Protocol IPv4 iLO firmware iLO2 2.05 for G6 servers iLO3 1.16 for G7 servers Browsers for management console GUI nl • Microsoft Internet Explorer 8 and 7 • Mozilla Firefox 3.6 and 3.5 • Adobe Flash Player 9.0.
2.05 using the following URL and copy the firmware update to each G6 server. Follow the installation instructions noted in the URL. This issue does not affect G7 servers. http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.
Remote replication The following changes have been made in this release: • The remote replication commands have been renamed. Be sure to update any scripts using the old names. Event messages still refer to remote replication as CFR. ◦ The ibrix_cfrjob command has been renamed ibrix_crr. The new -X option specifies an exported directory on the target and is used only for remote cluster replication. Previously, -P was used for this purpose.
Block snapshots The following changes have been made in this release: • Block snapshots can now be scheduled only through the GUI. The ibrix_at command is no longer supported. • The names of the CLI commands have been changed. Be sure to update any scripts using these commands. ◦ The ibrix_snap command now applies to the software snapshot feature. ◦ The ibrix_vs_snap command is now used for block snapshots. The ibrix_snap_strategy command has been renamed ibrix_vs_snap_strategy.
Fixes in the 6.0.1 release (build 6.0.340) The following fixes were made in this release: • The correct creation time was not maintained when a file on a CIFS share was modified or moved. Now, when a file is moved or modified, the original creation time is preserved as a file property visible to the client. • It was possible to create two directories with the same name, but differing in case, if one of the names used characters from the Latin-1 character set.
When a segment is successfully evacuated, the file system segment unavailable alert is displayed in the GUI and attempts to mount the file system will fail. There are several options at this point: ◦ Mark the evacuated segment as bad (retired), using the following command. The file system state changes to okay and the file system can now be mounted. However, the operation marking the segment as bad cannot be reversed.
1. Determine which management console is running the cluster virtual interface: ifconfig -a In the output, check for a configured bond0:1 virtual interface. 2. Place the management console that is not running the cluster interface into maintenance mode, and then place it into passive mode: ibrix_fm -m maintenance ibrix_fm -m passive If the recovery is not successful, contact HP Support. • If the node hosting the active management console goes down, it is important to reboot it as soon as possible.
on a CIFS file shared out by serverX, specify serverX\user1 in the Add dialog box on the security tab. If you later use the Windows security tab to look at this ACL, the server name will have been replaced by LOCAL (the CIFS server performs this remapping to ensure that local users are symmetric between all servers in the cluster, and are not specific to any one machine name in the cluster.
Remote Replication • 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.
ID>-.info (for example, Rebalance_29-ibfs1.info).
1. On the standard management console, check for the IbrixServer RPM: # rpm –qa | grep –i IbrixServer If the RPM is present, the output will be similar to the following: IbrixServer- 2. If the IbrixServer RPM is present, uninstall the RPM: # rpm -e IbrixServer- 3. On each file serving node, check for the Ibrix Fusion Manager RPM: # rpm –qa | grep –i IbrixFusionManager If the RPM is present, the output will be similar to the following: IbrixFusionManager- 4.
If you want to keep logging enabled, be aware that the log messages occur frequently, and you will need to monitor and clean up the log file regularly to avoid filling the file system.
• The log files for user-initiated tasks (such as running ibrix_fsck and migrating or rebalancing segments) are not rotated automatically. To control the space used by these log files, you will need to maintain them manually. The log files are located in /usr/local/ibrix/log. • NFS locks may return an error code (37) after an unlock operation even though the lock was correctly released. If other results are normal, you can ignore this error code.
Compatibility/Interoperability Note the following: • Every member of the cluster must be running the same version of X9000 Software. • The cluster must include an even number of file serving nodes. • All X9000 clients must be running 6.0.
