20414 Volume Logix Product Guide 2.1

EMC Corporation 171 South Street, Hopkinton, MA 01748-9103Corporate Headquarters: (508) 435-1000, (800) 424-EMC2

Fax: (508) 435-5374, Service: (800) SVC-4EMC

EMC Enterprise Storage

EMC Volume Logix

Version 2.1Product Guide

P/N 300-999-024REV F

Copyright © 1998-1999 EMC Corporation. All rights reserved.Printed July 1999

No part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written consent of EMC Corporation.

The information contained in this document is subject to change without notice. EMC Corporation assumes no responsibility for any errors that may appear.

All computer software programs, including but not limited to microcode, described in this document are furnished under a license, and may be used or copied only in accordance with the terms of such license. EMC either owns or has the right to license the computer software programs described in this document. EMC Corporation retains all rights, title and interest in the computer software programs.

EMC Corporation makes no warranties, express or implied, by operation of law or otherwise, relating to this document, the products or the computer software programs described herein. EMC CORPORATION DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. In no event will EMC Corporation be liable for (a) incidental, indirect, special or consequential damages or (b) any damages whatsoever resulting from the loss of use, data or profits, arising out of this document, even if advised of the possibility of such damages.

Trademark InformationUNIX is a registered trademark in the United States and other countries and is licensed exclusively through X/Open Company Ltd.HP is a registered trademark of Hewlett-Packard CompanyWindows and Windows NT are registered trademarks of Microsoft Corporation.WinZip is a registered trademark of Nico Mak Computing, Inc.Solaris, SPARCserver, UltraSPARC, Sun, Sun Microsystems are trademarks of Sun Microsystems, Inc.Compaq is a registered trademark of Compaq Computer Corporation.

EMC, EMC2 (the EMC logo), EMC Enterprise Storage, and Symmetrix are registered trademarks and TimeFinder and SRDF are trademarks of EMC Corporation.All other trademarks used herein are the property of their respective owners.

Contents

Preface ..................................................................................xi

Chapter 1 Introducing Volume Logix ............................1

1.1 Why Choose Volume Logix?..................................... 21.2 What is Volume Logix?.............................................. 4

How Volume Logix Works .................................... 5Volume Logix Interfaces ........................................ 6

Chapter 2 Installing Volume Logix.................................7

2.1 Preparing to Install Volume Logix ........................... 8Symmetrix Configuration...................................... 8Fibre Channel .......................................................... 8Volume Logix Database Device ............................ 9Host Systems ........................................................... 9

2.2 Upgrading Volume Logix........................................ 12Upgrading from Version 1.x................................ 12Upgrading from Version 2.0 ................................ 12

2.3 Upgrading the Java Runtime Environment.......... 142.4 Installing on an Administrator Host ..................... 15

Installing on a Windows NT System.................. 15Installing on a UNIX System............................... 18Installing the Command Line Interface............. 20

2.5 Installing Utilities on Host Systems....................... 22Windows NT Systems .......................................... 22UNIX Systems ....................................................... 23

2.6 Uninstalling Volume Logix from an Administrator Host ............................................................................ 25

Windows NT System............................................ 25UNIX System ......................................................... 25Command Line Interface ..................................... 26

iii

2.7 Uninstalling Host Utilities ...................................... 27Windows NT System............................................ 27UNIX System ......................................................... 27

2.8 Setting Environment Variables ............................... 29Setting the VLOGIX_DATA Environment

Variable ............................................................... 29VCMDBDEVICE Environment Variable ........... 31PATH Environment Variable............................... 33

2.9 Running vcmfind and fcompare at Start-up ........ 34Windows NT System............................................ 34UNIX System ......................................................... 35Editing Start-up Files............................................ 36

2.10 Checking your Installation...................................... 38Display VCMDB Device ...................................... 39

2.11 Initializing the Volume Logix Administrator....... 41Starting the Volume Logix Administrator......... 41Renaming Unnamed Hosts ................................. 45Help browser ......................................................... 46

Chapter 3 Introducing Volume Logix Administrator ..49

3.1 Volume Logix Administrator.................................. 503.2 Volume Logix Administrator Window ................. 523.3 Menu Bar ................................................................... 543.4 Tool Bar ...................................................................... 563.5 ESN Topology Pane.................................................. 573.6 Volumes Pane............................................................ 60

Icons view .............................................................. 60Details view ........................................................... 61

3.7 Status Bar ................................................................... 63

Chapter 4 Using Volume Logix Administrator .............65

4.1 Starting the Volume Logix Administrator ............ 66From Windows NT ............................................... 66From UNIX ............................................................ 67

4.2 Stopping the Volume Logix Administrator .......... 69Stopping with no pending tasks, no inactive

iv Contents

configurations, no unlogged tasks.................. 69Stopping with pending tasks .............................. 70Stopping with inactive Symmetrix configurations

71Stopping with tasks that have not been saved to

the log file ........................................................... 724.3 Changing the Password........................................... 734.4 Configuring Access Control.................................... 74

Initialize the Volume Logix Database ................ 74Select and Add Volumes ...................................... 75Activate the Configuration.................................. 75

4.5 Simple Case Study.................................................... 77Start Volume Logix Demo.................................... 78Initialize the Volume Logix Database ................ 78Select and Add Volumes ...................................... 80Activate the Configuration.................................. 85Back up Volume Logix database......................... 87What next? ............................................................. 88

Chapter 5 Managing Volume Logix Objects..............89

5.1 Tasks Overview......................................................... 905.2 Reloading the Display ............................................. 925.3 Refreshing the Display ............................................ 935.4 Task List ..................................................................... 935.5 Saving Tasks to the Log File.................................. 1075.6 Activating the Configuration................................ 1095.7 Symmetrix ................................................................111

To view Symmetrix properties...........................111To initialize the Volume Logix database.......... 112To back up the Volume Logix database ........... 114To restore the Volume Logix database ............. 116

5.8 FA Port ..................................................................... 117To view FA ports on a Symmetrix .................... 117To view FA port properties................................ 117

Contents v

5.9 Volume ..................................................................... 119Actions.................................................................. 119Type....................................................................... 119State....................................................................... 120Viewing volume properties ............................... 120Viewing volumes ................................................ 122Assigning volumes to HBAs ............................. 126Assigning volumes to hosts .............................. 128Releasing volumes from HBAs......................... 130Releasing volumes from hosts .......................... 131

5.10 Hosts......................................................................... 133Actions.................................................................. 133Viewing host properties ..................................... 133Viewing hosts ...................................................... 134Renaming a host.................................................. 135

5.11 HBA .......................................................................... 137To view HBA properties .................................... 137Viewing HBAs..................................................... 138Renaming an HBA.............................................. 141Clearing an HBA’s access rights ....................... 143Swapping access rights ...................................... 145Moving an HBA to a different host .................. 147

5.12 Reporting ................................................................. 150Report Output ..................................................... 153

Chapter 6 Using the Volume Logix CLI ......................157

6.1 The Volume Logix CLI........................................... 1586.2 Configuring Access Control.................................. 160

Identify your Configuration.............................. 160Update the Volume Logix Database................. 161Activate the Configuration................................ 162

6.3 Simple Case Study.................................................. 163Identify your Configuration.............................. 164Update the Volume Logix Database................. 166Activate the Configuration................................ 168

6.4 Complex Case Study.............................................. 170Identify your Configuration.............................. 172Update the Volume Logix Database................. 176Activate the Configuration................................ 177

vi Contents

6.5 Maintain the Volume Logix Database ................. 178

Chapter 7 Volume Logix CLI.......................................179

7.1 Volume Logix CLI .................................................. 1807.2 fpath Command Description ................................ 181

adddev.................................................................. 182backupdb.............................................................. 185chgname ............................................................... 186clrwwn.................................................................. 189help ....................................................................... 191initdb..................................................................... 193lsbackup ............................................................... 195lsdb........................................................................ 196lshbawwn............................................................. 199lshostdev .............................................................. 200lshosts ................................................................... 202lsstatus .................................................................. 204lssymmdev........................................................... 205lssymmfas ............................................................ 207refresh ................................................................... 208restoredb............................................................... 209rmdev.................................................................... 210swaphba ............................................................... 213

7.3 fpath Error Codes ................................................... 215

Chapter 8 vcmfind Utility ............................................219

8.1 Overview of the vcmfind Command................... 2208.2 vcmfind .................................................................... 2218.3 ASCII WWN............................................................ 223

Chapter 9 fconfig and fcompare Utilities..................225

9.1 Overview of Device Naming ................................ 226How Device Naming Works ............................. 226Device Name Binding ........................................ 228Benefits of fconfig and fcompare...................... 229When to use fconfig and fcompare .................. 229

9.2 fconfig Command Description ............................. 2319.3 fcompare Command Description......................... 233

Contents vii

A Hexadecimal Conversion.........................237

B Volume Logix with HP-UX .........................239

Glossary .............................................................................243Index...................................................................................251Sales and Service Locations ............................................255

viii Contents

ix

Figures

1 Point-to-Point and Multi-Initiator Topologies ....................................... 22 Volume Logix Solution .............................................................................. 33 Volume Logix Administrator Window ................................................. 524 Volume Logix Administrator Menu Bar ............................................... 545 Volume Logix Administrator Tool Bar.................................................. 566 ESN Topology View ................................................................................. 577 Volumes—Icon View................................................................................ 608 Volumes—Details View........................................................................... 619 Volume Logix Administrator Status Bar............................................... 63

10 Volume Logix demo application ............................................................ 7711 Tasks tab..................................................................................................... 9412 Log tab........................................................................................................ 9513 Log file ...................................................................................................... 10714 A Symmetrix Report............................................................................... 15315 An FA Port Report .................................................................................. 15316 A Volume Report .................................................................................... 15417 A Host Report.......................................................................................... 15418 An HBA report ........................................................................................ 15519 Determining Identifiers.......................................................................... 16120 Case Study: Simple Configuration (2) ................................................. 16321 Case Study: Complex Configuration ................................................... 17122 Discovering Devices (Point-to-Point) .................................................. 22723 Discovering Devices (Network)............................................................ 227

x Tables

Tables

1 Volume Logix Administrator Icons ....................................................... 502 Volume Logix Administrator Menu Options ....................................... 543 Volume Logix Administrator Tool Bar Options .................................. 564 Topology View Objects ............................................................................ 585 Topology View Lines ............................................................................... 586 Volumes—Details View Layout ............................................................. 627 Tasks Summary......................................................................................... 908 Properties of a Symmetrix ..................................................................... 1119 Properties of an FA Port ........................................................................ 117

10 Properties of a Volume........................................................................... 12111 Properties of a Host ................................................................................ 13312 Properties of an HBA ............................................................................. 13713 Volume Logix Reports ........................................................................... 15014 Volume Logix Command Summary.................................................... 15915 Steps in Identifying your Configuration ............................................. 16016 Steps in Updating the Database............................................................ 16117 Steps in Activating the Configuration ................................................. 16218 Symmetrix Device Types ....................................................................... 20519 The fpath Command Error Codes........................................................ 21520 vcmfind Error Codes .............................................................................. 22221 fcompare Error Codes ............................................................................ 23422 Hex to Decimal Conversion Chart ....................................................... 23823 Original configuration on Symmetrix using a single FA port ......... 24024 New configuration on Symmetrix using a single FA port................ 241

Preface

As part of its effort to continuously improve and enhance the performance and capabilities of the Symmetrix product line, EMC from time to time releases new revisions of Symmetrix hardware and microcode. Therefore, some functions described in this manual may not be supported by all revisions of Symmetrix microcode, software, or hardware presently in use. If your Symmetrix unit does not offer a function described in this manual, please contact your EMC representative for a hardware upgrade or microcode update.

The following chapters are included in this manual:

Chapter 1, "Introducing Volume Logix" introduces EMC Volume Logix and its capabilities.

Chapter 2, "Installing Volume Logix" lists the installation requirements and explains how to install or uninstall the Volume Logix GUI, CLI and utilities.

Chapter 3, "Introducing Volume Logix Administrator" gives an overview of Volume Logix objects and the Volume Logix Administrator GUI.

Chapter 4, "Using Volume Logix Administrator" explains how to specify access control using the Volume Logix Administrator interface.

Chapter 5, "Managing Volume Logix Objects" describes the procedures for viewing and changing the different elements in the topology.

Chapter 6, "Using Volume Logix CLI" explains how to specify access control using the command line interface.

xi

Chapter 7, "Volume Logix CLI Commands" defines each Volume Logix command.

Chapter 8, "vcmfind Utility" describes how to use the vcmfind utility to discover information.

Chapter 9, "fconfig and fcompare Utilities" describes how to use the fconfig and fcompare utilities to record and verify device name binding.

Appendix A, "Hexadecimal Conversion" provides a chart to convert between decimal and hexadecimal notation.

Appendix B, "Volume Logix with HP-UX" covers some special considerations relating to HP-UX device tables.

RelatedDocumentation

Other Symmetrix publications include:

• Symmetrix Fibre Channel Product Guide, P/N 200-999-642, EMC Corporation

• Symmetrix Open Systems Host Environment Product Guide - Volume I and II,P/N 200-999-563, EMC Corporation

• Symmetrix High Availability Product Guide,P/N 200-999-566, EMC Corporation

• Symmetrix Model 3700 Product Manual, P/N 200-810-531, EMC Corporation

• Symmetrix Model 3430 Product Manual, P/N 200-840-554, EMC Corporation

• Symmetrix Model 33XX Product Manual,P/N 200-858-550, EMC Corporation

• Symmetrix Remote Data Facility Product Guide,P/N 200-999-554, EMC Corporation

xii Preface

Conventions Usedin this Manual

The following conventions are used in this manual:

Boldface is used to highlight complete pathnames, and to emphasize warnings.

A note calls attention to any item of information that may be of special importance to the reader.

Italic font introduces new terms and denotes command line arguments.

A fixed space font introduces command line entries, displayed text, or program listings.

Where to Get Help EMC software products are supported directly by the EMC Customer Support Center.

Obtain technical support by calling the EMC Customer Support Center at one of the following numbers:

or by calling the number of the nearest EMC office listed at the back of this book.

Language services are available upon request.

United States: (800) 782-4362 (SVC-4EMC)

Canada: (800) 543-4782 (543-4SVC)

Worldwide: (508) 497-7901

Preface xiii

xiv Preface

1

Chapter 1 INTRODUCING VOLUME LOGIX

This chapter gives an overview of Volume Logix.

• Why Choose Volume Logix? ................................. 2• What is Volume Logix? .......................................... 4• What is Volume Logix? .......................................... 4

1

1.1 Why Choose Volume Logix?When each host’s storage volumes are kept separate from those of other hosts through direct point-to-point cabling, hosts can only detect volumes to which they are directly connected. In multi-initiator environments, in which multiple hosts are connected to a single Symmetrix port, a problem arises when all hosts have the potential to see and use the same storage volumes. Figure 1 illustrates the connections used in point-to-point and multi-initiator environments.

Figure 1. Point-to-Point and Multi-Initiator Topologies

Volume Logix is volume configuration management (VCM) software which controls access to Symmetrix volumes. Unlike host-based access control mechanisms, which are error prone since each host

HOST 1

HBA 1

FC Hub/Switch

HBA 2

HOST 2

FA2

HOST 1

HBA 2

HOST 2

FA1

HBA 1

Multi-Intitiator

Point-to-

Point

FA1

SYMMETRIXSYMMETRIX

2 INTRODUCING VOLUME LOGIX

1
must be trusted not to conflict with others, the Symmetrix-based access control mechanism provided by Volume Logix avoids such conflicts by single centralized monitoring.
Using Volume Logix, you can define a virtual channel connecting each host with its storage volumes in the Symmetrix, even though there may be many hosts sharing the same Symmetrix port. Figure 2 illustrates access control applied to three hosts in a multi-initiator environment. Volume Logix is used to grant access by Host 1 to two of the three devices available through FA1, and access by Host 2 to the third device. Similarly, Host 3 is granted access to only one of the two devices available through FA2, reserving the second device for use as a spare.

Figure 2. Volume Logix Solution

FA 1

HOST 1

HBA 1

FC Hub/Switch

HBA 2

HOST 2

HBA 3

HOST 3

virtual channels

SYMMETRIX

VCM

FA 2

VCM

Why Choose Volume Logix? 3

1.2 What is Volume Logix?Volume Logix is a combination of Symmetrix microcode and host-based software that allows you to query and define access control on Symmetrix volumes across an enterprise storage network (ESN) from a single, central, administrator station.

Using Volume Logix, you can:

• Display visual representations of Volume Logix objects (for example, Symmetrix and their hosts) and the relationships among these objects. Through the Volume Logix Administrator, you can display an entire ESN in graphical form on a single screen.

• Display listings of Volume Logix objects and the relationships among these objects.

• Assign and revoke access privileges on Symmetrix volumes to hosts connected in a Fibre Channel topology.

• Modify properties associated with Volume Logix objects (for example, change the name of a host) Volume Logix Objects

In a typical Fibre Channel topology, each host is connected to the Fibre Channel hub or switch through one or more Host Bus Adapter (HBA) ports.

Each Symmetrix is connected to the Fibre Channel hub or switch through one or more Fibre Channel Director/Interface Adapter (FA) ports, each FA port providing access to a given set of volumes.

Each port in the Fibre Channel topology (HBA and Symmetrix FA) is uniquely identified by its World Wide Name (WWN).


1
Volume Logix is used to specify which volumes through which FA ports each host HBA port is permitted to access. Volume Logix stores this information in a Volume Logix database (VCMDB) residing inside the Symmetrix.
How Volume Logix Works

Host HBAs connect to a Fibre Channel environment by logging on. When a host attempts to access a storage volume on the Symmetrix, the host HBA’s WWN, as supplied during the logon process to the Fibre, is passed to the Symmetrix FA port. The Symmetrix records the connection, stores the WWN in a Login History table, queries the Volume Logix database, and builds a filter listing the volumes available to that WWN through that FA port. The HBA port then sends I/O requests directed at particular Symmetrix volumes to the FA port. Each request includes the identity of the requesting HBA (from which its WWN can be determined) and the identity of the requested volume (its FA/LUN). The Volume Logix software, which runs on a Symmetrix, processes each I/O request to check that the HBA is allowed to access that volume. Any request for a volume that an HBA does not have access to returns an error to the host. This filter operation does not impose a performance penalty.

For more details on Fibre Channel, please see the Symmetrix Fibre Channel Product Guide.

What is Volume Logix? 5

Volume Logix Interfaces

Volume Logix provides two interfaces:

• Volume Logix Administrator is a Java-based graphical user interface (GUI). See Chapters 3, 4, and 5 for more information.

• The fpath set of commands is a command line interface (CLI) for performing administrative functions. See Chapters 6 and 7 for more information.

Additionally, several Volume Logix utilities on each host perform housekeeping functions in a Fibre Channel environment:

• vcmfind—a utility for discovering the WWN identity information of each HBA. See Chapter 8 for more information.

• fconfig—a utility for recording the binding configuration between the raw device name and a Symmetrix volume. See Chapter 9.

• fcompare—a utility for verifying the binding configuration recorded by the fconfig utility against the actual topology. See Chapter 9.


2
Chapter 2 INSTALLING VOLUME LOGIX
This chapter lists the Volume Logix installation requirements and explains how to install the Volume Logix graphical user interface (GUI), command line interface (CLI), and utilities.

• Preparing to Install Volume Logix ....................... 8• Upgrading Volume Logix .................................... 12• Upgrading the Java Runtime Environment ...... 14• Installing on an Administrator Host.................. 15• Installing Utilities on Host Systems ................... 22• Uninstalling Volume Logix from an

Administrator Host .............................................. 25• Uninstalling Host Utilities................................... 27• Setting Environment Variables ........................... 29• Running vcmfind and fcompare at Start-up..... 34• Checking your Installation .................................. 38• Initializing the Volume Logix Administrator ... 41

7

2.1 Preparing to Install Volume LogixVolume Logix software has three components that are installed separately.

• Symmetrix microcode is installed on a Symmetrix by an EMC Customer Engineer.

• Administrator host or control station software is software that you install after choosing an Administrator host.

• Host utilities software is software that you install on host systems in a Fibre Channel environment. Before you install Volume Logix, identify the hosts that are to be managed with Volume Logix.

Prior to installing Volume Logix, read the Volume Logix Release Notes for specific version and configuration information, and limitations that may apply to any of these key components.

Symmetrix Configuration

Installation and configuration of Volume Logix on the Symmetrix is performed by an EMC Customer Engineer via the Symmetrix service processor. The EMC Customer Engineer upgrades the microcode, designating the device that will be used as the Volume Logix database device, and switching on Volume Logix for those Fibre Adapter (FA) ports that you wish to be under Volume Logix control. The Symmetrix is configured offline.

Fibre Channel Volume Logix is designed to be used in a Fibre Channel environment. It depends upon a Fibre Channel connection between a Host Bus Adapter (HBA) and a Symmetrix FA that allows the HBA to

8 INSTALLING VOLUME LOGIX

2

identify itself to the Symmetrix. The following Fibre Channel topologies are supported:

• Arbitrated loop• Switched fabric

Volume Logix Database Device

The size of the Symmetrix device designated as the Volume Logix database device is 16 Symmetrix cylinders (approximately 7.5 MB). All space on this device is reserved for current and future Volume Logix functions.

There is one Volume Logix database for each Symmetrix. It should be locally mirrored.

The Volume Logix database contains records that specify the devices that may be accessed by a particular WWN through a specific FA. Each FA may control the access for up to 32 unique WWNs. Up to 16 FA ports (depending on the Symmetrix type) may be configured within the Volume Logix database.

Host Systems You can install and run Volume Logix on several supported OS platforms. Refer to the Volume Logix Release Notes for the specific requirements that apply to each platform

Preparing to Install Volume Logix 9

Administrator andHost Software

The Volume Logix software that you install includes:

• Administrator control software: the Volume Logix Administrator GUI, the fpath CLI, and host utilities that allow you to create, modify, and remove access control. You install this software only on the Administrator host.

• Host utilities (vcmfind, fconfig, and fcompare commands) gather information about the Fibre Channel topology. You install these on hosts connected to a Symmetrix.

Windows NT Administrator or UNIX root logins to any host running Volume Logix can set or reset access controls. EMC recommends that you restrict this ability to a single host machine -- designated as the Administrator host or control station—where you can secure access.

Java RuntimeEnvironment

The Volume Logix GUI for the Administrative host requires the Java Runtime Environment (JRE). The Volume Logix CD includes a JRE for each supported platform:

• JRE 1.1.8 for Windows NT systems

• JRE 1.1.7 for Solaris systems

• JRE 1.1.6 for HP-UX systems

EMC recommends that you use the JRE that is on the Volume Logix CD.

Default InstallationDirectories

Volume Logix uses these installation directories:

• Program Files\Symmapps\vcm on Windows NT systems

• /usr/symmapps/vcm on UNIX systems.


2

EMC recommends that you install Volume Logix in the default location. If you choose to install Volume Logix in a different location, follow the instructions in Section on page 29 to set the VLOGIX_DATA environment variable. VLOGIX_DATA is used by the host utilities only.

UnsupportedPlatforms

Volume Logix can provide access control for host platforms that are not supported by this release. Provided that a host can log on to the Fibre, its access can be controlled by either the GUI or CLI, no matter which platform it is running.

Contact EMC Customer Support for help with hosts on unsupported platforms.

Volume Logix cannot determine the configuration of hosts on unsupported platforms because unsupported hosts cannot run the vcmfind utility that discovers the Symmetrix devices attached to each HBA. Instead, you must manually set up a record for these hosts. See “Configuring Access Control” on page 160 and “lshosts” on page 202. for details.

Note also that hosts on unsupported platforms cannot run the Volume Logix fconfig, and fcompare utilities, thus limiting your ability to work with these hosts by name.

Preparing to Install Volume Logix 11

2.2 Upgrading Volume LogixThis section describes what to do to upgrade to Volume Logix 2.1 when a previous version of Volume Logix is currently installed.

Upgrading from Version 1.x

To upgrade to a new version do the following:

1. Copy the directory /usr/symapps/vcm/backup if you want to save customized files.

2. Remove the 1.x host utilities from any UNIX system where they are installed. To uninstall host utilities find and delete the directory in which Volume Logix is installed.

3. Install version 2.x on an Administrator system as described in Section 2.4 on page 15. Install the host utilities as described in Section 2.5 on page 22

4. Replace the directory /usr/symapps/vcm/backup in the new installation with the one that you created in Step 1.

