hp storageworks xp disk array os configuration guide: ibm aixh10032. · hp storageworks disk array...

HP StorageWorks

Disk Array XP operating systemconfiguration guide: IBM AIXXP12000

XP10000

XP1024

XP128

This guide describes the requirements and procedures for connecting and configuring the XP family ofdisk arrays to work with an IBM system running the IBM AIX operating system.

Part number: A5951–96045Seventh edition: November, 2005

Legal and notice information

© Copyright 2003-2005 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent withFAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and TechnicalData 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. The only warranties for HP productsand 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 technicalor editorial errors or omissions contained herein.

Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

Disk Array XP operating system configuration guide: IBM AIX

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . 5About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Disk arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . 6HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Subscription service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Other HP web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Installation . . . . . . . . . . . . . . . . . . . . . . . 9Features and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Fibre Channel interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Device emulation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10SNMP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11RAID Manager command devices . . . . . . . . . . . . . . . . . . . . . . . 11Installation procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Install and configure the disk array . . . . . . . . . . . . . . . . . . . . . . . 13Setting the host mode for the disk array ports . . . . . . . . . . . . . . . . . . 13Setting the System Option Modes . . . . . . . . . . . . . . . . . . . . . . . 15Configuring the Fibre Channel ports . . . . . . . . . . . . . . . . . . . . . . 16

Fibre address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Fabric and connection parameter settings . . . . . . . . . . . . . . . . . . 17

Install and configure the host . . . . . . . . . . . . . . . . . . . . . . . . . 18Loading the OS and software . . . . . . . . . . . . . . . . . . . . . . . . . 18Installing and configuring the HBAs . . . . . . . . . . . . . . . . . . . . . . . 18

Supported HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18To verify that the FC6227 drivers are installed: . . . . . . . . . . . . . . 18To check the firmware level: . . . . . . . . . . . . . . . . . . . . . . 19To install the drivers using the AIX command line: . . . . . . . . . . . . . 19To install the drivers using SMIT: . . . . . . . . . . . . . . . . . . . . 19

Clustering and fabric zoning . . . . . . . . . . . . . . . . . . . . . . . . . 21Fabric zoning and LUN security for multiple operating systems . . . . . . . . . . . 22Connect the disk array . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Defining the paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Verifying host recognition of disk array devices . . . . . . . . . . . . . . . . . . 24

To verify that the host recognizes the disk array devices: . . . . . . . . . . . . 24

Disk Array XP operating system configuration guide: IBM AIX 3

Configure disk array devices . . . . . . . . . . . . . . . . . . . . . . . . . 25Changing the device parameters . . . . . . . . . . . . . . . . . . . . . . . . 25Assigning the new devices to volume groups . . . . . . . . . . . . . . . . . . . 28Creating the Journaled File Systems . . . . . . . . . . . . . . . . . . . . . . . 31

To create the Journaled File Systems: . . . . . . . . . . . . . . . . . . . . 31Mounting and verifying the file systems . . . . . . . . . . . . . . . . . . . . . 35

2 Troubleshooting . . . . . . . . . . . . . . . . . . . . 37Error conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Calling the HP support center . . . . . . . . . . . . . . . . . . . . . . . . . 39

Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Before you call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

A Path Worksheet . . . . . . . . . . . . . . . . . . . . 41

B Disk array supported emulations . . . . . . . . . . . . . 43Supported emulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Emulation specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Disk parameters by emulation type . . . . . . . . . . . . . . . . . . . . . . . 46Byte information table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Physical partition size table . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Glossary . . . . . . . . . . . . . . . . . . . . . . . . 59

Index . . . . . . . . . . . . . . . . . . . . . . . . . 63

4

Preface

About this guideThis guide provides information about:

• Requirements and procedures for connecting an XP disk array to a host system• Configuring the disk array for use with the IBM AIX operating system

Intended audienceThis guide is intended for system administrators with knowledge of:• The host hardware• IBM AIX operating system• XP disk arrays

Disk arraysUnless otherwise noted, the term “disk array” refers to these disk arrays:• HP StorageWorks Disk Array XP128• HP StorageWorks Disk Array XP1024• HP StorageWorks XP10000 Disk Array• HP StorageWorks XP12000 Disk Array

Related documentationThe following documents provide related information:

• HP StorageWorks Disk Array XP128: Owner’s Guide• HP StorageWorks Disk Array XP1024: Owner’s Guide• HP StorageWorks XP10000 Disk Array: Owner’s Guide• HP StorageWorks XP12000 Disk Array: Owner’s Guide

You can find these documents on the storage web site:

http://h18006.www1.hp.com/storage/xparrays.html


http://h18006.www1.hp.com/storage/xparrays.html

Document conventions and symbolsConvention Element

Blue text Cross-reference links and email addresses

Bold • Keys that are pressed• Text typed into a GUI element, such as a box• GUI elements that are clicked or selected, such as

menu and list items, buttons, tabs, and check boxes• Literal values typed exactly as shown

Italics Text emphasis and book titles

Blue, underlined:www.hp.com

Web site addresses

Monospace font • File and directory names• System output• Code• Commands, their arguments, and argument values

Monospace, italicfont

• Code variables• Command variables

Monospace, boldfont

Emphasized monospace text

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.

NOTE:Provides additional information.

6 Preface

TIP:Provides helpful hints and shortcuts.

HP technical supportIn North America, call technical support at 1-800-633-3600, available 24 hours aday, 7 days a week.

Outside North America, call technical support at the location nearest you. Telephonenumbers for worldwide technical support are listed on the HP support web site:http://www.hp.com/support. From this web site, select your country.

Collect the following information before calling:

• Technical support registration number (if applicable)• Product serial numbers• Product model names and numbers• Applicable error messages• Operating system type and revision level• Detailed questions

For continuous quality improvement, calls may be recorded or monitored.

Subscription serviceHP strongly recommends that customers register online using the Subscriber’s Choiceweb site: http://www.hp.com/go/e-updates.

Subscribing to this service provides you with e-mail updates on the latest productenhancements, newest driver versions, and firmware documentation updates as well asinstant access to numerous other product resources.

After subscribing, locate your products by selecting Business support and then Storageunder Product Category.

Other HP web sitesFor additional information, see the following HP web sites:• http://www.hp.com/go/storage• http://www.hp.com/support/• http://www.hp.com/service_locator• http://www.docs.hp.com


http://www.hp.com/support

http://www.hp.com/go/e-updates

http://www.hp.com/go/storage

http://www.hp.com/support/

http://www.hp.com/service_locator

http://www.docs.hp.com

8 Preface

1 Installation

You and your HP service representative each play a role in installation. Your HP servicerepresentative is responsible for installing the disk array and formatting the disk devices.You are responsible for configuring the host server for the new devices with assistancefrom your HP service representative.

Features and requirementsAsk your HP service representative about the latest supported hardware and software.

The disk array has the following features:

• Storage capacity. The capacity for each model is listed below:XP128: From 8 to 128 drives for up to 36 TB, 48 FC portsXP1024: From 8 to 1024 drives for up to 149 TB, 64 FC portsXP10000: Up to 240 drives for up to 69.2 TB, 48 FC portsXP12000: Up to 1152 drives for up to 332 TB, 128 FC ports

