HP IBRIX X9000 Storage 5.6.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Version: 5.6.3 (5.6.151) Description This release contains updates to HP 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.
Other supported software Software Supported versions Linux X9000 clients • Red Hat Enterprise Linux 5.1, 5.2, 5.3, 5.4, 5.5 (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.
The 5.6.2 release provided the following implementation changes: • The default port for the X9000 SNMP agent has been changed from 161 to 5061. • The df command (and similar tools) report size and usage for a directory based on the quota limits set on that directory. To disable file system reporting based on directory tree quota limits, use the ibrix_mount –o noquotstatfs option when you mount the file. Fixes Corrected in 5.6.
• During a mkdir operation, the xdr_encode_netobj dereferencing NULL xdr_netobj->data pointer message was displayed. The underlying issue has been resolved so the message no longer appears. • The root file system was constantly running out of space. This release provides the option, -l, for placing log files in an alternative location for the ibrix_fsck -p 1 and ibrix_fsck -p 2 commands. Use the -l option to prevent the root file system from running out of space.
Corrected in 5.6.1 The following fixes were made in this release: File systems • The ibrix_fsck command needed an option to focus consistency checking on specific segments. • A modification to the lost+found directory could cause corruption, with the error ext3_dx_find_entry: bad entry in directory. • A race condition caused an error when ibrix_fsck checked the lost+found directory. • Running ibrix_fsck in phase 2 caused the file system to be read-only for X9000 clients.
The parameters are: ◦ TcpKeepaliveIdle: specifies how long the keepalive routines wait before sending the first keepalive probe. ◦ TcpKeepaliveIntvl: When the keepalive time is reached, specifies how often to resend a probe. ◦ TcpKeepaliveCnt: Specifies the number of probes to send with no ACK response received before marking the connection as broken.
Configuring HP Insight Remote Support Prerequisites The required components for supporting X9000 systems are preinstalled on the file serving nodes. You will need to install HP Insight Remote Support on a separate Windows system. The CMS has two versions: • Insight Remote Support Standard (IRSS). This version provides basic remote monitoring, notification/advisories and service dispatch. • Insight Remote Support Advanced (IRSA).
Configure SNMP on the file serving nodes Run the /sbin/hpsnmpconfig script, which configures SNMP to integrate the CMS/IRSS running on the Windows server with the HP System Management Homepage on the file serving node. The script edits the /etc/snmp/snmpd.conf file, adding entries similar to the following: # Following entries were added by HP Insight Management Agents at #
Discover nodes on HP SIM or IRSS For X9000 systems, HP Systems Insight Manager (SIM) uses the SNMP protocol to discover and identify systems automatically. If desired, you can configure HP SIM to discover system-specific network segments, a targeted host, or IP address ranges. For IRSS, see the HP Insight Remote Support Standard A.05.50 Hosting Device Configuration Guide for more information. (Use the link in the “Prerequisites” section to locate this guide.) For HP SIM, see the HP System Insight Manager 6.
Guide This document is available at http://www.hp.com/support/manuals. On the Manuals page, select storage >Disk Storage Systems > MSA Disk Arrays >HP S 2000sa G2 Modular Smart Array or HP P2000 G3 MSA Array Systems.) Refer to the HP StorageWorks 2xxx Modular Smart Array Reference Guide for other MSA versions. A Modular Storage Array (MSA) unit should be discovered with its IP address.
• When continuous remote replication is used and File Serving Nodes are configured for High Availability, you will need to take the following steps following failure of a node: 1. Stop continuous remote replication. 2. 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.
4. Start Likewise: /etc/init.d/lwsmd start && /opt/likewise/bin/lwsm start srvsvc 5. Restart the management console: /etc/init.d/ibrix_fusionmanager restart The management console will now recognize the Active Directory users and groups, and you can assign quotas to them. • For configurations with two management consoles, if the node hosting the active management console goes down, it is important to reboot it as soon as possible.
DOMAIN\username or a MACHINE\username. On X9000 systems, local users are displayed as LOCAL\username, and it may seem like you should specify LOCAL\username in the Add dialog box in Windows. However, in this case, the Windows client cannot interpret LOCAL. Instead, specify the machine name of the server. For example, to add LOCAL\user1 to an ACL on a CIFS file shared out by serverX, specify serverX\user1 in the Add dialog box on the security tab.
Migration to an agile management console configuration When a cluster is configured with a dedicated, standard management console, the Quick Restore installation procedure installs both the Fusion Manager and the File Serving Node packages on the dedicated, standard management console and on each node of the cluster. If you then attempt to migrate to an agile management console configuration, the migration procedure will fail.
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.
• When installing IRSA A.05.50 or IRSS A.05.50 on Windows Server 2008, install it to a non-default location (not under Program Files). • Onboard Administrator is discovered as unknown on IRSS. After Onboard Administrator discovery, manually enter the following details: ◦ Select System Subtype as ProLiant Onboard Administrator. ◦ Enter the Entitlement serial number (this is same as the X9000 enclosure product number).
• 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.
Installing a minor kernel update on Linux clients The X9000 client software is upgraded automatically when you install a compatible Linux minor kernel update. If you are planning to install a minor kernel update, first run the following command to verify that the update is compatible with the X9000 client software: /usr/local/ibrix/bin/verify_client_update The following example is for a RHEL 4.8 client with kernel version 2.6.9-89.ELsmp: # /usr/local/ibrix/bin/verify_client_update 2.
segments in the file system and is transparent to users or applications accessing the file system. When evacuating a segment, you should be aware of the following restrictions: • Segment evacuation uses the file system rebalance operation. While the rebalance task is running, the system will prevents tasks from running on the same file system. Similarly, if another task is running on the file system, the rebalance task cannot be scheduled until the first task is complete.
Installation instructions New installations HP X9000 File Serving Software is preinstalled on supported devices. If you need to reinstall the software, see the administration guide for your storage system. Upgrades The upgrade procedure is provided in the administration guide for your storage system. Contact HP Support for assistance with the procedure. IMPORTANT: If you are upgrading to the 5.6.1 release from an X9000 Software version earlier than 5.5, first upgrade to the latest 5.
