HPstorageon SOlaris

HP StorageWorks

XP Disk Array Configuration Guide for SunSolaris

XP24000, XP12000, XP10000, SVS200

Part number: A5951-96037Ninth edition: June 2007

Legal and notice information

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

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Itemsare 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 products and services are setforth in the express warranty statements accompanying such products and services. Nothing herein should be construed asconstituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

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

UNIX is a registered trademark of The Open Group.

Contents

About this guide ................................................................................... 7Intended audience ...................................................................................................................... 7Related documentation ................................................................................................................ 7Document conventions and symbols ............................................................................................... 8Conventions for storage capacity values ........................................................................................ 9Window illustrations .................................................................................................................... 9HP technical support ................................................................................................................... 9Subscription service .................................................................................................................... 9HP websites ............................................................................................................................. 10Documentation feedback ........................................................................................................... 10

1 Installing and configuring Sun Solaris for the XP disk array .................... 11Features and requirements ......................................................................................................... 11Fibre Channel interface ............................................................................................................. 12Device emulation types .............................................................................................................. 12Failover ................................................................................................................................... 12SNMP configuration .................................................................................................................. 13XP RAID Manager command devices .......................................................................................... 13Installation roadmap ................................................................................................................. 13Installing and configuring the disk array ...................................................................................... 14

Setting the host mode and host group mode for the disk array ports .......................................... 14Setting the System Option Modes ......................................................................................... 15Configuring the Fibre Channel ports ..................................................................................... 15

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

Installing and configuring the host ............................................................................................... 17Loading the operating system and software ........................................................................... 17Installing and configuring the HBAs ...................................................................................... 17

WWN ....................................................................................................................... 17Configuring HBAs with the Sun SAN driver stack ............................................................. 18Configuring Emulex HBAs with the lpfc driver .................................................................. 19Configuring Qlogic HBAs with the qla2300 driver ........................................................... 20Configuring AMCC/JNI HBAs (legacy support only) ........................................................ 21

Clustering and fabric zoning ................................................................................................ 23Fabric zoning and LUN security for multiple operating systems ................................................. 24

Connecting the disk array .......................................................................................................... 24Defining the paths .............................................................................................................. 25Verifying the HBA configuration ........................................................................................... 25Adding the new device paths to the system ............................................................................ 26Verifying host recognition of disk array devices ..................................................................... 26

Configuring disk array devices ................................................................................................... 26Labeling and partitioning the devices .................................................................................... 26Creating the file systems ...................................................................................................... 27Creating the mount directories ............................................................................................. 28

Configuring for use with Veritas Volume Manager v3.2 and later .................................................... 28

XP Disk Array Configuration Guide for Sun Solaris 3

2 Troubleshooting ............................................................................... 29Error conditions ........................................................................................................................ 29Calling the HP support center ..................................................................................................... 31

Contact Information ............................................................................................................ 31Before you call ................................................................................................................... 31

A Disk array supported emulations ........................................................ 33Supported emulations ................................................................................................................ 33Emulation specifications ............................................................................................................ 34

Glossary ............................................................................................ 37

Index ................................................................................................. 41

4

Figures

..SNMP configuration ............................................................................................... 131

..Point-to-point fabric topology example ....................................................................... 172

..Multi-cluster environment .......................................................................................... 243


Tables

..Document conventions ............................................................................................... 81

..Host group modes (options) ..................................................................................... 152

..Fabric topology settings ........................................................................................... 173

..SAN fabric zoning and LUN security settings ............................................................. 244

..Error conditions ...................................................................................................... 305

..Supported emulations ............................................................................................. 336

..Emulation specifications ........................................................................................... 347

6

About this guide

This guide provides information about:

• Requirements and procedures for connecting an XP disk array or SVS200 to a host system• Configuring the disk array for use with the Sun Solaris operating system

Intended audienceThis guide is intended for system administrators with knowledge of:

• The host hardware• Sun Solaris operating system• XP disk arrays and/or the SVS200

Related documentationThe following documents [and websites] provide related information:

• HP StorageWorks XP10000 Disk Array: Owner's Guide• HP StorageWorks XP12000 Disk Array: Owner's Guide• HP StorageWorks XP24000 Disk Array: Owner's Guide• HP StorageWorks 200 Storage Virtualization System: Owner's Guide• HP StorageWorks XP LUN Manager User's Guide• HP StorageWorks SAN design reference guide• HP StorageWorks Command View XP Advanced Edition Software Device Manager Web Client

User's Guide

You can find these documents from the Manuals page of the HP Business Support Center website:

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

In the Storage section, click Disk Storage Systems and then select your product.



Document conventions and symbolsTable 1 Document conventions

ElementConvention

Cross-reference links and e-mail addressesBlue text: Table 1

website addressesBlue, underlined text: http://www.hp.com

Bold text • 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

Text emphasisItalic text

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

Monospace, italic text • Code variables• Command variables

Emphasized monospace textMonospace, bold text

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.

About this guide8

http://www.hp.com

Conventions for storage capacity valuesHP XP storage systems use the following values to calculate physical storage capacity values (harddisk drives):

• 1 KB (kilobyte) = 1,000 bytes• 1 MB (megabyte) = 1,0002 bytes• 1 GB (gigabyte) = 1,0003 bytes• 1 TB (terabyte) = 1,0004 bytes

HP XP storage systems use the following values to calculate logical storage capacity values (logicaldevices):

• 1 KB (kilobyte) = 1,024 bytes• 1 MB (megabyte) = 1,0242 bytes• 1 GB (gigabyte) = 1,0243 bytes• 1 TB (terabyte) = 1,0244 bytes• 1 block = 512 bytes

Window illustrationsThe windows shown in this guide were displayed on a Windows computer with the Internet Explorerbrowser. The windows may appear different on your computer depending on the operating systemand browser being used. Window contents also vary depending on installed program products andthe storage system being managed.