• Server support. IBM RS/6000 series, POWERstation, POWERserver, or SP series• Operating system support. IBM AIX OS with current OS patches

Before installing the array, conform the environment to these requirements:

• Superuser access. Make sure you have superuser (root) access• Host Bus Adapters (HBAs). Install HBAs and all utilities and drivers. Refer to the

adapter documentation for installation details• (Recommended) HP StorageWorks Remote Web Console XP, Command View

XP Advanced Edition or Command View XP with LUN management feature forconfiguring disk array ports and paths

• (Recommended) HP StorageWorks LUN Configuration and Security Manager XP• (Optional) Other available XP software (some may not be supported by your

system):HP StorageWorks Business Copy XPHP StorageWorks Continuous Access XPHP StorageWorks Continuous Access Extension XPHP StorageWorks Auto LUN XPHP StorageWorks Data Exchange XPHP StorageWorks Resource Manager XPHP StorageWorks RAID Manager XP


HP StorageWorks Cache LUN XPHP StorageWorks Auto Path XPHP StorageWorks Cluster Extension XPHP StorageWorks Performance Advisor XP

Fibre Channel interfaceThe XP family of disk arrays supports these Fibre Channel elements:

• Connection speed of 1 Gbps and 2 Gbps• Short-wave non-OFC (open fiber control) optical interface• Multimode optical cables with SC or LC connectors• Public or private arbitrated loop (FC-AL) or direct fabric attach• Fibre Channel switches

Even though the interface is Fibre Channel, this guide uses the term “SCSI disk” becausedisk array devices are defined to the host as SCSI disks.

Device emulation typesThe XP family of disk arrays supports these device emulation types:

• OPEN-x devices: OPEN-x logical units represent disk devices. Except forOPEN-V, these devices are based on fixed sizes. OPEN-V is a user-defined size.Supported emulations include OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L,and OPEN-V devices.

• LUSE devices (OPEN-x*n): Logical Unit Size Expansion (LUSE) devices combine 2to 36 OPEN-x devices to create expanded LDEVs larger than standard OPEN-xdisk devices. For example, an OPEN-x LUSE volume created from ten OPEN-xvolumes is designated as OPEN-x*10.

• CVS devices (OPEN-x CVS): Volume Size Configuration (VSC) defines customvolumes (CVS) that are smaller than normal fixed-sized logical disk devices(volumes). (OPEN-V is a CVS-based custom disk size that you determine. OPEN-Ldoes not support CVS.)

• LUSE (expanded) CVS devices (OPEN-x*n CVS): LUSE CVS combines CVS devicesto create an expanded device. This is done by first creating CVS custom-sizeddevices and then using LUSE to combine from 2 to 36 CVS devices. For example,if three OPEN-9 CVS volumes are combined to create an expanded device, thisdevice is designated as OPEN-9*3-CVS.

FailoverThe disk arrays support many standard software products that provide host, application,or I/O path failover and management.

10 Installation

SNMP configurationThe XP family of disk arrays supports standard Simple Network Management Protocol(SNMP) for remotely managing the disk array. The SNMP agent on the service processor(SVP) performs error-reporting operations requested by the SNMP manager. SNMPproperties are usually set from the SVP but they can also be set remotely using RemoteWeb Console XP, Command View XP, or Command View XP Advanced Edition. Refer tothe applicable user’s guide for procedures.

RAID Manager command devicesRAID Manager manages Business Copy (BC) or Continuous Access (CA) operationsfrom a host server. To use RAID Manager with BC or CA, you use Remote Web Console,Command View, or Command View XP Advanced Edition to designate at least one LDEVas a command device. Refer to the applicable user’s guide for information about how todesignate a command device.


Installation proceduresPerform these actions to install and configure the disk array:

1. Install and configure the disk array

• Setting the host mode for the disk array ports• Setting the System Option Modes• Configuring the Fibre Channel ports

2. Install and configure the host

• Loading the OS and software• Installing and configuring the HBAs• Clustering and fabric zoning• Fabric zoning and LUN security for multiple operating systems

3. Connect the disk array

• Defining the paths• Verifying host recognition of disk array devices

4. Configure disk array devices

• Changing the device parameters• Assigning the new devices to volume groups• Creating the Journaled File Systems• Mounting and verifying the file systems

12 Installation

Install and configure the disk arrayThe HP service representative performs these tasks:

• Assembling hardware and installing software• Loading the microcode updates• Installing and formatting devices

After these tasks are finished, you will use Remote Web Console, Command View,Command View XP Advanced Edition, or LUN Configuration and Security Manager tocomplete the remaining tasks listed below. If you do not have these programs, your HPservice representative can perform these tasks for you.

Setting the host mode for the disk array portsAfter the disk array is installed, you must set the host mode for each disk array port tomatch the host OS. Set the host mode using LUN Manager in Remote Web ConsoleXP (shown), Command View XP, or Command View XP Advanced Edition. If these arenot available, the HP service representative can set the host mode using the SVP. Thehost mode for AIX is 0F.


For the XP1024/XP128 arrays, the host mode can also be set at the port informationwindow in Command View XP AE.

14 Installation

Setting the System Option ModesThe HP service representative sets the System Option Mode(s) based on the operatingsystem and software configuration of the host.

Mode Level HA Software Description and Usage

140 Optional None ON: Response to the Inquiry commandis changed, and the volume can be usedfrom VeritasNetBackUP in heterogeneousOS configuration, such as HP-UX.OFF: Normal response to the Inquirycommand.

186 Mandatory Veritas DatabaseEditions/ AdvancedCluster

ON: Mandatory setting when VERITASDatabase Editions/Advanced Cluster isconnected.OFF: VERITAS Database Editions/Advanced Cluster should not be connectedwith this setting.

254 Optional Veritas DatabaseEditions

Change the response of reserve conflictstatus to Read Capacity, Verify, and StartStop Unit.ON: Normal end is reported.OFF: Reserve conflict status is reported.

280 Optional HP-UX Ghost LUN Remove OS version:HP-UX 11.0 and later.ON: When the host scans the LUNS on theport, the disk array is not represented inthe device list for HP-UX.OFF: When the host scans the LUNS on theport, the disk array is represented in thedevice list for HP-UX.


Configuring the Fibre Channel portsConfigure the disk array Fibre Channel ports by using Remote Web Console (shown),Command View, or Command View XP AE. Select the settings for each port based onyour storage area network topology. Use switch zoning if you connect different types ofhosts to the array through the same switch.

Fibre addressIn fabric environments, the port addresses are assigned automatically. In arbitratedloop environments, set the port addresses by selecting a unique arbitrated loopphysical address (AL-PA) or loop ID for each port. For specific values, refer to the HPStorageWorks LUN Configuration and Security Manager XP User Guide applicableto your array.

16 Installation

Fabric and connection parameter settingsSet each array port to FABRIC ON or OFF with connections of POINT-TO-POINT or FC-ALas shown in the following figure and table. For detailed topology information, refer tothe HP StorageWorks SAN Design Reference Guide on the http://www.hp.com website.

Fabric Parameter Connection Parameter Provides

ON FC-AL FL-port (public arbitratedloop)

ON Point-to-Point F-port (fabric port)

OFF FC-AL NL-port (private arbitratedloop)

OFF Point-to-Point Not supported


http://www.hp.com

