HP StorageWorks XP24000, StorageWorks XP20000, StorageWorks XP12000, StorageWorks XP10000, StorageWorks SVS 200 XP Disk Array Configuration Guide for Linux
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211
and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items
are licensed to the U.S. Government under vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set
forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.
• 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.
Conventions for storage capacity values
HP XP storage systems use the following values to calculate physical storage capacity values (hard
disk drives):
• 1 KB (kilobyte) = 1,000 bytes
•
1 MB (megabyte) = 1,0002 bytes
•
1 GB (gigabyte) = 1,0003 bytes
Preface8
Page 9
•
1 TB (terabyte) = 1,0004 bytes
HP XP storage systems use the following values to calculate logical storage capacity values (logical
devices):
• 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
Graphical interface illustrations
The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer
browser. Actual windows may differ depending on the operating system and browser used. GUI
contents also vary with licensed program products, storage system models, and firmware versions.
HP technical support
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
• Product model names and numbers
• Technical support registration number (if applicable)
• Product serial numbers
• Error messages
• Operating system type and revision level
• Detailed questions
Subscription service
HP 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.
HP websites
For 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
XP Disk Array Configuration Guide for Linux9
Page 10
Documentation feedback
HP welcomes your feedback.
To make comments and suggestions about product documentation, please send a message to
1 Installing and configuring Linux for the
XP disk array
You and your HP service representative each play a role in installation. Your HP service representative
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 assistance from your HP service representative.
Features and requirements
Ask 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 ports
XP12000: Up to 1152 drives for up to 332 TB, 128 FC ports
XP20000: Up to 240 drives for up to 69.2 TB, 48 FC ports
XP24000: Up to 1152 drives for up to 332 TB, 256 FC ports
SVS 200: Up to 127 TB in external storage, 48 FC ports
• Server support: Server supported by HP to run Linux. Consult your HP representative for a list of
supported servers.
• Operating system support: Check with your HP representative for the current OS versions supported
by your XP disk array.
Before installing the disk array, ensure the following requirements are met:
• Fibre Channel Port configuration: Configure each Fibre Channel port on the disk array so it has
a unique Fibre Channel loop ID. (All ports are set to 0 by default at the factory.)
• Linux version: Confirm you are using Red Hat, SuSE, or United Linux.
• Superuser access: Make sure you have superuser (root) login access to the Linux system.
• Fibre Channel Adapter (FCAs): Install FCAs and all utilities and drivers. Refer to the adapter
documentation for installation details
• (Recommended) HP StorageWorks XP Remote Web Console, HP StorageWorks XP Command
View Advanced Edition Software or HP StorageWorks XP Command View with LUN management
feature 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.
Fibre Channel interface
The XP family of disk arrays and the SVS 200 support these Fibre Channel elements:
• 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 array
devices are defined to the host as SCSI disks.
Device emulation types
The XP family of disk arrays and the SVS 200 support these device emulation types:
• OPEN-x devices: OPEN-x logical units represent disk devices. Except for OPEN-V, these devices
are based on fixed sizes. OPEN-V is a user-defined size based on a CVS device. 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 36 OPEN-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.
are smaller than normal fixed-sized logical disk devices (volumes). OPEN-V is a CVS-based custom
disk size that you determine. OPEN-L does not support CVS. Although OPEN-V is a CVS-based
device, the product name in the SCSI inquiry string is OPEN-V opposed to the fixed size
OPEN-[389E] devices that appear as OPEN-x-CVS.
• LUSE (expanded) CVS devices (OPEN-x*n CVS): LUSE CVS combines CVS devices to create an
expanded device. This is done by first creating CVS custom-sized devices 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, this device is designated as OPEN-9*3-CVS. OPEN-V devices are
designated as OPEN-V*n (without CVS).
NOTE:
For the SVS 200, and the XP24000/XP20000/XP12000/XP10000 when connected to external storage
devices, HP recommends using OPEN-V as the emulation the array makes visible to the host. This allows
configuration of external storage LDEVs without losing data. Using any other emulation may cause data
loss in the external storage LUNs. For new deployments, OPEN-V should be chosen because some features
(such as XP Snapshot or Continuous Access Journal) are only supported with OPEN-V.
Refer to Table 8 on page 30 for detailed information.
Partitions
In a Linux environment, one LUN can be divided into a maximum of four primary partitions (using
fdisk) or maximum of one extended partition.
Failover
The disk arrays support many standard software products that provide host, application, or I/O path
failover and management.
Installing and configuring Linux for the XP disk array12
Page 13
SNMP configuration
The XP family of disk arrays and the SVS 200 support standard Simple Network Management Protocol
(SNMP) for remotely managing arrays. The SNMP agent on the service processor (SVP) performs
error-reporting operations requested by the SNMP manager. SNMP properties are usually set from
the SVP but they can also be set remotely using XP Remote Web Console, XP Command View (XP
arrays only), or XP Command View Advanced Edition Software. Refer to the applicable user's guide
for procedures.
Figure 1 SNMP configuration
XP RAID Manager command devices
HP StorageWorks XP RAID Manager manages HP StorageWorks XP Business Copy Software or HP
StorageWorks XP Continuous Access Software operations from a host server. To use XP RAID Manager
you must designate at least one LDEV as a command device. This can be done with XP Remote Web
Console, XP Command View (XP arrays only), or XP Command View Advanced Edition Software to
. Refer to the applicable user guide for information about how to designate a command device.
Installation roadmap
Perform these actions to install and configure the disk array:
1.Installing and configuring the disk array
• Setting the host mode and host group mode
• Configuring the Fibre Channel ports
• Setting the System Option Modes
2.Installing and configuring the host
• Installing and configuring the FCAs
• Loading the operating system and software
• Clustering and fabric zoning
• Fabric zoning and LUN security for multiple operating systems
3.Connecting the disk array
• Restarting the Linux server
• Verifying new device recognition
• Defining the paths
4.Configuring disk array devices
• Partitioning the devices
XP Disk Array Configuration Guide for Linux13
Page 14
• Creating the file systems
• Creating the mount directories
• Creating the mount table
• Verifying file system operation
Installing and configuring the disk array
The 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 (XP arrays
only), XP Command View Advanced Edition Software, or XP Array Manager to complete the remaining
tasks listed below. If you do not have these programs, your HP service representative can perform
these tasks for you.
Setting the host mode and host group mode for the disk array ports
After the disk array is installed, you must set the host mode for each disk array port to match the host
OS. Set the host mode using LUN Manager in XP Remote Web Console (shown), XP Command View
(XP arrays only), or XP Command View Advanced Edition Software. If these are not available, the
HP service representative can set the host mode using the SVP. The host mode setting for Linux is 00.
Test.
CAUTION:
The correct host mode must be set for all new installations (newly connected ports) to Linux hosts. Do not
select a mode other than 00 for Linux. Changing a host mode after the host has been connected is disruptive
and requires the server to be rebooted.
When a new host group is added, additional host group modes (options) may be configured. The
storage administrator must verify if an additional host group mode is required for the host group.
Installing and configuring Linux for the XP disk array14
Page 15
The following host group mode (option) is available for :
Table 2 Host group mode (option)
Group
Mode
CAUTION:
Changing host group modes for ports where servers are already installed and configured is disruptive and
requires the server to be rebooted.
Configuring the Fibre Channel ports
Configure the disk array Fibre Channel ports by using XP Remote Web Console (shown), XP Command
View (XP arrays only), or XP Command View 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 the array through the same switch.
CommentsDefaultFunctionHost
Previously MODE249InactiveReporting Unit Attention when adding LUN7
XP Disk Array Configuration Guide for Linux15
Page 16
Fabric and Connection parameter settings
Set each array port to FABRIC ON or OFF with connections of POINT-TO-POINT or FC-AL as shown
in the following figures and table. For detailed topology information, refer to the HP StorageWorksSAN Design Reference Guide at
http://www.hp.com/go/sandesign.
Figure 2 Simple point-to-point fabric topology example
Table 3 Fabric topology settings
ProvidesConnection parameterFabric parameter
FC-ALOFF
Installing and configuring Linux for the XP disk array16
Not supportedFC-ALON
FL-port (private arbitrated loop;
direct connect without a SAN)
N-port (SAN fabric port)Point-to-PointON
Not supportedPoint-to-PointOFF
Page 17
Fibre address
In 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 for
each port. For specific values, refer to the HP StorageWorks XP LUN Manager User's Guide applicable
to your array.
Setting the System Option Modes
The HP service representative sets the System Option Mode(s) based on the operating system and
software configuration of the host. Notify your HP representative if you install storage agnostic software
(such as backup or cluster software) that may require specific settings.
Installing and configuring the host
This section explains how to install and configure Fibre Channel adapter (FCAs) that connect the host
to the disk array.
Installing and configuring the FCAs
Install and configure the Fibre Channel adapters using the FCA manufacturer's instructions.
On Linux systems, the disk array only supports QLogic and Emulex adapters. Contact your HP service
representative for the latest information about supported FCAs.
Loading the operating system and software
Follow the manufacturer's instructions to load the operating system and software onto the host. Load
all OS patches and configuration utilities supported by HP and the FCA manufacturer.
Clustering and fabric zoning
If 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-cluster
environment with three clusters, each containing two nodes. The nodes share access to the disk array.
XP Disk Array Configuration Guide for Linux17
Page 18
Figure 3 Multi-cluster environment
Within the Storage Area Network (SAN), the clusters may be homogeneous (all the same operating
system) or they may be heterogeneous (mixed operating systems). How you configure LUN security
and fabric zoning depends on the operating system mix and the SAN configuration.
Fabric zoning and LUN security for multiple operating systems
You can connect multiple clusters of various operating systems to the same switch and fabric using
appropriate 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 can
access.
Table 4 Fabric zoning and LUN security settings
LUN SecurityFabric ZoningOS MixEnvironment
Standalone SAN
(non-clustered)
Clustered SAN
Multi-Cluster SAN
present in the SAN)
type present in the SAN)
Connecting the disk array
The HP service representative connects the disk array to the host by:
• Verifying operational status of the disk array channel adapters, LDEVs, and paths.
• Connecting the Fibre Channel cables between the disk array and the fabric switch or host.
• Verifying the ready status of the disk array and peripherals.
Installing and configuring Linux for the XP disk array18
Not requiredhomogeneous (a single OS type
Requiredheterogeneous (more than one OS
Must be used when
multiple hosts or cluster
nodes connect through a
shared port
Page 19
Restarting the Linux server
To recognize the new device(s), restart the Linux server as follows:
1.Power on the display of the Linux server.
2.Power on all devices other than the Linux server.
3.Confirm ready status of all devices.
4.Power on the Linux server.
Verifying new device recognition
1.Verify that the FCA driver is installed using the lsmod command.
2.View the device information in the /proc/scsi/scsi file.
In the above example, the “sd” devices represent the XP disk partitions and the “cciss” devices
represent the internal hard drive partitions on an HP Proliant system.
Defining the paths
Use XP Remote Web Console (shown), XP Command View (XP arrays only), or XP Command View
Advanced Edition Software 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 Fibre Channel adapter WWNs to host groups
• Mapping volumes (LDEVs) to host groups (by assigning LUNs)
In XP Command View 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 XP CommandView Advanced Edition Software Device Manager Web Client User's Guide. Note the LUNs and
their ports, WWNs, nicknames, and LDEVs for later use in verifying host and device configuration.
Installing and configuring Linux for the XP disk array20
Page 21
Configuring disk array devices
Disks in the disk array are configured using the same procedure for configuring any new disk on the
host. This includes the following procedures:
1.Partitioning the devices
2.Creating the file systems
3.Creating the mount directories
4.Creating the mount table
5.Verifying file system operation
Creating scripts to configure all devices at once may save you considerable time.
Partitioning the devices
After the device parameters have been set, the next step is to set the partitions. To partition the devices:
1.Enter fdisk/dev/device_name.
Example
# fdisk/dev/sda
2.Select p to display the present partitions.
3.Select n to make a new partition. You can make up to four primary partitions or you can make
one extended partition. The extended partition can be divided into a maximum of 11 logical
partitions, which can be assigned partition numbers from 5 to 15.
4.Select w to write the partition information to disk and complete the fdisk command.
5.Other commands that you might want to use include:
d to remove partitions
q to stop a change
6.Repeat the above steps for each device.
Creating the file systems
The supported file system for Linux is ext2.
Creating file systems with ext2
1.Enter mkfs –t ext2 /dev/device_name.
Example
# mkfs –t ext2 /dev/sdd
XP Disk Array Configuration Guide for Linux21
Page 22
2.Repeat step 1 for each device on the disk array.
Creating the mount directories
Create mount directories using the mkdir command. Choose names for the mount directories which
identify both the logical volume and partition.
1.Enter mkdir /mnt/mount_point.
Example
# mkdir /mnt/A5700F_LU00
2.Repeat step 1 for each device on the disk array.
Creating the mount table
Add the new devices to the /etc/fstab file to specify the automount parameters for each device.
1.Edit the /etc/fstab file to add one line for each device to be automounted.
Each line of the file contains: (A) device name, (B) mount point, (C) file system type (“ext2”), (D)
mount options (“defaults”), (E) enhance parameter (“1”), and (F) fsck pass 2.
Example
/dev/sdb /A5700F_ID08 ext2 defaults 1 2
/dev/sdc /A5700F_ID09 ext2 defaults 1 2
/dev/sdd /A5700F_ID10 ext2 defaults 1 2
A B C D E F
Make an entry for each device. After all the entries are made, save the file and exit the editor.
Installing and configuring Linux for the XP disk array22
Page 23
2.Reboot the system.
3.Display the mounted devices using the df –h command and verify that the devices were
Verify file system operation by copying a file to each device.
XP Disk Array Configuration Guide for Linux23
Page 24
Installing and configuring Linux for the XP disk array24
Page 25
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 26.
Error conditions
Depending on your system configuration, you may be able to view error messages (R-SIMS) as follows:
• In XP Remote Web Console (Status tab)
• In XP Command View Advanced Edition Software (Alerts window)
• In XP Command View (Event History or Event Notification windows) (XP arrays only)
Table 5 Error conditions
recognized by the host.
Recommended actionError condition
Verify the following:The logical devices are not
• The READY indicator lights on the disk array are ON.
• Fiber cables are correctly installed and firmly connected.
• The target IDs are properly configured. The LUNs for each TID must
start at 0 and continue sequentially without skipping any numbers.
• The TIDs/WWNs on each bus are unique. Do not install two
devices with the same ID on the same bus. Recheck the buses for
new devices.
• LUSE devices are not intermixed with normal LUNs on the same
port.
• The maximum number of LUSE devices per port has not been
exceeded.
• The disk array host mode is set correctly.
The host does not reboot properly
after hard shutdown.
Logical volumes cannot be created.
rebooting.
If you power off the host without executing the shutdown process, wait
three minutes to allow the disk array's internal timeout process to purge
queued commands. If the host restarts while the disk array is processing
queued commands, the host may not reboot successfully.
Verify that the disk array logical devices are correctly formatted.Physical volumes cannot be created.
Verify that the volume capacity for OPEN-x volumes is not greater than
the maximum capacity allowed. See “Disk array supported
emulations” on page 29.
Verify that the capacity of the volume group is not less than the total
capacity of the partitioned logical volume.
Verify that the host was restarted correctly.A file system is not mounted after
Verify that the file system attributes are correct.
XP Disk Array Configuration Guide for Linux25
Page 26
because the disk array was busy or
it logged a panic message.
or the disk array has displayed “Not
Ready” and timed out.
Recommended actionError condition
Reboot the host.The disk array performs a self reboot
Contact HP.The disk array responds “Not Ready”
The host detects a parity error.
The host hangs or devices are
declared and the host hangs.
Check the FCA and make sure it was installed properly. Reboot the
host.
Make sure there are no duplicate disk array TIDs and that disk array
TIDs do not conflict with any host TIDs.
Calling the HP support center
If you are unable to resolve an error condition, contact the HP support center for assistance.
Contact information
Telephone numbers for worldwide technical support are listed on the HP support web site:
http://www.hp.com/support/.
Before you call
Be 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.
Troubleshooting26
Page 27
A Path worksheet
Worksheet
Table 6 Path worksheet
control unit)
Device TypeLDEV (CU:LDEV) (CU =
Number
Alternate PathsPath 1SCSI Bus
TID:TID:TID:0:00
LUN:LUN:LUN:
TID:TID:TID:0:01
LUN:LUN:LUN:
TID:TID:TID:0:02
LUN:LUN:LUN:
TID:TID:TID:0:03
LUN:LUN:LUN:
TID:TID:TID:0:04
LUN:LUN:LUN:
TID:TID:TID:0:05
LUN:LUN:LUN:
TID:TID:TID:0:06
LUN:LUN:LUN:
TID:TID:TID:0:07
LUN:LUN:LUN:
TID:TID:TID:0:08
LUN:LUN:LUN:
TID:TID:TID:0:09
LUN:LUN:LUN:
TID:TID:TID:0:10
LUN:LUN:LUN:
XP Disk Array Configuration Guide for Linux27
Page 28
Path worksheet28
Page 29
B Disk array supported emulations
This appendix provides information about supported emulations and device type specifications. Some
parameters may not be relevant to your array. Consult your HP representative for information about
supported configurations for your system.
Supported emulations
HP recommends using OPEN-V as the emulation for better performance and features that may not be
supported with the legacy emulations (OPEN-[389LE]).
Table 7 Supported emulations
LUSE & CVSCVSLUSEFixed SizeEmulationXP model
YesYesYesYesOPEN-3
YesYesYesYesOPEN-8XP10000
YesYesYesYesOPEN-9XP12000
YesYesYesYesOPEN-EXP20000
OPEN-KXP24000
YesYesOPEN-LSVS 200
OPEN-M
YesYesOPEN-V
NOTE:
For the SVS 200, and the XP24000/XP20000/XP12000/XP10000 when connected to external storage
devices, HP recommends using OPEN-V as the emulation the array makes visible to the host. This allows
external storage LDEVs to be configured without losing data. Using any other emulation may cause data
loss in the external storage LUNs.
The value n is the number of volumes combined together. For example, with 8 combined volumes:
OPEN-V*8.
The availability of an emulation depends on the disk array.
The devices are defined to the host as SCSI disk devices, even though the interface is Fibre Channel.
The command device (used for XP Raid Manager) is distinguished by -CM on the product name (for
example, OPEN-3-CM, OPEN-3-CVS-CM).
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.
The number of blocks for a CVS volume is calculated as follows:
# of blocks = (# of cylinders) × (# of heads) × (# of sectors per track)
Note 6:
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
The number of cylinders for a CVS volume is calculated as follows ( ... means that the value 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
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 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
XP Disk Array Configuration Guide for Linux31
Page 32
Note 7:
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
The capacity of an OPEN-3/8/9/E CVS volume is specified in MB, not number of cylinders. The
capacity of an OPEN-V CVS volume can be specified in MB or number of cylinders. You set the
volume size using XP Remote Web Console, XP Command View (XP arrays only), or XP Command
View Advanced Edition Software.
Disk array supported emulations32
Page 33
Glossary
AL-PAArbitrated loop physical address.
array groupA group of 4 or 8 physical hard disk drives (HDDs) installed in an XP disk array
command deviceA volume on the disk array that accepts XP Continuous Access Software or XP
CUControl Unit. Contains LDEVs and is approximately equivalent to SCSI Target ID.
emulation modesThe logical devices (LDEVs) associated with each RAID group are assigned an
and 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 consist
of 4 (3D+1P) or 8 HDDs (7D+1P). All RAID6 array groups are made up of 8
HDDs (6D+2P).
Business Copy Software control operations which are then executed by the disk
array.
using array management software to be smaller than normal fixed-size OPEN
system volumes. Synonymous with volume size customization (VSC). OPEN-V is
a CVS-based volume.
emulation mode that makes them operate like OPEN system disk drives. The
emulation mode determines the size of an LDEV:
OPEN-3: 2.46 GB
OPEN-8: 7.38 GB
OPEN-9: 7.42 GB
OPEN-E: 13.56 GB
OPEN-L: 36 GB
OPEN-V: User-defined custom size
failoverUsing an alternate unit or path instead of a failed unit or path in order to continue
functioning.
FCFibre Channel.
FCAFibre Channel Adapter.
FC-ALFibre Channel arbitrated loop.
FCPFibre Channel Protocol.
HBAHost bus adapter.
host modeEach port can be configured for a particular host type. These modes are
represented as two-digit hexadecimal numbers. For example, host mode 08
represents an HP-UX host.
LDEVLogical device. An LDEV is created when a RAID group is carved into pieces
according to the selected host emulation mode (that is, OPEN-3, OPEN-8,
XP Disk Array Configuration Guide for Linux33
Page 34
OPEN-E). The number of resulting LDEVs depends on the selected emulation
mode. The term LDEV is often used synonymously with the term volume.
LUNLogical 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 the
emulation 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,693
MB.
LUSEA LUN is normally associated with only a single LDEV. The LUSE feature allows
a LUN to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible
for applications to access a single large pool of storage. The LUSE feature is
available when the HP StorageWorks XP Array Manager product is installed.
OFCOpen Fibre Control.
OPEN-
x
A general term describing any one of the supported OPEN emulation modes (for
example, OPEN-E. There are two types of OPEN-x devices: legacy OPEN-x
devices with a fixed size (such as, OPEN-3, OPEN-8, OPEN-9, OPEN-E), and
OPEN-V, which has a variable size and is a CVS-based volume.
PAPhysical address.
path“Path” and “LUN” are synonymous. Paths are created by associating a port and
a LUN ID with an LDEV.
portA physical connection that allows data to pass between a host and the disk
array. The number of ports on an XP disk array depends on the number of
supported I/O slots and the number of ports available per I/O adapter. The XP
family of disk arrays supports Fibre Channel (FC) ports as well as other port
types. Ports are named by port group and port letter, such as CL1-A. CL1 is the
group, and A is the port letter.
RAIDRedundant array of independent disks.
R-SIMRemote service information message.
SCSISmall computer system interface.
SIMService information message.
SNMPSimple Network Management Protocol.
SVPService processor, which is the PC built into the disk array. The SVP provides a
direct interface into the disk array. SVP use is reserved for HP support
representatives only.
SVSStorage Virtualization System, an appliance that manages multiple disk array
storage systems.
TIDTarget ID.
VolumeOn the XP array, a volume is a uniquely identified virtual storage device
composed of a control unit (CU) component and 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, and
the other as CU = 01 and LDEV = 00; they are two unique separate virtual
storage devices within the XP array.
Glossary34
Page 35
VSCVolume size customization. Synonymous with CVS.
WWNWorld Wide Name. A unique identifier assigned to a Fibre Channel device.
XP Command
View
XP Command
View Advanced
Edition Software
XP Remote Web
Console
HP StorageWorks XP Command View, a software product for managing XP
arrays. XP Command View runs on a Windows-based management workstation.
HP StorageWorks XP Command View Advanced Edition Software, installs on
the user-provided Device Manager server and provides a browser-based platform
from which you can manage the SVS 200 and the XP family of disk arrays—even
globally distributed arrays.
HP StorageWorks XP Remote Web Console. A browser-based program installed
on the SVP that allows you to configure and manage the disk array.