Upgrading from Version 2.0

Two steps are required to upgrade from version 2.0 to version 2.1.

1. On an Administrative host, if you install Volume Logix 2.1 over 2.0 and want to use the latest JRE (on the Volume Logix CD-ROM), you must first


2

remove the previous version of the JRE. See “Upgrading the Java Runtime Environment” on page 14 for instructions.

EMC recommends that you use the JRE that is on the Volume Logix CD. Using a version of the JRE other than the version shipped with Volume Logix may cause unexpected results when you run the application.

2. Install Volume Logix 2.1 using the instructions in Section 2.4 on page 15 for an Administrator Host. and in Section 2.5 on page 22 to install the host utilities.

Upgrading Volume Logix 13

2.3 Upgrading the Java Runtime Environment

If you are installing Volume Logix over a previous version, and want to use the latest Java Runtime Environment that is on the CD, you must first remove the previous version of the JRE:

1. Change to the installation directory of the Volume Logix Administrator.

On UNIX systems, type:

cd /usr/symmapps/vcm

On Windows NT systems use the Windows NT Explorer to change to:

C:\Program Files\Symmapps\vcm

2. Remove the directory containing the Java Runtime Environment:

On Unix systems, type:

rm -rf jre

On Windows NT systems, right click the JRE folder and select Delete.

3. Follow Volume Logix Administrator installation instructions, using the same installation directory that you used for the previous version of Volume Logix.


2

2.4 Installing on an Administrator HostThis section describes how to install Volume Logix on a Windows NT or UNIX system designated as the Administrator host. See Section 2.5 on page 22 for instructions for installing host utilities.

Installing on a Windows NT System

1. Log on to a Windows NT system as Administrator.

2. Insert the CD-ROM into the drive.

3. Using Windows NT Explorer, click the CD-ROM. icon.

4. Click startup to launch the installer.

5. You are prompted to select Administrator, Host, or Cancel. Select [A]. Press Enter.

6. The install dialog begins with an Introduction window. Click Next.

7. The install dialog prompts you to specify the folder where you want to install Volume Logix:

Installing on an Administrator Host 15

EMC recommends that you useC:\Program Files\Symmapps\vcm.

Select a folder and click Next.

8. The install dialog prompts you to select a Java Virtual Machine (JVM) also called the Java Runtime Environment (JRE):


2

You can install the JVM from the Volume Logix CD, or point to one already installed on the host. Then click Install.

EMC recommends that you use the JRE supplied with Volume Logix. If you use a JRE already installed on the host, make sure that it is Revision 1.1.6 or later.

9. After the software has been installed, click Done to end the installation. Then remove the CD-ROM from the drive. EMC recommends that you restart the Administrator host at this time.

The Volume Logix Administrator GUI, fpath command line interface, and vcmfind, fconfig, and fcompare utilities are now installed.

Next, configure the Administrator host, and test installation. For instructions see Section on page 29, Section 2.9 on page 34 and Section 2.10 on page 38 to continue setting up the Administrative host.

For information about installing host utilities see “Installing Utilities on Host Systems” on page 22


Installing on a UNIX System

This section describes how to install Volume Logix on a UNIX system designated as the Administrator host. The instructions in this section specify how to install the GUI interface. If you want to install only the command line interface, turn to “Installing the Command Line Interface” on page 20.

1. Log onto the UNIX system as root.

2. Start the windowing environment you use. (For example, X Windows or Open Windows.)

If you do not have a graphics display, then you can only install the CLI. See “Installing the Command Line Interface” on page 20 for more information.

3. Mount the CD-ROM to a subdirectory, for example, /cdrom.

4. Mount the CD-ROM.

Solaris. On Solaris systems, if the automounter is running, the CD-ROM mounts unattended.To mount the CD-ROM manually, the form of the command is:

:

where x is replaced by values specific to your site. For example:

HP-UX To mount the CD-ROM, you must use the -o option exactly as shown here. The form of the command is:

mount -F hsfs -o ro /dev/dsk/cxtxdxs0 /cdrom

mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom

mount -F cdfs -o cdcase /dev/dsk/cxtxdxs0 /cdrom


2


All Platforms 5. Change to the directory where you mounted the CD-ROM. For example:

cd /cdrom/

6. Locate the installation script and launch the installer. For example:

./startup.sh

7. You are prompted to select Administrator (A), Host (H), or Cancel (C). Select [A] and press Enter.

8. The install dialog begins with a Welcome window. Click Next.

9. The install dialog prompts you to specify the folder where you want to install Volume Logix:

EMC recommends that you use the folder: /usr/symmapps/vcm.

Specify a directory and click Next. 10. The install dialog prompts you to select a JVM

also called the Java Runtime Environment (JRE):

mount -F cdfs -o cdcase /dev/dsk/c5t2d0 /cdrom


You can install the JVM from the Volume Logix CD, or use one already installed on the host. Then click Install.

EMC recommends that you use the JRE supplied with Volume Logix. If you use a JVM already installed on the host, make sure that it is Revision 1.1.6 or later.

11. After the software has been installed, click Done to end the installation.

12. Unmount the CD-ROM and remove it from the drive. For example, to unmount from mount point /cdrom, type:

umount /cdrom

13. EMC recommends that you reboot the host.

Volume Logix Administrator, fpath, vcmfind, fconfig, and fcompare are installed on the Administrator host. • For information about setting environment

variables on the Administrator host, turn to Section on page 29.

• For information about installing Volume Logics on host machines see “Installing Utilities on Host Systems” on page 22.

Installing the Command Line Interface

On UNIX platforms, you may want to install only the CLI and host utilities on an Administrative host.

1. Create the directory /usr/symmapps/vcm. Enter:

mkdir -p /usr/symmapps/vcm

2. Change to this directory. Enter


2


3. Extract the tar file for your platform. Type:

Solaristar -xvf /cdrom/admin/SOLARIS/ttyadmin_SunOS_2_1.tar

HP-UX:tar -xvf /cdrom/admin/HP/ttyadmin_HP-UX_2_1.tar

4. Unmount the CD-ROM. For example, to unmount from mount point /cdrom, type:

umount /cdrom

The fpath CLI is installed in the specified directory.

5. Follow the instructions in “UNIX System” on page 25 in the Installing Utilities on Host Systems section to install the host utilities on the Administrator host.

For information about setting environment variables, turn to Section on page 29. For information about configuring Volume Logix, see Section 2.9 on page 34.


2.5 Installing Utilities on Host SystemsThis section describes how to install host utilities. See Section 2.4 on page 15 for information about installing Volume Logix on an Administrative host.

Windows NT Systems


2. Insert the CD-ROM into the drive.

3. Using Windows NT Explorer, open the icon for the CD-ROM.

4. Click startup to launch the installer.

5. You are prompted to select Administrator, Host or Cancel. Select [H] and click Enter.

6. The install dialog begins with an Introduction window. Click Next.

7. The install dialog prompts you to specify the folder where you want to install the utilities:


2

8. EMC recommends that you accept the default location (C:\Program Files\Symmapps\vcm).

9. Click Next to install the utilities.The utilities are installed into the directory you specified.

For information about setting environment variables, turn to Section on page 29. For information about configuring Volume Logix, see Section 2.9 on page 34

UNIX Systems This section describes how to install the host utilities on UNIX platforms.


2. Mount the CD-ROM to a subdirectory, for example, /cdrom.

Solaris If the automounter is running, the CD-ROM mounts unattended.

Installing Utilities on Host Systems 23

To mount the CD-ROM manually, the form of the command is:


HP-UX To mount the CD-ROM, you must use the -o option as shown here. The form of the command is:


All Platforms 3. Launch the installer. Enter

./startup.sh

4. You are prompted to select Administrator, Host, or Cancel. Select [H].

5. Press Enter to accept the Source File default.

6. Press Enter to accept the Destination default (/usr/symmapps/vcm), or type an absolute pathname for the destination.

At this point the host utilities are installed. For information about setting environment variables, turn to Section on page 29. For information about configuring Volume Logix, see Section 2.9 on page 34.

mount -F hsfs -o ro /dev/dsk/cxtxdxs0 /cdrom

mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom

mount -F cdfs -o cdcase /dev/dsk/cxtxdxs0 /cdrom

mount -F cdfs -o cdcase /dev/dsk/c5t2d0 /cdrom


2

2.6 Uninstalling Volume Logix from an Administrator Host

This section describes how to uninstall the Volume Logix version 2.0 or 2.1 software.

Windows NT System

To uninstall Volume Logix on a Windows NT Administrator host:


2. Make a copy of the folder:

C:\Program Files\Symmapps\vcm\Backup

if you want to save your customized configuration files before you uninstall Volume Logix.

3. Click Start and select Settings-Control Panel. Click Add/Remove Programs. Select Volume Logix from the list and click Add/Remove to launch the uninstaller.

4. After the uninstall program completes, delete all folders in


UNIX System To uninstall Volume Logix on a UNIX Administrative host:


Uninstalling Volume Logix from an Administrator Host25

2. Make a copy of the directory:

usr/symmapps/vcm/backup

if you want to save your customized configuration files before you uninstall Volume Logix.

3. Start X Windows, Open Windows, or CDE if one of these applications is not already running.

4. To remove the Volume Logix GUI, change directories to

install_dir/UninstallerData

where install_dir is the directory in which you installed Volume Logix. For example:

cd /usr/symmapps/vcm/UninstallerData

5. Uninstall Volume Logix. Enter

./Uninstall_vlogix

Command Line Interface

To uninstall the CLI from a UNIX Administrator host:


2. Make a copy of the directory:

usr\symmapps\vcm\backup

if you want to save your customized configuration files.

3. Change to the \usr\symmapps directory and delete the vcm subdirectory using the rm command. Type:

cd /usr/symmappsrm -rf vcm


2

2.7 Uninstalling Host UtilitiesThis section describes how to uninstall host utilities from a host system where Volume Logix version 1.x (UNIX systems only), or 2.x (UNIX and Windows NT systems) is installed.

Windows NT System

To uninstall host utilities on a Windows NT host system:


2. Click Start and select Settings-Control Panel. Click Add/Remove Programs. Select Volume Logix from the list and click Add/Remove to launch the uninstaller.

3. After the uninstall program completes, delete all folders in


UNIX System To uninstall host utilities from a UNIX host system where Volume Logix 2.x is installed:


2. Change to the directory where you installed the host utilities. For example


3. Delete the directory and its contents. For example

Uninstalling Host Utilities 27

rm -rf vcm

4. To delete the vcmfind startup script

On Solaris, type

rm -f /etc/rc2.d/S99vcmfind

On HP-UX, type

rm -f /sbin/rc2.d/S99vcmfind


2

2.8 Setting Environment VariablesThe environment variables to set for satisfactory performance on your system include:

• Set the VLOGIX_DATA environment variable if you did not install Volume Logix in the default folder or directory.

• Set the VCMDBDEVICE environment variable to identify the location of the Volume Logix database for use with commands.

• Set the PATH environment variable to include the Volume Logix home directory.

Setting the VLOGIX_DATA Environment Variable

By default, the fconfig command writes data files such as the .fconfig file to:

C:\Program Files\symmapps\vcm (Windows NT systems)

or

/usr/symmapps/vcm (UNIX systems)

When you set the VLOGIX_DATA environment variable, you can direct the fconfig command to write its data files to other locations.

EMC recommends that you set the VLOGIX_DATA environment variable to the Volume Logix installation directory:

C:\Program Files\Symmapps\vcm (Windows NT systems)

or

Setting Environment Variables 29

/usr/symmapps/vcm (UNIX systems)

Note: If you set VLOGIX_DATA to a directory other than the default installation directory, copy the error_list file to the non-default directory.

Ensure that the file system containing the Volume Logix directory is present at boot time and that the home directory gives write permission to Administrator (Windows NT) or root (UNIX system).

Windows NTSystem

To set VLOGIX_DATA, do the following.

1. Click Start, Settings, Control Panel. Click the System icon then select the Environment tab.

2. In the Variable window, type:

VLOGIX_DATA

In the Value window, type the path, for example, the default path is:


3. Click Set, then Apply, then OK.

4. If you did not set VLOGIX_DATA to the default installation directory, copy the error_list file to the directory where VLOGIX_DATA is set

UNIX System To set VLOGIX_DATA, perform the following.

1. For a UNIX C shell:

setenv VLOGIX_DATA /path

where path points to the Volume Logix installation directory, for example, /usr/symmapps/vcm.


2

For a UNIX Korn or Bourne shell:

set VLOGIX_DATA=/pathexport VLOGIX_DATA

where path points to the Volume Logix installation directory, for example, /usr/symmapps/vcm.

2. If you did not set VLOGIX_DATA to the default installation directory, copy the error_list file to the directory where VLOGIX_DATA is set.

VCMDBDEVICE Environment Variable

When you issue an fpath command, you must specify the pathname to the Volume Logix database device using the -d parameter. If you do not want to type this pathname each time you issue a command, you may specify the path in an environment variable, VCMDBDEVICE.

If VCMDBDEVICE is set, the -d pathname argument in fpath commands overrides this default.

This short cut is useful in two situations:

• There is only one Symmetrix

• You are setting up each Symmetrix in turn

▼ If there are several Symmetrix systems in the environment, each with its own Volume Logix database, take care to reset or override this environment variable so that the fpath commands act on the VCMDBDEVICE that you intend.

Windows NTSystem

To set VCMDBDEVICE, do the following.

1. Click Start, Settings, Control Panel. Click the System icon then select the Environment tab.


2. In the Variable window, type VCMDBDEVICE.

3. In the Value window, type:

\\.\PHYSICALDRIVEx

where x is the drive number of the VCMDB device shown in the output of the fpath lshostdev command. For example, \\.\PHYSICALDRIVE1.

4. Click Set, then Apply, then OK.

Alternatively, at the MS-DOS prompt, type:

set VCMDBDEVICE=\\.\PHYSICALDRIVEx

where \\.\PHYSICALDRIVEx is the drive number of the VCMDB device shown in the output of the fpath lshostdev command, for example, \\.\PHYSICALDRIVE1.

UNIX System To set VCMDBDEVICE, perform the following.

For UNIX C shell:

setenv VCMDBDEVICE /dev/rdsk/cxtxdxsx

where /dev/rdsk/cxtxdxsx is the path to the VCMDB device shown in the output of the fpath lshostdev command, for example, /dev/rdsk/c1t1d0s2.

For UNIX Korn or Bourne shell:

set VCMDBDEVICE=/dev/rdsk/cxtxdxsxexport VCMDBDEVICE

where /dev/rdsk/cxtxdxsx is the path to the VCMDB device shown in the output of the fpath lshostdev command, for example, /dev/rdsk/c1t1d0s2.


2

PATH Environment Variable

For convenience, you may wish also to add the Volume Logix installation folder or directory to your PATH environment variable as follows:

Windows NTSystem

1. Click Start, Settings, Control Panel. Click the System icon then select the Environment tab

2. On the upper scroll box titled System Variables, scroll down and click once on Path.

3. In the lower window titled Value, without altering the current contents, append this string:

;C:\Program Files\Symmapps\vcm

4. Click on Set, then Apply, then OK.

UNIX System For a UNIX C shell:

set path = ($path /usr/symmapps/vcm)

For a UNIX Korn or Bourne shell:

PATH=$PATH:/usr/symmapps/vcm export PATH


2.9 Running vcmfind and fcompare at Start-up

Once Volume Logix has been installed and the system configured:

• Run the fconfig utility (on all hosts) to create a baseline Name Bindings table (.fconfig file) for each host. The table is used to map raw device names to the Symmetrix volume members.

• Run both the vcmfind and fcompare utilities on all hosts after the host has booted. Refer to Overview of the vcmfind Command on page 220 and Overview of Device Naming on page 226 for more detailed information on using these utilities to record and compare device name binding information.

NOTE: In addition to running the fconfig utility at start up, run it whenever you add to or remove hosts from the configuration managed by Volume Logix.

Windows NT System

Windows NT lets you automatically run a program each time Windows NT starts by including it in the start-up folder. Alternatively, you can choose to run each utility manually.

You need to run three programs at start-up:

1. First, run vcmfind to discover WWN identity information and to map an AWWN to each WWN for that session.

2. Next, run fcompare to check the name bindings defined in the .fconfig file against the actual topology.


2

3. Finally, run a script that you write to check each difference reported by fcompare and take appropriate action. (Refer to fconfig Command Description on page 231 and fcompare Command Description on page 233 for example scripts.)

The procedure for including a program in the Windows NT start-up folder is:

1. Click Start, and then point to Settings.

2. Click Taskbar, and then click the Start Menu Programs tab.

3. Click Add, and then click Browse.

4. Locate the program (installed by default in C:\Program Files\Symmapps\vcm\vcmfind.exe) you want to start, and then click it.

5. Click Next, and then click the Start-Up folder.

6. Type the name that you want to see on the StartUp menu, and then click Next.

7. If Windows NT prompts you to choose an icon, click one, and then click Finish.

8. Repeat Steps 3 through 7 to add fcompare and your user-written script. Finally, click OK.

UNIX System On UNIX systems, you can either:

Running vcmfind and fcompare at Start-up 35

• Run each utility manually, or

• Edit your start-up file so that these utilities are automatically run each time the system is rebooted.

Editing Start-up Files

▼ To maintain the integrity of your system, contact your UNIX customer service representative for information about editing UNIX system startup files.

When a UNIX system is booted, it starts a daemon (usually called init(1M)) which takes its instructions from a start-up file (usually called /etc/inittab, short for init table). The contents of the inittab file differs greatly depending on which flavor of UNIX is running. Also, the procedure for editing inittab differs greatly — on some systems, it must not be edited by hand.

When you run Volume Logix, the inittab file must perform these steps at boot time:

1. After the system has logged onto the Fibre Channel, execute a shell script to run vcmfind.

2. Before other file systems are mounted and before the system is brought into multi-user mode, run a shell script to mount the /usr file system and run fcompare.

3. If fcompare returns a reply code of 0, then let the inittab process continue and bring the system up in multi-user mode.

4. If fcompare returns a non-zero reply code, then cause the inittab process to halt while the system is still in single-user mode. You should investigate all inconsistencies before mounting file systems.


2

On Solaris systems, you may instead choose to modify one of the scripts in /etc/rc2.d/ which contain the commands for entering or leaving run level. Edit this script so that it runs vcmfind and fcompare before any file systems are mounted.

See the command descriptions for vcmfind on page 220 and fcompare on for details of running each utility and for example shell scripts.

Running vcmfind and fcompare at Start-up 37

2.10 Checking your InstallationTo recap, these steps should now be complete:

1. The Volume Logix microcode has been installed on the Symmetrix system by a EMC customer service engineer who should also have checked that:

• All Fibre Channel connections work.

• A device in each Symmetrix has been designated as the Volume Logix database.

• Each FA port has been configured to access the Volume Logix database device.

• For those FA ports which:

• are connected to hosts and• wish to enforce access control

Volume Logix is switched on.

• For those FA ports which are not started, not connected to hosts, or which provide open access to their devices, Volume Logix is switched off.