Install and configure the hostThis section explains how to install and configure the host and host bus adapters (HBAs)that connect the host to the disk array.

Loading the OS and softwareFollow the manufacturer’s instructions to load the operating system and software ontothe host. Load all OS patches and configuration utilities supported by HP and the HBAmanufacturer.

Installing and configuring the HBAsInstall and configure the host bus adapters using the HBA manufacturer’s instructions.

Supported HBAsSupported HBAs include the IBM FC6227, IBM FC6228, and IBM FC6239.

To verify that the FC6227 drivers are installed:1. Use the lslpp command to display the drivers currently installed on the system.

Example

# lslpp -l | grep df1000f7

2. Check the list to see if the required drivers are installed. For the IBM FC6227 HBA,the following drivers are required:

devices.pci.df1000f7

devices.fcp.disk

If the drivers are not displayed, install the drivers by using the installp commandor SMIT.

18 Installation

To check the firmware level:The HBA should have the proper version of firmware installed.

1. Use the lsdev command to display the device object.

Example

# lsdev -Cc adapter

2. Use the lscfg command to display the firmware level.

Example

# lscgfg -vl fcsX

fcsX is the fiber device object (typically fcs0). The field “Devices Specific.(Z9)”shows the installed firmware revision of the HBA.

To install the drivers using the AIX command line:1. Insert the IBM drivers CD.

2. Use the installp command to install the drivers.

Example

# installp -a -dlpfc.installp all

3. Use the lslpp command to verify that the drivers are installed on the system.

4. Configure the new devices by rebooting the system with the shutdown –r commandor using the cfgmgr command to run Configuration Manager.

To install the drivers using SMIT:1. Insert the IBM drivers CD.

2. Start SMIT.

Example

# smit

The System Management screen appears.

3. Select Install Additional Software.

4. Select Input Device / Directory For Software and press F4 to select device.

5. Select Software To Install and press F4 to display a list of software.

6. Select the drivers needed using F7.


You can use the slash (“/”) to search for the components in the list.

HBA FC6227 requires these drivers:

devices.pci.df1000f7

devices.fcp.disk

7. Press Enter.

Wait for status to change from RUNNING to OK.

8. Check installation summary result (SUCCESS).

9. Press F10.

10. Use the smit devinst command to configure the devices.

20 Installation

Clustering and fabric zoningIf you plan to use clustering, install and configure the clustering software on the servers.

Clustering is the organization of multiple servers into groups. Within a cluster, eachserver is a node. Multiple clusters compose a multi-cluster environment. The followingexample shows a multi-cluster environment with three clusters, each containing twonodes. The nodes share access to the disk array.

Within the Storage Area Network (SAN), the clusters may be homogeneous (all thesame operating system) or they may be heterogeneous (mixed operating systems). Howyou configure LUN security and fabric zoning depends on the operating system mix andthe SAN configuration.


Fabric zoning and LUN security for multipleoperating systems

You can connect multiple clusters of various operating systems to the same switch andfabric using appropriate zoning and LUN security as follows:

• Storage port zones may overlap if more than one operating system needs toshare an array port.

• Heterogeneous operating systems may share an XP array port if you use SecureManager and set the appropriate host group and mode. All others must connectto a dedicated XP array port.

• Use Secure Manager for LUN isolation when multiple hosts connect through ashared array port. Secure Manager provides LUN security by allowing you torestrict which LUNs each host can access.

Environment OS Mix Fabric Zoning LUN Security

homogeneous (a single OStype present in the SAN)

Not requiredStandalone SAN(non-clustered)

heterogeneous (more thanone OS type present in theSAN)

Required

Must be usedwhen multiple hostsconnect through ashared port


Not requiredClustered SAN


Required

Must be used whenmultiple clusternodes connectthrough a sharedport


Not requiredMulti-ClusterSAN


Required

Must be used whenmultiple clusternodes connectthrough a sharedport

Connect the disk arrayThe HP service representative connects the disk array to the host by:

1. Verifying operational status of the disk array channel adapters, LDEVs, and paths.

2. Connecting the Fibre Channel cables between the disk array and the fabric switchor host.

3. Verifying the ready status of the disk array and peripherals.

22 Installation

Defining the pathsUse Remote Web Console (shown), Command View, or Command View XP AE to definepaths (LUNs) between hosts and volumes in the disk array.

This process is also called “LUN mapping.” In Remote Web Console and CommandView, LUN mapping includes:

• Configuring ports• Enabling LUN security on the ports• Creating host groups• Assigning host bus adapter WWNs to host groups• Mapping volumes to host groups (by assigning LUNs)

In Command View XP AE, LUN mapping includes:

• Configuring ports• Creating storage groups• Mapping volumes and WWN/host access permissions to the storage groups

For details see LUN Configuration and Security Manager XP User’s Guide or CommandView XP Advanced Edition Device Manager Web Client User’s Guide. Note the LUNS


and their ports, WWNs, nicknames, and LDEVs for later use in verifying host anddevice configuration.

Verifying host recognition of disk array devices

To verify that the host recognizes the disk array devices:1. Log into the host as an administrator (root).

2. If the disk array LUNs are defined after the IBM system is powered on, issue acfgmgr command to recognize the new devices.

3. Use the lsdev command to display system device data and verify that the systemrecognizes the newly installed devices.

The devices are listed by device file name. All new devices should be listed as“Available.” If they are listed as “Define,” you must do more configuration beforethey can be used.

Example

#lsdev -Cc diskhdisk0 Available 10-60-00-5, 0 16 Bit SCSI Disk Drivehdisk1 Available 10-60-00-6, 0 16 Bit SCSI Disk Drive

The example shows that Device hdisk0 is installed on bus 60 and has TID=5 andLUN=0.

4. Record the device file names for the new devices. You will use this information inchanging the device parameters.

5. Use the lscfg command to find out the AIX disk device’s corresponding array LDEVdesignation.

Example

# lscfg –vl hdisk3

In this example, the emulation type, LDEV number, CU number and array portdesignation should all be displayed for disk device hdisk3.

24 Installation

Configure disk array devicesDisks in the disk array are configured using the same procedure for configuring any newdisk on the host. This includes the following procedures:

• Changing the device parameters• Assigning the new devices to volume groups• Creating the Journaled File Systems• Mounting and verifying the file systems

Creating scripts to configure all devices at once may save you considerable time.

Changing the device parametersWhen the device files are created, the system sets the device parameters to the systemdefault values. You may need to change a few of those values for each new OPEN-xdevice (see table on next page):

• read/write (R/W) timeout value• queue depth• queue type

Parameter Default Value Required Value

Read/write timeout 30 60

Queue type None Simple

Parameter Recommended Value

Queue depth per LU ≤ 32

Queue depth per port (MAXTAGS) ≤ 512

The recommended queue depth settings may not provide the best I/O performance foryour system. You can adjust the queue depth setting to optimize the I/O performance ofthe disk array.

To show the device parameters using the AIX command line:At the command line prompt, enter lsattr -E -l hdiskx, where hdiskx is the device filename.

Example

# lsattr –E -l hdisk2


To change the device parameters using the AIX command line:1. To change the R/W timeout parameter, enter:

chdev –1 hdiskx –a rw_timeout=’60’

2. To change the queue depth parameter, enter:

chdev –l hdiskx –a queue_depth=’x’

where x is a value from the above table.

3. To change the queue type parameter, enter:

chdev –l hdiskx –a q_type=’simple’

Example

# chdev –l hdisk3 –a queue_depth=’2’

This changes the queue depth for device hdisk3.

4. Verify that the parameters for all devices were successfully changed.

Example

# lsattr –E –l hdisk3

5. Repeat these steps for each OPEN-x device on the disk array.

TIP:The lsattr command also shows other useful information, such as LUNID of the mapped LDEV, worldwide name of the disk array FC port,and N-Port ID.Another useful command for determining the slot position and portworldwide name of the HBA is the lscfg –v –l hdiskx command.

To change the device parameters using SMIT:1. Start SMIT. (Optional) For an ASCII session, use the smit –C command.

26 Installation

2. Select Devices.

Example

System ManagementMove cursor to desired item and press Enter.

Software Installation and MaintenanceSoftware License ManagementDevicesSystem Storage Management (Physical & Logical Storage)Security & UsersCommunications Applications and ServicesPrint SpoolingProblem DeterminationPerformance & Resource SchedulingSystem EnvironmentsProcesses & SubsystemsApplicationsUsing SMIT (information only)

3. Select Fixed Disk.

4. Select Change/Show Characteristics of a Disk.

5. Select the desired device from the Disk menu.

The Change/Show Characteristics of a Disk screen for that device is displayed.

6. Enter the correct values for the read/write timeout value, queue depth, and queuetype parameters. Press Enter to complete the parameter changes.

Example

Change/Show Characteristics of a DiskType or select values in entry fields.Press Enter AFTER making all desired changes.[MORE...4]

StatusLocationParent adapterConnection addressPhysical volume IDENTIFIERASSIGN physical volume identifier noQueue DEPTH [2]Queuing TYPE [simple]Use QERR Bit [yes]Device CLEARS its Queue on Error [no]READ/WRITE time out value [60]START unit time out value [60]REASSIGN time out value [120]APPLY change to DATABASE only no


7. Repeat these steps for each OPEN-x device on the disk array.

Assigning the new devices to volume groupsAssign the new devices to volume groups using the AIX system’s Logical VolumeManager (accessed from within SMIT). This operation is not required when the volumesare used as raw devices.

To assign a device to a volume group:1. Start SMIT. (Optional) For an ASCII session, use the smit –C command.

2. Select System Storage Management (Physical & Logical Storage).

Example



3. Select Logical Volume Manager.

Example

System Storage Management (Physical & Logical Storage)Move cursor to desired item and press Enter.

Logical Volume ManagerFile SystemsFiles & DirectoriesRemovable Disk Management *1System Backup Manager

28 Installation

4. Select Volume Groups.

Example

Logical Volume ManagerMove cursor to desired item and press Enter.

Volume GroupsLogical VolumesPhysical VolumesPaging Space

5. Select Add a Volume Group.

Example

Volume GroupsMove cursor to desired item and press Enter.

List All Volume GroupsAdd a Volume GroupSet Characteristics of a Volume GroupList Contents of a Volume GroupRemove a Volume GroupActivate a Volume GroupDeactivate a Volume GroupImport a Volume GroupExport a Volume GroupMirror a Volume Group *1Unmirror a Volume Group *1Synchronize LVM Mirrors *1Back Up a Volume GroupRemake a Volume GroupList Files in a Volume Group BackupRestore Files in a Volume Group Backup


6. Enter or select values for the following fields:

Volume Group name (the volume group can contain multiple hdisk devices)

Physical partition size in megabytes, see Physical partition size table

Physical Volume names

To enter values, place the cursor in the field and type the value.

To select values, place the cursor in the field and press F4.

Example

Type or select values in entry fields.Press Enter AFTER making all desired changes.[Entry Fields]

VOLUME GROUP name [vg01]Physical partition SIZE in megabytes 4PHYSICAL VOLUME names [hdisk1]Activate volume group AUTOMATICALLY yes

at system restart?Volume Group MAJOR NUMBER []

7. Enter yes or no in the Activate volume group AUTOMATICALLY at system restart?field.

If you are not using HACMP (High Availability Cluster Multi-Processing) or HAGEO(High Availability Geographic), enter yes.

If you are using HACMP and/or HAGEO, enter no.

8. Press Enter when you have entered the values. The confirmation screen appears.

Example

ARE YOU SURE?

Continuing may delete information you may wantto keep. This is your last chance to stopbefore continuing.

Press Enter to continue.Press Cancel to return to the applications.

9. Press Enter again.

The Command Status screen appears. To ensure the devices have been assigned toa volume group, wait for OK to appear on the Command Status line.

10. Repeat these steps for each volume group needed.

30 Installation

Creating the Journaled File SystemsCreate the Journaled File Systems using the System Manager Information Tool (SMIT).This operation is not required when the volumes are used as raw devices. The largest filesystem permitted in AIX is 64 GB.

To create the Journaled File Systems:1. Start SMIT.

2. Select System Storage Management (Physical & Logical Storage).

Example



3. Select File Systems.

Example

System Storage Management (Physical & Logical Storage)Move cursor to desired item and press Enter.

Logical Volume ManagerFile SystemsFiles & DirectoriesRemovable Disk Management *1System Backup Manager


4. Select Add / Change / Show / Delete File Systems .

Example

File SystemsMove cursor to desired item and press Enter.

List All File SystemsList All Mounted File SystemsAdd / Change / Show / Delete File SystemsMount a File SystemMount a Group of File SystemsUnmount a File SystemUnmount a Group of File SystemsVerify a File SystemBackup a File SystemRestore a File System

5. Select Journaled File System.

Example

Add / Change / Show / Delete File SystemsMove cursor to desired item and press Enter.

Journaled File SystemsCDROM File SystemsNetwork File System (NFS)Cache Fs *1

6. Select Add a Journaled File System

Example

Journaled File SystemMove cursor to desired item and press Enter.

Add a Journaled File SystemAdd a Journaled File System on a Previously Defined

Logical VolumeChange / Show Characteristics of a Journaled File SystemRemove a Journaled File SystemDefragment a Journaled File System

32 Installation

7. Select Add a Standard Journaled File System.

Example

Add a Journaled File SystemMove cursor to desired item and press Enter.

Add a Standard Journaled File SystemAdd a Compressed Journaled File SystemAdd a Large File Enabled Journaled File System

8. Select a volume group, and press Enter.

Example

Volume Group NameMove cursor to desired item and press Enter.

rootvgvg01


9. Enter values for the following fields:

SIZE of file system (in 512-byte blocks). Enter the lsvg command to display thenumber of free physical partitions and physical partition size. Calculate themaximum size of the file system as follows: (FREE PPs - 1) x (PP SIZE) x 2048

Mount Point: Enter mount point name. (Make a list of the mount point names forreference.)

Mount AUTOMATICALLY at system restart? Enter yes.

CAUTION:In high availability systems (HACMP and/or HAGEO), enter no.

Number of bytes per node. Enter the number of bytes appropriate for theapplication, or use the default value.

Example

Add a Journaled File SystemType or select values in entry fields.Press Enter AFTER making all desired changes.[Entry Fields]