HP technical supportFor 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 numbers• Error messages• Operating system type and revision level• Detailed questions

Subscription serviceHP recommends that you register your product at the Subscriber's Choice for Business website:

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

After registering, you will receive e-mail notification of product enhancements, new driver versions,firmware updates, and other product resources.


http://www.hp.com/support

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

HP websitesFor additional information, see the following HP websites:

• http://www.hp.com• http://www.hp.com/go/storage• http://www.hp.com/service_locator• http://www.hp.com/support/manuals

Documentation feedbackHP welcomes your feedback.

To make comments and suggestions about product documentation, please send a message [email protected]. All submissions become the property of HP.

About this guide10

http://www.hp.com

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

http://www.hp.com/service_locator


1 Installing and configuring Sun Solaris forthe XP disk array

You and your HP service representative each play a role in installation. Your HP service representativeis responsible for installing the disk array and formatting the disk devices. You are responsible forconfiguring the host server for the new devices with assistance from 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 storage capacity for each model is listed below:XP10000: Up to 240 drives for up to 69.2 TB, 48 FC portsXP12000: Up to 1152 drives for up to 332 TB, 128 FC portsXP24000: Up to 1152 drives for up to 332 TB, 256 FC portsSVS200: Up to 127 TB in external storage, 48 FC ports

• Server support: Sun servers (SPARC and x86), FSC (Fujitsu Siemens Computers) servers, HP servers(x86)

• Operating system support:Check with your HP representative for the current OS versions supportedby your XP disk array

Before installing the disk array, ensure the following requirements are met:

• Volume Manager: Solaris Volume Manager or Veritas Volume Manager• Sun SAN software: For Solaris 8/9 (if not using Emulex, Qlogic, or JNI drivers), latest SAN

Foundation Software with current patches. For Solaris 10 (if not using Emulex, or Qlogic drivers),latest SAN (Leadville driver stack) with current patchesSun StorEdge Traffic Manager/Sun Storage Multipathingrequires that you configure/kernel/drv/scsi_vhci.confFor Solaris 8/9 SAN information, refer to Sun StorEdge SAN Foundation Software & InstallationGuide and Sun StorEdge Traffic Manager Software Installation and Configuration Guide at http://www.sun.com/storagetek/management_software/ (select “Sun StorageTek Traffic Managersoftware”).For Solaris 10 and later SAN information, refer to Solaris Fibre Channel and Storage MultipathingAdministration Guide at http://docs.sun.com.

• Host Bus Adapters (HBAs): Install HBAs and all utilities and drivers. Refer to the adapterdocumentation for installation details

• (Recommended) HP StorageWorks XP Remote Web Console, HP StorageWorks Command ViewXP Advanced Edition Software or HP StorageWorks XP Command View with LUN managementfeature for configuring disk array ports and paths

• (Recommended) HP StorageWorks XP Array Manager• (Optional) Check with your HP representative for other XP software available for your system.


http://www.sun.com/storagetek/management_software/


http://docs.sun.com

Fibre Channel interfaceThe XP family of disk arrays and the SVS200 support these Fibre Channel elements:

• Connection speeds of 1 Gbps, 2 Gbps, and 4 Gbps (not available for the SVS200)• 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” because disk arraydevices are defined to the host as SCSI disks.

Device emulation typesThe XP family of disk arrays and the SVS200 support these device emulation types:

• OPEN-x devices: OPEN-x logical units represent disk devices. Except for OPEN-V, these devicesare 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 2 to 36OPEN-x devices to create expanded LDEVs larger than standard OPEN-x disk devices. For example,an OPEN-x LUSE volume created from ten OPEN-x volumes is designated as OPEN-x*10.

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

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

NOTE:For the SVS200, and the XP24000/XP12000/XP10000 when connected to external storage devices, HPrecommends using OPEN-V as the emulation the array makes visible to the host. This allows configurationof external storage LDEVs without losing data. Using any other emulation may cause data loss in theexternal storage LUNs.

Refer to Table 7 on page 34 for detailed information.

FailoverThe disk arrays support many standard software products that provide host, application, or I/O pathfailover and management. The VERITAS Cluster Server and Sun Cluster host failover products aresupported for the Sun Solaris operating system. Refer to the documentation for these products andSun technical support for installation and configuration information. Your HP representative may haveto set specific disk array System Modes for these products.

For I/O path failover, different products are available from Sun, Veritas and HP. Sun supplies softwarecalled Sun StorEdge Traffic Manager (STMS) for Solaris 8/ 9 and Storage Multipathing for Solaris10. Veritas offers Veritas Volume Manager (VxVM) which includes Dynamic MultiPathing (DMP). HP

Installing and configuring Sun Solaris for the XP disk array12

supplies Hitachi Data Link Manager (HDLM). All these products provide multipath configurationmanagement, HBA I/O load balancing, and automatic failover support, however their level ofconfiguration possibilities and HBA support differs.

Refer to the manufacturers' manuals for instructions. STMS, Sun Storage Multipathing, and VxVMinstallation manuals can be downloaded from the Sun website at www.sun.com and the Veritas website at www.veritas.com.

SNMP configurationThe XP family of disk arrays and the SVS200 support standard Simple Network Management Protocol(SNMP) for remotely managing the disk array. The SNMP agent on the SVP performs error-reportingoperations requested by the SNMP manager. SNMP properties are usually set from the SVP but theycan also be set remotely using XP Remote Web Console, XP Command View, or Command View XPAdvanced Edition Software. Refer to the applicable user's guide for procedures.

Figure 1 SNMP configuration

XP RAID Manager command devicesHP StorageWorks XP RAID Manager manages HP StorageWorks XP Business Copy Software or HPStorageWorks XP Continuous Access Software operations from a host server. To use XP RAID Managerwith XP Business Copy Software or XP Continuous Access Software, you use XP Remote Web Console,XP Command View, or Command View XP Advanced Edition Software to designate at least one LDEVas a command device. Refer to the applicable user's guide for information about how to designatea command device.

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

