HP StorageWorks 9100 Extreme Data Storage System administration guide V1.0.2 (AN540-96018, February 2010)

ManualsBrandsHP ManualsStorageExtreme Data Storage

HP StorageWorks

9100 Extreme Data Storage System

administration guide

V1.0.2

This guide describes how to operate the HP StorageWorks 9100 Extreme Data Storage System (HP ExDS9100

Storage System) and perform routine system administration tasks. This guide describes only the software and

hardware components of the HP ExDS9100 Storage System product. It does not document standard Linux

administrative tasks or the functions provided by standard Linux tools and commands; it provides only

administrative information and instructions for tasks specific to HP ExDS9100 Storage System. The intended

audience of this guide is system administrators and technicians who are experienced with managing SAN

environments, installing and administering networks, and performing Linux operating and administrative tasks.

Part number: AN540-96018 rev. 2

Third edition: February 2010

Summary of content (194 pages)

PAGE 1
HP StorageWorks 9100 Extreme Data Storage System administration guide V1.0.2 This guide describes how to operate the HP StorageWorks 9100 Extreme Data Storage System (HP ExDS9100 Storage System) and perform routine system administration tasks. This guide describes only the software and hardware components of the HP ExDS9100 Storage System product.
PAGE 2
Legal and notice information © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
PAGE 3
Contents 1 Overview ........................................................................................ 13 Product overview ...................................................................................................................... HP ExDS9100 Storage System features ........................................................................................ HP ExDS9100 Storage System components ..................................................................................
PAGE 4
Using mxconsole and mx(8) ....................................................................................................... Matrix management overview .............................................................................................. Restrictions on use of mxconsole and mx(8) ........................................................................... Issuing commands to groups of hosts ...........................................................................................
PAGE 5
Step 6 — Create symbolic links ..................................................................................... Step 7 — Configure virtual hosts .................................................................................... Step 8 — Configure a CUSTOM service monitor .............................................................. Log files for Samba service monitor operations ....................................................................... Managing Web services .............................
PAGE 6
Restoring the firewall configuration to the factory setting .......................................................... User accounts .......................................................................................................................... Customizing mySQL .................................................................................................................. Installing RPMs ...........................................................................................................
PAGE 7
Standard online update mechanism .................................................................................... Upgrading Onboard Administrator ........................................................................................... Upgrading all Virtual Connect modules ..................................................................................... Upgrading HP ExDS9100cc, HP ExDS9100cx I/O module, and disk drive firmware ....................... Upgrading SAS switch module firmware ..........
PAGE 8
Syntax ............................................................................................................................ Network testing ...................................................................................................................... exds_netdiag ................................................................................................................... Sample output ......................................................................................................
PAGE 9
Laser compliance .................................................................................................................... International notices and statements .......................................................................................... Canadian notice (Avis Canadien) ....................................................................................... Class A equipment .....................................................................................................
PAGE 10
Figures 1 Front view of an HP ExDS9100 base cabinet with one storage block ............................. 14 2 Back view of an HP ExDS9100 base cabinet with one storage block ............................. 15 3 Front view of an HP ExDS9100 expansion cabinet ...................................................... 16 4 Rear view of an HP ExDS9100 expansion cabinet ...................................................... 17 5 Front view of a c-Class Blade enclosure ..................................................
PAGE 11
Tables 1 Server states .......................................................................................................... 43 2 Disk drive states ..................................................................................................... 50 3 LUN roles ............................................................................................................... 51 4 Logical disk states ...................................................................................................
PAGE 12
PAGE 13
1 Overview Product overview HP StorageWorks 9100 Extreme Data Storage System (HP ExDS9100 Storage System) is a scalable network attached storage (NAS) product.
PAGE 14
Figure 1 shows the front view of the HP ExDS9100 Storage System base cabinet: Figure 1 Front view of an HP ExDS9100 base cabinet with one storage block . 1. ExDS9100c 1 2. TFT monitor and keyboard 3. c-Class Blade enclosure 4.
PAGE 15
Figure 2 shows the back view of the HP ExDS9100 Storage System base cabinet: Figure 2 Back view of an HP ExDS9100 base cabinet with one storage block . 1. Management switch 2 2. Management switch 1 3. ExDS9100c 1 4. TFT monitor and keyboard 5. c-Class Blade enclosure 6.
PAGE 16
The optional HP ExDS9100 expansion cabinet can comprise from one to six storage blocks. Figure 3 shows a front view of an expansion cabinet with four storage blocks: 1. ExDS9100c 8 5. ExDS9100cx 8 2. ExDS9100c 7 6. ExDS9100cx 7 3. ExDS9100c 6 7. ExDS9100cx 6 4. ExDS9100c 5 8. ExDS9100cx 5 Figure 3 Front view of an HP ExDS9100 expansion cabinet .
PAGE 17
Figure 4 shows a back view of an expansion cabinet with four storage blocks: 1. ExDS9100c 8 5. ExDS9100cx 8 2. ExDS9100c 7 6. ExDS9100cx 7 3. ExDS9100c 6 7. ExDS9100cx 6 4. ExDS9100c 5 8. ExDS9100cx 5 Figure 4 Rear view of an HP ExDS9100 expansion cabinet .
PAGE 18
HP ExDS9100 performance block (c-Class Blade enclosure) Half-height device bay numbering 1 through 16 Figure 5 Front view of a c-Class Blade enclosure . 1. Interconnect bay 1 (HP 1/10Gb VCEnet) 6. Interconnect bay 6 (HP 1/10Gb VC-Enet) 2. Interconnect bay 2 (HP 1/10Gb VCEnet) 7. Interconnect bay 7 (reserved for future HP 1/10Gb VC-Enet) 3. Interconnect bay 3 (SAS Switch) 8. Interconnect bay 8 (reserved for future HP 1/10Gb VC-Enet) 4. Interconnect bay 4 (SAS Switch) 9. Onboard Administrator 1 5.
PAGE 19
HP ExDS9100c (array controller with 12 disk drives) The following diagram shows the HP ExDS9100c enclosure. In the exdsmgr set array and show array commands, this enclosure is box number 1. The disk drives are identified by bay number as indicated in the diagram. 1. Bay 1 5. Power LED 2. Bay 2 6. System fault LED 3. Bay 3 7. UID LED 4. Bay 4 8. Bay 12 Figure 7 Front view of an HP ExDS9100c . 1. Battery 1 9. Fan 2 2. Battery 2 10. HP ExDS9100cc controller 2 3. SAS expander port 1 11.
PAGE 20
HP ExDS9100cx (dense JBOD with 70 disk drives) NOTE: This component is also known as the HP StorageWorks 600 Modular Disk System. For an explanation of the LEDs and buttons on this component, see the HP StorageWorks 600 Modular Disk System User Guide at http://www.hp.com/support/manuals. Under Storage click Disk Storage Systems, then under Disk Enclosures click HP StorageWorks 600 Modular Disk System. The following diagram shows the front view of the ExDS9100cx enclosure. The enclosure contains two drawers.
PAGE 21
1. Power supply 5. In SAS port 2. Primary I/O module drawer 2 6. Secondary I/O module drawer 1 3. Primary I/O module drawer 1 7. Secondary I/O module drawer 2 4. Out SAS port 8. Fan Figure 10 Rear view of an HP ExDS9100cx .
PAGE 22
Overview
PAGE 23
2 On-site setup and commissioning The HP Enterprise NAS Implementation Service provides installation and configuration of HP StorageWorks X9000 Network Storage Systems in your storage environment. The service provides HP Network Storage System installation, configuration, testing, documentation, project management and a customer orientation session.
PAGE 24
• Demonstrate functioning file serving in the cluster server environment: • Mount filesystem, present a single namespace, create a file, and show that file is universally accessible across all file serving nodes • Export filesystem from NFS, CIFS, and, if applicable, a host running X9000 client software and show that files are universally accessible to all clients • Demonstrate the High Availability feature • Initiate file serving node failure and monitor failover • Bring file server node back online and mo
PAGE 25
3 HP ExDS9100 concepts This section discusses HP ExDS9100 concepts. For information about specific HP ExDS9100 commands, see the chapter where the command is discussed. Server blades Server blades are numbered according to their bay number in the blade enclosure. Server 1 is in bay 1 in the blade enclosure, and so on. Server blades must be contiguous; empty blade bays are not allowed between server blades. Only HP ExDS9100 server blades can be inserted in a blade enclosure.
PAGE 26
1. Box 1—HP ExDS9100c 2. Box 2—HP ExDS9100cx, left drawer (as viewed from the front) 3. Box 3—HP ExDS9100cx, right drawer (as viewed from the front) Figure 11 Array box numbering . NOTE: The software does not distinguish left and right; instead, box 2 and 3 are determined by the way SAS cables are connected. As part of the factory installation process, the exdsmgr identify storage command verifies that SAS cables are wired correctly. An array normally has two controllers.
PAGE 27
In Linux, a LUN appears as a /dev/cciss device. However, these device numbers are only relevant within a given server. Each server might assign a different /dev/cciss device number to a given LUN. For use within the Matrix software, a LUN is “imported” by the Matrix software and mapped to a / dev/psd device. The psd device number is the same for all members of the Matrix cluster. The create filesystem command automatically imports LUNs and they are mapped together with psd devices.
PAGE 28
For network services such as NFS and HTTP, clients use virtual hosts (so that the services are highly available) instead of the server’s direct network interface. In addition, it is preferable to have all servers involved equally in serving services, because this provides a scalable solution. This is done by associating a different virtual host for each server and by organizing the environment so the client population is split across each virtual host/server.
PAGE 29
4 The HP ExDS CLI Overview You can manage and operate many aspects of the HP ExDS9100 Storage System with the exdsmgr command. All changes to system configuration or server configuration are executed by this utility. CAUTION: Do not try to manually configure the system. For example, do not edit the /etc/hosts file. As well as being unsupported, your changes will be lost the next time the ExDS configure server command executes.
PAGE 30
3. Start the HP ExDS9100 CLI by entering the exdsmgr command Running exdsmgr commands In exdsmgr commands where it is appropriate, you can use either the singular or the plural form of the component to which the command applies. For example, you can enter the show lun command in either of the following formats: ExDS> show lun ExDS> show luns All of the commands, except for the help command, can be abbreviated.
PAGE 31
Aborting a command To abort a command, find the command using the show commands command and abort it using the kill command as shown in the following example: Checking a command's progress Use the monitor command to see how a command is progressing: Getting command help Use the help command to get help about specific commands. You can only use the help command in interactive mode.
PAGE 32
The HP ExDS CLI
PAGE 33
5 Operating the system—Common tasks IMPORTANT: Do not modify any operating system- or kernel-related parameters or update any part of the HP ExDS9100 unless instructed to do so by HP; otherwise, the HP ExDS9100 could fail to operate properly. Logging in to the HP ExDS9100 using the network Use ssh to log in remotely from another host. You can log into any server using any configured external network interface (eth2, eth3, eth4, or eth5).
PAGE 34
Logging in using the serial link on the Onboard Administrator If you are connected to a terminal server, you can log in through the serial link on the Onboard Administrator. Booting the system and individual server blades Before booting the system, ensure that all of the system components other than the server blades—the storage blocks and so on—are turned on. By default, server blades boot whenever power is applied to the HP ExDS9100 performance block (c-Class Blade enclosure).
PAGE 35
NOTE: Do not run the exdsmgr shutdown command on the server you are shutting down because you will lose contact with the command as the shutdown advances. However, the shutdown will complete normally. If you shut down a group of servers that includes the server where the exdsmgr command is running, the other servers are shut down first, and then finally the server where the exdsmg command is running is shut down. 2.
PAGE 36
where 16.123.123.1 is the virtual host. CAUTION: Do not disable the exdsadmin virtual host (normally 192.168.0.1). If you do so, the exdsmgr command will not function normally. 3. Shut down all servers except for the first server as shown in the following example: # exsmgr shutdown server 2-16 4. If required, shut down the first server to single user mode. This is sometimes required to perform maintenance, for example, to update disk drive firmware on a storage block.
PAGE 37
You can use the mxconsole or mx(8) commands to modify configurations that were initially created by exdsmgr. Even where you cannot use exdsmgr to make a change, the command will show the affects of changes made using mxconsole or mx(8). Restrictions on use of mxconsole and mx(8) You can use the full functionality of the Matrix software to customize and manage applications on an HP ExDS9100 system.
PAGE 38
Shutting down servers and the entire system Use the shutdown server command to shut down and turn off the power to the servers in the system, as shown in the example: # exdsmgr shutdown server 2-4 where 2-4 are server numbers. The shutdown server attempts to perform a controlled shutdown. If this takes too long to perform, the server is powered off (put into standby state). The timeout is specified by the wait option.
PAGE 39
1. Obtain the local host's name by entering the # hostname command as shown in the following example: # hostname glory1 where glory1 is the hostname. 2. Search for the hostname in /etc/hosts to find the external hostname: # grep glory1 /etc/hosts 16.123.123.61 192.168.3.1 3. glory1.example.com glory1-ext2 glory1 glory1-adm Use the external hostname shown by /etc/hosts, glory1-ext1 in the example above, rather than the internal management hostname, glory1.
PAGE 40
Operating the system—Common tasks
PAGE 41
6 Viewing system status information Several exdsmgr commands allow you to view the following information about the configuration and status of your HP ExDS9100 Storage System: • Configuration, system, or status problems report • Server blade information • BladeSystem and interconnect details • Matrix state • Array information • LUN information • System information • Filesystem information • VNFS configuration details • HTTP service status information • Alert history information • Event logs • Firmware versi
PAGE 42
• Storage—Issues connected with storage blocks (arrays) or the SAS fabric connecting servers to storage blocks • Firmware—Checks whether all components are at the correct firmware levels and also reports inconsistencies between the firmware levels on different servers or arrays.
PAGE 43
Viewing server information The ExDS> show server command provides information on the state of servers: Table 1 explains server states: Table 1 Server states State Description booting The power to the server has just been turned on, and the server is booting. This is a temporary state. If the server does not respond after three minutes, it will be marked with the status down. not-resonding The server has not responded for 20 seconds.
PAGE 44
The Integrated Management Log (IML) records hardware errors that have occurred on a server blade. The show server command shows the total number of critical and caution events in the IML. You can view or clear the events using the hpasmcli(4) command. Use the command ExDS> show server n (where n is the server name) to see information about a specific server.
PAGE 45
Result (screen 2) 9100 Extreme Data Storage System administration guide 45
PAGE 46
Viewing blades information The ExDS> show blade_chassis command shows BladeSystem information such as bay number, type, part number, serial number, name, and ROM version, as well as interconnect details.
PAGE 47
Viewing Matrix state The exdsmgr show matrix command shows the state of the Matrix. The exdsmgr show matrix all command shows cluster state information that could help debug a system. For example, the all option shows export path errors that would not have generated an automatic alert otherwise, and would not have been visible with the show matrix command alone.
PAGE 48
Viewing array information The ExDS> show array command shows information on all of the arrays in the system. The ExDS> show array n (where n is the array number) command shows information on a specific array in the system.
PAGE 49
9100 Extreme Data Storage System administration guide 49
PAGE 50
Table 2 explains disk drive states: Table 2 Disk drive states State Description ok Drive is working normally. Removed Drive is not present (or is so badly failed that it is not detected by the controllers). Failed Drive is failed and cannot be used by the RAID logic used by the controllers. Predict-fail Drive is working normally but the SMART self-test logic on the drive predicts that the drive will fail in the near future.
PAGE 51
Viewing LUN information The ExDS> show luns command shows information on all LUNs in the system. The Role attribute indicates how the LUN is used. Table 3 explains LUN roles: Table 3 LUN roles State Description cfg Reserved for future use. mp LUN is a membership partition (used by Matrix software to manage its cluster). Normally, a system has three membership partitions - each on a different array.
PAGE 52
State Description Degraded One or two disks have failed. The RAID ADG logic is being used to continue operations; however, there is no redundancy anymore. You should take action as soon as possible to replace the failed disk drives. See Replacing storage block hard disk drivefor more information. Disconnected Some or all of the physical disks associated with the logical disk are no longer connected to the ExDS9100cc controller.
PAGE 53
Viewing system details The show system command provides details of a system: Viewing filesystem information The exdsmgr show filesystem command provides a summary (name, size, used, and available space information) of all successfully created filesystems.
PAGE 54
The ExDS> show filesystem detail command lists filesystems' names, capacity, the constituent psv(s), the available space, the servers on which they are mounted, and the mount flags on each server: 54 Viewing system status information
PAGE 55
The ExDS> show filesystem name where name is the filesystem name, command shows the details for a specific filesystem: 9100 Extreme Data Storage System administration guide 55
PAGE 56
Viewing firmware information The ExDS> show firmware command shows the versions of various system components: 56 Viewing system status information
PAGE 57
Viewing alert history The exdsmgr show alert history command shows a history of which alerts have been sent: 9100 Extreme Data Storage System administration guide 57
PAGE 58
Viewing system status information
PAGE 59
7 Managing data Creating a filesystem The exdsmgr create filesystem command creates PSFS filesystems. The create filesystem command works as follows to create a filesystem: • If not otherwise specified, the exdsmgr create filesystem command will create two filesytems, each using 4 LUNs. Each resulting filesystem uses 29 TB of space. • When you specify a filesystem size, the command matches the requested filesystem size against the available (free/unused) LUNs. For a filesystem of 7.
PAGE 60
8 58.02 TB Filesystem creation examples The following command creates filesystems on array 3. Since no mount points or sizes were specified, the command will create two filesystems, each of 29 TB and mount them on /mnt/exds_3_1 and /mnt/exds_3_2.
PAGE 61
NOTE: In the following example, filesystem EXDS_3_2 is a partially created filesystem. Deleting a filesystem Use the exdsmgr delete filesystem command to delete a filesystem and perform the following tasks: • • • • Unmounts the filesystem. Deletes the PSFS filesystem. Deletes the dynamic volume (psv). Un-imports the psd devices. NOTE: The exdsmgr delete filesystem command does not remove the filesystem from the VNFS configuration (that is, /etc/exports).
PAGE 62
# exdsmgr mount device=psv5 where psv5 is the filesystem label. This mounts the filesystem on all servers using the existing mount options that were used when the filesystem was created. The mount command queries the system to determine what mount options were previously used for the filesystem in question and then reuses those options without modification.
PAGE 63
• Mount point—The command changes the persistent mount associated with the filesystem on the specified servers. • The purpose of this command is not to have a filesystem mounted at a different mountpoint on different servers. It allows an administrator to change the mountpoint on all servers OR change the mountpoint on a subset of servers, mounting the filesystem with the new mount point on only those servers and leaving the filesystem unmounted on the remaining servers.
PAGE 64
• An IP address (for example, 10.10.10.70) • An FQDN (for example, www.acme.com) • specifies the export options for the clients • Several parameters are allowed and must be separated by a space. • There must not be any white space in . • Optional parameter. If not specified, the default export options are as shown below in the left column. • If specified, specifies the export options for the clients.
PAGE 65
Viewing a VNFS configuration The exdsmgr show vnfs command shows details of the existing VNFS configuration. Parameters Network=eth Mandatory parameter vip = Optional parameter. If not specified, the status of all VIPs will be displayed. If specified, the output is restricted to the specified VIP. Example—exdsmgr show vnfs network=eth2 Example—exdsmgr show vnfs network=eth2 vip=192.168.9.
PAGE 66
commands to modify the specified export group. However, if the addserver or removeserver actions are used, exdsmgr will restore the virtual address pattern to a balanced set, as described above. Parameters • action= • Specifies the action to take. The action is one of the following.
PAGE 67
• removeserver • Removes a server from the specified export group. The removal is done so as to maintain a balanced set of backup hosts across the members. • Has the following syntax: modify vnfs action=removeserver network=eth vip= server= • addfilesystem • Adds the specified filesystem to the specified export group.
PAGE 68
3. Run the mx exportgroup update command to reload the new options as shown in the following example: # mx exportgroup update --exports /tmp/newexports exds_expg_default Deleting a VNFS configuration Use the delete VNFS command to delete a specified exportgroup and all of its associated VNFSes.
PAGE 69
Configuring and using Samba You can configure Samba and the HP ExDS9100 system to provide failover support for virtual Samba servers. NOTE: Use the configuration steps only if you need to create a failover Samba configuration. Otherwise, you can use traditional methods to configure Samba, such as by using the /etc/samba/smb.conf file. Samba provides a set of UNIX applications that understand the Server Message Block (SMB) protocol, which is the networking protocol used by Microsoft Windows products.
PAGE 70
The backup server for one virtual Samba server can be the primary server for another virtual server. Also, a server blade can broadcast multiple PSFS filesystems. The only restriction is that each PSFS filesystem can be associated with only one virtual Samba server. A virtual host IP address used by Samba cannot be used as a VNFS or VHTTPD virtual host. Use of the configuration files The Samba smb.conf file determines what is shared and how it is shared. The Samba solution breaks smb.conf into an smb.
PAGE 71
to this configuration.) This avoids Master Browser elections, which can consume significant amounts of bandwidth. • The Samba options described in this guide have been tested by HP. Samba has many other configuration options, but those options have not been thoroughly tested by HP in the clustered Samba environment. If they are suited to your Samba environment, they can be used.
PAGE 72
Because this is the first time that the mxfs_cifs RPM is installed, you can ignore the message telling you to reboot the servers. Step 3 — Create /var/mxso/samba/conf directory The Samba configuration files should be the same on all servers. As a convenience, you can put the configuration files into /var/mxso/samba/conf directory and make symbolic links as described in the next section.
PAGE 73
NOTE: The HP ExDS system automatically generates the smb.conf file when it starts the Samba services via the smb_meth script described below. The smb.conf file is created from smb.default when no virtual Samba servers are active on the server and should not be edited directly. Do not use any GUI tools such as YaST to configure Samba, because they will modify and overwrite the smb.conf file. Templates for the smb.default and /etc/samba/ smb.conf.
PAGE 74
The following example shows the smb.conf.grp1 file. This virtual server is accessed via virtual host 99.12.10.205. The virtual server is named grp1 and three shares are exported. The data1 share exports the /mnt/exds_1_1 filesystem. The user1 and user2 shares are subdirectories of the / mnt/exds_1_2 filesystem. The file includes the following parameters: • interfaces. Required for Samba high availability.
PAGE 75
Step 5 — Set Samba user passwords If necessary, set each Samba user's password by using the smbpasswd command. A Samba user account will not be active until a Samba password is set for it. To add a user, use the following command syntax: smbpasswd -a where is the user being added. Do this on one server, then move the files to /var/mxso/samba/conf and create links as described in the next section.
PAGE 76
share. The first server listed is the primary server. The application ‘CIFS’ is simply a label, it will appear in mxconsole. If you are using another network other than ext2, change the names as appropriate. Step 8 — Configure a CUSTOM service monitor This monitor watches the Samba service on the primary server and controls Samba start and stop operations when the virtual host fails over to a backup server.
PAGE 77
Creating VHTTPD The exdsmgr create vhttpd command creates a default balanced set of virtual hosts for Apache services. When the exdsmgr create vhttpd command finishes, the HP ExDS9100 system serves a simple place-holder Web page on every virtual host address. See Customizing HTTP for more information. Parameters • network=eth • Mandatory parameter (must not be the management network). This network must have been configured by the exdsmgr reconfigure system command.
PAGE 78
Example Modifying VHTTPD The exdsmgr modify vhttpd command allows you to modify the existing default vhttpd configuration that was created using the exdsmgr command. Parameters • action= The following actions are supported: • addserver • removeserver • network=eth • vip= • server = Actions The following actions are supported: • addserver • Adds a virtual host IP address to the network interface for the specified server.
PAGE 79
Parameters • network=eth • Mandatory parameter Example The following removes all virtual host IP addresses that exist on eth2: # exdsmgr delete vhttpd network=eth2 Managing Apache configuration options The HP ExDS9100 includes a configured Apache server running on every server. The /etc/httpd/ conf/httpd.conf file is actually a symbolic link to /var/mxso/httpd/conf/httpd.conf. This file is located on the utility filesystem.
PAGE 80
Managing data
PAGE 81
8 Verifying and maintaining the system Managing e-mail alerts Alert filter overview An alert filter comprises the following: • Name—This is a convenient name used to identify the filter when modifying or deleting it. • Enabled status—An alert filter can be disabled.
PAGE 82
If you are receiving too many e-mails, you can change the throttle period of an alert filter. You can also disable the alert filter, although this means you will not be aware of events occurring on the system. Viewing pre-defined filters A number of pre-defined filters are installed by default in the system. To see the default filters, enter the command show alert filters. Creating e-mail alert filters To create an alert filter, enter the command # exdsmgr create alert filter.
PAGE 83
Viewing and clearing the Integrated Management Log (IML) The IML logs hardware errors that have occurred on a blade. The show server command shows the total number of critical and caution events in the IML. View or clear events using the hpasmcli(4) command.
PAGE 84
Verifying and maintaining the system
PAGE 85
9 Changing system parameters IMPORTANT: To avoid unintended consequences, HP recommends that you perform the procedures in this chapter during scheduled maintenance times. Passwords Changing hardware passwords Use the exdsmgr reconfigure system menu to change the OA, iLO, and Virtual Connect passwords. The password must be fewer than 15 characters in length. To change the iLO password, first shut down all servers except the server where you run the exdsmgr reconfigure system command.
PAGE 86
These files are purely for installation demonstration purposes. You are expected to edit the httpd.conf file to suit your application. Also, you can replace /etc/httpd/conf/httpd.conf with a link to a different shared filesystem (or even revert to a server-private file in /etc/httpd/conf). NOTE: If you modify the DocumentRoot directive, make sure there is an index.html file with appropriate permissions. When you restart Apache on every server, if the index.
PAGE 87
NOTE: You cannot change the IP addresses of an interface if there are any virtual host IP addresses hosted on that network. You can use this procedure to configure a network interface for the first time or to reconfigure an interface to use a different IP address or netmask. Use the exdsmgr reconfigure system command to change the IP address or netmask of eth2, eth3, eth4, or eth5 as follows: 1. Run the exdsmgr reconfigure system command. 2.
PAGE 88
Manually configuring network interfaces Instead of using the exdsmgr reconfigure system command to configure a network interface, you can manually configure the network interfaces. This can be used to create a bonded network interface. To manually configure a network interface, use then following procedure: 1. Use the exdsmgr reconfigure system command and set the IP address to None. 2. Manually configure the appropriate files (/etc/modprobe.conf and /etc/sysconfig/ network-scripts) on all servers. 3.
PAGE 89
Unless needed for a specific purpose, the general policy is to disallow traffic on all ports. The HP ExDS9100 firewall prevents unnecessary network traffic on the HP ExDS network infrastructure. However, it is not intended as a replacement for normal security procedures.
PAGE 90
1. Determine the rule number of the http rule by running the iptables list command as follows: # iptables -L MXSO-External-Filter This produces output like: Counting down the rule set, the http rule is rule number 3. 2. Having identified the rule to be updated, it can be replaced with the rule that limits requests to those with a source address on the 16.123.8 subnet with: # iptables -R MXSO-External-Filter 3 -p tcp -m tcp -s 16.123.8.0/24 -dport 80 -j ACCEPT # service iptables save 3.
PAGE 91
Customizing mySQL In this release it is not possible to use mySQL on an HP ExDS9100 system. If such support is required, contact HP Services for support. Installing RPMs Use the install update command to install or upgrade an RPM on the entire system. CAUTION: Do not register an HP ExDS9100 system with RedHat Update Agent (up2date). CAUTION: The install update should only be used to install RPMs that have been supplied by or approved by HP for use on an HP ExDS9100 system.
PAGE 92
2. Copy the RPM file to a convenient location. For example, if the firmware is called mxso-firmware-1.1-1234.rpm, copy it as shown in the following example: glory1# scp sys1:/stage/mxso-firmware-1.1-1234.rpm /tmp 3. Run the exdsmgr install update command: glory1# exdsmgr install update /tmp/mxso-firmware-1.1-1234.rpm 4.
PAGE 93
• /etc/sysconfig/iptables • /etc/resolv.conf /etc • /opt/polyserve/disable_dashboard • /etc/my.cnf • /etc/ntp/step-tickers 3. Run the delete server command: # exdsmgr delete server 8 where server 8 is the server being reinstalled. 4. Run the install server command: # exdsmgr install server 8 5. Except for the files mentioned in step 2 above, any customizations made to your system since it was originally installed are not present on the newly installed server.
PAGE 94
Changing system parameters
PAGE 95
10 Upgrading the HP ExDS9100 WARNING! Before performing any of the procedures in this chapter, read the important warnings, precautions, and safety information in Appendix D and Appendix E. Adding new server blades IMPORTANT: Use only an HP ExDS9100-specific server blade. Do not try to install a standard server blade; otherwise, the install server command fails with an invalid blade error message, and it will not boot.
PAGE 96
3. Install the server blade. 4. Run the exdsmgr install server n command, where n is the bay number (which is also the server blade number). For example, for a server blade in bay 9, the command would be: # exdsmgr install server 9 5. 6. Reboot the server blade installed in step 4. If you use the exsd_exgp_default export group, add an additional virtual host IP address. For example, if the virtual host IP address is 16.123.123.
PAGE 97
9. If you configured Samba, create symbolic links in /etc/samba as described in Configuring and using Samba on page 69. 10. If you made any other customizations to other servers, you may need to apply them to the newly installed server. Adding storage blocks Additional storage blocks can be added to an existing system while the system is still running. One or more storage blocks can be added at a time, up to the point where the system has the maximum number of storage blocks.
PAGE 98
Removing server blades CAUTION: Do not remove a server blade from the blade enclosure without first powering it off and waiting for two minutes. If you remove a “live” server blade, the Matrix could lock up because it cannot fence the removed server blade. If you inadvertently lock up the Matrix this way, you can recover by using the mx server markdown command. Only use this command when you are certain that the server blade is powered down or removed. To remove a server blade: 1.
PAGE 99
storage command, the array will be re-discovered and appear with a different array number in the system database. If this happens, use the exdsmgr delete array command again. CAUTION: Ensure that you remove the correct storage block. Removing the wrong storage block could result in data that is inaccessible. Adding Virtual Connect modules to bays 7 and 8 If you require additional network connectivity, you can add Virtual Connect (VC) modules to bays 7 and 8.
PAGE 100
7. 100 Repeat this process for the other server blades.
PAGE 101
11 Replacing components in the HP ExDS9100 Storage System Customer replaceable components WARNING! Before performing any of the procedures in this chapter, read the important warnings, precautions, and safety information in Appendix D and Appendix E. IMPORTANT: To avoid unintended consequences, HP recommends that you perform the procedures in this chapter during scheduled maintenance times.
PAGE 102
permits. If assistance is required, you can call the HP Technical Support Center, and a technician will help you over the telephone. The materials shipped with a replacement CSR part specify whether a defective part must be returned to HP. In cases where it is required to return the defective part to HP, you must ship the defective part back to HP within a defined period of time, normally five (5) business days.
PAGE 103
• T-15 Torx screwdriver • 4-mm flat-blade screwdriver • Phillips screwdriver Additional documentation The information in this section pertains to the specifics of the HP ExDS9100. For detailed component replacement instructions, see the following documentation which is available at http://www.hp.
PAGE 104
1. 2. 3. Connect the TFT Monitor/Keyboard to the first server blade. Power off all server blades. Power on the first blade. The server blade boots to single-user mode. 4. 5. Log in using the TFT Monitor/Keyboard. Delete the /opt/hp/mxso/etc/location file as follows: # rm /opt/hp/mxso/etc/location 6. Run init as follows: # init 3 7. 8. The server should boot fully and you can log in to the first server blade normally. Boot the remaining server blades.
PAGE 105
IMPORTANT: Only use an HP ExDS9100-specific server blade to replace a server blade in an HP ExDS9100 system. If you use a standard server blade, the server blade will not complete the boot process and remains in single-user mode. IMPORTANT: Before replacing a server blade or server blade system board (also called a motherboard), contact HP technical support. The HP ExDS9100 server blade product has a unique product ID. HP technical support will give you the appropriate product ID to use.
PAGE 106
e. f. Select Serial Number. Enter a serial number. CAUTION: Do not use the original server blade serial number. Use the serial number of the system board or any other serial number. If you use the original serial number, the HP ExDS9100 system software does not detect that the system board has been replaced and does not configure the server blade appropriately. g. 8. This is a convenient time to set the product ID. Contact HP technical support for the appropriate product ID.
PAGE 107
Replacing both disk drives The “system disk” on an HP ExDS9100 server blade comprises a logical RAID 1disk that is mirrored over two physical SFF disk drives in the server blade. As long as one drive continues to operate, the server blade can operate. However if both disk drives have failed, the system disk is lost, and the server must be reinstalled. To reinstall a server: 1. 2. 3. Remove both disk drives. Insert two replacement drives.
PAGE 108
8. Run the exdsmgr syscheck command to validate that all servers are the same and at the correct minimuml revision. See the HP BladeSystem c7000 Enclosure Maintenance and Service Guide for more information. Replacing the Ethernet Virtual Connect (VC) module (bay 1 or bay 2) To replace a VC module: 1. 2. 3. 4. 5. 6. Disconnect the network connections into the Ethernet Virtual Connect (the module in bay 1 or 2). Remove the VC module. Replace the VC module.
PAGE 109
IMPORTANT: A replacement SAS switch may contain firmware that is incompatible with the existing system software and firmware. You must follow the procedures described in this section to update firmware and where appropriate zone the switch. 1. Disconnect SAS cables, noting which cable goes to which port. 2. Remove the switch. 3. Replace the switch. 4. Connect to the OA using the HP ExDS9100 or Administrator username. For example, on a system called glory, ssh as follows: # ssh glory-mp -l exds 5.
PAGE 110
8. Update the firmware depending on the firmware currently installed on the replacement SAS Switch. If the firmware is 1.8.x.x, follow these steps: 1. Run the flash file=URL command on the switch to reload the firmware. The URL is: http://:9070/fw/SASsw_mp_fw where is the IP address of the exdsadmin virtual host. Look for the exdsadmin entry in /etc/hosts. On many systems, the exdsamin address is 192.168.0.1, so the command might be: flash file=http://192.168.1.
PAGE 111
9. Reconnect the SAS cables. 10. Determine whether the running firmware is 1.8.x.x or 2.x.x.x as explained earlier in this procedure. Exit from the OA CLI (ireturn to the shell prompt). If the firmware is 1.8.0.0, no further action is needed. If the firmware is 2.x.x.x, Zone the SAS Switch using the following command: exds_zone_sas -z -s –ic –u exds –p where is the the bay (3 or 4) of the replaced switch and is the OA password of the exds user.
PAGE 112
#exdsmgr shutdown server where is the server blade number. 2. 3. 4. 5. Remove the server blade. Replace the P700m. Replace the blade in the original blade bay. The server automatically boots. Run exdsmgr show firmware and exdsmgr syscheck to validate the firmware version. 6. If the firmware is not correct, see Updating BIOS, iLO, E200i, and P700m firmware.
PAGE 113
• The exds_stdiag reports that disks "have been ejected" from a logical disk – this indicates that the disk drive is failed. The command also reports "SMART predicts failure" for disks in the predictfail state. The following show a small section of an exds_stdiagreport: disk problems * box 2 drive [12] missing or failed on storage block SGA90100CV disk status problems * SMART predicts failure on HP 1000.
PAGE 114
replacing a failed disk, one LUN will be rebuilding while the others wait until the rebuild finishes. The following output from the exds_diag command shows an example lun status problems * RECOVERY_INPROGRESS on 1GB ADG lun 01 of SGA742000T * DEGRADED on 1GB ADG lun 02 of SGA742000T * DEGRADED on 23GB ADG lun 03 of SGA742000T * DEGRADED on 2210GB ADG lun 04 of SGA742000T For other data LUNs, only one LUN is affected by a disk failure, so you should see then go to recovery in progress immediately.
PAGE 115
6. 7. Insert the new controller in to the HP ExDS9100c chassis, but do not slide it fully in. Attach the two SAS expansion cables that connect the HP ExDS9100cc to the I/O controllers on the HP ExDS9100cx enclosure, ensuring that they are connected in the original places. 8. Push the controller fully into the chassis so it engages. 9. Reattach the SAS cable that connects the HP ExDS9100cc to the SAS switch in the c-Class blade enclosure. This is plugged into port 1. 10.
PAGE 116
See the HP StorageWorks 9100c Extreme Data Storage System user guide for more information. Replacing the HP ExDS9100c fan The system can operate using one fan. You can hot swap the fan. 1. 2. Remove the fan module. Insert a new fan module. NOTE: Removing a fan module significantly changes the air flow within the enclosure. Both fan modules must be installed for the enclosure to cool properly. Do not remove both fans simultaneously with the enclosure powered on.
PAGE 117
14. Run the exdsmgr syscheck command to validate that the firmware level is correct and that no other failures have occurred. Replacing the HP ExDS9100cx I/O module IMPORTANT: You must change the firmware of a replaced I/O module; therefore, schedule system downtime of approximately one hour to perform this procedure. There are four I/O modules in an HP ExDS9100cx chassis—two I/O modules (primary/secondary) for each of the drawers: two on the left, two on the right.
PAGE 118
1. Stop I/O to the affected storage block by pausing all filesystems except the utility files ystem (/ var/mxso): a. Run the following command: exdsmgr show luns Note the used by fields of LUNs on the affected array having a role of “data.” b. Run the following command: exdsmgr show filesystems c.
PAGE 119
8. Change the firmware of the I/O modules to the version included in the ExDS system. a. Identify the serial number of the array using the command: # exdsmgr show array b. Run the ExDS9100cx I/O module firmware update command: # /opt/hp/mxso/firmware/exds9100cx_scexe –s The command will pause to gather the system configuration which can take a several minutes on a large system. It then displays the serial number of an array and asks if it should be updated.
PAGE 120
11. Resume I/O on the filesystems that were paused in step 1 by running the following command on each filesystem that was suspended, from the same server on which the suspend command was run: # psfsresume filesystem-path where filesystem-path is the full path to the filesystem mount point on the server. NOTE: The filesystem resume command must be run on a server that has the filesystem mounted.
PAGE 121
• HP StorageWorks 9100 Extreme Data Storage System wiring diagrams for base cabinet configurations • HP StorageWorks 9100 Extreme Data Storage System wiring diagrams for expansion cabinet configurations 9100 Extreme Data Storage System administration guide 121
PAGE 122
Replacing components in the HP ExDS9100 Storage System
PAGE 123
12 Upgrading firmware and software IMPORTANT: Any time syscheck or exds_stdiag reports that your HP ExDS9100 Storage System has the wrong firmware installed, use the instructions in this section to upgrade to the correct firmware. Firmware update summary When the HP ExDS9100 system software is first loaded, it automatically updates the firmware for some components. For server-specific firmware (for example, P700m, but not OA), the exdsmgr install server command also automatically updates the firmware.
PAGE 124
SAS switch management (Solex) firmware Update RPM. Run online, then update using OA CLI. Reset SAS switches one by one. System remains operational. Storage block disk drive firmware Update RPM. Run online. Requires complete system shutdown.Note: For individual out-of-revision drives, return to HP. Locating firmware Obtain the firmware by one of the following methods: • HP technical support might send you an updated mxso-firmware RPM. This installs firmware in / opt/hp/mxso/firmware.
PAGE 125
The HP ExDS9100 update mechanism includes the firmware in the mxso-firmware RPM. This contains the appropriate version of all firmware needed at the time the RPM was made. However, there could be more recent updates available from www.hp.com. HP Support will tell you which mechanism is appropriate for you. HP ExDS9100 update mechanism 1. 2. Download the mxso-firmware RPM. Update the RPM on all servers using the exdsmgr update command. The update is automatically installed the next time you boot a server.
PAGE 126
Upgrading all Virtual Connect modules The Virtual Connect firmware upgrade process updates all Virtual Connect modules at once. You must shutdown all servers except one to perform the update. In addition, you will lose network connectivity during the update process. 1. Install the firmware onto the system in one of two ways depending on the source of the firmware: • HP ExDS9100 mxso-firmware RPM. Install the mxso-firmware RPM on all servers using the exdsmgr install update command.
PAGE 127
3. 4. 5. Use the exdsmgr show array command to verify that all storage units are online. In particular, make sure both controllers in every HP ExDS9100c chassis are online. If the path to any controller is "none," the controller might not be updated. Follow the process in Shutting down to a single server to shut down all servers except for the first server. Shut down the first server to single user mode. Run the update utility (or utilities) located in /opt/hp/mxso/firmware.
PAGE 128
shutdown -h now 4. 5. 6. Power cycle the blade chassis. Press the power button to boot server 1. Log in and run the following command: # exds_stdiag –v | grep SWH | grep -v P700 You should see 4 lines such as the following. In this example, the firmware version is 1.20. 1.20 on HP.3G.SAS.BL.SWH in 4A (min 1.20) 1.20 on HP.3G.SAS.BL.SWH in 3A (min 1.20) 1.20 on HP.3G.SAS.BL.SWH in 4B (min 1.20) 1.20 on HP.3G.SAS.BL.SWH in 3B (min 1.20) 7. 8.
PAGE 129
13 Troubleshooting General troubleshooting steps 1. Run the exdsmgr syscheck command. 2. Run the exds_stdiag storage diagnostic utility. 3. 4. Evaluate the results. To report a problem to HP technical support, see Escalating issues. Viewing support information To see HP ExDS9100 support contact details, enter the ExDS> show support command, or see the HP technical support section in this guide. Escalating issues The HP ExDS9100 escalate tool produces a report on the state of the system.
PAGE 130
Connecting to iLO console Use the mxso_ilo command to connect to the iLO console. For example, to connect to a server’s console, use the following command: # mxso_ilo glory2 vsp To connect to the remote console (for example, to access the RBSU settings) use the remcoms option: #mxso_ilo glory2 remcoms To connect to iLO command line, use the ilo option: # mxso_ilo glory2 ilo To see other available options, use the --help option to print a help message.
PAGE 131
7. 8. Press Enter to save. Press Ctrl-A, then m to reinitialize the modem. You are now connected to the serial interface of the OA. 9. Press Enter. 10. When you are finished, press Ctrl-A, then q to exit minicom. Accessing the Onboard Administrator (OA) via service port Each OA has a service port (this is the right-most Ethernet port on the OA). This allows you to use a laptop to access the OA command line interface.
PAGE 132
CAUTION: This can damage a system and make it impossible to operate. Use only if instructed by HP technical support. mysql> update mxso_servers set mxso_version=’junk’ where name=’glory1’; To delete records from a table (same warning): mysql> delete from mxso_hbas where hba=’PBACBA49VW15D9’; If you damage the database, you can attempt to restore it from backup. See Restoring a database backup. System log files Each server has the standard log files in /var/log.
PAGE 133
repair it using psfsck. However, if the underlying logical disk drive is failed, then this repair is impossible because the data is lost. Normally, the utility filesystem is based on an "adm" LUN on the first storage block. During normal operation, the HP ExDS9100 system software makes a backup copy of the utility filesystem and copies it to a filesystem on one of the "admspare" LUNs.
PAGE 134
• An email alert. • In the X9000 management console, the logical volumes in the affected capacity black show a warning. • The amber fault LED on the X9700c controller is flashing. • The seven-segment display shows an H1, H2, C1, or C2 code. The second digit represents the controller with a problem. For example, H1 indicates a problem with controller 1 (the left controller, as viewed from the back).
PAGE 135
2. Check the seven-segment display and note the following as it applies to your situation: • If the seven-segment display shows “on,” then both X9700c controllers are operational. • If the seven-segment displays shows “on” but there are path errors as described earlier in this document, then the problem could be with the SAS cables connecting the X9700c controller to the SAS Switch in the blade chassis. Replace the SAS cable and run the exds stdiag command, which should report two controllers.
PAGE 136
5. At this stage, you have identified that the problem is with an X9700cx I/O module. Determine if the fault lies with the top or bottom modules. For example, if the seven-segment display shows C1 02, then the fault may lie with one of the primary (top) I/O modules. 6. Stop I/O to the affected storage block by pausing all filesystems except the utility files ystem (/ var/mxso): a. Run the following command: exdsmgr show luns Note the used by fields of LUNs on the affected array having a role of “data.
PAGE 137
7. Examine the I/O module LEDs. If an I/O module has an amber LED: a. 8. Replace the I/O module as follows: a. Detach the SAS cable connecting the I/O module to the X9700c controller. b. Ensure that the disk drawer is fully pushed in and locked. c. Remove the I/O module. d. Replace with a new I/O module (it will not engage with the disk drawer unless the drawer is fully pushed in) e. Re-attach the SAS cable. Ensure it is attached to the “IN” port (the bottom port). b.
PAGE 138
9. If the seven-segment display now shows “on,” run the exds_stdiag command and validate that both controllers are seen by exds_stdiag. 10. If the fault has not cleared at this stage, there could be a double fault (that is, failure of two I/O modules). Alternatively, one of the SAS cables could be faulty. Contact HP Support to help identify the fault or faults. Run the exds_escalate command to generate an escalate report for use by HP Support as follows: # exds_escalate 11.
PAGE 139
14. Resume I/O on the filesystems that were paused in step 1 by running the following command on each filesystem that was suspended, from the same server on which the suspend command was run: # psfsresume filesystem-path where filesystem-path is the full path to the filesystem mount point on the server. NOTE: The filesystem resume command must be run on a server that has the filesystem mounted.
PAGE 140
Array 3 Controller 1 has no path from servers glory3 Array 3 Controller 2 has no path from servers glory3 • No controllers are seen when you run the exds_stdiag command. Sometimes this happens to all servers in the system. The underlying causes of these problems differ. However, the recovery process is similar in all cases. Do not replace the HP P700m until you have worked through the process described here.
PAGE 141
8. Wait until all sever-segment displays show "on" then power on all server blades. 9. If the HP P700m still cannot access the fabric, replace it on affected server blades and run exds_stdiagagain. Management database is inaccessible according to exdsmgr command (or ExDS monitoring daemons) If the exdsmgr command (or HP ExDS monitoring daemons) reports that the management database is inaccessible and this situation persists for several minutes, then the admin service may have been disabled.
PAGE 142
ExDS9100c seven-segment display shows an H1, H2, C1, or C2 code If the seven-segment display of an ExDS9100c enclosure shows an H1, H2, C1 or C2 error code this indicates that one of the controllers has been halted. The amber fault LED of one of the controllers will also be lit. The usual cause is that an ExDS9100cx I/O module has failed. In this situation is is normal for the ExDS9100cc controller that is attached to the I/O module to halt.
PAGE 143
3. 4. 5. 6. 7. 8. Before rebooting any servers, determine whether the system is otherwise operating normally. If the mx alert status command is not reporting problems with other virtual hosts or other filesystems, then the system can continue operation as the /var/mxso filesystem and the database are not needed for file I/O operations, NFS file serving, or HTTP serving. If these are working normally, you can postpone any action to correct the database access until a later time.
PAGE 144
SAS switch appears to have 169.254.0.x address The OA may miss-report the SAS switch(s) management IP address as being on the 169.254.0 network. You can see this when running the exsdsmgr show blade_chassis command. The SAS switch continues to operate as normal and in fact is using its originally configured IP address.
PAGE 145
6. If necessary repeat the process from step 3 for the other SAS Switch Degraded blade server/Power PIC After a blade server blade or motherboard replacement, the blade slot may show a degraded state (as seen in the exdsmgr show blade_chassis command) and the Insight display on the blade chassis may show an error message indicating that the power PIC module has outdated or incompatible firmware. If so, you can update the PIC firmware as follows: 1. Log on to the server. 2.
PAGE 146
HP ExDS9100c enclosure front panel fault ID LED is amber If the HP ExDS9100c enclosure fault ID LED is amber, check to see if the power supplies and controllers are amber. If they are not, wait until a suitable time and power cycle the storage block. In the meantime, the enclosure fault LED can be ignored. If the power supplies and controllers are amber, see the HP StorageWorks 9100c Extreme Data Storage System user guide for troubleshooting steps.
PAGE 147
Replacement disk drive LED is not illuminated green When a disk drive is replaced and the LUN is rebuilt, the online/activity LED on the replacement disk drive might not be illuminated green. However, activity on the disk will cause the online/activity LED to flicker green. Note that a disk drive could be in use even if the online/activity LED is not illuminated green. IMPORTANT: Do not remove a disk drive unless the fault/UID LED is amber.
PAGE 148
Troubleshooting
PAGE 149
14 Diagnostic tools The exds_stdiag utility The exds_stdiag utility probes the SAS storage infrastructure attached to an HP ExDS9100 system. The utility runs on a single server. Since the all the SAS fabric is connected together it means that exds_stdiag can access all pieces of storage data from the server where it runs. Having probed the SAS fabric the exds_stdiag utility performs a number of checks including: • Checks there is more than one path to every disk and LUN.
PAGE 150
• Reports missing or failed NICs in server blades Sample output exds_netperf The exds_netperf tool measures network performance. The tool measures performance between a client system and the HP ExDS9100 system. Run this test when the system is first installed. Where networks are working correctly, the performance results should match the expected link rate of the network, that is, for a 1 GB link, expect about 90 MB/s. You can also run the test at other times to determine if degradation has occurred.
PAGE 151
# exds_netperf --serial --server “16.123.123.1 16.123.123.2” • On a client host, run exds_netperf in parallel mode, as shown in the following example. In this example, hosts blue and red are the tested clients (exds_netperf itself could be one of these hosts or on a third host): # exds_netperf --parallell \ --server “16.123.123.1,16.123.123.2” \ --clients “red,blue” Normally, the IP addresses you use are the IP addresses of the host interfaces (eth2, eth3, and so on). You can use virtual host IP addresses.
PAGE 152
Diagnostic tools
PAGE 153
15 Support and other resources HP technical support For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: • Product model names and numbers • Technical support registration number (if applicable) • Product serial number • Diagnostic details—Run the exdsmgr escalate command to produce a diagnostic report (see Escalating issues for more information).
PAGE 154
• HP StorageWorks 9100c Extreme Data Storage System user guide—Describes how to install, administer, and troubleshoot the HP StorageWorks ExDS9100c. • Polyserve Matrix Server 3.5.1 administration guide • Polyserve Matrix Server 3.5.1 command reference • HP StorageWorks 600 Modular Disk System Maintenance and Service Guide—Describes removal and replacement procedures for the HP ExDS9100cx (also known as the HP StorageWorks 600 Modular Disk System).
PAGE 155
WARNING! Indicates that failure to follow directions could result in bodily harm or death. CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Rack stability Rack stability protects personnel and equipment.
PAGE 156
For more information about CSR, contact your local service provider, or see the CSR website: http://www.hp.com/go/selfrepair Product warranties For information about HP StorageWorks product warranties, see the warranty information website: http://www.hp.com/go/storagewarranty Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.
PAGE 157
A CLI command reference This appendix lists commands that can be used with the HP ExDS9100. The page number indicates the main page where the command is discussed. N/A indicates that the command is not specifically discussed in the guide, but is still available for use.
PAGE 158
Database commands Table 12 Database commands Command Page Create database_backup N/A Delete database_backup N/A Restore database_backup 132 Show database_backup 132 Filesystem commands Table 13 Filesystem commands Command Page Create filesystem 59 Delete filesystem 61 Modify filesystem 62 Show filesystem 53 Show filesystem detail 53 Show filesystem X 53 LUN commands Table 14 LUN commands Command Page Show LUN 51 Show LUN X 51 Matrix commands Table 15 Matrix commands Command Pa
PAGE 159
Command Page Show matrix detail N/A Show matrix devices N/A Show matrix monitors 34 Show matrix notifiers N/A Show matrix persistent_mounts N/A Miscellaneous commands Table 16 Miscellaneous commands Command Page Escalate 129 Help 31 Install update 91 Kill command X 31 Set attribute N/A Monitor command X 31 Scan macs N/A Show attribute N/A Show command X 31 Show firmware 56 Show license 38 Show log N/A Show log tail N/A Show software N/A Show support 129 Show versi
PAGE 160
Server commands Table 17 Server commands Command Page Boot server 30 Delete server 98 Discover server 104 Install server 30 Set server N/A Show blade_chassis 46 Show server 43 Show server X 43 Shutdown server 30 Storage commands Table 18 Storage commands Command Page Discover storage 98 Identify storage 25 System commands Table 19 System commands Command Page Syscheck 41 Show system 53 VHTTP commands Table 20 VHTTP commands Command Page Create VHTTP 77 160 CLI command re
PAGE 161
Command Page Delete VHTTP 78 Modify VHTTP 78 Show VHTTP 77 VNFS commands Table 21 NFS commands Command Page Create VNFS 63 Delete VNFS 68 Modify VNFS 65 Show VNFS 65 9100 Extreme Data Storage System administration guide 161
PAGE 162
CLI command reference
PAGE 163
B HP ExDS9100 specifications For specifications on the HP ExDS9100, see the HP StorageWorks 9100 Extreme Data Storage System QuickSpecs at http://h18006.www1.hp.com/products/storageworks/xtreme_9100/index.html. For specifications about a specific component in the system, see the documentation for that component.
PAGE 164
HP ExDS9100 specifications
PAGE 165
C HP ExDS9100 spare parts list Replacing components in the HP ExDS9100 Storage System explained how to replace some of the HP ExDS9100 components. The following tables list spare parts (both customer replaceable and non customer replaceable) for the HP ExDS9100 components. For a current spare parts list, see http:// partsurfer.hp.com/search.aspx. Spare parts are categorized as follows: • Mandatory—Parts for which customer self repair is mandatory.
PAGE 166
SPS-DOOR,REAR,10642,10KG2 385967-001 Mandatory SPS-HANDLE,REAR,10KG2 385975-001 Mandatory SPS-HARDWARE KIT,10KG2 385978-001 Mandatory SPS-PANEL,SIDE,10636,10KG2 385972-001 Mandatory SPS-PANEL,SIDE,10642,10KG2 385971-001 Mandatory SPS-RACK,BUS BAR & Wire Tray 457015-001 Optional SPS-RACK,UNIT,10642,10KG2 385969-001 Mandatory SPS-SHOCK PALLET,600MM,10KG2 385976-001 Mandatory SPS-SPS-STICK,ATTACH'D CBL,C13 419595-001 Mandatory SPS-STABILIZER,600MM,HVY,10KG2 389462-001 Mandatory SP
PAGE 167
SPS-STICK ATTACHD CBL C13 0-1F 358698-001 Optional SPS-STICK,4X FIXED,C-13,OFFSET 483915-001 Optional Table 24 AN541A—HP ExDS9100 Performance Chassis spare parts Description Spare part number Customer self repair SPS-BD, MID PLANE ASSY 414050-001 No SPS-BD,LCD Pass Thru Crd-Edge 432462-001 No SPS-BLANK, BLADE 414051-001 Mandatory SPS-BLANK, FAN 414052-001 Mandatory SPS-BLANK, INTERCONNECT 414053-001 Mandatory SPS-BLANK, ONBRD ADM 414054-001 Mandatory SPS-BLANK, ONBRD ADM 414054-0
PAGE 168
SPS-DIMM,4GB PC2-5300F,256Mx4, 467654-001 Mandatory SPS-DRV, HD,72GB SAS 2.5 DP 10 505608-001 Mandatory SPS-HARDWARE/PLASTICS, MISC 410296-001 Mandatory SPS-HARDWARE/PLASTICS, MISC 410302-001 Mandatory SPS-HEATSINK 410304-001 Optional SPS-PCA, HP BLc 5715S 4Port N 436011-001 Mandatory SPS-PROC,Harpertown 2.
PAGE 169
D Warnings and precautions Electrostatic discharge information See Electrostatic discharge. Grounding methods There are several methods for grounding. Use one or more of the following methods when handling or installing electrostatic sensitive parts: • Use a wrist strap connected by a ground cord to a grounded workstation or computer chassis. Wrist straps are flexible straps with a minimum of 1 megohm ±10 percent resistance in the ground cords.
PAGE 170
WARNING! Any RJ-45 receptacle marked with these symbols indicates a network interface connection. To reduce the risk of electrical shock, fire, or damage to the equipment, do not plug telephone or telecommunications connectors into this receptacle. WARNING! Any surface or area of the equipment marked with these symbols indicates the presence of a hot surface or hot component. Contact with this surface could result in injury.
PAGE 171
Rack warnings and precautions Ensure that precautions have been taken to provide for rack stability and safety. It is important to follow these precautions providing for rack stability and safety, and to protect both personnel and property. Follow all cautions and warnings included in the installation instructions. WARNING! To reduce the risk of personal injury or damage to the equipment: • Observe local occupational safety requirements and guidelines for heavy equipment handling.
PAGE 172
Device warnings and precautions WARNING! To reduce the risk of electric shock or damage to the equipment: • Allow the product to cool before removing covers and touching internal components. • Do not disable the power cord grounding plug. The grounding plug is an important safety feature. • Plug the power cord into a grounded (earthed) electrical outlet that is easily accessible at all times. • Disconnect power from the device by unplugging the power cord from either the electrical outlet or the device.
PAGE 173
CAUTION: To properly ventilate the system, you must provide at least 7.6 centimeters (3.0 inches) of clearance at the front and back of the device. CAUTION: When replacing hot-pluggable components in an operational HP ExDS9100, allow approximately 30 seconds between removing the failed component and installing the replacement. This time is needed to ensure that configuration data about the removed component is cleared from the system registry.
PAGE 174
Warnings and precautions
PAGE 175
E Regulatory compliance and safety Regulatory compliance identification numbers For the purpose of regulatory compliance certifications and identification, this product has been assigned a unique regulatory model number. The regulatory model number can be found on the product nameplate label, along with all required approval markings and information. When requesting compliance information for this product, always refer to this regulatory model number.
PAGE 176
• Reorient or relocate the receiving antenna. • Increase the separation between the equipment and receiver. • Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. • Consult the dealer or an experienced radio or television technician for help. Declaration of conformity for products marked with the FCC logo, United States only This device complies with Part 15 of the FCC Rules.
PAGE 177
WARNING! Use of controls or adjustments, or performance of procedures other than those specified herein, or in the laser product's installation guide, could result in hazardous radiation exposure. To reduce the risk of exposure to hazardous radiation: • 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.
PAGE 178
BSMI notice Japanese notice Korean notice (A&B) Class A equipment Class B equipment 178 Regulatory compliance and safety
PAGE 179
Safety Battery Replacement notice WARNING! The computer contains an internal lithium manganese dioxide, a vanadium pentoxide, or an alkaline battery pack. A risk of fire and burns exists if the battery pack is not properly handled. To reduce the risk of personal injury: • Do not attempt to recharge the battery. • Do not expose the battery to temperatures higher than 60˚C (140˚F). • Do not disassemble, crush, puncture, short external contacts, or dispose of in fire or water.
PAGE 180
Japanese Power Cord notice Electrostatic discharge To prevent damage to the system, be aware of the precautions you need to follow when setting up the system or handling parts. A discharge of static electricity from a finger or other conductor could damage system boards or other static-sensitive devices. This type of damage could reduce the life expectancy of the device.
PAGE 181
Waste Electrical and Electronic Equipment directive Czechoslovakian notice Danish notice Dutch notice 9100 Extreme Data Storage System administration guide 181
PAGE 182
English notice Estonian notice Finnish notice 182 Regulatory compliance and safety
PAGE 183
French notice German notice Greek notice 9100 Extreme Data Storage System administration guide 183
PAGE 184
Hungarian notice Italian notice Latvian notice 184 Regulatory compliance and safety
PAGE 185
Lithuanian notice Polish notice Portuguese notice 9100 Extreme Data Storage System administration guide 185
PAGE 186
Slovakian notice Slovenian notice Spanish notice 186 Regulatory compliance and safety
PAGE 187
Swedish notice 9100 Extreme Data Storage System administration guide 187
PAGE 188
Regulatory compliance and safety
PAGE 189
Index Symbols components replacing, A aborting commands, 31 ACU using hpacucli, 131 adding server blades, storage blocks, alerts overview, 27 Apache configuration options, 79 Array Configuration Utility using hpacucli, B backend commands, 30 battery failure in ExDS9100cc after replacement, BIOS firmware, 124 blade enclosure replacing, 103 booting ExDS9100, 34 booting server blades, 34 bugfix install, 91 C changing mount persistence, system parameters, hardware passwords, network parameters, 86 system par
PAGE 190
create alert filter command, create filesystem command, create vhttpd command, 77 create vnfs command , customer self repair, 155 D database backup restoring, 132 declaration of conformity, 176 delete alert filter command, delete filesystem command, delete vhttpd command, 78 delete vnfs command, 68 diagnostic tools, 149 disable alert filter command, disenable quotas, 62 disk drive replacement, ExDS9100c, 112 document conventions, 154 related documentation, 153 documentation HP website, providing feedback,
PAGE 191
filesystem creating, 59 deleting, 61 managing, 61 modify, 62 mounting, 61 overview, 27 quotas, 62 recovering from creation failure, unmounting, 61 firewall closing a port through MXSO-External Filter chain, concepts, 88 managing, 88 opening a port, 89 restricting a port to an IP, firmware BIOS, 124 E200i, 124 iLO, 124 locating, 124 OA, 125 Onboard Administrator, P700m, 124 SAS switch, 127 SAS switch management, 128 storage block, 126 update summary, 123 VC module, 126 Virtual Connect module, 126 G groundin
PAGE 192
NFS exports managing, 63 O OA accessing via serial port, 130 accessing via service port, 131 firmware update, 125 replacing, 107 Onboard Administrator accessing via serial port, accessing via service port, firmware update, 125 replacing, 107 P P700m firmware, 124 P700M apparent failure, P700m mezzanine card replacing, 111 performance charting colplot, 151 pmxs, 90 POST error messages, 133 Q quotas disable, 62 enable, 62 R rack stability warning, 155 reconfigure system command, recovering from filesystem
PAGE 193
server blades adding, 95 booting, 34 disk drive replacement, 106 motherboard replacing, 104 moving, 104 overview, 25 reinstalling, 92 removing, 98 replacing, 104 replacing both disk drives, swapping, 104 servers shutting down, 38 show alert filters command, show alert history command, show array command, 48 show blade_chassis command, 46 show filesystem command, 53 show firmware command, 56 show license command, 38 show lun command, 51 show matrix command, 47, 92 show server command, 43 show system command,
PAGE 194
W warning rack stability, 155 warnings loading rack, 171 weight, 170 Waste Electrical and Electronic Equipment directive, 181 Web services Apache configuration options, create VHTTPD, 77 delete VHTTPD, 78 managing, 76 modify VHTTPD, 78 show VHTTPD, 77 websites customer self repair, 155 HP , HP Subscriber's Choice for Business, 156 product manuals, 154 weight, warning, 170 194