Volume group name vg01SIZE of file system (in 512-byte blocks) [4792320]MOUNT POINT [VG01]Mount AUTOMATICALLY at system restart? noPERMISSIONS read/writeMount OPTIONS []Start Disk Accounting? noFragment Size (bytes) 4096Number of bytes per inode 4096Compression algorithm noAllocation Group Size (Mbytes) *1

10. Press Enter to create the Journaled File System.

The Command Status screen appears.

Wait for OK to appear on the Command Status line.

11. To continue creating Journaled File Systems, press the F3 screen. key until youreturn to the Add a Journaled File System screen. Repeat steps 2 through 10 foreach Journaled File System to be created.

12. To exit SMIT, press the F10 key.

34 Installation

Mounting and verifying the file systemsMount the file systems and verify that the file systems were created correctly and arefunctioning properly.

To mount and verify the file systems:

1. Mount the file system. Enter:

mount mount_point_name

Example

# mount /vg01

2. Repeat step 1 for each new file system.

3. Use the df command to verify the size of the file systems. The capacity is listed in512-byte blocks. To list capacity in 1024-byte blocks, use the df –k command.

Example

# df

File system 512-blocks free %Used Iused %Iused Mounted on

/dev/hd4 8192 3176 61% 652 31% /

/dev/hd2 1024000 551448 46% 6997 5% /usr

/dev/hd9var 8192 5512 32% 66 6% /var

/dev/hd3 24576 11608 52% 38 0% /tmp

/dev/hd1 8192 7840 4% 17 1% /home

/dev/lv00 4792320 4602128 4% 16 1% /VG00 (OPEN-3)/dev/lv01 4792320 4602128 4% 16 1% /VG01 (OPEN-3)

/dev/lv02 14401536 13949392 4% 16 1% /VG02 (OPEN-9)

4. Verify that the file system is usable by performing some basic operations (forexample, file creation, copying, and deletion) on each logical device.

Example

# cd /hp00

# cp /smit.log /hp00/smit.log.back1# ls -l hp00

–rw-rw-rw- 1 root system 375982 Nov 30 17:25 smit.log.back1

# cp smit.log.back1 smit.log.back2

# ls -l

-rw-rw-rw- 1 root system 375982 Nov 30 17:25 smit.log.back1

-rw-rw-rw- 1 root system 375982 Nov 30 17:28 smit.log.back2

# rm smit.log.back1

# rm smit.log.back2


5. Use the df command to verify that the file systems have successfully automountedafter a reboot. Any file systems that were not automounted can be set to automountusing the SMIT Change a Journaled File System screen.

If you are using HACMP or HAGEO, do not set the file systems to automount.

Example

# df

File system 512-blocks free %Used Iused %Iused Mounted on

/dev/hd4 8192 3176 61% 652 31% /

/dev/hd2 1024000 551448 46% 6997 5% /usr

/dev/hd9var 8192 5512 32% 66 6% /var

/dev/hd3 24576 11608 52% 38 0% /tmp

/dev/hd1 8192 7840 4% 17 1% /home

/dev/lv00 4792320 4602128 4% 16 1% /hp00/dev/lv01 4792320 4602128 4% 16 1% /hp01

/dev/lv02 14401536 13949392 4% 16 1% /hp02

HACMP and HAGEO do not provide a complete disaster recovery or backupsolution and are not a replacement for standard disaster recovery planning andbackup/recovery methodology.

36 Installation

2 Troubleshooting

This section includes resolutions for various error conditions you may encounter.

If you are unable to resolve an error condition, ask your HP support representative forassistance. See Calling the HP support center

Error conditionsDepending on your system configuration, you may be able to view error messages(R-SIMS) as follows:

• In Remote Web Console (Status tab)• In Command View Advanced Edition (Alerts window)• In Command View (Event History or Event Notification windows)


Error Condition Recommended Action

The logical devices are notrecognized by the host.

Verify that the READY indicator lights on the disk arrayare ON.Verify that fiber cables are correctly installed and firmlyconnected.Verify that the target IDs are properly configured.The LUNs for each TID must start at 0 and continuesequentially without skipping any numbers.Verify that the TIDs/WWNs on each bus are unique.Do not install two devices with the same ID on the samebus.Recheck the buses for new devices.Verify that LUSE devices are not intermixed with normalLUNs on the same port.Verify that the maximum number of LUSE devices per porthas not been exceeded.Verify that the disk array host mode is set correctly.

The host does not rebootproperly after hard shutdown.

If you power off the host without executing the shutdownprocess, wait three minutes to allow the disk array’sinternal timeout process to purge queued commands. Ifthe host restarts while the disk array is processing queuedcommands, the host may not reboot successfully.

Physical volumes cannot becreated.

Verify that the disk array logical devices are correctlyformatted.

Logical volumes cannot becreated.

Verify that the volume capacity for OPEN-x volumes isnot greater than the maximum capacity allowed. SeeAppendix B,Disk array supported emulationsVerify that the capacity of the volume group is not lessthan the total capacity of the partitioned logical volume.

A file system is not mountedafter rebooting.

Verify that the host was restarted correctly.Verify that the file system attributes are correct.

The disk array performs a selfreboot because the disk arraywas busy or it logged a panicmessage.

Reboot the host.

The disk array responds “NotReady” or the disk array hasdisplayed “Not Ready” andtimed out.

Contact HP.

The host detects a parity error. Check the HBA and make sure it was installedproperly.Reboot the host.

The host hangs or devices aredeclared and the host hangs.

Make sure there are no duplicate disk array TIDs and thatdisk array TIDs do not conflict with any host TIDs.

38 Troubleshooting

Calling the HP support centerIf you are unable to resolve an error condition, contact the HP support center forassistance.

Contact InformationIn North America, call technical support at 1-800-633-3600, available 24 hours aday, 7 days a week.

Outside North America, call technical support at the location nearest you. Telephonenumbers for worldwide technical support are listed on the HP support web site:http://www.hp.com/support. From this web site, select your country.

Before you callBe sure to have the following information available:

• Technical support registration number (if applicable)• Product serial numbers• Product model names and numbers• Applicable error messages• Operating system type and revision level• Detailed, specific questions


http://www.hp.com/support

40 Troubleshooting

A Path Worksheet

LDEV (CU:LDEV) (CU =control unit)

DeviceType

SCSI BusNumber

Path 1 Alternate Paths

0:00 TID:LUN:

TID:LUN:

TID:LUN:

0:01 TID:LUN:

TID:LUN:

TID:LUN:

0:02 TID:LUN:

TID:LUN:

TID:LUN:

0:03 TID:LUN:

TID:LUN:

TID:LUN:

0:04 TID:LUN:

TID:LUN:

TID:LUN:

0:05 TID:LUN:

TID:LUN:

TID:LUN:

0:06 TID:LUN:

TID:LUN:

TID:LUN:

0:07 TID:LUN:

TID:LUN:

TID:LUN:

0:08 TID:LUN:

TID:LUN:

TID:LUN:

0:09 TID:LUN:

TID:LUN:

TID:LUN:

0:10 TID:LUN:

TID:LUN:

TID:LUN:

0:11 TID:LUN:

TID:LUN:

TID:LUN:

0:12 TID:LUN:

TID:LUN:

TID:LUN:

0:13 TID:LUN:

TID:LUN:

TID:LUN:


42 Path Worksheet

