Emc Tru64 Guide

7/25/2019 Emc Tru64 Guide

1/176

EMC Corporation

Corporate Headquarters:

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

EMCHost Connectivity Guide

for Tru64 UNIX

P/N 300-000-616REV A25


2/176

EMC Host Connectivity Guide for Tru64 UNIX2

Copyright 2003 2012 EMC Corporation. All rights reserved.

Published October, 2012

EMC believes the information in this publication is accurate as of its publication date. The information issubject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THISPUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the UnitedState and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulator document for your product line, go to EMC Online Support(https://support.emc.com).


3/176

EMC Host Connectivity Guide for Tru64 UNIX 3

Preface............................................................................................................................ 13

PART 1 Symmetrix Connectivity

Chapter 1 Tru64 UNIX/Symmetrix Environment

Overview............................................................................................ 20Patches and online documentation..........................................20

Enginuity minimum requirements................................................. 21Tru64 UNIX commands and utilities ............................................. 23Tru64 UNIX devices.......................................................................... 24

Device naming conventions......................................................24Disk label and device partitions ...............................................25

Using file systems ............................................................................. 26Creating and mounting the UNIX file system........................26AdvFS ...........................................................................................26Creating and mounting an AdvFS...........................................27Reconstructing an AdvFS domain ...........................................28LUN expansion ...........................................................................28

Logical storage manager.................................................................. 30Example 1: Setting Up LSM .....................................................30Example 2: Creating a mirrored volume.................................31Example 3: Creating a four-way striped volume...................32

System and error messages ............................................................. 34

Contents


4/176


Contents

Chapter 2 Virtual Provisioning

Virtual Provisioning on Symmetrix ............................................... 36Terminology................................................................................37Thin device ..................................................................................38

Implementation considerations ...................................................... 41Over-subscribed thin pools.......................................................42Thin-hostile environments ........................................................ 42Pre-provisioning with thin devices in a thin hostileenvironment ................................................................................43

Host boot/root/swap/dump devices positioned onSymmetrix VP (tdev) devices ................................................... 44Cluster configurations ............................................................... 45

Symmetrix Virtual Provisioning in a Tru64 UNIXenvironment ...................................................................................... 46

Tru64 UNIX Virtual Provisioning support.............................47Precaution considerations ......................................................... 47Unbound thin devices................................................................ 48

Chapter 3 Tru64 UNIX and Symmetrix over Fibre Channel

Tru64 UNIX/Symmetrix Fibre Channel environment................ 52Hardware connectivity ..............................................................52Boot device support ................................................................... 52Logical devices............................................................................52Symmetrix configuration........................................................... 53

Port sharing ................................................................................. 55Host configuration with Compaq HBAs....................................... 56

Planning zoning and connections ............................................ 56Installing the HBA...................................................................... 56Configuring boot support ......................................................... 57Rebuilding the Tru64 UNIX kernel.......................................... 58Upgrading the Tru64 UNIX Fibre Channel driver ................58Adding the Symmetrix device entry ....................................... 59

V4.0F/V4.0G notes ..................................................................... 60V5.x notes..................................................................................... 61

Addressing Symmetrix devices...................................................... 63Arbitrated loop addressing....................................................... 63Fabric addressing........................................................................ 64SCSI-3 FCP addressing .............................................................. 65


5/176

5EMC Host Connectivity Guide for Tru64 UNIX

Contents

Chapter 4 Tru64 UNIX and Symmetrix over SCSI

Symmetrix configuration ................................................................. 68Host configuration ............................................................................ 69

Installing the HBA ..................................................................... 69Scanning and configuring a boot device .................................69Rebuilding the Tru64 UNIX kernel ..........................................70Adding the Symmetrix device entry to the ddr.dbase..........70

Device management ......................................................................... 72Adding and managing devices.................................................72

Chapter 5 TruCluster Servers

TruCluster V1.6 overview ................................................................ 76Available Server ..........................................................................76Production Server .......................................................................76TruCluster V1.6 services ............................................................76asemgr...........................................................................................77

TruCluster V1.6 daemons and error logs ................................78TruCluster V1.6 with Symmetrix .................................................... 79

Symmetrix connectivity .............................................................79Symmetrix configuration...........................................................81Additional documentation ........................................................82

TruCluster V5.x overview ................................................................ 83Connection manager...................................................................83Device request dispatcher..........................................................84

Cluster File System .....................................................................85Cluster Application Availability...............................................86

TruCluster V5.x with Symmetrix .................................................... 87Symmetrix connectivity .............................................................87TruCluster V5.x system disk requirements.............................89Symmetrix configuration...........................................................89Direct-access device and DRD barrier configuration ............90Persistent reservations................................................................94Additional documentation ........................................................95

PART 2 VNX Series and CLARiiON Connectivity

Chapter 6 Tru64 UNIX Hosts with VNX Series and CLARiiON

Tru64 UNIX in a VNX series and CLARiiON environment ..... 100

Host connectivity ......................................................................100Boot device support..................................................................100


6/176


Contents

Logical devices..........................................................................100General configuration overview ............................................ 100

Host configuration with Compaq HBAs..................................... 102Installing the HBA.................................................................... 102Creating an entry in ddr.dbase............................................... 103Upgrading the Tru64 UNIX Fibre Channel HBA driver .... 107Rebuilding the Tru64 UNIX kernel........................................ 107Zoning HBA connections ........................................................ 108Setting the UDID ......................................................................108

Setting connection properties ................................................. 109Creating a storage group......................................................... 112Booting from the VNX series and CLARiiON storagesystem............................................................................................... 115

Preparatory steps......................................................................116Establish preliminary zone .....................................................116Create initiator record..............................................................116Binding the boot LUN..............................................................116

Preparing the SRM console boot device................................ 117Installing Tru64 UNIX ............................................................. 119Completing zoning................................................................... 119Updating connection information..........................................119Updating SRM console information...................................... 120Setting BOOTDEF_DEV .......................................................... 120

TruCluster configurations and persistent reservations............. 122Enabling persistent reservations ............................................ 122

Performing a new TruCluster installation............................126Configuring LUNs on the host ..................................................... 128

HBA management.................................................................... 128Device naming ..........................................................................128Adding devices .........................................................................129LUN trespassing and path failover........................................ 130Multipath configurations ........................................................ 130LUN expansion .........................................................................131

PART 3 Appendix

Appendix A Methods of Data Migration

Tru64 UNIX V5 overview .............................................................. 136Device naming ......................................................................... 136Disk labels................................................................................. 136Logical Storage Manager........................................................ 137Advanced File System ............................................................ 137


7/176

7EMC Host Connectivity Guide for Tru64 UNIX

Contents

Data migration methods ................................................................ 138

Migration of file systems using vdump/vrestore............... 138Migration of AdvFS domains using addvol/rmvol ........... 141Data migration using LSM mirroring ................................... 143Storage-based data migration .................................................145

System and boot device migration ............................................... 148Tru64 UNIX V5 system and boot device migration ............ 148TruCluster V5 system and boot device migration............... 151

Related documentation .................................................................. 170

Index .............................................................................................................................. 171


8/176


Contents


9/176


Title Page

1 Partitioning layout using default disk type ................................................ 252 Virtual Provisioning on Symmetrix ............................................................. 363 Thin device and thin storage pool containing data devices ..................... 404 ASE cluster cabling ........................................................................................ 805 Basic TruCluster V5.x configuration using Symmetrix devices .............. 886 Storage system properties and the base UUID ........................................ 1097 Connectivity status window ....................................................................... 1108 Register Initiator Record window .............................................................. 1119 Storage Group Properties window, General tab ..................................... 11210 Storage Group Properties window, LUN tab .......................................... 11311 Storage Group Properties window, Host tab ........................................... 11412 Storage group properties with host LUN unit ID ................................... 118

Figures


10/176


Figures


11/176


Title Page

1 Minimum Enginuity requirements ...............................................................212 Tru64 UNIX commands and utilities ...........................................................233 FC-AL addressing parameters ......................................................................644 Symmetrix SCSI-3 addressing modes ..........................................................665 Tru64 UNIX SCSI device support .................................................................686 Device management commands and utilities .............................................72

Tables


12/176


Tables


13/176


Preface

As part of an effort to improve and enhance the performance and capabilitiesof its product line, EMC from time to time releases revisions of its hardwareand software. Therefore, some functions described in thisdocument might

not be supported by all revisions of the software or hardware currently inuse. For the most up-to-date information on product features, refer to your

product release notes.

If a product does not function properly or does not function as described inthis document, please contact your EMC representative.

This guide describes the features and setup procedures for Tru64 UNIX host

interfaces to EMC Symmetrix, EMC VNX series, and CLARiiON storagesystems over Fibre Channel or (Symmetrix only) SCSI connections.

Audience This guide is intended for use by storage administrators, systemprogrammers, or operators who are involved in acquiring, managing,or operating EMC Symmetrix, EMC VNX series, and EMCCLARiiON, and host devices.

Readers of this guide are expected to be familiar with the following

topics:

Symmetrix, VNX series, and CLARiiON system operation

HP Tru64 UNIX operating environment


14/176

14 EMC Host Connectivity Guide for Tru64 UNIX

Preface

Relateddocumentation

Related documents include:

EMC Host Connectivity Guide for Compaq True64 UNIX, available atEMC Online Support at https://support.emc.com.

EMC Support Matrix, available throughhttp://elabnavigator.EMC.com

Note: Always refer to the EMC Support Matrixfor the most up-to-dateinformation.

Tru64 UNIX online documentation can be found athttp://h30097.www3.hp.com/docs/pub_page/doc_list.html.

Patches for Tru64 UNIX are available atftp://ftp.itrc.hp.com/patch_bundles/tru64/.

Conventions used inthis guide

EMC uses the following conventions for notes and cautions.

Note: A note presents information that is important, but not hazard-related.

IMPORTANT

An important notice contains information essential to operation ofthe software.

CAUTION

A caution contains information essential to avoid damage to thesystem or equipment. The caution may apply to hardware orsoftware.
https://elabnavigator.emc.com/http://gttp//h30097.www3.hp.com/docs/pub_page/doc_list.htmlhttp://gttp//h30097.www3.hp.com/docs/pub_page/doc_list.htmlhttps://elabnavigator.emc.com/


15/176


Preface

Typographical conventionsEMC uses the following type style conventions in this guide:

Normal Used in running (nonprocedural) text for:

Names of interface elements (such as names of windows,dialog boxes, buttons, fields, and menus)

Names of resources, attributes, pools, Boolean expressions,buttons, DQL statements, keywords, clauses, environmentvariables, filenames, functions, utilities

URLs, pathnames, filenames, directory names, computernames, links, groups, service keys, file systems, notifications

Bold: Used in running (nonprocedural) text for:

Names of commands, daemons, options, programs,processes, services, applications, utilities, kernels,notifications, system call, man pages

Used in procedures for:

Names of interface elements (such as names of windows,dialog boxes, buttons, fields, and menus)

What user specifically selects, clicks, presses, or types

Italic: Used in all text (including procedures) for:

Full titles of publications referenced in text

Emphasis (for example a new term)

Variables

Courier: Used for:

System output, such as an error message or script

URLs, complete paths, filenames, prompts, and syntax whenshown outside of running text

Courier bold: Used for:

Specific user input (such as commands)

Courier italic: Used in procedures for:

Variables on command line

User input variables

< > Angle brackets enclose parameter or variable values supplied bythe user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means or

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from theexample


16/176


Preface

Where to get help EMC support, product, and licensing information can be obtained asfollows.

Product information

For documentation, release notes, software updates, or forinformation about EMC products, licensing, and service, go to theEMC Online Support website at https://support.emc.com.

Technical support

For technical support, go to the EMC Online Support website athttps://support.emc.com. You must have a valid support agreement.Please contact your EMC sales representative for details aboutobtaining a valid support agreement or to answer any questionsabout your account.

Your comments Your suggestions will help us continue to improve the accuracy,organization, and overall quality of the user publications. Please sendyour opinion of this guide to:

[email protected]


17/176

PART 1

Part 1 includes:

Chapter 1, Tru64 UNIX/Symmetrix Environment

Chapter 2, Virtual Provisioning Chapter 3, Tru64 UNIX and Symmetrix over Fibre Channel

Chapter 4, Tru64 UNIX and Symmetrix over SCSI

Chapter 5, TruCluster Servers

Symmetrix Connectivity


18/176


19/176


20/176


Tru64 UNIX/Symmetrix Environment

Overview

When using an EMCSymmetrixsystem in the Tru64 UNIXenvironment, note the following:

The minimum version of Tru64 UNIX supported is V4.0F.

The latest information regarding any restrictions, exceptions,firmware/driver versions, and requirements is listed in theEMC Support Matrix, which is available at

http://elabnavigator.EMC.com

Note: Always refer to theEMC Support Matrixfor the most up-to-dateinformation.

Patches and online documentation

Patches for Tru64 UNIX are available at:

ftp://ftp.itrc.hp.com/patch_bundles/tru64/.

Tru64 UNIX online documentation can be found at:

http://h30097.www3.hp.com/docs/pub_page/doc_list.html
https://elabnavigator.emc.com/http://powerlink.emc.com/http://h30097.www3.hp.com/docs/pub_page/doc_list.htmlhttp://powerlink.emc.com/http://h30097.www3.hp.com/docs/pub_page/doc_list.htmlhttps://elabnavigator.emc.com/


21/176


22/176



Symmetrix DMX-4 Tru64 V5.1B-0 5772.83.755773.79.58

Tru64 V5.1B-1

Tru64 V5.1B-2

Tru64 V5.1B-3

Tru64 V5.1B-4

Tru64 V5.1B-5

Tru64 V5.1B-6

Symmetrix DMX-3 Tru64 V5.1B-0 5771.68.755772.55.515773.79.58Tru64 V5.1B-1

Tru64 V5.1B-2

Tru64 V5.1B-3

Tru64 V5.1B-4

Tru64 V5.1B-5

Tru64 V5.1B-6

Symmetrix DMX-2 Tru64 V5.1B-0 5671.58.64

Tru64 V5.1B-1

Tru64 V5.1B-2

Tru64 V5.1B-3

Tru64 V5.1B-4

Tru64 V5.1B-5

Table 1 Minimum Enginuity requirements (page 2 of 3)

Symmetrix model Tru64 UNIX model Minimum Enginuity code


23/176

Enginuity minimum requirements 23


Symmetrix DMX Tru64 V5.1B-0 5670.23.255671.31.35

Tru64 V5.1B-1

Tru64 V5.1B-2

Tru64 V5.1B-3

Tru64 V5.1B-4

Tru64 V5.1B-5

Symmetrix 8000 Tru64 V5.1B-0 5568.34.14

Tru64 V5.1B-1

Tru64 V5.1B-2

Tru64 V5.1B-3

Tru64 V5.1B-4

Tru64 V5.1B-5

Table 1 Minimum Enginuity requirements (page 3 of 3)

Symmetrix model Tru64 UNIX model Minimum Enginuity code


24/176



Tru64 UNIX commands and utilities

Table 2describes Tru64 UNIX commands and utilities that you canuse to define and manage Symmetrix devices. Use of thesecommands and utilities is optional; they are listed for reference only.

Table 2 Tru64 UNIX commands and utilities

Command or utility Definition

disklabel Displays and partitions a disk device. Some useful parameters for thiscommand are:

-rread label from disk

-rwwrite label to disk

-reuse your default editor to change the default partition sizes

scu Provides a listing and scanning of devices connected to the host.

iostat [device name]

Displays I/O statistics.

You can use sarinstead if System V habitat is installed. (The System V habitatrequires a separate license.)

By default, iostatshows the first four disks in the system (internal) or theLUNs associated with a specified device. For example:

iostat rz16 rz32 5 0

LSM (Logical Storage Manager) Supports mirroring and striping based on Veritas Volume Manager.

You can use three interfaces with LSM commands:

Command l ine:vol*commands

Character_cell:voldiskadm

Motif-based GUI: dxlsm(requires separate license)

Use of LSM system-level mirroring and striping requires the same license asthe GUI.

Refer to Logical storage manager on page 31for more information.

newfs Creates a new UNIX File System (UFS).

mkfdmn, mkfsetCreates a new Advanced File System (AdvFS). AdvFS provides rapid crashrecovery, high performance, and the ability to manage the file system while itis on line.

scsimgr Creates device special files for newly attached disk and tape devices. ThisV4.0x operating system utility is automatically invoked at system boot time.

hwmgr Displays and manages hardware components. This is a V5.x operatingsystem command.

dsfmgr Creates and manages device special files.This is a V5.x operating systemcommand.


25/176

Tru64 UNIX devices 25


Tru64 UNIX devices

This section describes device naming and partitioning conventions inthe Tru64 UNIX environment.

Device naming conventions

V4.0x In the 4.0x versions of the Tru64 UNIX operating system, devicenames (device special files) are determined by bus-target-LUNlocation, in this format:

rz[lun][unit][partition]

where:

[lun] is a letter ranging from b to h, corresponding to LUNs1 through 7. For LUN 0, the LUN letter is omitted.

[unit] is bus number * 8 + target ID number.

[partition] is the letter of the disk partition, from a to h.

Example:

/dev/rrzb16c is the raw device name for partition c of the disk atbus 2 target 0 LUN 1.

/dev/rz28his the block device name for partition h of the disk atbus 3 target 4 LUN 0.

V5.x In the 5.x versions of the Tru64 UNIX operating system, device names(device special files) are only created for device LUNs that reportunique device identifiers, and not for every bus-target-LUN instancevisible to the system. If the same device identifier (WWID) is reportedfrom multiple bus-target-LUN instances, Tru64 will only create onedevice name for what it considers to be one unique device. Tru64 V5.xcan support multipath configurations and provide path failover and

load balancing to devices. The bus-target-LUN paths that reportedthe same WWID are grouped together as the available paths of adevice. The device names in Tru64 UNIX V5.x have the followingformat:

dsk[unit][partition]

where:

[unit] is a number assigned sequentially to new devices (withunique WWIDs) when they are discovered and configured by theoperating system.

T 64 UNIX/S t i E i t


26/176



[partition] is the letter of the disk partition, from a to h.

Example:/dev/rdisk/dsk2cis the raw device name for partition c of thesecond unique device configured by the host.

/dev/disk/dsk853g is the block device name for partition g of theeight hundred fifty third unique device configured.

Note: With the WWID-based device naming in Tru64 V5.x, a device will

retain its original device name (device special file) even if moved to adifferent adapter/bus location or assigned a new target or LUN address. If anexisting device is replaced by a new Symmetrix logical device at the sameexact bus-target-LUN, the new device will have a new device name becauseits WWID will be different.

Disk label and device partitions

Before using specific device partitions, file systems, or LSM, devicesshould be labeled and partitioned with the disklabelutility.

For example:

Clear or zero out any existing label:

disklabel -z dsk853

Label the disk using defaultor unknown, as follows:disklabel -rw dsk853 default

Figure 1shows a default disk partition layout.

Figure 1 Partitioning layout using default disk type

To edit the label and disk partitions with customized parameters:

disklabel -re dsk853

To read and check the existing label and disk partitions:

disklabel -r dsk853

g ha b

c

Entire Disk



27/176

Using file systems 27


Using file systems

This section describes how to use Tru64 UNIX file systems.

Creating and mounting the UNIX file system

To create a new file system on each Symmetrix disk or disk partition:

1. Use thenewfs command in a statement similar to the following:

newfs /dev/rz3c

2. Create a directory:

mkdir /symm

3. Mount the file system by typing a statement similar to thefollowing:

mount /dev/rz3c /symm

4. Assign the ownership:

chown oracle:dba /symm

Use thedf command to show all mounted file systems and theavailable free space.

AdvFS

Understanding the following concepts prepares you for planning,creating, and maintaining an Advanced File System (AdvFS).

Volumes A volume is any mechanism that behaves like a UNIX block device,such as a logical volume that is configured with the LSM or a diskpartition.

File domain A file domain is a named set of one or more volumes that provides ashared storage pool for one or more filesets.

When you create a file domain using themkfdmn command, youmust specify a domain name and one initial volume. Themkfdmncommand creates a subdirectory in the /etc/fdmns directory for eachnew file domain. The file domain subdirectory contains a symbolic

link to the initial volume.



28/176



You can add additional volumes to an existing file domain by usingtheaddvol utility. With each added volume, addvol creates a new

symbolic link in the appropriate file domain subdirectory of/etc/fdmns.

Filesets A fileset is both the logical file structure that the user recognizes and aunit that you can mount. Whereas you typically mount a wholeUNIX file system, with the AdvFS you mount the individual filesetsof a file domain.

An AdvFS consists of a file domain with at least one fileset that youcreate using themkfset command.

Creating and mounting an AdvFS

To create an AdvFS domain and fileset for each Symmetrix disk:

1. Create a new file domain; for example:

mkfdmn /dev/rz112c domain1

2. Create a fileset in the domain created in step 1:

mkfset domain1 fileset1

3. Create a directory:

mkdir /symm1

4. Mount the AdvFS fileset by entering a command similar to thefollowing:

mount -t advfs domain1#fileset1 /symm1

Note: A BCV device can be mounted on the same host by specifying theoptionmount -o dual.

5. Assign the ownership:

chown oracle:dba /symm1

To mount a directory for an AdvFS each time the system boots:

1. Edit /etc/fstab:

vi /etc/fstab

2. Specify each file system to mount using a statement similar to thefollowing:

domain1#fileset1 /symm1 advfs rw



29/176

Using file systems 29


Use thedf command to show all mounted file systems and theavailable free space.

Reconstructing an AdvFS domain

If a device with an existing AdvFS file system is newly added to aTru64 host, follow these steps to create a new AdvFS domaindirectory and device link:

1. Verify that the new device is a valid AdvFS volume by checking

the partition fstype; for example:

disklabel -r dsk1355

2. Re-create (if necessary) and change to the domain directory:

mkdir /etc/fdmns/cd /etc/fdmns/

3. Reconstruct the device link(s) of the AdvFS domain using thenew device special file(s):

ln -s /dev/disk/dsk1355c

You can also use the advscan command to reconstruct AdvFSdomains.

LUN expansionThe AdvFS and UFS file systems on Tru64 UNIX can supportexpanded LUNs. AdvFS file systems can be extended on hosts withTru64 UNIX V5.1B or later installed. UFS file systems can be extendedon hosts with Tru64 UNIX V5.1 or later installed.

The disk label of an expanded LUN must be updated before the newcapacity can be used by file systems. Disk partition sizes can be

increased to the new capacity, but the disk offsets of in-use diskpartitions must not be changed. The disk label updates should onlybe done by experienced system administrators. Partitioning andsizing errors in disk label updates can cause data loss. A data backupis recommended before expanding a LUN.



30/176


y

The steps for file system LUN expansion are:

1. Back up data on the LUN to be expanded.2. Save a copy of the existing disk label:

disklabel -r > disklabel.orig.out

3. Expand the Symmetrix LUN.

4. Reread the disk label or runinqto query the new LUN capacity:

disklabel -r

5. Rewrite or edit the existing disk label to reflect the new LUNcapacity. Increase the size of the disk partition containing the filesystem to be extended. Do not change the offsets of any diskpartitions that are used or open:

disklabel -w disklabel -re

6. Extend the file system by remounting with the extend option:

mount -u -o extend



31/176

Logical storage manager 31

Logical storage manager

This section describes three ways of using LSM (a Veritas VolumeManager):

Example 1: Setting Up LSM,next

Example 2: Creating a mirrored volume on page 32

Example 3: Creating a four-way striped volume on page 33

Example 1: Setting Up LSM

This example takes you through the steps for setting up LSM the firsttime.

1. Use thevolsetup command to add disks to your setup.For example:

volsetup rz16 rzb32 rzb40

These three disks are added to your setup as disk01, disk02, anddisk03.

2. To add more disks:

For an entire disk, type a command similar to the following:

voldiskadd rzb16

This command adds the entire disk as disk04.

For certain partitions, type a command similar to thefollowing:

voldiskadd rzc16g

This command adds the disk partition as disk05.

3. To create a volume on a disk: To create a 100 MB volume on disk01, type a command similar

to the following:

volassist make myvol1 100m disk01

To create a 100 MB volume anywhere but on disk02, type acommand similar to the following:

volassist make myvol2 100m !disk02



32/176


To create a 10 GB volume anywhere (in rootdg), type acommand similar to the following:

volassist make mybigvol 10gb

UNIX file system To create a UNIX file system on a volume:

1. To put a UFS on a 10 GB volume, type a command similar to thefollowing:

newfs /dev/rvol/rootdg/mybigvol

2. To mount a volume type a command similar to the following:mount /dev/vol/rootdg/mybigvol /symm

Advanced file system To create a new AdvFS on a volume:

1. To create a new AdvFS domain, type a command similar to thefollowing:

mkfdmn /dev/vol/rootdg/mybigvol domain1

2. To create a new fileset, type a command similar to the following:

mkfset domain1 fset1

3. To mount the fileset, type a command similar to the following:

mount -t advfs domain1#fset1 /symm

Example 2: Creating a mirrored volume

This example demonstrates a bottom-up approach to create amirrored (two-way) volume.

1. Create two subdisks (for example, sd1 and sd2) by typing thefollowing commands. The subdisks in this example are 100 MB insize and start at offset 0 of each disk.

volmake sd sd1 rzb16,0,100mvolmake sd sd2 rzb32,0,100m

2. Create a plex on each subdisk by typing commands similar to thefollowing:

volmake plex plx1 sd-sd1volmake plex plx2 sd-sd2



33/176

Logical storage manager 33

3. Create a mirrored volume by typing a command similar to thefollowing:

volmake -U gen vol vol01 plex=plx1,plx2

Note: An unmirrored volume consists of one plex. A two-way mirroredvolume consists of two plexes. A three-way mirrored volume consists ofthree plexes. LSM supports up to eight-way mirrors.

4. Start the volume by typing a command similar to the following:

volume start vol01

Note: This command takes some time as it synchronizes both plexes.

Use the volprint command to view the result of these commands:

volprint -ht s-vol

To set volume attributes and make them permanent for an LSMvolume, type this command:

voledit set user=oracle group=dba mode=0640 vol01

Example 3: Creating a four-way striped volume

This example demonstrates a bottom-up approach to create a

four-way striped volume with a striped width of 64 K.1. Create four subdisks (for example, of 500 MB each starting at

offset 0 of each disk) by typing the following commands:

volmake sd s1-sd rz16,0,500mvolmake sd s2-sd rz32,0,500mvolmake sd s3-sd rz40,0,500mvolmake sd s4-sd rz48,0,500m

2. Create a striped plex by typing a command similar to thefollowing:

volmake plex s-pl sd=s1-sd,s2-sd,s3-sd,s4-sd layout=stripe stwidth=64k

3. Create a volume on the striped plex by typing a command similarto the following:

volmake -U gen vol s-vol plex=s-pl



34/176


4. Start the volume by typing a command similar to the following:

volume start s-vol

Use thevolprint command to view the result of these commands:

volprint -ht s-vol

To set volume attributes and make them permanent for an LSMvolume, type this command:

voledit set user=oracle group=dba mode=0640 s-vol



35/176

System and error messages 35

System and error messages

Tru64 UNIX logs system and error messages to the/var/adm/messages file.

Tru64 UNIX V5.x also logs errors to the Event Manager (EVM). EVMmessages can be viewed using commands such asevmget andevmshow. For example:

evmget -f "[since 2000:10:21:05:00:00]" | evmsort | evmshow -t "@timestamp @@"

To check SCSI errors, use either thediacommand or the uerfcommand. Before you can use thedia command, the DECeventsoftware subset must be installed. The subset can be found on the

Associated Products Volume 2 CD.

The following are some dia usage examples:

The following are someuerf usage examples

dia -o full -i ios Provides a full report of allI/O-related error events.

dia -o terse -i -ios -R Provides a detailed report allI/O-related error events in reverseorder.

dia -o brief -i disk -c Provides a detailed report allI/O-related error events in reverse

order.

uerf -c err -o full Provides a full report of all errorevents.

uerf -c err -o terse -R Provides a detailed report of all error

events in reverse order.

uerf -c err -o brief -n Provides a short summary of all errorevents as they occur.



36/176


2


37/176

Virtual Provisioning 35

2Invisible Body Tag

This chapter provides information about Virtual Provisioning andTru64 UNIX.

Virtual Provisioning on Symmetrix ................................................... 36 Implementation considerations.......................................................... 41 Symmetrix Virtual Provisioning in a Tru64 UNIX environment... 46

Virtual Provisioning



38/176


Virtual Provisioning on Symmetrix

EMC Virtual Provisioningenables organizations to improve speedand ease of use, enhance performance, and increase capacityutilization for certain applications and workloads. Symmetrix VirtualProvisioning, as shown in Figure 2, integrates with existing devicemanagement, replication, and management tools, enabling customersto easily build Virtual Provisioning into their existing storagemanagement processes.

Virtual Provisioning, which marks a significant advancement overtechnologies commonly known in the industry as thinprovisioning, adds a new dimension to tiered storage in the array,without disrupting organizational processes.

Figure 2 Virtual Provisioning on Symmetrix


39/176



40/176


Thin device

Symmetrix Virtual Provisioning introduces a new type ofhost-accessible device called a thin devicethat can be used in many ofthe same ways that regular host-accessible Symmetrix devices havetraditionally been used. Unlike regular Symmetrix devices, thindevices do not need to have physical storage completely allocated atthe time the devices are created and presented to a host. The physicalstorage that is used to supply disk space for a thin device comes froma shared thin storage pool that has been associated with the thin

device.

Thin device userpre-allocated capacity

The initial amount of capacity that isallocated when a 'Thin Device' is

bound to a 'Thin Pool'. This propertyis under user control.

Bind Refers to the act of associating one ormore 'Thin Devices' with a 'ThinPool'.

Pre-provisioning An approach sometimes used to

reduce the operational impact ofprovisioning storage. The approachconsists of satisfying provisioningoperations with larger devices thatneeded initially, so that the futurecycles of the storage provisioningprocess can be deferred or avoided.

Over-subscribed thin poolA thin pool whose thin pool capacityis less than the sum of the reportedsizes of the thin devices using thepool.

Thin device extent The minimum quantum of storagethat must be mapped at a time to athin device.

Data device extent The minimum quantum of storagethat is allocated at a time whendedicating storage from a thin poolfor use with a specific thin device.



41/176

Virtual Provisioning on Symmetrix 39

A thin storage pool is comprised of a new type of internal Symmetrixdevice called a data devicethat is dedicated to the purpose of

providing the actual physical storage used by thin devices. Whenthey are first created, thin devices are not associated with anyparticular thin pool. An operation referred to as binding must beperformed to associate a thin device with a thin pool.

When a write is performed to a portion of the thin device, theSymmetrix allocates a minimum allotment of physical storage fromthe pool and maps that storage to a region of the thin device,including the area targeted by the write. The storage allocationoperations are performed in small units of storage called data deviceextents. A round-robin mechanism is used to balance the allocation ofdata device extents across all of the data devices in the pool that haveremaining un-used capacity.

When a read is performed on a thin device, the data being read isretrieved from the appropriate data device in the storage pool towhich the thin device is bound. Reads directed to an area of a thin

device that has not been mapped does not trigger allocationoperations. The result of reading an unmapped block is that a blockin which each byte is equal to zero will be returned. When morestorage is required to service existing or future thin devices, datadevices can be added to existing thin storage pools. New thin devicescan also be created and associated with existing thin pools.

It is possible for a thin device to be presented for host use before all of

the reported capacity of the device has been mapped. It is alsopossible for the sum of the reported capacities of the thin devicesusing a given pool to exceed the available storage capacity of thepool. Such a thin device configuration is said to be over-subscribed.



42/176


Figure 3 Thin device and thin storage pool containing data devices

In Figure 3, as host writes to a thin device are serviced by theSymmetrix array, storage is allocated to the thin device from the data

devices in the associated storage pool. The storage is allocated fromthe pool using a round-robin approach that tends to stripe the datadevices in the pool.



43/176

Implementation considerations 41

Implementation considerations

When implementing Virtual Provisioning, it is important that realisticutilization objectives are set. Generally, organizations should targetno higher than 60 percent to 80 percent capacity utilization per pool.A buffer should be provided for unexpected growth or a runawayapplication that consumes more physical capacity than was originallyplanned for. There should be sufficient free space in the storage poolequal to the capacity of the largest unallocated thin device.

Organizations also should balance growth against storage acquisitionand installation timeframes. It is recommended that the storage pool

be expanded before the last 20 percent of the storage pool is utilizedto allow for adequate striping across the existing data devices and thenewly added data devices in the storage pool.

Thin devices can be deleted once they are unbound from the thinstorage pool. When thin devices are unbound, the space consumed

by those thin devices on the associated data devices is reclaimed.

Note: Users should first replicate the data elsewhere to ensure it remainsavailable for use.

Data devices can also be disabled and/or removed from a storagepool. Prior to disabling a data device, all allocated tracks must beremoved (by unbinding the associated thin devices). This means that

all thin devices in a pool must be unbound before any data devicescan be disabled.

This section contains the following information:

Over-subscribed thin pools on page 42

Thin-hostile environments on page 42

Pre-provisioning with thin devices in a thin hostile

environment on page 43 Host boot/root/swap/dump devices positioned on Symmetrix

VP (tdev) devices on page 44

Cluster configurations on page 45



44/176


Over-subscribed thin pools

It is permissible for the amount of storage mapped to a thin device tobe less than the reported size of the device. It is also permissible forthe sum of the reported sizes of the thin devices using a given thinpool to exceed the total capacity of the data devices comprising thethin pool. In this case the thin pool is said to be over-subscribed.Over-subscribing allows the organization to present larger-than-needed devices to hosts and applications without having to purchaseenough physical disks to fully allocate all of the space represented by

the thin devices.

The capacity utilization of over-subscribed pools must be monitoredto determine when space must be added to the thin pool to avoidout-of-space conditions.

Not all operating systems, filesystems, logical volume managers,multipathing software, and application environments will beappropriate for use with over-subscribed thin pools. If the

application, or any part of the software stack underlying theapplication, has a tendency to produce dense patterns of writes to allavailable storage, thin devices will tend to become fully allocatedquickly. If thin devices belonging to an over-subscribed pool are usedin this type of environment, out-of-space and undesired conditionsmay be encountered before an administrator can take steps to addstorage capacity to the thin data pool. Such environments are calledthin-hostile.

Thin-hostile environments

There are a variety of factors that can contribute to making a givenapplication environment thin-hostile, including:

One step, or a combination of steps, involved in simply preparingstorage for use by the application may force all of the storage thatis being presented to become fully allocated.

If the storage space management policies of the application andunderlying software components do not tend to reuse storagethat was previously used and released, the speed in whichunderlying thin devices become fully allocated will increase.

Whether any data copy operations (including disk balancingoperations and de-fragmentation operations) are carried out aspart of the administration of the environment.



45/176


If there are administrative operations, such as bad block detectionoperations or file system check commands, that perform dense

patterns of writes on all reported storage. If an over-subscribed thin device configuration is used with a

thin-hostile application environment, the likely result is that thecapacity of the thin pool will become exhausted before the storageadministrator can add capacity unless measures are taken at thehost level to restrict the amount of capacity that is actually placedin control of the application.

Pre-provisioning with thin devices in a thin hostile environment

In some cases, many of the benefits of pre-provisioning with thindevices can be exploited in a thin-hostile environment. This requiresthat the host administrator cooperate with the storage administrator

by enforcing restrictions on how much storage is placed under thecontrol of the thin-hostile application.

For example:

The storage administrator pre-provisions larger than initiallyneeded thin devices to the hosts, but only configures the thinpools with the storage needed initially. The various steps requiredto create, map, and mask the devices and make the target hostoperating systems recognize the devices are performed.

The host administrator uses a host logical volume manager tocarve out portions of the devices into logical volumes to be used

by the thin-hostile applications.

The host administrator may want to fully preallocate the thindevices underlying these logical volumes before handing themoff to the thin-hostile application so that any storage capacityshortfall will be discovered as quickly as possible, and discoveryis not made by way of a failed host write.

When more storage needs to be made available to the application,the host administrator extends the logical volumes out of the thindevices that have already been presented. Many databases canabsorb an additional disk partition non-disruptively, as can mostfile systems and logical volume managers.

Again, the host administrator may want to fully allocate the thindevices underlying these volumes before assigning them to the

thin-hostile application.



46/176


In this example it is still necessary for the storage administrator toclosely monitor the over-subscribed pools. This procedure will

not work if the host administrators do not observe restrictions onhow much of the storage presented is actually assigned to theapplication.

Host boot/root/swap/dump devices positioned on Symmetrix VP (tdev) devices

A boot /root /swap /dump device positioned on Symmetrix VirtualProvisioning (thin) device(s) is supported with Enginuity 5773 andlater. However, some specific processes involving boot/root/swap/dump devices positioned on thin devices should nothave exposure to encountering the out-of-space condition.Host-based processes such as kernel rebuilds, swap, dump, savecrash, and Volume Manager configuration operations can all beaffected by the thin provisioning out-of-space condition. Thisexposure is not specific to EMC's implementation of ThinProvisioning. EMC strongly recommends that the customer avoidencountering the out-of-space condition involving boot / root/swap/dump devices positioned on Symmetrix VP (thin) devicesusing the following recommendations;

It is strongly recommended that Virtual Provisioning devicesutilized for boot /root/dump/swap volumes must be fullyallocated1or the VP devices must not be oversubscribed2.

Should the customer use an over-subscribed thin pool, theyshould understand that they need to take the necessaryprecautions to ensure that they do not encounter the out-of-spacecondition.

1. A fully allocated Symmetrix VP (thin) device has 100% of the advertisedspace mapped to blocks in the data pool that it is bound to. This can beachieved by use of the Symmetrix VP pre-allocation mechanism orhost-based utilities that will enforce pre-allocation of the space (such as,host device format.)

2. An over-subscribed Symmetrix VP (thin) device is a thin device, bound to

a data pool, that does not have sufficient capacity to allocate for theadvertised capacity of all the thin devices bound to that pool.


d d l l l bl


47/176


It is not recommended to implement space reclamation, availablewith Enginuity 5874 and later, with pre-allocated or

over-subscribed Symmetrix VP (thin) devices that are utilized forhost boot/root/swap/dump volumes. Although notrecommended, Space reclamation is supported on the listed typesof volumes

Should the customer use space reclamation on this thin device,they need to be aware that this freed space may ultimately beclaimed by other thin devices in the same pool and may not beavailable to that particular thin device in the future.

Cluster configurations

When using high availability in a cluster configuration, it is expectedthat no single point of failure exists within the cluster configurationand that one single point of failure will not result in dataunavailability, data loss, or any significant application becoming

unavailable within the cluster. Virtual provisioning devices (thindevices) are supported with cluster configurations; however,over-subscription of virtual devices may constitute a single point offailure if an out-of-space condition should be encountered. To avoidpotential single points of failure, appropriate steps should be taken toavoid under-provisioned virtual devices implemented within highavailability cluster configurations.



48/176


Symmetrix Virtual Provisioning in a Tru64 UNIX environment

Symmetrix Virtual Provisioning introduces advantages to the Tru64UNIX environment otherwise not possible:

Reduction of System Administration tasks

The frequency of tasks such as extending volume groups,extending logical volumes, and expansion of file systems can bereduced significantly. System administrators can configure theirenvironments initially for future capacity requirements withoutthe necessity of having the physical storage needed for futuregrowth requirements available.

Reduction and simplification of storage management tasks

The frequency and complexity of making new storage capacityavailable to hosts is significantly reduced. Storage managementoperations such as device assignments, LUN masking, LUNcapacity changes, device discovery operations, and storagecapacity availability monitoring can be reduced or simplified.Monitoring of remaining available storage capacity is simplifiedand more accurate. EMC tools for the monitoring of thin poolcapacity utilization can accurately indicate the current amount ofavailable capacity remaining in the thin pools.

Efficient storage capacity management

Efficient utilization of storage capacity is easily achieved sinceactual physical storage is not allocated to a Symmetrix thin deviceuntil the thin device is written to. Only the required amountstorage capacity to save the update is utilized unless the useroptionally pre-allocates capacity to the thin device.

Performance considerations

Data written to thin devices is striped across data devices of therelated thin pool (or thin pools) the thin devices are bound to.This can alleviate back-end contentions or compliment othermethods of alleviating contentions, such as host-based striping.



49/176

Symmetrix Virtual Provisioning in a Tru64 UNIX environment 47

Tru64 UNIX Virtual Provisioning support

EMC Symmetrix Virtual Provisioning is supported with Tru64 UNIXv5.1B.

Precaution considerations

EMC Virtual Provisioning and the industrys thin provisioning arenew technologies. Relevant industry specifications have not yet been

drafted. Virtual Provisioning, like thin provisioning, has the potentialto introduce events into the environment which would not otherwiseoccur. The unavailability of relevant industry standards results indeviations with the host-based handling of these events and thepossibility of undesirable implications when these events occur.However, with the proper precautions these exposures can beminimized or eliminated.

Thin pool out-of-space event

Insufficient monitoring of the thin pool can result in all of the thinpool enabled capacity to be allocated to thin devices bound to thepool. If over-subscription is implemented, the thin pool out-of-spaceevent can result in a non-recoverable error being returned to a writerequest when it is sent to a thin device area that does not havecapacity allocated from the thin pool. Simple precautions can avoidthis from occurring, including the following:

Monitoring of the consumption of the thin pool enabled capacityusing EMC Solutions Enabler or EMC Symmetrix Managementconsole will keep the user informed when additional data devicesshould be added to the thin pool to avoid the thin poolout-of-space event. Threshold-based alerts can also be configuredto automatically notify of the event or to add to capacity to thethin pool.

Thin device allocation limits can be set to limit the amount ofcapacity a thin device can withdraw from the thin pool.

Predictable growth of capacity utilization results in avoidingunexpected capacity demands. Implementing VirtualProvisioning with applications which have predictable growth ofcapacity utilization will avoid unexpected thin pool enabledcapacity depletion.


Avoid unnecessary block-for-block copy of a device to a thin


50/176


Avoid unnecessary block-for-block copy of a device to a thindevice. Block-for-block copy of a device to a thin device results in

the entire capacity of the source volume to be written to the thindevice, regardless of how much user data the source volumecontains. This can result in unnecessary allocation of space to thethin device.

Plan for thin pool enabled capacity utilization not to exceed 60% 80%.

File system compatibility

Choose to implement file system types which are VirtualProvisioning compatible:

LSM, ADVFS, only 1% or less of thin device space is allocated atfile system creation.

Avoid defragmenting file systems positioned on thin devicessince this can result in unnecessary capacity allocation from thethin pool.

Avoid implementing Virtual Provisioning in Virtual Provisioninghostile environments.

Possible implications of the thin pool out-of-space event

The following are possible implications of thin pool out-of-spaceevent:

Tru64 UNIX v5.1B Thin pool out-of-space and write request to an

area of a thin device which has not had capacity allocated from thethin pool.

Write request to a raw device (no fs) is not retried.

LSM, ADVFS, write request not retried when system is full.

Unbound thin devices

Host-visible thin devices which are not bound to a thin pool have thesame behavior as any other Symmetrix device inclusive of standardand bound thin devices, except for the handling of write requests. Aprocess attempting to write to an unbound thin device will receive anerror. An unbound thin device will appear to system administrationutilities and a Volume Manager as an eligible device to be utilized orconfigured since all device discovery operations, device OPENs, and

READ requests will successfully complete. However, when the


system administration process attempts to write to the unbound thin


51/176

Symmetrix Virtual Provisioning in a Tru64 UNIX environment 49

system administration process attempts to write to the unbound thindevice, an error will be returned.

Avoid attempting to utilize a thin device before it is bound to a thinpool.

Possible implications of write request received by an unbound thin device

Tru64 UNIX v5.1BWith visible unbound TDEVs, write request tounbound thin device results in write error which is not retried.



52/176


3Invisible Body Tag

Tru64 UNIX and


53/176

Tru64 UNIX and Symmetrix over Fibre Channel 51

This chapter provides information specific to AlphaServers runningTru64 UNIX and connecting to Symmetrix systems over FibreChannel.

Tru64 UNIX/Symmetrix Fibre Channel environment ................. 52 Host configuration with Compaq HBAs........................................ 56 Addressing Symmetrix devices ....................................................... 63

Tru64 UNIX and

Symmetrix over FibreChannel

Tru64 UNIX and Symmetrix over Fibre Channel

T 64 UNIX/S t i Fib Ch l i t


54/176


Tru64 UNIX/Symmetrix Fibre Channel environment

This section contains the following information:

Hardware connectivity,next

Boot device support on page 52

Logical devices on page 52

Symmetrix configuration on page 53

Port sharing on page 55

Hardware connectivity

Refer to theEMC Support Matrixor contact your EMC representativefor the latest information on qualified hosts, host bus adapters, andconnectivity equipment.

Boot device support

HP/Compaq hosts with Tru64 UNIX and TruCluster V5.x have beenqualified for booting from Symmetrix devices interfaced throughFibre Channel as described in Configuring boot support onpage 57.

Logical devices

LUNs are supported as follows:

a. Each Symmetrix Fibre Channel director port is a single Fibre Channel target.

OS version Max LUNs per target a

Tru64 V4.0F/G 8 (Valid LUN addresses 000-007)

Tru64 V5.x 255 (Valid LUN addresses 000-0FE)


Symmetrix configuration
http://powerlink.emc.com/http://powerlink.emc.com/


55/176

Tru64 UNIX/Symmetrix Fibre Channel environment 53

Symmetrix configuration

Symmetrix configuration is done by an EMC Customer Engineer (CE)through the Symmetrix service processor.

Note: Refer to the following paragraphs and to theEMC Support Matrixforrequired bit settings on Symmetrix Fibre Channel directors.

Configuring theSymmetrix for Tru64

UNIX V5.x

Note the following requirements:

Set the following director bits for each port attached to Tru64UNIX and TruCluster V5.x Fibre Channel environments:

OVMS P2P (Point-to-point) UWN (Unique worldwide name)

Set the Symmetrix OVMS director bit:

The OVMS bit enables the device identifier (WWID)

information necessary for Tru64 UNIX and TruCluster V5.xFibre Channel environments. Incorrect device WWIDs result ifthe OVMS bit is not set.

The OVMS bit requires minimum Symmetrix microcode5265.48.30 or 5566.26.19.

All Fibre Channel director ports configured for Tru64 V5.x hostsmust have a LUN 000 device mapped. Not mapping a LUN 000device can cause conflicting duplicate WWIDs and possible

bootup problems on the Tru64 host.

Table 3shows differences in LUN 000 behavior with the differentSymmetrix models and microcode levels.

Table 3 LUN 000 behavior differences (page 1 of 2)

Symmetrix model Microcode LUN 000 device type Usable by Tru64 host

Symmetrix VMAX 40K 5876 Array controller (scp) No, use a smaller gatekeeperfor LUN 000

Symmetrix VMAX 20K 5876 Array controller (scp) No, use a smaller gatekeeperfor LUN 000

Symmetrix VMAX 5876

5875

5874

Array controller (scp) No, use a smaller gatekeeperfor LUN 000


Table 3 LUN 000 behavior differences (page 2 of 2)


56/176


VCMDB and devicemasking guidelines

Note these requirements and recommendations:

Configure and administer Symmetrix device masking from eitherthe Tru64 UNIX host with EMC Solutions Enabler SymmetrixDevice Masking CLI V5.x.x or from a separate EMC IonixControlCenter host with EMC SAN Manager.

On Symmetrix 8000 series systems, do not map the VCMDB asLUN 000. A VCMDB device mapped as LUN 000 cannot beupdated because LUN 000 is not a normal device when theOVMS director bit is set.

Enable access to LUN 000 devices. Conflicting duplicate deviceWWIDs can result if the LUN 000 device is masked from theTru64 host bus adapters.

TruCluster V5 hosts with persistent reservations enabled willattempt to establish reservation locks on all visible devices. AVCMDB device that has been reserved by TruCluster can bemanaged only from the TruCluster host.

If device masking will be managed from non-cluster hosts, do notconfigure the VCMDB device as visible to TruCluster hosts. Youcan enable a restricted access setting on the Symmetrix system tomask the VCMDB device from TruCluster hosts.

Change the device label of the VCMDB device from SYMto VCM,especially if the VCMDB device is logical device 000. Forexample, change the label of the VCMDB device 000 fromSYM000 to VCM000.

Symmetrix DMX-3, DMX-4 5773 Array controller (scp) No, use a smaller gatekeeperfor LUN 000

Symmetrix DMX, DMX-2 with VCM 5671 Array controller (scp) No, use a smaller gatekeeperfor LUN 000

Symmetrix DMX, DMX-2 5670, 5671 Normal disk device (dsk) Yes

Symmetrix 8000 55xx Array controller (scp) No, use a smaller gatekeeperfor LUN 000

Symmetrix model Microcode LUN 000 device type Usable by Tru64 host


Port sharing


57/176

Tru64 UNIX/Symmetrix Fibre Channel environment 55

Port sharing

Tru64 UNIX V5.x hosts require special director bit settings differentfrom Tru64 UNIX V4.0x hosts. If a Symmetrix Fibre Channel directorport will be shared by Tru64 UNIX hosts, the configuration optionsare as follows:

Set the OVMS director bit on the port as required for Tru64 UNIXV5.x hosts. If the port is on a Symmetrix 8000 system, LUN 000will not be usable. A Tru64 UNIX V4.0x host can normallysupport up to 8 devices per port, but only 7 devices (LUNaddresses 001 007) will be usable by the Tru64 UNIX V4.0 hostwhen the OVMS director bit is set. On Symmetrix DMX systems,the maximum 8 devices (LUN addresses 000 007) will be usable

by Tru64 UNIX V4.0x hosts even when the OVMS director bit isset.

Use the features in EMC Solutions Enabler Symmetrix DeviceMasking CLI Version 5.1 or later to set different director bit

settings for each host connected to a shared director port. Theheterogeneous host configuration feature can be used to setindividualized director bit settings for Tru64 UNIX V4.0 andTru64 UNIX V5.x HBAs on the same director port. Since Tru64UNIX hosts only configure a specific range of supported LUNaddresses, the LUN base and offset adjustment feature can beused to maximize the number of LUNs available to Tru64 UNIXhosts on a shared director port.


Host configuration with Compaq HBAs


58/176


Host configuration with Compaq HBAs

This section describes the tasks required to install one or moreCompaq host bus adapters into the AlphaServer host and configurethe host for connection to a Symmetrix system over Fibre Channel.

Planning zoning and connections

Before setting up the hardware in a fabric switch configuration with

the Symmetrix, you should plan an effective zone map. Check theswitch manufacturers user documentation for help on definingzones.

The Fibre Channel fabric must be zoned so that the Tru64 V5.x hostdiscovers only Symmetrix Fibre Channel director ports that have

been properly configured. Otherwise, misconfigured device WWIDsand associated problems may result.

Installing the HBA

Follow the instructions included with your adapter. The adapterinstalls into a single PCI bus slot.

If necessary, load the required HBA firmware level specified in theEMC Support Matrix.

Verify that the AlphaServer SRM console firmware is V5.6 or higher.At the AlphaServer console prompt, typeshow version and pressEnter.

Note: EMC recommends using the latest available console firmware version.

Console firmware updates are available on the OS Release Kit CD,and can also be downloaded from this location:

ftp.digital.com/pub/DEC/Alpha/firmware/

Check that the adapters are set up properly for fabric topology byusing the WWIDMGR utility (wwidmgr -show adapter). Format theNVRAM (wwidmgr -set adapter -item 9999 -topo fabric) for fabricsupport if necessary.


Configuring boot support


59/176

Host configuration with Compaq HBAs 57

g g pp

Compaq hosts with Tru64 UNIX and TruCluster V5.x have beenqualified for booting from Symmetrix devices interfaced throughFibre Channel. Ensure that the necessary Symmetrix director flags(OVMS, P2P, UWN) is enabled. The AlphaServer SRM consolefirmware should be V5.7 or higher.

Note: EMC recommends using the latest available console firmware version.

To configure boot support, complete the following steps.

1. To set up the boot device, first identify the Unique DeviceIdentifier (UDID) of the Symmetrix logical volume that will beused for boot support.

a. Run the WWIDMGR utility (wwidmgr -show wwid| more)from the AlphaServer console prompt to display the FibreChannel devices on the system.

b. All devices in the WWIDMGR output have UDID and WWIDvalues. To identify the UDID value of a specific Symmetrixlogical volume, look for the WWIDMGRentry containing theexpected WWID for the Symmetrix device. Symmetrix FibreChannel device WWIDs should have the format:

6006-0480-ssss-ssss-ssss-dddd-dddd-dddd

where ssss-ssss-ssssis the Symmetrix serial number, anddddd-dddd-dddd is the Symmetrix device label (ASCIIcharacters in hex).

The following WWID example is Symmetrix logical device10D (5359-4d31-3044 is label SYM10D) on Symmetrix system000184600025:

WWID:01000010:6006-0480-0001-8460-0025-5359-4d31-3044

2. Set the boot device:

wwidmgr -quickset -udid

3. Reinitialize the AlphaServer console:

init

4. Check that the boot device has been set:

show bootdef_dev


If the variable was not set, look for the appropriate device in theshow dev output and set it manually. (The Fibre Channel device


60/176


p yhas the format dg[N][UDID value].)

Example:

set bootdef_dev dga32.1001.0.3.1

Rebuilding the Tru64 UNIX kernel

If the Compaq Fibre Channel HBA is newly added to the system, the

Tru64 UNIX kernel must be rebuilt to identify and support the newadapter.

To rebuild the kernel:

1. At the SRM console prompt, typeboot -fi genvmunix and pressEnter.

2. After the host boots, type doconfig and press Enter.

3. When prompted Do you want to edit the config file?, type Nandpress Enter.

4. After the kernel is built, type cp /sys//vmunix/ andpress Enter.

5. Reboot the host.

Upgrading the Tru64 UNIX Fibre Channel driverWhen new revisions of the Tru64 Fibre Channel driver are available,they are released as part of Tru64 UNIX Aggregate Patch Kits. Toupgrade the driver to the latest revision available, download andinstall the latest OS Patch Kit from this location:

ftp.itrc.hp.com/data/patch_bundles/tru64


Adding the Symmetrix device entry


61/176


Follow these steps to add the device entry:1. Include the following entry for Symmetrix Fibre Channel devices

in the host file /etc/ddr.dbase.

2. Recompile the edited /etc/ddr.dbase:

ddr_config -c

3. Reboot the system.

4. Verify the changes:

ddr_config -s disk EMC SYMMETRIX 2

SCSIDEVICE # # Entry for Symmetrix Fibre Channel devices # Type = disk Stype = 2 Name = "EMC" "SYMMETRIX"

PARAMETERS: TypeSubClass = hard_disk, raid BlockSize = 512

BadBlockRecovery = disabledDynamicGeometry = trueLongTimeoutRetry = enabled

DisperseQueue = falseTagQueueDepth = 20ReadyTimeSeconds = 45InquiryLength = 160RequestSenseLength = 160PwrMgmt_Capable = false

# # Uncomment ATTRIBUTE stanza (delete # from the 4 lines below)

# for TruCluster V5.x only: # ubyte[0] = 8 Disable AWRE/ARRE only, Persistent Reserve enabled

# ubyte[0] = 25 Disable PR & AWRE/ARRE, Enable I/O Barrier Patch#

# ATTRIBUTE:# AttributeName = "DSBLflags"# Length = 4# ubyte[0] = (8 or 25)


V4.0F/V4.0G notes


62/176


The Tru64 UNIX emx Fibre Channel driver provides persistentbinding functionality. Each World Wide Name (WWN) found ismapped to a target ID. This mapping persists across reboots andconfiguration changes; however, only the initial seven WWN/targetID mappings are available to the CAM SCSI subsystem.

Refer to the emx and emx_data.c operating system man pages forinformation on modifying the target ID mappings in the /etc/emx.dbdatabase.

If a V4.0F/V4.0G host has had multiple Fibre Channel configurationchanges or was connected to an unzoned switch, all seven validtarget IDs may have already been assigned. When a valid target IDmust be freed, or a specific WWN must be mapped to a specific targetID (such as for TruCluster 1.x), the following example shows theprocedure for modifying the database:

1. View and copy the existing configuration from the file/etc/emx.info:

2. Modify and paste the data into the file /sys/data/emx_data.c. Inthis example, WWN 0x4e7c is specifically assigned target ID 0,and WWN 0x5e7c is assigned target 2. All other target IDs arefreed by specifying -1.

emx? tgtid FC Port Name FC Node Name{ 0, 0, 0x0650, 0x8204, 0x60bc, 0x4fed, 0x0650, 0x8204, 0x60bc, 0x4fed },{ 0, 1, 0x0650, 0x8104, 0xdaa7, 0xd7f1, 0x0650, 0x8104, 0xdaa7, 0xd7f1 },{ 0, 2, 0x0650, 0x8204, 0x61bc, 0x4f06, 0x0650, 0x8204, 0x61bc, 0x4f06 },{ 0, 3, 0x0650, 0x8204, 0x31c0, 0x4e7c, 0x0650, 0x8204, 0x31c0, 0x4e7c },{ 0, 4, 0x0650, 0x8204, 0x31c0, 0x5e7c, 0x0650, 0x8204, 0x31c0, 0x5e7c },{ 0, 5, 0x0010, 0x0000, 0x21c9, 0xd378, 0x0010, 0x0000, 0x21c9, 0xd378 },{ 0, 6, 0x0010, 0x0000, 0x20c9, 0xb6cf, 0x0010, 0x0000, 0x20c9, 0xb6cf },{ 0, 7, 0x0010, 0x0000, 0x20c9, 0x82d0, 0x0010, 0x0000, 0x20c9, 0x82d0 },{ 0, 8, 0x0010, 0x0000, 0x21c9, 0x827f, 0x0010, 0x0000, 0x21c9, 0x827f },


EMX_FCPID_RECORD emx_fcpid_records[] = {


63/176


3. Rebuild the kernel:

doconfig -c

4. Reboot the system.

Note: If available, you can use theemxmgr utility instead to remap targetIDs. Read the emxmgr man page for details.

V5.x notes

The V5.x OS uses a new device naming scheme that is based on theunique WWID of a device, and not its physical location(bus-target-LUN). A device that is moved, or removed and re-added,keeps its original device name.

In V5.x, it is not necessary to configure Fibre Channel persistentbinding, since the device naming scheme is not dependent on devicelocation and 255 valid SCSI targets are available on each bus.

emxmgr The emxmgrutility displays all Fibre Channel adapter instances onthe host system:

emxmgr -d

The emxmgrutility also displays the link status, topology, andN_Port detail of each adapter:

emxmgr -t emx

/* Insert records below here */

emx? tgtid FC Port Name FC Node Name{ 0, -1, 0x0650, 0x8204, 0x60bc, 0x4fed, 0x0650, 0x8204, 0x60bc, 0x4fed },{ 0, -1, 0x0650, 0x8104, 0xdaa7, 0xd7f1, 0x0650, 0x8104, 0xdaa7, 0xd7f1 },{ 0, -1, 0x0650, 0x8204, 0x61bc, 0x4f06, 0x0650, 0x8204, 0x61bc, 0x4f06 },{ 0, 0, 0x0650, 0x8204, 0x31c0, 0x4e7c, 0x0650, 0x8204, 0x31c0, 0x4e7c },{ 0, 2, 0x0650, 0x8204, 0x31c0, 0x5e7c, 0x0650, 0x8204, 0x31c0, 0x5e7c },{ 0, -1, 0x0010, 0x0000, 0x21c9, 0xd378, 0x0010, 0x0000, 0x21c9, 0xd378 },{ 0, -1, 0x0010, 0x0000, 0x20c9, 0xb6cf, 0x0010, 0x0000, 0x20c9, 0xb6cf },

{ 0, -1, 0x0010, 0x0000, 0x20c9, 0x82d0, 0x0010, 0x0000, 0x20c9, 0x82d0 },{ 0, -1, 0x0010, 0x0000, 0x21c9, 0x827f, 0x0010, 0x0000, 0x21c9, 0x827f },

/* Insert records above here */


hwmgr The commandhwmgr -show fibre (in Tru64 UNIX V5.1B and later)displays Fibre Channel adapter information that is similar to theemxmgr commands


64/176


emxmgrcommands.

The command hwmgr -view devices displays all the devices on thehost system.

To view detailed information about the configured devices, use thecommand hwmgr -show scsi -full.

Example:

The WWID for the device has the format:

6006-0480-ssss-ssss-ssss-dddd-dddd-dddd

wheressss-ssss-ssss is the Symmetrix serial number, and

dddd-dddd-dddd is the Symmetrix device label (ASCII characters inhex).

In this example, dsk281 is Symmetrix device 0F2. (5359-4d30-4632 islabel SYM0F2.)

The command hwmgr -show scsi -staleshows any failed or removeddevices/paths on the host system. If you need to permanentlyremove device entries, use these commands:

hwmgr -refresh componenthwmgr -refresh scsihwmgr -delete scsi -did

SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRSTHWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH-------------------------------------------------------------------------673: 18 losaz205 disk none 0 3 dsk281 [4/0/3]

WWID:01000010:6006-0480-0000-0000-3220-5359-4d30-4632

BUS TARGET LUN PATH STATE------------------------------

4 0 3 valid6 0 3 valid6 1 3 valid


Addressing Symmetrix devices


65/176

Addressing Symmetrix devices 63

This section describes methods of addressing Symmetrix devicesover Fibre Channel:

Arbitrated loop addressing

Fabric addressing

SCSI-3 FCP addressing

Arbitrated loop addressing

The Fibre Channel arbitrated loop (FC-AL) topology defines amethod of addressing ports, arbitrating for use of the loop, andestablishing a connection between Fibre Channel NL_Ports (levelFC-2) on HBAs in the host and Fibre Channel directors (using theiradapter cards) in the Symmetrix. Once loop communications areestablished between the two NL_Ports, device addressing proceeds

in accordance with the SCSI-3 Fibre Channel protocol (SCSI-3 FCP,level FC-4).

The Loop Initialization Process (LIP) assigns a physical address(AL_PA) to each NL_Port in the loop. Ports that have a previouslyacquired AL_PA are allowed to keep it. If the address is not available,another address may be assigned, or the port may be set tonon-participating mode.

Note: The AL-PA is the low-order 8 bits of the 24-bit address. (The upper 16bits are used for Fibre Channel fabric addressing only; in FC-AL addresses,these bits are x0000.)

Symmetrix Fibre Channel director parameter settings, shown inTable 4 on page 64, control how the Symmetrix system responds tothe Loop Initialization Process.

After the loop initialization is complete, the Symmetrix port canparticipate in a logical connection using the hard-assigned orsoft-assigned address as its unique AL_PA. If the Symmetrix port is innon-participating mode, it is effectively off line and cannot make alogical connection with any other port.


A host initiating I/O with Symmetrix uses the AL_PA to request anopen loop between itself and the Symmetrix port. Once thearbitration process has established a logical connection between the


66/176


a b t at o p ocess as estab s ed a og ca co ect o betwee t eSymmetrix and the host, addressing specific logical devices is donethrough the SCSI-3 FCP.

Fabric addressing

Each port on a device attached to a fabric is assigned a unique 64-bitidentifier called a Worldwide Port Name (WWPN). These names arefactory-set on the HBAs in the hosts, and are generated on the FibreChannel directors in the Symmetrix.

Note: For comparison to Ethernet terminology, an HBA is analogous to a NICcard, and a WWPN to a MAC address.

Table 4 FC-AL addressing parameters

Parameter Bit Description Default

Disk Array A If enabled, the Fibre Channel Director presents the port as a diskarray. Refer to Table 5 on page 66, for settings for each addressing

mode.

Enabled

Volume Set V If enabled and disk array is enabled, volume set addressing mode isenabled. Refer to Table 5 on page 66, for settings for eachaddressing mode.

Enabled

Use HardAddressing

H If enabled, entering an address (00 through 7D) in the Loop ID fieldcauses the port to attempt to get the AL_PA designated by the LoopID. If the port does not acquire the AL_PA, the Symmetrix reacts

based on the state of the non-participating (NP) bit. If the NP bit isset, the port switches to non-participating mode and is not assignedan address. If non-participating mode is not selected, or if the H-bitwas not set, the Symmetrix port accepts the new address that issoft-assigned by the host port.

Enabled

Hard AddressingNon-participating

NP If enabled andthe H-bit is set, the director uses onlythe hardaddress. If it cannot get this address, it re-initializes and changes itsstate to non-participating. If the NP bit is not set, the director acceptsthe soft-assigned address.

Disabled

Loop ID --- Valid only if the H-bit is set, is a 1-byte address (00 through 7D). 00

Third-partyLogout acrossthe Port

TP Allows broadcast of the TPRLO extended link service through all ofthe FC-AL ports.

Disabled


Note: The ANSI standard also defines a WWNN, but this name has beeninconsistently defined by the industry.


67/176

Addressing Symmetrix devices 65

When an N_Port (host server or storage device) connects to the fabric,a login process occurs between the N_Port and the F_Port on thefabric switch. During this process, the devices agree on suchoperating parameters as class of service, flow control rules, and fabricaddressing. The N_Ports fabric address is assigned by the switch andsent to the N_Port. This value becomes the source ID (SID) on theN_Port's outbound frames and the destination ID (DID) on the

N_Port's inbound frames.

The physical address is a pair of numbers that identify the switch andport, in the format s,p, where s is a domain ID and p is a valueassociated to a physical port in the domain. The physical address ofthe N_Port can change when a link is moved from one switch port toanother switch port. The WWPN of the N_Port, however, does notchange. A name server in the switch maintains a table of all logged-in

devices, so N_Ports can automatically adjust to changes in the fabricaddress by keying off the WWPN.

The highest level of login that occurs is the process login. This is usedto establish connectivity between the upper-level protocols on thenodes. An example is the login process that occurs at the SCSI FCPlevel between the HBA and the Symmetrix system.

SCSI-3 FCP addressing

The Symmetrix director extracts the SCSI Command DescriptorBlocks (CDB) from the frames received through the Fibre Channellink. Standard SCSI-3 protocol is used to determine the addressingmode and to address specific devices.

The Symmetrix supports three addressing methods based on asingle-layer hierarchy as defined by the SCSI-3 controller commands(SCC):

Peripheral device addressing Logical unit addressing Volume set addressing

All three methods use the first two bytes (0 and 1) of the eight-byteLUN addressing structure. The remaining six bytes are set to 0s.


For logical unit and volume set addressing, the Symmetrix portidentifies itself as an array controller in response

Documents

Emc Tru64 Guide