HP IBRIX X9000 Installation Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Network Hardware
  5. IBRIX X9000
  6. Installation manual

HP IBRIX X9000 Installation Manual

Network storage system
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
HP IBRIX X9000 Network Storage System

Installation Guide

Abstract
This document describes how to install the X9000 File Serving Software. It is intended for HP Services personnel who configure
X9000 series Network Storage systems at customer sites. For upgrade information, see the administration guide for your system.
For the latest X9000 guides, browse to http://www.hp.com/support/manuals. In the storage section, select NAS Systems and
then select HP X9000 Network Storage Systems from the IBRIX Storage Systems section.
HP Part Number: TA768-96058
Published: June 2012
Edition: 9

Advertisement

Table of Contents
loading

Related Manuals for HP IBRIX X9000

Summary of Contents for HP IBRIX X9000

  • Page 1: Installation Guide

    Installation Guide Abstract This document describes how to install the X9000 File Serving Software. It is intended for HP Services personnel who configure X9000 series Network Storage systems at customer sites. For upgrade information, see the administration guide for your system.
  • Page 2 The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    Contents 1 Installing X9300 and X9320 systems.............6 Network information.........................6 Installation checklist........................6 Installing the latest IBRIX X9000 software release................7 Starting the installation and configuration..................8 Completing the installation in text mode — unified network............11 Installing additional servers without the template..............14 Installing additional servers using the template...............17 Completing the installation in text mode —...
  • Page 4 Uninstalling Linux X9000 clients...................94 Uninstalling Windows X9000 clients..................95 7 Completing the X9730 Performance Module installation........96 Prerequisites...........................96 Installing the latest IBRIX X9000 software release................96 Installing the first expansion blade....................97 Installing the second expansion blade..................102 Using the new storage......................106 8 Expanding an X9720 or X9320 10GbE cluster by an X9730 module....109 Prerequisites.........................109...
  • Page 5 Troubleshooting the InfiniBand network..................145 Enabling client access......................146 Setting up Voltaire InfiniBand ....................146 12 Support and other resources..............148 Contacting HP........................148 Related information.......................148 HP websites.........................148 13 Documentation feedback...............149 Glossary....................150 Contents...

  • Page 6: Installing X9300 And X9320 Systems

    This procedure is described in detail later in this chapter. See the HP IBRIX X9000 Network Storage System Network Best Practices Guide for a detailed description of the unified network on X9300/X9320 systems, including the physical layout of the network.

  • Page 7: Installing The Latest Ibrix X9000 Software Release

    (page 83) Installing the latest IBRIX X9000 software release Obtain the latest 6.1 release from the IBRIX X9000 software dropbox. Download the Quick Restore ISO image and then use either a DVD or a USB key to install the image.

  • Page 8: Starting The Installation And Configuration

    Restart the server to boot from the USB key. (Press F1 1 and use option 3 ). When the “HP Network Storage System” screen appears, enter qr to install the software. Repeat steps 5–8 on each server and then go to the next section, “Starting the installation and configuration.”...
  • Page 9 VLAN capabilities provide hardware support for running multiple logical networks over the same physical networking hardware. IBRIX supports the ability to associate a VLAN tag with a FSN interface. For more information, see the HP IBRIX X9000 Network Storage System Network Best Practices Guide.
  • Page 10 Select a method to complete the installation: Web UI over the network from a remote system. The URL for the IBRIX Getting Started Wizard is displayed on the console when you select this option. A local Web UI session on this console. Selecting this option launches the IBRIX Getting Started Wizard from a web browser on this console.

  • Page 11: Completing The Installation In Text Mode - Unified Network

    Completing the installation in text mode — unified network To configure the first server, complete the following steps: On the Form a Cluster — Step 2 dialog box, enter a name for the cluster and specify the IP address and netmask for the Management Console IP (also called the Cluster Management IP).
  • Page 12 The Configuration Summary lists the configuration you have specified. Select Commit to continue. The wizard now configures the active management console (Fusion Manager) on the server. Installing X9300 and X9320 systems...
  • Page 13 Optionally, create a template to configure the remaining nodes. To use the template, all nodes must have identical network configurations. If you are using separate cluster/user networks, or the node configurations will not be identical, select Exit. In the hostname templates, the parameters enclosed in braces ({...}) expand in the following manner: number num: The number of file serving nodes in the cluster.

  • Page 14: Installing Additional Servers Without The Template

    A configuration script now performs some tuning and imports the LUNs into the X9000 software. When the script is complete, you can install the remaining servers. If you did not create a template, go to the next section. If you created a template, go to “Installing additional servers using the template”...
  • Page 15 The Verify Configuration dialog box shows the configuration for the server. Select Commit to continue. On the Form a Cluster — Step 2 dialog box, enter the cluster name and specify the IP address and netmask for the Management Console IP (also called the Cluster Management IP). Also enter the IP addresses and domain for your DNS servers, and the IP addresses for your NTP servers.
  • Page 16 The Configuration Summary dialog box lists the configuration you specified. Select Commit to apply the configuration. The wizard registers a passive Fusion Manager on the server, and then configures and starts The installation is complete. Installing X9300 and X9320 systems...

  • Page 17: Installing Additional Servers Using The Template

    Installing additional servers using the template Complete the following steps: Using a console connection, log into the server you are installing. The Set IP or Discover FMs dialog box appears. Select Discover Existing Clusters to join them from this console. The installation wizard scans the network for existing clusters and lists the clusters on the Join Cluster dialog box.
  • Page 18 The Verify Configuration dialog box shows the configuration for the server. If the configuration is correct, select Accept and go to step 4. NOTE: To change the configuration, select Reject, and the following screen appears. Choose Select FM Again to reselect the Fusion Manager and use the template again. To configure the server manually, select Enter FM IP and use the procedure corresponding to your network type.

  • Page 19: Completing The Installation In Text Mode - Separate Cluster And User Networks

    The wizard registers a passive Fusion Manager on the server, and then configures and starts The installation is complete. Completing the installation in text mode — separate cluster and user networks To configure the first server, complete the following steps: On the Form a Cluster —...
  • Page 20 On the Edit Bonded Interface dialog box, enter the IP address and netmask and specify any bond options. The slaves are selected by the system based on the following preference: 10G dual port PCI add-on card 1G quad port PCI add-on card Embedded server network ports Change the slave devices as necessary for your configuration.
  • Page 21 On the Select Interface Type dialog box, select Ok to create a bonded interface. On the Add Bonded Interface dialog box, enter bond1 as the name for the interface. Also specify the appropriate options and slave devices. Use mode 6 bonding for a 1GbE network, and mode 1 bonding for a 10GbE network.
  • Page 22 When you select Ok, the Configure Network dialog box reappears. Select bond1, and then select Configure. The Edit Bonded Interface dialog box is displayed. Enter the IP address and netmask for bond1 and select Ok. The Configuration Summary lists the configuration you have specified. Select Commit to continue.

  • Page 23: Installing Additional Servers

    A configuration script now performs some tuning and imports the LUNs into the X9000 software. If the bond0/cluster network is not routed and the bond1/user network is routed, complete the following steps to define the default gateway for bond1: Set the default gateway in /etc/sysconfig/network. Add a default route for bond1: ibrix_nic -r -n IFNAME -h HOSTNAME -A -R ROUTE For example:...
  • Page 24 The installation wizard scans the network for existing clusters and lists the clusters on the Join Cluster dialog box. Select the appropriate cluster. The Verify Hostname dialog box lists a hostname generated from the management console. Accept or change this hostname. Installing X9300 and X9320 systems...
  • Page 25 The Verify Configuration dialog box shows the configuration for the server. Because you need to change the configuration, select Reject, and the following screen appears. Select Enter FM IP. On the System Date and Time dialog box, enter the system date (day/month/year) and time (24-hour format).
  • Page 26 VLAN capabilities provide hardware support for running multiple logical networks over the same physical networking hardware. IBRIX supports the ability to associate a VLAN tag with a FSN interface. For more information, see the HP IBRIX X9000 Network Storage System Network Best Practices Guide.
  • Page 27 On the Join a Cluster – Step 2 dialog box, enter the requested information. NOTE: Register IP is the Fusion Manager (management console) IP, not the IP you are registering for this server. 10. The Network Configuration dialog box lists the Ethernet devices in bond0. If the devices are correct, go to the next step.
  • Page 28 On the Edit Bonded Interface dialog box, enter the IP address and netmask, specify any bond options, and change the slave devices as necessary for your configuration. When you select Ok, the Configuration Summary dialog box appears. Select Back and return to the Network Configuration dialog box.
  • Page 29 On the Select Interface Type dialog box, select Ok to create a bonded interface. On the Add Bonded Interface dialog box, enter bond1 as the name for the interface. Also specify the appropriate options and slave devices. Use mode 6 bonding for a 1GbE network, and mode 1 bonding for a 10GbE network.
  • Page 30 When you select Ok, the Configure Network dialog box reappears. Select bond1, and then select Configure. The Edit Bonded Interface dialog box is displayed. Enter the IP address and netmask for bond1, specify any bond options, and change the slave devices if necessary. 12.

  • Page 31: Configuring The Cluster With The Getting Started Wizard (X9300/X9320 Systems)

    2 Configuring the cluster with the Getting Started Wizard (X9300/X9320 systems) The Getting Started Wizard configures the cluster in a few steps. Be sure to have the necessary IP addresses available. NOTE: This wizard can be used only for X9300 and X9320 systems. Running the wizard The Cluster Settings page asks for information to identify your cluster.
  • Page 32 To update your license keys, click Update. Typically, you will need a license key for each server. Download your licenses from the HP website and place them in a location that can be accessed by this server. Use Browse to locate a license key and then click Add. Repeat this step for each license key.
  • Page 33 The wizard attempts to access the addresses that you specify. If it cannot reach an address, a message such as Primary DNS Server Unreachable will be displayed on the screen. The File Servers page lists all servers the wizard found on your network. If the list includes servers that do not belong in the cluster, select those servers and click Remove.
  • Page 34 IP addresses in the range. HP recommends that you create a single file system using all of the available storage. You can create this file system on the Create a Default File System page. You can also create NFS and CIFS shares on the file system.
  • Page 35 CIFS share, you will need to configure the file serving nodes for CIFS and configure authentication. You might also want to set certain CIFS parameters such as user permissions. Other configuration options are also available for NFS shares. See the HP IBRIX X9000 Network Storage System File System User Guide for more information.

  • Page 36: Troubleshooting The Getting Started Wizard

    When you click Finish to exit the wizard, the Fusion Manager is restarted. When the service is running again, you can log into the GUI. Troubleshooting the Getting Started Wizard If you are unable to resolve an issue, contact HP support for assistance. Cluster Settings page The cluster name cannot be set Probable cause: The command failed because of a timeout or other condition.

  • Page 37: Dns/Ftp Page

    Troubleshooting steps: Relaunch the wizard, go to the Cluster Settings page, and click Next to retry the operation. If the operation fails again, run ifconfig bond0:0. If the output is empty, use the following command to set the VIF on the server: ibrix_fm -c <VIF IP address>...

  • Page 38: File Servers Page

    The network is behaving inconsistently, causing a timeout. Troubleshooting steps: Check the system type. Run the following command on the servers you expected to discover: /opt/hp/platform/bin/hpsp_srvid If the system type is X9720, the servers will not be displayed. The installation does not support X9720 systems.
  • Page 39 displayed. This situation could be caused by network inconsistencies or an outage. Usually a network outage lasts only a few minutes. Try relaunching the wizard and revisiting this page. If the operation continues to fail, use the text-based installation method to form the cluster. Server registration fails with “Error: Registering server”...
  • Page 40 network details such as the IP address and hostname, relaunch the wizard, and try to set the HA pair again. If the operation still fails, use the following command to set the HA pair: ibrix_server -b -h SERVERNAME1,SERVERNAME2 Network inconsistencies or an outage could cause the wizard to fail. Usually a network outage lasts only a few minutes.
  • Page 41 /usr/local/ibrix/autocfg/bin/create_bonds -d 0 <Bond Mode> bond0 <eth port(s)> Restart the discovery application. To determine values for the bond mode and Ethernet ports, contact HP Support or your network administrator, or follow these steps: ◦ On X9730 systems, create the bond on internal NIC ports.

  • Page 42: Create A Default File System Page

    Use ethtool <eth port> to detect the speed information. The port value for X9300/X9320 systems is detected as described in the previous step. For X9730 systems, the ports are internal. ◦ If the speed of the NIC ports selected for bond creation is 10GB, use any two NIC ports in bond mode 1.
  • Page 43 QR the preformatted systems. An NFS/CIFS share cannot be created Probable cause: The server on which the file system is mounted is not available for share creation. The storage configuration is incorrect. Troubleshooting steps: Run the ibrix_fs l command to determine whether the file system was actually created. If the file system exists but is unmounted, use the GUI or the following command to mount the file system: ibrix_mount -f FSNAME [-o { RW | RO } ] [-O MOUNTOPTIONS] [-h HOSTLIST] -m MOUNTPOINT...

  • Page 44: Installing X9730 Systems

    NOTE: Use layout 2 when adding an X9730 system to an existing 2-network IBRIX cluster. See the HP IBRIX X9000 Network Storage System Network Best Practices Guide for detailed information about the network layouts. Table 1 Supported X9730 network layouts...

  • Page 45: Ip Address Requirements

    You will need the following IP addresses when you perform the installation for the unified network. The HP IBRIX X9000 Network Storage System Network Best Practices Guide describes the components in more detail, and also lists IP address requirements for the other supported network layouts.

  • Page 46: Installation Checklist

    Configure active and standby IP addresses for Onboard “Configuring OA1 IP addresses for Onboard Administrator Administrator” (page 46) Install the latest IBRIX X9000 software release “Installing the latest IBRIX X9000 software release” (page 48) Perform the installation “Starting the installation and configuring the chassis”...
  • Page 47 On the Network Settings: OA1 Active screen, select Network Properties and press OK. On the Change OA Network Properties screen, set Enclosure IP to Enable and press OK to Accept. On the Network Settings:OA1 Active screen, navigate to Active IPv4 and press OK. On the Change:OA1 Network Mode screen, change DHCP to Static and press OK to Accept.

  • Page 48: Installing The Latest Ibrix X9000 Software Release

    The Main Menu reappears and the procedure is complete. Installing the latest IBRIX X9000 software release Obtain the latest 6.1 release from the IBRIX X9000 software dropbox. Download the Quick Restore ISO image and transfer it to a DVD or USB key.

  • Page 49: Starting The Installation And Configuring The Chassis

    Insert the USB key into the server to be installed. Restart the server to boot from the USB key. (Press F1 1 and use option 3 ). When the “HP Network Storage System” screen appears, enter qr to install the software. Repeat steps 5–8 on each server.
  • Page 50 IMPORTANT: HP recommends that you update the firmware before continuing with the installation. X9730 systems have been tested with specific firmware recipes. Continuing the installation without upgrading to a supported firmware recipe can result in a defective system. The setup wizard checks the network for an existing cluster. If a cluster is found, you will be asked if you want to join an existing cluster or create a new cluster.
  • Page 51 VLAN capabilities provide hardware support for running multiple logical networks over the same physical networking hardware. IBRIX supports the ability to associate a VLAN tag with a FSN interface. For more information, see the HP IBRIX X9000 Network Storage System Network Best Practices Guide.
  • Page 52 The wizard now sets up the blade based on the information you entered. The setup wizard next configures the chassis on the X9730 system. See the HP IBRIX X9000 Network Storage System Network Best Practices Guide for detailed information about the chassis components.
  • Page 53 The wizard now validates the information you have entered. It performs the following tests: Pings the active OA. Verifies the OA password. Verifies that that OA at that IP address is the active OA. If any of these tests fail, verify the configuration of the OA and VC modules as described on the failure report displayed on the GUI.
  • Page 54 To configure the iLO IP addresses manually, enter each iLO IP address on the Enter iLO IP Addresses dialog box. 1 1. The wizard lists the IP addresses you specified on the Confirm iLO IP Addresses dialog box. Select Ok to continue. 12.
  • Page 55 To configure the Interconnect (IC) IP addresses in sequence, enter the first Interconnect (IC) IP address on the Set Interconnect IP Addresses dialog box. The installer then sets the remainder of the addresses sequentially for all 8 interconnect bays. For example, if 172.16.3.21 is the starting Interconnect (IC) IP Address, the installer sets the Interconnect (IC) IP Addresses in the range 172.16.3.21–172.16.3.28.
  • Page 56 14. Enter the DNS and NTP server information used by the Onboard Administrator. 15. The wizard now configures the OA. This process takes up to 45 minutes to complete. 16. Next, the wizard verifies the VC configuration and creates a new user called hpspAdmin. You may need to provide input for the following: The wizard attempts to log into the Virtual Connect manager using the Administrator password you supplied earlier.
  • Page 57 The wizard makes the following checks: Pings the VC management IP address. Verifies the hpspAdmin account created earlier. If a check fails, take the corrective actions described on the GUI. 18. The wizard now configures the remaining bays for the Virtual Connect modules in the chassis. 19.
  • Page 58 22. The wizard powers off blades 2–16, applies the SAS configuration, and then reboots blade 1. Log into blade 1 when the Linux login prompt appears. 23. The wizard takes the following actions: Verifies the SAS configuration to ensure that SAS zoning is set up correctly Powers on blades 2–16 Verifies storage firmware to ensure that is set up correctly Validates the LUN layout and configures it if necessary...

  • Page 59: Creating The Cluster On Blade 1

    25. The wizard is ready to create the cluster. Note the situations listed on the Proceed to Cluster Creation dialog box, and select Exit if they apply to you. Otherwise, select Proceed. Creating the cluster on blade 1 To create the cluster on blade 1, complete the following steps: On the Form a Cluster —...
  • Page 60 The Network Configuration dialog box lists the interfaces you configured earlier. If you are using the unified network layout, bond0 is already set up. Select Continue and go to step 3. If you are using a different network layout, the necessary bonds appear on the Network Configuration screen with the correct eth devices assigned, but you need to configure the IP addresses for those bonds.
  • Page 61 NOTE: Ensure that the Management IP is on the same subnet as the cluster network (bond0 for the unified network layout; bond1 for all other layouts). The wizard now configures the active management console (Fusion Manager) on this blade. Optionally, create a template to configure the remaining nodes. The template is useful only if all of the blades have identical network configurations, such as in the unified network.
  • Page 62 In the hostname templates, the parameters enclosed in braces ({...}) expand in the following manner: number num: The number of file serving nodes in the cluster. NOTE: When using the number format, allow each file serving node to register before logging in to the next system.

  • Page 63: Installing Additional X9730 Blades

    The wizard verifies the firmware on the system and notifies you if a firmware update is needed. IMPORTANT: HP recommends that you update the firmware before continuing with the installation. X9730 systems have been tested with specific firmware recipes. Continuing the installation without upgrading to a supported firmware recipe can result in a defective system.
  • Page 64 The wizard scans the network for existing clusters. On the Join Cluster dialog box, select the management console (Fusion Manager) for your cluster. You have several options at this point: Use the template to configure the blade. Select Ok, and go to “Configure the blade with the template”...
  • Page 65 The blade you are installing is assigned the appropriate name from the template, plus the last octet IP for a hostname. If necessary, you can change the hostname on the Verify Hostname dialog box. The Verify Configuration dialog box shows the configuration for this blade. If the configuration is correct, select Accept and go to step 3.
  • Page 66 The installer now obtains OA/VC information from the chassis. If the installer cannot obtain the information programmatically, the following screen will appear and you will need to enter the OA/VC credentials manually. The wizard now takes the following actions: Checks the OA and VC firmware and notifies you if an update is needed Verifies the VC configuration Creates the hpspAdmin user accounts on the iLOs Verifies the chassis configuration...
  • Page 67 The Network Configuration dialog box lists the interfaces configured on bond0. The configuration is complete. Select Continue. The Configuration Summary dialog box lists the configuration you specified. Select Commit to apply the configuration. Installing additional X9730 blades...
  • Page 68 NOTE: Ensure that the Management IP is on the same subnet as the cluster network (bond0). The wizard registers and starts a passive management console on the blade. The installation is complete. Configure the blade manually Complete the following steps: On the System Date and Time dialog box, enter the system date (day/month/year) and time (24-hour format).
  • Page 69 VLAN capabilities provide hardware support for running multiple logical networks over the same physical networking hardware. IBRIX supports the ability to associate a VLAN tag with a FSN interface. For more information, see the HP IBRIX X9000 Network Storage System Network Best Practices Guide.
  • Page 70 The wizard now takes the following actions: Checks the OA and VC firmware and notifies you if an update is needed Verifies the VC configuration Creates the hpspAdmin user accounts on the iLOs Verifies the chassis configuration Checks the firmware on the SAS switches and notifies you if an update is needed Verifies the SAS configuration Checks the storage firmware and notifies you if an update is needed Verifies the storage configuration...
  • Page 71 If you are using the unified network layout, bond0 is already set up. Select Continue and go to step 8. If you are using a different network layout, the necessary bonds appear on the Network Configuration screen with the correct eth devices assigned, but you need to configure the IP addresses for those bonds.

  • Page 72: Firmware Updates

    NOTE: Ensure that the Management IP is on the same subnet as the cluster network (bond0) for the unified network layout; bond1 for all other layouts). The wizard registers and starts a passive management console on the blade. The installation is complete. Firmware updates If a firmware check determines that firmware needs to be updated, you will see a dialog box such as the following.
  • Page 73 If the firmware check determines that firmware should be downgraded, you will see a dialog box such as the following. You cannot downgrade the firmware during the installation. Select Skip and then downgrade the firmware when the installation is complete. Chassis component firmware can be flashed only from blade 1.

  • Page 74: Troubleshooting

    Troubleshooting Install software cannot ping the OA This condition can occur if OA2 becomes the Active OA. Configure the OA as follows to resolve this condition: From the Main Menu of the Insight Display, navigate to Enclosure Settings and press OK. On the Enclosure Settings screen, select Active OA and press OK.
  • Page 75 On the Change OA Network Properties screen, set Enclosure IP to Enable and press OK to Accept. On the Network Settings: OA1 Active screen, select Accept All and press OK. On the Enclosure Settings screen, select Standby OA and press OK. On the Network Settings:OA2 screen, navigate to Active IPv4 and press OK.
  • Page 76 Credential Manager will fail. To initialize the Credential Manager from the command line, complete the appropriate procedure. OA and VC have the same username and password. Update the OA and VC with their credentials: /opt/hp/platform/bin/hpsp_credmgmt --init-cred --master-passwd=hpdefault --hw-username=<username> --hw-password=<password> Update the iLO with its credentials:...

  • Page 77: Post-Installation Tasks

    4 Post-installation tasks Updating license keys Typically you need a license key for each server. If you did not update your license keys during the installation, download the license keys and install them as described in the administrator guide for your system. Configuring and Enabling High Availability X9730 systems The installation process configures the servers for High Availability;...

  • Page 78: X9000 Software Manpages

    MANPATH=$MANPATH:/usr/local/ibrix/man Configuring data collection with Ibrix Collect Ibrix Collect is a log collection utility that gathers relevant information for diagnosis by HP Support. For information about configuring Ibrix Collect, see “Collecting information for HP Support with Ibrix Collect” in the administrator guide for your system.

  • Page 79: Configuring Cifs Shares (Optional)

    When setting up CIFS, you will need to configure user authentication and then create CIFS shares. For more information, see the following: “Configuring authentication for CIFS, FTP, and HTTP” and “Using CIFS” in the HP IBRIX X9000 Network Storage System File System User Guide...

  • Page 80: Configuring Virtual Interfaces For Client Access

    Fusion Manager configuration, a virtual interface is also created for the cluster network interface to provide failover support for the console. Although the cluster network interface can carry traffic between file serving nodes and clients, HP recommends that you configure one or more user network interfaces for this purpose.

  • Page 81: Configuring Nic Failover

    Add the VIF: # ibrix_nic a -n bond0:2 h node1,node2,node3,node4 Set up a standby server for each VIF: # ibrix_nic H node1/bond0:1,node2/bond0:2 # ibrix_nic H node2/bond0:1,node1/bond0:2 # ibrix_nic H node3/bond0:1,node4/bond0:2 # ibrix_nic H node4/bond0:1,node3/bond0:2 Configuring NIC failover NIC monitoring should be configured on VIFs that will be used by NFS, CIFS, FTP, or HTTP. IMPORTANT: When configuring NIC monitoring, use the same backup pairs that you used when configuring standby servers.

  • Page 82: Specifying Vifs In The Client Configuration

    Specifying VIFs in the client configuration When you configure your clients, you may need to specify the VIF that should be used for client access. NFS/CIFS. Specify the VIF IP address of the servers (for example, bond0:1) to establish connection. You can also configure DNS round robin to ensure NFS or CIFS client-to-server distribution.

  • Page 83: Adding Linux And Windows X9000 Clients

    6 Adding Linux and Windows X9000 clients Linux and Windows X9000 clients run applications that use the file system. The clients can read, write, and delete files by sending requests to File Serving Nodes. This chapter describes how to install, configure, and register the clients. Linux X9000 client Prerequisites for installing the Linux X9000 client Before installing the client software, do the following:...

  • Page 84: Registering Linux X9000 Clients

    To register a client using the CLI, use the following command: <installdirectory>/bin/ibrix_client -a -h HOST -e IPADDRESS For example, to register client12.hp.com, which is accessible at IP address 192.168.2.12: <installdirectory>/bin/ibrix_client -a -h client12.hp.com -e 192.168.2.12 Registering multicluster clients A multicluster client is one that is registered to more than one management console and is thus a member of more than one cluster.

  • Page 85: Removing An X9000 Client From The Cluster

    <installdirectory>/bin/ibrix_hostgroup -n -g HOSTGROUP -A DESTHOST/IFNAME The destination host (DESTHOST) cannot be a hostgroup. For example, to prefer network interface eth3 for traffic from all X9000 clients (the clients hostgroup) to file serving node s2.hp.com: <installdirectory>/bin/ibrix_hostgroup -n -g clients -A s2.hp.com/eth3...

  • Page 86: Windows X9000 Client Setup

    Windows X9000 client setup When setting up the Windows X9000 client, you will need to perform specific tasks on the Active Directory server, the management console, and the Windows X9000 client. Set up Services for UNIX 3.5 on the Active Directory global catalog server. To configure automatic user mapping, either specify your domain controllers, or allow mapping of local users.

  • Page 87: Configuring Static User Mapping

    After configuring automatic user mapping, register the Windows client, and start the service. See “Registering Windows X9000 clients and starting services” (page 88). Configuring static user mapping This section describes how to configure static user mapping. Configuring groups and users on the Active Directory server You must configure an administrative user and group, a proxy user, the “unknown”...

  • Page 88: Configuring Active Directory Settings On The Management Console

    Windows client. NOTE: You might encounter problems with client access due to firewall settings. HP recommends that you turn off the firewall during testing. When you turn the firewall back on, open ports 1234 and 9000 through 9010 in both directions for X9000 software use.
  • Page 89 Launch the Windows X9000 client GUI and navigate to the Registration tab. Select the client’s IP address from the list. Enter the management console name in the FM Host Name field. Select Recover Registration to avoid having to re-register this client if you reinstall it. This option automatically retrieves the client’s ID from the management console.

  • Page 90: Importing Uids/Gids To The Active Directory Server

    Starting the X9000 client service automatically The X9000 client service, FusionClient, starts manually by default. When the client is functioning to your satisfaction, change the client service to start automatically when the machine is booted. On the client machine, select Settings > Control Panel > Administrative Tools > Services. In the services list, scroll to FusionClient, right-click, and select Properties.

  • Page 91: Preferring A User Network Interface For A Windows Client

    Tune Host. Tunable parameters include the NIC to prefer (the client uses the cluster interface by default unless a different network interface is preferred for it), the communications protocol (UDP or TCP), and the number of server threads to use. Active Directory Settings.
  • Page 92 ACEs can be explicit or inherited. An explicit ACE is assigned directly to the object by the owner or an administrator, while an inherited ACE is inherited from the parent directory. ACEs are governed by the following precedence rules: An explicit deny ACE overrides an explicit allow ACE, and an inherited deny ACE overrides an inherited allow ACE.
  • Page 93 read-write-execute permissions, the corresponding permission in the file mode mask for others is set to read-only. The write-execute permissions of the inherited ACE are ignored in the mapping. When an explicit deny ACE is added to a file’s ACL, the corresponding allow permissions are removed for group and others in the file mode mask, and the corresponding special explicit ACEs are updated accordingly.

  • Page 94: Uninstalling X9000 Clients

    The Permissions Entry window has three permissions that are important to X9000 software: Read Data, Write Data, and Execute File. These map directly to Read, Write, and Execute in the Linux mode mask, as shown in the following table. Linux permission Windows permission Read Read Data...

  • Page 95: Uninstalling Windows X9000 Clients

    Uninstalling Windows X9000 clients NOTE: It is not necessary to unmount the file system before uninstalling the Windows X9000 client software. To uninstall a client, complete the following steps: On the active management console, delete the Windows X9000 clients from the configuration database: <installdirectory>/bin/ibrix_client -d -h <CLIENTLIST>...

  • Page 96: Completing The X9730 Performance Module Installation

    HP IBRIX X9730 Network Storage System Performance Module Installation Instructions. The latest IBRIX X9000 release must be installed on each blade, as described in the next section. Installing the latest IBRIX X9000 software release Obtain the latest 6.1 release from the IBRIX X9000 software dropbox.

  • Page 97: Installing The First Expansion Blade

    Installing the first expansion blade The examples in this procedure show the installation of the first performance module, adding new blades to an existing X9730 cluster with two blades. Additional performance modules are installed in the same manner. The following screen shows the cluster before the expansion blades are added. To install the first blade in the expansion module, complete these steps: Log into the blade in the first expansion slot.
  • Page 98 IMPORTANT: HP recommends that you update the firmware before continuing with the installation. X9730 systems have been tested with specific firmware recipes. Continuing the installation without upgrading to a supported firmware recipe can result in a defective system. The setup wizard checks the network for an existing active Management Console. When the Set IP or Discover FMs dialog box appears, select Discover Existing Clusters to join them from this console.
  • Page 99 The Verify Hostname dialog box displays a hostname generated by the management console. If the hostname is incorrect, enter the correct hostname.. The Verify Configuration dialog box shows the configuration of the blade. If you changed the hostname in the previous step, select Reject because the IP address is incorrect. If all of the information on the Verify Configuration dialog box is correct, select Accept and go to the next step.
  • Page 100 Enter the information for the blade on the Server Setup dialog box. Review the information on the Configuration Summary that appears next, and select Commit. The wizard now verifies the VC firmware and then sets up the hpspAdmin user account. The wizard verifies the SAS configuration.
  • Page 101 10. The wizard verifies the SAS configuration. All blades should be powered on during this step. A warning appears if a controller cannot be accessed. Power up the blades and retry the operation. 1 1. The wizard validates the storage RAID/volume layout. 12.

  • Page 102: Installing The Second Expansion Blade

    15. The blade is now registered with the active management console and a passive management console is installed and registered on the blade. 16. The GUI now shows the blade has been added to the cluster. Installing the second expansion blade The installation procedure is similar to the first node, except the firmware, chassis, SAS, and storage checks are already in place.
  • Page 103 IMPORTANT: HP recommends that you update the firmware before continuing with the installation. X9730 systems have been tested with specific firmware recipes. Continuing the installation without upgrading to a supported firmware recipe can result in a defective system. The setup wizard checks the network for an existing active Management Console. When the Set IP or Discover FMs dialog box appears, select Discover Existing Clusters to join them from this console.
  • Page 104 The Verify Hostname dialog box displays a hostname generated by the management console. If the hostname is incorrect, enter the correct hostname. The Verify Configuration dialog box shows the configuration of the blade. If you changed the hostname in the previous step, select Reject because the IP address is incorrect. If all of the information on the Verify Configuration dialog box is correct, select Accept and go to the next step.
  • Page 105 The wizard now sets up the blade. The wizard performs several checks: Verifies the VC firmware Validates the chassis configuration Verifies VC authentication Sets up the hpspAdmin iLO user account Verifies SAS firmware Verifies SAS configuration Validates the storage RAID LUN configuration When the Join a Cluster —...

  • Page 106: Using The New Storage

    1 1. The Configuration Summary dialog box lists the configuration of the blade. If the information is correct, select Commit. 12. The blade is now registered with the active management console and a passive management console is installed and registered on the blade. 13.
  • Page 107 Verify vendor storage Run the Linux pvscan command on the expansion blades to verify that the operating system can see the factory-provisioned preformatted segments (physical volumes): [root@ib121-121 ~]# pvscan PV /dev/sdh VG vg7a32272126c746bfb7829a688c61e5b8 lvm2 [5.46 TB / 0 free] PV /dev/sdg VG vg22d0827592e34a6b9cda1daa746ca4ba lvm2 [5.46 TB / 0 free]...
  • Page 108 To see the LUNs associated with the physical volumes, select Vendor Storage from the Navigator and select the new storage expansion module from the Vendor Storage Panel. In the lower Navigator, expand the Summary completely and select LUN. Expand an existing file system To add any or all of the new physical volumes to an existing file system, complete these steps: Create a mountpoint for the file system on the new blades: ]# ibrix_mountpoint -c -h ib121-123,ib121-124 -m /ibfs1...

  • Page 109: Expanding An X9720 Or X9320 10Gbe Cluster By An X9730 Module

    Installing the latest IBRIX X9000 software release Obtain the latest 6.1 release from the IBRIX X9000 software dropbox and install it on each expansion blade. Download the Quick Restore ISO image and transfer it to a DVD or USB key.

  • Page 110: Installing The First Expansion Blade

    Restart the blade to boot from the DVD-ROM. When the HP Network Storage System screen appears, enter qr to install the software. Repeat steps 2–4 on each expansion blade. Use a USB key Copy the ISO to a Linux system.
  • Page 111 IMPORTANT: HP recommends that you update the firmware before continuing with the installation. X9730 systems have been tested with specific firmware recipes. Continuing the installation without upgrading to a supported firmware recipe can result in a defective system.
  • Page 112 The Verify Hostname dialog box displays a hostname generated by the management console. Enter the correct hostname and select Ok. The Verify Configuration dialog box shows the configuration of the blade. Select Reject; it is necessary to specify the setup information for the server. The following screen appears.
  • Page 113 VLAN capabilities provide hardware support for running multiple logical networks over the same physical networking hardware. IBRIX supports the ability to associate a VLAN tag with a FSN interface. For more information, see the HP IBRIX X9000 Network Storage System Network Best Practices Guide.
  • Page 114 Review the information on the Configuration Summary. If the information is correct, select Accept. The wizard now configures the blade. The network layout configured on the blade must match the layout used by the X9720or X9320 system. By default, the installation creates a single, unified network for all cluster and user traffic.
  • Page 115 When you press F2, the following screen appears. When you answer Yes to configure a dedicated management network, the Get Total Networks dialog box appears. Enter the number of networks used by the existing cluster (this will typically be 2). The Confirming Onboard Administrator and Virtual Connect Settings dialog box is displayed again, and the setup wizard configures the chassis on the X9730 system.
  • Page 116 The Active VC is by default the VC in interconnect bay 1. If the system is at factory defaults, the administrator passwords for OA and VC are on the labels affixed to the back of the chassis. If the passwords have been reset, enter the new passwords. The wizard now validates the information you have entered.
  • Page 117 sets the iLO IP addresses in the range 172.16.3.1 to 172.16.3.16 by incrementing 1 to the last octet of the IP address. To configure the iLO IP addresses manually, enter each iLO IP address on the Enter iLO IP Addresses dialog box. 12.
  • Page 118 To configure the Interconnect (IC) IP addresses in sequence, enter the first Interconnect (IC) IP address on the Set Interconnect IP Addresses dialog box. The installer then sets the remainder of the addresses sequentially for all 8 interconnect bays. For example, if 172.16.3.21 is the starting Interconnect (IC) IP Address, the installer sets the Interconnect (IC) IP Addresses in the range 172.16.3.21–172.16.3.28.
  • Page 119 15. Enter the DNS and NTP server information used by the Onboard Administrator. 16. The wizard now configures the OA. This process takes up to 45 minutes to complete. 17. Next, the wizard verifies the VC configuration and creates a new user called hpspAdmin. You may need to provide input for the following: The wizard attempts to log into the Virtual Connect manager using the Administrator password you supplied earlier.
  • Page 120 The wizard makes the following checks: Pings the VC management IP address. Verifies the hpspAdmin account created earlier. If a check fails, take the corrective actions described on the GUI. 19. The wizard now configures the remaining bays for the Virtual Connect modules in the chassis. 20.
  • Page 121 23. The wizard powers off blades 2–16, applies the SAS configuration, and then reboots blade 1. Log into blade 1 when the Linux login prompt appears. 24. The wizard takes the following actions: Verifies the SAS configuration to ensure that SAS zoning is set up correctly Powers on blades 2–16 Verifies storage firmware to ensure that is set up correctly Validates the LUN layout and configures it if necessary...
  • Page 122 27. The Network Configuration dialog box lists the interfaces you configured earlier. The correct eth devices should be assigned, but you need to configure the IP addresses for the bonds. Select a bond and then select Configure. On the Edit Bonded Interface dialog box, enter the IP address and netmask and specify any bond options.

  • Page 123: Installing The Second Expansion Blade

    28. The Configuration Summary dialog box lists the configuration of the blade. If the information is correct, select Commit. 29. The blade is now registered with the active management console and a passive management console is installed and registered on the blade. Installing the second expansion blade The installation procedure is similar to the first node, except the firmware, chassis, SAS, and storage checks are already in place.
  • Page 124 IMPORTANT: HP recommends that you update the firmware before continuing with the installation. X9730 systems have been tested with specific firmware recipes. Continuing the installation without upgrading to a supported firmware recipe can result in a defective system. The setup wizard checks the network for an existing active Management Console. When the Set IP or Discover FMs dialog box appears, select Discover Existing Clusters to join them from this console.
  • Page 125 The Verify Hostname dialog box displays a hostname generated by the management console. Select Ok. You will enter the correct hostname later in this procedure. The Verify Configuration dialog box shows the configuration of the blade. Select Reject, as it is necessary to customize the configuration.
  • Page 126 Review the information on the Configuration Summary that appears next, and select Commit. The wizard now sets up the blade. The wizard performs several checks: Verifies the VC firmware Validates the chassis configuration Verifies VC authentication Sets up the hpspAdmin iLO user account Verifies SAS firmware Verifies SAS configuration Validates the storage RAID LUN configuration...
  • Page 127 If the blade check fails, select Enter Manually and enter the information on the following dialog box. When the Join a Cluster — Step 2 dialog box appears, enter the requested information. NOTE: Register IP is the Fusion Manager (management console) IP, not the IP you are registering for this server.
  • Page 128 On the Edit Bonded Interface dialog box, enter the IP address and netmask and specify any bond options. 1 1. The Configuration Summary dialog box lists the configuration of the blade. If the information is correct, select Commit. 128 Expanding an X9720 or X9320 10GbE cluster by an X9730 module...

  • Page 129: Using The New Storage

    12. The blade is now registered with the active management console and a passive management console is installed and registered on the blade. Using the new storage To make the new storage available to the cluster, take these steps: Verify the vendor storage Import the new physical volumes into the IBRIX database Extend an existing file system to include the new physical volumes or create a new file system Verify vendor storage...
  • Page 130 The Storage panel now lists the original physical volumes and the newly discovered physical volumes. To discover the physical volumes from the CLI, run the following command on the active Fusion Manager, specifying just the new blades with the -h option: ibrix_pv -a -h ib121-123,ib121-124 To see the LUNs associated with the physical volumes, select Vendor Storage from the Navigator and select the new storage expansion module from the Vendor Storage Panel.
  • Page 131 Expand an existing file system To add any or all of the new physical volumes to an existing file system, complete these steps: Create a mountpoint for the file system on the new blades: ]# ibrix_mountpoint -c -h ib121-123,ib121-124 -m /ibfs1 Mount the file system on the blades: # ibrix_mount -f ibfs1 h ib121-123,ib121-124 -m /ibfs1...

  • Page 132: Expanding An X9320 Cluster With An X9320 Starter Kit

    9 Expanding an X9320 cluster with an X9320 starter kit The following prerequisites must be complete before adding the new couplet to the existing cluster: The X9320 starter kit must be cabled to the existing cluster as described in the HP IBRIX X9000 Networking Best Practices Guide.
  • Page 133 The wizard scans the network for active management consoles and lists them on the Join Cluster dialog box. Select the appropriate management console. If the wizard does not locate a cluster or you select Cancel, go to step 6. If you selected a cluster on the Join Cluster dialog box, the Verify Hostname dialog box displays a hostname generated by the management console.
  • Page 134 If you changed the hostname, select Reject, and the following screen appears. (The screen also appears if your cluster was not found in step 3.) Select Enter FM IP. The wizard asks for information about the server you are using. On the System Date and Time dialog box, enter the system date (day/month/year) and time (in 24-hour format).

  • Page 135: Completing The Installation With The Ewizard

    FSN interface. For more information, see the HP IBRIX X9000 Network Storage System Network Best Practices Guide. Review the information on the Configuration Summary that appears next, select Commit, and the wizard will set up the server.

  • Page 136: Completing The Installation In Text Mode

    Select the first new undefined server and click Configure. On the Configure File Server dialog box, enter the information for the server and click OK. The status of the server is now updated on the GUI. Configure the second new server in the same manner. When you click OK, the new server is updated on the GUI.
  • Page 137 On the Join a Cluster – Step 2 dialog box, enter the requested information. NOTE: Register IP is the Fusion Manager (management console) IP, not the IP you are registering for this server. The Network Configuration dialog box allows you to configure the network on this server to be compatible with the existing cluster: X9320 10GbE having bond0(eth4,5) as a combined cluster/user network, with the onboard LOM nic ports(eth0-3) used in the configuration of the management network for...
  • Page 138 On the Edit Bonded Interface dialog box, enter the IP address and netmask, specify any bond options, and change the slave devices as necessary. When you select Ok, the Configuration Summary dialog box appears. Select Back and return to the Network Configuration dialog box. Set up bond1 if necessary.
  • Page 139 On the Select Interface Type dialog box, select Ok to create a bonded interface. On the Add Bonded Interface dialog box, enter bond1 as the name for the interface. Also specify the appropriate options and slave devices. Use mode 6 bonding for a 1GbE network, and mode 1 bonding for a 10GbE network.
  • Page 140 When you select Ok, the Configure Network dialog box reappears. Select bond1, and then select Configure. The Edit Bonded Interface dialog box is displayed. Enter the IP address and netmask for bond1 and select Ok. The Configuration Summary lists the configuration you have specified. Select Commit to continue.

  • Page 141: 10 Using Ibrixinit

    10 Using ibrixinit The ibrixinit utility is used to install or uninstall the Fusion Manager, file serving node, and statstool packages on a file serving node. It can also be used to install or uninstall the X9000 client package on a Linux client. Synopsis Install the Fusion Manager, file serving node, and statstool packages on a file serving node: ./ibrixinit -C <CLUSTER_IF>...
  • Page 142 Option Description Specifies the Cluster virtual interface network mask for Fusion Manager -m <VIF_NETMASK> Installs or uninstalls the Linux X9000 client Uninstalls Fusion Manager, file serving node software, and statstool components, including the RPMs, on this file serving node Specifies the Cluster virtual interface IP address for Fusion Manager -v <VIF_IP>...

  • Page 143: 1 Setting Up Infiniband Couplets

    1 1 Setting up InfiniBand couplets InfiniBand is supported for X9300 and X9320 systems. The following logical network diagram shows an InfiniBand configuration. The following diagram shows network cabling for an InfiniBand configuration.

  • Page 144: Downloading And Installing The Infiniband Software

    Downloading and installing the InfiniBand software HP supports Mellanox OFED 1.5.3 for use with X9300/X9320 systems. To download the software, go to: http://h2031 1.www2.hp.com/hpc/us/en/infiniband-matrix.html Locate the HCA you have installed and click Firmware/Software. Select your version of Red Hat Enterprise Linux 5 Server, and then download the appropriate Mellanox InfiniBand Driver.

  • Page 145: Troubleshooting The Infiniband Network

    /lib/modules/2.6.18-194.el5/updates/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko /lib/modules/2.6.18-194.el5/updates/kernel/fs/exportfs/exportfs.ko Rename all of the above files to use the following suffix: /path/name.ofed. For example: mv /lib/modules/2.6.18-194.el5/updates/kernel/fs/nfs/nfs.ko /lib/modules/2.6.18-194.el5/updates/kernel/fs/nfs/nfs.ko.ofed Clean up the modules with the depmod -a command and reboot the nodes. A reboot is necessary for the changes to take effect. "depmod -a"...

  • Page 146: Enabling Client Access

    InfiniBand tests for end to end: On listener host, run ib_read_bw. On sender, run ib_read_bw <ip address>. You might need to specify a port number with -i. Run ibnetdiscover. This is a Voltaire tool that does a LID crawl. Troubleshoot switches: Run the Voltaire switch port_verify utility.
  • Page 147 [root@ib~]# tar -xf ufm-client-utils-2.0.0-28.tgz [root@ib ~]# cd ufm-client-utilst [root@ib ufm-client-utils]# ./install.sh Check dependencies ... Checking VoltaireOFED ..OK Checking version ... 1.4.2_2 Check the distribution ... Red Hat Proceed ufm-discover package /usr/src/redhat/SRPMS/ufm-discover-1.0.0-1.src.rpm ucceed to building ufm-discover package Preparing... ########################################### [100%] 1:ufm-discover ########################################### [100%] Proceed...

  • Page 148: 12 Support And Other Resources

    HP IBRIX X9300/X9320 Network Storage System Administrator Guide HP IBRIX X9720/X9730 Network Storage System Administrator Guide Related documents are available on the Manuals page at http://www.hp.com/support/manuals. On the Manuals page, select storage > NAS Systems > Ibrix Storage Systems > HP X9000 Network Storage Systems. HP websites For additional information, see the following HP websites: http://www.hp.com/go/X9000...

  • Page 149: 13 Documentation Feedback

    13 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). Include the document title and part number, version number, or the URL...

  • Page 150: Glossary

    Domain name system. File Transfer Protocol. Global service indicator. High availability. Host bus adapter. Host channel adapter. Hard disk drive. HP X9000 Software Administrative Daemon. Integrated Lights-Out. Initial microcode load. IOPS I/Os per second. IPMI Intelligent Platform Management Interface. JBOD Just a bunch of disks.
  • Page 151 Transmission Control Protocol/Internet Protocol. User Datagram Protocol. Unit identification. SNMP User Security Model. VACM SNMP View Access Control Model. HP Virtual Connect. Virtual interface. WINS Windows Internet Naming Service. World Wide Name. A unique identifier assigned to a Fibre Channel device. WWNN World wide node name.

Table of Contents