HP StoreAll Storage 6.
© Copyright 2013 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Version: 6.3 (6.3.72) Description Update eligibility Customers running StoreAll File Serving Software 6.2.x, 6.1.x, 6.0.x, 5.6.x, 5.5.x, or 5.4.x are eligible for the update. Refer to the administrator guide for your storage system for specific update requirements and procedures. Customers running StoreAll File Serving Software 5.3.2 or earlier versions should contact HP Support to determine compatibility before updating their software. IMPORTANT: Some systems shipped from the factory with version 6.1.0.
Other supported software Software Supported versions Linux StoreAll clients • Red Hat Enterprise Linux 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 6.1, 6.2 (all 64 bit) nl • SUSE Linux Enterprise Server 11 (64 bit) • SUSE Linux Enterprise Server 10.3 (64 bit) • openSUSE 11.1 (64 bit) • CentOS 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 6.1, 6.
NOTE: For the latest compatibility information, see the HP StoreAll Storage Compatibility Guide on HP Storage SPOCK: 1. Go to http://spock.corp.hp.com/spock/index.aspx. 2. In the left navigation pane, select Storage Servers (NAS) under Other Hardware. 3. Select HP StoreAll Storage Compatibility Guide in the right pane. Updated X9730 firmware included in the Firmware Management Tool (FMT) • 1210m controller firmware version 1.72 • 6GB SAS Switch firmware version 3.2.2.
• A crash would sometimes occur while renaming a folder. • Quotas were being incorrectly reported after an upgrade. • The ibrix_fsck command was showing "illegal inode number while reading inode." • The ibrix_vs -a command would fail on combined 9730+9720 and 9320+9730 clusters. • Long delays (approximately 10 minutes) followed by an HTTP status code in the 5XX range would occur while using the StoreAll REST API. • The server running the active Fusion Manager would inexplicably reboot.
delay now occurs after the file closes so that all data can be flushed before the antivirus scan. This 35-second delay resolves the issue of the antivirus scan not detecting a closed infected file while the scan policy is set to CLOSED or BOTH.
Terminate the ibrix_aj_ command, which is mentioned in the output, by pressing Y to continue with the upgrade. • The Firmware Management Tool is sometimes unable to update the firmware for a 9720 or 9730 SAS switch when the hpsp_fmt -f chassis command is entered.
NOTE: This pass through connection to the integrated I/O console is provided for convenience and does not supply additional access control. For security reasons, use the password features of the integrated switch. The following is an example of command’s output: Connecting to integrated switch 3 at 115200,N81...
Express Query Database • If you use hard links, be aware that there could be some inconsistencies in the metadata stored in the Express Query database. If you perform any file system operations on a hard link that changes the system metadata, metadata stored in the file system is updated, and it is visible to a stat call to any of the links to that file.
previously active management console from nofmfailover mode to passive mode. (Use the ibrix_fm -i command to check the mode of each management console.) If the passive management console has not yet assumed active mode, the management console being moved from nofmfailover to passive mode will become active again. Management console • File system creation on the 9300 server fails from the Getting Started Wizard.
1. Enter the following CLI command: ibrix_event -p [-o DAYS_COUNT] If you want to change the number of days the event database is purged, include the -o DAYS_COUNT option when you enter the command. Events are removed starting with the oldest events. The default is to remove the oldest seven days of messages. Purge the event database periodically to prevent it from becoming too large. 2. After the events are purged, create a new FM Store archive by entering the following command: ibrix_fm -B 3.
3. To verify your installation of the credentials, list the credentials by entering the following command: hpsp_credmgmt --get-cred -s couplet:couplet/* --output-sl The command displays the credentials for your system. Your output would differ from the following example to reflect your system configuration: 10.125.2.221|monitor|!monitor|couplet:couplet/array/500c0ff1390c0000/mgmtport_b/ro 10.125.2.221|manage|!manage|couplet:couplet/array/500c0ff1390c0000/mgmtport_b/rw 10.125.2.
• If you are using a Windows Vista client and running more than a single copy of Robocopy from that client, a hang is possible. The work around is to disable the SMB2 protocol on all file serving nodes. Complete these steps: 1. Disable the SMB2 protocol on all nodes: ibrix_cifsconfig -t -S SupportSmb2=0 2. Restart the SMB service on all nodes: ibrix_server -s -t cifs -c restart You may also need to restart the Windows client, as the original negotiated protocol, SMB2, may be cached by the client.
LDAP • When configuring LDAP on the GUI, double quotes are not supported in any fields of the LDAP configuration window, including the password field. Also, escaped slashes are not supported. If you enter \\; it will be parsed literally as \\ instead of \. Also, the ibrix_ldapconfig command supports double quotes only at the beginning and end of a value. For example: ibrix_ldapconfig -a -h 10.30.239.174 -b "cn=Manager,dc=ldapx,dc=net" -p "mypassword " The command does not support escaped slashes.
1. 2. Stop continuous remote replication. After the migration to the surviving node is complete, restart continuous remote replication to heal the replica. If these steps are not taken, any changes that had not yet been replicated from the failed node will be lost. • No alert is generated if the continuous remote replication target becomes unavailable. Confirm the connection to the target system by issuing a ping command and by inspecting ibrcfrworker.log.
https:///fusion/reporting/retention/retention_ifs1.pdf ◦ Log into the node specified as the hostname in the URL and go to the directory /usr/local/ ibrix/reports/output/retention, which contains the report. Antivirus support • If McAfee is used as a virus scan engine, when virus definitions are updated on the virus scan engine, the updated definitions are not sent automatically to the StoreAll servers. To correct this condition, request hotfix HF692368 from McAfee.
• 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. Cluster component states • Changes in file serving node status do not appear on the management console until 6 minutes after an event.
• If Fully Qualified Domain Name (FQDN) resolution is not configured properly for the hosts, the following error appears when hpsmhd is restarted: Could not reliably determine the server's fully qualified domain name, using for ServerName To configure FQDN resolution, use either the /etc/hosts file or the Domain Name Service. • If SNMP is logging excessively, add the following command to the file /etc/sysconfig/ snmpd.options to stop the logging: OPTIONS="-LS 0-4 d -Lf /dev/null -p /var/run/snmpd.
Windows Client • If the StoreAll Windows Client is registered with Fusion Manager already, clicking on Start Service After registration under the Registration tab displays a Response Code =400 error. Click the Recover Registration option instead. General • A crash might occur if there is a change in ownership of the file while a quota is being enabled. There are plans to provide a fix in a future release. • The output from the ibdircheck command might show incorrect statistics counters.
command times out while waiting for a response from the storage. Although the deletion was successful the command reports it as failed and StoreAll preserves the associated volume group (ivg) and logical volume (ilv). This issue has been observed on the HP StoreAll 9730. To resolve this issue, rerun the logical volume delete command using the “-X” override option, for example: ibrix_lv -d -s —X The override option forces the removal of the StoreAll Logical Volume record from the StoreAll database.
requires that the network subsystem be configured. The error message can be safely ignored. After the network is configured, restart the SMB service. Installation instructions New installations HP StoreAll software is preinstalled on supported devices. If you need to reinstall the software, see the administrator guide for your storage system. Upgrades The upgrade procedure is provided in the administrator guide for your storage system. Contact HP Support for assistance with the procedure.