B Disk array supportedemulations

This appendix provides information about supported emulations and device typespecifications. Some parameters may not be relevant to your array. Consult your HPrepresentative for information about supported configurations for your system.

Supported emulations

XP Model EmulationEmulationSupported LUSE CVS LUSE & CVS

OPEN-3 Yes Yes Yes Yes

OPEN-8 Yes Yes Yes Yes

XP128 OPEN-9 Yes Yes Yes Yes

XP1024 OPEN-E Yes Yes Yes Yes

XP10000 OPEN-K

XP12000 OPEN-L Yes Yes

OPEN-M

OPEN-V Yes Yes


Emulation specificationsEmulation(Note 1)

Category(Note 2)

Blocks (512bytes )

SectorSize(bytes)

# ofCylinders

Heads SectorsperTrack

CapacityMB* (Note

3)

OPEN-3 SCSI disk 4806720 512 3338 15 96 2347

OPEN-8 SCSI disk 14351040 512 9966 15 96 7007

OPEN-9 SCSI disk 14423040 512 10016 15 96 7042

OPEN-E SCSI disk 28452960 512 19759 15 96 13893

OPEN-L SCSI disk 71192160 512 49439 15 96 34761

OPEN-V SCSI disk max=125827200 512 Note 5 15 128 Note 6

LUSE

OPEN-3*n SCSI disk 4806720*n 512 3338*n 15 96 2347*n



OPEN-E*n SCSI disk 28452960*n 512 19759*n 15 96 13893*n

OPEN-L*n SCSI disk 71192160*n 512 49439*n 15 96 34761*n

OPEN-V*n SCSI disk max=125827200Note 4

512 Note 5 15 128 Note 6

CVS

OPEN-3 CVS SCSI disk Note 4 512 Note 5 15 96 Note 6



OPEN-E CVS SCSI disk Note 4 512 Note 5 15 96 Note 6

CVS LUSE

OPEN-3*n CVS SCSI disk Note 4 512 Note 5 15 96 Note 6



OPEN-E*n CVS SCSI disk Note 4 512 Note 5 15 96 Note 6

OPEN-V*n SCSI disk Note 4 512 Note 5 15 128 Note 6

*Capacity = (512 x number of blocks) ÷ 10242

44 Disk array supported emulations

Note 1:The availability of an emulation depends on the disk array.

Note 2:The devices are defined to the host as SCSI disk devices, even though the interface isFibre Channel.

Note 3:The device capacity can sometimes be changed by the BIOS or host adapter board.This may make actual capacity different from that listed in the table.

Note 4:The number of blocks for a CVS volume is calculated as follows:

# of blocks = (# of cylinders) × (# of heads) × (# of sectors per track)

Example

For an OPEN-3 CVS volume with capacity = 37 MB:# of blocks = (53 cylinders–see Note 5) × (15 heads) ×(96 sectors per track) = 76320

Example

For an OPEN-V CVS volume with capacity = 49 MB:# of blocks = (53 cylinders–see Note 5) × (15 heads) ×(128 sectors per track) = 101760

Note 5:The number of cylinders for a CVS volume is calculated as follows (↑…↑ means that thevalue should be rounded up to the next integer):

OPEN-3/8/9/E: The number of cylinders for a CVS volume = # of cylinders = ↑(capacity (MB) specified by user) × 1024/720 ↑

ExampleFor an OPEN-3 CVS volume with capacity = 37 MB:# of cylinders = ↑37 × 1024/720↑ = ↑52.62↑(rounded up to next integer) = 53 cylinders

OPEN-V: The number of cylinders for a CVS volume = # of cylinders = ↑ (capacity(MB) specified by user) × 16/15 ↑


Example

For an OPEN-V CVS volume with capacity = 49 MB:# of cylinders = ↑49 × 16/15↑ = ↑52.26↑(rounded up to next integer) = 53 cylinders

OPEN-3/8/9/E: The number of cylinders for a CVS LUSE volume = # of cylinders = ↑(capacity (MB) specified by user) × 1024/720 ↑ × n

Example

For a CVS LUSE volume with capacity = 37 MB and n = 4:# of cylinders = ↑37 × 1024/720↑ × 4 = ↑52.62↑× 4 = 53 × 4 = 212

OPEN-V: The number of cylinders for a CVS LUSE volume = # of cylinders = ↑ (capacity(MB) specified by user) × 16/15 ↑ × n

Example

For an OPEN-V CVS LUSE volume with capacity = 49 MB and n = 4:# of cylinders = ↑49 × 16/15↑ × 4 = ↑52.26↑× 4 = 53 × 4 = 212

Note 6:The capacity of an OPEN-3/8/9/E CVS volume is specified in MB, not number ofcylinders. The capacity of an OPEN-V CVS volume can be specified in MB or numberof cylinders. You set the volume size using Remote Web Console, Command Viewor Command View XP Advanced Edition.

Disk parameters by emulation type

OPEN-3 parametersEmulation Type

Parameter OPEN-3 OPEN-3*n(n=2 to 36)

OPEN-3 CVS OPEN-3 CVS*n(n=2 to 36)

ty Disk category Winchester Winchester Winchester Winchester

dt Control type SCSI SCSI SCSI SCSI

ns Sectors/tracks 96 96 96 96

nt Tracks/cylinder 15 15 15 15

nc Number of all cylinders 3,338 3,338*n Depends onconfiguration ofCV1

Depends onconfiguration ofCV3


Emulation Type



rm Number of rotations of the disk 6,300 6,300 6,300 6,300

oa a partition offset (Starting blockin a partition)

Set optionally Set optionally Set optionally Set optionally

ob b partition offset (Starting blockin b partition)


oc c partition offset (Starting blockin c partition)

0 0 0 0

od d partition offset (Starting blockin d partition)


oe e partition offset (Starting blockin e partition)


of f partition offset (Starting blockin f partition)


og g partition offset (Starting blockin g partition)


oh h partition offset (Starting blockin h partition)


pa a partition size Set optionally2 Set optionally2 Set optionally2 Set optionally2

pb b partition size Set optionally Set optionally Set optionally Set optionally

pc c partition size 4,806,720 4,806,720*n Depends onconfiguration ofCV1


pd d partition size Set optionally Set optionally Set optionally Set optionally

pe e partition size Set optionally Set optionally Set optionally Set optionally

pf f partition size Set optionally Set optionally Set optionally Set optionally

pg g partition size Set optionally Set optionally Set optionally Set optionally

ph h partition size Set optionally Set optionally Set optionally Set optionally

ba a partition block size 8,192 8,192 8,192 8,192

bb b partition block size 8,192 8,192 8,192 Set optionally

bc c partition block size 8,192 8,192 8,192 8,192

bd d partition block size 8,192 8,192 8,192 8,192


Emulation Type



be e partition block size 8,192 8,192 8,192 8,192

bf f partition block size 8,192 8,192 8,192 8,192

bg g partition block size 8,192 8,192 8,192 8,192

bh h partition block size 8,192 8,192 8,192 8,192

fa a partition fragment size 1,024 1,024 1,024 1,024

fb b partition fragment size 1,024 1,024 1,024 1,024

fc c partition fragment size 1,024 1,024 1,024 1,024

fd d partition fragment size 1,024 1,024 1,024 1,024