2. The Volume Logix control software (the Volume Logix Administrator GUI, the fpath CLI and the host utilities (vcmfind, fconfig, and fcompare) have been installed on an Administrator host.

3. The Volume Logix host utilities (vcmfind, fconfig, and fcompare) have been installed on all hosts.


2

4. The Administrator host should have been rebooted and lshostdev run to verify that the Volume Logix database device is accessible from this host.

5. EMC recommends that all non-Administrator host have been rebooted and vcmfind has been run on each host to assign AWWNs to the hosts and HBAs. The HBAs of any host that does not run vcmfind will be shown as located within a single unnamed host.

Display VCMDB Device

To confirm that your installation is working correctly, enter the following command on the Administrator host:

fpath lshostdev

If your system is correctly set up, then before you have defined any access controls, this command should display for each Symmetrix connected to this host, a single device—the Volume Logix database device (VCMDB)— for each path from this host to the Symmetrix.

For example:

This example output shows a UNIX host HBA with two paths to the Symmetrix, via FA 15a and FA 16b, each providing access to a single VCMDB device via pathnames /dev/rdsk/c1t0d0s2 and /dev/rdsk/c1t1d0s2. The example output for a Windows NT host would be similar, except that the pathname field would show NT-style device names such as \\.\physicaldrive2.

fpath, Copyright EMC Corp. 1998-1999Symmetrix Fibre Devices on this computer

Pathname TID LUN Device Symm serial FA /dev/rdsk/clt0d0s2 0 0 000 0182601088 15a VCMDB/dev/rdsk/c1t1d0s2 0 0 000 0182601088 16b VCMDB

Checking your Installation 39

If no devices are listed, then check that:

• The physical connections between the host and the Symmetrix are intact. In a loop environment, this involves checking the physical connections for all hosts and Symmetrixes in the loop. In a switch environment, this involves checking that the host and the Symmetrix have each successfully logged into the fabric.

• The appropriate device driver for your Fibre Channel HBA is loaded.

• The Administrator host was rebooted and lshostdev run to verify that the Volume Logix database device is accessible from this host.

• On Solaris, verify that the cxtxdx of the vcmdb is configured correctly in the /kernel/drv/sd.conf file so that the device can display.

If all devices are listed, please contact your EMC representative to correctly configure Volume Logix.


2

2.11 Initializing the Volume Logix Administrator

Volume Logix ships with an Administrator already defined so that you can start the GUI interface. Before moving Volume Logix to a production environment, you should change the password for this user account.

Additionally, you should tell Volume Logix where to find a web browser on your system so that it can display the online help files.

Starting the Volume Logix Administrator

Follow this procedure the first time that you start Volume Logix after installing the software. For subsequent starts, see Starting the Volume Logix Administrator on page 66.

EMC recommends that you run vcmfind on every host prior to starting the Volume Logix Administrator.

You can start Volume Logix from the Start menu or a Command Prompt window.

Initializing the Volume Logix Administrator 41

From Windows NTStart menu

1. Log on to the Windows NT system as Administrator.

2. Click on Start in the Task bar, and then point to Programs—Volume Logix—Volume Logix Administrator 2.1. Volume Logix displays the following dialog box:

3. Click OK. Volume Logix prompts you to change the password.

Note: Passwords are case-sensitive.

4. Enter the default 4-character password, P2%0, supplied with the Volume Logix software in the Old Password text box. Enter the new password in the New Password text box. Enter the new password a second time in the Retype to confirm text box and then press Enter. The new password takes effect immediately.

The Volume Logix Administrator workspace is displayed on your workstation. If there are a large number of devices configured on the Symmetrix systems, it can take several minutes for the workspace to display.


2

From aWindows NTCommand

Prompt window

1. Log on to the Windows NT system as Administrator.

2. Open a Command Prompt window.

3. Change directories to the directory where Volume Logix is installed. For example,

cd D:\Program Files\Symmapps\vcm

4. Enter vlogix.bat

vlogix.bat

5. Volume Logix displays the following dialog box:


Passwords are case-sensitive.

7. Enter the default password (4 characters: P2%0) supplied with the Volume Logix software in the Old Password text box. Enter the new password in the New Password text box. Enter the new


password a second time in the Retype to confirm text box and then press Enter. The new password takes effect immediately.

The Volume Logix Administrator workspace is displayed on your workstation. If there are a large number of devices configured on the Symmetrix systems, it can take several minutes for the workspace to display

From a UNIXSystem


2. From the command line, change directories to the directory where Volume Logix is installed. For example, cd /usr/symmapps/vcm.

3. Run the vlogix.sh script. Enter

./vlogix.sh

4. Volume Logix displays the following dialog box:




2

6. Enter the default password (4 characters: P2%0) supplied with the Volume Logix software in the Old Password text box. Enter the new password in the New Password text box. Enter the new password a second time in the Retype to confirm text box and then press Enter. The new password takes effect immediately.

The Volume Logix Administrator workspace is displayed on your workstation. If there are a large number of devices configured on the Symmetrix systems, it can take several minutes for the workspace to display

Renaming Unnamed Hosts

If a host called Unnamed is displayed in the left-hand topology pane:

• Either you omitted to run vcmfind on one or more of the hosts

• Or you are running in a switched environment. At this release, Volume Logix displays the switch connection as a host and since you can’t run vcmfind on a switch, it will show as “Unnamed”. You can ignore the Unnamed host, or you can use the HBA Properties sheet to manually rename the WWNs associated with the Unnamed host. To do this:

1. Expand the Unnamed host icon.

2. Select a WWN and display the Properties sheet.

3. Enter a new name for the Unnamed host in the Host box (for example, switch1) and apply the change.

4. Enter a new name for the WWN in the Bus box (for example, port1) and apply the change.

5. Run the task list.


See “Renaming an HBA” on page 141 for more information.

Help browser The online help is supplied as HTML pages. On a UNIX system, you must specify the path to your preferred web browser to Volume Logix so that it can launch the web browser when you request Help.

1. On the Volume Logix Administrator menu bar, select Help.

2. From the Help pull-down menu, select Settings.

3. Either type the path to the executable for your preferred web browser or click the Browse button to discover the executable.

4. If you chose to click the Browse button, a dialog is displayed.


2
5. Move to the folder containing the executable for
your preferred browser. Select the file and click Open.

6. The path is displayed in the User Settings field. Click OK.

You have now completed initializing the Volume Logix Administrator. See Stopping the Volume Logix Administrator on page 69 to exit.



3
Chapter 3 INTRODUCING
VOLUME LOGIX ADMINISTRATOR

This chapter introduces the Volume Logix Administrator GUI.

• Volume Logix Administrator .............................. 50• Volume Logix Administrator Window.............. 52• Menu Bar................................................................ 54• Tool Bar................................................................... 56• ESN Topology Pane .............................................. 57• Volumes Pane ........................................................ 60• Status Bar ............................................................... 63

49

3.1 Volume Logix AdministratorVolume Logix Administrator is a Java-based GUI that allows you to query and define access control on Symmetrix volumes across an enterprise storage network (ESN) from a single, central control station.

Volume Logix Administrator displays the components of an ESN as objects. Each object is represented by an easily recognizable icon. The following table identifies the objects in a Volume Logix system and the icon used to represent them.

Table 1. Volume Logix Administrator IconsThis icon Represents a ...

Symmetrix

FA port

Symmetrix volume

Volume Logix database

Business Continuity Volume (BCV)

Meta volume

Host

Administrator Host (control station)

Host bus adapter

50 INTRODUCING VOLUME LOGIX ADMINISTRATOR

3

These are the objects that you, as the storage manager, can manipulate using the Volume Logix Administrator. The relationships that you define among these objects determine which host/HBA pairs can access volumes on a Symmetrix/FA port pair.

Note some objects within the ESN that are not under Volume Logix control — hubs and switches, for example — are not displayed.

Object Properties Objects within a Volume Logix system are defined by a set of properties, or attributes, that define key aspects of that object. Some properties, such as the Symmetrix serial number, are controlled by the system and cannot be changed. Other properties, such as the host name, while initially set by the system, are dynamic and can be changed by you.

Object Actions You perform actions by selecting objects and (sometimes) invoking a menu command or right-clicking on the objects. An action can be performed on a single object (such as changing the name of a host), or a set of objects of the same or different types (such as setting up multi-pathing).

The Volume Logix Administrator assumes the mouse has two buttons. The left button is used to select objects. The right button is used to display popup menus. For more information on selecting objects, see Exploring the Volume Logix Administrator Workspace in the on-line help.

Volume Logix Administrator 51

3.2 Volume Logix Administrator WindowAs a visual medium, the Volume Logix Administrator allows you to gather substantial information about an ESN simply by glancing at the screen. You can quickly navigate to a specific object and initiate a configuration task with the click of a button. The Volume Logix Administrator workspace is shown below.

Figure 3. Volume Logix Administrator Window

The figures in this book show Volume Logix on the Windows NT platform. If you are using Volume Logix on a different platform, your windows and icons may not be the same as shown here. The functionality, however, is the same across all platforms.


3

The workspace has the following components:

• Menu bar• Tool bar• ESN Topology pane• Volumes pane• Status bar

Volume Logix Administrator Window 53

3.3 Menu Bar

Figure 4. Volume Logix Administrator Menu Bar

The menu bar, shown in Figure 4, is positioned across the top of the Volume Logix Administrator workspace. It has five pull-down menus, each providing several options:

Table 2. Volume Logix Administrator Menu Options

Menu Options Function

File Run Tasks Executes the queued configuration operations.

Properties Displays or modifies the properties of the selected object.

Report Generates a report for the selected object.

Save Log Saves the completed tasks to the current log file.

Save Log As Specifies a new log file for completed tasks.

Exit Stops the Volume Logix Administrator.

Edit Tasks Modifies or deletes a queued configuration operation.

Change Passwords Changes your login password.

Select All Selects all volumes displayed in the Volumes view.

Invert Selection Inverts the selections in the Volumes view.

View Icons Displays volumes as icons in the Volumes view.

Details Displays a table in the Volumes view.

Reload Display Repaints the workspace to reflect the configuration currently stored in the Volume Logix database.

Refresh Display Repaints the workspace without reloading data from the Volume Logix database.


3

Actions Bus Clears all or swaps access rights on a bus.

Volume Adds or removes access privileges to a Symmetrix volume.

Symmetrix Activates the configuration for a Symmetrix or manipulates the Volume Logix database.

Help Contents Displays Help files.

About Volume Logix Displays information about this version of the Volume Logix Administrator.

Settings Sets the path to the HTML browser used to view Help

Table 2. Volume Logix Administrator Menu Options (Continued)

Menu Options Function

Menu Bar 55

3.4 Tool Bar

Figure 5. Volume Logix Administrator Tool Bar

The buttons on the tool bar, shown in Figure 5, provide quick access to some of the most frequently used Volume Logix options.

Table 3. Volume Logix Administrator Tool Bar Options

Button Name Description

Properties Displays the Properties dialog box for currently selected items

Reload Display Reloads the current configuration from the Volume Logix database.

Run Tasks Commits all pending volume assignments for all Symmetrixes or a selected Symmetrix.

Icons Displays volumes as icons. Mutually exclusive with the Details button.

Details Shows volumes in a table. Mutually exclusive with the Icons button.

Help Displays Help file.


3

3.5 ESN Topology PaneOn the left-hand side of the Volume Logix Administrator window is the ESN Topology pane. This shows the paths between host/HBA pairs and Symmetrix/FA port pairs in a Fibre Channel topology. Paths are anchored by hosts on the left-hand side of the display and by Symmetrixes on the right-hand side of the display.

Figure 6. ESN Topology View

ESN Topology Pane 57

The Topology view displays the objects shown in Table 4 connected by the lines shown in Table 7.

Entities in an ESN that are not under Volume Logix control are not shown.

Table 4. Topology View Objects

Host Administrator Host (control

station)

HBA FA Port Symmetrix

A host can either be collapsed or expanded.

A collapsed host hides the HBAs attached to it; an expanded host shows the HBAs attached to it.

When a host is collapsed, path connections are drawn directly from the host to the Symmetrix or FA port. When the host is expanded, path connections are drawn from the host to the HBA, and then to the Symmetrix or FA port.

Visible when a host is expanded.

Visible when a Symmetrix is expanded.

A Symmetrix can either be collapsed or expanded.

A collapsed Symmetrix hides the FA ports residing on it, while an expanded Symmetrix shows the FA ports residing on it.

When a Symmetrix is collapsed, path connections are drawn directly from the Symmetrix to the host or HBA. When the Symmetrix is expanded, path connections are drawn from the Symmetrix to the port, and then to the host or HBA.

Table 5. Topology View Lines

Line Description

Gray lines, representing paths, connect the various objects in the ESN topology view.

Black lines indicate a selected connection.

Blue lines indicate an assignment to the volume selected in the Volumes view.

Red lines indicate a broken assignment (for example, the HBA has logged out from the Fibre Channel).


3

The ESN Topology view allows you to view the paths at different levels of granularity. You can view the connections from

• host to Symmetrix• host/HBA to Symmetrix• host to FA port on a Symmetrix• host/HBA to FA port on a Symmetrix

This visibility into the ESN allows you to effectively manage access control in an ESN in a top-to-bottom manner — from a host down to its HBAs and from a Symmetrix down to its ports.

Single clicking on an object highlights the path connections associated with that object in the ESN Topology view, and fills the Volumes view with all volumes owned and possibly available to or residing on that object.

For example, assume that hostA/bus1 owns volume 001 (which is accessible and owned by hostA/bus1 via FA 3a and FA15a). Selecting bus1 results in connection lines being highlighted between hostA/bus1 and FA 3a and FA 15a in the ESN Topology view, and all the volumes accessible via FA 3a and FA 15 being displayed in the Volumes view. The status of Volume 001 is shown further by a blue border indicating that it is owned by the selected object, in this case bus1. All other connection lines remain light gray if they are not selected, or black if they are a selected connection.

Right clicking on a selected object displays a popup menu, which allows you to view properties or invoke a command.

Double clicking a Symmetrix icon, host icon, or expansion sign expands or collapses that object. (The expansion icon varies by platform.)

ESN Topology Pane 59

3.6 Volumes PaneOn the right-hand side of the Volume Logix Administrator window is the Volumes pane. Clicking on an object in the ESN Topology pane, populates the Volumes pane with the volumes available to or residing on the selected object.

Two views are available: an Icons view or a Details view. To choose:

• On menu bar, select View, then Icons or Details • On tool bar, select the Icons or Details button

Icons view The Icons view displays an icon for each volume associated with the objects selected in the ESN Topology view.

Figure 7. Volumes—Icon View


3

The volumes are sorted first by Symmetrix (if more than one Symmetrix is selected), and then by name/device number.

If the number of volumes exceeds the available space, a scroll bar appears on the right side of the view.

Details view The Details view displays a table with extended information about the volumes associated with the objects selected in the ESN Topology view.

Figure 8. Volumes—Details View

The table is sorted first by Symmetrix (if more than one Symmetrix is selected), and then by device number.

Volumes Pane 61

If the number of volumes exceeds the available space, a scroll bar appears on the right side of the view.

The following table identifies each column in the Table view:

You can show, hide, resize, or rearrange the columns in the table.

The mouse actions are the same for both the Icon and Table view:

• Single clicking on an owned or shared volume highlights the connection lines associated with that ownership in blue. For example, if hostA/HBA1 owns volume 001 on FA3a and FA15a, then the connection lines between the hostA/HBA1 and FA3a and FA15a turn blue. All

Table 6. Volumes—Details View Layout

Column Description

Volumes Displays the volume icon.

Capacity Capacity in GigaBytes of this volume.

Symmetrix Name of Symmetrix on which this volume resides.

FA ports List of Symmetrix/FA port pairs through which this volume can be accessed. You may need to expand this column to read the entire value.

Owners List of host/HBA pairs assigned access rights on this volume. You may need to expand this column to read all the values.


3

other connection lines remain light gray if not a selected connection, or black if it is a selected connection.

• Right clicking on a volume displays a popup menu that allows you to view properties, add, remove, or clear access rights, or generate a report.

3.7 Status Bar

Figure 9. Volume Logix Administrator Status Bar

The status bar is positioned across the bottom of the Volume Logix Administrator workspace. The left side displays informational text about the current action; the right side indicates the number of pending tasks on the task list.

Status Bar 63


4

Chapter 4 USING VOLUME LOGIX ADMINISTRATOR

This chapter explains how to configure access control through the Volume Logix Administrator interface.

• Starting the Volume Logix Administrator......... 66• Stopping the Volume Logix Administrator ...... 69• Changing the Password ....................................... 73• Configuring Access Control ................................ 74• Simple Case Study ................................................ 77

65

4.1 Starting the Volume Logix Administrator

If you are starting Volume Logix for the first time, see Initializing the Volume Logix Administrator on page 41.

You must be logged on as Administrator (Windows NT) or root (UNIX) to use the Volume Logix Administrator.

EMC recommends that you have previously run vcmfind and fcompare on each client host. Refer to Running vcmfind and fcompare at Start-up on page 34 for step-by-step instructions.

From Windows NT

There are two ways to start the Volume Logix Administrator:

• from the Start menu• from a Command Prompt window

From the Startmenu

1. Click on Start in the Task bar, then point to Programs—Volume Logix—Volume Logix Administrator 2.1.

Volume Logix prompts you for a password.


66 USING VOLUME LOGIX ADMINISTRATOR

4

2. Type your password and press Enter. The Volume Logix Administrator workspace is displayed on your workstation.

From a CommandPrompt window

1. Open a Command Prompt window.

2. Change directories to the directory where Volume Logix is installed. For example:

C:\>cd C:\Program Files\SymmApps\vcm

3. Enter vlogix:

C:\Program Files\SymmApps\vcm>vlogix


4. Type your password and press Enter. The Volume Logix Administrator workspace is displayed on your workstation.

From UNIX 1. From the command line, change directories to the directory where Volume Logix is installed. For example:


2. Enter vlogix.sh:

vlogix.sh

Starting the Volume Logix Administrator 67


3. Type your password and press Enter. The Volume Logix Administrator is displayed on your workstation.


4

4.2 Stopping the Volume Logix Administrator

Use the following procedures on both Windows NT and UNIX systems. The sequence varies depending on whether there are:

• Pending tasks in the task list

• Inactive Symmetrix configurations

• Completed tasks that have not been saved to the log file

Stopping with no pending tasks, no inactive configurations, no unlogged tasks

1. Select File-Exit.

2. Click Yes to end the Volume Logix Administrator session.

Stopping the Volume Logix Administrator 69

Stopping with pending tasks

If you have pending tasks when you exit, Volume Logix discards these tasks. If you want to commit these tasks, select File-Run Tasks to run the task list before exiting Volume Logix.


2. Click OK.

3. Click on Yes to end the Volume Logix Administrator session without running the tasks. Click on No and then select File-Run Tasks if you want to run the task list before exiting.


4

Stopping with inactive Symmetrix configurations

If you attempt to exit Volume Logix after having run the task list but without having activated the configuration for the Symmetrixes affected by those tasks, you are prompted to activate the configuration for each affected Symmetrix before exiting.


2. Click Yes to queue the activation task to the task list.

3. Click Confirm on the Task List dialog.

4. Select File-Run Tasks to make the configuration active.

5. Reselect File-Exit to exit Volume Logix.


Stopping the Volume Logix Administrator 71

Stopping with tasks that have not been saved to the log file

If you attempt to exit Volume Logix while there are completed tasks that have not been saved to the log file, Volume Logix prompts you to log those events.

1. Select File, Exit.

2. Click Yes to write the events to the log file before exiting. Click No to exit without logging the events.



4

4.3 Changing the Password

Passwords are case-sensitive. While Volume Logix accepts null (blank) passwords, EMC recommends that you use an alphanumeric password unless the control stations is physically secure.

From either Windows NT or UNIX:

1. Select the Change Password option from the Edit menu.

2. Enter the current password in the Old Password text box.

3. Enter the new password in the New Password text box.

4. Enter the new password a second time in the Retype to confirm text box and then press Enter.

The new password takes effect immediately.

Changing the Password 73

4.4 Configuring Access ControlThis section gives an overview of configuring access control using the Volume Logix Administrator. The process involves these steps:

1. First time only: Initialize the Volume Logix database.

2. Select the host(s)/HBA(s). Select the volumes to be assigned. Add access to those volumes.

3. Activate the configuration.

Tasks are not run immediately but instead are stored on a task list. After performing each step, you must update the Volume Logix database by running outstanding tasks. Full details of each of these procedures are given in Chapter 5.

Initialize the Volume Logix Database

▼ First time only!

After installation and before you have configured any access control, the Volume Logix database exists but has no records.

1. In the ESN Topology pane, select the Symmetrix. Then from the Actions menu, select Symmetrix, then Initialize.

2. Run the task.

▼ Initializing the database formats the Volume Logix database and destroys any existing Volume Logix access control records.


4

Select and Add Volumes

Study the connections between hosts and Symmetrixes in the ESN Topology pane.

Notice that when you select two objects, the line connecting them changes from gray to black. Notice also that when you select an object (a host, an HBA, an FA, a Symmetrix) in the ESN Topology pane, the Volumes pane changes to show only the volumes available to the selected object. Since you have not yet defined any access control, all volumes in the Volumes pane are shown as available (the icon is gray).

1. In the ESN Topology pane, select the objects to which the volumes will be assigned. You may select a single HBA, multiple HBAs on a host, or multiple hosts.

2. In the Volumes pane, select the volume(s) that you wish to assign.

3. From the Actions menu, select Volume, then Add Access. Confirm your action.

In the Volumes pane, the assigned volume icon is now shown as owned by the selected host. (The icon changes from gray to black and is enclosed in a blue border.)

4. Run the tasks.

Activate the Configuration

Your updates to the Volume Logix database do not take effect until you cause the Symmetrix to refresh the FA ports with the new contents of the Volume Logix database.

1. In the ESN Topology pane, select a Symmetrix. From the Actions menu, select Symmetrix, then Activate Configuration. This action is queued to the task list.

Configuring Access Control 75

2. Backup the Volume Logix database to a file.

The location and filename of the backup file must be unique. Volume Logix will not overwrite an existing file.

In the ESN Topology pane, select a Symmetrix. From the Actions menu, select Symmetrix, then Backup. Enter a file name and click Save. This action is queued to the task list.

3. Run the tasks.

4. Finally, reboot the host(s) to which volumes have been assigned to cause them to rescan for volumes. Then rerun the fconfig and vcmfind commands on the affected hosts.


4

4.5 Simple Case StudyVolume Logix provides a demo application that you can use to learn how Volume Logix works. The demo application is shown in Figure 10 below.

Figure 10. Volume Logix demo application

The simple case study in this section describes how to use Volume Logix to grant Host dali access privileges to volumes 1 and 2 on Symmetrix 0000003221.

Simple Case Study 77

The steps you must complete are:

• Starting the Volume Logix demo

• Initializing the Volume Logix database

• Selecting and adding access to volumes

• Activating the configuration for a Symmetrix

• Backing up the Volume Logix database

Start Volume Logix Demo

To run the demo, start the Volume Logix Administrator with the -demo flag:

vlogix -demo

Initialize the Volume Logix Database

You need to initialize the Volume Logix database when you first start to define access control for your ESN.

Initializing the database after it has been created will clear all records. You only need to do this step once, unless you want to clear all volume assignments and start over.

1. Select Symmetrix 0000003221 by clicking on its name or its icon in the ESN Topology view.

2. Select the Actions—Symmetrix—Initialize option.

3. Volume Logix prompts you for a password. Type your password and press Enter.


4

4. The Initialize Database dialog box asks for confirmation. Click on the Yes button.

5. Volume Logix prompts you to save the current database (even though it is empty). Enter the location and filename in which to back up the database. Click the Save button. The default backup directory is /usr/symmapps/vcm/backup (UNIX systems) or C:\Program Files\Symmapps\vcm\Backup (Windows NT systems).

The location and filename of the backup file must be unique. Volume Logix will not overwrite an existing file.

6. Press Confirm to add the initialization to the task list.

7. Run the File—Run Tasks command to complete the initialization.

After the database has been initialized, the Volume Logix Administrator display is updated to show that no access privileges are currently granted; all volumes are shown as available.


Select and Add Volumes

Now you are ready to make volume assignments.

1. Select Symmetrix 0000003221 by clicking on it in the ESN Topology view. The Symmetrix becomes highlighted. The Volumes view shows the volumes residing on this Symmetrix. Expand Symmetrix 0000003221; click the expansion sign, for example plus (+) on Windows NT systems) to show its FA ports.

Note the different icon used for logical volume 0, the Volume Logix database.


4

2. Select FA port Fa16b. The port becomes highlighted and the grey lines from the Symmetrix to the selected port become black. Black lines are drawn from the FA port to each HBA to which it is connected (not yet shown in the display).

3. Select Host dali. The host becomes highlighted and the line from the FA port Fa16b to Host dali is now entirely black.


4. Expand Host dali; click the expansion sign, for example plus (+) on Windows NT systems) to show its HBAs. Select HBA 1f,0,fcaw@1,0.

5. In the Volumes view, select Volumes 1 and 2. Then select Actions—Volume—Add Access.


4

6. A confirmation box lists the host/HBA pairs that will be assigned access privileges. Select the Confirm button.


The workspace is refreshed to show the assignment. Volumes 1 and 2 are shown enclosed in a blue border.

7. You must now execute the Run Task command to commit these assignments to the Volume Logix database. Select the Run Tasks option from the File menu.

8. Volume Logix asks for your password. Type your password and press OK.

9. Volume Logix displays the Run Tasks dialog box. Click on the Yes button to run all pending tasks.


4

10. The volume assignments are written to the database.


Configuration changes are not visible to hosts/HBAs in the ESN until you activate the configuration, which causes the Symmetrix to refresh its WWN-memory related tables with the contents of the Volume Logix database.

1. On the ESN Topology pane, select Symmetrix 0000003221.

2. Select Actions—Symmetrix—Activate Configuration.


3. Volume Logix prompts you to activate the configuration. Select Yes.

4. Select Confirm to add the activation to the task list.

5. Select File—Run Tasks to complete the activation. Re-enter your password. Then select Run.


4

Back up Volume Logix database

You should back up the Volume Logix database whenever you change the ESN configuration.

1. Select Symmetrix 0000003221 in the ESN Topology view.

2. Select Actions—Symmetrix—Backup.

3. Enter the location and filename in which to back up the database. Click the Save button.


4. Select Confirm to add the backup to the task list.

5. Select File—Run Tasks to complete the backup. Re-enter your password. Then select Run.

6. Finally, reboot those hosts to which a volume has been assigned.

7. Run the fconfig command to create the .fconfig file that contains the mapping between the raw device names and the Symmetrix volume numbers.

What next? A similar case study is given in Chapter 6 to show which CLI commands you would enter to configure access control. That chapter also has an advanced case study which you may find helpful in understanding when to perform particular tasks in a real life scenario. See Simple Case Study on page 163 and Complex Case Study on page 170.


5

Chapter 5 MANAGING VOLUME LOGIX OBJECTS

This chapter describes the procedures for managing Volume Logix objects.

• Tasks Overview ..................................................... 90• Task List.................................................................. 93• Activating the Configuration ............................ 109• Symmetrix.............................................................111• FA Port.................................................................. 117• Volume.................................................................. 119• Hosts ..................................................................... 133• HBA ...................................................................... 137• Reporting ............................................................. 150

89

5.1 Tasks OverviewActions on the objects within a Volume Logix system. Actions are divided in two categories:

• view actions• configuration actions

A view action is a query about how the Volume Logix system is currently configured. For example, determining which hosts are permitted to access volumes on a specific FA port. A view action reports information; it does not change a Volume Logix system in any way.

A configuration action changes some aspect of the ESN, for example, deleting a host's access privileges on a volume. Configuration actions are immediately reflected on the ESN Topology view but are not committed to the Volume Logix database until you execute the Run Tasks command.

Volume Objects and the procedures for changing them are summarized in Table 7.

Table 7. Tasks Summary

Object TaskSee

pageCLI fpath equivalent

Display Reloading the display 92 —

Refreshing the display 93 —

Task List Managing the task list 93 —

Activating the configuration 109 refresh

Logging Saving tasks to the log file 107 —

Changing the log file 107 —

90 MANAGING VOLUME LOGIX OBJECTS

5

Symmetrix Viewing Symmetrix properties 111 lssymmdev

Initializing the Volume Logix database 112 initdb

Backing up the Volume Logix database backupdb

Restoring the Volume Logix database 116 restoredb

FA port Viewing FA ports on a Symmetrix lssymmfas

Viewing FA port properties 117 lsstatus

Volume Viewing volume properties 120 lshostdev

Viewing volumes 122 lssymmdev

Assigning volumes to HBAs 126 adddev

Assigning volumes to hosts 128 adddev

Releasing volumes from HBAs 130 rmdev

Releasing volumes from hosts 131 rmdev

Host Viewing host properties 133 lshosts

Viewing hosts 134 —

Renaming a host 135 chgname

HBA Viewing HBA properties 137 lshbawwn

Viewing HBAs 138 lshosts

Renaming an HBA 141 chgname

Clearing an HBA's access rights on all Symmetrix systems

143 clrwwn

Swapping access rights from one HBA to another 145 swaphba

Moving an HBA 147 —

Reporting Viewing a Symmetrix report 153 —

Viewing an FA port report 153 —

Viewing a volume report 154 —

Viewing a host report 154 —

An HBA report 155 —

Table 7. Tasks Summary

Object TaskSee

pageCLI fpath equivalent

Tasks Overview 91

5.2 Reloading the DisplayReloading the display resets the Volume Logix Administrator ESN Topology and Volumes views to reflect the configuration stored in Volume Logix databases for all Symmetrix systems. Reload the display whenever changes have been made to the ESN beyond the scope of the Volume Logix Administrator. If a new host has been added to the ESN, for example, the Volume Logix Administrator will not recognize the host until you reload the display.

To reload the display:

1. Select View-Reload Display.

2. Click Yes.

Volume Logix synchronizes its display with the configurations in the Volume Logix databases on all Symmetrix systems.


5

5.3 Refreshing the DisplayRefreshing the display redraws the workspace without reloading data from the Volume Logix database. To refresh the display, select View-Refresh Display.

5.4 Task ListEach time that you execute a command (for example, grant access privileges on a volume or rename a host, for example), that task is queued to a staging area known as the task list. Volume Logix does not complete the task (commit it to the Volume Logix database) until you run the task list.

Volume Logix queues tasks to a task list, rather than running them immediately, so that you can run them as a batch. Running tasks in batches is more efficient than running them separately.

The Task List dialog has two tabs, Tasks and Log.

The Tasks tab, shown in Figure 11 below, identifies each pending operation, indicates its status (Cancelled, Running, Failed, or Completed), and the relevant Symmetrix.

Refreshing the Display 93

Figure 11. Tasks tab

The Log tab, shown in Figure 12 below, identifies each completed operation, indicates when it completed, its result, and the relevant Symmetrix. You can use the Save Log command to write the contents of the Log tab to a log file.


5
Figure 12. Log tab
From the Task List dialog, you can:

• Run all pending tasks

• Run a subset of pending tasks

• Omit (delete) a task from the task list

• Restore an omitted (deleted) task to the task list

Running the task list can take several minutes to complete.

EMC recommends that you back up the database every time you run the task list.

Task List 95

To run all tasks You can use either the Edit-Tasks command or the File-Run Tasks command to run all pending tasks.

The configuration changes you make by running the task list are not visible to the hosts and HBAs within the ESN until you run a task list that contains the Activate Configuration task for the effected Symmetrix or reboot the hosts.

Using Edit-Task torun all tasks

1. Select Edit-Tasks.

2. Click Run.


5

3. Type your password and press Enter.

4. Click All.

As the task list runs, the status bar indicates the current task and the task counter indicates how tasks are remaining to be run.

5. Click Close.

6. Select Actions-Symmetrix-Backup to back up the Volume Logix database.

Task List 97

Using File-RunTasks to run all

tasks

1. Select File-Run Tasks.

2. Click Yes.


As the task list runs, the status bar indicates the current task and the task counter indicates how many tasks are remaining to be run.



5

To run selectedtasks

1. Select Edit-Tasks. The Volume Logix Task List appears.

2. Select the tasks to run. Use Shift-select to select contiguous tasks. Use Control-select to select non-contiguous tasks.

Task List 99

3. Click Run.


5. Click Selected.


5
6. Click Close.

The configuration changes you make by running the task list are not visible to the hosts and HBAs within the ESN until you run a task list that contains the Activate Configuration task for the effected Symmetrix and then reboot the hosts.

Task List 101

To omit tasks fromthe task list

1. Select Edit-Tasks. The Volume Logix Task List appears.

2. Select the tasks to omit. Use Shift-select to select contiguous tasks. Use Control-select to select non-contiguous tasks. The tasks are highlighted.

3. Click Omit. Volume Logix updates the task list, placing an X to the left of each deleted task and changing its status to Cancelled.


5
4. Click Close to end the task list.
To restore apreviously omitted

task

1. Select Edit-Tasks. The Volume Logix Task List appears. A red X to the left of a task indicated that it has been deleted.

Task List 103

2. Select the tasks that you want to restore to the task list. Use Shift-select to select contiguous tasks. Use Control-select to select non-contiguous tasks. The tasks are highlighted.


5
3. Click Restore. Volume Logix removes the red X
to the left of the task, indicating that it has been returned to the task list.

Task List 105

4. Click Close to end the task list.


5

5.5 Saving Tasks to the Log FileFigure 13 below shows an example of a log file.

Figure 13. Log file

Select File-Save Log to save the events added to the Log tab of the Task List since the Save Log command was last run in the current log file.

The first time that you run the Save Log command, Volume Logix prompts you to create the log file. Subsequent tasks are appended to this log (until you use the Save Log As command to change the log file).

If you want to change the log file where you store events do the following:

Saving Tasks to the Log File 107

1. Select File-Save Log As.

2. Specify the file in the File name edit box and click Save. The Save Log command now saves tasks in this file.


5

5.6 Activating the Configuration Configuration changes are not visible to hosts/HBAs in the ESN until you run the Actions—Symmetrix— Activate Configuration command, which causes the Symmetrix to refresh its WWN-memory related tables with the contents of the Volume Logix database.

If you attempt to exit Volume Logix after having run the task list but without having activated the configuration for the Symmetrix systems affected by those tasks, you are prompted to activate the configuration for each affected Symmetrix before exiting.

▼ Caution: All volume assignments are effective after you commit the Volume Logix database. If your changes to the configuration make a volume inaccessible to a host with currently active sessions with that volume, users will not be able to save data. Therefore, before activating the configuration, determine which hosts/HBAs are logged onto which FA ports. You can then warn users to complete their sessions before you remove their connection.

To activate theconfiguration for a

Symmetrix

1. Select a Symmetrix.

2. Select Actions—Symmetrix—Activate Configuration.

Activating the Configuration 109

3. Select Yes.

4. Click Confirm to add the activation to the task list.

5. Run the File—Run Tasks command to complete the activation.


5

5.7 SymmetrixThe Symmetrix is the central object in a Volume Logix system. Associated with the Symmetrix are a set of volumes, a set of FA ports, and one Volume Logix database.

Actions involving Symmetrix systems include:

• Viewing Symmetrix properties• Initializing the Volume Logix database• Backing up a Volume Logix database• Restoring a Volume Logix database

See also A Symmetrix Report on page 153.

To view Symmetrix properties

1. In the ESN Topology view, left-click a Symmetrix to select it. The Symmetrix name becomes highlighted.

2. Right-click the Symmetrix to display the popup menu.

3. Select Properties to display the Properties sheet.

Table 8. Properties of a Symmetrix

Property Description

Symmetrix Name

Descriptive name of this Symmetrix. Set by system.

Serial Number Serial number. Set by system.

Database Device

Device file name to the Volume Logix database. Storage Administrator can define alternate databases.

Volume Count Total number of volumes on this Symmetrix. Set by system.

Total capacity Total capacity in GigaBytes of all volumes on this Symmetrix. Set by system.

Symmetrix 111

4. After viewing the properties (none can be changed), click OK to cancel the Properties sheet.

To initialize the Volume Logix database

Initializing a Volume Logix database removes all information from it. Initialize a database once, when you first start to define access control for your ESN. Once you have initialized the database, initialize it again only if you want to clear all volume assignments and start over.

1. Select the Symmetrix whose database is to be initialized.

2. Select Actions—Symmetrix—Initialize. Volume Logix prompts you for a password.


4. The Initialize Database dialog box asks for confirmation:


5

5. Click Yes. Volume Logix prompts you to save a copy of the current database before it is initialized.

6. Enter the location and filename in which to back up the database. The location and filename of the backup file must be unique. Volume Logix will not overwrite an existing file. You can use this back up to restore the current configuration should you desire to do so later.

7. Click Save. The initialization is added to the task list.

8. Click Confirm.

9. Run the File—Run Tasks command to complete the initialization.

Symmetrix 113

To back up the Volume Logix database

EMC recommends that you back up the database every time you run the task list.

1. Select the Symmetrix whose database you want to back up.

2. Select Actions—Symmetrix—Backup. The following dialog box appears.

3. Enter the location and filename in which to back up the database. The location and filename of the backup file must be unique. Volume Logix will not overwrite an existing file.


5

4. Click Save. The backup is added to the task list.

5. Click Confirm.

6. Run the File—Run Tasks command to complete the backup.

Symmetrix 115

To restore the Volume Logix database

1. Select the Symmetrix whose database is to be restored.

2. Select Actions-Symmetrix-Restore. Volume Logix prompts for a password.

3. Type your password and press Enter. The following dialog box appears.

4. Enter the location and filename of the file you want to restore.

5. Click Open. Volume Logix adds the restore to the task list.

6. Click Confirm.

7. Run the File—Run Tasks command to complete the restore.


5

5.8 FA PortThe FA port is a Fibre Channel Director/Interface Adapter combination that connects the host/HBA to a Symmetrix in a Fibre Channel topology.

View actions involving FA ports are:

• Viewing FA ports on a Symmetrix• Viewing FA port properties

See also An FA Port Report on page 153.

To view FA ports on a Symmetrix

In the ESN Topology view, click the expansion symbol next to the Symmetrix whose FA ports you want to see. The Symmetrix expands, displaying each FA attached to it.

To view FA port properties

1. In the ESN Topology view, click the expansion symbol next to the Symmetrix on which the FA port resides.

2. The Symmetrix expands to show all its FA ports. Select a port. That port becomes highlighted.

3. Right-click the port to display a popup menu.


Table 9. Properties of an FA Port

Properties Description

Port Name Descriptive name of this port. Set by the system.

FA Port 117

5. After viewing the properties (none can be changed), click OK to end the Properties sheet.

Logged Into List of host/HBAs connected to this port. List changes as access rights on this port are granted and revoked.

Volume Count Number of Symmetrix volumes this port can access.

Total Capacity Total capacity in Gigabytes of the volumes that this port can access.

Table 9. Properties of an FA Port


5

5.9 VolumeIn the Volume Logix environment, a volume is a single logical device residing on the Symmetrix visible to the host.

Actions Actions involving volumes include:

• Viewing volume properties• Viewing volumes • Viewing shared volumes• Assigning volumes to HBAs• Assigning volumes to hosts• Releasing volumes from HBAs• Releasing volumes from hosts

See also A Volume Report on page 154.

Type Volume Logix supports four types of volumes:

Standard Fixed Block Addressing (FBA) volume

Business Continuity Volume (BCV), which functions as a mirror to a standard device

Meta volume, one of a concatenated group of adjacent Symmetrix devices that appear as one target volume

Meta BCV

Volume Logix database volume

Volume 119

State A volume in a Volume Logix system is in one of the following three states:

A blue border around the owned or shared volume icon indicates that it is owned by the host/HBA currently selected in the ESN Topology view.

The state shown is that after any pending tasks are committed.

Viewing volume properties

The Volume Logix Administrator provides several ways of viewing a volume’s properties:

Gray indicates available. No access rights have been granted on this volume.

Black with one path indicates owned, single-path. Exactly one host/HBA pair has been assigned access rights to this volume.

Black with two paths indicates shared, multi-pathed. Two or more host/HBA pairs have been assigned access rights to this volume.


5

• The volume icon itself, shown in both the Icon view and the Details view. The icon indicates a volume’s name, type, and state.

• The Details view, which shows an expanded list of properties.

• The volume's property sheet, which shows the volume's total capacity, and whether it is a BCV, meta, or Volume Logix database volume

To view a volume’sProperty sheet

1. Select objects in the ESN Topology to generate a list of volumes in the Volumes view. The further you can refine the list by making multiple selections, the quicker your search for volumes will be.

2. In the Volumes view, left-click the volume whose properties you want to view. You can select only one volume; multiple selections are not permitted.

3. Right-click the volume to display the popup menu.


Table 10. Properties of a Volume


Volume Name

Descriptive name of this volume. Set by system.

Ports List of Symmetrix/FA port pairs through which this volume can be accessed.

Owners List of host/HBA pairs assigned access rights on this volume. List changes as access rights on this volume are granted and revoked.

Total Capacity

Total capacity in GigaBytes of this volume.

Volume 121

After viewing the properties (none can be modified by the storage Administrator UNIX), click OK to end the Properties sheet.

Viewing volumes

You can view the volumes as simply as icons, or arranged in a table with additional information.

1. Select how you want to view the volumes. Select either Icons or Details from the View menu, or click the (Icons) or (Details) icon in the tool bar.

2. Then, in the ESN Topology view:

To view volumes on a specific Symmetrix:

• left-click the Symmetrix whose volumes you want to see.

To view volumes on multiple Symmetrix systems:

• Select the Symmetrix systems whose volumes you want to see. You can use Shift-select, Control-select, or drag the cursor while holding down the left mouse button.

To view volumes on a specific FA port:

• click the expansion symbol next to a Symmetrix on which the port you want to view resides. The Symmetrix expands,

BCV Volume

Indicates whether this is a BCV volume. Mutually exclusive with the VCM Volume and Meta Volume properties.

VCM Volume

Indicates whether this volume stores a Volume Logix database. Mutually exclusive with the BCV Volume and Meta Volume properties.

Meta Volume

Indicates whether this volume is part of a meta volume. Mutually exclusive to the BCV Volume and VCM Volume properties.

Table 10. Properties of a Volume (Continued)


5

showing all its ports. A grey line is drawn between each Symmetrix port and the hosts that can access volumes on the Symmetrix through that port.

• Left-click a specific FA port to select it. The port becomes highlighted and the grey lines from the Symmetrix to the selected port become black.

To view volumes on multiple FA ports:

This procedure displays the total set of volumes accessible collectively through a group of Symmetrix ports. Not every volume may be accessible through each port.

• Click The expansion symbol next to a Symmetrix on which the ports you want to view reside. The Symmetrix expands, showing all its ports. A grey line is drawn between each FA port and the hosts that can access volumes on the Symmetrix through that port.

• Select the FA ports. You can use Shift-select, Control-select, or drag the cursor while holding down the left mouse button. The selected ports become highlighted and the grey lines between those ports and Symmetrix become black.

3. The Volumes view shows the total set of volumes accessible through the selected ports.

Volume 123

Available to a host Four related, cumulative procedures follow. Each successive procedure builds on the previous procedure, further refining the selected volumes.

On all Symmetrix systems:

1. In the ESN Topology view, left-click the host to select it.

2. Black lines are drawn from that host to the Symmetrix systems to which it is connected.

3. The Volumes view displays the volumes available to that host.

On a specific Symmetrix:

1. In the ESN Topology view, select the Symmetrix.

2. In the Volumes view, the list contracts to only those volumes on the selected Symmetrix.

On multiple FA ports:

1. In the ESN Topology view, click the expansion symbol next to the Symmetrix.

2. The Symmetrix expands to show its ports.

3. Select the group of FA ports.

4. In the Volumes view, the list contracts to only those volumes accessible through the selected ports on the selected Symmetrix.

On a specific FA port:

1. In the ESN Topology view, select a single FA port.

2. In the Volumes view, the list contracts even further to only those volumes on the selected port on the selected Symmetrix.


5

Available to anHBA

Four related, cumulative procedures follow. Each successive procedure builds on the previous procedure, further refining the set of selected volumes.

On all Symmetrix systems:

1. In the ESN Topology view, click the expansion symbol next to the host that contains the HBA.

2. The host expands to show its HBAs, and a black line is drawn from the Symmetrix to each HBA connected to it.

3. Select the HBA. Black lines are drawn from that HBA to the Symmetrix systems to which it is connected.

4. The Volumes view displays the volumes available to that HBA.

On a specific Symmetrix:

1. In the ESN Topology view, select the Symmetrix.

2. In the Volumes view, the list contracts to only those volumes on the selected Symmetrix.

On multiple FA ports:

1. In the ESN Topology view, click the expansion symbol next to the Symmetrix.

2. The Symmetrix expands to show its ports. Select the group of FA ports.

3. In the Volumes view, the list further contracts to only those volumes accessible through the selected ports on the selected Symmetrix.

On a specific FA port:

1. In the ESN Topology view, select a single FA port.

2. The list contracts to only those volumes on selected port on the selected Symmetrix.

Volume 125

Assigning volumes to HBAs

Use the following procedures to grant access privileges to specific HBAs on a host:

1. In the ESN Topology view, click the expansion symbol next to the host to which the HBA is attached. The host expands to show its HBAs. The Volumes view displays that volumes available to that host.

2. Select the HBA(s) to which you want to assign the volumes.

3. In the Volumes view, select the volume to assign.

To select multiple volumes, you can Shift-click, Control-click, or drag the mouse pointer while holding down the left button.


5

4. Select Actions—Volume—Add Access or right-click the volumes and select Add Access. A confirmation box lists the host/HBA pair(s) that will be assigned access privileges.

5. Select Confirm.

6. Volume Logix assigns the shared volumes to the selected HBAs. The workspace is to show the assignments. The assignments are queued to the task list. You must execute the File-Run Task command to commit the assignment to the Volume Logix database.

Volume 127

Assigning volumes to hosts

When you assign one or more volumes to a host, Volume Logix assigns the volumes to each HBA attached that host. Use the following procedures to grant access privileges.

To restrict the assignment to specific HBAs, follow the procedure described in Assigning volumes to HBAs on page 126.

1. Select a host from the ESN Topology view.

To select multiple hosts, you can shift-click, control-click, or make a marque selection. A table of Symmetrix devices available to those hosts appears in the Volumes view.

2. In the Volumes view, select a volume to assign.

To assign multiple volumes, you can Shift-click, Control-click, or drag the mouse pointer while holding down the left button.


5

3. Select Actions—Volume—Add Access or right-click the volume and select Add Access. A confirmation box lists the host/HBA pairs that will be assigned access privileges.

4. Select Confirm.

5. Volume Logix assigns the shared volume to each HBA on the selected host. The workspace is refreshed to show the assignment. The assignment is queued to the task list. You must execute the File-Run Task command to commit the assignment to the Volume Logix database.

Volume 129

Releasing volumes from HBAs

Releasing volumes from HBAs revokes the HBAs’ access privileges on the volumes.

1. Select one or more hosts in the ESN Topology view. Expand the host(s) to show their HBAs.

2. Select the HBAs whose access privileges you want to revoke.

3. In the Volumes view, select one or more volumes to release. Valid volumes are enclosed in a blue box.

4. Select Actions—Volume—Remove Access. A confirmation box lists the volumes to which access privileges for the selected host/HBA pair(s) will be removed.

.

5. Select Confirm.


5

Volume Logix releases the volume(s) from the selected HBA(s). The workspace is refreshed to show that the volume is now released. The task list reflects the new status of the volume. You must execute the File-Run Task command to update the Volume Logix database with the volume’s new status.

Releasing volumes from hosts

Releasing volumes from hosts revokes the hosts' access privileges on the volumes.

1. Select one or more hosts in the ESN Topology view.

2. In the Volumes view, select one or more volumes to release.

3. Select Actions—Volume—Remove Access. A confirmation box lists the volumes to which access privileges for the selected host(s) will be removed.

Volume 131

4. Select Confirm.

5. Volume Logix releases the volume(s) from the selected host(s). The workspace is refreshed to show that the volume is now released. The task list reflects the new status of the volume. You must execute the File-Run Task command to update the Volume Logix database with the volume’s new status.


5

5.10 HostsThe host initiates requests on volumes. Associated with the host is a set of HBAs. Using the Volume Logix Administrator, you can view which Symmetrix/FA port pairs a host can log into.

Actions Actions involving hosts include:

• Viewing host properties• Viewing hosts • Renaming a host.

Refer to Assigning volumes to hosts on page 128 and Releasing volumes from hosts on page 131 for information on adding and removing volumes. See also A Host Report on page 154.

Viewing host properties

1. In the ESN Topology view, left-click a host to select it. The host is highlighted.

2. Right-click the host to display the popup menu.

3. Select Properties to display the Properties sheet

4. After viewing the properties, click OK to end the Properties sheet.

Table 11. Properties of a Host


Host Name Descriptive name of this host. Set by system. You can rename the host.

Total Capacity

Total capacity in GigaBytes of the volumes assigned to this host.

Hosts 133

Viewing hosts You can view hosts that can access a specific Symmetrix, multiple Symmetrix systems, or FA ports.

In the first two procedures, the host and Symmetrix icons must be collapsed. If not, the path connections terminate at the HBA for the host) and at the FA (for the Symmetrix).

Access a specificSymmetrix

1. In the ESN Topology view, left-click a Symmetrix to select it. A black line is drawn from the Symmetrix to each host that can access volumes on that Symmetrix.

2. The Volumes view shows the volumes on that Symmetrix accessible by the hosts.

Access multipleSymmetrix

systems

1. In the ESN Topology view, select the Symmetrix systems. You can use Shift-select, Control-select, or drag the cursor while holding down the left mouse button. A black line is drawn from each Symmetrix to each host that can access volumes on that Symmetrix.

2. The Volumes view shows the volumes on the Symmetrix systems, grouped by Symmetrix.

Access FA Ports 1. In the ESN Topology view, click the expansion symbol next to a Symmetrix on which the port resides. The Symmetrix expands, showing all its ports. A grey line is drawn between each FA port and the hosts that can access volumes on the Symmetrix through that port.

2. Left-click a specific FA port to select it. The grey lines from the Symmetrix to that port and from that port to the hosts that can access that port become black.


5

Renaming a host

1. In the ESN Topology view, left-click a host to select it. The host is highlighted

2. Right-click the host to display the popup menu.


4. Type a new name for the host in the Host Name edit box.

Hosts 135

5. Click OK.

6. Click Confirm to add the name change to the task list.

7. Execute File-Run Tasks.

The new name is displayed in the ESN Topology view, as well on the properties sheets for the host, HBA, and FA port.


5

5.11 HBAA host bus adapter connects a host to a Fibre Channel loop and switched fabric. Using the Volume Logix Administrator, you can specify which Symmetrix/FA port pairs an HBA can log into.

Actions involving HBAs include:

• Viewing HBA properties• Viewing HBAs • Renaming an HBA• Clearing an HBA's access rights• Swapping access rights• Moving an HBA to a new host

Refer to Assigning volumes to HBAs on page 126 and Releasing volumes from HBAs on page 130 for information on adding and removing volumes. See also An HBA report on page 155.

To view HBA properties

1. In the ESN Topology view, click the expansion symbol next to the host to which the HBA is attached. The host expands to show all HBAs attached to it.

2. Left-click an HBA to select it. Right-click the HBA to display the popup menu.


Table 12. Properties of an HBA


Bus Name Descriptive name of this bus. Set by system. You can rename the HBA.

Port WWN The World Wide Name associated with this port.

Node WWN The World Wide Name associated with this node

HBA 137

4. After viewing the properties, click OK to end the Properties sheet.

Viewing HBAs You can view HBAs that can access volumes on a specific Symmetrix, or view HBAs that can access volumes on multiple Symmetrix systems.

To access aSymmetrix

1. In the ESN Topology view, left-click a Symmetrix to select it. A black line is drawn from the Symmetrix to each host that can access volumes on that Symmetrix.

2. Click the expansion symbol next to each host that has a black line drawn to it to expand that host and display its HBAs. A black line connects each HBA that can access the Symmetrix to the Symmetrix.

3. The Volumes view shows the volumes on the Symmetrix systems Symmetrix systems.

Host Name The host to which this HBA connects.

Ports List of Symmetrix/FA port pairs this bus can access.

Total Capacity

Total capacity in GigaBytes of all volumes assigned to this HBA.

Volume Count

Total number of volumes owned by or assigned to this HBA

Table 12. Properties of an HBA


5

To access multipleSymmetrix

systems

1. In the ESN Topology view, select the Symmetrix systems with the Shift-select, or Control-select keys. A black line is drawn from each Symmetrix to each host that can access volumes on that Symmetrix.

2. Click the expansion symbol next to each host that has a black line drawn to it to expand that host and display its HBAs. A black line connects each HBA that can access the Symmetrix to the Symmetrix.

3. The Volumes view shows the volumes on the Symmetrix systems.

HBA 139

Access FA ports 1. In the ESN Topology view, click the expansion symbol next to a Symmetrix on which the port resides. The Symmetrix expands, showing all its ports. A grey line is drawn between each FA port and the hosts that can access volumes on the Symmetrix through that port.

2. Left-click a specific FA port to select it. The port becomes highlighted and the grey lines from the Symmetrix to that port become black.

3. Click the expansion symbol next to the host that contains the HBA. The host expand to show its HBAs, and a black line is drawn from the port to each HBA connected to it. The Volumes view contracts to show the volumes the HBAs can access through the selected FA port.


5

Renaming an HBA

1. In the ESN Topology view, click the expansion symbol chickenpox to the host to which the adapter is connected.

2. Left-click an HBA to select it. The HBA is highlighted.

3. Right-click the HBA to display the popup menu.


5. Type a new name for the HBA in the Bus edit box.

HBA 141

6. Click OK.

7. Click Confirm to add the name change to the task list.


The new name is displayed in the ESN Topology view, as well on the properties sheets for the host and FA port.


5

Clearing an HBA’s access rights

Clearing an HBA’s access rights revokes all access privileges granted to that HBA across selected or all Symmetrix systems.

You cannot clear the access rights on multiple HBAs simultaneously.

