HP IBRIX 9000 Storage 6.2.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Version: 6.2.1 (IBRIX Software) Description The IBRIX software release version 6.2.1 provides a number of important bug fixes and enhancements. Update eligibility Customers running IBRIX 9000 File Serving Software 6.1, 6.0, 5.6, 5.5, 5.4.1, or 5.4.0 are eligible for the update. Refer to the administrator guide for your storage system for specific update requirements and procedures. Customers running IBRIX 9000 File Serving Software 6.
Other supported software Software Supported versions Linux 9000 clients • Red Hat Enterprise Linux 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 6.1, 6.2 (all 64 bit) nl • Red Hat Enterprise Linux 4 Updates 5, 6, 7, 8 (all 64 bit) • SUSE Linux Enterprise Server 11 (64 bit) • SUSE Linux Enterprise Server 10 SP3 (64 bit) • openSUSE 11.1 (64 bit) • CentOS 4.5, 5.1, 5.2, 5.3, 5.
create custom metadata entries for a file, replace values of existing entries, and delete entries. The API extends the existing HTTP Shares feature that was introduced in IBRIX version 6.0. ◦ • • • Express Query — Express Query provides a per file system database of system and custom metadata, and audit histories of system and file activity.
• On the IBRIX 9320, Storage platform the HA_STORAGE health monitoring category has been replaced with the new STORAGE_CLUSTER category for monitoring couplet visible storage. The HA_STORAGE category is still supported but is being deprecated in the next release. • A subset of all visible storage clusters can be monitored by specifying a list of storage cluster UUIDs on the hpspmon command line. Prior to this change all storage clusters would have been monitored.
The following restrictions apply to both hybrid file systems and pure 6.x file systems: • A snap tree root cannot be renamed. Also, the path to a snap tree root cannot be changed. • Rename is allowed when neither the old directory or the new directory are in snap trees. • Rename is allowed when the old directory and the new directory are in the same snap tree. Rename is not allowed when the directories are in different snap trees.
decremented. Since the newly created file was not marked with the directory quota ID, it was never was accounted for. As a result, a reduction in quota usage was shown post replication. The fix was to mark the replica created with the quota ID same as that of the original file, so any data written into this file is accounted for against the set quota ID. • Data tiering could result in zero length files. • When a snapshot was taken, files could be deleted from the source directory.
• MDS600 and D6000 drive enclosure drawers are now reported by number: Drawer 1 for the front-facing left drawer and Drawer 2 for the front-facing right drawer. • For a list of fixes in the Storage Provisioning Tool (SPT), see the HP HPSP_SPT User Guide. Workarounds This section contains workarounds for product situations that may occur: Installation and network configuration • On 9720 systems with G6 blades, the Quick Restore installation reports that the G6 Ethernet firmware must be upgraded.
1. Manually check your version by entering the following command: ethtool -i eth0 The command displays the following: driver: be2net version: 4.1.402.6 firmware-version: 4.1.402.20 bus-info: 0000:02:00.0 Bootable ISO Download: 2. Verify the firmware-version is 4.1.402.20. If it is not, download a bootable ISO file (OneConnect-Flash-4.1.402.20.iso) from the following link to perform the NIC upgrade offline: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.
• System User login credentials are backed up and restored during upgrades. However, any user data is not retained. Users must save and restore their individual data manually during an upgrade. • If clients previously mapped an SMB share using the hostname/FQDN, they will be prompted continuously to enter their credentials when attempting to access the SMB share after the upgrade. (The share can be accessed successfully using the IP address.
for all other hard links to the same file will not show an updated last modified time in this example. Express Query will treat all hard links as if they are separate files. To find all hard linked files in a directory tree, enter the following command: find -links +1 -xtype f Soft links, also known as symbolic links, do not have the these inconsistencies with the metadata. Soft links are treated as "normal" paths by Metabox.
• File system creation on the 9300 server fails from the Getting Started Wizard. No data loss or corruption occurs, and you can still create the file system using the Create Filesystem Wizard or its comparable CLI command (ibrix_fs -c -f...). • File system creation from the Management Console, not the CLI, might sometimes fail with the message Exporting filesystem (NFS) failed. The file system was created correctly and all the other steps in the process have completed.
which status for all sensors in the array is unavailable. The statuses will be corrected in the next monitoring polling cycle. ◦ If there is a hardware event involving a fan in a D2700 drive enclosure then the location of the fan will incorrectly state that it is part of the enclosure’s power supply. The fan is a separate FRU in the D2700 drive enclosure. ◦ Disconnected SAS cables between D2700 small form factor drive enclosures are not detected by the hardware.
1. Enter the following command: ibrix_task –k –n -F 2. Manually kill the specific coordinator process related to rogue task. See the following table for information on how to kill each task. Hung Task Enter the following command on one line to kill the specific coordinator process OnlineQuotacheck /usr/local/ibrix//bin/ibrix_online_quotacheck, -f, -ugt, -M, 192.168.56.
• 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. • When you use the Windows security tab to add local users or groups to a security ACL on an SMB file (for either file or share-level permissions), you typically specify the user to add as either a DOMAIN\username or a MACHINE\username.
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.
has expired), use the touch command to set its last accessed time (atime) forward to the desired expiration time. The file will then be retained until that time. • PDF reports cannot be generated from the GUI when using Windows Internet Explorer 8. To display the PDF, use one of these options: ◦ On the browser, right-click in the white border surrounding the grey area, and select View Source. Locate the src= line in the source. For example: src="/fusion/reporting/retention/retention_ifs1.
Segment evacuation • The segment evacuator cannot evacuate segments in a READONLY, BROKEN or UNIVAILABLE state. NDMP • When Symantec NetBackup is used, a full backup job fails for a file system with large directory tree. To correct this, set TYPE=tar in the Backup Selections tab in Symantec NetBackup. This changes the backup type to tar instead of the default dump and forces NetBackup to handle the file-based NDMP file history.
components to toggle from Up, to Stale, and back to Up. Common causes of failures in the monitoring system include: ◦ Reboot of a file serving node ◦ Network connectivity issues between the management console and a file serving node ◦ Resource exhaustion on a file serving node (CPU, RAM, I/O or network bandwidth) While network connectivity and resource exhaustion issues should be investigated, they can occur normally due to heavy workloads.
service snmpd restart • On 9320/9720 systems, the virtual SAS manager and VC connect manager must be configured manually for HP Support. • On HP SIM 7.1, 9320/9300 nodes are discovered as “HP 9320 NetStor FSN” if MSA storage is registered on the cluster nodes. This does not affect sending alerts to HP Support. IBRIX 9000 Windows clients • Reading of snaps as memory mapped files is not supported.
successful the command reports it as failed and IBRIX preserves the associated volume group (ivg) and logical volume (ilv). This issue has been observed on the HP IBRIX 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 IBRIX Logical Volume record from the IBRIX database.
Installation instructions New installations HP IBRIX 9000 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. Compatibility/Interoperability Note the following: • Every member of the cluster must be running the same version of 9000 software.