fe e partition fragment size 1,024 1,024 1,024 Set optionally

ff f partition fragment size 1,024 1,024 1,024 1,024

fg g partition fragment size 1,024 1,024 1,024 1,024

fh h partition fragment size 1,024 1,024 1,024 1,024

See Notes for disk parameters.








nt Tracks/cylinder 15 15 15 Set optionally









0 0 0 0


















Emulation Type







bb b partition block size 8,192 8,192 8,192 8,192




bf f partition block size 8,192 8,192 8,192 Set optionally

bg g partition block size 8,192 8,192 8,192 Set optionally






fe e partition fragment size 1,024 1,024 1,024 1,024





















0 0 0 0


















Emulation Type


















fe e partition fragment size 1,024 1,024 1,024 1,024






OPEN-E parametersEmulation Type

Parameter OPEN-E OPEN-E*n(n=2 to 36)

OPEN-E CVS OPEN-E CVS*n(n=2 to 36)













0 0 0 0


















Emulation Type

Parameter OPEN-E OPEN-E*n(n=2 to 36)

OPEN-E CVS OPEN-E CVS*n(n=2 to 36)
















fe e partition fragment size 1,024 1,024 1,024 1024






Notes for disk parameters1. The value of pc is calculated as follows:

pc = nc nt ns

The nc of OPEN-x CVS corresponds to the capacity specified by SVP or remoteconsole.

The CVS size of OPEN-x is specified by capacity (megabyte), not by number ofcylinders.

The number of cylinders of an OPEN-x CVS volume can be obtained by thefollowing calculation (↑ ↑means round up to integer).

The number of cylinders = ↑ (specified capacity in megabytes from SVP or remoteconsole) × 1,024 / 720 ↑.

Example

When 37 MB is specified for an OPEN-3 CVS volume from SVP,the number of cylinders of the OPEN-3 CVS can becalculated as follows:

37 × 1,024 / 720 = 52.62↑52.62↑ = 53

The OPEN-3 CVS volume has 53 cylinders.

2. The value of pa must be equal to or more than 131,072.

3. The number of cylinders of a Logical Unit Size Expansion (LUSE) composed ofOPEN-x CVS volumes corresponds to the capacity specified by the SVP or theremote console. CVS size of OPEN-x is specified by the capacity (megabytes), notby the number of cylinders. The number of cylinders of the OPEN-x CVS volumecan be obtained by the following calculation (↑ ↑ means round up to integer):

The number of cylinders = ↑ (specified capacity in megabytes from SVP or remoteconsole) × 1,024 / 720 ↑ × n

where n is the number of concatenated volumes for LUSE.

Example

When 37 MB is specified for the OPEN-3 CVS volume and thefour volumes are concatenated, the number of cylinders ofthe OPEN-3 CVS can be calculated as follows:

↑37 × 1,024 / 720↑ × 4 = ↑52.62↑ × 4 = 53 × 4 = 212

The LUSE for the OPEN-3 CVS volume has 212 cylinders.


Byte information tableValues in this table assume that large files are stored in large volumes, and the maximumnumber of files stored in each device type is approximately the same for each devicetype.

Byte information tableCategory LU Product Name Number of

Bytes per Inode

OPEN-3 OPEN-3*2 to OPEN-3*28 4096OPEN-3

OPEN-3*29 to OPEN-3*36 8192

OPEN-8 OPEN-8*2 to OPEN-8*9 4096

OPEN-8*10 to OPEN-8*18 8192

OPEN-8

OPEN-8*19 to OPEN-8*36 16384

OPEN-9 OPEN-9*2 to OPEN-9*9 4096

OPEN-9*10 to OPEN-9*18 8192

OPEN-9

OPEN-9*19 to OPEN-9*36 16384

OPEN-3/8/9 CVS OPEN-3 CVS OPEN-8 CVS OPEN-9 CVSOPEN-E CVS OPEN-K CVS

4096

35 to 64800 4096

64801 to 126000 8192

OPEN-3/8/9*nCVS

126001 and higher 16384

OPEN-E OPEN-E*2-OPEN-E*4 4096

OPEN-E*5 to OPEN-E*9 8192

OPEN-E


OPEN-L 4096

OPEN-L*2 to OPEN-L*3 8192

OPEN-L


OPEN-x CVS OPEN-3 CVS, OPEN-9 CVS, OPEN-E CVS,OPEN-V CVS

4096


Physical partition size tableCategory LU Product Name Physical Partition

Size in Megabytes

OPEN-3 4

OPEN-3*2 to OPEN-3*3 8




OPEN-3

OPEN-3*28 to OPEN-3*36 128

OPEN-8 8

OPEN-8*2 16



OPEN-8*10 to OPEN-8*18 128

OPEN-8

OPEN-8*19 to OPEN-8*36 256

OPEN-9 8

OPEN-9*2 16



OPEN-9*10 to OPEN-9*18 128

OPEN-9

OPEN-9*19 to OPEN-9*36 256

OPEN-E 16

OPEN-E*2 32



OPEN-E


OPEN-L 64


OPEN-L



Category LU Product Name Physical PartitionSize in Megabytes

35 to1800 2

1801 to 2300 4

2301 to 7000 8

7001 to 16200 16

13201 to 32400 32

32401 to 64800 64

64801 to 126000 128

126001 to 259200 256

259201 - 518400 512

OPEN-x*n CVS

518401 and higher 1024


Glossary

AL Arbitrated loop.

AL-PA Arbitrated loop physical address.

array group A group of 4 or 8 physical hard disk drives (HDDs) installed inan XP disk array and assigned a common RAID level. RAID1array groups consist of 4 (2D+2D) or 8 HDDs (4D+4D). RAID5array groups include a parity disk but also consist of 4 (3D+1P)or 8 HDDs (7D+1P). All RAID6 array groups are made up of8 HDDs (6D+2P).

BC HP StorageWorks Business Copy XP. BC lets you maintain up tonine local copies of logical volumes on the disk array.

CA HP StorageWorks Continuous Access XP. CA lets you createand maintain duplicate copies of local logical volumes on aremote disk array.

Command View(CVXP)

HP StorageWorks Command View XP, a software productfor managing XP arrays. Command View runs on aWindows-based management workstation.

Command ViewXP Advanced Edi-tion (CVXP AE)

HP StorageWorks Command View XP Advanced Edition,installs on the user-provided Device Manager server andprovides a browser-based platform from which you can managethe XP family of disk arrays—even globally distributed arrays.

command device A volume on the disk array that accepts Continuous Accessor Business Copy control operations which are then executedby the disk array.

CU Control Unit. Contains LDEVs and is approximately equivalentto SCSI Target ID.

CVS Custom volume size. CVS devices (OPEN-x CVS) are customvolumes configured using array management software tobe smaller than normal fixed-size OPEN system volumes.Synonymous with volume size customization (VSC).

DKC The array cabinet that houses the channel adapters and serviceprocessor (SVP).


DKU (disk cabinetunit)

The array cabinets that house the disk array physical disks.

emulation modes The logical devices (LDEVs) associated with each RAID groupare assigned an emulation mode that makes them operate likeOPEN system disk drives. The emulation mode determines thesize of an LDEV:OPEN-3: 2.46 GBOPEN-8: 7.38 GBOPEN-9: 7.42 GBOPEN-E: 13.56 GBOPEN-L: 36 GBOPEN-V: User-defined custom size