1. Installing and configuring the disk array

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

2. Installing and configuring the host

• Loading the operating system and software• Installing and configuring the HBAs• Verifying the HBA configuration• Clustering and fabric zoning


www.sun.com

www.veritas.com

• Fabric zoning and LUN security for multiple operating systems3. Connecting the disk array

• Defining the paths• Adding the new device paths to the system• Verifying host recognition of disk array devices

4. Configuring disk array devices

• Labeling and partitioning the devices• Creating the file systems

5. Configuring for use with Veritas Volume Manager v3.2 and later

Installing and configuring 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 XP Remote Web Console, XP Command View, CommandView XP Advanced Edition Software, or XP Array Manager to complete the remaining tasks listedbelow. If you do not have these programs, your HP service representative can perform these tasks foryou.

Setting the host mode and host group mode for the disk array portsAfter the disk array is installed, you must set the host mode for each disk array port to match the hostOS. Set the host mode using LUN Manager in XP Remote Web Console (shown), XP Command View,or Command View XP Advanced Edition Software. If these are not available, the HP representativecan set the host mode using the SVP. The host mode setting for Solaris is 09.

CAUTION:The correct host mode must be set for all new installations (newly connected ports) to Solaris hosts. Do notselect a mode other than 09 for Solaris. Changing a host mode after the host has been connected isdisruptive and requires the server to be rebooted.


When a new host group is added, additional host group modes (options) may be configured. Thestorage administrator must verify if an additional host group mode is required for the host group. ForSolaris, host group mode 7 should be set as this is a prerequisite when using the Sun SAN driver.

The following host group modes (options) are available for Solaris:

Table 2 Host group modes (options)

CommentsDefaultFunction

HostGroupMode

Previously MODE186Do not apply this optionto Sun Cluster.

InactiveVERITAS DBE+RAC DatabaseEdition/Advanced Cluster for RealApplication Clusters or if VERITAS® ClusterServer 4.0 or later with I/O fencing functionis used.

2

Previously MODE249InactiveReporting Unit Attention when adding LUN7

CAUTION:Changing host group modes for ports where servers are already installed and configured is disruptive andrequires the server to be rebooted.

Setting the System Option ModesThe HP service representative sets the System Option Mode(s) based on the operating system andsoftware configuration of the host.

Configuring the Fibre Channel portsConfigure the disk array Fibre Channel ports by using XP Remote Web Console (shown), XP CommandView, or Command View XP Advanced Edition Software. Select the settings for each port based on


your storage area network topology. Use switch zoning if you connect different types of hosts to thearray through the same switch.

Fibre addressIn fabric environments, the port addresses are assigned automatically. In arbitrated loop environments,set the port addresses by selecting a unique arbitrated loop physical address (AL-PA) or loop ID foreach port. For specific values, refer to the HP StorageWorks XP LUN Manager User's Guide applicableto your array.

Fabric and connection parameter settingsSet each array port to FABRIC ON or OFF with connections of POINT-TO-POINT or FC-AL as shownin the following table and figures. For detailed topology information, refer to the HP StorageWorksSAN design reference guide at:

www.hp.com.


www.hp.com

Figure 2 Point-to-point fabric topology example

Table 3 Fabric topology settings

ProvidesConnection parameterFabric parameter

FL-port (public loop) for loop connection to aswitch

FC-ALON

NL-port (private arbitrated loop)FC-ALOFF

F-port (fabric port) for connection to a switchPOINT-TO-POINTON

Not supportedPOINT-TO-POINTOFF

Installing and configuring the hostThis section explains how to install and configure the host and host bus adapters (HBAs) that connectthe host to the disk array.

Loading the operating system and softwareFollow the manufacturer's instructions to load the operating system and software onto the host. Loadall OS patches and configuration utilities supported by HP and the HBA manufacturer.

Installing and configuring the HBAsInstall and configure the HBA driver software and setup utilities according to the manufacturer'sinstructions. Configuration settings specific to the XP array differ depending on the manufacturer.

Specific configuration information is detailed below.

WWNThe HBA configuration process may require you to enter the WWN for the array port(s) to which theHBA connects. Your HP representative can provide you this information or you may display thisinformation on the SAN switch.