1. Click the expansion symbol to expand the host on which the HBA resides.

2. Select the HBA.

3. If you want to clear access on one or more specific Symmetrix systems, use Control-Select to select those Symmetrix systems. If you want to clear access on all Symmetrix systems, go to the next step.

4. Select Actions—Bus—Clear All Access. A dialog box asks you if you want to clear the access rights for the selected HBA from the Symmetrix systems you indicated.

5. Click Yes. Volume Logix asks for your password.


HBA 143

7. Click Confirm to add the task to the task list.


Volume Logix revokes any previously granted access privileges for that HBA on the indicated Symmetrix systems.


5

Swapping access rights

Should an HBA malfunction, you can swap (move) the access privileges granted to that HBA to another HBA. This allows you to substitute a new HBA for the old HBA while retaining the previously granted access privileges.

The new HBA must not have an entry in the Volume Logix database.

Before using the Volume Logix Administrator to swap access privileges, install the new adapter on the host, connect it to the Fibre, and reboot.

1. Select Actions—Bus—Swap Access.

2. In the Symmetrix column, select the Symmetrix to which the HBA is attached:

HBA 145

3. In the Source Candidate HBAs column, select the HBA whose access privileges are being moved:


5

4. In the Destination Candidate HBAs column, select the HBA that will be assigned the access privileges:

5. Click OK.

6. Click Confirm to add the swap to the task list.

7. Volume Logix refreshes to show the reassignment and queues it to the task list. You must execute the File-Run Task command to complete the reassignment.

Moving an HBA to a different host

1. In the ESN Topology view, click the expansion sign next to the host to which the HBA is connected.

2. Left-click the HBA you want to move to a different host.

HBA 147

3. Select File-Properties, or right-click the HBA and select Properties from the popup menu.

4. Indicate the new host by entering its name in the Host edit box or by selecting it from the drop-down list.


5

5. Click OK.

6. Click Confirm.

The ESN Topology view shows the HBA attached to the new host. The move is queued to the task list. You must execute the File-Run Task command to commit the move to the Volume Logix database.

HBA 149

5.12 ReportingFor each type of Volume Logix object, you can view reports online or save to a file.

Table 13. Volume Logix Reports

Report Shows...

Symmetrix For each Symmetrix, you can view a report that shows:• the host/HBAs pairs connected to it• its volumes (and their capacities)• its Fibre Channel ports• its Status• its Type

FA port For each FA port, you can view a report that shows:• the host/HBAs pairs connected to it• the volumes accessible through it (and their capacities)• HBA WWN• Status• Type

Volume For each volume, you can view a report that shows:• its capacity• serial number• its type (standard, Volume Logix database, BCV, or meta volume)• the Symmetrix/FA port pair it resides on• the host/HBAs pairs that own it

Host For each host, you can view a report that shows:• its HBAs• the Symmetrix systems connected to these HBAs• the volumes (and capacity and status) owned by the host• the FA ports through which the volumes are being accessed• the total capacity of volumes owned by the host• the number of free volumes (and their total capacity) that the host

can access

HBA For each HBA, you can view a report that shows the:• Symmetrix systems and FA ports connected to it• assigned volumes (and their capacities)• total capacity owned• total capacity free


5

To view aSymmetrix report

online

1. Select the object in the ESN Topology view

2. Right-click the object to display the popup menu.

3. Select Report.

4. Press Preview to view the report.

5. Press OK to return to the Report Dialog box. Press Cancel to end the report.

To select... Do this...

Symmetrix Click a Symmetrix. The Symmetrix is highlighted.

FA port Click the expansion symbol next to the Symmetrix on which the port resides. The Symmetrix expands to show all its ports.Select a port. That port becomes highlighted.

Volume Select objects to generate a list of volumes in the Volumes view. The further you can refine the list by making multiple selections, the quicker your search for volumes will be.In the Volumes view, left-click a volume to report on. You can select only one volume; multiple selections are not permitted.

Host Click a host. The host is highlighted.

HBA Click the expansion symbol next to the host to which the HBA is attached. The host expands to show all HBAs attached to it.Select an HBA. That HBA becomes highlighted.

Reporting 151

To save a report toa file

1. On the Report Dialog, select "To file".

2. Press OK to generate the report.

3. Select a folder to store the report, name it (or accept the default name) and press Save.


5

Report Output This section shows sample output for each report.

Figure 14. A Symmetrix Report

Figure 15. An FA Port Report

Reporting 153

Figure 16. A Volume Report

Figure 17. A Host Report


5

Figure 18. An HBA report

Reporting 155


6

Chapter 6 USING THE VOLUME LOGIX CLI

This chapter describes how to specify access control using the command line interface.

• The Volume Logix CLI ....................................... 158• Configuring Access Control .............................. 160• Simple Case Study .............................................. 163• Complex Case Study .......................................... 170• Maintain the Volume Logix Database.............. 178

157

6.1 The Volume Logix CLIYou use the Volume Logix CLI through:

• The fpath command line interface which you run on the host designated as a control station. Using fpath commands, you can define and query which volumes each host HBA port is permitted to access.

• The vcmfind utility that you run on each host, to discover WWN identity information and to map an AWWN to each WWN.

You must be logged on as administrator (Windows NT) or root (UNIX) to run fpath and vcmfind commands.

When an HBA port sends an I/O request to a Symmetrix volume, Volume Logix processes this request and either grants or denies access based on information in the Volume Logix database.

The format of the fpath command is:

fpath action { arguments }

where actions are subcommands to fpath. The actions fall into two broad categories: actions that update the Volume Logix database, and actions that display configuration information from the Symmetrix or a host, typically by querying the Volume Logix database.

The format of the vcmfind command is simply:

vcmfind

Volume Logix commands are summarized in Table 14. For the definition of each fpath action, see Chapter 7. For vcmfind, see Chapter 8.

158 USING THE VOLUME LOGIX CLI

6

Table 14. Volume Logix Command Summary

Command Action Description

fpath initdb Creates and initializes a Volume Logix database. This action removes all information from the Volume Logix database. On completion, the database device is write-protected for the operating system.

adddev In the Volume Logix database, adds a device to the list of devices that a WWN can access.

rmdev In the Volume Logix database, removes a device from the list of devices that a WWN can access.

backupdb Backs up a Volume Logix database to the specified file.

restoredb Restores a Volume Logix database from the specified file.

clrwwn Deletes all access rights for a WWN in the Volume Logix database (specified either by WWN or AWWN).

swaphba Allows the swapping out of one HBA with another.

chgname Changes the AWWN for the specified WWN in the Volume Logix database and the Login History table.

refresh Causes Symmetrix to refresh its WWN-related memory tables with the contents in the Volume Logix database.

lshostdev Lists the Symmetrix devices that are accessed through Fibre Channel and shows their controlling FA, TID and LUN, Symmetrix device number, and Symmetrix serial number. Also shows which device holds the Volume Logix database.

lsstatus Lists whether the Symmetrix FA has Volume Logix turned on.

lssymmdev Lists all FAs in a Symmetrix and which devices they can access.

lsdb Lists, for each Symmetrix FA, which devices in a Symmetrix a WWN can access (Volume Logix database contents).

lsbackup Lists, in lsdb form, the contents of a backup file.

lshosts Lists, for each FA, which hosts and HBAs are logged onto a Symmetrix (Login History table contents).

lshbawwn Lists the WWNs of the Fibre HBAs on this host.

lssymmfas Lists all FAs in a Symmetrix.

vcmfind Runs on each host. Displays WWN identity information for the host and assigns an alias to the WWN, if one does not yet exist.

The Volume Logix CLI 159

6.2 Configuring Access ControlThis section describes how to configure access control. The process involves three stages:

1. Identify elements of your configuration.

2. Update the Volume Logix database.

3. Activate the configuration.

You should be logged on to the control station as administrator (Windows NT) or root (UNIX), in an MS-DOS command prompt window (Windows NT) or an xterm window (UNIX).

Refer to Simple Case Study on page 163 and Complex Case Study on page 170 for examples of command input.

Identify your Configuration

First, you need to determine the identifiers by which each element is known. See Figure 19

Table 15. Steps in Identifying your Configuration

To identify... Use:

Symmetrix logical device name of the VCMDB.

fpath lshostdev

For each HBA on this host, its WWN.

fpath lshbawwnvcmfind

For each HBA on this host, the Symmetrix FA port to which it connects.

fpath lshosts

For each FA port, the available Symmetrix devices.

fpath lssymmdev


6

Figure 19. Determining Identifiers

Update the Volume Logix Database

Now that you have identified each element, you initialize the Volume Logix database and create records:

SYMMETRIXHOST

WWN2

FA 1

FA 2

FC Hub/Switch

WWN1FibreHBA 1

FibreHBA 2

DB Backup

VCM DB

Isdb

Ishostdev

Login Table

IshostsIssymmdevIshbawwn

VCM

Table 16. Steps in Updating the Database

To do this... Use

Initial creation only: Initialize the Volume Logix database device .

fpath initdb

Designate, for a specified WWN, which devices are allocated to which HBA on this host. Use the names/identifiers displayed in the previous section: VCMDB: lshostdev.WWN: lshbawwn or vcmfind.FA: lshosts.Devices: lssymmdev.Repeat for each WWN in the Fibre Channel configuration.

fpath adddev

Configuring Access Control 161


Your updates to the Volume Logix database do not take effect until you cause the Symmetrix to allow the HBA to see the changes (by performing a refresh or when the host HBA logs in again), and you cause the host to see the changes (by rescanning for volumes).

Configuration of the Volume Logix database is now complete. Use fpath lshostdev (control station) or the EMC inquiry utility, inq, (other hosts) to view current access controls on that host.

For information about inq, refer to the Symmetrix Open Systems Environment Product Guide for information on downloading the EMC inquiry utility, or use the SInquiry utility provided with the base component of Symmetrix Manager.

Table 17. Steps in Activating the Configuration

To do this... Use

Cause the Symmetrix to refresh its WWN-related memory tables with the contents of the VCM DB.

fpath refresh

Backup the VCMDB to a file. fpath backupdb

Reboot all hosts that have had devices added or removed for the changes to take effect.


6

6.3 Simple Case StudyThis section describes how to set up access control for the simple configuration illustrated in Figure 20.

Figure 20. Case Study: Simple Configuration (2)

In this scenario, two hosts, each with two HBAs, connected to two hubs. One hub potentially provides access through one Symmetrix FA to nine devices. The other hub potentially provides access through another Symmetrix FA to the same nine devices, thereby providing continued availability if a hub or its connections fail.

Both hosts are Sun systems. Host 1 has the Administrator utilities installed (fpath, vcmfind, fcompare, and fconfig); host 2 has the host utilities installed (vcmfind, fcompare, and fconfig).

FA1a

FA1b

HOST 1

Hub

AvailableDevice Ranges

000-008

SYMMETRIX

HBA 1

HBA 2

Hub

HOST 2

HBA 1

HBA 2


In this case study, each host will be given the same access controls:

• HBA1 will be granted access to Symmetrix logical volumes 003 and 005-008.

• HBA2 will be granted access to Symmetrix logical volume 004.


1. On Host 1, determine the Volume Logix database device name (VCMDB) using the fpath lshostdev command:

fpath lshostdev fpath, Copyright EMC Corp. 1998-1999Symmetrix Fibre Devices on this computer

Pathname TID LUN Device Symm serial FA /dev/rdsk/clt0d0s2 0 0 000 0182601088 1a VCMDB/dev/rdsk/c2t0d0s2 0 0 000 0182601088 1b VCMDB

In this example, the system displays two paths by which the VCMDB can be seen from this host, one for each FA. Either path may be used in fpath commands. The logical volume number of the VCMDB, in hexadecimal, is 000.

If we had chosen a Windows NT system as the control station running fpath, then the VCMDB would have had a Windows NT-style raw device name such as \\.\PHYSICALDRIVE3.

2. On Host 1, determine the WWN of the HBAs on this host using the fpath lshbawwn command:

fpath lshbawwn fpath, Copyright EMC Corp. 1998-19991f,0,[email protected] 300000e06900052b1f,0,fca@2,0 200000e0698002ad

Note the WWN of each HBA: 300000e06900052b and 200000e0698002ad.


6

3. On Host 2, determine the WWN of the HBAs on this host using the vcmfind command:

vcmfind vcmfind, Copyright EMC Corp. 1998-1999ADAPTER WWN DEVICE1f,0,[email protected] 50060482b891601f /dev/rdsk/c1t0d0s21f,0,fca@1,1 50060482b891600e /dev/rdsk/c1t1d0s2

4. On Host 1, determine which FA each HBA is connected to using the fpath lshosts command:

fpath lshosts -d /dev/rdsk/clt0d0s2 fpath, Copyright EMC Corp. 1998-1999Displaying login-history table for FA 1aEntry SID originator originator user gen user gen

node_wwn port_wwn node name port name0 1 100000e06900052b 300000e06900052b NULL0 1 50060482b891601f 50060482b891601f host2 1f,0,[email protected]

Displaying login-history table for FA 1bEntry SID originator originator user gen user gen

node_wwn port wwn node name port name0 1 100000e0698002ad 200000e0698002ad NULL NULL0 1 50060482b891600e 50060482b891600e host2 1f,0,fca@1,1

Note the FA for 300000e06900052b and 50060482b891601f is 1a and for 200000e0698002ad and 50060482b891600e is 1b.

5. On Host 1, identify which Symmetrix devices are potentially available through each FA using the fpath lssymmdev command.


The output from fpath lssymmdev shows the capacity and type of each device to assist you in device selection. Note that the Volume Logix database device is among those listed—in this case study, device 000, as recorded from Step 1.

fpath lssymmdev -d /dev/rdsk/clt0d0s2fpath, Copyright EMC Corp. 1998-1999Devices Available on FA 1aDEVICE NUMBER CAPACITY TYPE000 0.008 FBA001 4.510 FBA002 4.510 FBA003 4.510 FBA004 4.510 FBA005 4.510 FBA006 4.510 FBA007 4.510 FBA008 4.510 FBA

Devices Available on FA 1bDEVICE NUMBER CAPACITY TYPE000 0.008 FBA001 4.510 FBA002 4.510 FBA003 4.510 FBA004 4.510 FBA005 4.510 FBA006 4.510 FBA007 4.510 FBA008 4.510 FBA


Now that you have identified the names of each HBA, the FA to which it is connected, and the devices that may be assigned, you are ready to initialize the Volume Logix database and create records.


6

1. Initial creation only: Initialize the Volume Logix database device using the fpath initdb command.

▼ Running initdb once the database has been created will clear all records. You only need to do this step once, unless you want to clear all records.

fpath initdb -d /dev/rdsk/clt0d0s2# ./fpath initdb -d /dev/rdsk/c1t0s2Copyright EMC Corp. 1998-1999, @(#) fpath Revision: 2.0.13 $Enter full pathname of backup file:

2. Specify the filename.

After specifying the filename, the confirmation query appears:

Do you really want to do this answer y/n:

3. Type y to initialize the VCM database.

4. Designate, for the Host 1 HBA’s WWNs, which devices (in hexadecimal) are allocated to that HBA using the fpath adddev command. Use the identifier information noted in earlier steps.

fpath adddev -d /dev/rdsk/clt0d0s2 -w 300000e06900052b -f 1a -r "3 5-8"fpath adddev -d /dev/rdsk/clt0d0s2 -w 200000e0698002ad -f 1b -r "4"

5. Repeat the fpath adddev command for the other host HBA’s WWNs.

fpath adddev -d /dev/rdsk/clt0d0s2 -w 50060482b891601f -f 1a -r "3 5-8" fpath adddev -d /dev/rdsk/clt0d0s2 -w 50060482b891600e -f 1b -r "4"



Your updates to the Volume Logix database do not take effect until you cause the Symmetrix to allow the HBA to see the changes, and you cause the host to see the changes.

1. Cause the Symmetrix to refresh its WWN-related memory tables with the contents of the VCMDB using the fpath refresh command:

fpath refresh -d /dev/rdsk/clt0d0s2

2. Backup the VCMDB to a file using the fpath backupdb command so that, if needed, it can later be restored.

fpath backupdb -d /dev/rdsk/clt0d0s2 -o /tmp/backup

3. You must reboot the hosts for the changes to take effect.

Configuration of the Volume Logix database is now complete. Use fpath lshostdev (on control station) or the EMC inquiry utility, inq, (all hosts) to view current access controls for the host.

fpath lshostdev fpath, Copyright EMC Corp. 1998-1999

Symmetrix Fibre Devices on this computer Pathname TID LUN Device Symm serial FA /dev/rdsk/clt0d0s2 0 0 000 0182601088 1a VCMDB/dev/rdsk/c1t1d0s2 0 0 000 0182601088 1b VCMDB/dev/rdsk/c1t0d3s2 0 3 003 0182601088 1a /dev/rdsk/c1t0d5s2 0 5 005 0182601088 1a /dev/rdsk/c1t0d6s2 0 6 006 0182601088 1a /dev/rdsk/c1t0d7s2 0 7 007 0182601088 1a /dev/rdsk/c1t0d8s2 0 8 008 0182601088 1a /dev/rdsk/c2t0d4s2 0 4 004 0182601088 1b


6

inq DEVICE :VEND :PROD :REV :SER NUM :CAP (kb)/dev/rdsk/c1t0d0s2 :EMC :SYMMETRIX :5265 88000010 :7680/dev/rdsk/c1t1d0s2 :EMC :SYMMETRIX :5265 88000170 :7680/dev/rdsk/c1t0d3s2 :EMC :SYMMETRIX :5265 88003010 :4417920/dev/rdsk/c1t0d5s2 :EMC :SYMMETRIX :5265 88005010 :4417920/dev/rdsk/c1t0d6s2 :EMC :SYMMETRIX :5265 88006010 :4417920/dev/rdsk/c1t0d7s2 :EMC :SYMMETRIX :5265 88007010 :4417920/dev/rdsk/c1t0d8s2 :EMC :SYMMETRIX :5265 88008010 :4417920/dev/rdsk/c1t0d4s2 :EMC :SYMMETRIX :5265 88004170 :4417920


6.4 Complex Case StudyConsider a configuration with multiple hosts involving exclusive and shared access in both hub and switch environments.

Imagine that Host 4 in Figure 21 on page 171 has been designated the control station and has fpath installed. The other hosts have vcmfind installed. Device ranges are shown in hexadecimal.

• Host 1 and Host 2 are Windows NT systems each providing shared access to devices 000 to 01F. Host 1 and Host 2 both have two HBAs, each connected via a different hub to the Symmetrix in order to provide failover in the event of an HBA, Hub, or FA malfunctioning.

• Host 3 is a Windows NT system with exclusive access to devices 110 - 130.

• Host 4 is a Sun system (designated the control station) with exclusive access to devices 040-06F and shared access to devices 070-07F.

• Host 5 is a Sun system with shared access to devices 070-07F and exclusive access to devices 080-087.

• Host 6 is a Windows NT system with exclusive access to devices 088-098.

• Host 7 is a Windows NT system with exclusive access to devices 0b0-0cf and 110-124.


6
Figure 21. Case Study: Complex Configuration
FA1b

FA1a

FA1b

FA1a

Device Ranges

000 0FF 100 1FF

FA15a

FA15b

FA15a

FA15b

SYMMETRIX

HOST1

HOST2

HOST3

HOST6

HOST7

HOST4

HOST5

Hub

Hub

Switch

AvailableDevice Ranges

000-03F, 100-160

000-03F

000, 040-07F, 100-13F

000, 060-09F, 0B0-0FF

Complex Case Study 171


1. On the control station (Host 4): Determine the Volume Logix database device name (VCMDB) using the fpath lshostdev command:


Symmetrix Fibre Devices on this computer Pathname TID LUN Device Symm serial FA /dev/rdsk/clt0d0s2 0 0 000 0182601088 15a VCMDB/dev/rdsk/c1t1d0s2 0 0 000 0182601088 15b VCMDB

The system displays one device (the VCMDB) for the Symmetrix, accessed via two paths (via FA 15a and FA 15b) from host 4. Note the VCMDB path, /dev/rdsk/c1t0d0s2 or /dev/rdsk/c1t1d0s2, and logical volume number, 000.

2. Determine the WWN of each HBA on this host that is connected to the Symmetrix using the fpath lshbawwn command:

fpath lshbawwn fpath, Copyright EMC Corp. 1998-19991f,0,[email protected] 300000e06900052b

Host 4 has one HBA whose WWN is 300000e06900052b.


6

3. Determine the WWN of each HBA on each of the other six hosts by running the vcmfind command on each host, noting their WWNs. For example:

On HOST1

vcmfind vcmfind, Copyright EMC Corp. 1998-1999ADAPTER WWN DEVICEadapter0 200010e0698002ad \\.\physicaldrive3adapter1 200011e0698002ad \\.\physicaldrive4

On HOST 2

vcmfind vcmfind, Copyright EMC Corp. 1998-1999ADAPTER WWN DEVICEadapter0 200020e0698002ad \\.\physicaldrive3adapter1 200021e0698002ad \\.\physicaldrive4

Repeat on Hosts 3, 5, 6, and 7.

Host WWNs from lshbawwn and vcmfind

Host 1 200010e0698002ad200011e0698002ad

Host 2 200020e0698002ad200021e0698002ad

Host 3 200030e0698002ad

Host 4 300000e06900052b

Host 5 300050e0698002ad

Host 6 200060e0698002ad

Host 7 200070e0698002ad


4. Back on the control station (Host4), determine which FA each HBA is connected to using the fpath lshosts command. Each time you ran the vcmfind command, it added a record for that host to the Login History table.

fpath lshosts -d /dev/rdsk/clt0d0s2fpath, Copyright EMC Corp. 1998-1999Displaying login-history table for FA 1aEntry SID originator originator user gen user gen

node_wwn port_wwn node name port name0 1 200010e0698002ad 200010e0698002ad NT410a adapter00 1 200020e0698002ad 200020e0698002ad NT420a adapter00 1 200030e0698002ad 200030e0698002ad NT430a adapter0


node_wwn port_wwn node name port name0 1 200011e0698002ad 200011e0698002ad NT410a adapter10 1 200021e0698002ad 200021e0698002ad NT420a adapter1

Displaying login-history table for FA 15aEntry originator originator user gen user gen

node_wwn port_wwn node name port name0 1 300000e06980052b 300000e06900052b NULL NULL 0 1 300050e0698002ad 300050e0698002ad lss2105 1f,0,[email protected] 1 200060e0698002ad 200060e0698002ad NT460a adapter0 0 1 200070e0698002ad 200070e0698002ad NT470a adapter0

Displaying login-history table for FA 15bEntry originator originator user gen user gen

node_wwn port_wwn node name port name0 1 300000e06980052b 300000e06900052b NULL NULL0 1 300050e0698002ad 300050e0698002ad lss2105 1f,0,[email protected] 1 200060e0698002ad 200060e0698002ad NT460a adapter00 1 200070e0698002ad 200070e0698002ad NT470a adapter1

Note which FAs each WWN is logged onto.

Host Originator port_wwn AWWN FAs

Host 1 200010e0698002ad200011e0698002ad

NT410a/adapter0NT410a/adapter1

FA 1a,FA 1b

Host 2 200020e0698002ad200021e0698002ad

NT420a/adapter0NT420a/adapter1

FA 1aFA 1b

Host 3 200030e0698002ad NT430a/adapter0 FA 1a

Host 4 300000e06900052b NULL (vcmfind not run) FA 15a, FA 15b

Host 5 300050e0698002ad lss2105/1f,0,[email protected] FA 15a, FA 15b

Host 6 200060e0698002ad NT460a/adapter0 FA 15a, FA 15b

Host 7 200070e0698002ad NT470a/adapter0 FA 15a, FA 15b


6

5. Identify which Symmetrix devices are potentially available through each FA using the fpath lssymmdev command.

In the following output, ellipses (...) are used to show ranges of devices.

fpath lssymmdev -d /dev/rdsk/clt0d0s2 fpath, Copyright EMC Corp. 1998-1999

Devices Available on FA 1aDEVICE NUMBER CAPACITY TYPE

000 0.008 FBA001 4.510 FBA... ... ...03F 4.510 FBA100 4.510 FBA... ... ...160 4.510 FBA

Devices Available on FA 1bDEVICE NUMBER CAPACITY TYPE

000 0.008 FBA001 4.510 FBA... ... ...03F 4.510 FBA


000 0.008 FBA040 4.510 FBA... ... ...07F 4.510 FBA100 4.510 FBA... ... ...13F 4.510 FBA