failover Disconnecting a failed unit or path and replacing it with analternative unit or path in order to continue functioning.

FC Fibre Channel.

FC-AL Fibre Channel arbitrated loop.

FCP Fibre Channel Protocol.

GB Gigabytes

HBA Host bus adapter.

host mode Each port can be configured for a particular host type. Thesemodes are represented as two-digit hexadecimal numbers. Forexample, host mode 08 represents an HP-UX host.

LDEV Logical device. An LDEV is created when a RAID group iscarved into pieces according to the selected host emulationmode (that is, OPEN-3, OPEN-8, OPEN-L). The number ofresulting LDEVs depends on the selected emulation mode. Theterm LDEV is often used synonymously with the term volume.

LUN Logical unit number. A LUN results from mapping a SCSIlogical unit number, port ID, and LDEV ID to a RAID group.The size of the LUN is determined by the emulation mode ofthe LDEV and the number of LDEVs associated with the LUN.For example, a LUN associated with two OPEN-3 LDEVs has asize of 4,693 MB.

LUSE A LUN is normally associated with only a single LDEV. TheLUSE feature allows a LUN to be associated with 1 to 36LDEVs. Essentially, LUSE makes it possible for applicationsto access a single large pool of storage. The LUSE featureis available when the HP StorageWorks LUN ConfigurationManager product is installed.

60 Glossary

OFC Open Fibre Control.

OPEN-x A general term describing any one of the supported OPENemulation modes (for example, OPEN-L).

OS Operating system.

PA Physical address.

path “Path” and “LUN” are synonymous. Paths are created byassociating a port, a target, and a LUN ID with one or moreLDEVs.

port A physical connection that allows data to pass between ahost and the disk array. The number of ports on an XP diskarray depends on the number of supported I/O slots and thenumber of ports available per I/O adapter. The XP family ofdisk arrays supports Fibre Channel (FC) ports as well as otherport types. Ports are named by port group and port letter, suchas CL1-A. CL1 is the group, and A is the port letter.

RAID Redundant array of independent disks.

remote console PC The PC running HP StorageWorks Remote Control XP.

Remote Control(RC)

HP StorageWorks Remote Control XP. A software product usedfor managing XP arrays.

Remote Web Con-sole (RWC)

HP StorageWorks XP Remote Web Console. A browser-basedprogram installed on the SVP that allows you to configure andmanage the disk array.

R-SIM Remote service information message.

SCSI Small computer system interface.

SIM Service information message.

SNMP Simple Network Management Protocol.

SVP Service processor, which is the PC built into the disk controller.The SVP provides a direct interface into the disk array. SVP useis reserved for HP support representatives only.

TB Terabyte.

TID Target ID.

Volume On the XP array, a volume is a uniquely identified virtualstorage device composed of a control unit (CU) componentand a logical device (LDEV) component separated by a colon.For example 00:00 and 01:00 are two uniquely identified


volumes; one is identified as CU = 00 and LDEV = 00, andthe other as CU = 01 and LDEV = 00; they are two uniqueseparate virtual storage devices within the XP array.

VSC Volume size customization. Synonymous with CVS.

WWN World Wide Name. A unique identifier assigned to a FibreChannel device.

62 Glossary

Index

Aarbitrated-loop physical address, 16audience, 5Auto LUN XP, 9Auto Path XP, 10

BBusiness Copy XP, 9, 11

CCache LUN XP, 10Cluster Extension XP, 10clustering, 21, 22command device(s)

one LDEV as a, 11RAID Manager, 11

Command View, 9, 11, 13, 16, 23Command View XP Advanced Edition,9, 11, 13, 14, 16, 23configuration

device, 25emulation types, 10

disk array, 13Fibre Channel ports, 16HBAs, 18host, 18port, 16System Option Mode, 15

Continuous Access Extension XP, 9Continuous Access XP, 9, 11conventions, document, 6CVS devices, 10cylinders, calculating for disk volume,55

DData Exchange XP, 9

device(s)configuration, 25emulation types, 10logical volume, 28logical, not recognized by host, 38parameters

change using SMIT commandline, 26changing, 25changing using AIX commandline, 26show using AIX command line,25

recognition, 24type specifications, 44verifying, 24volume groups, 28

disk array(s)configuration, 13connecting, 22features, 9installation overview, 12Not Ready error message, 38operating system versions, 9self reboots, 38server support, 9storage capacity, 9system requirements, 9

disk volume, calculating cylinders, 55document conventions, 6documentation

HP web sites, 5related, 5

Eemulation(s)

device emulation types, 10supported, 44

error conditions, 37


Ffabric environment

parameter settings, 17port addresses, 16zoning, 21, 22

failover, 10features, disk array, 9Fibre Channel

connection speed, 10interface, 10parameter settings, 17ports, configuring, 16supported elements, 10topology example, 17

file system(s)creating, 31journaled, 31mounting, 35not mounted after rebooting, 38verifying, 35

Gglossary, 59

HHBA(s), 9

configuring, 18firmware level, 19installing driver

using AIX command line, 19using SMIT, 19

supported, 18verifying installation, 18

help, obtaining, 7host

configuration, 18doesn’t reboot properly, 38hangs up, 38

host bus adapters, see "HBAs", 9host mode

setting, 13HP

storage web site, 7Subscriber’s Choice web site, 7technical support, 7, 39

Iinstallation, 9

connecting disk array, 22overview, 12

interface, Fibre Channel, 10

JJournaled File Systems, creating, 31

LLDEV(s)

one designated as a commanddevice, 11

logical volumes, cannot be created, 38LUN Configuration and SecurityManager XP, 9, 13, 23LUN(s)

creating, 23mapping, 23security, 21, 22

LUSE devices, 10

Mmulti-cluster environment, 21

OOPEN-x devices, 10operating system(s)

loading, 18LUN security for, 22multiple, fabric zoning for, 22supported versions, 9

Pparameter tables

byte information, 56physical partition size, 57

parity error, 38path(s)

defining, 23worksheet, 41

Performance Advisor XP, 10

64

physical volumes, cannot be created,38port(s)

address, 16Fibre Channel, 16

RR-SIMS, 37RAID Manager command devices, 11RAID Manager XP, 9related documentation, 5Remote Web Console, 9, 11, 13, 16,23requirements, disk array, 9Resource Manager XP, 9

SSCSI disk, Fibre Channel interface andterm "SCSI disk", 10security, LUN, 21, 22server, support, 9SIMS, 37SMIT, installing HBA drivers using, 19SNMP configuration, 11software, optional, 9storage capacity, 9Subscriber’s Choice, HP, 7symbols in text, 6System Option Mode, setting, 15

Ttechnical support, 39

HP, 7text symbols, 6topology, fabric, 17troubleshooting, 37

error conditions, 37technical support, 39

Vvolume(s)

groups, assigning new device, 28logical, cannot be created, 38physical, cannot be created, 38

Wweb sites, 5

HP documentation, 7HP storage, 7HP Subscriber’s Choice, 7

worksheet, path, 41

XXP family

optional software, 9storage capacity, 9

Zzoning, fabric, 21, 22


hp storageworks xp disk array os configuration guide: ibm aixh10032. · hp storageworks disk array...

Documents