Configuring HBAs with the Sun SAN driver stackSun branded HBAs are only supported with the Sun SAN driver stack. The Sun SAN driver stack alsosupports current Emulex (http://www.sun.com/io_technologies/vendor/emulex_corporation.html )and Qlogic (http://www.sun.com/io_technologies/vendor/qlogic_corp_.html HBAs.

NOTE:Ensure host group mode 7 is set for the XP array or SVS200 ports where the host is connected to enableautomatic LUN recognition using this driver.

To configure the HBA:

• Check with your HP representative to determine which non-Sun branded HBAs are supported byHP with the Sun SAN driver Stack, and if a specific System Mode or Host Group Mode setting isrequired for Sun and non-Sun branded HBAs.

• For Solaris 8/9, install the latest Sun StorEdge SAN software with associated patches. Use theSun supplied install_it script to automate installation. The script is available at http://www.sun.com/storagetek/management_software/ (select “Sun StorageTek Traffic Managersoftware”).

• For Solaris 10, use the Sun update manager (http://www.sun.com/service/sunupdate/) to installthe latest patches.

• To use Sun StorEdge Traffic Manager (MPxIO)/Sun Storage Multipathing, edit the driverconfiguration file /kernel/drv/scsi_vhci.conf to add the Vendor ID and Product ID to the“device-type-scsi-options-list” parameter. Refer to the Sun StorEdge Traffic Manager SoftwareInstallation and Configuration Guide or the Solaris Fibre Channel and Storage MultipathingAdministration Guide as applicable.

• For Solaris 8/9 change to “no” as shown:mpxio-disable="no";

• For all Solaris releases, add the following lines:

device-type-scsi-options-list ="HP OPEN", "symmetric-option";symmetric-option = 0x1000000;

NOTE:There must be exactly 6 spaces between HP and OPEN.

• For Solaris 8/9, perform a reconfiguration reboot of the host to implement changes to theconfiguration file. For Solaris 10, use the stmsboot command which will perform the modificationsand then initiate a reboot.

• For Solaris 8/9, after you have rebooted and the LDEV has been defined as a LUN to the host,use the cfgadm command to configure the controller instances for SAN connectivity. The controllerinstance (c#) may differ between systems. Replace the WWPN in the example below with theWWPNs for your array ports):

Example


http://www.sun.com/io_technologies/vendor/emulex_corporation.html

http://www.sun.com/io_technologies/vendor/qlogic_corp_.html



http://www.sun.com/service/sunupdate/

# cfgadm -alAp_Id Type Receptacle Occupant Conditionc3 fc-fabric connected configured unknownc3::50060e8003285301 disk connected configured unknownc4 fc-fabric connected configured unknownc4::50060e8003285311 disk connected configured unknown

# cfgadm -c configure c3::50060e8003285301

# cfgadm -c configure c4::50060e8003285311

Configuring Emulex HBAs with the lpfc driver

NOTE:The lpfc driver cannot be used with Sun StorEdge Traffic Manager/Sun Storage Multipathing. Emulex doesnot support using both the lpfc driver and the emlxs driver (provided with the Sun SAN driver stack)concurrently. To use the emlxs driver, refer to “Configuring HBAs with the Sun SAN driver stack” on page 18.

Configure Emulex HBAs with the lpfc driver as follows:

• Ensure you have the latest supported version• Edit the /kernel/drv/lpfc.conf driver configuration file to set up the HBA for a SAN

infrastructure:

topology = 2;scan-down = 0;

• If multiple HBAs and VxVM are used, adjust the following parameters to assure correct VxVMbehavior:

no-device-delay=0;nodev-tmo=30;linkdown-tmo=30; # verify, should be default value

• Persistent bindings are necessary in a fabric topology and are used to bind a SCSI target ID to aparticular WWPN (of an array port). This is required to guarantee that the SCSI target IDs willremain the same when the system is rebooted. Persistent bindings can be set by editing theconfiguration file or by using the lputil utility. The following example illustrates the binding oftarget 20 (lpfc instance 2) to WWPN 50060e8003285301 and the binding of target 30 (lpfcinstance 0) to WWPN 50060e8003285311:

fcp-bind-WWPN="50060e8003285301:lpfc2t20","50060e8003285311:lpfc0t30";

(Replace the WWPNs above with the WWPNs for your array ports.)

• For each LUN that needs to be accessed, add an entry to the /kernel/drv/sd.conf file. Forexample, assume you want to access LUNs 1 and 2 through both paths. You would add thefollowing entries (preferably at the end of the file):


name="sd" parent="lpfc" target=20 lun=1;name="sd" parent="lpfc" target=20 lun=2;name="sd" parent="lpfc" target=30 lun=1;name="sd" parent="lpfc" target=30 lun=2;

• Perform a reconfiguration reboot to implement the changes to the configuration files.• If LUNs have been preconfigured in the /kernel/drv/sd.conf file, use the devfsadm command

to perform LUN rediscovery after configuring LUNs as explained in“Defining the paths” on page 25.

Configuring Qlogic HBAs with the qla2300 driver

NOTE:The qla2300 driver cannot be used with Sun StorEdge Traffic Manager/Sun Storage Multipathing. Toconfigure a Qlogic HBA using the Sun SAN driver stack, refer to“Configuring HBAs with the Sun SAN driver stack” on page 18.

Configure Qlogic HBAs with the qla2300 driver as follows:

• Ensure you have the latest supported version• Edit the /kernel/drv/qla2300.conf driver configuration file to set up the HBA for a SAN

infrastructure:

hba0-connection-options=1;hba0-link-down-timeout=30;hba0-persistent-binding-configuration=1;

• Persistent bindings are necessary in a fabric topology and are used to bind a SCSI target ID to aparticular WWPN (of an array port). This is required to guarantee that the SCSI target IDs willremain the same when the system is rebooted. Persistent bindings can be set by editing theconfiguration file or by using the Sansurfer utility. The following example illustrates the bindingof target 20 (hba instance 0) to WWPN 50060e8003285301 and the binding of target 30 (hbainstance 1) to WWPN 50060e8003285311:

hba0-SCSI-target-id-20-fibre-channel-port-name="50060e8003285301";hba1-SCSI-target-id-30-fibre-channel-port-name="50060e8003285311";


• With qla2300 v4.13.01 and earlier:If LUNs have been preconfigured in the /kernel/drv/sd.conf file, use the devfsadm commandto perform LUN rediscovery after configuring LUNs as explained in“Defining the paths” on page 25.

• With qla2300 v4.15 or later:Verify that the following entry is present in /kernel/drv/sd.confname="sd" parent="qla2300" target=0;

Perform a reconfiguration reboot to implement the changes to the configuration files.Use the /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig –d qla2300 -scommand to perform LUN rediscovery after configuring LUNs as explained in“Defining the paths” on page 25.


Configuring AMCC/JNI HBAs (legacy support only)Applied Micro Circuits Corporation (AMCC) merged with Jaycor Networks Incorporated (JNI) anddiscontinued their HBA hardware and software products. Refer to http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_CN0714W for more information and migrationto different HBAs.

Configure 2 Gbit and 1 Gbit HBAs differently as explained below. JNI HBA drivers are availablefrom AMCC/JNI at http://www.jni.com/drivers. The JNI EZFibre HBA configuration utility does notallow dynamic LUN addition. Instead edit the configuration files manually as explained below, anduse EZFibre for view-only purposes. If you do not plan to use dynamic LUN addition, you may useEZFibre to configure the HBA.

Persistent bindings are necessary in a fabric topology and are used to bind a SCSI target ID to aparticular WWPN (of an array port). This is required to guarantee that the SCSI target IDs will remainthe same when the system is rebooted. Persistent bindings can be set by editing the configuration fileas shown in the examples that follow. Make sure the target in the driver configuration file and in thekernel file (/kernel/drv/sd.conf) match. Replace the WWNs shown in the examples with thecorrect WWNs for your array ports. You can view port WWNs using XP Command View or XP ArrayManager.

AMCC/JNI 2 Gbit HBAs• Use JNIC146x driver (version 5.3 or later).• Edit the HBA driver settings in the /kernel/drv/jnic146x.conf file.

For a SAN environment:

FcLoopEnabled = 0;FcFabricEnabled = 1;

For a direct connect:

FcLoopEnabled = 1;FcFabricEnabled = 0;

To enable failover for VxVM Dynamic Multi Pathing (DMP):

FailoverDelay = 30;

For SAN persistent binding:

automap = 0;jnic146x0-target20_hba = "jnic146x0";jnic146x0-target20_wwpn = "50060e8003285301";jnic146x1-target30_hba = "jnic146x1";jnic146x1-target30_wwpn = "50060e8003285311";


• Make sure the jnic146x entry below is present at the bottom of the /kernel/drv/sd.conf file:name="sd" parent="jnic146x" target=0;

• Perform a reconfiguration reboot so the host can implement the changes you made in theconfiguration files.


http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_CN0714W

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_CN0714W

http://www.jni.com/drivers

• After configuring LUNs as explained in “Defining the paths” on page 25, use thejnic146x_update_drv command to request that the jnic146x driver instances perform LUNrediscovery:/opt/JNIC146x/jnic146x_update_drv -r -a

AMCC/JNI 1 Gbit HBAs (JNIC driver, version 4.x)• Edit the /kernel/drv/jnic.conf file:

Set the Fibre topology for a SAN or direct connect.For a SAN environment:

FcLoopEnabled=0;FcFabricEnabled=1;FcPortCfgEnable = 1;

For a direct connect (FcLoopEnabled=1):

FcFabricEnabled=0;FcPortCfgEnable = 0;

To enable failover for VxVM Dynamic MultiPathing (DMP):

FailoverDelay=30;


def_hba_binding="null";target20_wwpn="50060e8003285301";target20_hba="jnic0";target30_wwpn="50060e8003285311";target30_hba="jnic1";


• Edit the /kernel/drv/sd.conf file:

name="sd" class="scsi" target=20 lun=1;name="sd" class="scsi" target=20 lun=2;...name="sd" class="scsi" target=30 lun=1;name="sd" class="scsi" target=30 lun=2;...



AMCC/JNI 1 Gbit HBAs (JNIfcaw/JNIfcaPCI drivers, version 2.x)• Edit the /kernel/drv/fca-pci.conf (or fcaw.conf) file:

Set the Fibre topology for a SAN or direct connect.For a SAN environment:


fca_nport = 1;

For a direct connect:

fca_nport = 0;

To enable failover for VxVM Dynamic Multi Pathing (DMP):

failover = 30;


def_hba_binding = "null";target20_wwpn="50060e8003285301";target20_hba="fca-pci0";target30_wwpn="50060e8003285311";target30_hba="fca-pci1";


• Edit the /kernel/drv/sd.conf file:

name="sd" class="scsi" target=20 lun=1;name="sd" class="scsi" target=20 lun=2;...name="sd" class="scsi" target=30 lun=1;name="sd" class="scsi" target=30 lun=2;...



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, each server is a node.Multiple clusters compose a multi-cluster environment. The following example shows a multi-clusterenvironment with three clusters, each containing two nodes. The nodes share access to the disk array.


Figure 3 Multi-cluster environment

Within the Storage Area Network (SAN), the clusters may be homogeneous (all the same operatingsystem) or they may be heterogeneous (mixed operating systems). How you configure LUN securityand fabric zoning depends on the operating system mix and the SAN configuration.

Fabric zoning and LUN security for multiple operating systemsYou can connect multiple clusters of various operating systems to the same switch and fabric usingappropriate zoning and LUN security as follows:

• Storage port zones may overlap if more than one operating system needs to share an array port.• Heterogeneous operating systems may share an XP array port if you use Secure Manager and set

the appropriate host group and mode. All others must connect to a dedicated XP array port.• Use Secure Manager for LUN isolation when multiple hosts connect through a shared array port.

Secure Manager provides LUN security by allowing you to restrict which LUNs each host canaccess.

Table 4 SAN fabric zoning and LUN security settings

LUN SecurityFabricZoning

OS MixEnvironment

Must be used when multiple hostsor cluster nodes connect through ashared port

Notrequired

homogeneous (a single OS typepresent in the SAN)

Standalone SAN(non-clustered)Clustered SANMulti-Cluster SAN

Requiredheterogeneous (more than one OStype present in the SAN)

Connecting 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 switch or host.


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

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

This process is also called “LUN mapping.” In XP Remote Web Console and XP Command View,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 Advanced Edition Software, LUN mapping includes:

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

For details see HP StorageWorks XP LUN Manager User's Guide or HP StorageWorks CommandView XP Advanced Edition Software Device Manager Web Client User's Guide. Note the LUNs andtheir ports, WWNs, nicknames, and LDEVs for later use in verifying host and device configuration.

Verifying the HBA configurationAfter installing the HBAs, verify recognition of the HBAs and drivers as follows:

1. Log into the system as root. Verify that all devices are powered on and properly connected tothe system.

2. Use the prtdiag command (SPARC only) to verify that the HBA is installed properly. Use theprtconf command and/or browse the /var/adm/messages file to check whether the HBAdriver has attached. Look for the WWN/WWPN of the HBA in the /var/adm/messages fileor use an HBA-specific tool or command.


Adding the new device paths to the systemAfter configuring the HBAs and to ensure the new devices are recognized, some HBA drivers requireyou to configure each LUN individually (either through the driver configuration file or in/kernel/drv/sd.conf).

CAUTION:To ensure that the system can boot properly even if you make a mistake in the driver configuration file,add the new paths at the end of the file. (This ensures that the system boot entries higher up in the file willexecute first.)

Preconfigure additional LUNs (non yet made available) to avoid unnecessary reboots. Refer to“Installing and configuring the HBAs ” on page 17 for individual driver requirements.

Verifying host recognition of disk array devicesVerify that the host recognizes the disk array devices as follows:

1. Use format to display the device information.

2. Check the list of disks to verify the host recognizes all disk array devices. If any devices aremissing or if no array devices are shown, check the following:

• SAN (zoning configuration)• Disk array path configuration (HBA WWNs)• Host HBA configuration (WWN information, driver instance, target and LUN assignment,

and /var/adm/messages)• Cables

Configuring disk array devicesDisk arrays are configured using the same procedure for configuring any new disk on the host. Thistypically includes the following procedures:

1. Labeling and partitioning the devices

2. Creating the file systems

3. Creating the mount directories

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

Labeling and partitioning the devicesPartition and label the new devices using the Sun format utility.


CAUTION:The repair, analyze, defect, and verify commands/menus are not applicable to the XP arrays and SVS200.When selecting disk devices, be careful to select the correct disk as using the partition/label commandson disks that have data can cause data loss.

1. Enter format at the root prompt to start the utility.

2. Verify that all new devices are displayed. If they are not, exit the format utility (quit or Ctrl-D),and ensure the Fibre Channel-to-LDEV paths were defined correctly for all devices and that allnew devices were added to the driver configuration file.

3. Record the character-type device file names (for example, c1t2d0) for all the new disks. You willuse this data either to create the file systems or to use them with the Sun or Veritas VolumeManager.

4. When you are asked to specify the disk, enter the number of the device to be labeled.

5. When you are asked if you want to label the disk, enter y for “yes.”

6. If you are not using Veritas Volume Manager, use the partition command to create or adjust theslices (partitions) as necessary.

7. Repeat this labeling procedure for each new device (Use the disk command to select anotherdisk).

8. When you finish labeling the disks, enter quit or press Ctrl-D to exit the format utility.

For further information, see the System Administration Guide - Devices and File systems at:

http://docs.sun.com.

Creating the file systems1. If you want to create a UFS file system, create the file system using the newfs –Cmaxcontig

command.

Example

# newfs -C 6 /dev/rdsk/c1t2d0s0

Use 6 or one of the following multiples of 6 as the maxcontig value for all disk array OPEN-xdevices: 12, 18, 24, or 30.

If you use 6, the Sun OS will access 48 KB as a unit (6*8 KB), which matches the track size ofthe OPEN-x devices. These maxcontig values (6, 12, 18, 24, 30) optimize the I/O performanceof the disk array by keeping the I/O data range on one track. The maxcontig value that youchoose depends on your applications, and you can change the maxcontig parameter to adifferent value at any time.

Use the character-type device file (for example, /dev/rdsk/c1t2d0s0) as the argument.

2. When the confirmation appears, enter y for yes if the file name is correct. If the file name is notcorrect, enter n and repeat step 1.

3. Repeat this procedure for each new OPEN-x device. Use the same maxcontig value for all diskarray devices.


http://docs.sun.com

Creating the mount directories1. Create a mount directory for each device using the mkdir command.

2. Enter each device into the mount table by editing /etc/vfstab.

3. Use the mount -a command to auto-mount devices.

4. Use a df -k command to verify the devices auto-mounted.

Configuring for use with Veritas Volume Manager v3.2 andlater

HP XP disk arrays are certified for VxVM support.

Be sure to set the driver parameters correctly when you install the HBA. Failure to do so may result ina loss of path failover in Dynamic Multipathing (DMP). See“Installing and configuring the HBAs ” on page 17 and the HBA manufacturer's instructions for settingspecific HBA parameters.

VxVM 3.2 and later use Array Support Libraries (ASL) to configure the Dynamic Multipathing (DMP)feature and other parameters. The ASL is required for all arrays. To download and install the ASLfrom the Symantec/Veritas support website: http://support.veritas.com:

1. In the “Select Product Family” menu click Volume Manager.2. In the “Select Product” menu, click Volume Manager for Unix; the “Support: Volume Manager

for UNIX” page opens.3. Enter the XP array model (for example, XP12000) in the “Ask a question” block, select “Solaris”

as Platform, and then click GO.4. Read the TechFile that appears and follow the instructions to download and install the ASL.

After installing the ASL, verify that the XP array is visible and the ASL is present using the vxdmpadmlistctlr all and vxddladm listsupport all commands.

Example

# vxddladm listsupport allgrep HPlibvxxp256.so HP Alllibvxhpxp.so HP 0450, 0451libhpxp12k.so HP 50, 51


http://support.veritas.com

2 Troubleshooting

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

If you are unable to resolve an error condition, ask your HP support representative for assistance. See“Calling the HP support center” on page 31.

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

• In XP Remote Web Console (Status tab)• In Command View XP Advanced Edition Software (“Alerts” panel).• In XP Command View (Event History or Event Notification panels)


Table 5 Error conditions

Recommended ActionError Condition

Verify that the READY indicator lights on the disk array are ON. Verifythat fiber cables are correctly installed and firmly connected.If using the Sun SAN driver stack on Solaris 8/9, verify that the Array isconfigured (cfgadm -al). Use the luxadm –e dump_map/dev/cfg/c# command (where c# is your HBA instance) to verify thatthe HBA WWN matches the WWN configured on the XP array.If not using the Sun SAN driver stack, check HBA configuration asexplained in Chapter 1. Look for the HBA WWN in the/var/adm/messages file and verify that it matches the WWNconfigured on the XP array. Verify the correct WWN for the XP ports isconfigured in the driver configuration file (WWN binding). Verify thecorrect driver instance is configured for the given WWN. Check that theHBA driver has attached with the prtconf command or by browsingthe /var/adm/messages file.On Sun SPARC servers, verify the HBA is properly installed with theprtdiag command: /usr/platform/<platform>/sbin/prtdiag.Check SAN (zoning configuration), as explained in Chapter 1.A reconfiguration reboot or a rescan for new LUNs may be required (referto “Installing and configuring the HBAs ” on page 17in Chapter 1).Verify that the disk array host mode is set correctly.

The logical devices are notrecognized by the host.

If you power off the host without executing the shutdown process, waitthree minutes to allow the disk array's internal timeout process to purgequeued commands. If the host restarts while the disk array is processingqueued commands, the host may not reboot successfully.

The host does not reboot properlyafter hard shutdown.

Verify that the LUN has been correctly labeled by the format commandand VxVM made aware of the new LUN (vxdctl enable).

Disks are not visible in VxVM.

Check that a character-type device file is specified as the device file inthe newfs command. Verify that the logical unit is correctly labeled bythe format command.

A file system cannot be created.

Verify that the host was restarted correctly.Verify that the file system attributes are correct.Verify that /etc/vfstab was edited correctly.

A file system is not mounted afterrebooting.

Reboot the host.The disk array performs a selfreboot because the disk array wasbusy or it logged a panicmessage.

Contact HP.The disk array responds “NotReady” or the disk array hasdisplayed “Not Ready” and timedout.

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

Verify the installed HBA driver is the correct one for the HBA and the HBAfirmware.

HBA driver is not attached.

Verify that you have installed the Array Support Library.vxinstall aborts after devicedetection.

Troubleshooting30

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

Contact InformationTelephone numbers for worldwide technical support are listed on the HP support web site:

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

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

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


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

Troubleshooting32

A Disk array supported emulations

This appendix provides information about supported emulations and device type specifications. Someparameters may not be relevant to your array. Consult your HP representative for information aboutsupported configurations for your system.

Supported emulationsTable 6 Supported emulations

LUSE & CVSCVSLUSE

OPENEmulationSupported

OPENEmulationTypeXP Model

YesYesYesYesOPEN-3

YesYesYesYesOPEN-8

YesYesYesYesOPEN-9XP10000

YesYesYesYesOPEN-EXP12000

OPEN-KXP24000

YesYesOPEN-LSVS200

OPEN-M

YesYesOPEN-V

NOTE:For the SVS200, and the XP24000/XP12000/XP10000 when connected to external storage devices, HPrecommends using OPEN-V as the emulation the array makes visible to the host. This allows externalstorage LDEVs to be configured without losing data. Using any other emulation may cause data loss in theexternal storage LUNs.


Emulation specificationsTable 7 Emulation specifications

CapacityMB*(Note 3)

Sectorsper

track

Heads# ofCylinders

SectorSize

(bytes)

Blocks (512 bytes)

Category(Note 2)

Emulation(Note1)

2347961533385124806720SCSI diskOPEN-3

70079615996651214351040SCSI diskOPEN-8

704296151001651214423040SCSI diskOPEN-9

1389396151975951228452960SCSI diskOPEN-E

3476196154943951271192160SCSI diskOPEN-L

Note 612815Note 5512max=125827200SCSI diskOPEN-V

LUSE

2347*n96153338*n5124806720*nSCSI diskOPEN-3*n



13893*n961519759*n51228452960*nSCSI diskOPEN-E*n

34761*n961549439*n51271192160*nSCSI diskOPEN-L*n

Note 612815Note 5512max=125827200Note 4

SCSI diskOPEN-V*n

CVS

Note 69615Note 5512Note 4SCSI diskOPEN-3 CVS



Note 69615Note 5512Note 4SCSI diskOPEN-E CVS

CVS LUSE

Note 69615Note 5512Note 4SCSI diskOPEN-3*n CVS



Note 69615Note 5512Note 4SCSI diskOPEN-E*n CVS

Note 612815Note 5512Note 4SCSI diskOPEN-V*n

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

Disk array supported emulations34

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 is Fibre Channel.

Note 3:The device capacity can sometimes be changed by the BIOS or host adapter board. This may makeactual 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 the value shouldbe rounded up to the next integer):

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

Example

For 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 byuser) × 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) specifiedby 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 of cylinders. Thecapacity of an OPEN-V CVS volume can be specified in MB or number of cylinders. You set thevolume size using XP Remote Web Console, XP Command View or Command View XP AdvancedEdition Software.