000 0.008 FBA060 4.510 FBA... ... ... 09F 4.510 FBA0B0 4.510 FBA... ... ...0FF 4.510 FBA

Note that, as recorded in Step 1, the VCMDB device is device 000.



Now that you have identified the WWN of the HBA, the FA to which it is connected, and the devices that may be assigned, you are ready to initialize the Volume Logix database and create records.

Do the following steps on the control station (host 4):

1. Initialize the Volume Logix database device using the fpath initdb command.

▼ Initial creation only

fpath initdb -d /dev/rdsk/clt0d0s2 fpath, Copyright EMC Corp. 1998-1999Do you really want to do this answer y/n: ySuccessfully initialized VCM database

2. Specify the access control for each host using the fpath adddev command.

For Host 1, provide access to devices 001 to 01F across two connections (HBA1 to FA1a, HBA2 to FA 1b).

fpath adddev -d /dev/rdsk/clt0d0s2 -w 200010e0698002ad -f 1a -r "001-01F" fpath adddev -d /dev/rdsk/clt0d0s2 -w 200011e0698002ad -f 1b -r "001-01F"

For Host 2, provide access to devices 001 to 01F across two connections (HBA1 to FA 1a, HBA2 to FA 1b).

fpath adddev -d /dev/rdsk/clt0d0s2 -w 200020e0698002ad -f 1a -r "001-01F"fpath adddev -d /dev/rdsk/clt0d0s2 -w 200021e0698002ad -f 1b -r "001-01F"

For Host 3, provide access to devices 110 to 130 across a single connection to FA1a.

fpath adddev -d /dev/rdsk/clt0d0s2 -w 200030e0698002ad -f 1a -r "110-130"

For Host 4, provide access to devices 040-06F and 070-07F across a switch connection to FA 15a and FA 15b.

fpath adddev -d /dev/rdsk/clt0d0s2 -w 300000e06900052b -f 15a -r "040-06F 070-07F"fpath adddev -d /dev/rdsk/clt0d0s2 -w 300000e06900052b -f 15b -r "040-06F 070-07F"


6

For Host 5, provide access to devices 070-07F and 080-087.

fpath adddev -d /dev/rdsk/clt0d0s2 -u lss2105/1f,0,[email protected] -f 15a -r "070-07F"fpath adddev -d /dev/rdsk/clt0d0s2 -u lss2105/1f,0,[email protected] -f 15b -r "070-07F 080-087"

For Host 6, provide access to devices 088-098.

fpath adddev -d /dev/rdsk/clt0d0s2 -u NT460a/adapter0 -f 15b -r "088-098"

For Host 7, provide access to devices 0b0-0cf and 110-124.

fpath adddev -d /dev/rdsk/clt0d0s2 -u NT470a/adapter0 -f 15a -r "110-124"fpath adddev -d /dev/rdsk/clt0d0s2 -u NT470a/adapter0 -f 15b -r "0b0-0cf"


Your updates to the Volume Logix database do not take effect until you cause the Symmetrix to allow the HBA to see the changes, and you cause the host to see the changes.

1. Cause the Symmetrix to refresh its WWN-related memory tables with the contents of the Volume Logix database using the fpath refresh command.

fpath refresh -d /dev/rdsk/clt0d0s2

2. Backup the Volume Logix database using the fpath backupdb command.

fpath backupdb -d /dev/rdsk/clt0d0s2 -o /tmp/backup

3. Reboot Hosts 1, 2, 3, 4, 5, 6, and 7.

Configuration of the Volume Logix database is now complete. From the control station, use fpath lshostdev to view current access controls. From other hosts, use the EMC inquiry utility (inq command) to verify that they can see the specified devices.


6.5 Maintain the Volume Logix Database

After the initial setup, you can add, modify, or remove records in the Volume Logix database by running Volume Logix commands to:

• Add devices for a WWN (fpath adddev).

• Remove devices for a WWN (fpath rmdev).

• Modify the easy-to-type AWWN for use as an alias for a WWN (fpath chgname).

• Swap one HBA for another, while retaining the same device allocation (fpath swaphba).

• Clear an HBA, removing its device allocation (fpath clrwwn).

After each set of changes, remember to activate the configuration by refreshing the Symmetrix, backing up the database, and rebooting the affected hosts.

See Chapter 7 for details of Volume Logix fpath commands.


7

Chapter 7 VOLUME LOGIX CLI

This chapter defines each Volume Logix fpath command.

• Volume Logix CLI ............................................... 180• fpath Command Description ............................ 181• fpath Error Codes................................................ 215

179

7.1 Volume Logix CLIVolume Logix access control functions are controlled through the fpath command line interface that can be invoked from any of the major shell programs. You must be logged on as Administrator (Windows NT) or root (UNIX systems) to run fpath.

You run fpath commands on a host. You can manage the current host or a different host.

▼ CAUTION: Administrator or root logins can reset the database on any host that has Volume Logix Administrative commands installed and is connected to the Symmetrix. EMC recommends that fpath and the Administrative utilities be installed only on a host you designate to be the Administrator host.

180 VOLUME LOGIX CLI

7

7.2 fpath Command DescriptionThe format of an fpath request is:

fpath action { arguments }

Entering the fpath command without any actions or arguments simply lists the fpath version and possible actions/arguments.

Actions are commands to fpath. fpath performs the requested action, displays results to stdout, and returns an error code (See Table 19, The fpath Command Error Codes). The only exception to this general protocol is the initdb action which, since it clears the database, prompts the user for a backup filename and confirmation.

Some of the query actions can result in lengthy output. For any action, you may redirect the output to a file or pipe it to the more command (UNIX systems) or type command (DOS). Also, you may write shell scripts to run fpath commands.

fpath Command Description 181

adddev

Synopsisfpath adddev -d db_device [-w wwn|-u awwn] -f fa -r "range"

Description In the Volume Logix database, adds a device to a list of devices that the HBA identified by the given WWN or AWWN, connected through a given FA port, can access. You may specify devices for up to 32 WWNs for each FA port. This takes effect after either the affected HBA attempts to log on again to the Symmetrix or you enter the fpath refresh command.

To add a meta device, simply add the volume designated as the meta head (as displayed by fpath lssymmdev). The other volumes comprising the meta device will automatically also be added. Do not add volumes designated meta or meta tail.

Options -d db_device

Device name of the Volume Logix database device. If the VCMDBDEVICE environment variable is set, this argument can be used to override that value.

[-w wwn|-u awwn]

WWN or AWWN uniquely identifying an HBA on the host.

The first time you add a device for a particular host HBA, you must use the -w WWN option in order to create a record in the Volume Logix database for this WWN. Once you have created this record and used the fpath chgname command to define an AWWN for this WWN,


7

you can use the -u AWWN in place of the -w WWN if you wish to add more devices for this host HBA.

-f fa

Director number, in hexadecimal, of a Fibre adapter on the Symmetrix.

-r range

Logical device number of one or more Symmetrix volumes.

Entries must be enclosed in double quotes, separated by spaces, and use hexadecimal notation. You may specify individual volumes (e.g., 4 5) and/or hyphenated ranges of volumes (e.g., 11-17 040-06F) and/or the single volume designated the head of a meta volume.

Examples In the Volume Logix database device at /dev/rdsk/clt0d0s2, to define that the host HBA WWN 100003eb00000010, through Symmetrix FA 15a, may access the Symmetrix meta device encompassing 095 through 099, as shown by this fragment of fpath lssymmdev output:


095 4.510 FBA metahead096 4.510 FBA meta097 4.510 FBA meta098 4.510 FBA meta099 4.510 FBA metatail

fpath adddev -d /dev/rdsk/c1t0d0s2 -w 100003eb00000010 -f 15a -r "095"

In the Volume Logix database device at \\.\physicaldrive1, to update an existing record for the host HBA identified by the AWWN john/0 (by a prior fpath adddev and fpath chgname), through its connection to Symmetrix FA 16b, may access Symmetrix logical device 4:


fpath adddev -d \\.\physicaldrive1 -u john/0 -f 16b -r "4"

With the Volume Logix database device specified by the VCMDBDEVICE environment variable, to define that the host HBA WWN 100003eb00000010, through Symmetrix FA 15a, may access Symmetrix logical devices 11 through 17 and a0:

fpath adddev -w 100003eb00000010 -f 15a -r "11-17 A0"


7

backupdb

Synopsis fpath backup -d db_device -o hostpath

Description Backs up a Volume Logix database to the specified NT or UNIX pathname.

This command can be used to maintain several possible configurations of access control which the Administrator can select as needed. See also lsbackup on page 195.

EMC recommends that you backup the database every time you update the database.



-o hostpath

Pathname of a file on the host. The location and filename of the backup file must be unique. Volume Logix will not overwrite an existing file.

Examples On a Windows NT system, to backup the Volume Logix database device specified by \\.\physicaldrive3 to a file C:\Program Files\Symmapps\vcm\backup\bkfile, type:

fpath backupdb -d \\.\physicaldrive3 -o \Program Files\Symmapps\vcm\backup\bkfilefpath backupdb is SUCCESSFUL

On a UNIX system, to backup the Volume Logix database device specified by /dev/rdsk/c1t0d0s2 to a file /usr/symmapps/vcm/backup/bkfile, type:

fpath backupdb -d /dev/rdsk/clt0d0s2 -o /usr/symmapps/vcm/backup/bkfile fpath backupdb is SUCCESSFUL


chgname

Synopsisfpath chgname -d db_device -w wwn -f fa -n awwn

Description Writes an ASCII WWN to the Volume Logix database.You must already have created a record for the WWN in the Volume Logix database using the fpath adddev command.

The AWWN is also stored in the login history table. When you change an ASCII name, the chgname command must look in boththe database and the login history table to make the change.

The chgname command first looks for an occurrence of the AWWN in the login history table and then in the VCMDB.

• If it finds the name in both places, it writes a new AWWN to the login history table and the VCMDB.

• If it does not find an AWWN in the VCMDB, it writes a new AWWN only to the login history table.

• If the command does not find an AWWN in the login history table, it looks in the VCMDB. If it finds an AWWN there, it writes a new AWWN to the VCMDB.

• If the command does not find an ASCII name in the login history table or the VCMDB, it displays an error message.

You may also specify a new AWWN of NULL. This clears any existing AWWN from the database.


7



-w wwn

WWN uniquely identifying an HBA on the host.

-n awwn

User-specified string for use as an alias identifying an HBA on the host. It has two parts, representing a node AWWN and a port AWWN. Each part must be 16 characters or fewer.

It must be unique within this database or be NULL. The port AWWN cannot be NULL unless the node AWWN is also NULL.

-f fa


Examples In the Volume Logix database device specified by /dev/rdsk/c1t0d0s2 on FA 15a, to change the alias 100003eb00000010 to sun_4fl/0:

fpath chgname -d /dev/rdsk/clt0d0s2 -w 100003eb00000010 -f 15a -n "sun_4fl/0" fpath chgname was SUCCESSFUL

In the Volume Logix database device specified by \\.\physical drive1 on FA16b, to change the alias 100003eb00000010 to john/0.


fpath chgname -d \\.\physicaldrive1 -w 100003eb00000010 -f 16b -n "john/0"

fpath chgname was SUCCESSFUL

In the Volume Logix database device specified by /dev/rdsk/c1t0d0s2 on FA 15a, to clear the alias for 100003eb00000010

fpath chgname -d /dev/rdsk/c1t0d0s2 -w 100003eb00000010 -f 15a -n "/"

fpath chgname was SUCCESSFUL


7

clrwwn

Synopsis fpath clrwwn -d db_device [-w wwn -u awwn]

Description Deletes a WWN and all access rights for that WWN (specified by the WWN or AWWN) in the Volume Logix database.

This takes effect after either the affected HBA attempts to log on again to the Symmetrix or you enter the fpath refresh command.



[-w wwn -u awwn]

WWN or ASCII WWN uniquely identifying an HBA on the host.

In order to use the -u awwn option, you must previously have used the fpath adddev command to create a record for this WWN and the fpath chgname command to define an AWWN for this WWN.

The first time you add a device for a particular host HBA, you must use the -w WWN option in order to create a record in the Volume Logix database for this WWN. Once you have created this record and used the fpath chgname command to define an AWWN for this WWN, you can use the -u AWWN in place of the -w WWN if you wish to add more devices for this host HBA.


Example In the Volume Logix database device identified by \\.\physicaldrive1, to remove the record for the host HBA identified by AWWN sun_4fl/0.

fpath clrwwn -d \\.\physicaldrive1 -u sun_4fl/0 fpath clrwwn was SUCCESSFUL

In the Volume Logix database device identified by /dev/rdsk/c1t0d0s2, to remove the record for the host HBA identified by WWN 100003eb00000010.

fpath clrwwn -d /dev/rdsk/clt0d0s2 -w 100003eb00000010 fpath clrwwn was SUCCESSFUL


7

help

Synopsis fpath help

Description Lists the possible actions/arguments.

Examplefpath help

fpath, Copyright EMC Corp. 1998-1999$

Online help for fpath

lsstatus -d pathname indicates whether VCM is on

lshosts lists hosts logged onto a Symmetrix

lsdb lists VCM database

adddev -d pathname [-w wwn -u awwn] -f fa -r "" range of devices

range values are hexadecimaladds devices to access list of an fa for a symm

rmdev -d pathname [-w wwn -u awwn] -f fa -r "" range of devices

range values are hexadecimal, deletes devices to access list of an fa for a symm

lshostdev lists fibre devices visible from this computer

lshbawwn lists the fibre adapters and WWNs on this computer

help requests brief summary of commands

initdb -d pathname initializes VCM database

lsbackup -o hostpath displays the contents of the specified backup file in the same format as the fpath lsdb command

chgname -d pathname -w wwn -f FA -n new_awwn

changes ASCII AWWN

refresh -d pathnamecauses the Symmetrix to refresh VCM from VCMDB

lssymmfas -d pathname lists the Fibre adapters on this Symmetrix

lssymmdev -d pathname lists what devices in Symm are on what FA

backupdb -d pathname -o filename


restoredb -d pathname -o filename

swaphba -d pathname [-w wwn -u awwn] -n new_wwn

clrwwn -d pathname [-w wwn -u awwn]


7

initdb

Synopsis fpath initdb -d db_device

Description Creates and initializes a Volume Logix database.

▼ This action removes all the information from the Volume Logix database. Use only when you start to define access control or wish to clear everything and start over.

Since initdb could be very destructive, it asks the following question of the user interactively:

“Enter full pathname of backup file:"

You must enter the pathname of a file to be created. If the pathname you enter already exists, fpath initdb will fail with the message:

fpath initdb backup file is already present

Next, fpath initdb prompts:

Do you really want to do this answer y/n:

Respond "y".

The fpath initdb action can take several minutes to clear and re-initialize the database. On completion, the database becomes write locked to the operating system and can be updated only via fpath commands.

The new database takes effect after either an affected HBA attempts to log on again to the Symmetrix or you enter the fpath refresh command.



Device name of the Volume Logix database device. If the VCMDBDEVICE environment variable is set, will override that value.

Examples To initialize a Volume Logix database on the Symmetrix identified by \\.\physicaldrive3:

fpath initdb -d \\.\physicaldrive3

To initialize a Volume Logix database on the Symmetrix identified by /dev/rdsk/c1t1d0s2:

fpath initdb -d /dev/rdsk/c1t1d0s2


7

lsbackup

Synopsis fpath lsbackup -o hostpath

Description Displays the contents of the specified backup file in the same format as the fpath lsdb command.

Options -o hostpath

Pathname of a file on the host.

Example Displays the Volume Logix database held in the backup file archive/BK021599:

fpath backupdb -o backups/021599fpath, Copyright EMC Corp. 1998-1999lsbackup VCM DB device = /dev/rdsk/c2t1d0s2 listing VCM Database for FA 15aDISKS permitted access by:WWN = 200000e0698002ad AWWN = / 000 001 002 003 004 00a 00e 013 014 015 ...


lsdb

Synopsis fpath lsdb -d db_device

Description Lists which devices in a Symmetrix the specified WWN can access (lists the Volume Logix database contents).


Device name of the Volume Logix database device. If the VCMDBDEVICE environment variable is set, will override that value.

Example Lists the Volume Logix database identified by /dev/rdsk/c1t0d0s2:

fpath lsdb -d /dev/rdsk/c1t0d0s2 fpath, Copyright EMC Corp. 1998-1999 lsdb VCM DB device = /dev/rdsk/c2t1d0s2 listing VCM Database for FA 15aDISKS permitted access by:WWN = 200000e0698002ad AWWN = / 000 001 002 003 004 00a 00e 013 014 015 ...


7

WWN = 100000e06900052b AWWN = / 000 001 002 003 004 005 006 007 008 009 00a 00b 00c 00d 00e 00f 010 011 012 013 014 015 016 017 018 019 01a 01b 01c 01d 01e 01f 020 WWN = 100000e0690015ba AWWN = lss2105/1e,0,fca@1,0 000 01a

01b 01c 01d 01e 01f 020 listing VCM Database for FA 16aDISKS permitted access by:WWN = 10000060b03e8650 AWWN = / 008


listing VCM Database for FA 15bDISKS permitted access by:WWN = 10000060b03e8650 AWWN = / 001 002 008 009 listing VCM Database for FA 16bDISKS permitted access by:WWN = 200000e0698002ad AWWN = / 000 001 002 003 004 005 WWN = 8765432187654321 AWWN = / 001 002 WWN = 100000e0690015ba AWWN = lss2105/1f,0,fca@1,0 000 001 002 003

fpath lsdb was SUCCESSFUL


7

lshbawwn

Synopsis fpath lshbawwn

Description Lists the WWNs of the HBAs on this host.

Example To discover the WWN of the current host:

fpath lshbawwn fpath, Copyright EMC Corp. 1998-1999$1e,0,fca@1,0 100000e06900052b1f,0,fca@3,0 100000e0690015ba

fpath lshbawwn was SUCCESSFUL


lshostdev

Synopsis fpath lshostdev

Description Gives a host-centric view of Symmetrix devices available through an FA, displays their TID and LUN, Symmetrix device number, Symmetrix serial number, and their controlling FA. It also shows, for each Symmetrix to which this host is connected, the device that has been designated as the Volume Logix database device (VCMDB).

The VCMDB entry is listed for each path between the host and the VCMDB device. Multiple entries may indicate more than one HBA on this host, a connection to more than one FA on the Symmetrix, or a combination, as shown below. Use the fpath lshostdev and fpath lshbawwn commands together to show the different paths.

Examples To discover the pathname of the Volume Logix database device prior to defining any access controls:

Connections fpath lshostdev fpath lshbawwn

HBA1-FA1HBA1-FA2

2 paths VCMDB 1 HBA

HBA1-FA1HBA2-FA1

2 paths VCMDB 2 HBAs

HBA1-FA1HBA1-FA2HBA2-FA1HBA2-FA2

4 paths VCMDB 2 HBAs


7


Symmetrix Fibre Devices on this computer Pathname TID LUN Device Symm serial FA \\.\PHYSICALDRIVE3 0 0 000 0182601088 15a VCMDBfpath lshostdev was SUCCESSFUL

To view the Symmetrix devices available to this host. Note that four paths to this Symmetrix’s VCMDB are available, each representing a different HBA-FA connection:

fpath lshostdev fpath, Copyright EMC Corp. 1998-1999$ Symmetrix Fibre Devices on This computer

Pathname TID LUN Device Symm serial FA /dev/rdsk/c1t0d0s2 0 0 000 0182601088 15a VCMDB/dev/rdsk/c1t0d1s2 0 1 001 0182601088 15a /dev/rdsk/c1t0d2s2 0 2 002 0182601088 15a /dev/rdsk/c1t0d3s2 0 3 003 0182601088 15a /dev/rdsk/c1t0d4s2 0 4 004 0182601088 15a /dev/rdsk/c1t0d5s2 0 5 005 0182601088 15a /dev/rdsk/c1t0d6s2 0 6 006 0182601088 15a /dev/rdsk/c1t0d7s2 0 7 007 0182601088 15a /dev/rdsk/c1t0d8s2 0 8 008 0182601088 15a /dev/rdsk/c1t0d9s2 0 9 009 0182601088 15a /dev/rdsk/c1t0d10s2 0 a 00A 0182601088 15a /dev/rdsk/c1t0d11s2 0 b 00E 0182601088 15a /dev/rdsk/c1t1d0s2 0 0 000 0182601088 16b VCMDB/dev/rdsk/c2t0d0s2 0 0 000 0182601088 15a VCMDB/dev/rdsk/c2t0d1s2 0 1 001 0182601088 15a /dev/rdsk/c2t0d2s2 0 2 002 0182601088 15a /dev/rdsk/c2t0d3s2 0 3 003 0182601088 15a /dev/rdsk/c2t0d4s2 0 4 004 0182601088 15a /dev/rdsk/c2t0d5s2 0 5 005 0182601088 15a /dev/rdsk/c2t0d6s2 0 6 006 0182601088 15a /dev/rdsk/c2t0d7s2 0 7 007 0182601088 15a /dev/rdsk/c2t0d8s2 0 8 008 0182601088 15a /dev/rdsk/c2t0d9s2 0 9 009 0182601088 15a /dev/rdsk/c2t0d10s2 0 a 00A 0182601088 15a /dev/rdsk/c2t0d11s2 0 b 00E 0182601088 15a /dev/rdsk/c2t1d0s2 0 0 000 0182601088 16b VCMDB/dev/rdsk/c2t1d1s2 0 1 001 0182601088 16b /dev/rdsk/c2t1d2s2 0 2 002 0182601088 16b /dev/rdsk/c2t1d3s2 0 3 003 0182601088 16b /dev/rdsk/c2t1d4s2 0 4 004 0182601088 16b fpath lshostdev was SUCCESSFUL


lshosts

Synopsis fpath lshosts -d db_device

Description Lists which hosts and HBAs are logged onto a Symmetrix for all FAs (Login History table). The originator node_wwn field shows the WWN for a master HBA if present. The originator port_wwn shows the WWN for the HBA which is communicating with the Symmetrix. The columns labelled user gen node name and user gen port name show the AWWN generated by the vcmfind utility. You can view similar information with the fpath -chgname command.



Example To display the login history table for the Symmetrix identified by the VCMDB named /dev/rdsk/c1t0d0s2.


7

fpath lshosts -d /dev/rdsk/clt0d0s2 fpath, Copyright EMC Corp. 1998-1999Displaying login-history table for FA 1aEntry SID originator originator user gen user gen

node_wwn port_wwn node name port name0 1 200010e0698002ad 200010e0698002ad NT410a adapter00 1 200020e0698002ad 200020e0698002ad NT420a adapter00 1 200030e0698002ad 200030e0698002ad NT430a adapter0


node_wwn port_wwn node name port name0 1 200011e0698002ad 200011e0698002ad NT410a adapter10 1 200021e0698002ad 200021e0698002ad NT420a adapter1

Displaying login-history table for FA 15aEntry SID originator originator user gen user gen

node_wwn port_wwn node name port name0 1 300000e06980052b 300000e06900052b NULL NULL 0 1 300050e0698002ad 300050e0698002ad lss2105 1e,0,fca@1,00 1 200060e0698002ad 200060e0698002ad lss2106 1e,0,fca@1,0 0 1 200070e0698002ad 200070e0698002ad lss2107 1e,0,fca@1,0


node_wwn port_wwn node name port name0 1 300000e06980052b 300000e06900052b NULL NULL0 1 300050e0698002ad 300050e0698002ad lss2105 1e,0,fca@1,00 1 200060e0698002ad 200060e0698002ad lss2106 1e,0,fca@1,00 1 200070e0698002ad 200070e0698002ad lss2107 1e,0,fca@1,0

fpath lshosts was SUCCESSFUL


lsstatus

Synopsis fpath lsstatus -d db_device

Description From the viewpoint of the host on which this command is run, indicates whether or not the FA on the Symmetrix identified by the db_device argument has Volume Logix turned on. This command is typically run in conjunction with fpath lshostdev.



Example Imagine that the Symmetrix has two FAs, 15a and 16a, such that fpath lshostdev outputs:

Pathname TID LUN Device Symm serial FA .../dev/rdsk/c1t0d0s2 0 0 000 0182601088 15a VCMDB/dev/rdsk/c2t0d0s2 0 0 000 0182601088 16a VCMDB...

To determine whether Volume Logix is turned on for an FA, select the VCMDB pathname which uses that FA.

fpath lsstatus -d /dev/rdsk/c1t0d0s2 fpath, Copyright EMC Corp. 1998-1999VCM IS ONfpath lsstatus was SUCCESSFUL

