HP X9000 Series 6.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Version: 6.0 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.
Workarounds Following are workarounds for product situations that may occur: Management console • If the management console service is stopped on the active management console and, within a minute, the passive management console experiences a shutdown or reboot, the passive management console will become active when the node is restarted. When the fusionmanager is started on the formerly active management console (or that node is rebooted), that management console will also be in active mode.
available from the file serving node to which Windows Share Management was connected, it will not be propagated to the other file serving nodes in the cluster. • The ibrix_localusers -i command fails if the user information includes commas. To enter commas in the user information, use the management console GUI instead of the CLI.
Block snapshots • Snapshot creation may fail while mounting the snapshot. The snapshot will be created successfully, but it will not be mounted. Use the following command to mount the snapshot manually: ibrix_mount -f -m / • Quotas are disabled on block level snapshots (for example, MSA2000 snapshots) and the quota information from the origin file system is not carried to the block level snap file system. Block level snapshots are temporary file systems that are not writable.
xattr value ibrix.virtual.retention_state, Operation not supported, or Error recovering attributes. • The ibrix_vs_snap command cannot delete a block snapshot file system that is enabled for data retention. Instead, use the ibrix_fs command with the -R option. For example: ibrix_fs -d -f block_snap_ifs2_1 -R Segment evacuation • The segment evacuator cannot evacuate segments in a READONLY or BROKEN state.
• Email notifications do not include information about failed attempts to collect the cluster configuration. • In some situations, ibrix_collect successfully collects information after a system crash but fails to report a completed collection. The information is available in the /local/ibrixcollect/ archive directory on one of the file serving nodes.
The default value of this command is 900; the value is in seconds. A higher value reduces the probably of all components toggling from Up to Stale and back to Up because of the conditions listed above, but will increase the time before an actual component failure is reported. HP Insight Remote Support • In certain cases, large number of error messages such as the following appear in /var/log/ hp-snmp-agents/cma.
General • The ibrix_pv -a -o mpath command does not recognize a multipath device. The command works properly when an argument is added to ignore the standard scsi devices. Execute the command as follows, specifying the path to your device. ibrix_pv -a -o accept:/dev/mapper/mpath10,~standard • HP-OpenIPMI does not work with the HP-Health service. For example, Proliant health check tools such as SMH and SIM and hpasmcli commands such as SHOW POWERSUPPLY do not report errors.