Disk array supported emulations36

Glossary

AL Arbitrated loop.

AL-PA Arbitrated loop physical address.

array group A group of 4 or 8 physical hard disk drives (HDDs) installed in an XP disk arrayand assigned a common RAID level. RAID1 array groups consist of 4 (2D+2D)or 8 HDDs (4D+4D). RAID5 array groups include a parity disk but also consistof 4 (3D+1P) or 8 HDDs (7D+1P). All RAID6 array groups are made up of 8HDDs (6D+2P).

Command ViewXP AdvancedEdition Software

HP StorageWorks Command View XP Advanced Edition Software, installs onthe user-provided Device Manager server and provides a browser-based platformfrom which you can manage the SVS200 and the XP family of disk arrays—evenglobally distributed arrays.

command device A volume on the disk array that accepts XP Continuous Access Software or XPBusiness Copy Software control operations which are then executed by the diskarray.

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

CVS Custom volume size. CVS devices (OPEN-x CVS) are custom volumes configuredusing array management software to be smaller than normal fixed-size OPENsystem volumes. Synonymous with volume size customization (VSC).

emulation modes The logical devices (LDEVs) associated with each RAID group are assigned anemulation mode that makes them operate like OPEN system disk drives. Theemulation mode determines the size 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 an alternative unit orpath in order to continue functioning.

