HP IBRIX 9000 Storage 6.2.
© Copyright 2013 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Version: 6.2.2 (build 6.2.386) Description Update eligibility Customers running IBRIX 9000 File Serving Software 6.2.1, 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 IBRIX 9000 File Serving 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 9000 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 SP3 (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.
Enhancements The intent of the 6.2.2 release was to resolve key issues found in earlier releases. See “Fixes” (page 7) for a list of those fixes. Enhancements in the 6.2.1 release The 6.2.1 release provides the following enhancements.
Implementation changes in the 6.2.1 release The following implementation changes occurred with hardware monitoring: • During an upgrade, user must now run the Firmware Management Tool and perform a set of manual steps to update the firmware. • All of the logical (volumes) and physical (controllers, ports, drive enclosures, drives, etc.
restrictions have been implemented on rename operations. The following restrictions apply to hybrid file systems: • Only directories created in version 6.0 or later can become snap tree roots. • If the old directory is not in a snap tree and the new directory is in a snap tree, rename is allowed only if the object being renamed is snapable (that is, it has the new inode format). The following restrictions apply to both hybrid file systems and pure 6.x file systems: • A snap tree root cannot be renamed.
• Fusion Manager (FM) restarted a CFR job even if it is marked “stopped by the user.” Fusion Manager has been modified so that it does not automatically restart a CFR job when the user requests the CFR job to be stopped. • A soft lockup of the CPU was occurring during connection/delegation recovery.
in the kernel log (BUG: soft lockup – CPU# stuck for 10s! [i_worker_X:]). The serialization issue has now been fixed. • There was a request to document file system mount information (specifically, the change to the default mount options in 6.1 and the use of ibrix_mountpoint to set mount options). The man pages for the ibrix_mount and ibrix_mountpoint commands and the HP IBRIX 9000 Storage File System User Guide were updated.
is used, the server failover process sends the VIF to the running/active node. If I/O has occurred through a non-virtual IP for the server, this I/O might need to be halted, and you might need to reboot the server to proceed with an online upgrade. • After upgrading to 6.2.1, use the Firmware Management Tool (FMT) by entering the hpsp_fmt –fr server) command to determine if any firmware upgrades are required.
NOTE: 2. The above command does not place the local/Active FM in nofmfailover mode. Make the desired node passive by entering the following command: ibrix_fm -m passive -h 3. 4. Wait 1 minute for the commands to complete. Place the current Active FM into 'nofmfailover' mode, this will trigger the migration by entering the following command: ibrix_fm -m nofmfailover 5. Wait another minute, after which, you should find the Active FM on the desired node.
and both the source and destination segments contain the file and its replica. To resolve this issue, add another segment and restart the evacuation process. 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.
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. • File system creation on the 9300 server fails from the Getting Started Wizard.
1. Enter the hpsp_couplet_info -i command to get a list of UUID for attached MSA enclosures. Each enclosure is on a separate line, as shown in the following example of the command and its output: [root@ib25-02s1 security]# hpsp_couplet_info -i 500c0ff1390c0000 2. Install the credentials for a single MSA by running the following four commands once for each MSA that the hpsp_couplet_info command lists in step 1.
drive enclosures that are connected behind the first drive enclosure. If the customer restarts the other storage controller that has access to the enclosure or removes the other cable to the enclosure loss of access to storage will occur. ◦ Spurious failure indications and potential system crashes can occur if storage controller or hard drive firmware is flashed while monitoring is active. Run the hpspmonControl --pause command on both servers in the couplet before performing the flash operation.
Hung Task Enter the following command on one line to kill the specific coordinator process /usr/local/ibrix/bin/migrator_daemon --serviceid=4100 --port=9174 -f ifs2 --logflag=6 -L /usr/local/ibrix//log/ -j Migrator_58-ifs2-worker1 SnapReclamation /usr/local/ibrix/bin/purge_coordinator --serviceid=5379 --port=9173 -D -y -f ifs2 -L /usr/local/ibrix//log/ -j SnapReclamation_59-ifs2 DataValidation /usr/local/ibrix/bin/validation_coord --serviceid=6147 --port=9173/usr/local/ibrix/bin/validator --jobid=60 --fsn
local users 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.
The LDAP ID mapping features depends on successful communication with the configured LDAP server. The openldap-clients- RPM is required to perform ldapsearch commands from the command line. This RPM is available on the OpenLDAP site. • Increasing the values of the LdapMaxWaitTime and LdapMaxEntries can affect the performance of name resolutions for SMB and non-SMB users in large LDAP directory environments. The AD name cache protects against excessive LDAP searches.
• The mountpoint /mnt/ibrix is reserved for remote replication. Hiding or blocking this mountpoint by mounting anything over the parent /mnt will prevent Run Once replication from working at all, and the initial domain scan of Continuous replication will fail. • When a replication task encounters a file on the target system that was added or changed outside of a previous replication, the replication task stops and does not replicate the remaining files from the source to the target.
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 IBRIX 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. The IBRIX server excludes the process corresponding to NDMP from scanning any files on a cluster with Antivirus enabled.
• 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 ibrix_collect command supports a maximum collection size of 4 GB. If the size of the final collection exceeds 4 GB, the collection fails. You must either: ◦ Delete the excess older logs from each node to reduce the size.
SNMP • When the IBRIX 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 IBRIX SNMP agent. HP Insight Remote Support • After HP Insight Remote Support is configured, do not restart snmpd. See “SNMP” (page 22) for more information.
IBRIX 9000 Windows clients • Reading of snaps as memory mapped files is not supported. Undesired results can occur if a snap file is used as memory mapped file while the current version of the file is being modified by a different instance. ibrix_fsck command • 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.
Contact HP Support for assistance. • You might not be able to mount a file system after an unmount if you: 1. Stop the metabox. 2. Evacuate the segment. 3. Failover of a server (ibrix_server -f -h ) 4. Unmount the file system. Workaround: Restart the server with the issue before unmounting the file system. • If the ibrix_auth command fails after a QR restore of a server in a cluster with a message similar to: ibrix_auth -n IBRQA1.HP.COM -A administrator@ibrqa1.hp.
Compatibility/Interoperability Note the following: • Every member of the cluster must be running the same version of 9000 software. • The cluster must include an even number of file serving nodes. • All IBRIX 9000 clients must be running 6.0 or later. Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com).
