HP StoreAll OS v6.3.
© Copyright 2013, 2014 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Description These release notes describe StoreAll OS Software version 6.3.122. Customers running StoreAll OS Software 6.3.x, 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 OS Software 5.3.2 or earlier versions should contact HP Support to determine compatibility before updating their software.
Other supported software Software Supported versions Linux StoreAll clients • Red Hat Enterprise Linux/CentOS 5.7, 5.8, 6.1, 6.2, 6.3, 6.
NOTE: The HP-SMB server supports the following languages for file and directory names: English (ASCII), Latin-1 (Danish, German, French, Spanish, Italian, and Portuguese), Russian, Greek, Japanese, Korean, and Chinese (Mandarin). This language support will be available for file share names in a future release. 6.3.3 release Enhancements The intent of the 6.3.3 release was to resolve key issues found in earlier releases.
ibrix_event –l –n 21474883647 > /local/ibrix_event_l_all.log 6 • After using the QR DVD for installation and configuration, the default gateways for the Cluster and User networks are now restored by restarting the network. This ensures users can connect to the StoreAll services, which are on the User network, without rebooting the server. • Temporary files that are created during the restoration of WORM-retained and legal hold files are now deleted when the restoration is complete.
NOTE: You can reboot a node at any time. The purpose of implementing these features is to ensure the maximum uptime of a node does not exceed 400 days, thereby preventing file system performance issues. To reboot the node, see "Powering file serving nodes on or off" in the Administrator Guide for your model. • The ibrix_fsck command now runs successfully on a file system that had the root segment evacuated.
• When the virtual interface (VIF) IP address is changed after initial installation or after Phone Home configuration, the change is automatically detected by SNMP traps and Phone Home solution information. (The Fusion Manager IP address still needs to be rediscovered in HP Systems Insight Manager (SIM) with the new VIF IP.) Previously, the traps and solution information detected the old VIF IP address until the Fusion Manager was restarted or Phone Home was reconfigured.
6.3.2 release Enhancements The intent of the 6.3.2 release was to resolve key issues found in earlier releases. Updated firmware included in the Firmware Management Tool (FMT) • 1210m controller firmware version 1.78 (9730) • ibrix_cifs and other scripts now correctly display output for user names starting with an “n”.
• Under certain circumstances, the purge utility was not working correctly during the snapshot reclamation task, which prevented the snapshot directory (snaptree) from being deleted. The fix ensures the purge utility works correctly. • After an installation (and system reboot) using the QR DVD, the output of the date and hwclock settings did not match.
When this occurs, you must reset the switch manually. • When using the ibrix_auth command to add a user as share administrator, the versions of user DB maintained by Fusion Manager and HP-SMB will be in sync. • When a target cluster node is rebooted/failed over, it is now repeatedly checked for UP status by the CRR job. This ensures that all target nodes are participating in the replication, which results in maximum replication performance.
Fixes • 12 Firmware release version 1.42 provides the following enhancements: ◦ The timeout for READ CAPACITY commands was increased to 45 seconds. Previously, certain drive models would be identified as FAILED shortly after a replacement drive was inserted (if the response time exceeded 15 seconds). ◦ Fixed regressions introduced in firmware version 1.40 that caused the controller to occasionally hang during replacement drive insertion.
• Some SNMP managers, such as Netcool Omnibus Manager, received StoreAll SNMP traps with an incorrect Specific Trap type and mismatched variable bindings. The fix changes the SNMP Trap OID (OID of IBRIXGENERICEVENT) to “.1.3.6.1.4.1.18997.2.0.1” and adds “eventIndex” to the variable bindings. Additionally, this fix includes a change to the StoreAll MIB file, which requires the following configuration steps after installing the 6.3.1 patch: 1.
• The file name in the DCN response was changed to be the relative Windows file name (which is the Windows server behavior) instead of the absolute UNIX file name. • The HP-SMB share management utility called lwnet previously failed when run with the lwnet share --set-info option. This occurred only when a domain user was used in the command, and the node had been removed from the domain. • Wrapper scripts were modified to accept spaces in arguments.
The ibrix_collect command has also been expanded so that the field can create add-on scripts that capture custom StoreAll and operating system commands and logs. See the HP StoreAll Storage CLI Reference Guide for additional information. See “Fixes” (page 15) for a list of fixes in this release. Fixes • When using the –e “date/timestamp” option in the ibrix_reten_adm command, the command now correctly handles date strings that include spaces.
• After an upgrade, the following message no longer appears: The IbrixArchiving rpm is not installed. • Use of StoreAll Native clients for any SUSE or SLES kernel is now supported for file systems with Express Query enabled. • The MDImport tool can now import large files created by MDExport or ibrix_audit_reports.
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. • For performance reasons, when an NDMP backup is in progress, Antivirus scans are not triggered for the files being backed up.
LVM view. This issue is a timing condition for large file system delete operations where the delete 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.
Data retention and validation • In a retention-enabled file system, if the absolute pathname (/FSNAME/) of the file is greater than 1023 characters, the checksum is not generated and the validation scan fails. • When using the ibrix_datavalidation –s –f FSNAME [-d PATH] command, be aware that if the PATH is a StoreAll Archiving Infrastructure directory, the files within the path will not be validated.
can assign custom attributes to a soft link that differ from the custom attributes assigned to the target of the link. • The following Express Query audit event types are not yet audited when data validation scans start and end, even when enabled. ◦ val_scan_started ◦ val_scan_ended The audit event types are in place to support this functionality in the future.
3. 4. 5. 6. 7. 8. Increase the file descriptor limit for Fusion Manager from 2048 to a larger number based on your environment. Save the file. Repeat Steps 1 through 4 for each Fusion Manager server. Disable High Availability from the High Availability Configuration Wizard for all Fusion Manager servers or use the following CLI command:ibrix_fm -m nofmfailover -A. Restart Fusion Manager for your changes to take effect for all Fusion Manager servers.
hpsp_credmgmt --update-cred -s couplet:couplet/array//mgmtport_b/rw --cred-type upwpair --cred-username manage --cred-password '!manage' hpsp_credmgmt --update-cred -s couplet:couplet/array//mgmtport_b/ro --cred-type upwpair --cred-username monitor --cred-password '!monitor' 3.
1. Stop Express Query: ibrix_archiving -S 2. Evacuate the segment. 3. Fail over a server (ibrix_server -f -h ) 4. Unmount the file system. Workaround: Restart the server with the issue before unmounting the file system. • 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. This situation occurs because StoreAll software requires standard RHEL IPMI.
• 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.pid -a" To enable the default SNMP logging, add a pound sign (#) to the following command in the file /etc/sysconfig/snmpd.options and save the file: # OPTIONS="-LS 0-4 d -Lf /dev/null -p /var/run/snmpd.pid -a" Then do the following: ◦ If Phone Home was configured, reconfigure it.
ibrix_fsck • 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. • After running a tiering, rebalance or segment evacuation job, a phase 1 of the ibrix_fsck command might display a message regarding “bad replica” inodes.
• If StoreAll does not discover a node in your cluster, verify that the ibrix_discovery service is running by entering the following command on the node that was not discovered: service ibrix_discovery status If the ibrix_discovery service is not running, enter the following command to start the service: service ibrix_discovery start • After a server is rebooted following a QR install and before the server is configured, an error message reports that the SRVSVCD service failed to load.
◦ ST1000NM0023, ST2000NM0023 ◦ ST3000NM0023 ◦ HUS723020ALS640, HUS723030ALS640 ◦ MK1001TRKB, MK2001TRKB ◦ EG0900FCSPN, EG0900FDJYR ◦ WD1001FYYG-70SL3W0, WD2001FYYG-70SL3W0, WD3001FYYG-70SL3W0 ◦ HUS724020ALS640, HUS724030ALS640 As a result, the FMT displays a message that these disk drives are unsupported, which is incorrect. The disk drives are supported; the firmware has just not been added to the FMT yet. This will be fixed in a future release of the FMT.
Drive model • Drive description Correct firmware version MB2000FBUCL HP 2TB 6Gb/sec SAS 7.2K RPM 3.5-inch (LFF) Hard Drive HPD7 or later MB3000FBUCN HP 3TB 6Gb/sec SAS 7.2K RPM 3.5-inch (LFF) Hard Drive HPD7 or later 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.
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.
1. On every StoreAll cluster node, execute the following commands: [root@ibrix01b ~]# /opt/likewise/bin/lwregshell \> cd [HKEY_THIS_MACHINE\Services\lwio\Parameters\Drivers\ibfs] HKEY_THIS_MACHINE\Services\lwio\Parameters\Drivers\ibfs> add_value AllowPVFSFilemodeChange reg_dword 0 HKEY_THIS_MACHINE\Services\lwio\Parameters\Drivers\ibfs>exit 2.
are symmetric between all servers in the cluster, and are not specific to any one machine name in the cluster.) • When joining an SMB domain, the $ character cannot be used in passwords unless it is escaped with a slash (\) and enclosed in single quotes (' '). For example: ibrix_auth -n IB.LAB -A john -P 'password1\$like' • If you are using a Windows Vista client and running more than a single copy of Robocopy from that client, a hang is possible.
connected to a busy server, they may be encountering timeouts from overload. For more information about SMB client timeouts, see http://support.microsoft.com/kb/102067. SNMP • When the StoreAll SNMP agent is configured, do not restart snmpd. If the snmpd restart command is run on the active node, you will need to take one of these steps: ◦ If Phone Home was configured, reconfigure it. ◦ If Phone Home was not configured, reconfigure the StoreAll SNMP agent.
ERROR :Flash not attempted for SAS switch SAS_SWITCH_BAY_4 : Flash operation has failed for Peer switch in interconnect bay 3. Skipped flashing of this switch In this output, the peer switch in interconnect bay 3 is the victim switch. To resolve the issue: 1. Make sure that the affected switch has a working peer SAS switch. 2. Find the Onboard Administrator (OA) IP address by running the following command: hpsp_chassis_info -o 3.
----------------------------------------------------------------------------VSM-0025B3D4AD5D login: exds Password: HP Virtual SAS Manager CLI 2.2-17.0 (SEP 1 FW 2.82) (SEP 2 FW 2.82 6. Once the prompt is given, reset the SAS switch by entering the following command. sw local reset hardware forced The following is an example of the command’s output from a 9730: [2013-Jan-29 11:06:39] Hardware reset on Switch 5, Scope: Local switch only. Performing hard reset 7. 8.
The file system does not need to be unmounted when Express Query settings are enabled on a file system The 6.3 HP StoreAll Storage CLI Reference Guide says that the file system must be unmounted while running the ibrix_fs -T -E -f FSNAME command to enable Express Query settings on a file system. The file system does not need to be unmounted to run the command. Permissions cannot be assigned to objects individually for object mode shares The “Creating StoreAll REST API shares” section in the 6.
For example: • A file (a.txt) is created on a non-StoreAll file system (fs1). On fs1, the ctime and mtime both equal T. • The a.txt file is copied to a StoreAll file system (fs2) one hour later. On fs2, the ctime is T+1 hour and the mtime is still T. • fs2 has an autocommit period of 10 minutes and a data retention period of 30 minutes. When the 10 minute autocommit period has passed (T + 1 hour + 10 min), the copy is autocommitted.