FC Fibre Channel.

FC-AL Fibre Channel arbitrated loop.

FCP Fibre Channel Protocol.

HBA Host bus adapter.


host mode Each port can be configured for a particular host type. These modes arerepresented as two-digit hexadecimal numbers. For example, host mode 08represents an HP-UX host.

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

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

LUSE A LUN is normally associated with only a single LDEV. The LUSE feature allowsa LUN to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possiblefor applications to access a single large pool of storage. The LUSE feature isavailable when the HP StorageWorks XP Array Manager product is installed.

OFC Open Fibre Control.

OPEN-x A general term describing any one of the supported OPEN emulation modes (forexample, OPEN-L).

PA Physical address.

path “Path” and “LUN” are synonymous. Paths are created by associating a port, atarget, and a LUN ID with one or more LDEVs.

port A physical connection that allows data to pass between a host and the diskarray. The number of ports on an XP disk array depends on the number ofsupported I/O slots and the number of ports available per I/O adapter. The XPfamily of disk arrays supports Fibre Channel (FC) ports as well as other porttypes. Ports are named by port group and port letter, such as CL1-A. CL1 is thegroup, and A is the port letter.

RAID Redundant array of independent disks.

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 providesa direct interface into the disk array. SVP use is reserved for HP supportrepresentatives only.

