Page 1
This guide describes tasks related to cluster configuration and monitoring, system upgrade and recovery, hardware component replacement, and troubleshooting for the HP 9300 Storage Gateway and the HP 9320 Storage. It does not document IBRIX file system features or standard Linux administrative tools and commands. For information about configuring and using IBRIX...
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.
Configuring HP Insight Remote Support on IBRIX 9000 systems.............21 Configuring the IBRIX cluster for Insight Remote Support............22 Configuring Insight Remote Support for HP SIM 7.1 and IRS 5.7..........23 Configuring Insight Remote Support for HP SIM 6.3 and IRS 5.6..........26 Testing the Insight Remote Support configuration..............29 Updating the Phone Home configuration................29...
Page 4
Failing back a server ......................46 Setting up HBA monitoring....................46 Checking the High Availability configuration.................48 Capturing a core dump from a failed node................49 Prerequisites for setting up the crash capture................50 Setting up nodes for crash capture..................50 5 Configuring cluster event notification............52 Cluster events.........................52 Setting up email notification of cluster events................52 Associating events and email addresses................53...
Page 5
Health check reports......................77 Viewing logs..........................79 Viewing operating statistics for file serving nodes................80 9 Using the Statistics tool................81 Installing and configuring the Statistics tool................81 Installing the Statistics tool....................81 Enabling collection and synchronization................81 Upgrading the Statistics tool from IBRIX software 6.0..............82 Using the Historical Reports GUI....................82 Generating reports......................83 Deleting reports.........................84 Maintaining the Statistics tool....................84...
Page 6
Steps for upgrading the firmware....................126 Finding additional information on FMT................129 Downloading MSA2000 G2/G3 firmware for 9320 systems.............129 15 Troubleshooting..................130 Collecting information for HP Support with Ibrix Collect.............130 Collecting logs........................130 Downloading the archive file.....................131 Deleting the archive file....................131 Configuring Ibrix Collect....................132 Viewing data collection information..................133...
Page 7
Related information.......................145 HP websites........................146 Rack stability........................146 Product warranties........................146 Subscription service......................146 18 Documentation feedback...............147 A Cascading Upgrades................148 Upgrading the IBRIX software to the 6.1 release................148 Online upgrades for IBRIX software 6.x to 6.1..............148 Preparing for the upgrade....................148 Performing the upgrade....................149 After the upgrade......................149 Offline upgrades for IBRIX software 5.6.x or 6.0.x to 6.1............150...
Page 9
Class B equipment......................239 Taiwanese notices.........................240 BSMI Class A notice......................240 Taiwan battery recycle statement..................240 Turkish recycling notice......................240 Vietnamese Information Technology and Communications compliance marking......240 Laser compliance notices.......................240 English laser notice......................240 Dutch laser notice......................241 French laser notice......................241 German laser notice......................241 Italian laser notice......................242 Japanese laser notice.......................242 Spanish laser notice......................242 Recycling notices........................243...
It is important to keep regular backups of the cluster configuration. 9300 Storage Gateway The 9300 Storage Gateway is a flexible, scale-out solution that brings gateway file services to HP MSA, EVA, P4000, or 3rd-party arrays or SANs. The system provides the following features:...
IBRIX software is designed to operate with high-performance computing applications that require high I/O bandwidth, high IOPS throughput, and scalable configurations. Some of the key features and benefits are as follows: Scalable configuration. You can add servers to scale performance and add storage devices to scale capacity.
Follow these guidelines when using your system: Do not modify any parameters of the operating system or kernel, or update any part of the 9320 Storage unless instructed to do so by HP; otherwise, the system could fail to operate properly.
File allocation. Use this feature to specify the manner in which segments are selected for storing new files and directories. Data tiering. Use this feature to move files to specific tiers based on file attributes. For more information about these file system features, see the HP IBRIX 9000 Storage File System User Guide. Localization support Red Hat Enterprise Linux 5 uses the UTF-8 (8-bit Unicode Transformation Format) encoding for supported locales.
Configuration database consistency (ibrix_dbck) Shell task management (ibrix_shell) The following operations can be performed only from the GUI: Scheduling recurring data validation scans Scheduling recurring software snapshots Scheduling recurring block snapshots Scheduling recurring block snapshots Scheduling recurring block snapshots Using the GUI The GUI is a browser-based interface to the Fusion Manager.
Page 15
System Status The System Status section lists the number of cluster events that have occurred in the last 24 hours. There are three types of events: Alerts. Disruptive events that can result in loss of access to file system data. Examples are a segment that is unavailable or a server that cannot be accessed.
Page 16
Services Whether the specified file system services are currently running: One or more tasks are running. No tasks are running. Statistics Historical performance graphs for the following items: Network I/O (MB/s) Disk I/O (MB/s) CPU usage (%) Memory usage (%) On each graph, the X-axis represents time and the Y-axis represents performance.
NOTE: When you perform an operation on the GUI, a spinning finger is displayed until the operation is complete. However, if you use Windows Remote Desktop to access the GUI, the spinning finger is not displayed. Customizing the GUI For most tables in the GUI, you can specify the columns that you want to display and the sort order of each column.
9000 clients can access the Fusion Manager as follows: Linux clients. Use Linux client commands for tasks such as mounting or unmounting file systems and displaying statistics. See the HP IBRIX 9000 Storage CLI Reference Guide for details about these commands.
You will be prompted to enter the new password. Configuring ports for a firewall IMPORTANT: To avoid unintended consequences, HP recommends that you configure the firewall during scheduled maintenance times. When configuring a firewall, you should be aware of the following: SELinux should be disabled.
Port Description 9009/tcp 9200/tcp Between file serving nodes and NFS clients (user network) 2049/tcp, 2049/udp 1 1 1/tcp, 1 1 1/udp 875/tcp, 875/udp quota 32803/tcp lockmanager 32769/udp lockmanager 892/tcp, 892/udp mount daemon 662/tcp, 662/udp stat 2020/tcp, 2020/udp stat outgoing 4000:4003/tcp reserved for use by a custom application (CMU) and can be disabled if not used 137/udp Between file serving nodes and SMB clients (user network)
You must install HP Insight Remote Support on a separate Windows system termed the Central Management Server (CMS): HP Insight Manager (HP SIM). This software manages HP systems and is the easiest and least expensive way to maximize system uptime and health.
Limitations Note the following: For IBRIX systems, the HP Insight Remote Support implementation is limited to hardware events. Configuring the IBRIX cluster for Insight Remote Support To enable 9300/9320 systems for remote support, first register MSA disk arrays and then configure Phone Home settings.
-c -i 99.2.4.75 -P US -r public -w private -t Admin -n SYS01.US -o Colorado Next, configure Insight Remote Support for the version of HP SIM you are using: HP SIM 7.1 and IRS 5.7. See “Configuring Insight Remote Support for HP SIM 7.1 and IRS 5.7”...
Page 24
HP Systems Insight Manager (SIM) uses the SNMP protocol to discover and identify IBRIX systems automatically. On HP SIM, open Options > Discovery > New. Select Discover a group of systems, and then enter the discovery name and the Fusion Manager IP address on the New Discovery dialog box.
Page 25
HP 9320 NetStor FSN(ProLiant DL380 G7) HP 9320 NetStor FSN(ProLiant DL380 G6) HP 9300 NetStor FSN(ProLiant DL380 G7) HP 9300 NetStor FSN(ProLiant DL380 G6) The following example shows discovered devices on HP SIM 7.1. Configuring HP Insight Remote Support on IBRIX 9000 systems...
File serving nodes and MSA arrays are associated with the Fusion Manager IP address. In HP SIM, select Fusion Manager and open the Systems tab. Then select Associations to view the devices. You can view all IBRIX devices under Systems by Type > Storage System > Scalable Storage Solutions >...
Page 27
The following example shows discovered devices on HP SIM 6.3. File serving nodes are discovered as ProLiant server. Configuring device Entitlements Configure the CMS software to enable remote support for IBRIX systems. For more information, see "Using the Remote Support Setting Tab to Update Your Client and CMS Information” and “Adding Individual Managed Systems”...
Page 28
Go to Remote Support Configuration and Services and select the Entitlement tab. Check the devices discovered. NOTE: If the system discovered on HP SIM does not appear on the Entitlement tab, click Synchronize RSE. Select Entitle Checked from the Action List.
Troubleshooting Insight Remote Support Devices are not discovered on HP SIM Verify that cluster networks and devices can access the CMS. Devices will not be discovered properly if they cannot access the CMS. Configuring HP Insight Remote Support on IBRIX 9000 systems...
Page 30
Phone Home configuration” (page 29). Fusion Manager IP is discovered as “Unknown” Verify that the read community string entered in HP SIM matches the Phone Home read community string. Also run snmpwalk on the VIF IP and verify the information: # snmpwalk -v 1 -c <read community string>...
Fusion Manager, a virtual interface is created for the cluster network interface. 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.
To assign the IFNAME a default route for the parent cluster bond and the user VIFS assigned to FSNs for use with SMB/NFS, enter the following ibrix_nic command at the command prompt: # ibrix_nic -r -n IFNAME -h HOSTNAME-A -R <ROUTE_IP> Configure backup monitoring, as described in “Configuring backup servers”...
For example: # ibric_nic –m -h node1 -A node2/bond0:1 # ibric_nic –m -h node2 -A node1/bond0:1 # ibric_nic –m -h node3 -A node4/bond0:1 # ibric_nic –m -h node4 -A node3/bond0:1 Configuring automated failover To enable automated failover for your file serving nodes, execute the following command: ibrix_server —m [-h SERVERNAME] Example configuration This example uses two nodes, ib50-81 and ib50-82.
Create the user FM VIF: ibrix_fm -c 15.226.51.125 -d bond0.51:1 -n 255.255.255.0 -v user For more information about VLAG tagging, see the HP IBRIX Storage Network Best Practices Guide. Configuring link state monitoring for iSCSI network interfaces Do not configure link state monitoring for user network interfaces or VIFs that will be used for SMB or NFS.
Page 35
To determine whether link state monitoring is enabled on an iSCSI interface, run the following command: ibrix_nic -l Next, check the LINKMON column in the output. The value yes means that link state monitoring is enabled; no means that it is not enabled. Configuring link state monitoring for iSCSI network interfaces...
4 Configuring failover This chapter describes how to configure failover for agile management consoles, file serving nodes, network interfaces, and HBAs. Agile management consoles The agile Fusion Manager maintains the cluster configuration and provides graphical and command-line user interfaces for managing and monitoring the cluster. The agile Fusion Manager is installed on all file serving nodes when the cluster is installed.
console. This Fusion Manager rebuilds the cluster virtual interface, starts Fusion Manager services locally, transitions into active mode, and take over Fusion Manager operation. Failover of the active Fusion Manager affects the following features: User networks. The virtual interface used by clients will also fail over. Users may notice a brief reconnect while the newly active Fusion Manager takes over management of the virtual interface.
What happens during a failover The following actions occur when a server is failed over to its backup: The Fusion Manager verifies that the backup server is powered on and accessible. The Fusion Manager migrates ownership of the server’s segments to the backup and notifies all servers and 9000 clients about the migration.
Page 39
Use the NIC HA Setup dialog box to configure NICs that will be used for data services such as SMB or NFS. You can also designate NIC HA pairs on the server and its backup and enable monitoring of these NICs. Configuring High Availability on the cluster...
Page 40
For example, you can create a user VIF that clients will use to access an SMB share serviced by server ib69s1. The user VIF is based on an active physical network on that server. To do this, click Add NIC in the section of the dialog box for ib69s1. On the Add NIC dialog box, enter a NIC name.
Page 41
Next, enable NIC monitoring on the VIF. Select the new user NIC and click NIC HA. On the NIC HA Config dialog box, check Enable NIC Monitoring. In the Standby NIC field, select New Standby NIC to create the standby on backup server ib69s2. The standby you specify must be available and valid.
Page 42
You can create additional user VIFs and assign standby NICs as needed. For example, you might want to add a user VIF for another share on server ib69s2 and assign a standby NIC on server ib69s1. You can also specify a physical interface such eth4 and create a standby NIC on the backup server for it.
Changing the HA configuration To change the configuration of a NIC, select the server on the Servers panel, and then select NICs from the lower Navigator. Click Modify on the NICs panel. The General tab on the Modify NIC Properties dialog box allows you change the IP address and other NIC properties. The NIC HA tab allows you to enable or disable HA monitoring and failover on the NIC and to change or remove the standby NIC.
Page 44
–m -h node2 -A node1/bond0:1 ibric_nic –m -h node3 -A node4/bond0:1 ibric_nic –m -h node4 -A node3/bond0:1 The next example sets up server s2.hp.com to monitor server s1.hp.com over user network interface eth1: ibrix_nic -m -h s2.hp.com -A s1.hp.com/eth1 4.
-b -U HOSTNAME1/IFNAME1 For example, to delete the standby that was assigned to interface eth2 on file serving node s1.hp.com: ibrix_nic -b -U s1.hp.com/eth2 Turn off automated failover: ibrix_server -m -U [-h SERVERNAME] To specify a single file serving node, include the -h SERVERNAME option.
A failback might not succeed if the time period between the failover and the failback is too short, and the primary server has not fully recovered. HP recommends ensuring that both servers are up and running and then waiting 60 seconds before starting the failback. Use the ibrix_server -l command to verify that the primary server is up and running.
Page 47
HBA failure. Use the following command: ibrix_hba -m -h HOSTNAME -p PORT For example, to turn on HBA monitoring for port 20.00.12.34.56.78.9a.bc on node s1.hp.com: ibrix_hba -m -h s1.hp.com -p 20.00.12.34.56.78.9a.bc To turn off HBA monitoring for an HBA port, include the -U option:...
-b argument. To view results only for file serving nodes that failed a check, include the -f argument. ibrix_haconfig -l [-h HOSTLIST] [-f] [-b] For example, to view a summary report for file serving nodes xs01.hp.com and xs02.hp.com: Configuring failover...
The -v option produces detailed information about configuration checks that received a Passed result. For example, to view a detailed report for file serving node xs01.hp.com: ibrix_haconfig -i -h xs01.hp.com...
IMPORTANT: Complete the steps in “Prerequisites for setting up the crash capture” (page 50) before setting up the crash capture. Prerequisites for setting up the crash capture The following parameters must be configured in the ROM-based setup utility (RBSU) before a crash can be captured automatically on a file server node in failed condition.
Page 51
Tune Fusion Manager to set the DUMPING status timeout by entering the following command: ibrix_fm_tune -S -o dumpingStatusTimeout=240 This command is required to delay the failover until the crash kernel is loaded; otherwise, Fusion Manager will bring down the failed node. Capturing a core dump from a failed node...
5 Configuring cluster event notification Cluster events There are three categories for cluster events: Alerts. Disruptive events that can result in loss of access to file system data. Warnings. Potentially disruptive conditions where file system access is not lost, but if the situation is not addressed, it can escalate to an alert condition.
Be sure to specify valid email addresses, especially for the SMTP server. If an address is not valid, the SMTP server will reject the email. The following command configures email settings to use the mail.hp.com SMTP server and turns on notifications: ibrix_event -m on -s mail.hp.com -f FM@hp.com -r MIS@hp.com -t Cluster1 Notification...
Some SNMP parameters and the SNMP default port are the same, regardless of SNMP version. The default agent port is 161. SYSCONTACT, SYSNAME, and SYSLOCATION are optional MIB-II agent parameters that have no default values. NOTE: The default SNMP agent port was changed from 5061 to 161 in the IBRIX 6.1 release. This port number cannot be changed.
The subtree is added in the named view. For example, to add the 9000 software private MIB to the view named hp, enter: ibrix_snmpview -a -v hp -o .1.3.6.1.4.1.18997 -m .1.1.1.1.1.1.1 Configuring groups and users A group defines the access control policy on managed objects for one or more users. All users must belong to a group.
For example, to create the group group2 to require authorization, no encryption, and read access to the hp view, enter: ibrix_snmpgroup -c -g group2 -s authNoPriv -r hp The format to create a user and add that user to a group follows:...
Page 58
See the MSA array documentation for additional information. For HP P2000 G3 MSA systems, see the HP P2000 G3 MSA System SMU Reference Guide. For P2000 G2 MSA systems, see the HP 2000 G2 Modular Smart Array Reference Guide. To locate these documents, go to http:// www.hp.com/support/manuals.
6 Configuring system backups Backing up the Fusion Manager configuration The Fusion Manager configuration is automatically backed up whenever the cluster configuration changes. The backup occurs on the node hosting the active Fusion Manager. The backup file is stored at <ibrixhome>/tmp/fmbackup.zip on that node. The active Fusion Manager notifies the passive Fusion Manager when a new backup file is available.
hard quota limit for the directory tree has been exceeded, NDMP cannot create a temporary file and the restore operation fails. Configuring NDMP parameters on the cluster Certain NDMP parameters must be configured to enable communications between the DMA and the NDMP Servers in the cluster.
status of the session (backing up data, restoring data, or idle), the start time, and the IP address used by the DMA. To cancel a session, select that session and click Cancel Session. Canceling a session kills all spawned sessions processes and frees their resources if necessary. To see similar information for completed sessions, select NDMP Backup >...
To rescan for devices, use the following command: ibrix_tape –r NDMP events An NDMP Server can generate three types of events: INFO, WARN, and ALERT. These events are displayed on the GUI and can be viewed with the ibrix_event command. INFO events.
7 Creating host groups for 9000 clients A host group is a named set of 9000 clients. Host groups provide a convenient way to centrally manage clients. You can put different sets of clients into host groups and then perform the following operations on all members of the group: Create and delete mount points Mount file systems...
-m -g GROUP -h MEMBER For example, to add the specified host to the finance group: ibrix_hostgroup -m -g finance -h cl01.hp.com Adding a domain rule to a host group To configure automatic host group assignments, define a domain rule for host groups. A domain rule restricts host group membership to clients on a particular cluster subnet.
Additional host group operations are described in the following locations: Creating or deleting a mountpoint, and mounting or unmounting a file system (see “Creating and mounting file systems” in the HP IBRIX 9000 Storage File System User Guide) Changing host tuning parameters (see “Tuning file serving nodes and 9000 clients”...
8 Monitoring cluster operations This chapter describes how to monitor the operational state of the cluster and how to monitor cluster health. Monitoring 9300/9320 hardware The GUI displays status, firmware versions, and device information for the servers, virtual chassis, and system storage included in 9300 and 9320 systems. Monitoring servers To view information about the server and chassis included in your system.
Page 67
Select the server component that you want to view from the lower Navigator panel, such as NICs. Monitoring 9300/9320 hardware...
Page 68
The following are the top-level options provided for the server: NOTE: Information about the Hardware node can be found in “Monitoring hardware components” (page 70). HBAs. The HBAs panel displays the following information: ◦ Node WWN ◦ Port WWN ◦ Backup Monitoring cluster operations...
Page 69
◦ Monitoring ◦ State NICs. The NICs panel shows all NICs on the server, including offline NICs. The NICs panel displays the following information: ◦ Name ◦ ◦ Type ◦ State ◦ Route ◦ Standby Server ◦ Standby Interface Mountpoints. The Mountpoints panel displays the following information: ◦...
Events. The Events panel displays the following information: ◦ Level ◦ Time ◦ Event Hardware. The Hardware panel displays the following information: ◦ The name of the hardware component ◦ The information gathered in regards to that hardware component. “Monitoring hardware components” (page 70) for detailed information about the Hardware panel.
Page 71
Message Diagnostic Message Column dynamically appears depending on the situation. Obtain detailed information for hardware components in the server by clicking the nodes under the Server node. Monitoring 9300/9320 hardware...
Page 72
Table 1 Obtaining detailed information about a server Panel name Information provided Status Type Name UUID Model Location ILO Module Status Type Name UUID Serial Number Model Firmware Version Properties Memory DiMM Status Type Name UUID Location Properties Status Type Name UUID Properties...
Page 73
Table 1 Obtaining detailed information about a server (continued) Panel name Information provided Location Properties Storage Controller (Displayed for a server) Status Type Name UUID Serial Number Model Firmware Version Location Message Diagnostic message Volume: Displays volume information for each server. Status Type Name...
Monitoring storage and storage components Select Vendor Storage from the Navigator tree to display status and device information for storage and storage components. The Summary panel shows details for a selected vendor storage, as shown in the following image: The Management Console provides a wide-range of information in regards to vendor storage. Drill down into the following components in the lower Navigator tree to obtain additional details: Servers.
Managing LUNs in a storage cluster The LUNs panel provides information about the LUNs in a storage cluster. The following information is provided in the LUNs panel: LUN ID Physical Volume Name Physical Volume UUID In the following image, the LUNs panel displays the LUNs for a storage cluster. Monitoring the status of file serving nodes The dashboard on the GUI displays information about the operational status of file serving nodes, including CPU, I/O, and network performance information.
Events are written to an events table in the configuration database as they are generated. To maintain the size of the file, HP recommends that you periodically remove the oldest events. See “Removing events from the events database table” (page 77).
The ibrix_event -l and -i commands can include options that act as filters to return records associated with a specific file system, server, alert level, and start or end time. See the HP IBRIX 9000 Network Storage System CLI Reference Guide for more information.
Page 78
all tested file serving nodes are included when the overall result is determined. The results will be one of the following: Passed. All tested hosts and standby servers passed every health check. Failed. One or more tested hosts failed a health check. The health status of standby servers is not included when this result is calculated.
Iad and Fusion Manager PASSED Viewing logs Logs are provided for the Fusion Manager, file serving nodes, and 9000 clients. Contact HP Support for assistance in interpreting log files. You might be asked to tar the logs and email them to HP.
-n Network statistics -f NFS statistics -h The file serving nodes to be included in the report Sample output follows: ---------Summary------------ HOST Status CPU Disk(MB/s) Net(MB/s) lab12-10.hp.com 22528 ---------IO------------ HOST Read(MB/s) Read(IO/s) Read(ms/op) Write(MB/s) Write(IO/s) Write(ms/op) lab12-10.hp.com 22528 0.00 ---------Net------------...
9 Using the Statistics tool The Statistics tool reports historical performance data for the cluster or for an individual file serving node. You can view data for the network, the operating system, and the file systems, including the data for NFS, memory, and block devices. Statistical data is transmitted from each file serving node to the Fusion Manager, which controls processing and report generation.
Upgrading the Statistics tool from IBRIX software 6.0 The statistics history is retained when you upgrade to version 6.1 or later. The Statstool software is upgraded when the IBRIX software is upgraded using the ibrix_upgrade and auto_ibrixupgrade scripts. Note the following: If statistics processes were running before the upgrade started, those processes will automatically restart after the upgrade completes successfully.
The Time View lists the reports in chronological order, and the Table View lists the reports by cluster or server. Click a report to view it. Generating reports To generate a new report, click Request New Report on the IBRIX Management Console Historical Reports GUI.
To generate a report, enter the necessary specifications and click Submit. The completed report appears in the list of reports on the statistics home page. When generating reports, be aware of the following: A report can be generated only from statistics that have been gathered. For example, if you start the tool at 9:40 a.m.
Updating the Statistics tool configuration When you first configure the Statistics tool, the configuration includes information for all file systems configured on the cluster. If you add a new node or a new file system, or make other additions to the cluster, you must update the Statistics tool configuration.
NOTE: If the old active Fusion Manager is not available (pingable) for more than two days, the historical statistics database is not transferred to the current active Fusion Manager. If configurable parameters were set before the failover, the parameters are retained after the failover.
“Controlling Statistics tool processes” (page 86). Installation issues. Check the /tmp/stats-install.log and try to fix the condition, or send the /tmp/stats-install.log to HP Support. Missing reports for file serving nodes. If reports are missing on the Stats tool web page, check the following: ◦...
10 Maintaining the system Shutting down the system To shut down the system completely, first shut down the IBRIX software, and then power off the system hardware. Shutting down the IBRIX software Use the following procedure to shut down the IBRIX software. Unless noted otherwise, run the commands from the node hosting the active Fusion Manager.
Unmount all file systems on the cluster nodes: ibrix_umount -f <fs_name> To unmount file systems from the GUI, select Filesystems > unmount. Verify that all file systems are unmounted: ibrix_fs -l If a file system fails to unmount on a particular node, continue with this procedure. The file system will be forcibly unmounted during the node shutdown.
Power on the node hosting the active Fusion Manager. Power on the file serving nodes (*root segment = segment 1; power on owner first, if possible). Monitor the nodes on the GUI and wait for them all to report UP in the output from the following command: ibrix_server -l Mount file systems and verify their content.
/etc/init.d/ibrix_client [start | stop | restart | status] Tuning file serving nodes and 9000 clients Typically, HP Support sets the tuning parameters on the file serving nodes during the cluster installation and changes should be needed only for special situations.
Page 92
The IAD Tunings dialog box configures the IBRIX administrative daemon. The Module Tunings dialog box adjusts various advanced parameters that affect server operations. Maintaining the system...
Page 93
On the Servers dialog box, select the servers to which the tunings should be applied. Tuning file serving nodes and 9000 clients...
Page 94
To tune host parameters on nodes or host groups: ibrix_host_tune -S {-h HOSTLIST|-g GROUPLIST} -o OPTIONLIST Contact HP Support to obtain the values for OPTIONLIST. List the options as option=value pairs, separated by commas. To set host tunings on all clients, include the -g clients option.
--list See the ibrix_lwhost command description in the HP IBRIX 9000 Storage CLI Reference Guide for other available options. Windows clients. Click the Tune Host tab on the Windows 9000 client GUI. Tunable parameters include the NIC to prefer (the default is the cluster interface), the communications protocol (UDP or TCP), and the number of server threads to use.
Page 96
The Change Ownership dialog box reports the status of the servers in the cluster and lists the segments owned by each server. In the Segment Properties section of the dialog box, select the segment whose ownership you are transferring, and click Change Owner. Maintaining the system...
The new owner of the segment must be able to see the same storage as the original owner. The Change Segment Owner dialog box lists the servers that can see the segment you selected. Select one of these servers to be the new owner. The Summary dialog box shows the segment migration you specified.
Page 98
Identify the segment residing on the physical volume to be removed. Select Storage from the Navigator on the GUI. Note the file system and segment number on the affected physical volume. Locate other segments on the file system that can accommodate the data being evacuated from the affected segment.
Page 99
Guide. Troubleshooting segment evacuation If segment evacuation fails, HP recommends that you run phase 1 of the ibrix_fsck command in corrective mode on the segment that failed the evacuation. For more information, see “Checking and repairing file systems” in the HP IBRIX 9000 Storage File System User Guide.
# ./inum2name --fsname=ibfs 500000017 ibfs:/sliced_dir/file3.bin After obtaining the name of the file, use a command such as cp to move the file manually. Then run the segment evacuation process again. The analyzer log lists the chunks that were left on segments. Following is an example of the log: 2012-03-13 11:57:35:0332834 | <INFO>...
For a highly available cluster, HP recommends that you put protocol traffic on a user network and then set up automated failover for it (see “Configuring High Availability on the cluster”...
Execute this command once for each destination host that the file serving node or 9000 client should contact using the specified network interface (IFNAME). For example, to prefer network interface eth3 for traffic from file serving node s1.hp.com to file serving node s2.hp.com: ibrix_server -n -h s1.hp.com -A s2.hp.com/eth3...
-n -g HOSTGROUP -A DESTHOST/IFNAME The destination host (DESTHOST) cannot be a host group. For example, to prefer network interface eth3 for traffic from all 9000 clients (the clients host group) to file serving node s2.hp.com: ibrix_hostgroup -n -g clients -A s2.hp.com/eth3...
The following command adds a route for virtual interface eth2:232 on file serving node s2.hp.com, sending all traffic through gateway gw.hp.com: ibrix_nic -r -n eth2:232 -h s2.hp.com -A -R gw.hp.com Deleting a routing table entry If you delete a routing table entry, it is not replaced with a default entry. A new replacement route must be added manually.
“Changing the cluster interface” (page 104). To delete a network interface, use the following command: ibrix_nic -d -n IFNAME -h HOSTLIST The following command deletes interface eth3 from file serving nodes s1.hp.com and s2.hp.com: ibrix_nic -d -n eth3 -h s1.hp.com,s2.hp.com Viewing network interface information Executing the ibrix_nic command with no arguments lists all interfaces on all file serving nodes.
/tmp/X93xx/ibrix. If this directory no longer exists, download the installation code from the HP support website for your storage system. IMPORTANT: The migration procedure can be used only on clusters running HP IBRIX 9000 software 5.4 or later. Backing up the configuration...
Page 107
/etc/init.d/network restart service network restart Verify that you can ping the new local IP address. Configure the agile management console: ibrix_fm -c <cluster_VIF_addr> -d <cluster_VIF_device> –n <cluster_VIF_netmask> -v cluster -I <local_cluster_IP_addr> In the command, <cluster_VIF_addr> is the old cluster IP address for the original management console and <local_cluster_IP_addr>...
[root@x109s1 ~]# ibrix_fm -f NAME IP ADDRESS ------ ---------- X109s1 172.16.3.100 Command succeeded! 1 1. Install a passive agile management console on a second file serving node. In the command, the -F option forces the overwrite of the new_lvm2_uuid file that was installed with the IBRIX software.
On the node hosting the active Fusion Manager, place the Fusion Manager into maintenance mode. This step fails over the active Fusion Manager role to the node currently hosting the passive agile Fusion Manager. <ibrixhome>/bin/ibrix_fm –m nofmfailover Wait approximately 60 seconds for the failover to complete, and then run the following command on the node that was hosting the passive agile Fusion Manager: <ibrixhome>/bin/ibrix_fm -i The command should report that the agile Fusion Manager is now Active on this node.
Page 110
Uninstall the management console from the Management Server machine: /ibrix/ibrixinit -tm -U Verify that the uninstalled management console is no longer registered. Run the following command from the file serving node hosting the newly active management console: ibrix_fm -f The command should now report only the agile management console on the file serving node. [root@x109s3 ibrix]# ibrix_fm -f NAME IP ADDRESS...
12 Upgrading the IBRIX software to the 6.2 release This chapter describes how to upgrade to the 6.2 IBRIX software release. IMPORTANT: Print the following table and check off each step as you complete it. Table 2 Prerequisites checklist for all upgrades Step Step Description...
Table 2 Prerequisites checklist for all upgrades (continued) Step Step Description completed? If your FSN network bonded interfaces are currently configured for mode 6, configure them for mode 4 bonding (LACP). Make sure your Network Administrator reconfigures the network switch for LACP support on all effected ports. . Mode 4 has been found to outperform mode 6.
./auto_online_ibrixupgrade Upgrade Linux 9000 clients. See “Upgrading Linux 9000 clients” (page 120). If you received a new license from HP, install it as described in the “Licensing” chapter in this guide. After the upgrade Complete these steps: If your cluster nodes contain any 10Gb NICs, reboot these nodes to load the new driver. You must do this step before you upgrade the server firmware, as requested later in this procedure.
a file system, use the upgrade60.sh utility. For more information, see “Upgrading pre-6.0 file systems for software snapshots” (page 153). Data retention. Files used for data retention (including WORM and auto-commit) must be created on IBRIX software 6.1.1 or later, or the pre-6.1.1 file system containing the files must be upgraded for retention features.
Server, the Fusion Manager is installed in passive mode on that server. Upgrade Linux 9000 clients. See “Upgrading Linux 9000 clients” (page 120). If you received a new license from HP, install it as described in the “Licensing” chapter in this guide. After the upgrade Complete the following steps: If your cluster nodes contain any 10Gb NICs, reboot these nodes to load the new driver.
Review the file /etc/hosts on every IBRIX node (file serving nodes and management nodes) to ensure the hosts file contains two lines similar to the following: 127.0.0.1 <hostname> localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 In this instance, <hostname> is the name of the IBRIX node as returned by the hostname command.
Page 117
Verify that all file system node servers have separate file systems mounted on the following partitions by using the df command: /local /stage /alt Verify that all FSN servers have a minimum of 4 GB of free/available storage on the /local partition by using the df command .
Server, the Fusion Manager is installed in passive mode on that server. Upgrade Linux 9000 clients. See “Upgrading Linux 9000 clients” (page 120). If you received a new license from HP, install it as described in the “Licensing” chapter in this guide. After the upgrade Complete the following steps: If your cluster nodes contain any 10Gb NICs, reboot these nodes to load the new driver.
Page 119
-t -S "ignore_writethru=1" The SMB signing feature specifies whether clients must support SMB signing to access SMB shares. See the HP IBRIX 9000 Storage File System User Guide for more information about this feature. Whenignore_writethru is enabled, IBRIX software ignores writethru buffering to improve SMB write performance on some user applications that request it.
/etc/init.d/ibrix_client status IBRIX Filesystem Drivers loaded IBRIX IAD Server (pid 3208) running... The IAD service should be running, as shown in the previous sample output. If it is not, contact HP Support. Installing a minor kernel update on Linux clients The 9000 client software is upgraded automatically when you install a compatible Linux minor kernel update.
If you are using Remote Desktop to perform an upgrade, you must log out and log back in to see the drive mounted. Troubleshooting upgrade issues If the upgrade does not complete successfully, check the following items. For additional assistance, contact HP Support. Automatic upgrade Check the following: If the initial execution of /usr/local/ibrix/setup/upgrade fails, check /usr/local/ibrix/setup/upgrade.log for errors.
Manual upgrade Check the following: If the restore script fails, check /usr/local/ibrix/setup/logs/restore.log for details. If configuration restore fails, look at /usr/local/ibrix/autocfg/logs/appliance.log to determine which feature restore failed. Look at the specific feature log file under /usr/ local/ibrix/setup/logs/ for more detailed information. To retry the copy of configuration, use the following command: /usr/local/ibrix/autocfg/bin/ibrixapp upgrade –f –s Offline upgrade fails because iLO firmware is out of date...
[root@ib51-102 ~]# ibrix_fm -f NAME IP ADDRESS -------- ---------- ib51-101 10.10.51.101 ib51-102 10.10.51.102 [root@ib51-102 ~]# ibrix_fm -i FusionServer: ib51-102 (active, quorum is running) ================================================== File system unmount issues If a file system does not unmount successfully, perform the following steps on all servers: Run the following commands: chkconfig ibrix_server off chkconfig ibrix_ndmp off...
Fax the Password Request Form that came with your License Entitlement Certificate. See the certificate for fax numbers in your area. Call or email the HP Password Center. See the certificate for telephone numbers in your area or email addresses.
Parent device ID Components for firmware upgrades The HP IBRIX system includes several components with upgradable firmware. The following table lists these components and specifies whether they can be upgraded online and in a nondisruptive manner. The following example is an example for the 9320 system.
Do not cycle power or restart devices during a firmware update. To upgrade the firmware for components: Run the /opt/hp/platform/bin/hpsp_fmt -fr command to verify that the firmware on this node and subsequent nodes in this cluster is correct and up-to-date. This command should be performed before placing the cluster back into service.
Page 127
Do the following based on the Proposed Action and Severity: Status in Proposed Action column Status in Severity column Go to UPGRADE MANDATORY Step 3 UPGRADE RECOMMENDED Step 3 is optional. However, it is recommended to perform step 3 for system stability and to avoid any known issues.
Page 128
Determine whether the node to be flashed is the active Fusion Manager by enter the following command: ibrix_fm –i Perform a manual FM failover on the local node by entering the following command from the active Fusion Manager: ibrix_fm -m nofmfailover server1 The FM failover will take approximately one minute.
Online help for FMT. To access the online help for FMT, enter the hpsp_fmt command on the file system node console. HP HPSP_FMT User Guide. To access the HP HPSP_FMT User Guide, go to the HP StoreAll Storage Manuals page: http://www.hp.com/support/IBRIXManuals...
Ibrix Collect is a log collection utility that allows you collect relevant information for diagnosis by HP Support when system issues occur. The collection can be triggered manually using the GUI or CLI, or automatically during a system crash. Ibrix Collect gathers the following information:...
NOTE: You may later be asked to email this final zip file to HP Support. Be aware that the final zip file is not the same as the zip file that you receive in your email.
To specify more than one collection to be deleted at a time from the CLI, provide the names separated by a semicolon. To delete all data collections manually from the CLI, use the following command: ibrix_collect –F Configuring Ibrix Collect You can configure data collection to occur automatically upon a system crash.
The file system and IAD/FS output fields should show matching version numbers unless you have installed special releases or patches. If the output fields show mismatched version numbers and you do not know of any reason for the mismatch, contact HP Support. A mismatch might affect the operation of your cluster.
SELINUX=parameter to either permissive or disabled. SELinux will be stopped at the next boot. For 9000 clients, the client might not be registered with the Fusion Manager. For information on registering clients, see the HP IBRIX 9000 Storage Installation Guide. Failover Cannot fail back from failover caused by storage subsystem failure When a storage subsystem fails and automated failover is turned on, the Fusion Manager will initiate its failover protocol.
To maintain access to a file system, file serving nodes must have current information about the file system. HP recommends that you execute ibrix_health on a regular basis to monitor the health of this information. If the information becomes outdated on a file serving node, execute ibrix_dbck -o to resynchronize the server’s information with the configuration database.
Page 136
of the Express Query, they are typically due to another unrelated event in the cluster or the file system. Therefore, most of the work to recover from an Express Query MIF is to check the health of the cluster and the file system and take corrective actions to fix the issues caused by these events. Once the cluster and file system have an OK status, the MIF status can be cleared since the Express Query service will be recovering and restarting automatically.
Page 137
Wait for the resynchronizer to complete by entering the following command: ibrix_archiving -l Repeat this command until it displays the OK status for the file system. If none of the above worked, contact HP. Troubleshooting an Express Query Manual Intervention Failure (MIF) 137...
This is a destructive process that completely erases all of the data on local hard drives. Obtaining the latest IBRIX software release To obtain the latest HP IBRIX 6.2.1 (pkg-full.ISO) ISO image, register to download the software on the HP StoreAll Download Drivers and Software web page.
Page 139
Enter the information for the node being restored on the Network Configuration dialog box and click OK. Confirm that the information displayed in the Configuration Summary dialog box is correct and click Commit. Performing the recovery 139...
Page 140
On the X9000 Installation — Network Setup Complete dialog box, select Join this IBIRX server to an existing cluster and click OK. 140 Recovering a file serving node...
Page 141
The wizard scans the network for existing clusters. On the Join Cluster dialog box, select the management console (Fusion Manager) for your cluster, and then click OK. If your cluster does not exist in the list of choices, click Cancel so that you can provide the IP address of the FM to which this node has to be registered.
Page 142
If you clicked the Cancel button in the previous dialog box, enter the management console IP of the desired cluster on the Management Console IP dialog box and click OK. On the Replace Existing Server dialog box, click Yes when you are asked if you want to replace the existing server.
For example: ibrix_nic -m -h titan16 -A titan15/eth2 Configure Insight Remote Support on the node. See “Configuring HP Insight Remote Support on IBRIX 9000 systems” (page 21). Run ibrix_health -l from the IBRIX management console to verify that no errors are being reported.
Page 144
Take the appropriate actions: If Active Directory authentication is used, join the restored node to the AD domain manually. If Local user authentication is used, create a temporary local user on the GUI and apply the settings to all servers. This step resynchronizes the local user database. Then remove the temporary user.
HP ProLiant DL380 G6 Server Maintenance and Service Guide To find these documents, go to the Manuals page (http://www.hp.com/support/manuals) and select servers > ProLiant ml/dl and tc series servers > HP ProLiant DL380 G7 Server series or HP ProLiant DL380 G6 Server series.
Online help for HP Storage Management Utility (SMU) and Command Line Interface (CLI) To find these documents, go the Manuals page (http://www.hp.com/support/manuals) and select storage >Disk Storage Systems > MSA Disk Arrays >HP 2000sa G2 Modular Smart Array or HP P2000 G3 MSA Array Systems.
18 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...
A Cascading Upgrades If you are running an IBRIX version earlier than 5.6, do incremental upgrades as described in the following table. If you are running IBRIX 5.6, upgrade to 6.1 before upgrading to 6.2. If you are upgrading from Upgrade to Where to find additional information IBRIX version 5.4...
./auto_online_ibrixupgrade Upgrade Linux 9000 clients. See “Upgrading Linux 9000 clients” (page 120). If you received a new license from HP, install it as described in the “Licensing” chapter in this guide. After the upgrade Complete these steps: Start any Remote Replication, Rebalancer, or data tiering tasks that were stopped before the upgrade.
a file system, use the upgrade60.sh utility. For more information, see “Upgrading pre-6.0 file systems for software snapshots” (page 153). ◦ Data retention. Files used for data retention (including WORM and auto-commit) must be created on IBRIX software 6.1.1 or later, or the pre-6.1.1 file system containing the files must be upgraded for retention features.
Server, the Fusion Manager is installed in passive mode on that server. Upgrade Linux 9000 clients. See “Upgrading Linux 9000 clients” (page 120). If you received a new license from HP, install it as described in the “Licensing” chapter in this guide. After the upgrade Complete the following steps:...
/etc/init.d/ibrix_client status IBRIX Filesystem Drivers loaded IBRIX IAD Server (pid 3208) running... The IAD service should be running, as shown in the previous sample output. If it is not, contact HP Support. Installing a minor kernel update on Linux clients The 9000 client software is upgraded automatically when you install a compatible Linux minor kernel update.
NOTE: To use the verify_client command, the 9000 client software must be installed. Upgrading Windows 9000 clients Complete the following steps on each client: Remove the old Windows 9000 client software using the Add or Remove Programs utility in the Control Panel. Copy the Windows 9000 client MSI file for the upgrade to the machine.
After the command finishes upgrading the file system, re-mount the file system. Enter the ibrix_fs command to set the file system’s data retention and autocommit period to the desired values. See the HP IBRIX 9000 Storage CLI Reference Guide for additional information about the ibrix_fs command.
Automatic upgrade Check the following: If the initial execution of /usr/local/ibrix/setup/upgrade fails, check /usr/local/ibrix/setup/upgrade.log for errors. It is imperative that all servers are up and running the IBRIX software before you execute the upgrade script. If the install of the new OS fails, power cycle the node. Try rebooting. If the install does not begin after the reboot, power cycle the machine and select the upgrade line from the grub boot menu.
================================================== [root@ib51-101 ibrix]# ibrix_fm -f NAME IP ADDRESS -------- ---------- ib51-101 15.226.51.101 ib51-102 10.10.51.102 If the node is hosting the active Fusion Manager, as in this example, stop the Fusion Manager on that node: [root@ib51-101 ibrix]# /etc/init.d/ibrix_fusionmanager stop Stopping Fusion Manager Daemon [root@ib51-101 ibrix]# On the node now hosting the active Fusion Manager (ib51–102 in the example), unregister node ib51–101:...
GUI or use the ibrix_health command. To upgrade all nodes in the cluster automatically, complete the following steps: Check the dashboard on the management console GUI to verify that all nodes are up. Obtain the latest release image from the HP kiosk at http://www.software.hp.com/kiosk (you will need your HP-provided login credentials).
The manual upgrade process requires external storage that will be used to save the cluster configuration. Each server must be able to access this media directly, not through a network, as the network configuration is part of the saved configuration. HP recommends that you use a USB stick or DVD.
For an agile configuration, on all nodes hosting the passive management console, return the management console to passive mode: <ibrixhome>/bin/ibrix_fm -m passive If you received a new license from HP, install it as described in the “Licensing” chapter in this document. Troubleshooting upgrade issues If the upgrade does not complete successfully, check the following items.
Automatic upgrade Check the following: If the initial execution of /usr/local/ibrix/setup/upgrade fails, check /usr/local/ibrix/setup/upgrade.log for errors. It is imperative that all servers are up and running the IBRIX software before you execute the upgrade script. If the install of the new OS fails, power cycle the node. Try rebooting. If the install does not begin after the reboot, power cycle the machine and select the upgrade line from the grub boot menu.
NOTE: If you are upgrading from an IBRIX 5.x release, any support tickets collected with the ibrix_supportticket command will be deleted during the upgrade. Download a copy of the archive files (.tgz) from the /admin/platform/diag/supporttickets directory. Upgrades can be run either online or offline: Online upgrades.
To determine whether you have an agile management console configuration, run the ibrix_fm -i command. If the output reports the status as quorum is not configured, your cluster does not have an agile configuration. Be sure to use the upgrade procedure corresponding to your management console configuration: For standard upgrades, use Page 162.
Page 163
2323332 0 (unused) lsmod|grep ipfs ipfs1 102592 0 (unused) If either grep command returns empty, contact HP Support. From the management console, verify that the new version of IBRIX software FS/IAS is installed on the file serving node: <ibrixhome>/bin/ibrix_version -l –S If the upgrade was successful, failback the file serving node: <ibrixhome>/bin/ibrix_server -f -U -h HOSTNAME...
If you followed all instructions and the version indicators do not match, contact HP Support. Propagate a new segment map for the cluster: <ibrixhome>/bin/ibrix_dbck -I -f FSNAME Verify the health of the cluster: <ibrixhome>/bin/ibrix_health -l The output should specify Passed / on.
Page 165
2323332 0 (unused) lsmod|grep ipfs ipfs1 102592 0 (unused) If either grep command returns empty, contact HP Support. From the management console, verify that the new version of IBRIX software FS/IAS has been installed on the file serving nodes: <ibrixhome>/bin/ibrix_version -l –S...
The output should show Passed / on. Agile upgrade for clusters with an agile management console configuration Use these procedures if your cluster has an agile management console configuration. The IBRIX software 5.4.x to 5.5 upgrade can be performed either online or offline. Future releases may require offline upgrades.
Page 167
This step fails back the active management console role to the node currently hosting the passive agile management console (the node that originally was active). Wait approximately 90 seconds for the failover to complete, and then run the following command on the node that was the target for the failover: <ibrixhome>/bin/ibrix_fm -i The command should report that the agile management console is now Active on this node.
Page 168
When the upgrade is complete, verify that the IBRIX software services are running on the node: /etc/init.d/ibrix_server status The output will be similar to the following. If the IAD service is not running on your system, contact HP Support. IBRIX Filesystem Drivers loaded ibrcud is running.. pid 23325 IBRIX IAD Server (pid 23368) running...
2323332 0 (unused) lsmod|grep ipfs ipfs1 102592 0 (unused) If either grep command returns empty, contact HP Support. From the management console, verify that the new version of IBRIX software FS/IAS has been installed on the file serving node: <ibrixhome>/bin/ibrix_version -l –S...
Page 170
Preparing for the upgrade On the active management console node, disable automated failover on all file serving nodes: <ibrixhome>/bin/ibrix_server -m -U Verify that automated failover is off. In the output, the HA column should display off. <ibrixhome>/bin/ibrix_server -l On the active management console node, stop the NFS and SMB services on all file serving nodes to prevent NFS and SMB clients from timing out.
Page 171
2323332 0 (unused) lsmod|grep ipfs ipfs1 102592 0 (unused) If either grep command returns empty, contact HP Support. From the active management console node, verify that the new version of IBRIX software FS/IAS is installed on the file serving nodes: <ibrixhome>/bin/ibrix_version -l –S...
If there is a version mismatch, run the /ibrix/ibrixupgrade -f script again on the affected node, and then recheck the versions. The installation is successful when all version indicators match. If you followed all instructions and the version indicators do not match, contact HP Support. Verify the health of the cluster: <ibrixhome>/bin/ibrix_health -l The output should show Passed / on.
B Component diagrams for 9300 systems Front view of file serving node Item Description Quick-release levers (2) HP Systems Insight Manager display Hard drive bays SATA optical drive bay Video connector USB connectors (2) Rear view of file serving node...
Page 174
Item Description NIC 1 connector NIC 2 connector Mouse connector Keyboard connector Serial connector iLO 2 connector NIC 3 connector NIC 4 connector Component diagrams for 9300 systems...
Page 175
Server PCIe card PCI slot HP SC08Ge 3Gb SAS Host Bus Adapter NC364T Quad 1Gb NIC empty SATA 1Gb empty empty empty HP SC08Ge 3Gb SAS Host Bus Adapter empty empty SATA 10Gb NC522SFP dual 10Gb NIC empty empty HP SC08Ge 3Gb SAS Host Bus Adapter...
Optional. Parts for which customer self repair is optional. These parts are also designed for customer self-repair. If, however, you require that HP replace them for you, there may or may not be additional charges, depending on the type of warranty service designated for your product.
D System component and cabling diagrams for 9320 systems System component diagrams Front view of 9300c array controller or 9300cx 3.5" 12-drive enclosure Item Description 1–12 Disk drive bay numbers Enclosure ID LED Disk drive Online/Activity LED Disk drive Fault/UID LED Unit Identification (UID) LED Fault ID LED Heartbeat ID LED...
Rear view of 9300c array controller Item Description Power supplies Power switches Host ports CLI port Network port Service port (used by service personnel only) Expansion port (connects to drive enclosure) Rear view of 9300cx 3.5" 12-drive enclosure Item Description Power supplies Power switches SAS In port (connects to the controller enclosure)
Front view of file serving node Item Description Quick-release levers (2) HP Systems Insight Manager display Hard drive bays SATA optical drive bay Video connector USB connectors (2) Rear view of file serving node Item Description PCI slot 5 PCI slot 6...
Page 188
Item Description Mouse connector Keyboard connector Serial connector iLO 2 connector NIC 3 connector NIC 4 connector 188 System component and cabling diagrams for 9320 systems...
Page 189
Server PCIe card PCI slot HP SC08Ge 3Gb SAS Host Bus Adapter NC364T Quad 1Gb NIC empty SATA 1Gb empty empty empty HP SC08Ge 3Gb SAS Host Bus Adapter empty empty SATA 10Gb NC522SFP dual 10Gb NIC empty empty HP SC08Ge 3Gb SAS Host Bus Adapter...
SAS option cabling Line Description SAS I/O pathArray 1: Controller A SAS I/O pathArray 1: Controller B SAS I/O pathArray 2: Controller A SAS I/O pathArray 2: Controller B 192 System component and cabling diagrams for 9320 systems...
Optional. Parts for which customer self repair is optional. These parts are also designed for customer self repair. If, however, you require that HP replace them for you, there may or may not be additional charges, depending on the type of warranty service designated for your product.
9320 Storage HP IBRIX 9320 72 TB LFF ML Storage Starter Kit (QZ722A) Description Spare part number CSR type SPS-CA,EXT MINI SAS, 2M 408767-001 Mandatory SPS-CONTROLLER-P2000 G3 SAS 582934-001 Optional SPS-CHASSIS 2U12 6G w/MIDPLANE 582938-001 Mandatory SPS-CONTROLLER BD IO 6GB...
Page 230
CSR type SPS-PWR SUPPLY 595W 592267-001 Optional SPS-DRV HD 3TB SAS 7.2K 6G 3.5 656102-001 Mandatory HP IBRIX 9320 7.2 TB SFF Ent Storage Starter Kit (QZ724B) Description Spare part number CSR type CABLE-CAT5E, RJ45, male/male 5183-2685 Mandatory SPS-CA,EXT MINI SAS, 2M...
Page 231
530834-001 SPS-POWER SUPPLY, 460W 536404-001 Mandatory SPS-DRV HD 300GB 10K SFF M6625 SAS 58371 1-001 Mandatory HP IBRIX 9320 21.6 TB SFF Ent Storage Starter Kit (QZ726A) Description Spare part number CSR type SPS-CA,EXT MINI SAS, 2M 408767-001 Mandatory SPS-CONTROLLER-P2000 G3 SAS...
Page 232
Description Spare part number CSR type SPS-FAN ASSY,SAS,2600/2700 519325-001 Mandatory SPS-ASSY,CHASSIS, M6412 DISK SHELF 530834-001 SPS-POWER SUPPLY, 460W 536404-001 Mandatory SPS-DRV HD 900GB 6G 10K SFF M6625 SAS 665749-001 Mandatory 232 Spare parts list for 9320 systems...
Use conductive field service tools. Use a portable field service kit with a folding static-dissipating work mat. If you do not have any of the suggested equipment for proper grounding, have an HP-authorized reseller install the part. NOTE: For more information on static electricity or assistance with product installation, contact your HP-authorized reseller.
Equipment symbols If the following symbols are located on equipment, hazardous conditions could exist. WARNING! Any enclosed surface or area of the equipment marked with these symbols indicates the presence of electrical shock hazards. Enclosed area contains no operator serviceable parts. To reduce the risk of injury from electrical shock hazards, do not open this enclosure.
WARNING! Verify that the AC power supply branch circuit that provides power to the rack is not overloaded. Overloading AC power to the rack power supply circuit increases the risk of personal injury, fire, or damage to the equipment. The total rack load should not exceed 80 percent of the branch circuit rating.
Page 236
CAUTION: Protect the installed solution from power fluctuations and temporary interruptions with a regulating Uninterruptible Power Supply (UPS). This device protects the hardware from damage caused by power surges and voltage spikes, and keeps the system in operation during a power failure.
The regulatory model number is not the marketing name or model number of the product. Product specific information: HP ________________ Regulatory model number: _____________ FCC and CISPR classification: _____________ These products contain laser components.
This compliance is indicated by the following conformity marking placed on the product: This marking is valid for non-Telecom products and EU harmonized Telecom products (e.g., Bluetooth). Certificates can be obtained from http://www.hp.com/go/certificates. Hewlett-Packard GmbH, HQ-TRE, Herrenberger Strasse 140, 71034 Boeblingen, Germany 238 Regulatory compliance notices...
Japanese notices Japanese VCCI-A notice Japanese VCCI-B notice Japanese VCCI marking Japanese power cord statement Korean notices Class A equipment Class B equipment Japanese notices 239...
Do not try to open the module enclosure. There are no user-serviceable components inside. Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein. Allow only HP Authorized Service technicians to repair the unit. 240 Regulatory compliance notices...
The Center for Devices and Radiological Health (CDRH) of the U.S. Food and Drug Administration implemented regulations for laser products on August 2, 1976. These regulations apply to laser products manufactured from August 1, 1976. Compliance is mandatory for products marketed in the United States.
Recycling notices English recycling notice Disposal of waste equipment by users in private household in the European Union This symbol means do not dispose of your product with your other household waste. Instead, you should protect human health and the environment by handing over your waste equipment to a designated collection point for the recycling of waste electrical and electronic equipment.
Estonian recycling notice Äravisatavate seadmete likvideerimine Euroopa Liidu eramajapidamistes See märk näitab, et seadet ei tohi visata olmeprügi hulka. Inimeste tervise ja keskkonna säästmise nimel tuleb äravisatav toode tuua elektriliste ja elektrooniliste seadmete käitlemisega egelevasse kogumispunkti. Küsimuste korral pöörduge kohaliku prügikäitlusettevõtte poole. Finnish recycling notice Kotitalousjätteiden hävittäminen Euroopan unionin alueella Tämä...
Italian recycling notice Smaltimento di apparecchiature usate da parte di utenti privati nell'Unione Europea Questo simbolo avvisa di non smaltire il prodotto con i normali rifi uti domestici. Rispettare la salute umana e l'ambiente conferendo l'apparecchiatura dismessa a un centro di raccolta designato per il riciclo di apparecchiature elettroniche ed elettriche.
Romanian recycling notice Casarea echipamentului uzat de către utilizatorii casnici din Uniunea Europeană Acest simbol înseamnă să nu se arunce produsul cu alte deşeuri menajere. În schimb, trebuie să protejaţi sănătatea umană şi mediul predând echipamentul uzat la un punct de colectare desemnat pentru reciclarea echipamentelor electrice şi electronice uzate.
Domain name system. File Transfer Protocol. Global service indicator. High availability. Host bus adapter. Host channel adapter. Hard disk drive. HP 9000 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 251
TCP/IP Transmission Control Protocol/Internet Protocol. User Datagram Protocol. Unit identification. 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. A globally unique 64-bit identifier assigned to each Fibre Channel node process.
9000 clients components add to host group, 9300 diagrams, change IP address, 9320 diagrams, identify a user network interface, contacting HP, monitor status, core dump, prefer a user network interface, start or stop processes, troubleshooting, Disposal of waste equipment, European Union,...
Page 253
HP Insight Remote Support, tune, Phone Home, view process status, troubleshooting, file system migrate segments, firewall configuration, Ibrix Collect, firmware, upgrade,...