fpath lsstatus -d /dev/rdsk/c2t0d0s2 fpath, Copyright EMC Corp. 1998VCM IS OFFfpath lsstatus was SUCCESSFUL

VCM is turned on for FA15a, off for FA 16a.


7

lssymmdev

Synopsis fpath lssymmdev -d db_device

Description For the Symmetrix pointed to by the db_device, lists all FAs, which devices they provide access to, their capacity, and their type.

Type may be one of:



Table 18. Symmetrix Device Types

Type Capacity Description

FBA Gigabytes Fixed Block Addressing, typically a SCSI device. Type may be qualified by one of:• BCV: Business Continuance Volume, that functions as

a mirrored media to a standard device.• Meta: One of a concatenated group of adjacent

Symmetrix devices that appear as one target volume. The first volume of a meta device is labeled meta head; the last volume is labeled metatail.

• DRV: Dynamic Relocation Volume, that functions as a non user-addressable unit of storage used to hold customer data while reconfiguration (on a volume granularity) is executed.

CKD Cylinders Not supported at this release. Count Key Data, typically, an IBM mainframe device.


Example To display the devices available on the Symmetrix pointed to by /dev/rdsk/c1t0d0s2:

fpath lssymmdev -d /dev/rdsk/clt0d0s2 fpath, Copyright EMC Corp. 1998-1999


000 0.008 FBA001 4.510 FBA... ... ...03F 4.510 FBA100 4.510 FBA... ... ...160 4.510 FBA


000 0.008 FBA001 4.510 FBA... ... ...03F 4.510 FBA


000 0.008 FBA040 4.510 FBA... ... ...07F 4.510 FBA095 4.510 FBA metahead096 4.510 FBA meta097 4.510 FBA meta098 4.510 FBA meta099 4.510 FBA metatail09A 4.510 FBA metahead09B 4.510 FBA meta09C 4.510 FBA meta09D 4.510 FBA meta09E 4.510 FBA meta09F 4.510 FBA metatail0A0 4.510 FBA


000 0.008 FBA0B0 4.510 FBA... ... ...0FF 4.510 FBA

fpath lssymmdev was SUCCESSFUL


7

lssymmfas

Synopsis fpath lssymmfas -d db_device

Description Lists the FAs on the Symmetrix pointed to by the db_device argument.



Example To list the Fibre adapters on the Symmetrix identified by /dev/rdsk/c1t0d0s2.

fpath lssymmfas -d /dev/rdsk/c1t0d0s2 fpath, Copyright EMC Corp. 1998-1999 FIBRE directors are: director number: 15a director number: 16a director number: 15b director number: 16bfpath lssymmfas was SUCCESSFUL


refresh

Synopsis fpath refresh -d db_device

Description Causes the Symmetrix to refresh its WWN-related memory tables with the contents in the Volume Logix database. You should issue the refresh command whenever you change either the volume configuration or the topology.

Note that this command makes only the Symmetrix aware of changes. You also need to make the host aware of the changes. To do this, EMC recommends you reboot the host after each refresh.

All changes you have made are now effective. If your changes to the configuration make a volume not accessible to a host where there are currently active sessions with that volume, the user will not be able to save the data.

Before issuing the refresh command, use the fpath lshosts command to list which hosts/HBAs are logged on to which FAs. You can then warn users to complete their sessions before you remove their connection.



Example To refresh the memory tables of the Symmetrix identified by Volume Logix database device path /dev/rdsk/c1t0d0s2:

fpath refresh -d /dev/rdsk/c1t0d0s2


7

restoredb

Synopsis fpath restoredb -d db_device -o hostpath

Description Restores a Volume Logix database from the specified NT or UNIX pathname.

This command may take several minutes to complete before returning to the command prompt. This is because it performs an initdb before restoring the database.


Device name of the Volume Logix database device. If the VCMDBDEVICE environment variable is set, this will override that value.

-o hostpath

Pathname of a file on the host.

Example To restore a Volume Logix database from the UNIX file /usr/vlogix/backup_file to the Symmetrix device specified by /dev/rdsk/c1t0d0s2:

fpath restoredb -d /dev/rdsk/clt0d0s2 -o /usr/vlogix/backup_file fpath restoredb is SUCCESSFUL

To restore a Volume Logix database from the Windows NT file \temp\vlback to the Symmetrix device specified by \\.\physicaldrive3:

fpath restoredb -d \\.\physicaldrive3 -o \temp\vlback fpath restoredb is SUCCESSFUL


rmdev

Synopsisfpath rmdev -d db_device [-w wwn -u awwn] -f fa -r "range"

Description In the Volume Logix database, removes a device from the list of devices that the HBA (specified by the WWN or AWWN) can access.

The first time you add a device for a particular host HBA, you must use the -w WWN option in order to create a record in the Volume Logix database for this WWN. Once you have created this record and used the fpath chgname command to define an AWWN for this WWN, you can use the -u AWWN in place of the -w WWN if you wish to remove more devices for this host HBA.

To remove a meta device, simply remove the volume designated as the meta head (as displayed by fpath lssymmdev). The other volumes comprising the meta device will automatically also be removed. Do not remove a volume of type meta or meta tail.

This takes effect after either the affected HBA attempts to log on again to the Symmetrix or you enter the fpath refresh command.


Device name of the Volume Logix database device. If the VCMDBDEVICE environment variable is set, this will override that value.


7

[-w wwn -u awwn]

WWN or ASCII WWN uniquely identifying an HBA on the host.

You can only use the -u AWWN option if you have previously used the fpath chgname command to define an AWWN for this WWN. The first time you add a device for a particular host HBA, you must use the -w WWN option in order to create a record in the Volume Logix database for this WWN. Once you have created this record and used the fpath chgname command to define an AWWN for this WWN, you can use the -u AWWN in place of the -w WWN if you wish to remove more devices for this host HBA.

-f fa


-r range

Logical device name of a volume in the Symmetrix. Entries must be enclosed in double quotes, separated by spaces, and use hexadecimal notation. You may specify individual volumes (for example., 4 5) and/or hyphenated ranges of volumes (for example, 11-17 040-06F), and/or the single volume designated as the head of a meta volume.

Example To remove access to the Symmetrix meta device which encompasses logical devices 095 through 099, through FA 15a for the HBA identified by WWN 100003eb00000010 on the Symmetrix identified by


/dev/rdsk/clt0d0s2 as shown by this fragment of fpath lssymmdev output:


095 4.510 FBA metahead096 4.510 FBA meta097 4.510 FBA meta098 4.510 FBA meta099 4.510 FBA metatail

...

fpath rmdev -d /dev/rdsk/c1t0d0s2 -w 100003eb00000010 -f 15a -r "095" fpath rmdev was SUCCESSFUL

To remove access to Symmetrix logical devices 11 through 17 and A0 through FA15a for the HBA identified by WWN 100003eb00000010 on the Symmetrix identified by /dev/rdsk/c1t0d0s2.

fpath rmdev -d /dev/rdsk/c1t0d0s2 -w 100003eb00000010 -f 15a -r "11-17 A0"fpath rmdev was SUCCESSFUL


7

swaphba

Synopsisfpath swaphba -d db_device [-w old_wwn|-u awwn] -n new_wwn

Description Allows you to swap one host HBA with another.

In the event of a host HBA malfunctioning, you can use the fpath swaphba command to substitute a new WWN for the old WWN while retaining a given set of volumes.

To swap a host HBA, follow the host system manufacturer’s instructions for installing the new board, connecting it to the Fibre, and rebooting.

Use fpath lshosts to determine the WWN of the original HBA (from the original database entry). Then run fpath lshbawwn or vcmfind to determine the WWN of the new HBA. Finally, use fpath swaphba to substitute the new WWN for all occurrences in the database of the old WWN.

This action takes effect after either the affected HBA attempts to log on again to the Symmetrix or you enter the fpath refresh command.




-w old_wwn|-u awwn-n new_wwn

WWN (or AWWN created by fpath chgname) uniquely identifying an HBA on the host.

The new WWN must not exist in the VCMDB, with or without devices. (To reuse an existing HBA, remove all devices, then run fpath clrwwn to remove all knowledge about this WWN.)

Example To move the access controls previously granted to the HBA identified by WWN 10003eb0000010, to the HBA identified by WWN 100000e0698002ad, on the Symmetrix identified by /dev/rdsk/c1t0d0s2.

fpath swaphba -d /dev/rdsk/clt0d0s2 -w 100003eb00000010 -n 100000e0698002adfpath swaphba was SUCCESSFUL


7

7.3 fpath Error CodesThe fpath commands return error codes as listed in Table 19. On UNIX systems, you can write a shell script to process these error codes.

Table 19. The fpath Command Error Codes

Number and Error Error Description

0 VCMAPI_SUCCESS (Command) "was SUCCESSFUL"

-1 VCMAPI_FAIL (Command)"FAILED"

-2 VCMAPI_CANT_OPEN "FAILED could not open specified device"

-3 VCMAPI_NO_MEM "FAILED could not get memory"

-4 VCMAPI_NO_PATH "FAILED no path to VCM database provided"

-5 VCMAPI_DB_READ_FAIL "FAILED VCM database read failed"

-6 VCMAPI_NO_UGH_MATCH "FAILED could not match awwn"

-7 VCMAPI_NO_FREE_SLOTS "FAILED found no free slots in VCM database"

-8 VCMAPI_BAD_DEVICE_LIST "FAILED bad list of devices"

-9 VCMAPI_BAD_PARAM_ALLOCATION_MAP "FAILED because of bad allocation map"

-10 VCMAPI_WRITESYMPORTENTRY_FAILED "FAILED write to VCM database failed"

-11 VCMAPI_NO_FAS "FAILED NO FAs found on this Symmetrix"

-12 VCMAPI_INVALID_FA_VALUE "FAILED invalid FA value"

-13 VCMAPI_DVSCNFIG_FAIL "FAILED could not do PSCdsvcnfig syscall"

-14 VCMAPI_CHG_BAD_OPTION "FAILED bad option for change"

-15 VCMAPI_CANT_READ_LOGIN "FAILED could not read login-history table in Symmetrix"

-16 VCMAPI_NO_WWN_MATCH "FAILED could not match WWN"

fpath Error Codes 215

-17 VCMAPI_BAD_WWN_LENGTH "FAILED incorrect wwn length"

-18 VCMAPI_PSCsyserptr_FAILED "FAILED doing PSCsyserptr syscall"

-19 VCMAPI_UGH_TOO_LONG "FAILED because AWWN was too long"

-20 VCMAPI_NOT_A_SYMM_DEVICE "FAILED not a Symmetrix device"

-21 VCMAPI_EMCINQUIRY_FAIL "FAILED doing EMCInquiry"

-22 VCMAPI_WWN_IN_DB "FAILED replacement WWN already in VCM DB"

-23 VCMAPI_NO_FILE "No such input filename"

-24 VCMAPI_FA_NOT_ON_SYMM "FA specified is not on this Symmetrix"

-25 VCMAPI_NO_SYMM_FIBRE_HBA "vcmfind did not find any Symmetrix fibre hba devices"

-26 VCMAPI_NO_RANGE "No range specified"

-27 VCMAPI_NOT_A_SYMM_FIBRE_DEVICE "Device is not a Symmetrix Fibre Device"

-28 VCMAPI_NOT_VCMDB_DEVICE "It is a symm fibre device but not a VCMDB device"

-29 VCMAPI_BAD_RANGE "Bad range specified"

-30 VCMAPI_PSCSADVRECD_FAIL "PSCSADVRECD syscall flopped"

-31 VCMAPI_BAD_INCOMING_AWWN "Invalid format of incoming AWWN"

-32 VCMAPI_BAD_BACKUP_NAME "Bad backup name"

-33 VCMAPI_BACKUP_THERE "Backup file is already present"

-34 VCMAPI_CANT_WRITE_BACKUP "Could not write backup file"

-35 " "

-36 VCM_PARM_INVALID " "

-37 SYSCALL_FAILED " "

-38 VCM_ACCESS_VIOLATION " "




7

-39 VCM_NO_AVAILABLE_RECORDS ""

-40 SVCM_WR_EN_FAILE ""

-41 SVCM_WR_DIS_FAILED ""

-42 SVCM_INVALID_RESTORE_REQUEST ""

-43 VCMAPI_INVALID_VCM_DEVICE "Specified device is not a VCM database device"

-44 VCMAPI_NO_WWN_SPECIFIED "chgname requires a WWN to be specified "

-45 VCMAPI_MATCHING_AWWN "New awwn is already assigned to that wwn"

-46 VCMAPI_DUPLICATE_AWWN "New awwn is already assigned to another wwn"

-47 VCMAPI_MATCH_DUPE_AWWN "New awwn is assigned to that wwn and another one"

-48 VCMAPI_BAD_AWWN "Could not use that awwn because it matched another one"

-49 VCMAPI_INIT_NO_BACKUP "Did initdb but could not backup because VCMDB was bad"

-50 VCM_READ_ERR "Bad read from VCMDB"

-51 VCM_WRITE_ERR "Bad write to VCMDB"

-52 VCM_HDR_INVALID "Invalid vcm header record"

-53 SVCM_INVALID_VCM_DEVICE "Not a VCMDB device"

-54 VCM_TOO_MANY_DEVICES "Too many devices on host"

-99 VCM_RECORD_ERR "Bad record in the DB"



fpath Error Codes 217


8

Chapter 8 VCMFIND UTILITY

This chapter describes the Volume Logix vcmfind utility

• Overview of the vcmfind Command............... 220• vcmfind ................................................................ 221• ASCII WWN ........................................................ 223

219

8.1 Overview of the vcmfind CommandThe vcmfind utility should be installed on each host attached to a Symmetrix in the Fibre Channel environment. vcmfind has two purposes:

• to determine the WWN of each host HBA, for hosts that do not have fpath installed.

The fpath lshbawwn command also displays WWNs of each host’s HBAs. However, in addition, the vcmfind command assigns the HBAs with AWWNs.

• to assign an easy-to-type alias known as an ASCII WWN (AWWN) to each WWN, if one is not already present.

220 VCMFIND UTILITY

8
8.2 vcmfind
Synopsis vcmfind

Description You must be logged on as administrator (Windows NT) or root (UNIX) to use this command.

We recommend that you run vcmfind each time the host is rebooted. On a UNIX system, you can to do this by including the /usr/symmapps/vcm/.vcmfind command in the startup file /etc/inittab file so that it is run automatically at boot time. (Refer to Running vcmfind and fcompare at Start-up on page 34.)

The vcmfind utility is primarily a discovery mechanism.

Host HBAs connect to a Fibre Channel environment by "logging on to the Fibre." The vcmfind utility runs on a host and searches the Fibre Channel environment for Symmetrix devices on each HBA on the host.

When vcmfind finds a Symmetrix FA, it connects to it, locates the Login History table held in the Symmetrix’s memory, and does one of the following for its host’s HBA’s WWN:

1. If there is already an AWWN in the Login History table for this WWN, it is not touched.

2. If there is not an AWWN in the Login History table record, vcmfind checks whether an AWWN exists in the VCMDB. If one does, vcmfind writes it to the Login History Table.

vcmfind 221

3. If there is no AWWN in the VCM DB entry and no AWWN in the Login History table, then vcmfind creates an AWWN and writes it to the Login History table.

This AWWN is only for internal use.

The vcmfind utility does NOT update AWWNs in the VCM DB. You must use the fpath chgname command to define an AWWN for an existing WWN record in the database. Refer to fpath Command Description on page 181.

vcmfind returns information about this connection back to its host system—vcmfind is the primary mechanism by which hosts other than the administrator host can learn about their connection to the Symmetrix. The information displayed on the host includes the adapter number and WWN of the host HBA together with the device name which the HBA used to locate the Symmetrix and its FA.

For example, the vcmfind output for a host with two HBAs connecting via a hub to two FAs on a single Symmetrix would show:

vcmfindvcmfind, Copyright EMC Corp. 1998-1999 ADAPTER WWN PATHNAME FAfca@1,0 300000e06900052b /dev/rdsk/c1t0d0s2 15afca@1,0 300000e06900052b /dev/rdsk/c1t1d0s2 16bfca@3,0 100000e06900015a /dev/rdsk/c2t0d0s2 15afca@3,0 100000e06900015a /dev/rdsk/c2t1d0s2 16b

The vcmfind utility returns a code to indicate success or failure as listed Table 20.

Table 20. vcmfind Error Codes

Number Description

0 Normal successful return code

non-zero vcmfind did not find any paths to Symmetrix fibre devices

222 VCMFIND UTILITY

8
8.3 ASCII WWN Because the Login History table exists only in Symmetrix memory, the AWWN generated by vcmfind is not lost when a host is reboots. If the Symmetrix is rebooted the AWWN information is lost unless it has been saved in the VCMDB. However, as soon as vcmfind is run again, the AWWN is recreated. The AWWN that is recreated will be the same unless you have renamed the host or HBA.
AWWN format An ASCII WWN (AWWN) generated by vcmfind consists of two parts: the host’s host name and the adapter’s adapter name.

• On Windows NT, the adapter number takes the form adapter0, adapter1, etc. For example, the AWWN for host whose TCP/IP host name is john4554b, on adapter 0 would be john4554b/adapter0.

• On Solaris, the adapter number takes the form sbus,fca@adapter. For example, the AWWN for host lss1205, sbus 1f, adapter 0, would be lss1205/1f,0,fca@1,0.

• On HP-UX, the adapter number takes the form bus-slotx4. For example, the AWWN for host puckoon, bus 8, third slot (slot times 4) would be puckoon/8-12.

Each part of the AWWN is from one to 16 characters or can be both be NULL.

Using the AWWN An AWWN can only be used in the fpath adddev, rmdev, and clrwwn commands once it has been defined to the Volume Logix database of login

ASCII WWN 223

history t able. In other words, you must have previously used the fpath adddev command to create a record for this WWN, and have used the fpath chgname command to create an AWWN for this WWN. (Refer to chgname on page 186.)

The fpath chgname command writes the specified AWWN to the Volume Logix database record for this WWN and into the Login History table, thereby making it permanent across both host and Symmetrix reboots. For example, you could change lss1205/fca@1,0 to Sun_4thFloorLab/0.

Once this has been done, then the AWWN may be used to uniquely identify the HBA in place of the longer and more difficult to type WWN.

Displaying theAWWN

From the administrator host, you can use the fpath lshosts command to display the contents of the Login History table, and thereby determine the AWWN given to a host by vcmfind or fpath chgname.

224 VCMFIND UTILITY

9
Chapter 9 FCONFIG AND FCOMPARE UTILITIES
This chapter describes how to use the Volume Logix fconfig and fcompare utilities to perform name binding in a Fibre Channel environment.

• Overview of Device Naming ............................ 226• fconfig Command Description ......................... 231• fcompare Command Description ..................... 233

225

9.1 Overview of Device Naming

How Device Naming Works

During an operating system boot sequence, each host bus adapter goes through a discovery process, assigning to each physical device it finds, the next number in a series. Each physical device can then be uniquely identified. For example, on a Windows NT system, a device name takes the form \\.\physicaldrive1, \\.\physicaldrive2. On a UNIX system, a device name uses the combination of host bus controller, target, and LUN, for example, c1t0d0s2.

When an HBA is physically connected to a device via point-to-point cable (or when several devices are daisy-chained together), devices are discovered in the same sequence and assigned the same device identifier each time the system boots. In a Fibre Channel and Fibre Channel Arbitrated Loop environments, each host bus adapter goes through the same discovery process.

With Fibre Channel Switched Fabric however, devices are discovered in random order. The host has no control over the order in which the switch sends or receives packets, makes routing choices, or connnects or disconnects Symmetrix systems.

In these environments the host bus adapter is likely to assign to a device a different device identifier each time the host system is booted. This can present a problem if the system administrator has scripts or mount commands that point to devices whose names have changed during a reboot.

Figure 22 and Figure 23 illustrate these differences.

226 FCONFIG AND FCOMPARE UTILITIES

9

Figure 22. Discovering Devices (Point-to-Point)

Figure 23. Discovering Devices (Network)

HOST

SYMMETRIX

HBA

FA

1 2 3 4

Discovery

Findings

HOST

HBA

Discovery

HOST

SYMMETRIX SYMMETRIX

FA15b FA15bFA15a FA15a

2

c1t0d0c1t0d1

c1t0d0c1t0d1

c1t1d0c1t1d1

c1t1d0c1t1d1

24 43 31 1

HBA

Network Network

Discovery Target 0 and 1assignmentshave changed

FindingsFindings

(After)(Before)

Overview of Device Naming 227

Device Name Binding

To ensure that the host application sees the same device after the host has been rebooted, a persistent relationship between the device name and the actual device must be created. This is called binding.

The rules for discovering a hostname, are:

1. Use the hostname first.

2. If a hostname is not available or is greater than 16 characters, get its IP address and create a name such as: HOST.123.56.789 where 123.56.789 is the last three octets of the IP address.

3. If an IP address is not available then the first two characters of the node AWWN will be the type of host computer:

• SO Solaris (Sparc) system

• HP HP-UX system

• NT Windows NT system

The last 14 characters will be the left justified ASCII representation of the WWN of the first HBA found on that host. For example, on an HP-UX system without a hostname or IP address, the WWN of the first HBA found on this system is 10000060b03e861c the AWWN will be HP000060b03e861c

For Adaptors a name is generated from hardware specific information. If a name is greater than 16 characters, the string is truncated, preserving the right-most 16 characters.

Creating this binding is the responsibility of the host bus adapter driver software.

Note that currently only Jaycor has this functionality for Solaris. It requires modifying the sd.conf file. Before modifying the sd.conf file, make a backup copy. Extreme care must be taken while editing the


9

file since a typo could render the system unbootable. For details on syntax, refer to the driver release notes and the EMC Connectrix Enterprise Storage Network System Topology Guide.

The Volume Logix fconfig and fcompare utilities are provided to record the binding information and compare it to the original in subsequent boots.

Benefits of fconfig and fcompare

By using fconfig and fcompare with fpath backupdb, it is possible to save a known configuration. You can then use fpath restoredb to restore the saved configuration to a Volume Logix database device. A good method for archiving could be to create subdirectories named by date under the /usr/vcm or \usr\vcm directories. In those subdirectories, store the .fconfig file and associated backup files.

This method will not restore any associated raw device names with Symmetrix devices that may have changed. It will indicate that the configuration has changed from the time the .fconfig file was created.

When to use fconfig and fcompare

On each host in turn:

1. Check that all file systems are mounted and all required devices are visible.

2. Run fconfig to create a Name Binding table that associates raw device names to specific Symmetrix devices. The fconfig command creates the .fconfig file that is used as a base line for comparison using the fcompare command.

3. When the host is rebooted, run fcompare to check the name bindings defined in the .fconfig Name Bindings table against the actual topology.

Overview of Device Naming 229

4. Check each difference reported by fcompare and take appropriate action. For example, assign new raw devices to applications, or reassign raw devices names whose Symmetrix device association has changed.

5. As new devices (and new Symmetrixes) are added to the Fibre Channel environment, rerun fconfig periodically to update it with new device information.


9

9.2 fconfig Command Description

Synopsis fconfig

Description The fconfig program is a utility that you run once to all configure devices, file systems, and databases in order to create a Name Bindings table with a record for each device visible in your Fibre Channel environment. You should run fconfig after initial installation, and always after any changes are made to to the configuration on a VCMDB.

You must be root (UNIX) or Administrator (Windows NT) to run fconfig.

The fconfig utility records the Name Bindings table (.fconfig) in the default data directory:

C:\usr\vcm\.fconfig (on Windows NT systems)

/usr/vcm.fconfig (on UNIX systems)he configuration on a VCMDB.

The directory must exist for the file to be created. The .fcompare file is in machine-readable form and must not be edited.

If you have installed Volume Logix elsewhere, you must set the VLOGIX_DATA environment variable to point to your custom installation directory. For example, if on a UNIX system you installed Volume Logix in this directory:

/usr/local/volume_logix

then you must set the VLOGIX_DATA environment variable to the same directory.

fconfig Command Description 231

The fconfig utility creates a file if one does not already exist, else it updates an existing file. The information includes:

• Raw device name• Symmetrix serial number• Symmetrix identifier


9

9.3 fcompare Command Description

Synopsis fcompare

Description fcompare is a utility program that compares the list of Symmetrix devices recorded by fconfig utility with those currently available in the Fibre Channel environment. You should run fcompare at start-up to ensure that all devices are present and configured as indicated in the .fconfig file that was previously created by the fconfig command.