SVS Storage Virtualization System, an appliance that manages multiple disk arraystorage systems.

TID Target ID.

Volume On the XP array, a volume is a uniquely identified virtual storage devicecomposed of a control unit (CU) component and a logical device (LDEV)

Glossary38

component separated by a colon. For example 00:00 and 01:00 are twouniquely identified volumes; one is identified as CU = 00 and LDEV = 00, andthe other as CU = 01 and LDEV = 00; they are two unique separate virtualstorage devices within the XP array.

VSC Volume size customization. Synonymous with CVS.

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

XP CommandView

HP StorageWorks XP Command View, a software product for managing XParrays. XP Command View runs on a Windows-based management workstation.

XP Remote WebConsole

HP StorageWorks XP Remote Web Console. A browser-based program installedon the SVP that allows you to configure and manage the disk array.


Glossary40

Index

Aarbitrated-loop physical address, 16audience, 7

Cclustering, 23command device(s)

designate at least one LDEV as a, 13command device(s)

XP RAID Manager, 13Command View XP Advanced Edition Software,11Command View XP Advanced Edition Software,13, 15, 25Command View XP Advanced Edition Software, 14configuration

device, 26emulation types, 12

Fibre Channel ports, 16HBAs, 17host, 17port, 16System Mode, 15Veritas Volume Manager, 28

