HP StorageWorks X9000 Series 5.5.
© Copyright 2011 Hewlett-Packard Development Company, L.P.
Version: 5.5.265 Description This release contains updates to HP StorageWorks 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 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 Internet Protocol IPv4 iLO firmware 1.82 and lower Browsers for management console GUI • Microsoft Internet Explorer 8 and 7 nl • Mozilla Firefox 3.6 and 3.5 • Adobe Flash Player 9.0.
reporting based on directory tree quota limits, use the ibrix_mount –o noquotstatfs option when you mount the file. • The GUI could not be accessed using port 80 or port 443. • Changing or generating a quotatree id no longer changes the mtime and ctime of files contained in the directory. • A directory tree quota could not be deleted if its name contained a space. • The Local Authentication feature allowed passwords to be entered only as text.
Remote replication • Running the X9000 Software snapshot feature on a file system that was a replica target for continuous remote replication could result in snapshot errors if the target was the root of the file system. • Subsequent remote replication jobs (run-once or continuous) started on the same source file system to the same target file system did not sync all objects that were deleted on the source between replications.
management console, and uninstall the IbrixFusionManager package from the file serving nodes. You can then upgrade the cluster. IMPORTANT: This workaround does not apply to clusters using the agile management console. The RPMs should not be uninstalled on these clusters. Complete the following steps: 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.
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_exportcfr -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.
If the recovery is not successful, contact HP Support. • If your cluster uses a dedicated management console, and you want to apply quotas to users and groups from your Active Directory (AD) domain, take the following steps before assigning the quotas: 1. Install the likewise-cifs.x86_64.rpm. (This RPM is in the /usr/local/ibrix/ installation/ibrix/distrib/engine/RHEL5/x86-64 directory in the X9000 Software distribution.) rpm –i likewise-cifs.x86_64-X9000_v5.5.rpm 2.
• Alternate Data Streams (ADS) are not supported. When a file with an ADS is moved or copied to the CIFS Server, X9000 Software moves/copies the file, but the attached ADS is not copied. Attempts to create an ADS or a filename containing a colon (:) will be failed by the CIFS Server. Some older versions of the CIFS Server allowed these ADS files to be saved as separate files with a colon (:) in their names, such as testfile.htm:Zone.Identifier or Thumbs.db:encryptable:$DATA.
occur for 15 to 20 minutes. The client's copy will then continue without error if the retry timeout has not expired. To work around this situation, take one of these steps: ◦ Stop and restart the Likewise process on the affected file serving node: # /opt/likewise/bin/lwsm stop lwreg && /etc/init.d/lwsmd stop # /etc/init.d/lwsmd start && /opt/likewise/bin/lwsm start srvsvc ◦ Power down the file serving node before failing it over, and do failback operations only during off hours.
Cluster component states • Changes in file serving node status do not appear on the management console until 6 minutes after an event. During this time, the node status may appear to be UP when it is actually DOWN or UNKNOWN. Be sure to allow enough time for the management console to be updated before verifying node status. • Generally, when a vendorstorage component is marked Stale, the component has failed and is not responding to monitoring.
• The log files for user-initiated jobs (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. • When you perform a Quick Restore of a file serving node, the NFS, CIFS, FTP, and HTTP export information is not automatically restored to the node.
ftp:ftp and not by the user who uploaded to the share. In 5.5.257 and later releases, files uploaded to an FTP share are owned by the user doing the upload. Accessing HTTP shares. The HP StorageWorks X9000 File Serving Software User Guide incorrectly states on page 92 that when a file is uploaded into an HTTP share, the file is owned by daemon:daemon and not by the user who uploaded to the share. In 5.5.257 and later releases, files uploaded to an HTTP share are owned by the user doing the upload.