You must log in as root (UNIX systems) or Administrator (Windows NT systems) to run fcompare.

You should install fcompare on each host attached to a Symmetrix in the Fibre Channel environment and run it at boot time. (Refer to Running vcmfind and fcompare at Start-up on page 34.)

The fcompare command works as follows:

1. If <VLOGIX_DATA>/.fconfig does not exist, the fcompare command defaults to C:\usr\symmapps\vcm\.fconfig (Windows NT systems) or /usr/symmapps/vcm/.fconfig (UNIX systems) if it exists on this host.

If the .fconfig file does not exist, then fcompare exits with an error stating that no .fcompare file was found.

2. It checks that, for this host:

• All devices are present• The current devices are the same devices

as the originals• There are no extra devices

fcompare Command Description 233

3. It returns a code indicating success or that an inconsistency has occurred

EMC expects that each user decide whether or not to use fconfig and fcompare in their environment. It may depend on their configuration or other requirements. If they choose to use them, then they should write a shell script (UNIX) customized to their needs.

Actions you should consider taking are for non-zero return codes are:

• write an event to the system log

• send an administrative alert

• investigate the problem.

▼ If any code of 1, 3, 4, 5, 6, or 7 is returned, EMC strongly recommends that you stop the system while you investigate the problem.

Table 21. fcompare Error Codes

Code Meaning

0 Success

1 Missing device. A device was present and is not now.

2 Extra device. A device has appeared that was not present before

3 Conditions 1 and 2 occurred.

4 A device is present that is not the same as the original device



7 Conditions 1, 2, and 4 occurred.


9

These codes do not display on the monitor so you must write a script or batch file to test the return code variable.

A simple shell script is shown below:

fcompareif (( $? !=0 ))then

echo "WARNING: fcompare has detected inconsistency"fiexit

For details of how to write shell scripts, see your UNIX operating system documentation.

Examples Screen output of a configuration that would return an error code of 0 to a script.

/usr/symmapps/vcm fcomparefcompare , fcompare , Copyright EMC Corp. 1998-1999fcompare SUCCESSFUL

Screen output of a configuration that would return an error code of 2 to a script.

/usr/symmapps/vcm fcomparefcompare , fcompare , Copyright EMC Corp. 1998-1999New RawDevice Name was not there when fconfig was run New RawDevice Name is /dev/rdsk/c8t1d1 device 019 FA Symm 0182600765New RawDevice Name was not there when fconfig was run New RawDevice Name is /dev/rdsk/c8t1d2 device 01A FA Symm 0182600765New RawDevice Name was not there when fconfig was run New RawDevice Name is /dev/rdsk/c8t1d3 device 01B FA Symm 0182600765New RawDevice Name was not there when fconfig was run New RawDevice Name is /dev/rdsk/c8t1d4 device 01C FA Symm 0182600765New RawDevice Name was not there when fconfig was run New RawDevice Name is /dev/rdsk/c8t1d6 device 01E FA Symm 0182600765New RawDevice Name was not there when fconfig was run New RawDevice Name is /dev/rdsk/c8t1d7 device 01F FA Symm 0182600765fcompare completed please check status

Screen output of a configuration that would return an error code of 3 to a script.

fcompare Command Description 235

/usr/symmapps/vcm fcomparefcompare , fcompare , Copyright EMC Corp. 1998-1999, 01/21/1999Missing RawDevice Name. Preconfig /dev/rdsk/c8t1d6 was device 01E FA Symm 0182600765New RawDevice Name was not there when fconfig was run New RawDevice Name is /dev/rdsk/c8t1d5 device 01D FA Symm 0182600765fcompare completed please check status


A

Appendix A HEXADECIMAL CONVERSION

This appendix provides a chart for converting from the decimal to the hexadecimal numbering system.

• Hex to Decimal Conversion Chart ................... 238

237

A.1 Hex to Decimal Conversion ChartTable 22 shows the mapping between decimal and hexadecimal numbers.

Table 22. Hex to Decimal Conversion ChartDecimal 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

HexaDecimal 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

Decimal 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31


Decimal 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47


Decimal 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63


Decimal 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79


Decimal 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95


Decimal 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111


Decimal 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127


Decimal 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143


Decimal 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159


Decimal 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175

HexaDecimal A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF

Decimal 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191

HexaDecimal B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF

Decimal 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207

HexaDecimal C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF

Decimal 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223

HexaDecimal D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF

Decimal 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239

HexaDecimal E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF

Decimal 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255

HexaDecimal F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF

238 HEXADECIMAL CONVERSION

B

Appendix B VOLUME LOGIX WITH HP-UX

Here are some special considerations for using Volume Logix with HP-UX.

• Considerations .................................................... 240

239

B.1 ConsiderationsWhen using Volume Logix it is important to understand how HP-UX builds its device table. This information applies to servers based on the HSC bus (Parallel SCSI and Fibre Channel). The HSC base controller will start scanning at target 0 and continue sequentially up to the last target. For each target, the HSC base controller driver begins scanning for LUNs starting with 0 and going up to the point where it does not find a LUN in the sequence. If for any reason the driver does not find a LUN 0 or there is a break in the sequence of LUNs, the driver will not detect the remaining LUNs. This is not a defect. It is just a fact of how the driver was designed.

Example: HP-UXwith HSC-based

controller

The Symmetrix has an FA port configured as Target 3 and has LUNs 0-7 assigned to it. Using Volume Logix, the HBA attached to the FA is not allowed to access LUN 3. The result is that on the next boot, the HBA will only be able to communicate with target 3 LUNs 0-2 although it is allowed to access LUNs 4-7 from a Volume Logix viewpoint. One must also take into account LUN 3. If another host is only allowed access to LUN 3, it will not be able to build an entry for it for the same reason stated above.

Table 23. Original configuration on Symmetrix using a single FA port

Device Target LUN

34 3 0

35 3 1

36 3 2

37 3 3

38 3 4

240 VOLUME LOGIX WITH HP-UX

B

Possible Solution: There may be several ways to solve this situation. One recommendation is to use the modify feature in Symmetrix Dynamic Device Reallocation (SDDR). Leave LUNs 0-2 under target 3. Re-identify target 3 LUNs 4-7 under another target; for example change them to target 1 and LUNs 0-4 the devices can then be scanned. If another host is only allowed access to target 3 LUN 3, the same work around can be used by making the device target 0 LUN 0.

39 3 5

40 3 6

41 3 7

Table 24. New configuration on Symmetrix using a single FA port

Device Target LUN

34 3 0

35 3 1

36 3 2

37 0 0

38 1 0

39 1 1

40 1 2

41 1 3

Table 23. Original configuration on Symmetrix using a single FA port

Device Target LUN

Considerations 241

242 VOLUME LOGIX WITH HP-UX

Glossary

G

This glossary contains terms related to disk storage subsystems. Many of these terms are used in this manual.

AAWWN ASCII World Wide Name. An alias created by

Volume Logix for use in place of the 64-bit World Wide Name. See also WWN.

CCA Channel Adapter. See Parallel Channel Director.

Cache Random access electronic storage used to retain frequently used data from disk for faster access by the channel.

Channel Director The component in the Symmetrix subsystem that interfaces between the host channels and data storage. It transfers data between the channel and cache.

CLI Command Line Interface.

DDA Disk Adapter. See Disk Director.

Destage The asynchronous write of new or updated data from cache to disk device.

Device A uniquely addressable part of the Symmetrix subsystem that consists of a set of access arms, the associated disk surfaces, and the electronic circuitry

243

required to locate, read, and write data. See also Volume.

Device Address The hexadecimal value that uniquely defines a physical I/O device on a channel path. A SCSI address consists of a Target ID and a Logical Unit Number (LUN).

Device Number The value that logically identifies a disk device in a string.

Diagnostics System level tests or firmware designed to inspect, detect, and correct failing components. These tests are comprehensive and self-invoking.

Director The component in the Symmetrix subsystem that allows Symmetrix to transfer data between the host channels and disk devices. See also Channel Director and Disk Director.

Disk Director The component in the Symmetrix subsystem that interfaces between cache and the disk devices.

Dynamic Sparing A Symmetrix feature that automatically transfers data from a failing disk device to an available spare disk device without affecting data availability. This feature supports all non-mirrored devices in the Symmetrix subsystem.

EEA ESCON Adapter. See Serial Channel Director.

FFA The Fibre Channel Director/Interface Adapter

combination in the Symmetrix subsystem.

Fabric One or more switching devices that interconnect Fibre Channel N_Ports, and route Fibre Channel frames based on destination IDs in the frame headers. See also Fibre Channel Switch.

244 Glossary

G

Fast-Wide SCSIChannel Director

The component in the Symmetrix subsystem that interfaces between host SCSI channels and data storage. It transfers data between the channel and cache.

Fast Write In Symmetrix, a write operation at cache speed that does not require immediate transfer of data to disk. The data is written directly to cache and is available for later destaging.

FC Fibre Channel. See Fibre Channel Director.

Fibre Channel Director The component in the Symmetrix subsystem that interfaces between the host fibre channel interface and data storage. It transfers data between the channel and cache.

Fibre Channel Switch Fibre Channel Switch topology, or fabric, allows dynamic interconnections between nodes through ports connected to the fabric. A Fibre Channel switch creates a fibre channel fabric (FC-SW), while a hub provides an interconnect mechanism in an arbitrated loop (FC-AL).

GGatekeeper A Symmetrix volume accessible by the host via

which the Symmetrix Manager software communicates with the Symmetrix. Transfers the SCSI commands executed by the Symmetrix Manager to the Symmetrix.

Gigabyte (GB) 109 bytes.

HHBA Host Bus Adapter

Host Bus Adapter A card in the host device that provides a connection to a Fibre Channel loop.

Glossary 245

IIdentifier (ID) A sequence of bits or characters that identifies a

program, device, controller, or system.

IML Initial microcode program loading.

IPL Initial program loading.

I/O Device An addressable input/output unit, such as a disk device.

KKilobyte (K) 1024 bytes.

LLocal Volume A Symmetrix logical volume that is not participating

in SRDF operations. All CPUs attached to the Symmetrix may access for read/write operations. It is available for local mirroring or dynamic sparing operations to the Symmetrix unit in which it resides only.

Logical Volume A user-addressable unit of storage. In the Symmetrix subsystem, the user can define multiple logical volumes on a single physical disk device.

MMedia The disk surface on which data is stored.

Megabyte (MB) 106 bytes.

MII Machine Initiated Interrupt.

Mirroring The Symmetrix maintains two identical copies of a designated volume on separate disks. Each volume automatically updates during a write operation. If one disk device fails, Symmetrix automatically uses the other disk device.

246 Glossary

G

Mirrored Pair A logical volume comprised of two physical devices with all data recorded twice, once on each device.

Multi-initiator A topology in which multiple hosts are connected to a single Symmetrix port.

PParallel Channel

DirectorThe component in the Symmetrix subsystem that interfaces between mainframe host bus & tag channels and data storage. It transfers data between the channel and cache.

Promotion The process of moving data from a track on the disk device to cache. See also Stage.

PTF Program Temporary Fix.

RR1 See Source Volume.

R2 See Target Volume.

RA RLD Adapter. See Remote Link Director.

RAID Redundant Array of Independent Disks.

Read Hit Data requested by the read operation is in cache.

Read Hit Ratio Percentage of read hits out of all read requests.

Read Miss Data requested by the read operation is not in cache.

Remote Link Director The Remote Link Director (RLD) is a 2-port serial channel director microcode-configured as the link between the two Symmetrix units in a Symmetrix Remote Data Facility (SRDF) configuration.

RLD Remote Link Director. See Remote Link Director.

Glossary 247

SSA SCSI Adapter. See Fast-Wide SCSI Channel Director

and Ultra SCSI Channel Director.

Serial ChannelDirector

The component in the Symmetrix subsystem that interfaces between mainframe serial channels (ESCON) and data storage. It transfers data between the channel and cache.

Source Volume (R1) A Symmetrix logical volume that is participating in SRDF operations. It resides in the “local” Symmetrix unit. All CPUs attached to the Symmetrix may access a source volume for read/write operations. All writes to this volume are mirrored to a remote Symmetrix unit. A source volume is not available for local mirroring or dynamic sparing operations.

SRDF Symmetrix Remote Data Facility. SRDF consists of the microcode and hardware required to support Symmetrix remote mirroring.

Stage The process of writing data from a disk device to cache. See also Promotion, Destage.

Storage Control Unit The component in the Symmetrix subsystem that connects Symmetrix to the host channels. It performs channel commands and communicates with the disk adapters and cache. See also Channel Director.

TTarget Volume (R2) A Symmetrix logical volume that is participating in

SRDF operations. It resides in the “remote” Symmetrix unit. It is paired with a source volume in the local Symmetrix unit and receives all write data from its mirrored pair. This volume is not accessed by user applications during normal I/O operations. A target volume is not available for local mirroring or dynamic sparing operations.

Throughput Data transfer rate.

248 Glossary

G

TimeFinder A business continuance solution which allows customers to use special devices (BCVs) that contain copies of Symmetrix devices while the standard devices are online for regular Symmetrix operation. A software product formerly known as Symmetrix Multiple Mirror Facility (SMMF).

UUltra SCSI Channel

DirectorThe component in the Symmetrix subsystem that interfaces between host Ultra SCSI channels and data storage. It transfers data between the channel and cache.

VVCM Volume Configuration Management. See also Volume

Logix.

VCMDB See Volume Logix database.

Volume A general term referring to a storage device. In the Symmetrix subsystem, a volume corresponds to single disk device visible to the host.

Volume Logix An access control mechanism for Symmetrix that regulates which host HBAs in a Fibre Channel environment can access specific Symmetrix volumes.

Volume LogixAdministrator

A Java-based graphical user interface providing Volume Logix functions.

Volume Logixdatabase

A Symmetrix device used by Volume Logix as a database storing access control information.

Glossary 249

WWrite Hit There is room in cache for the data presented by the

write operation.

Write Miss There is no room in cache for the data presented by the write operation. Symmetrix will disconnect from the channel and reconnect when space is available.

Write Ratio Percentage of write requests out of all I/Os.

WWN World Wide Name uniquely identifying a connection to the Fibre Channel environment. A 64-bit value expressed as a sequence of eight hexadecimal values separated by periods.

250 Glossary

Index

I

AAbout Volume Logix option 55Actions menu 55Activate configuration option 109Activating the configuration 75, 85,

109Adapter number 223adddev action 161, 167, 176, 178Administrator host station 10ASCII WWN (AWWN) 223, 243

assigning 220changing 186listing 196, 220

Assigning volumes 75, 80, 126, 128, 182

BBacking up VCMDB 114, 185backupdb action 162, 168, 177,

182, 185Binding 228Boot time tasks 34Bus option 55

CChange Password option 54, 73chgname action 178, 186clrwwn action 178, 189Configuring access control 74Conventions xiiiCreating a Volume Logix database

176

DDeleting a WWN 189

Details button 56Details view 61Devices

adding 161, 167, 176name binding 228naming process 226relationship to FAs 205removing 210

EEdit menu 54Environment variable

PATH 33VCMDBDEVICE 31VLOGIX_DATA 29, 231

ESN Topology View 56Exit option 54

FFA port 58, 117

report 150viewing 117viewing properties 117

fcompare 34, 36, 229, 233fconfig 229, 231Fibre Adapter (FA) 4, 244Fibre Channel 4, 9, 245File Menu 54First time use 41

251

fpathsyntax 158, 181action (none) 181action summary 159adddev 161, 167, 176, 178backupdb 162, 168, 177, 182,

185chgname 178, 186clrwwn 178, 189initdb 161, 167, 176, 193lsbackup 195lsdb 196lshbawwn 160, 164, 172, 199lshostdev 39, 160, 164, 172,

200lshosts 160, 165, 174, 202lsstatus 204lssymmdev 160, 165, 175, 205lssymmfas 207refresh 162, 168, 177, 208restoredb 209return code 215rmdev 178, 210swaphba 178, 213

HHBA 58, 137

assigning volumes 126clearing access rights 143properties 137releasing volumes 130renaming 141report 150swapping access rights 145viewing 138

Help button 56Help Contents option 55Help menu 55Hexadecimal conversion chart 238

Host 133 58

assigning volumes 128name 223properties 133releasing volumes 131renaming 135report 150unnamed 45viewing 134

Host Bus Adapter (HBA) 245Host Bus Adapter (HBA), See HBA

IIcons button 56Icons view 60Icons/Details option 54initdb action 161, 167, 176, 193Initialize database dialog 79, 112Initializing a VCMDB 74, 78, 112,

161, 167Initializing the GUI 41inittab file 36Installation

check 38CLI only 20client stations only 22uninstalling 25Unix 18Windows NT 15

JJava 10JRE 10

LLines in Topology view 58

252 Index

I

Listingdevice names 200FAs/devices 205Login History table 202VCMDB contents 196VCMDB name 160, 164, 172,

200WWNs of host HBAs 160, 199

Login History table 5, 165, 202, 223

lsbackup action 195lsdb action 196lshbawwn action 160, 164, 172,

199lshostdev action 160, 164, 172, 200lshosts action 160, 165, 174, 202lsstatus action 204lssymmdev action 160, 165, 175,

205lssymmfas action 207

MMenu bar 54Microcode version 8

NName binding 228

PPATH environment variable 33Privileges required 66, 158Properties button 56Properties of objects 51Properties option 54

RRecording name bindings 231refresh action 162, 168, 177, 208Refresh Display 54, 93Refresh Display button 56

ReportFA port 150HBA 150host 150Symmetrix 150volume 150

restoredb action 209Restoring the VCMDB 114, 116rmdev action 178, 210Run Tasks button 56Run Tasks option 54

SSettings option 55Shell script 235Simple case study 77Starting Volume Logix

Administrator 66Status bar 63swaphba action 178, 213Symmetrix 58, 111

report 150viewing properties 111

Symmetrix option 55

TTask list 93

omitting tasks 102restoring tasks 103running all tasks 96

Task listLrunning selected tasks 99Tasks option 54Tool bar 56Topology view

lines 58

VVCM database

restoring from backup 116, 209VCMDBDEVICE environment

variable 31vcmfind 34, 36, 158, 159, 160,

173, 220return code 222

Index 253

Verifying name bindings 233View menu 54Viewing

FA port report 150FA ports 117HBA report 150HBAs 138, 140host properties 133host report 150hosts 134Symmetrix properties 111Symmetrix report 150volume properties 120volume report 150

Viewing FA port properties 117Viewing HBA properties 137Virtual channel 3VLOGIX_DATA environment

variable 29, 231Volume

assigning to HBA 126assigning to hosts 128properties 120releasing from HBAs 130releasing from hosts 131states 120types 119

Volume configuration management (VCM) 2

Volume Logix 2, 249components 6on/off 8, 204

Volume Logix Administrator 50demo 78icons 50main window 52menu bar 54starting 66starting first time 41status bar 63tool bar 56topology view 56volumes view 60

Volume Logix database 5adding devices 161, 167, 176assigning volumes 126, 128backing up 114, 162, 168,

177, 182, 185clearing 193creating 176deleting a WWN 189designating db_device 8initializing 78, 112, 161, 167,

193listing contents 196listing device names 200listing VCMDB name 200refresh 162, 168, 177releasing volumes 130, 131restoring 114, 116size 9

Volume option 55Volume report 150Volumes view 60

WWorld Wide Name (WWN) 4

deleting 189listing HBAs allowed access 196listing HBAs on host 160, 164,

172, 173, 199, 220swapping 213

254 Index

Sales and Service Locations

CorporateHeadquarters

EMC CorporationHopkinton, Massachusetts01748-9103 U.S.A.508-435-10001-800-424-EMC2

Asia PacificHeadquarters

EMC Japan K.K.P.O. Box 323Shinjuku-Mitsui Bldg., 551-1, Nishi-Shinjuku2-chome Shinjuku-kuTokyo 163-0466 JAPANTel: 81-3-3345-3211Fax: 81-3-3345-3221

North AmericanSales and Service

Locations

Atlanta, GA 404-705-4750Baltimore, MD 410-850-4324Bellevue, WA 425-201-6400Bethesda, MD 301-530-0091Boston, MA 617-449-8100Charlotte, NC 704-521-9773Chicago, IL 708-390-8800Cincinnati, OH 513-745-0300Cleveland, OH 216-573-1162Columbus, OH 614-436-3900Dallas, TX 972-233-5676Denver, CO 303-294-9966Farmington Hills, Ml 313-553-4810Ft. Lauderdale, FL 305-776-3622Greensboro, NC 910-665-1077Houston, TX 713-621-9800Indianapolis, IN 317-577-9766Inglewood, CA 310-364-1222

255

Irvine, CA 714-833-1442Lenexa, KS 913-469-9292Long Island, NY 516-393-5045Minneapolis, MN 612-835-1994Montreal, Quebec 514-856-6166Nashville, TN 615-781-4394New York City, NY 212-564-6866Ottawa, Ontario 613-233-0111Orlando, FL 407-855-4087Phoenix, AZ 602-955-0702Philadelphia, PA 610-834-7740Pittsburgh, PA 412-922-5222Portland, OR 503-293-8450Raleigh, NC 919-420-0405Rochester, NY 716-387-0970Salt Lake City, UT 801-532-1454San Diego, CA 619-576-1880San Francisco, CA 415-871-1970Southington, CT 860-620-6730Springfield, NJ 201-467-7979St. Louis, MO 314-469-9005Tampa, FL 813-282-0274Toronto, Ontario 905-206-1580Tulsa, OK 918-663-2255Vancouver, BC 604-270-1657Vienna, VA 703-893-8400

International SalesLocations

Berlin, Germany (49) 30 25 49 31 86Bologna, Italy (39) 51 522579Brescia, Italy (39) 30 2421791Brussels, Belgium (32) 2 725 74 25Cape Town, South Africa (27) 21 686 1430Dublin, Ireland (353) 1 475 4172Durban, South Africa (27) 31 83 6611Dusseldorf, Germany (49) 2131 9191 0Frankfurt, Germany (49) 6196 4 72 80Hamburg, Germany (49) 4069 69 610Hong Kong, Taikooshing (852) 2839 9600Johannesburg, South Africa (27) 11 807 5300Leatherhead, Surrey, UK (44) 1372 36 0000Lyon, France (33) 7 860 1330

256 Sales and Service Locations

Marseille, France (33) 4292 2549Melbourne, Australia (61) 3 653 9519Milan, Italy (39) 02 409081Munich, Germany (49) 89 14 31 320Nagoya, Japan (81) 52 223 1900Newton Le Willows, Merseyside, UK

(44) 1942 275 511Nieuwegein, Netherlands (31) 03 6055777Nuernberg, Germany (49) 911 2379260Osaka, Japan (81) 6 373 8300Padua, Italy (39) 49 8235853Paris, France (33) 1 3082 5100Pretoria, South Africa (27) 12 663 6635Rome, Italy (39) 06 8552116Schlieren, Switzerland (411) 743 4949Seoul, Korea (82) 2 539 4455Singapore (65) 338 9265Stuttgart, Germany (49) 7152 979340Sydney, Australia (61) 2 922 7888Toulouse, France (33) 6131 6262Turin, Italy (39) 11 746527Vienna, Austria (43) 1 599 99 627

Sales and Service Locations 257

258 Sales and Service Locations

Reader’s Comment Form

Your suggestions will help us continue to improve the accuracy, organization, and overall quality of our user publications. Please use this form, or email us at [email protected], to let us know your impression of this manual.

Manual Title: _______________________________________________________Document Number:_________________________Revision:____________________

What is your general reaction to this manual?

What parts of the manual do you use most?1.______________________________ 2. ____________________________3.______________________________ 4. ____________________________

What errors have you found?____________________________________________________________________________________________________________________________________________________________________________________________________________

Additional comments or suggestions:____________________________________________________________________________________________________________________________________________________________________________________________________________

Name: ______________________________________________________________Telephone Number: __________________________________________________Company: __________________________________________________________Address: ________________________________________________________________________________________________________________________________Country: ____________________________________________________________

Accuracy

Completeness

Usability

excellent

excellent

excellent

very good

very good

very good

good

good

good

fair

fair

fair

poor

poor

poor

|||||||||||||||||||||

Fold and Tape Please do not Staple Fold and Tape |------------------------------------------------------------------------------------------------------------

|||||||

Technical Publications |EMC Corporation |171 South Street |Hopkinton, MA 01748-9103 |

||||||||||

Documents

20414 Volume Logix Product Guide 2.1