Ctl-B/FP-1/Optimized/dev/rdsk/c17t1d6 5000-1FE1-5007-DBD0

6005-08B4-0010-78F1-0000-E000-0034-0000 25600MB

Ctl-B/FP-3/Optimized/dev/rdsk/c18t1d6 5000-1FE1-5007-DBD0

6005-08B4-0010-78F1-0000-E000-0034-0000 25600MB

Ctl-B/FP-2/Optimized/dev/rdsk/c19t1d6 5000-1FE1-5007-DBD0

6005-08B4-0010-78F1-0000-E000-0034-0000 25600MB

Ctl-B/FP-4/Optimized

For more information on using the EVAInfo tool, see HP StorageWorks EVAInfo Release Notes.

Identifying Special Device Files for Native Multi-pathing

With HP-UX 11i v3, Secure Path is no longer supported. The mass storage stack in HP-UX 11i v3 provides native multi-pathing functionality, distributing I/O requests transparently across all available lunpaths to the LUN. Use the HP-UX native multi-pathing for identifying special device files.

Following is the sample output of the evainfo command on HP-UX 11i v3 that uses agile Device Special File (DSF) naming convention:

# evainfo

-P -w wwn

 

 

Devicefile

Array

WWNNCapacity

Controller/Port/Mode

/dev/rdisk/disk10

5000-1FE1-5007-DBA0

 

6005-08B4-0010-786B-0000-A000-02DB-0000

2048MB

Ctl-A/FP-3/NonOptimized

 

 

Creating Volume Groups using Source Volumes for Secure Path v3.0D, v3.0E, and v3.0F

Use the following procedure to create volume groups for source volumes and export them for access by other nodes.

NOTE: Create volume groups only for source storage on a locally connected EVA unit. To create volume groups for source volumes on EVA unit located at the remote site, it is necessary to log onto a node located at that site before configuring the volume groups.

1.Define the appropriate Volume Groups on each node that might run the application package. Use the following commands:

#mkdir /dev/vgname

#mknod /dev/vgxx/group c 64 0xnn0000

where the name /dev/vgxx and the number nn are unique within the cluster.

2.Create the Volume Groups on source volume. Use the following commands: pvcreate -f /dev/rdsk/cxtydz

vgcreate /dev/vgname /dev/dsk/cxtydz

3.Create the logical volume(s) for the volume group.

4.De-activate the Volume Groups.

#vgchange -a n /dev/vgname

5.Start the cluster and clusterize the Volume Groups.

#cmruncl (if cluster is not already up and running)

#vgchange -c y /dev/vgname

6.Test activating the Volume Groups with exclusive option.

#vgchange -a e /dev/vgname

7.Create a back-up config file that will contain the cluster ID, having already an ID on disks/ luns.

#vgcfgbackup /dev/vgname

Preparing a Serviceguard Cluster for Metrocluster Continuous Access EVA 227