conventionsdocument, 8storage capacity values, 9

Ddevice(s)

configuring, 26emulation types, 12labeling, 26logical, not recognized by host, 30partitioning, 26type specifications, 34verifying recognition, 26vxinstall aborts after detection, 30

disk array(s)Not Ready error message, 30self reboots, 30

disk array(s)connecting, 24features, 11installation overview, 13operating system versions, 11requirements, 11storage capacity, 11

documentconventions, 8related documentation, 7

documentationHP website, 7providing feedback, 10

Eemulation(s)

device emulation types, 12supported, 33

error conditions, 29

Ffabric environment

port addresses, 16zoning, 23

failover, 12features, disk array, 11Fibre Channel

connection speed, 12interface, 12ports, configuring, 16supported elements, 12

file system(s)cannot be created, 30creating, 27not mounted after rebooting, 30

Gglossary, 37


HHBA(s)

configuring, 17driver not attached, 30Emulex, 19JNI, 21Qlogic, 20Sun, 18supported, 17verifying configuration, 25

helpobtaining, 9

hostconfiguration, 17doesn't reboot properly, 30

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

setting, 14HP

service representative tasks, 14technical support, 9, 31

Iinstallation, 11

HP service representative tasks, 14overview, 13

interface, Fibre Channel, 12

Llabeling devices, 26LDEV(s)

designate at least one as a command device,13

LUN(s)creating, 25mapping, 25security, 23

Mmulti-cluster environment, 23

Ooperating system(s)

loading, 17LUN security for, 24multiple, fabric zoning for, 24supported versions, 11

Pparity error, 30

partitioning devices, 26path(s)

adding, 26defining, 25SCSI, 26

port(s)address, 16Fibre Channel, 16

RR-SIMS, 29related documentation, 7Remote Web Console, 11requirements, disk array, 11

SSCSI disk, Fibre Channel interface and term"SCSI disk", 12Secure Manager XP, 24security, LUN, 23server(s), supported, 11storage capacity, 11storage capacity values

conventions, 9Subscriber's Choice, HP, 9System Mode, setting, 15

Ttechnical support, 31

HP, 9service locator website, 10

troubleshooting, 29error conditions, 29technical support, 31

VVeritas Volume Manager

configuration, 28Veritas Volume Manager

disks not visible, 30vxinstall

aborts after device detection, 30VxVM, see "Veritas Volume Manager", 30

Wwebsites

HP , 10HP Subscriber's Choice for Business, 9product manuals, 7

42

XXP Array Manager, 11, 14, 25XP arrays

storage capacity, 11XP Business Copy Software, 13XP Command View, 11, 13, 14, 15, 25XP Continuous Access Software, 13XP RAID Manager command devices, 13XP Remote Web Console, 14XP Remote Web Console, 13, 15, 25

Zzoning, fabric, 23


44

Date post:	20-Jul-2016
Category:	Documents
Upload:	naga-karthik
View:	10 times
Download:	0 times

HPstorageon SOlaris

Documents