20999642 Fc Director

EMC Enterprise Storage

SymmetrixFibre Channel

PRODUCT GUIDEP/N 200-999-642

REV C

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

ii

Symmetrix Fibre Channel Product Guide

Copyright © 1999 EMC Corporation. All rights reserved.Printed September 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, expressed 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 MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. In no event shall 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 InformationEMC2 (the EMC logo), EMC, ICDA, MOSAIC:2000, and Symmetrix are registered trademarks, and EMC Enterprise Storage, EMC Storage Logic, Celerra, CopyPoint, DataReach, Extended-Online, FarPoint, InfoMover, PowerPath, SDMS, SRDF, TimeFinder, The EMC Effect, and The Enterprise Storage Company are trademarks of EMC Corporation.

IBM, ESCON, AIX, and Netfinity are registered trademarks of International Business Machines, Inc.Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation.UNIX is a registered trademark in the United States and other countries and is licensed exclusively through X/Open Company Ltd.Sun and Ultra are trademarks of Sun Microsystems, Inc.HP, HP-UX, and SureStore are registered trademarks of Hewlett-Packard Company.SPARC and UltraSPARC are trademarks of SPARC International, Inc., licensed exclusively to Sun Microsystems, Inc.Intel is a registered trademark of Intel Corporation.Compaq is a registered trademark, and Proliant is a trademark, of Compaq Computer Corporation.Dell and PowerEdge are registered trademarks of Dell Computer Corporation.Silicon Graphics, Challenge, and IRIX are registered trademarks of Silicon Graphics, Inc.DG and AViiON are registered trademarks of Data General Corporation.Novell and NetWare are registered trademarks of Novell, Inc.Siemens is a registered trademark of Siemens Nixdorf Information Systems.Express 5800 is a trademark of NEC Corporation.WorldMark is a trademark of NCR Corporation.

All other trademarks used herein are the property of their respective owners.


Contents

Preface .............................................................................................................................xv

Part 1 Introduction to Symmetrix Fibre Channel

Chapter 1 Symmetrix Fibre Channel OverviewIntroduction.......................................................................................1-2

What is Fibre Channel?.............................................................1-2Fibre Channel Topologies.........................................................1-2Symmetrix and Fibre Channel.................................................1-3

Configuration Examples..................................................................1-4Connectivity Equipment..................................................................1-7

Hubs and Switches ....................................................................1-7Muxes ..........................................................................................1-7

Supported Hosts ...............................................................................1-8Where to Find Host-Specific Information............................1-19

Fibre Channel Port Types ..............................................................1-20Fibre Channel Topologies ..............................................................1-21

Arbitrated Loop Topology .....................................................1-21Fabric Topology .......................................................................1-23Hubs vs. Switches....................................................................1-23

Connectivity Topologies ................................................................1-25Distance Topology ...................................................................1-25Capacity Topology...................................................................1-27Consolidation Topology .........................................................1-30Combined Topologies .............................................................1-33

Symmetrix Fibre Channel Hardware...........................................1-35Fibre Channel Director............................................................1-35Cables ........................................................................................1-38

Contents iii

Contents

Part 2 Host Support on Arbitrated Loop

Chapter 2 HP 9000 Host on Arbitrated LoopHP Arbitrated Loop Environment .................................................2-2Host Connectivity.............................................................................2-3Symmetrix Configuration................................................................2-4Host Configuration...........................................................................2-5

Installing an HBA ......................................................................2-5Incorporating Symmetrix Fibre Channel ...............................2-5

HP 9000 Fibre Channel Hubs..........................................................2-6HP Hub Support........................................................................2-6Hub Configuration Guidelines................................................2-6

HP 9000 Fibre Channel Mux ...........................................................2-8Connection Example .................................................................2-8Supported Models .....................................................................2-8Configuration Guidelines.........................................................2-8

Chapter 3 Sun Solaris Host on Arbitrated LoopSolaris Arbitrated Loop Environment ...........................................3-2Host Connectivity.............................................................................3-3Symmetrix Configuration................................................................3-4Host Configuration with Jaycor HBA ...........................................3-5

Installing the HBA.....................................................................3-5Installing the HBA Driver ........................................................3-5Incorporating Symmetrix .........................................................3-9Partitioning and Labeling New Devices ..............................3-14Migrating to Fibre Channel....................................................3-14

Host Configuration with Qlogic HBA.........................................3-15Installing the HBA...................................................................3-15Installing the HBA Driver ......................................................3-15Incorporating Symmetrix Fibre Channel .............................3-18Partitioning and Labeling Devices........................................3-24Migrating to Fibre Channel....................................................3-24

Host Configuration with Emulex HBA .......................................3-25Installing the HBA...................................................................3-25Installing the HBA I/O Driver ..............................................3-26Incorporating Symmetrix Fibre Channel .............................3-28Partitioning and Labeling Devices........................................3-36Migrating to Fibre Channel....................................................3-36

Partitioning and Labeling New Devices .....................................3-37Sun Hub Configuration Guidelines .............................................3-38

Symmetrix Fibre Channel Product Guideiv

Contents

Sun Hub Support .................................................................... 3-38Sun Hub Configuration Guidelines ..................................... 3-38

Chapter 4 Windows NT Host on Arbitrated LoopWindows NT Arbitrated Loop Environment............................... 4-2Host Connectivity ............................................................................ 4-3Symmetrix Configuration ............................................................... 4-6Host Operating System Configuration ......................................... 4-7Host Configuration with Compaq HBA....................................... 4-8

Installing the HBA .................................................................... 4-8Installing the HBA Driver........................................................ 4-8Incorporating Symmetrix Fibre Channel............................... 4-9

Host Configuration with HP A5246A HBA ............................... 4-10Installing the HBA .................................................................. 4-10Installing the HBA Driver...................................................... 4-10Incorporating Symmetrix Fibre Channel............................. 4-11

Host Configuration with HP D8602A (Tachlite) HBA.............. 4-12Installing the HBA .................................................................. 4-12Installing the HBA Driver...................................................... 4-12Registry Settings...................................................................... 4-13Incorporating Symmetrix Fibre Channel............................. 4-14

Host Configuration with Qlogic HBAs....................................... 4-16Installing the HBA .................................................................. 4-16EMC NVRAM Settings........................................................... 4-16Configuring the HBA ............................................................. 4-17Installing the HBA Driver...................................................... 4-19Modifications for Service Pack 4 or 5 ................................... 4-20Incorporating Symmetrix Fibre Channel............................. 4-20

Host Configuration with Emulex HBAs..................................... 4-22Installing the HBA .................................................................. 4-22Updating the Flash Firmware/BIOS.................................... 4-23Installing the HBA Driver...................................................... 4-24Changing the Registry............................................................ 4-26Using the Emulex Configuration Tool ................................. 4-26Incorporating Symmetrix Fibre Channel............................. 4-28

Chapter 5 SGI Challenge Host on Arbitrated LoopSGI Challenge Fibre Channel Environment ................................. 5-2Host Connectivity ............................................................................ 5-3Symmetrix Configuration ............................................................... 5-4Host Configuration with Prisa HBA ............................................. 5-5

vContents

Contents

Installing NetFX Software ........................................................5-5Installing an HBA ......................................................................5-6Configuring and Enabling Software Files..............................5-6Incorporating Symmetrix Fibre Channel .............................5-15

Chapter 6 SGI Origin Host on Arbitrated LoopSGI Origin Fibre Channel Environment........................................6-2Host Connectivity.............................................................................6-3Symmetrix Configuration................................................................6-4Incorporating Symmetrix ................................................................6-5

Partitioning and Labeling the Devices ...................................6-6Tag Command Queuing Enabled............................................6-7

Adding Devices On Line .................................................................6-8

Chapter 7 AIX Host on Arbitrated LoopAIX Fibre Channel Environment....................................................7-2Host Connectivity.............................................................................7-3Symmetrix Configuration................................................................7-4Host Configuration with Emulex HBA .........................................7-5AIX Hub Configuration Guidelines...............................................7-6

AIX Hub Support ......................................................................7-6AIX Hub Configuration Guidelines........................................7-6

Chapter 8 Siemens/Reliant UNIX Host on Arbitrated LoopSiemens Fibre Channel Environment ............................................8-2Host Connectivity.............................................................................8-3Symmetrix Configuration................................................................8-4Host Configuration with Siemens HBA........................................8-5

Installing the RAID Software...................................................8-5Installing an HBA ......................................................................8-6Incorporating Symmetrix Fibre Channel ...............................8-7

Siemens Hub Configuration Guidelines ..................................... 8-11Siemens Hub Support ............................................................. 8-11Siemens Hub Configuration Guidelines .............................. 8-11

Chapter 9 Netware Host on Arbitrated LoopNetWare Arbitrated Loop Environment .......................................9-2Host Connectivity.............................................................................9-3Symmetrix Configuration................................................................9-4Host Configuration with Qlogic QLA2100F-EMC HBA.............9-5

Symmetrix Fibre Channel Product Guidevi

Contents

Prepare the Adapter(s) ............................................................. 9-5Installing the HBA .................................................................... 9-6Upgrading QLA2100F BIOS .................................................... 9-7Configuring an HBA ................................................................ 9-8Installing the HBA Driver...................................................... 9-10Incorporating Symmetrix Fibre Channel............................. 9-11

Hub Connection Guidelines ......................................................... 9-12

Chapter 10 Solaris X86 Host on Arbitrated LoopSolaris X86 Arbitrated Loop Environment ................................. 10-2Host Connectivity .......................................................................... 10-3Symmetrix Configuration ............................................................. 10-4Host Configuration with Qlogic QLA2100F-EMC HBA .......... 10-5

Setup Checklist ........................................................................ 10-5Installing the HBA .................................................................. 10-7Configuring Firmware Settings ............................................ 10-7Verifying the Disk Media ....................................................... 10-8Upgrading HBA Firmware.................................................... 10-9Installing the HBA Driver.................................................... 10-10Editing Host Files.................................................................. 10-12

Partitioning and Labeling a New Device.................................. 10-19Disk Device File Naming Conventions.............................. 10-19Partitioning and Slicing Symmetrix Devices .................... 10-19

Creating and Mounting a UFS File System .............................. 10-23Create a New File System .................................................... 10-23Create a Mount Directory .................................................... 10-23Mount the Filesystem ........................................................... 10-23

Adding Devices On Line............................................................. 10-24Solaris X86 Hub Configuration Guidelines.............................. 10-25

Part 3 Host Support on Fabric

Chapter 11 Solaris SPARC Host on FabricSolaris Fibre Channel Environment............................................. 11-2Host Connectivity .......................................................................... 11-3Symmetrix Configuration ............................................................. 11-4Host Configuration with Jaycor HBA ......................................... 11-5

Planning Zoning and Connections....................................... 11-5Installing the HBA .................................................................. 11-5Installing the HBA Driver...................................................... 11-6Incorporating Symmetrix Fibre Channel............................11-11

viiContents

Contents

Migrating to Fibre Channel.................................................. 11-21Dynamic Reconfiguration in the Ultra Enterprise 10000 ........ 11-22

Chapter 12 Windows NT Host on FabricWindows NT Fibre Channel Environment .................................12-2Host Connectivity...........................................................................12-3Symmetrix Configuration..............................................................12-5Host Operating System Configuration........................................12-6Planning for Zoning and Connections ........................................12-7

Understanding Persistent Binding........................................12-7Host Configuration with Qlogic HBA.........................................12-9

Installing the HBA...................................................................12-9EMC NVRAM Settings ...........................................................12-9Configuring the HBA............................................................12-10Installing the HBA Driver ....................................................12-12Incorporating Symmetrix Fibre Channel ...........................12-13

Host Configuration with Emulex HBAs ...................................12-14Installing the HBA.................................................................12-14Updating the Flash Firmware/BIOS ..................................12-15Installing the HBA Driver ....................................................12-16Changing the Registry ..........................................................12-17Using the Emulex Configuration Tool................................12-18Incorporating Symmetrix Fibre Channel ...........................12-20

Part 4 Appendixes and Back Matter

Appendix A Specifications

Appendix B Migrating from SCSI to Fibre ChannelIntroduction ..................................................................................... B-2Running Inquiry ............................................................................. B-3

Connecting to EMC’s FTP Server ........................................... B-4Migrating in Specific Host Environments ................................... B-5

Sun Veritas VxVM Environment ............................................ B-5Sun Solstice DiskSuite Environment ..................................... B-5HP LVM Environment ............................................................. B-6SGI Challenge Environment ................................................... B-6

EMC Migration Scripts .................................................................. B-8emc_s2f....................................................................................... B-8emc_s2f_hp .............................................................................. B-10

Symmetrix Fibre Channel Product Guideviii

Contents

Appendix C Addressing Symmetrix DevicesArbitrated Loop Addressing ........................................................ C-2Fabric Addressing .......................................................................... C-4SCSI-3 FCP Addressing ................................................................. C-5

Glossary

Sales and Service Locations

Index

ixContents

Contents

Symmetrix Fibre Channel Product Guidex

Figures and Tables

Figures1-1 Fibre Channel Port Types .......................................................................... 1-201-2 Hubless Loop .............................................................................................. 1-211-3 Loop with Hub ............................................................................................ 1-221-4 Loop vs. Fabric Data Flow ......................................................................... 1-241-5 FC-AL Distance Topology Example ........................................................ 1-261-6 FC-AL High-Availability Distance Topology Example ........................ 1-261-7 FC-SW Distance Topology Example ........................................................ 1-271-8 FC-AL Capacity Expansion Topology Example .................................... 1-281-9 FC-AL High-Availability Capacity Expansion Topology Example .... 1-281-10 FC-SW Capacity Expansion (Fan-in) Topology ..................................... 1-291-11 FC-AL Consolidation Topology Example .............................................. 1-301-12 FC-AL High-Availability Consolidation Topology Example .............. 1-311-13 FC-SW Consolidation (Fan-out) Topology Example ............................. 1-321-14 FC-AL Combined Hub Topologies Example ......................................... 1-331-15 FC-SW Combined Topologies Example .................................................. 1-341-16 Fibre Channel Director .............................................................................. 1-361-17 Symmetrix Director Locations .................................................................. 1-382-1 Hub Cabling Recommendation .................................................................. 2-72-2 HP Fibre Channel Mux ................................................................................ 2-83-1 LP7000E-EMC Jumpers ............................................................................. 3-254-1 LP7000E-EMC and LP8000-EMC Jumpers ............................................. 4-224-2 Emulex Configuration Tool Window ...................................................... 4-275-1 SGI IO 4 Card with NetFX-HIO64 ............................................................. 5-69-1 QLA2100F-EMC Banner Example .............................................................. 9-710-1 QLA2100F-EMC Banner Example ............................................................ 10-710-2 Solaris X86 fdisk Menu Example ............................................................ 10-2111-1 Fabric Switch Case Study ........................................................................ 11-1612-1 Recommended Connections Example ..................................................... 12-8

Figures xi

xii

Figures

12-2 LP7000E-EMC and LP8000-EMC Jumpers ............................................ 12-1412-3 Emulex Configuration Tools and Settings for Fabric .......................... 12-18B-1 Sample Inquiry Display ............................................................................... B-3


Tables

Tables1-1 Fibre Channel Support on Symmetrix ....................................................... 1-31-2 Arbitrated Loop Support on UNIX-Based Hosts ..................................... 1-81-3 Arbitrated Loop Support on Windows-Based Hosts ............................ 1-101-4 Arbitrated Loop Support on NetWare-Based Hosts ............................. 1-151-5 Fabric Switch Support on UNIX Hosts ................................................... 1-151-6 Fabric Switch Support on Windows Hosts ............................................. 1-161-7 Fibre Channel Port Types .......................................................................... 1-201-8 Fibre Channel Hub/Switch Connectivity Topologies .......................... 1-251-9 Fibre Channel Directors and Ports ........................................................... 1-351-10 Operator Panel LEDs ................................................................................. 1-371-11 EMC Fibre Channel Cables ....................................................................... 1-392-1 HBAs for HP 9000 Hosts ............................................................................. 2-32-2 Symmetrix Configuration for HP Hosts ................................................... 2-43-1 HBAs for Solaris Hosts on Arbitrated Loop ............................................. 3-33-2 Symmetrix Configuration for Solaris Hosts on Arbitrated Loop .......... 3-43-3 Jaycor HBA Configuration File Parameters ............................................ 3-103-4 /kernel/drv/qla2100.conf Settings for Solaris SPARC Host ............... 3-193-5 /kernel/drv/lpfc.conf Settings for Solaris SPARC Host ..................... 3-294-1 HBAs for Windows NT/FC-AL Hosts ...................................................... 4-34-2 Symmetrix FC-AL Configuration for Windows NT Hosts .................... 4-64-3 Emulex Configuration Tool Settings for Arbitrated Loop ................... 4-285-1 HBAs for SGI Challenge Hosts ................................................................... 5-35-2 Symmetrix Configuration for SGI Challenge Hosts ................................ 5-46-1 HBAs for SGI Origin Hosts ......................................................................... 6-36-2 Symmetrix Configuration for SGI Origin Hosts ...................................... 6-47-1 HBAs for AIX Hosts ..................................................................................... 7-37-2 Symmetrix Configuration for AIX Hosts .................................................. 7-48-1 HBAs for Siemens Hosts ............................................................................. 8-38-2 Symmetrix Configuration for Siemens Hosts ........................................... 8-48-3 Reliant UNIX Fibre Channel Naming Conventions .............................. 8-109-1 HBAs for NetWare/FC-AL Hosts .............................................................. 9-39-2 Symmetrix FC-AL Configuration for NetWare Hosts ............................ 9-49-3 QLA2100F BIOS Settings ............................................................................. 9-810-1 HBAs for Solaris X86 Hosts on Arbitrated Loop ................................... 10-310-2 Symmetrix Configuration for Solaris X86 Hosts .................................... 10-410-3 /kernel/drv/qla2100.conf Settings for Solaris X86 Host ................... 10-1311-1 HBAs for Sun Hosts on Fabric .................................................................. 11-311-2 Symmetrix Configuration for Sun Hosts ................................................ 11-411-3 FC-SW Zoning and Connections .............................................................. 11-511-4 Jaycor HBA Configuration File Parameters .......................................... 11-1111-5 Case Study LUN Mapping ...................................................................... 11-16

Tables xiii

Tables

12-1 HBAs for Windows NT Hosts ................................................................... 12-312-2 Symmetrix Fabric Configuration for Windows NT Hosts .................... 12-512-3 Recommended Connections Example ..................................................... 12-812-4 Emulex Configuration Tool Settings for Fabric .................................... 12-19A-1 ANSI Fibre Channel Standards .................................................................. A-1C-1 FC-AL Addressing Parameters .................................................................. C-3C-2 Symmetrix SCSI-3 Addressing Modes ...................................................... C-6

xiv Symmetrix Fibre Channel Product Guide

Preface

As part of its effort to continuously improve and enhance the performance and capabilities of the Symmetrix product line, EMC periodically 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 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.

This manual describes the features and setup procedures for the Symmetrix Fibre Channel interface. The manual is intended for the storage administrator, system programmer, or operator involved in acquiring, managing, or operating the Symmetrix and host devices that contain the Fibre Channel interfaces.

Organization of thisManual

Here is an overview of where information is located in this manual.

• Chapter 1, Symmetrix Fibre Channel Overview — Highlights the major Symmetrix Fibre Channel features and provides an overview of its major components.

• Chapter 2, HP 9000 Host on Arbitrated Loop — Describes incorporating Symmetrix Fibre Channel into the HP arbitrated loop environment.

• Chapter 3, Sun Solaris Host on Arbitrated Loop — Describes incorporating Symmetrix Fibre Channel into the UNIX-based Solaris arbitrated loop environment.

• Chapter 4, Windows NT Host on Arbitrated Loop — Describes incorporating Symmetrix Fibre Channel into the Windows NT arbitrated loop environment.

Preface xv

xvi

Preface

• Chapter 5, SGI Challenge Host on Arbitrated Loop — Describes incorporating Symmetrix Fibre Channel into the SGI Challenge arbitrated loop environment.

• Chapter 6, SGI Origin Host on Arbitrated Loop — Describes incorporating Symmetrix Fibre Channel into the SGI Origin arbitrated loop environment.

• Chapter 7, AIX Host on Arbitrated Loop — Describes incorporating Symmetrix Fibre Channel into the AIX arbitrated loop environment.

• Chapter 8, Siemens/Reliant UNIX Host on Arbitrated Loop — Describes incorporating Symmetrix Fibre Channel into the Reliant UNIX arbitrated loop environment.

• Chapter 9, Netware Host on Arbitrated Loop — Describes incorporating Symmetrix Fibre Channel into the Novell Netware arbitrated loop environment.

• Chapter 10, Solaris X86 Host on Arbitrated Loop— Describes incorporating Symmetrix Fibre Channel into the Solaris X86 arbitrated loop environment.

• Chapter 11, Solaris SPARC Host on Fabric — Describes incorporating Symmetrix Fibre Channel into the Solaris fabric environment.

• Chapter 12, Windows NT Host on Fabric — Describes incorporating Symmetrix Fibre Channel into the Windows NT fabric environment.

• Appendix A, Specifications — Describes some basic hardware and software specifications that can be helpful in planning a configuration.

• Appendix B, Migrating from SCSI to Fibre Channel — Describes the procedure for upgrading from a SCSI Director to a Fibre Channel Director.

• Appendix C, Addressing Symmetrix Devices — Describes FC-AL, FC-SW, and SCSI-3 FCP addressing conventions

• Glossary— Defines some terms used in this manual.


Preface

RelatedDocumentation

Related EMC documents specific to the Fibre Channel fabric switch topology are:

• EMC Connectrix Enterprise Storage Network System Topology Guide (P/N 300-600-008)

• Enterprise Connectivity Cabinet Model EC-1000 Planning Guide (P/N 300-600-002)

• Enterprise Connectivity Cabinet Model EC-1000 User’s Guide (P/N 300-600-001)

• Enterprise Fibre Channel Director Model ED-1032 User’s Guide (P/N 300-600-004)

Some other related Symmetrix publications include:

• Symmetrix Model 3630/5630 Product Manual, P/N 300-857-002, EMC Corporation



• Symmetrix Open Systems Environment Product Guide (Volumes I & II), P/N 200-999-563, EMC Corporation

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

• EMC PowerPath Product Guide, P/N 200-999-598, EMC Corporation

• EMC Volume Logix Product Guide P/N 300-999-024, EMC Corporation

• EMC Fibre Channel Interface Version 1.0 for AIX Platforms Product Guide, P/N 300-999-038, EMC Corporation

Other documents that might be helpful include:

• Host-specific documentation, available from the manufacturer(s) of the host device(s)

• Fibre Channel standards, white papers, etc., from such sources as the Fibre Channel Association (www.fibrechannel.com)

Preface xvii

xviii

Preface

Conventions Used inthis Manual

This document uses the following text conventions:

• General text looks like this.

• User input, command names, and parameter names are bold.

• Screen output is in Courier font.

• File and path names are italicized.

Keyboard References

References to keyboard keys and entry are presented as follows:

• <N> is a reference to a key (where "N" is the key). References to keys are shown in uppercase, but usually it does not matter whether you use uppercase or lowercase when pressing a key.

• "Type xxx <Enter>" (for example) means type xxx, then press the <Enter> key.

• "Enter xxx" (for example) is similar to "Type xxx <Enter>," except that the key designation <Enter> is assumed, and therefore omitted.

• <Ctrl> or <Alt> followed by one or two other key designations (for example, "press <Alt><E>") means press the keys simultaneously.

If a sentence ends with a reference to a key (for example, "... then press <Enter>."), the period is not part of the information to be entered. If a period should be entered, it is shown in brackets (<.>) .

Notes, Cautions, and Warnings

EMC uses the following conventions for notes, cautions, and warnings.

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

CAUTION!A caution contains information essential to avoid a hazard that can cause minor personal or property damage if you ignore the message.


Preface

WARNING

A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the message.

DANGER

A danger notice contains information essential to avoid a hazard that will cause severe personal injury, death, or substantial property damage if you ignore the message.

Where to Get Help Obtain technical support by calling your local sales office.

For service, call:

(800) 782-4362 (SVC-4EMC)or(800) 543-4782 (543-4SVC)

and ask for Customer Service.

If you are located outside the USA, call the nearest EMC office for technical assistance. These offices are listed at the back of this manual.

Your Comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please e-mail us at [email protected] to let us know your opinion of this manual.

Preface xix

xx

Preface


Part 1

This section contains an overview of EMC’s Symmetrix Fibre Channel implementation. The contents of Part 1 are:

• Chapter 1, Symmetrix Fibre Channel Overview

Introduction toSymmetrix Fibre

Channel

1

This chapter provides an overview of the EMC® Symmetrix® Fibre Channel implementation. The chapter contains these sections:

• Introduction ........................................................................................1-2• Configuration Examples ...................................................................1-4• Connectivity Equipment ...................................................................1-7• Supported Hosts.................................................................................1-8• Fibre Channel Port Types................................................................1-20• Fibre Channel Topologies ...............................................................1-21• Connectivity Topologies .................................................................1-25• Symmetrix Fibre Channel Hardware ............................................1-35

Symmetrix FibreChannel Overview

Symmetrix Fibre Channel Overview 1-1

1

1-2

Symmetrix Fibre Channel Overview

IntroductionThis section provides a brief overview of Fibre Channel, and of the Symmetrix implementation of Fibre Channel.

What is Fibre Channel?

Fibre Channel is a serial data transfer interface that operates over copper wire and/or optical fiber at data rates up to 100 MB/second. Networking and I/O protocols (such as SCSI commands) are mapped to Fibre Channel constructs, then encapsulated and transported within Fibre Channel frames. This allows high-speed transfer of multiple protocols over the same fiber.

Communication is possible in full-duplex mode at rates up to 1062.5 megabaud. Physical connections are made via multimode optical fiber at distances up to 500 meters between devices. (Table 1-11 on page 1-39 lists the Fibre Channel cables available from EMC.)

Fibre Channel Topologies

ANSI Fibre Channel standards define three topologies used to interconnect various devices. These topolgies are described briefly below, and in greater detail under Fibre Channel Topologies on page 1-21.

Point-to-Point Point-to-point is a single connection between two devices. Symmetrix Fibre Channel does not support this topology as defined by ANSI standards.

Arbitrated Loop Fibre Channel arbitrated loop (FC-AL) is basically a "daisy-chain," interconnecting from two to 126 devices in a loop configuration, via attachment points called L_Ports. FC-AL is a low-cost solution because it does not require switching devices. FC-AL is a good choice for small to medium-sized configurations, and provides an upward growth path by allowing connection of the loop to a switched fabric.

Efficiency and connectivity of a loop environment is enhanced by incorporation into the loop of one or more hubs. Routing traffic through a hub on each leg of a loop eliminates the loss of the entire loop, as happens in a hubless loop.

Fabric The Fibre Channel fabric switch topology (FC-SW) is one or more switches dynamically interconnecting multiple nodes (Symmetrix and host devices, for example). FC-SW provides the interconnection effectiveness of a hub, and adds much greater performance and manageability.


1Symmetrix Fibre Channel Overview

Symmetrix and Fibre Channel

Symmetrix uses the SCSI protocol on its Fibre Channel interface; therefore, Fibre Channel interfaces and standard SCSI interfaces look the same to host devices. Each Symmetrix is recognized and addressed by controller number and logical unit number (LUN). Implementation of the Fibre Channel interface is handled at the host bus adapter (HBA) driver and hardware level, so configuration of devices at the host is the same for SCSI or Fibre Channel.

All qualified Fibre Channel HBAs have the same basic functionality; however, Symmetrix does not currently support configurations that combine different brands of Fibre Channel HBA in the same server.

Symmetrix devices accessed through the Fibre Channel cannot currently be used as boot devices.

CAUTION!Before upgrading from SCSI to Fibre Channel, make sure both the existing and new Symmetrix configurations are well documented.

Hardware andMicrocode Support

Fibre Channel is supported in Symmetrix as shown in Table 1-1.

Table 1-1 Fibre Channel Support on Symmetrix

Symmetrix Model Microcode Level FC-AL? FC-SW?

3330/5330 5264 Yes No

5265 Yes Yes

3430/5430 5264 Yes No

5265 Yes Yes

3700/5700 5264 Yes No

5265 Yes Yes

3630/5630 5265 Yes Yes

3830/5830 5265 Yes Yes

3930/5930 5265 Yes Yes

Introduction 1-3

1

1-4


Configuration ExamplesThis section contains some examples of Fibre Channel and SCSI configurations. Although not necessarily representative of actual customer installations, these types of configurations can be used in various combinations to create specific enterprise storage solutions.

Only HP® hosts running HP-UX® currently support device sharing between SCSI and Fibre Channel.

Example Characteristics

• Multiple Fibre Channel• No device sharing

• Multiple Fibre Channel• Device sharing between

channels• Typically used for channel

failover

• Multiple Fibre Channel• Multiple SCSI Channel• No device sharing between

Fibre and SCSI

• Multiple Fibre Channel• Multiple SCSI Channel• Device sharing between

Fibre and SCSI• Possible use: Support of old

SCSI cards as alternate channel, or for migration from SCSI to Fibre Channel




• Multiple Fibre Channel• Multiple SCSI Channel• No device sharing between

Fibre and SCSI• Separate volume groups

connected via Fibre and SCSI

• Device sharing between Fibre Channel links

• Device sharing between SCSI Channel links

• Multiple Fibre Channel• Shared devices between

Fibre Channels• Typical use: High

Availability with channel failover and clustering

• Multiple Fibre Channel• Multiple SCSI Channel• No sharing devices between

Fibre Channel and SCSI• Typical use: Partitioned

Symmetrix

Configuration Examples 1-5

1

1-6



• Multiple Fibre Channel• Multiple SCSI Channel• Device sharing between

Fibre and SCSI• High Availability with

channel failover and clustering

• Typical use: Online cluster upgrade, SCSI to Fibre Channel

• Multiple Fibre Channel• Multiple Symmetrix from a

single host

• Multiple Hosts• Multiple Symmetrix• Multiple Fibre Channel• Multiple Symmetrix from

multiple hosts• High Availability: Example:

PV Links channel failover, ServiceGuard cluster for HP-UX



Connectivity EquipmentFibre Channel connectivity equipment can be categorized by capability into hubs, switches, and multiplexers (muxes).

Hubs and Switches There are distinct differences between Fibre Channel hubs and switches. A switch creates a Fibre Channel fabric (FC-SW), while a hub provides an interconnect mechanism in an arbitrated loop (FC-AL).

The Fibre Channel switch topology allows dynamic interconnections between nodes through ports connected to the fabric.

A hub is limited to a total of 100 Megabytes of bandwidth that must be shared by all ports connected to the hub.

Symmetrix supports the use of Fibre Channel hubs in certain environments. These supported hosts types (see Supported Hosts on page 1-8) can connect to Fibre Channel hubs:

• HP hosts running HP-UX• Sun hosts running Solaris• Siemens hosts running Reliant UNIX v5.44B10 or higher

Muxes Routers, Muxes, and Bridges convert one connection technology to another. In Fibre Channel, these terms are generally interchangeable.

The HP Fibre Channel SCSI-MUX converts SCSI to Fibre Channel. This product will be used to provide Fibre Channel connectivity for older models of Symmetrix (3100/5100, 3200/5200, 3500/5500) that do not support Fibre Channel directors.

The HP Fibre Channel Mux is supported only in HP environments. Refer to HP 9000 Fibre Channel Mux on page 2-8.

Connectivity Equipment 1-7

1

1-8


Supported HostsTables 1-3 through 1-5 list the supported hosts and basic system requirements for Symmetrix Fibre Channel connectivity as of the current revision of this manual.

Contact your EMC representative for the latest support information, as updates are frequent. If you have access to EMC’s internal website, the latest support information can be found in this file ( where YYMMDD is the year, month, and day):

www.lss.emc.com/opensymm/hostmatrix/osYYMMDD.pdf

I/O driver software is required for all Fibre Channel adapter cards. (Each host-specific chapter has a section titled Host Connectivity, which identifies required driver software.)

Table 1-2 Arbitrated Loop Support on UNIX-Based Hosts

Host Modelsor Series Min. Operating System

Host Bus Adapters and Drivers

HP 9000 D-Class HP-UX 10.20 TFC HP A3591A or A3591B a

HP 9000 K-Class HP-UX 10.20 TFC HP 3404A a

HP 9000 N-Class HP-UX 11.00 HP 3740A a

HP 9000 R-Class HP-UX 10.20 TFC HP A3591A or A3591B a

HP 9000 T600 HP-UX 10.20 TFC HP A3636A a

HP 9000 V-Class HP-UX 11.00 HP 3740A a

Sun SPARC, UltraSPARC (Sbus)

Solaris 2.5.1 with EMC-approved OS patches

Jaycor FC-1063-EMC, rev H; driver 2.2.2.EMC plus any OS patches

Jaycor FC64-1063-EMC, rev B, C, D, or E; driver 2.2.2.EMC plus any OS patches

Jaycor FCIN-1063-EMC, rev B; driver 2.2.2.EMC

continued on next page — footnotes follow table



Sun Enterprise 250/450, Ultra 30/60, 3x00/4x00/ 5x00/6x00 (PCI bus)

Solaris 2.5.1 with EMC-approved OS patches

Jaycor FC-1063-EMC, rev H; driver 2.2.2.EMC plus any OS patches

Jaycor FC64-1063-EMC, rev B, C, D, or E; driver 2.2.2.EMC plus any OS patches


Solaris 2.6 with EMC-approved OS patches

Qlogic QLA2100F-EMC;BIOS version 1.37; driver version 2.20

Emulex LP7000E-EMC;Firmware version 2.20;driver version 3.38

NCR 4300/4400 Solaris X86 version 7 Qlogic QLA2100F-EMC;BIOS version 1.37; driver version 2.20

Siemens Nixdorf PRIMERGY 7xx

Solaris X86 version 7 Qlogic QLA2100F-EMC;BIOS version 1.37; driver version 2.20

SGI Challenge™ IRIX® 6.2 with patch 07/01/98

Prisa NetFX-HIO64;driver version 1.3 plus patches 28 and 29

SGI Origin™ 200 (PCI) IRIX 6.4.1 SGI PCI-FC-1P

SGI Origin 2000 (PCI) IRIX 6.4.1 SGI PCI-FC-1P

SGI Origin 2000 (XIO) IRIX 6.4.1 SGI XT-FC-2P

IBM® RS/6000® AIX® 4.3.0 Emulex LP7000E-EMC;driver LPP devices.pci.df10e51a and devices.pci.df1001f7


Table 1-2 Arbitrated Loop Support on UNIX-Based Hosts (continued)



Supported Hosts 1-9

1

1-10


a. The host I/O driver software for HP 9000-system adapters is included as part of the HP-UX operating system installation.

Bull Escala T series AIX 4.3.0 Emulex LP7000E-EMC;driver LPP devices.pci.df10e51a and devices.pci.df1001f7

Siemens RM300E Reliant UNIX® v5.44C Siemens RM300-CF02;Firmware version FW 2.12

Siemens RM400C/E Reliant UNIX v5.44C Siemens RM400-CF02;Firmware version FW 2.12

Siemens RM600E30/E70 Reliant UNIX v5.44C Siemens RM6T5-CF10;Firmware: LP6502 version 2.12 or LP8000 version 2.82

RM600E40/E80, RM600CS42

Reliant UNIX v5.45A Siemens RM6T5-CF10;Firmware: LP6502 version 2.12 or LP8000 version 2.82

Table 1-2 Arbitrated Loop Support on UNIX-Based Hosts (continued)



Table 1-3 Arbitrated Loop Support on Windows-Based Hosts



Compaq® Proliant 5000, 5500, 6000, 6500, 7000

Windows NT® 4.0, Service Pack 3, 4, or 5

Compaq FC (PCI) 223180-B21;driver version 4.04 a


Emulex LP8000-EMCFirmware version 2.82;Driver version 1.22




Compaq Proliant 5000, 5500, 6000, 6500, 7000 (continued)

Windows NT 4.0, Service Pack 3, 4, or 5


Dell® PowerEdge® 6100/6300

Windows NT 4.0,Service Pack 3, 4, or 5

Qlogic QLA2100F-EMC;BIOS version 1.37;driver version 6.16

Dell PowerEdge 6100/6300 (continued)


Qlogic QLA2200F-EMC; see note c




HP® Netserver LH, LH3, LH4, LH-II, LXr, LXr Pro8, LXr8000


HP A5246A a;driver version 2.09d a

HP D8602A b;driver version 1.12a





Table 1-3 Arbitrated Loop Support on Windows-Based Hosts (continued)



Supported Hosts 1-11

1

1-12


HP Netserver LH, LH3, LH4, LH-II, LXr, LXr Pro8, LXr8000 (continued)




IBM® Netfinity® 5000, 5500, 5500M10, 7000, 7000M10







NCR 4300, 4380, 4400 Windows NT 4.0,Service Pack 3, 4, or 5











NCR 4300, 4380, 4400 (continued)



Siemens PRIMERGY 7xx, 8xx







Unisys Aquanta QS/2V Windows NT 4.0,Service Pack 3, 4, or 5



Emulex LP7000E-EMC;Firmware version 2.20;Driver version 1.22








1

1-14


a. Does not yet support EMC PowerPath TM.

b. Supports PowerPath 1.5 only.

c. Contact your EMC representative for the latest Firmware/BIOS and Driver versions.

X

NEC Express 5800™/ 140 Ma




NEC Express 5800/140 Ma (continued)




Emulex LP7000E-EMC;Firmware version 2.20;Driver version 1.22








Table 1-4 Arbitrated Loop Support on NetWare-Based Hosts



Compaq Proliant 850, 1600, 1850, 2500, 3000, 5000, 5500, 6000, 6500, 7000

NetWare® 4.11 with support pack 6, or NetWare 5.00 with support pack 1

Qlogic QLA2100F-EMC;BIOS version 1.37; driver version 2.14g

HP Netserver LH II, LH 3, LH 4, LX. LXr, LXr Pro8, LXr8000

NetWare 4.11 with support pack 6, or NetWare 5.00 with support pack 1


IBM Netfinity 5000, 5500, 5500M10, 7000, 7000M10

NetWare 4.11 with support pack 6, or NetWare 5.00 with support pack 1


Table 1-5 Fabric Switch Support on UNIX Hosts



Sun UltraSPARC I/II, Ultra Enterprise 3x00, 4x00, 5x00, 6x00, 10000

Solaris 2.6 w/current patches

Jaycor FC-1063-EMC, rev H; BIOS version 13.3.5; driver 2.2.2.EMC

Jaycor FC64-1063-EMC, rev C, D, or E; BIOS version 13.3.5; driver 2.2.2.EMC



1

1-16


Table 1-6 Fabric Switch Support on Windows Hosts



Compaq Proliant 5000, 5500, 6000, 6500, 7000

Windows NT 4.0, Service Pack 5




Dell PowerEdge 6100/6300 Windows NT 4.0,Service Pack 5

Qlogic QLA2200F-EMC; see note a




HP Netserver LH, LH3, LH4, LH-II, LXR, LXR Pro8, LXr8000

Windows NT 4.0,Service Pack 5







IBM Netfinity 5000, 5500, 5500M10, 5500M20, 7000, 7000M10





Siemens PRIMERGY 7xx, 8xx






Unisys Aquanta QS/2V Windows NT 4.0,Service Pack 5






Table 1-6 Fabric Switch Support on Windows Hosts (continued)




1

1-18


a. Contact your EMC representative for the latest Firmware/BIOS and Driver versions.

NEC Express 5800/140 Ma Windows NT 4.0,Service Pack 5





NCR WorldMark™ 4300, 4380, 4400

Windows NT 4.0, Service Pack 3, 4, or 5





Table 1-6 Fabric Switch Support on Windows Hosts (continued)





Where to Find Host-Specific Information

These chapters describe the steps to incorporate Symmetrix into each host-specific system environment:

Fibre Channel Topology Host Type Refer to:

Arbitrated Loop HP9000 Chapter 2

Solaris SPARC Chapter 3

Windows NT Chapter 4

SGI Challange Chapter 5

SGI Origin Chapter 6

AIX Chapter 7

Siemens (running Reliant UNIX) Chapter 8

NetWare Chapter 9

Solaris X86 Chapter 10

Fabric Solaris SPARC Chapter 11

Windows NT Chapter 12


1

1-20


Fibre Channel Port TypesFibre Channel standards use the term “node” to describe any device connected to one or more other devices over Fibre Channel. Each node has at least one port that connects to other ports in other nodes.

There are seven types of Fibre Channel port, some of which are shown in Figure 1-1.

Figure 1-1 Fibre Channel Port Types

Table 1-7 Fibre Channel Port Types

Port Type Description

N_Port A port on a node outside the fabric

NL_Port An N_Port that can also connect to a Fibre Channel arbitrated loop

F_Port A port, located on a switching device, that connects to an N_Port and brings that connection (internally within the switch) to the fabric

FL_Port An F_Port that can also connect to a Fibre Channel arbitrated loop

E_Port A port, located on a switching device, that connects to another E_Port on the same or a different switching device

G_Port A port that can act as either an E_Port or an F_Port

GL_Port A port that can act as E_Port, an F_Port, or an FL_Port



Fibre Channel TopologiesANSI standards define three Fibre Channel topologies: point-to-point, arbitrated loop, and fabric. Symmetrix Fibre Channel supports arbitrated loop (FC-AL) and fabric (FC-SW).

Arbitrated Loop Topology

The standard Symmetrix loop configuration has two ports—the host bus adapter (see supported adapters in Table 1-3 on page 1-10) and the Symmetrix director. (FC-AL supports up to 126 ports on any one loop.)

Loops without Hubs On a Fibre Channel arbitrated loop without a hub (Figure 1-2), each node acts as a repeater for all other nodes on the loop. As a result, if one node goes down, the entire loop goes down, and access to the storage device is lost by all of the nodes.

Figure 1-2 Hubless Loop

As shown in Figure 1-2, devices in a hubless loop are daisy-chained to form a closed loop. Experience with Ethernet has shown that as devices are added or removed over time, this configuration produces a random wiring topology, introducing problems with maintenance, testability, and reliability.

Fibre Channel Topologies 1-21

1

1-22


Loops with Hubs Fibre Channel hubs are used to build arbitrated loops of three or more nodes. Hubs can be used in many different cabling configurations to provide extended connectivity and high availability to the arbitrated loop topology.

Much like Ethernet hubs in LAN environments, Fibre Channel hubs provide high availability in storage network environments, by ensuring that a hardware failure in one node will not affect other nodes in the loop.

Figure 1-3 Loop with Hub

As shown, a hub configuration still involves a loop; however, hubs can usually automatically bypass an unused or failed ports. Nodes can be powered off or added to the loop without serious loop effects.

Hubs also support the popular physical star cabling topology, for more manageable cabling and more effective fault isolation.

Refer to the following chapters for host-specific hub support information:

• HP — Chapter 2• Solaris SPARC — Chapter 3• Siemens — Chapter 8• Solaris X86 — Chapter 10



Fabric Topology The Fibre Channel fabric topology involves a switching device (the fabric) interconnecting two or more nodes. (Symmetrix and host devices are nodes.) Rather than traveling around an entire loop, frames are routed between source and destination by the fabric.

EMC Connectrix is an example of a Fibre Channel switch. Connectrix manuals are listed under Related Documentation in the Preface of this manual.

Fabric switches offer strong advantages over hubs, in both performance and manageability.

Hubs vs. Switches Here are some comparisons between arbitrated loop hubs and fabric switches.

Speed A hub supports only one full-duplex connection between port pairs at one time. Although every port in a 10-port hub is capable of full-speed operation, only one pair of ports can be active at any one time. On a switched fabric, every port pair can run full duplex simultaneously at 100 Mbytes/second.

The 32 ports of the EMC Connectrix ED-1032 can connect 16 port pairs, each capable of 100 Mbyte/second full duplex, for an aggregate bandwidth of 3,200 Mbytes/second.

Bandwidth The aggregate bandwidth of a hub is fixed, but the aggregate bandwidth of a fabric increases as additional port pairs are added. This scaling capability is an important management feature, because it allows the administrator of the Enterprise Storage Network to reallocate the bandwidth of the network among ports without moving cables and/or reconfiguring the environment.

Data Flow Figure 1-4 shows the data flow in a switch versus the data flow in a hub. In the hub configuration, a loop connection between the top host and the top Symmetrix prevents the host at the bottom from connecting to the loop until the next arbitration cycle. A Fibre Channel switch, on the other hand, provides a non-blocking switched fabric with fully duplexed 100 MB/sec bandwidth available at each port. The top host can be connected at full speed with the top Symmetrix while the bottom host is connected at full speed to the bottom Symmetrix.

Fibre Channel Topologies 1-23

1

1-24


Figure 1-4 Loop vs. Fabric Data Flow



Connectivity TopologiesFibre Channel hub and switch topologies have been developed to solve three distinct customer problems, identified in Table 1-8.

Symmetrix Fibre Channel currently supports the Capacity and Consolidation topologies. The concept of Proximity Extension is supported; however, implementation requires a longwave switch-to-switch connection, which is not currently supported.

These topology solutions can be combined to solve multiple customer problems simultaneously. For example if you combine all three topologies you get high-capacity, highly available, multi-server, geographically dispersed clusters with a minimum of host I/O slots.

Distance Topology The distance topology uses both shortwave and longwave connections to extend the maximum distance between the host and Symmetrix. Access to the longwave right-of-way by multiple mainframe connections and multiple storage connections increases availability.

For both availability and resource management reasons, data centers generally prefer to terminate the longwave into an ESCON® director, then implement a connection to another ESCON director. Fibre Channel can be deployed in a similar fashion, where the server and storage connections are made into connectivity gear (hub or switch, for example), and the longwave/single-mode link is implemented hub to hub, or switch to switch.

Table 1-8 Fibre Channel Hub/Switch Connectivity Topologies

Problem Solution Description of Solution

Proximity Extension

Distance Topology

Uses shortwave-to-longwave conversion to extend server-to-storage distance beyond shortwave’s 500-meter limitation.

Capacity Expansion

Capacity Topology

Expands the storage capacity supported per host port by allowing a host port to connect to two or more Symmetrix nodes.

Storage Consolidation

Consolidation Topology

Allows connecting a single Symmetrix node to two or more host nodes, thereby consolidating server interconnects into fewer Symmetrix connections.

Connectivity Topologies 1-25

1

1-26


Most Fibre Channel equipment is designed for shortwave lasers with multimode optical fibers, which is effective for up to 500 meters. Symmetrix and all of its qualified Fibre Channel directors support that distance.

Longwave lasers with single-mode fiber are intended to allow distances exceeding 500 meters. The Fibre Channel standard provides for longwave distances up to 10 kilometers, although the first longwave options for arbitrated loop support a maximum distance of two kilometers. A future release of Symmetrix Fibre Channel will support longwave fabric configurations.

Distance Topology inthe Arbitrated Loop

Environment

Here is an example of Symmetrix implementation of the distance topology in the arbitrated loop environment.

Figure 1-5 FC-AL Distance Topology Example

The right-of-way containing the single-mode fiber may be one of the most valuable assets to the data center, providing critical disaster-recovery facilities. By replicating the hubs/switches, as well as the server and storage connections at each site, a highly fault-resistant topology ensures maximum availability for the site-to-site interconnection.

Figure 1-6 FC-AL High-Availability Distance Topology Example



Distance Topology inthe Fabric

Environment

Here is an example of Symmetrix implementation of the distance topology in the fabric environment.

Figure 1-7 FC-SW Distance Topology Example

The configuration shown in Figure 1-7 requires a longwave switch-to-switch connection, which is not supported in the current release of Symmetrix Fibre Channel.

Capacity Topology The capacity topology expands storage capacity in the Symmetrix environment. This application allows a single Host Bus Adapter in a file server to access a large capacity that might be stored on multiple Symmetrix devices.

Capacity Topology inthe Arbitrated Loop

Environment

Use of the capacity topology might be less frequent in the Symmetrix environment because Symmetrix provides access to at least 128 volumes in the Sun and HP FC-AL environments without a hub. However, this requirement can be driven by server I/O slot constraints when the customer has used up or reserved for other purposes his server I/O slots.

By using a hub, the host system includes a fault-resilient connection to a large pool of Symmetrix storage, reducing server I/O slot count.


1

1-28


Figure 1-8 FC-AL Capacity Expansion Topology Example

HP-UX PV Links play an essential role in providing high availability in many Fibre topologies. EMC’s PowerPath does the same when deployed with Fibre Channel. These host-based software products provide availability during the failure and repair of one of the hubs. In addition, PowerPath provides load balancing services, which facilitates performance management of the system.

Figure 1-9 FC-AL High-Availability Capacity Expansion Topology Example



Capacity Topology inthe Fabric

Environment

The logical concept of the capacity topology in a switched fabric is described by the fan-in rate ("in" as in "into Symmetrix"). Figure 1-10 illustrates a fan-in rate of four. In the figure there are four Symmetrix systems. Each Symmetrix connects one Fibre Channel director port to a shared server port.

In the example in Figure 1-10, several host I/O slots are needed for tape, clustering, and networking connections, leaving only one slot available for attachment to four Symmetrix units. By using a Fibre Channel fabric switch, the system provides connectivity to a large pool of Symmetrix storage, reducing server I/O slot count to a minimum.

Figure 1-10 FC-SW Capacity Expansion (Fan-in) Topology

ED-1032-32Host

Symmetrix

Symmetrix

Symmetrix

Symmetrix


1

1-30


Consolidation Topology

The consolidation topology delivers server interconnect consolidation. The consolidation topology is required by many Windows NT environments where low-capacity servers need to be connected to a high-capacity Symmetrix, expanding the required number of server connections into the Symmetrix.

ConsolidationTopology in theArbitrated Loop

Environment

Figure 1-11 and Figure 1-12 are examples of the consolidation topology in a loop environment.

Figure 1-11 FC-AL Consolidation Topology Example



Figure 1-12 FC-AL High-Availability Consolidation Topology Example

In the example in Figure 1-12, six hosts, each with two FC-AL ports, require twelve storage connections. By using a pair of Fibre Channel hubs, all twelve server connections can be consolidated into two storage connections. Servers with low I/O demands (for example, they may be bottlenecked on CPU or networking resources) can share the storage bandwidth of two Symmetrix connections.

Both clustered and non-clustered applications are possible. Through host-based file-locking facilities, clustered hosts share information assets. Non-clustered application environments can share physical storage assets, capacity, bandwidth, and connectivity.

Channel failover and channel load-balancing software products like PowerPath can play a central role in providing manageability, reliability, and performance benefits in this solution.


1

1-32


ConsolidationTopology in the Fabric

Environment

The logical concept of a consolidation topology is described by the fan-out rate ("out" as in "out of Symmetrix"). Figure 1-13 illustrates a fan-out rate of four. In the figure, a single Symmetrix port is shared by four server connections. The 4:1 logical topology is implied. As developed in the solutions section of this document, a 32-port switch can be configured with a physical topology of 24 server-links and six storage-links, organized into a logical topology of six 4:1 fan-outs.

Figure 1-13 FC-SW Consolidation (Fan-out) Topology Example

Both clustered and non-clustered applications of the consolidation topology are possible. Through host-based file-locking facilities, clustered hosts share information assets. Non-clustered application environments can share physical storage assets, capacity, bandwidth, and connectivity.

Channel failover and channel load-balancing software products like EMC’s PowerPath can play a central role in providing manageability, reliability, and performance benefits in this solution.



Combined Topologies

The three basic topologies can be combined to take advantage of the benefits of each.

Figure 1-14 FC-AL Combined Hub Topologies Example


1

1-34


Figure 1-15 FC-SW Combined Topologies Example



Symmetrix Fibre Channel Hardware

Fibre Channel Director

The Symmetrix Fibre Channel director supports data transfer rates up to 100 MB/sec over each channel interface simultaneously. Data transfers between host and cache can execute concurrently across two separate Fibre Channel ports on each director. Each Fibre Channel port has its own DMA pipe to support concurrent operations.

Table 1-9 lists the maximum number of Fibre Channel directors and ports for each Symmetrix model that supports Fibre Channel.

a. Requires standard RPQ for six channel directors. The standard configuration is four directors (eight Fibre Channel ports).

HardwareComponents

The Fibre Channel director comprises two circuit boards: a director board and an adapter board. Fibre Channel directors can occupy the same backplane slots that are available to SCSI channel directors. (Refer to Figure 1-17 on page 1-38.)

Director Board

The director board contains the following:

• Two ANSI-compliant one-gigabit Fibre Channel interfaces for connection to open systems hosts, and one high-speed path to cache.

• HP TACHYON chips, which implement encode/decode and framing protocol functions (layers FC-1 and FC-2 of the Fibre Channel standard). The TACHYON chips also provide the repeater function required in the arbitrated loop topology.

Table 1-9 Fibre Channel Directors and Ports

Model Max Directors Max Ports

3330/5330 4 8

3430/5430 6 a 12

3700/5700 8 16

3630/5630 4 8

3830/5830 6 a 12

3930/5930 8 16

Symmetrix Fibre Channel Hardware 1-35

1

1-36


• Two advanced microprocessors that process commands and data from the host, and manage access to cache. The Fibre Channel SCSI protocol mapping and upper-level protocol layers are both implemented within the director.

Figure 1-16 Fibre Channel Director

Adapter Board

The adapter provides an interface (FC-0 layer of the Fibre Channel standard) between the director board and host channels. Each adapter provides transceiver connections for two Fibre Channel ports. Each adapter is located on the rear backplane, opposite its corresponding director board.

Operation Figure 1-16 illustrates the interconnects and data paths for a Fibre Channel director. Two host channels connect to the adapter board, located at the rear of the Symmetrix chassis. The director board, located on the other side of the chassis midplane, receives one Fibre Channel on each half of the board. The A and B sides of the director board operate independently, routing data to the system bus through a high-speed buffer cache interface. The channel directors and cache handle the storage control functions, while the disk directors handle the data storage functions.

A

FA-01A

TACHYONCHIP

PROCA

DirectorAdapter Mid

pla

ne

Two-Port Dual-Processor, Fibre ChannelDirector (DP-FCD2-MM)

X-Bus

B

TACHYONCHIP

PROCB

FA-01B



Operator PanelDisplays

The channel director operator panel on the front of the Symmetrix cabinet displays the current activity and status of each Fibre Channel director.

The operator panels for various Symmetrix devices are shown in the device-specific manuals.

The Enable/Disable switch on the operator panel places a channel interface on line or off line. The operator panel LEDs function as shown in the following table.

Installation Figure 1-17 on page 1-38 shows card locations for each Symmetrix model that supports Fibre Channel. Fibre Channel directors can be installed into any channel director slot (labeled CD in the figure).

Installation of a Fibre Channel director includes the physical installation of two circuit card assemblies (adapter and director), and configuration of the director through the Symmetrix service processor interface.

Symmetrix Fibre Channel directors must be installed and configured by an EMC Customer Engineer.

Table 1-10 Operator Panel LEDs

LED Function

Power Fibre Channel Director is operational.

Active Channel activity – when LED is lit, I/O operations are in progress.

Ready Channel state – when LED is lit, that channel is on line to the host system. There is a Ready LED for each channel.


1

1-38


Figure 1-17 Symmetrix Director Locations

As shown in Figure 1-17, six Fibre Channel directors can be installed into a Symmetrix 34xx/54xx or 3830/5830 if memory is limited to two boards (standard RPQ required).

Cables Symmetrix Fibre Channel cables currently use 50/125-µm (core/cladding) optical fiber that supports transmission of multimode short-wavelength laser. The specified maximum distance for this transmission mode is 500 meters.

Installation of Fibre Channel cables is done according to each site’s configuration plan. The following guidelines apply.

• Recommended fiber optic cable is 50/125 µm. However, 62.5/125-µm cable, found in some existing facility installations, may be used for distances up to 300 meters. The two types of cable cannot be mixed.

• Copper and 9-µm fiber cables are not supported in the current release of Symmetrix Fibre Channel.

DDDDCD DD

34xx/54xx

DDDD CDCDCD CDMEM CDCDCD

= CACHE MEMORYMEM

= CHANNEL DIRECTOR(SCSI, ULTRA SCSI, FIBRE, PARALLEL,SERIAL)

CD

DD = DISK DIRECTOR

DD CDCD MEM CDDD CD

DDDDCD DD CDMEMCD CDDDMEMor CD

DD

3330/5330

3700/5700

DD

F

DD

EDC321016151432

DIR NUMBER

FEDC543210 BA

1

MEM MEMMEM

MEMMEMor CD

MEM

FEDC9876541110321 1312BA0

M2M1

SLOT NUMBER

1615141398765 M4M3432 1211101 M2M1

161514135432 121 M2M1



• Use EMC cables for lengths 100 meters or shorter. Longer cables (up to 500 meters) can be obtained from AMP, Inc., or from an authorized distributor of AMP products. (AMP is an EMC-qualified vendor. Contact information can be found on AMP’s website, www.amp.com.)

Table 1-11 lists the Fibre Channel cables available from EMC.

Table 1-11 EMC Fibre Channel Cables

Length Model No. Part No.

5 Meters FC5M-50M 038-001-488

10 Meters FC10M-50M 038-001-489

30 Meters FC30M-50M 038-001-490

50 Meters FC50M-50M 038-001-491

100 Meters FC100M-50M 038-001-492


1

1-40



Part 2

This section describes configuration of the hosts that Symmetrix supports over Fibre Channel arbitrated loop. The contents of Part 2 are:

• Chapter 2, HP 9000 Host on Arbitrated Loop

• Chapter 3, Sun Solaris Host on Arbitrated Loop

• Chapter 4, Windows NT Host on Arbitrated Loop

• Chapter 5, SGI Challenge Host on Arbitrated Loop

• Chapter 6, SGI Origin Host on Arbitrated Loop

• Chapter 7, AIX Host on Arbitrated Loop

• Chapter 8, Siemens/Reliant UNIX Host on Arbitrated Loop

• Chapter 9, Netware Host on Arbitrated Loop

• Chapter 10, Solaris X86 Host on Arbitrated Loop

Host Support onArbitrated Loop

2

This chapter provides information specific to HP 9000-series hosts connecting to Symmetrix over Fibre Channel arbitrated loop. The chapter includes the following sections:

• HP Arbitrated Loop Environment...................................................2-2• Host Connectivity ..............................................................................2-3• Symmetrix Configuration .................................................................2-4• Host Configuration............................................................................2-5• HP 9000 Fibre Channel Hubs ...........................................................2-6• HP 9000 Fibre Channel Mux.............................................................2-8

Before installing a Fibre Channel connection between a host and Symmetrix, refer to Chapter 1 for an overview of Symmetrix Fibre Channel connectivity.

HP 9000 Host onArbitrated Loop

HP 9000 Host on Arbitrated Loop 2-1

2

2-2

HP 9000 Host on Arbitrated Loop

HP Arbitrated Loop EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the arbitrated loop/HP host environment.

Host OperatingSystem

Refer to Table 2-1 on page 2-3.

Supported Software • PV (Physical Volume) Links, which are dual I/O paths between Symmetrix and the HP host with automatic failover to the second I/O path.

• HP Logical Volume Manager (although some restrictions are placed on mixing devices accessed through SCSI and Fibre Channel).

• HP MirrorDisk/UX.

• MC/ServiceGuard for clusters of up to eight nodes.

• Oracle Parallel Server (OPS) with MC/LockManager for clusters of up to four hosts. HP has set a limitation that, in an MC/LockManager configuration, no more than two nodes can access a single LUN present on a Fibre Channel loop. (More than two nodes can have the same LUN visible, but only two nodes can have active I/O to the LUN.)

Supported Hardware • Hosts and host bus adapters — Refer to Table 2-1 on page 2-3.

• Hubs — Refer to HP 9000 Fibre Channel Hubs on page 2-6.

Boot Device Support Symmetrix devices interfaced through Fibre Channel are not supported as boot devices.

Logical Devices • Symmetrix supports up to 16 virtual busses per port, with up to 128 logical devices per bus (but not exceeding 128 devices per port).

• Symmetrix Fibre Channel supports up to 128 logical devices per port. (Future implementations will support many more.)

• HP-UX supports 16 targets per Fibre Channel virtual bus, each with up to 8 LUNs. Symmetrix devices appear identical to standard SCSI devices.

Addressing Symmetrix supports Volume Set Addressing mode, used by HP hosts to address Fibre Channel devices.


2HP 9000 Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel Arbitrated Loop is qualified for use with the HP hosts listed in Table 2-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.

Symmetrix Fibre Channel does not currently support the mixing of different types of HBA (including different types from the same vendor) in a single server. .

a. Host I/O driver software for these adapters is included as part of the HP-UX operating system installation.

b. "Active" means all possible active LUNs, which can be all primary LUNs or all alternate LUNs, but not both.

c. "Total" includes all primary and all alternate PVL (PV Links) LUNs.

d. 512 in a high-availability configuration.

Table 2-1 HBAs for HP 9000 Hosts

Host TypeMinimum OS Version

Host Bus Adapter (HBA) a

Max LUNs

Active per Host b

Total per Loop c

Total per Symm Port c

HP D-Class HP-UX 10.20 TFC or 11.00

A3591A, A3591B 768 320 (or 512 d) 128

HP K-Class HP-UX 10.20 TFC or 11.00

A3404A 768 320 (or 512 d) 128

HP N-Class HP-UX 11.00 A3740A 768 320 (or 512 d) 128

HP R-Class HP-UX 10.20 TFC or 11.00

A3591A, A3591B 768 320 (or 512 d) 128

HP T600 HP-UX 10.20 TFC or 11.00

A3636A 768 320 (or 512 d) 128

HP V-Class HP-UX 11.00 A3740A 768 320 (or 512 d) 128

Host Connectivity 2-3

2

2-4


Symmetrix ConfigurationSymmetrix configuration is performed by an EMC Customer Engineer (CE) via the Symmetrix service processor. The CE will configure the Symmetrix with the following settings for each Fibre Channel port.

a. The attached server must be off line before enabling the UWN flag.

Table 2-2 Symmetrix Configuration for HP Hosts

Parameter Setting

Disk Array Mode (A-bit) Enabled

Volume Set Addressing (V-bit) Enabled

Hard Addressing (H-bit) Enabled

Loop ID Unique ID for each Symmetrix port on a Fibre Channel loop

Non-participating Mode (NP-bit) Disabled—accept soft- assigned address if hard address is not available

Third-party Logout (TP-bit) Enabled

Tag Command Queuing (T-bit) Enabled

Common Serial Number (C-bit) Enabled

Disable Queue Reset on Unit Attention (D-bit)

Disabled

UWN (Unique Worldwide Name) Flag Enabled a

Point-to-Point Mode (PP-bit) Disabled



Host ConfigurationThis section describes the tasks required to configure an HP host for Symmetrix Fibre Channel arbitrated loop.

Installing an HBA Follow the HP recommendations for installation and setup of the appropriate host bus adapter (HBA) adapter for your system. (The card has no user-configurable jumpers or switches.)

Incorporating Symmetrix Fibre Channel

The host can see all the Symmetrix devices assigned to that host’s interface once the following have been accomplished:

• Symmetrix has devices assigned with device addresses• IOSCAN with Probe has been done• Device files have been built with INSF• The directors have been switched on line

Devices are presented to the host in the same manner as devices accessed through a standard SCSI interface. Follow the instructions for hardware mapping and recognizing new devices in the HP/9000 environment in the Symmetrix Open Systems Environment Product Guide (Volume 1).

Device Definitions Devices are defined as physical volumes using the pvcreate command or through the SAM utility. For example, to create the physical volume /dev/rdsk/c3t0d0, enter pvcreate /dev/rdsk/c3t0d0.

Volume Manager andFile Systems

Follow the instructions for volume manager functions and file system creation for HP-UX 10.x devices in the Symmetrix Open Systems Environment Product Guide.

Channel failover (PV Links) can be configured using Fibre Channel, or between Fibre Channel and SCSI.

Migrating to FibreChannel

If upgrading an existing Symmetrix SCSI interface to Fibre Channel, follow the procedures described in Appendix B.

Host Configuration 2-5

2

2-6


HP 9000 Fibre Channel Hubs

HP Hub Support The following hub models are supported for use in HP 9000 systems:

• Model A3724A - 10 shortwave ports

• Model A4839A - 9 shortwave ports and 1 longwave port (for hub-to-hub cascading or connection to 16-port HP SureStore® E Switch F16—see note)

HP Model A52224A is cascadable; Model A52223A is not.

HP hubs use integrated optics, and do not require gigabit interface converters (GBICs).

Refer to Loops with Hubs on page 1-22 for descriptions of various hub configurations.

Hub Configuration Guidelines

The following paragraphs provide guidelines and limitations for using hubs in an HP 9000 and Symmetrix Fibre Channel storage network.

Host Connections One to four host connections per Fibre Channel loop—limited by hub connectivity capacity.

SymmetrixConnections

One to eight Symmetrix connections per Fibre Channel loop—limited by hub connectivity capacity.

Host and Symmetrix connections can be added to or removed from the hub on line (hot plugging/ unplugging).

Cascaded Hubs For site-to-site interconnection, hub-to-hub connections are supported. More than two hubs in one cascaded loop are not supported.

All longwave connections will be hub-to-hub, with a maximum distance of 10 km between hubs. Host-to-hub or hub-to-Symmetrix longwave connections are not supported.

Physical connections to a hub should be made on adjacent port connectors. Do not leave open connectors between cable connections. (See Figure 2-1.)



Figure 2-1 Hub Cabling Recommendation

Cable Lengths The sum of the lengths of all Fibre Channel cable connected to the hub cannot exceed 13 km. (A 500-meter duplex cable adds 500 meters to the length budget, not 1 km.)

There are no restrictions on the mixing of Fibre Channel cable lengths on a hub, as long as the total distance restriction is met.

Software Support Host software and Symmetrix software supported in non-hub Fibre Channel topologies is also supported in hub configurations.

Diagnostics andMaintenance

Repair and system recovery from a hub failure can be done on line with a properly configured high-availability system.

NOYES

HP 9000 Fibre Channel Hubs 2-7

2

2-8


HP 9000 Fibre Channel MuxA Fibre Channel Mux (multiplexer) is a device that provides two-node arbitrated loop Fibre Channel connectivity between the previous generation of Symmetrix systems (models 3100/5100, 32x0/52x0, and 3500/5500) and an HP 9000 host. A Fibre Channel Mux is also sometimes referred to as a Fibre Channel-to-SCSI router.

Symmetrix models not listed in the above paragraph do not support Fibre Channel connections to the mux.

Connection Example

As shown in Figure 2-2, the Mux connects a single Host Fibre Channel port to four SCSI ports connected to Symmetrix FWD SCSI Channel Directors. Mux-to-Symmetrix connections are made using standard SCSI cables.

Figure 2-2 HP Fibre Channel Mux

Supported Models These Mux models are supported for use in HP 9000 systems:

• HP A3511A - stand-alone model• HP A3511AZ - factory-racked model• HP A3308A - deskside model

Configuration Guidelines

The following are guidelines and limitations for using the HP Mux in an HP 9000/Symmetrix Fibre Channel storage network:

• Single Fibre Channel port per Mux

• Direct-host attach only (no Mux connections through hubs)

• PV Link support for redundant Mux connections (separate Muxes only)



• Inactive device sharing through separate Muxes is supported - (not on same Mux)

• Only non-High Availability Mux configurations are supported in this release

• Fibre Channel Arbitrated Loop (FC-AL) protocol

• ANSI-standard 100 MByte/sec Fibre Channel

• Distance up to 500 meters

HP 9000 Fibre Channel Mux 2-9

2

2-10



3

This chapter provides information specific to Sun Solaris hosts connecting to Symmetrix over Fibre Channel arbitrated loop. (Chapter 11 describes Solaris host support over fabric.) The chapter includes the following sections:

• Solaris Arbitrated Loop Environment ............................................3-2• Host Connectivity ..............................................................................3-3• Symmetrix Configuration .................................................................3-4• Host Configuration with Jaycor HBA.............................................3-5• Host Configuration with Qlogic HBA ..........................................3-15• Host Configuration with Emulex HBA ........................................3-25• Partitioning and Labeling New Devices.......................................3-37• Sun Hub Configuration Guidelines ..............................................3-38


Sun Solaris Host onArbitrated Loop

Sun Solaris Host on Arbitrated Loop 3-1

3

3-2

Sun Solaris Host on Arbitrated Loop

Solaris Arbitrated Loop EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the arbitrated loop/Solaris host environment.



Supported Hardware • Hosts and host bus adapters — Refer to Table 3-1 on page 3-3.

• Hubs — Refer to Sun Hub Configuration Guidelines on page 3-38.


Addressing • Sun uses SCSI-2 device access protocol in addressing its Fibre Channel devices. SCSI-3 Array Controller addressing modes are not supported. The peripheral device access mode is supported in Symmetrix to address up to 128 logical devices, in an address range of 0 to 256. Refer to Appendix C for the available addressing modes.

• If you attempt to access existing devices previously interfaced via SCSI, your raw device addressing may be changed after upgrading to Fibre Channel Directors.


3Sun Solaris Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with Solaris hosts on arbitrated loops as shown in Table 3-1. Contact your EMC representative for the latest the latest information on supported hosts and HBAs, as updates are frequent.

Symmetrix Fibre Channel does not currently support the mixing of different types of HBA (including different types from the same vendor) in a single server.

The Fibre Channel HBA driver functions as a device driver layer below the standard “sd” Solaris SCSI adapter driver. The Fibre Channel interface is therefore transparent to the Solaris disk administration system.

Table 3-1 HBAs for Solaris Hosts on Arbitrated Loop

Host TypeMinimum OS Version Host Bus Adapter (HBA) Driver Version Max LUNs

SPARC, UltraSPARC (Sbus)

Solaris 2.5.1 with EMC-approved patches

Jaycor FC-1063-EMC, rev H 2.2.2.EMC 128

Jaycor FC64-1063-EMC, rev B, C, D, or E

2.2.2.EMC 128

Jaycor FCIN-1063-EMC, rev B 2.2.2.EMC 128

Enterprise 250/450, Ultra 30/60, 3x00/ 4x00/5x00/6x00 (PCI bus)

Solaris 2.5.1 with EMC-approved patches

Jaycor FC-1063-EMC, rev H 2.2.2.EMC 128

Jaycor FC64-1063-EMC, rev B, C, D, or E

2.2.2.EMC 128

Jaycor FCIN-1063-EMC, rev B 2.2.2.EMC 128

Solaris 2.6 with EMC-approved patches

Qlogic QLA2100F-EMC 2.20 128

Emulex LP7000E-EMC, BIOS 2.20 3.38 128


3

3-4


Symmetrix ConfigurationSymmetrix configuration is performed by an EMC Customer Engineer (CE) through the Symmetrix service processor. The CE will configure your Symmetrix with the following settings for each Fibre Channel port.

a. If Disk Array Mode and Volume Set Addressing are disabled, the Symmetrix defaults to Peripheral Address Mode for that port. (There is no bit setting for peripheral mode.)

b. Enabled for Veritas DMP.

c. Enabled for PowerPath and Veritas DMP.

‘Setting up an arbitrated loop environment requires EMC Volume Logix software. The EMC CE configures Volume Logix software after configuring the Symmetrix. For additional information, refer to EMC Volume Logix Product Guide, P/N 300-999-024.

Table 3-2 Symmetrix Configuration for Solaris Hosts on Arbitrated Loop

Parameter Setting

Disk Array Mode (A-bit) Disabled a

Volume Set Addressing (V-bit) Disabled a


Loop ID Unique ID for each Symmetrix port on a Fibre Channel loop



Common Serial Number (C-bit) Disabled b


Disabled c




Host Configuration with Jaycor HBAThis section describes the tasks required to install one or more Jaycor host bus adapters into a Solaris host and configure the host for Symmetrix Fibre Channel arbitrated loop.

Refer to Table 3-1 on page 3-3 for approved HBAs. Symmetrix Fibre Channel does not currently support the mixing of different types of host bus adapter (HBA) in a single server.

Installing the HBA Follow the instructions included with your adapter, including installation of all required Solaris system patches. The adapter installs into a single slot, and has no user-configurable jumpers or switches.

Installing the HBA Driver

The HBA I/O driver software is required to interface the Fibre Channel Adapter card to the Solaris Operating system. The driver functions at a layer below the Solaris SCSI driver to present Fibre Channel devices to the operating system as if they were standard SCSI devices.

To install the driver:

1. Be sure you have the latest qualified driver software. If necessary, obtain it on CD-ROM from Jaycor, or FTP the driver from the Jaycor website. Refer to release notes provided with the current driver for information that might be unique to new driver revisions.

2. The next step depends on the type of installation:

Type of Installation Installing From: Go to:

New Web Downloading and Installing a New Driver from the Jaycor Web Site on page 3-6

New CD-ROM Installing a New Driver from CD-ROM on page 3-6

Upgrade Web Downloading and Installing a Driver Upgrade from the Jaycor Web Site on page 3-7

Upgrade CD-ROM Installing a Driver Upgrade from CD-ROM on page 3-8

Host Configuration with Jaycor HBA 3-5

3

3-6


Downloading andInstalling a New Driver

from the Jaycor WebSite

Use the following procedure to download the Jaycor driver from the Jaycor web site and perform a first-time install:

1. Use a web browser to access this link:

http://www.jaycor.com/fibre/ftp/Released/Symmetrix/Solaris/v2.2.2.EMC

2. Download the appropriate driver to the host:

3. Add the appropriate package:

4. Follow the procedures described under Incorporating Symmetrix on page 3-9.

Installing a New Driverfrom CD-ROM

Use the following procedure to load the driver from the Jaycor CD-ROM, and perform a first time install.

1. Insert the JNI CD-ROM.

2. Change to the appropriate directory:

If HBA is: Download driver:

FC-1063-EMC JNIfcaEMC.pkg

FC64-1063-EMC JNIfcawEMC.pkg

FCIN-1063-EMC JNIfca-pciEMC.pkg

If HBA is: Enter:

FC-1063-EMC pkgadd -d JNIfcaEMC.pkg

FC64-1063-EMC pkgadd -d JNIfcawEMC.pkg

FCIN-1063-EMC pkgadd -d JNIfca-pciEMC.pkg

If HBA is: Enter:

FC-1063-EMC cd /cdrom/jni/Solaris/SBus

FC64-1063-EMC cd /cdrom/jni/Solaris/SBus

FCIN-1063-EMC cd /cdrom/jni/Solaris/PCI



3. Add the package:


Downloading andInstalling a DriverUpgrade from the

Jaycor Web Site

Use the following procedure to download the driver from the Jaycor web site, and perform a Fibre Channel driver upgrade.




3. Back up the appropriate file:

If HBA is: Enter:








If HBA is: Back up file:

FC-1063-EMC /kernel/drv/fca.conf

FC64-1063-EMC /kernel/drv/fcaw.conf

FCIN-1063-EMC /kernel/drv/fca-pci.conf


3

3-8


4. Remove the old driver:

5. Add the new package:

6. Restore the appropriate file:


Installing a DriverUpgrade from

CD-ROM

Use the following procedure to load the Jaycor driver from the Jaycor CD-ROM, and perform a Fibre Channel drive upgrade:


If HBA is: Enter:

FC-1063-EMC pkgrm JNIfca

FC64-1063-EMC pkgrm JNIfcaw

FCIN-1063-EMC pkgrm JNIfca-pci

If HBA is: Enter:




If HBA is: Restore file:














6. Follow the procedures described under Incorporating Symmetrix.

Incorporating Symmetrix

To insure smooth integration and maximum performance from the host and Symmetrix, you must you must edit these files (as described in detail later):

• fca driver configuration file — Refer to fca .conf, fcaw.conf, fca-pci.conf on page 3-10

• Driver configuration file sd.conf — Refer to sd.conf on page 3-12• System specification file etc/system — Refer to etc/system on

page 3-13

If HBA is: Enter:




If HBA is: Enter:




If HBA is: Enter:





3

3-10


After editing the files, type reboot -- -r <Enter>. This reboots the host with the -r (reconfigure) option, which rebuilds the kernel and implements the changes.

fca .conf, fcaw.conf,fca-pci.conf

1. The configuration file is created automatically by pkgadd. The file contains important information about how the driver should behave. The file name depends on the HBA:

If necessary, edit the configuration file as shown in Table 3-3. Changes to the HBA configuration file will take effect when the host is rebooted.

If HBA is: File path and name are:




Table 3-3 Jaycor HBA Configuration File Parameters

Parameter Description Default

fca_nport Specifies whether HBA port is on arbitrated loop (fca_nport = 0) or fabric (fca_nport = 1)

0

failover Determines how many seconds PowerPath will wait to switch to the alternate path if a path fails

60 a

failover_extension Extends a target’s failover period by the number of seconds specified, to perform target rediscovery

0

recovery_attempts Determines how many times the driver should try to log into the Symmetrix after a link failure

5

class2_enable Enables (if 1) or disables (if 0) class 2 exchanges (ACK_1 mode) for devices that support class 2

0

fca_heartbeat Determines the number of microseconds between test frames (This is used only for debugging)

0

reset_glm Resets the link before adapter initialization if set to a value other than 0

0

continued on next page — footnotes follow table.



a. Set failover to 0 if you are not using EMC PowerPath for devices accessed through this Fibre Channel connection.

b. An asterisk (*) following an HBA name indicates all instances of that HBA driver. Set this value to fas to disable the default bind to fcaw*.

c. A $ preceding the string indicates that static binding is enabled. An x in place of a digit indicates "don’t care" for that digit. The default value shown means the WWN is static (don’t care). (Note that the default is shown on two lines only because of space limitations.)

d. A $ preceding the string indicates that static binding is enabled. An x in place of a digit indicates "don’t care" for that digit. The default value shown means the port is non-static (don’t care).

timeout_reset_enable Clears the problem when commands are being timed out:• If 0, driver attempts to clear the command by sending an

ABTS_LS request to the target• If 1, driver attempts to reset the target

0

busy_retry_delay Sets the time delay (in 10-millisecond increments) after the target returns BUSY status

100

link_recovery_delay Sets the time delay (in 10-ms increments) between Link Up and Login Recovery, to help link stability before recovery

100

scsi_probe_delay Sets the delay (in 10-millisecond increments) before SCSI probes are allowed to occur during boot.

500

abort_retry_delay Sets the time delay (in 10-millisecond increments) before a command is retried due to an abort from timeout or link recovery condition

100

def_hba_binding Sets the HBA binding for every Target/LUN instance that does not explicitly define one

fcaw* b

def_wwn_binding Sets the 16-digit hexadecimal default world-wide name (WWN) binding for every Target/LUN instance that does not explicitly define one

$xxxxxxxxxxxxxxxx c

def_port_binding Sets the 6-digit hexadecimal default port binding for every Target/LUN instance that does not explicitly define one

xxxxxx d

fca_verbose Determines how many messages are displayed to the console.• A setting of 0 quiets the driver messages to the console,

but still prints them to the system message log. (A "boot -v" overrides this setting and makes the driver verbose again.)

• A setting of 1 makes the driver print all messages to the console and to the system message log

1

Table 3-3 Jaycor HBA Configuration File Parameters (continued)



3

3-12


sd.conf Symmetrix devices are addressed using target IDs and LUNs. By default, Solaris searches only for target IDs on the bus. You must modify the lower-level driver configuration file /kernel/drv/sd.conf to include the correct definitions for each target ID that needs to support multiple LUNs.

Changes to sd.conf will not take effect until the host is rebooted.

Also refer to the instructions for hardware mapping and recognizing new devices under Solaris Environment in the Symmetrix Open Systems Environment Product Guide.

Devices accessed via Fibre Channel using the Jaycor driver are addressed behind a single target ID with up to 256 LUNs. (This differs from existing SCSI device addressing, which can have multiple targets and LUNS.) In the standard Symmetrix device definition file, target 0 should have 256 LUNs, and all other targets (1 through 125) have a LUN 0 only.

Edit the sd.conf file to list all targets and all LUNs that might be addressed. The Target ID needed to address a device is determined by the Fibre Channel Arbitrated Loop Physical Address (AL_PA). A Loop_ID of 00 (AL_PA of EF) will have LUNS behind Target ID 0, Loop_ID 01 has LUNs on target ID 1, and so on. Refer to Appendix C for the available addressing modes.

Since each Fibre Channel port can have only one loop ID (or AL_PA), all devices accessed through a port will have the same target ID. If you need to access existing devices that previously had multiple target IDs, be aware of changes required for raw device addressing.

For example:

SCSI Target LUN Fibre/SCSI Target LUN

0 0 0 0

0 1 0 1

0 15 0 15

1 0 0 16

2 0 0 32

15 0 0 240



Your actual target/LUN assignment will vary depending on unique system configuration requirements. Be sure that existing and new configurations are well documented before upgrading to Fibre Channel Directors.

Make sure that only the target=x lun=0 line is specified for any target ID that does not need LUN support. This decreases the time needed to reboot the system.

Sample sd.conf file:name=”sd” class=”scsi”target=0 lun=0;name=”sd” class=”scsi”target=0 lun=1;..name=”sd” class=”scsi”target=0 lun=255;name=”sd” class=”scsi”target=1 lun=0;name=”sd” class=”scsi”target=2 lun=0;..name=”sd” class=”scsi”target=125 lun=0;

Device definition files are available on EMC’s FTP server, ftp.emc.com, in /pub/symm3000/solaris. The file sd.conf.fibre is a device definition file for Fibre Channel devices. You can copy/paste the contents of the file into the file /kernel/drv/sd.conf in the Solaris host. Use only those lines from sd.conf.fibre that apply to your host’s configuration.

Refer to Symmetrix Device Definition Files in the Symmetrix Open Systems Environment Product Guide for instructions on how to transfer these files to your host.

etc/system Operation in a Solaris environment requires that some parameters in the file /etc/system first be modified, as described in the following steps.

Changes to /etc/system will not take effect until the host is rebooted.


3

3-14


The modification to the parameter sd_max_throttle is required specifically for Fibre Channel. Other settings apply to both standard SCSI and Fibre Channel.

1. Type set sd:sd_max_throttle=20 <Enter>.

2. Type set scsi_options = 0x7F8 <Enter>.

The bit meaning for scsi_options is as follows:

Since /etc/system can also affect other disks in the system, consider the effects of implementing the scsi_options=0x7f8 mask on the other disks. If it is not set, Symmetrix operations will not benefit from these options.

3. Type set sd:sd_io_time = 0x78 <Enter>.

This setting prevents the host from issuing warning messages when non-disruptive operations are performed on Symmetrix.

Partitioning and Labeling New Devices

Refer to Partitioning and Labeling New Devices on page 3-37.

Migrating to Fibre Channel

If upgrading an existing Symmetrix-to-host SCSI interface to Fibre Channel, see Appendix B.

Bit Mask Meaning

3 0x8 Disconnect enable

4 0x10 Link enable

5 0x20 Sync xfer enable

6 0x40 Parity support enable

7 0x80 Tag commands enable

8 0x100 Fast SCSI enable

9 0x200 Wide SCSI enable

10 0x400 Ultra SCSI enable



Host Configuration with Qlogic HBAThis section describes the procedures required to install one or more Qlogic QLA2100F-EMC host bus adapters into a Solaris host and configure the host for Symmetrix Fibre Channel arbitrated loop.

Refer to Table 3-1 on page 3-3 for approved HBAs. Symmetrix Fibre Channel does not currently support the mixing of different types of host bus adapter (HBA) in a single server.

Installing the HBA Follow the instructions included with your adapter, including installation of all required Solaris system patches. The adapter installs into a single slot, and has no user-configurable jumpers or switches.


Using the QLA2100F-EMC adapter with the Solaris Operating system requires HBA I/O driver software. The driver functions at a layer below the Solaris SCSI driver to present Fibre Channel devices to the operating system as if they were standard SCSI devices.


1. Be sure you have the latest qualified driver software. If necessary, you can download the driver from the Qlogic website (as described later in this procedure). Refer to release notes provided with the driver for information that might be unique to new driver revisions.



New Web Downloading and Installing a New Driver from the Qlogic Web Site on page 3-16


Upgrade Web Downloading and Installing a Driver Upgrade from the Qlogic Web Site on page 3-17


Host Configuration with Qlogic HBA 3-15

3

3-16



from the Qlogic WebSite

Use the following procedure to download the QLA2100F driver from the Qlogic web site and perform a first-time install:

1. Use a web browser to access this link: http://www.qlc.com

Then:

a. Click ADAPTER DRIVERS & UTILITIES

b. Click QLA2100/QLA2000

c. Click EMC Approved Drivers

d. Click Solaris 2.6 Driver

e. Click sparc

2. Download qla2100.Z to the host.

3. Type uncompress qla2100.Z <Enter>.

4. Type pkgadd -d qla2100 <Enter>, to install the new driver.

5. Edit any necessary files as described under Incorporating Symmetrix Fibre Channel on page 3-18.

6. Type reboot -- -r <Enter> to reboot the host with the -r (reconfigure) option.


Use the following procedure to load the driver from the Qlogic CD-ROM, and perform a first time install.

1. Insert the Qlogic CD-ROM.

2. Change to the directory /cdrom/qla2100/sparc.

3. Copy the file qla2100.Z to the host.

4. If the file extension z is lowercase, rename the file with an uppercase Z extension.








Qlogic Web Site

Use the following procedure to download the driver from the Qlogic web site, and perform a Fibre Channel driver upgrade.

1. Back up the file /kernel/drv/qla2100.conf.

2. Type pkgrm QLA2100 <Enter>, to remove the old driver.

3. Use a web browser to access this link: http://www.qlc.com

Then:

a. Click ADAPTER DRIVERS & UTILITIES

b. Click QLA2100/QLA2000

c. Click EMC Approved Drivers

d. Click Solaris 2.6 Driver

e. Click sparc

4. Download the file qla2100.Z to the host.






CD-ROM

Use the following procedure to load the Qlogic driver from the Qlogic CD-ROM, and perform a Fibre Channel drive upgrade:

1. Back up the file /kernel/drv/qla2100.conf.

2. Type pkgrm QLA2100 <Enter>, to remove the old driver.

3. Insert the Qlogic CD-ROM.

4. Change to the directory /cdrom/qla2100/sparc.

5. Copy the file qla2100.Z to the host.

6. If the file extension z is lowercase, rename the file with an uppercase Z extension.





3

3-18




Once the Symmetrix has devices assigned with device addresses and the directors have been switched on line, the host can see all the target Symmetrix devices assigned to that host interface. Devices are presented to the host in the same manner as devices accessed through a standard SCSI interface.

To insure smooth integration and maximum performance from the host and Symmetrix, you must edit these files (as described in detail later):

• Qlogic driver configuration file qla2100.conf — Refer to qla2100.conf below

• Host sd driver configuration file sd.conf — Refer to sd.conf on page 3-21

• System specification file etc/system — Refer to /etc/system on page 3-23


qla2100.conf The configuration file (qla2100.conf) is created automatically by pkgadd. The file contains important information about how the driver should behave. If necessary, edit qla2100.conf as shown in Table 3-4.

Changes to qla2100.conf will not take effect until the host is rebooted.

Table 3-4 lists the required settings for the configuration file variables. Descriptions of the variables follow the table.



a. PowerPath is not currently supported in a hub environment.

b. In a hub environment, the hard loop ID for each HBA must be unique.

Descriptions of qla2100.conf Variables

hba0-frame-payload-size — Configuration flag (512, 1024 or 2048 bytes) for "maximum frame length."

hba0-max-iocb- allocation — Number of commands (1 to 750) queued internally within the HBA. Exceeding the adapter’s buffers causes unnecessary retries, which impact performance. The

Table 3-4 /kernel/drv/qla2100.conf Settings for Solaris SPARC Host

Variable Default Value

Required Setting

If No Hub If Hub(s) If PowerPath a

hba0-frame-payload-size 1024 bytes 1024 bytes 1024 bytes 1024 bytes

hba0-max-iocb-allocation 256 512 512 512

hba0-execution-throttle 16 20 20 20

hba0-login-retry-count 5 5 5 5

hba0-enable-adapter-hard-loop-ID 0 (disable) 1 (enable) 1 (enable) 1 (enable)

hba0-adapter-hard-loop-ID 100 100 see note b 100

hba0-login-timeout 4 (sec) 4 (sec) 4 (sec) 4 (sec)

hba0-enable-extended-logging 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-enable-64bit-addressing 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-enable-LIP-reset 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-enable-LIP-full-login 1 (enable) 1 (enable) 1 (enable) 1 (enable)

hba0-enable-target-reset 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-enable-database-storage 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-scsi-reset-delay 5000 (millisec) 5000 (millisec) 5000 (millisec) 5000 (millisec)

hba0-link-down-error 1 (enable) 0 (disable) 0 (disable) 1 (enable)

hba0-port-down-retry-count 30 5 5 5

hba0-loop-down-timeout 60 (sec) 60 (sec) 60 (sec) 60 (sec)


3

3-20


maximum setting might be less, depending on the size of the firmware.

hba0-execution- throttle — Maximum number of commands (1 to 65635) sent to the LUN by the firmware. Exceeding a device’s capabilities causes unnecessary command retries, which impact performance.

hba0-login-retry-count — Maximum number (0 to 255) of retries to attempt when login into a device fails. Large values can cause long delays during initialization.

hba0-enable-adapter-hard-loop-ID — Enables/disables the hard loop ID and activates (if enabled) the setting for variable hba0-adapter-hard-loop-ID. (See the next item.)

hba0-adapter-hard-loop-ID — Sets (if activated) the hard loop ID (in the range 1 to 125) for the HBA during the Loop Initialization Process (LIP). If hba0-enable-adapter-hard-loop-ID and hba0-adapter-hard-loop-ID are not set as shown in Table 3-4, the LIP might fail and the host might not recognize the Symmetrix. These variables become crucial in a hub environment, since no device (Symmetrix target or host bus adapter) can have the same hard loop ID. The host HBA is conventionally assigned the highest Hard Loop ID, starting from 125 and working down (124, 123, 122, etc.). The Symmetrix is conventionally assigned a lowest Hard Loop ID for each port, starting with 0 and working up (1, 2, 3, etc.).

Example:

The following example is a configuration for three QLA2100F HBAs with separate Hard Loop IDs:

# Adapter hard loop ID.# Range: 0 - 126hba0-adapter-hard-loop-ID=125;hba1-adapter-hard-loop-ID=124;hba2-adapter-hard-loop-ID=123;

hba0-login-timeout — Sets the login timeout (in seconds).

hba0-enable-extended-logging — Enables/disables the driver extended error reporting capabilities.

hba0-enable-64bit-addressing — Enables/disables the adapter to directly access memory above 4 gigabytes with 64-bit Direct Memory Access addressing.



hba0-enable-LIP-reset — Enables/disables the adapter to issue a LIP reset during Fibre Channel reset.

Only one of the variables hba0-enable-LIP-reset, hba0-enable-LIP-full-login, and hba0-enable-target-reset should be enabled at the same time.

hba0-enable-LIP-full-login — Enables/disables the adapter to issue a LIP full login reset during Fibre Channel reset. (See the note below hba0-enable-LIP-reset.)

hba0-enable-target-reset — Enables/disables the adapter to issue a LIP target reset during Fibre Channel reset. (See the note below hba0-enable-LIP-reset.)

hba0-enable-database-storage — Enables/disables the driver to save device position on the Fibre Channel bus.

hba0-scsi-reset-delay — Delay after a reset before sending commands to the devices on the Fibre Channel bus.

hba0-link-down-error — Disables all link_down time out values. The sd driver will not be notified of any and error conditions if the qla2100 driver detects a link_down condition. If the Symmetrix goes off line or the link with the host is broken for any reason, the qla2100 driver holds all pending I/Os indefinitely until the link is restored or the Symmetrix rejoins the loop. In a Power Path or Veritas DMP environment, this variable should be enabled (1) so the PowerPath or Veritas DMP driver will be notified of any error conditions.

hba0-port-down-retry-count — Number of command retries to be done when devices are not responding on the Fibre Channel bus. Large values might cause long delays for fail over software to detect a failing device.

hba0-loop-down-timeout — Time the driver waits for a Fibre Channel loop to come up before reporting the failure. Small values might report transient errors that should be ignored.Operation in a Solaris environment requires that some parameters in the file /etc/system first be modified, as described in the following steps.

sd.conf Symmetrix devices are addressed using target IDs and LUNs. By default, Solaris searches only for target IDs on the bus. You must modify the file /kernel/drv/sd.conf to include the correct definitions for each target ID that needs to support multiple LUNs.


3

3-22




Devices accessed via Fibre Channel using the Qlogic driver are addressed behind a single target ID with up to 256 LUNs. (This differs from existing SCSI device addressing, which might have multiple targets and LUNS.) In the standard Symmetrix device definition file, target 0 should have 256 LUNs, and all other targets (1 through 125) have a LUN 0 only.

Edit the sd.conf file to list all targets and all LUNs that might be addressed. The Target ID needed to address a device is determined by the Fibre Channel Arbitrated Loop Physical Address (AL_PA). A Loop_ID of 00 (AL_PA of EF) will have LUNS behind Target ID 0, Loop_ID 01 has LUNs on target ID 1, and so on. Refer to Appendix C for the available addressing modes.

Since each Fibre Channel port can have only one loop ID (or AL_PA), all devices accessed through a port will have the same target ID. If you need to access existing devices that previously had multiple target IDs, be aware of changes required for raw device addressing.

For example:



0 0 0 0

0 1 0 1

0 15 0 15

1 0 0 16

2 0 0 32

15 0 0 240




Sample sd.conf file:name=”sd” class=”scsi”target=0 lun=0;name=”sd” class=”scsi”target=0 lun=1;..name=”sd” class=”scsi”target=0 lun=255;name=”sd” class=”scsi”target=1 lun=0;name=”sd” class=”scsi”target=2 lun=0;..name=”sd” class=”scsi”target=125 lun=0;

Device definition files are available on EMC’s FTP server, ftp.emc.com, in /pub/symm3000/solaris. The file sd.conf.fibre is a device definition file for Fibre Channel devices. Change the file name to sd.conf and copy it to the /kernel/drv directory.


/etc/system Operation in a Solaris environment requires that some parameters in the file /etc/system first be modified, as described in the following steps.






3

3-24






Partitioning and Labeling Devices



If upgrading an existing Symmetrix-to-host SCSI interface to Fibre Channel, see Appendix B.

Bit Mask Meaning


4 0x10 Link enable









Host Configuration with Emulex HBAThis section describes the tasks required to install one or more Emulex host bus adapters into a Sun Solaris host and configure the host for Symmetrix Fibre Channel. (Refer to Table 3-1 on page 3-3 for approved HBAs.)

Symmetrix Fibre Channel does not currently support the mixing of different types of HBA in a single server.

Installing the HBA Set the jumpers on the LP7000E-EMC as shown in Figure 3-1 to enable it for use with the Solaris host.

With host system power removed, install the HBA and make cable connections. The card installs into a single PCI bus slot.

Figure 3-1 LP7000E-EMC Jumpers

1 32

JX2

1 32

JX1

Host Configuration with Emulex HBA 3-25

3

3-26


Installing the HBA I/O Driver

Using the LP7000E-EMC adapter with the Solaris Operating system requires HBA I/O driver software. The driver functions at a layer below the Solaris SCSI driver to present Fibre Channel devices to the operating system as if they were standard SCSI devices.


1. Be sure you have the latest qualified driver software. If necessary, you can download the driver from the Emulex website (as described later in this procedure). Refer to release notes provided with the driver for information that might be unique to new driver revisions.


Downloading andInstalling a New Driverfrom the Emulex Web

Site

Use the following procedure to download the Emulex driver from the Emulex web site and perform a first-time install:


http://www.emulex.com/ts/fc/index.htm/LP7000E-EMC/sparc/version-3.38

2. Download lpfc-sparc-tar to the host.

3. Type tar xvf lpfc-sparc-tar <Enter>.

4. Type pkgadd -d . <Enter>, to install the new driver.




New Web Downloading and Installing a New Driver from the Emulex Web Site on page 3-26


Upgrade Web Downloading and Installing a Driver Upgrade from the Emulex Web Site on page 3-27





Use the following procedure to load the driver from the Emulex CD-ROM, and perform a first time install.

1. Insert the Emulex CD-ROM.

2. Change to the directory /cdrom/emulex/sparc.

3. Copy the file lpfc-sparc-tar to the host.






Emulex Web Site

Use the following procedure to download the driver from the Emulex web site, and perform a Fibre Channel driver upgrade.

1. Back up the file /kernel/drv/lpfc.conf.

2. Type pkgrm lpfc <Enter>, to remove the old driver.


http://www.emulex.com/ts/fc/index.htm/LP7000E-EMC/sparc/version-3.38

4. Download the file lpfc-sparc-tar to the host.






CD-ROM

Use the following procedure to load the Emulex driver from the Emulex CD-ROM, and perform a Fibre Channel drive upgrade:

1. Back up the file /kernel/drv/lpfc.conf.

2. Type pkgrm lpfc <Enter>, to remove the old driver.

3. Insert the Emulex CD-ROM.

4. Change to the directory /cdrom/emulex/sparc.

5. Copy the file lpfc-sparc-tar to the host.


3

3-28








To insure smooth integration and maximum performance from the host and Symmetrix, you must edit these files (as described in detail later):

• Emulex driver configuration file lpfc.conf — Refer to lpfc.conf below

• Host sd driver configuration file sd.conf — Refer to sd.conf on page 3-33

• System specification file etc/system — Refer to etc/system on page 3-35


lpfc.conf The configuration file (lpfc.conf) is created automatically by pkgadd. The file contains important information about how the driver should behave. If necessary, edit lpfc.conf as shown in Table 3-5.

Changes to lpfc.conf will not take effect until the host is rebooted.

Table 3-4 lists the required settings for the configuration file variables. Descriptions of the variables follow the table.



Table 3-5 /kernel/drv/lpfc.conf Settings for Solaris SPARC Host


Recommended Setting

If No PowerPath If PowerPath

identify-self 1 1 1

log-verbose 0 0x10 0x10

log-only 1 1 1

automap 1 1 1

fcp-on 1 1 1

device-report 1 1 1

lun-queue-depth 30 20 20

tgt-queue-depth 0 512 512

no-device-delay 1000000 1000000 1000000

network-on N/A N/A N/A

xmt-que-size 256 256 256

scan-down 1 1 1

linkdown-tmo 30 0 30

nodev-holdio 0 1 0

num-iocbs 512 2048 2048

num-bufs 512 1024 1024

topology 4 4 4

ip-class 3 3 3

fcp-class 3 3 3

sli 2 2 2

fabric-reg 1 1 1

use-adisc 0 0 0

fcpfabric-tmo 0 0 0

continued on next page


3

3-30


Descriptions of lpfc.conf Variables:

identify-self — Forces the driver to report itself at boot-time.

log-verbose — Sets a bit mask to record specific types of verbose messages:

log-only — Setting the value to 0 causes log messages print on the console and to be logged to syslog (which may send them to the console again if it is configured to do so). Setting log-only to 1 causes log messages to go to syslog only.

automap — Is always 1 in an arbitrated loop environment.

fcp-on— Is always 1 in an arbitrated loop environment.

device-report — Reports (if set to 1) on SCSI devices as they are discovered/re-discovered.

post-ip-buf 128 128 128

avoid-resets 1 1 1

zone-rscn 0 0 0

ack0 0 0 0

class-code 0x00020000 0x00020000 0x00020000

use-lomempages 0 0 0

Table 3-5 /kernel/drv/lpfc.conf Settings for Solaris SPARC Host (continued)


Recommended Setting

If No PowerPath If PowerPath

0x1 ELS events

0x2 Device Discovery events

0x4 Mailbox Command events

0x8 Miscellaneous events

0x10 Link Attention events

0x20 IP events

0x40 FCP events

0x80 Node table events



lun-queue-depth — Number of outstanding commands per FCP LUN. This value is global, affecting each LUN recognized by the driver, but it may be overridden on a per-LUN basis (see lpfcNtM-lun-throttle below). It might be a good idea to configure RAID arrays using the per-LUN tunable throttles.

tgt-queue-depth — Number of outstanding commands per FCP target. This value is global, affecting each target recognized by the driver, but it may be overridden on a per-target basis (see lpfcNtM-tgt-throttle below). RAID arrays may want to be configured using the per-target tunable throttles.

lpfcNtM-lun-throttle — Maximum number of outstanding commands to permit for each LUN of an FCP target that supports multiple LUNs. The default throttle for the number of commands outstanding to a single LUN of a multiple-LUN target is the lun-queue-depth. For a target that supports multiple LUNs, it may be useful to specify a LUN throttle that differs from the default.

Example — lpfc0t17-lun-throttle=31 means that each LUN on target 17, interface lpfc0 should be allowed up to 31 simultaneous outstanding commands.

lpfcNtM-tgt-throttle — Maximum number of outstanding commands to permit for a FCP target. By default, target throttle is disabled.

Example — lpfc0t17-tgt-throttle=256 means that target 17, interface lpfc0 should be allowed up to 256 simultaneous outstanding commands.

no-device-delay — Interval in microseconds (0 to 30000000) between deciding to fail back an I/O because there is no way to communicate with its particular device (for example, due to device failure) and the actual fail back. A value of zero implies no delay.

Cautions:

• The system generally rounds values smaller than 10,000 microseconds (10 milliseconds) up to roughly 10 milliseconds, depending on the system clock rate.

• Setting a long delay value might permit I/O to build up, each with a pending timeout, possibly resulting in exhaustion of critical Solaris kernel resources. In this case, you might see a fatal message, such as PANIC — Timeout table overflow. Note that this value can have an impact on the speed with


3

3-32


which a system can shut down with I/Os pending and with the HBA unable to communicate with the loop (if a cable is pulled, for example).

network-on — Is 1 if networking is enabled, 0 if disabled. This variable is set during installation of the driver via pkgadd.

xmt-que-size — Size of the transmit queue (128 to 10240) for mbufs.

scan-down — Determines scanning of AL_PAs. If enabled (1), the lpfc driver uses an inverted AL_PA map, effectively scanning AL_PAs from high to low, as specified in the FC-AL annex.

linkdown-tmo — Time (1 to 255 seconds) the driver waits to begin linkdown processing when a cable has been pulled or the link has otherwise become inaccessible. Linkdown processing includes failing back commands to the target driver that have been waiting around for the link to come back up.

Small values of the link-down timer cause the link to appear to "bounce", while large values of the timer can delay failover in a fault-tolerant environment. Units are in seconds. A value of 0 means never failback commands until the link comes up.

nodev-holdio — If enabled (1), the lpfc driver holds all I/O errors on devices that disappear until they come back. If disabled (0), the lpfc driver return errors with no-device-delay.

num-iocbs — Number of iocb buffers to allocate (128 to 10240).

num-bufs — Number of ELS buffers to allocate (128 to 4096). ELS buffers are needed to support Fibre Channel Extended Link Services. ELS buffers are also used for SLI-2 FCP buffers (one per FCP command) and Mailbox commands.

topology — Link topology for initialized link. The value is always 4 in an arbitrated loop environment.

ip-class — Fibre Channel class (2 or 3) to use for the IP protocol.

fcp-class — Fibre Channel class (2 or 3) to use for the FCP protocol.

sli — Service Level Interface; the lpfc driver supports SLI-1 (1) or SLI-2 (2) device driver interfaces.

fabric-reg — Has no function in an arbitrated loop environment.

use-adisc — If 1, ADISC is used for FCP rediscovery; if 2, PLOGI is used.



fcpfabric-tmo — Has no function in an arbitrated loop environment.

post-ip-buf — Number of 4K STREAMS buffers to post to an IP ring.

avoid-resets — If enabled (1), the target driver does not send BUS RESET commands down to the HBA driver.

zone-rscn — Has no function in an arbitrated loop environment.

ack0 — Determines Class 2 acknowledgement: ACK0 (1) or ACK1 (0).

class-code — Temporary configuration flag that resolves a hardware interrupt issue with the current release of Solaris 2.6.

CAUTION!Do not change (or comment out) the class-code setting without approval from your EMC Customer Engineer.

sd.conf Symmetrix devices are addressed using target IDs and LUNs. By default, Solaris searches only for target IDs on the bus. LUN addressing is required in addition to target ID addressing. You must modify the file /kernel/drv/sd.conf to have the following definitions for each target ID that needs to support multiple LUNs.



Devices accessed via Fibre Channel using the Emulex LP7000E-EMC adapter and Emulex driver are addressed behind a single target ID with up to 256 LUNs. (This differs from existing SCSI device addressing, which can have multiple targets and LUNS.)

Edit sd.conf to list all targets and all LUNs that might be addressed. The Target ID needed to address a device is determined by the Fibre Channel Arbitrated Loop Physical Address (AL_PA). A Loop_ID of 00 (AL_PA of EF) will have LUNS behind Target ID 0, Loop_ID 01 has LUNs on target ID 1, and so on. Refer to Appendix C for the available addressing modes.

Since each Fibre Channel port can have only one loop ID (or AL_PA), all devices accessed through a port will have the same target ID. If you need to access existing devices that previously had multiple


3

3-34


target IDs, you must be aware of changes required for raw device addressing.

For example:



Sample sd.conf file:name=”sd” parent=”lpfc” target=0 lun=0;name=”sd” parent=”lpfc” target=0 lun=1;name=”sd” parent=”lpfc” target=0 lun=2;..name=”sd” parent=”lpfc” target=0 lun=31;name=”sd” parent=”lpfc” target=1 lun=0;name=”sd” parent=”lpfc” target=2 lun=0;..name=”sd” parent=”lpfc” target=124 lun=0;


0 0 0 0

0 1 0 1

0 15 0 15

1 0 0 16

1 15 0 31



etc/system Operation in a Solaris environment requires that some parameters in the file /etc/system first be modified, as described in the following steps.









Bit Mask Meaning


4 0x10 Link enable








3

3-36


Partitioning and Labeling Devices



If upgrading an existing Symmetrix-to-host SCSI interface to Fibre Channel, see the host-specific procedures in Appendix B.



Partitioning and Labeling New DevicesUse the format command to partition and label new Fibre Channel devices. The devices will appear under /dev/dsk.

To partition and label new devices:

1. At the root prompt, type format <Enter>.

The host searches for all disks and displays a list, placing all unlabeled disks at the beginning of the list.

2. At the Specify Disk prompt, enter the number of the first EMC drive.

3. The FORMAT MENU appears. At the format prompt, type label <Enter>.

4. At the Disk not labeled. Label it now? prompt, type Y <Enter>.

5. Type disk <Enter> at the prompt to display a list of the disks.

6. Repeat steps 2 through 5 for all Symmetrix disks.

Managing PhysicalVolumes and Creating

Filesystems

Physical volumes can be managed under Solstice DiskSuite or Veritas Volume Manager in the same manner as devices accessed through a standard SCSI interface. Follow the instructions for volume manager functions in the Symmetrix Open Systems Environment Product Guide.

If you plan to use raw devices, there is no need to create filesystems for each device. Otherwise, create new filesystems for each device as described in the Symmetrix Open Systems Environment Product Guide.

Partitioning and Labeling New Devices 3-37

3

3-38


Sun Hub Configuration Guidelines

Sun Hub Support Symmetrix Fibre Channel supports Sun hub model X6732A (seven shortwave ports, no GBICs). Refer to Loops with Hubs on page 1-22 for descriptions of various hub configurations.

Sun Hub Configuration Guidelines

The following paragraphs provide guidelines and limitations for using hubs in a Sun Solaris and Symmetrix Fibre Channel storage network.

Solaris OperatingSystem

Solaris version is 2.5.1 or 2.6 is required.

Connections Connections supported per hub:

• 1 to 6 host connections• 1 to 6 Symmetrix connections

Host and Symmetrix connections can be added to or removed from the hub on line.

Cascaded Hubs Hub-to-hub connections are supported; however, more than two hubs in one cascaded loop are not supported.

Physical connections to a hub should be made in adjacent port connectors. Do not leave open connectors between cable connections.

Longwave GBICs are not supported.

Multiple Host Systems Up to six hosts can be connected to the loop, as long as there is some consideration for total I/O demand. Estimate each host’s I/O per second using a performance analysis tool such as VxSTAT, SAR, or Symmetrix Manager. Host nodes can be added to the hub loop within the suggested limit of a combined estimated 1000 IOPS (8KB block size).

Volume Sharing Access to the same Symmetrix device through more than one Fibre Channel-connected host is supported with VERITAS VxVM version 2.4.1.

Cable Lengths There are no restrictions on the mixing of Fibre Channel cable lengths on a hub. As long as each link does not exceed its allowed length, links of varying lengths can be mixed.



Software Support Host software and Symmetrix software supported in non-hub Fibre Channel topologies is also supported with hubs.

Diagnostic andMaintenance

Repair and System recovery from a hub failure can be done on line with a properly configured high-availability system.

Sun Hub Configuration Guidelines 3-39

3

3-40



4

This chapter provides information specific to Windows NT hosts connecting to Symmetrix over Fibre Channel arbitrated loop. (Chapter 12 describes Windows NT support over fabric.) The chapter includes the following sections:

• Windows NT Arbitrated Loop Environment.................................4-2• Host Connectivity ..............................................................................4-3• Symmetrix Configuration .................................................................4-6• Host Operating System Configuration ...........................................4-7• Host Configuration with Compaq HBA.........................................4-8• Host Configuration with HP A5246A HBA.................................4-10• Host Configuration with HP D8602A (Tachlite) HBA................4-12• Host Configuration with Qlogic HBAs.........................................4-16• Host Configuration with Emulex HBAs.......................................4-22


Windows NT Host onArbitrated Loop

Windows NT Host on Arbitrated Loop 4-1

4

4-2

Windows NT Host on Arbitrated Loop

Windows NT Arbitrated Loop EnvironmentThe following lists some Symmetrix Fibre Channel support information specific to the Windows NT host environment.


Refer to Table 4-1 on page 4-3 and to Host Operating System Configuration on page 4-7.

Supported Software Symmetrix Fibre Channel supports Microsoft® Cluster Server (MSCS—also known as Wolfpack) for direct-connect arbitrated loop only. (Hub configurations are not yet supported).

Supported Hardware • Hosts and host bus adapters — Symmetrix Fibre Channel supports up to eight Fibre Channel HBAs per host (depending on the number of available PCI slots). Refer to Table 4-1 on page 4-3.

• Hubs — Windows NT hosts on Symmetrix Fibre Channel support Vixel hub models 1000 (7 shortwave ports, no GBICs) and 2000 (12 shortwave ports, no GBICs). Refer to Loops with Hubs on page 1-22 for descriptions of various hub configurations.


Addressing Windows NT SCSI drivers and host adapter drivers use SCSI-2 device access protocol in addressing Fibre Channel devices. SCSI-3 Array Controller addressing modes are not supported. The peripheral device access mode is supported in Symmetrix to address up to 128 logical devices per port (up to 8 with an HP or Compaq adapter). Refer to Appendix C for the available addressing modes.


4Windows NT Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with the Windows NT hosts shown in Table 4-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.


Table 4-1 HBAs for Windows NT/FC-AL Hosts

Host TypeQualified OS Version a Host Bus Adapter

Firmware/BIOS Rev

Driver Version

Max LUNs

Compaq Proliant 5000, 5500, 6000, 6500, 7000

Windows NT 4.0 with SP 3, 4, or 5

Compaq FC 223180-B21 b N/A 4.04 8

Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

Dell PowerEdge 6100/6300


Qlogic QLA2100F-EMC 1.37 6.16 128

Qlogic QLA2200F-EMC See note e See note e 128

Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

HP Netserver LH, LH3, LH4, LH-II, LXr, LXr Pro8, LXr8000


HP A5246A b N/A 2.09d 8

HP D8602A d N/A 1.12 128

Qlogic QLA2100F-EMC 1.37 6.16 128


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128



4

4-4


IBM Netfinity 5000, 5500/5500M10, 7000/7000M10


Qlogic QLA2100F-EMC 1.37 6.16 128


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

NCR 4300, 4380, 4400 Windows NT 4.0 with SP 3, 4, or 5

Qlogic QLA2100F-EMC 1.37 6.16 128


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

Siemens PRIMERGY 7xxc, 8xxx


Qlogic QLA2100F-EMC 1.37 6.16 128


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

Unisys Aquanta QS/2V Windows NT 4.0 with SP 3, 4, or 5

Qlogic QLA2100F-EMC 1.37 6.16 128


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

NEC Express 5800/ 140 Ma


Qlogic QLA2100F-EMC 1.37 6.16 128



Table 4-1 HBAs for Windows NT/FC-AL Hosts (continued)


Firmware/BIOS Rev

Driver Version

Max LUNs



a. SP stands for Service Pack.

b. Does not support PowerPath.

c. Requires PRIMERGY firmware 1.07.887 version 4.05.

d. Supports PowerPath 1.5 only.

e. Contact your EMC representative.

Driver software for Windows NT hosts is provided with each HBA. Standard NT driver installation procedures enable use of the HBAs.

The Fibre Channel Adapter driver functions as a device driver layer below the standard SCSI adapter driver; therefore, the Fibre Channel interface is transparent to the Windows NT disk administration system.

NEC Express 5800/ 140 Ma (continued)


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

Table 4-1 HBAs for Windows NT/FC-AL Hosts (continued)


Firmware/BIOS Rev

Driver Version

Max LUNs


4

4-6


Symmetrix ConfigurationSymmetrix configuration is done by an EMC Customer Engineer (CE) via the Symmetrix service processor. The CE will configure your Symmetrix with the following settings for each Fibre Channel port.


b. The Disk Array Mode and Volume Set Addressing bits must be enabled when connecting to the HP D8602A (Tachlite) HBA.

Table 4-2 Symmetrix FC-AL Configuration for Windows NT Hosts

Parameter Setting

Disk Array Mode (A-bit) Disabled a, b

Volume Set Addressing (V-bit) Disabled a, b


Loop ID 00



Common Serial Number (C-bit) Disabled


not used




Host Operating System ConfigurationConnecting a Windows NT host to Symmetrix over Fibre Channel requires editing the Windows NT registry, as follows:

1. Run Winnt\system32\Regedt32.exe and display the device parameters under the following path.

2. Look for the TimeOutValue entry in the right pane of the registry editor window:

• If the TimeOutValue exists, double-click it, then go to step 3.

• If the TimeOutValue does not exist:

a. Select Add Value from the Edit menu.

b. In the Value Name box, type TimeOutValue (exactly as shown).

c. For the data type, select REG_DWORD from the pull-down menu.

d. Click OK, then go to step 3.

3. In the DWORD Editor window:

a. Click decimal in the radix box.

b. Change the value in the data box to 60.

4. Click OK.

5. Close the registry editor.

6. Reboot the host.

H_KEY_LOCAL_MACHINESYSTEM

CurrentControlSetServices

Disk

Host Operating System Configuration 4-7

4

4-8


Host Configuration with Compaq HBAThis section describes the procedures required to install one or more Compaq host bus adapters into a Windows NT host and configure the host for Symmetrix Fibre Channel. (Refer to Table 4-1 on page 4-3 for approved HBAs.)

Before installing the HBA, be sure to edit the Windows NT registry as described under Host Operating System Configuration on page 4-7.

Installing the HBA With host system power removed, install the adapter card and make cable connections. (The card has no user-configurable jumpers or switches.) Reapply power and allow the system to boot normally.


To use Symmetrix disks with a Windows NT host, you need a Fibre Channel host adapter driver. You can obtain this driver directly from the manufacturer of your Fibre Channel adapter card. The driver must be installed and configured prior to partitioning the Symmetrix disks.

To configure the driver, follow these steps:

1. Boot the host with Windows NT 4.0.

2. Open the Control Panel and double-click on the SCSI Adapter icon.

3. Select the Drivers tab.

4. Click on the Add button to display the SCSI Adapter drivers database.

5. Select HAVE DISK.

6. Locate the appropriate driver for your adapter card and continue with the install procedure.

7. Reboot the host. It should recognize all new host adapter cards.

After rebooting you can verify that the driver installed and started by checking the Control Panel -> SCSI Adapter -> Drivers window for a statement similar to the following:

SCSI driver for Compaq Fibre Channel Controller (Started)

The driver is now loaded and the adapter is available to the system.





Follow the instructions for configuring and partitioning Symmetrix devices under Windows NT Environment in the Symmetrix Open Systems Environment Product Guide (Volume II).

Recognizing LUNs Symmetrix devices are addressed on the SCSI bus using SCSI target IDs and SCSI LUNs. Each target ID can have up to 128 LUNs associated with it. The Target ID needed to address a device is determined by the Fibre Channel Arbitrated Loop Physical Address (AL_PA). A Loop_ID of 00 (AL_PA of EF) will have LUNS behind Target ID 0, Loop_ID 01 has LUNs behind target ID 1, and so on. Refer to Appendix C for the available addressing modes.


The first time a disk appears on a Windows NT system, the Windows NT Disk Administrator writes a signature to that disk. The signature is a unique 32-bit number for Windows NT to use as an internal identification number for that disk. Windows NT uses the signature to associate drive letters with a disk and disks with volume sets. The Disk Administrator can reassociate the drive letter with the correct disk even if you reconfigure device channels or change the disk target and LUN.

Windows NT searches for disks on each host adapter in Target ID/LUN sequence. Adapters are also accessed in a particular sequence that is unique to each host. This process determines the order in which the disk devices are assigned drive letters.

Drive letters can be reassigned manually using Disk Administrator after a new signature is written.

Once all disk signatures are written, devices are ready to be used by Windows NT. (Follow the instructions for configuring and partitioning Symmetrix devices under Windows NT Environment in the Symmetrix Open Systems Environment Product Guide, Volume II.)

Host Configuration with Compaq HBA 4-9

4

4-10


Host Configuration with HP A5246A HBAThis section describes the procedures required to install one or more HP host bus adapters into a Windows NT host and configure the host for Symmetrix Fibre Channel. (Refer to Table 4-1 on page 4-3 for approved HBAs.)


Installing the HBA With host system power removed, install the adapter card and make cable connections. Reapply power and allow the system to boot normally. (The card has no user-configurable jumpers or switches.)


To use Symmetrix disks with a Windows NT host, you need a Fibre Channel host adapter driver, which can be obtained from Hewlett Packard. The driver must be installed and configured prior to partitioning the Symmetrix disks.









After rebooting you can verify that the driver installed and started by checking the Control Panel, SCSI Adapter, Drivers window for a statement similar to the following:

SCSI driver for HP HHBA-5000 Fibre Channel Controller (Started)













Host Configuration with HP A5246A HBA 4-11

4

4-12


Host Configuration with HP D8602A (Tachlite) HBAThis section describes the procedures required to install one or more HP host bus adapters into a Windows NT host and configure the host for Symmetrix Fibre Channel. (Refer to Table 4-1 on page 4-3 for approved HBAs.)

The HP D8602A requires that the Disk Array Mode and Volume Set Addressing bits be enabled. (Refer to Table 4-2 on page 4-6.)


Installing the HBA With host system power removed, install the adapter card and make cable connections. Reapply power and allow the system to boot normally. (The card has no user-configurable jumpers or switches.)


To use Symmetrix disks with a Windows NT host, you need a Fibre Channel host adapter driver, which can be obtained from Hewlett Packard. The driver must be installed and configured prior to partitioning the Symmetrix disks.









After rebooting you can verify that the driver installed and started by checking the Control Panel, SCSI Adapter, Drivers window for a statement similar to the following:

SCSI driver for HP HHBA-5100 Fibre Channel Controller (Started)




Registry Settings The HP D8602A HBA requires that these two settings be edited in the Windows NT registry:

• System Pages — Determines the number of memory pages Windows NT allocates.

• Number of Requests — Determines the number of requests the HBA queues.

Newer versions of the D8602A driver include an EMC icon that you can click to automatically make these registry settings. After installing the driver, you should follow the below procedure to verify that the correct settings have been made.

Follow this procedure to modify the settings:

1. Run Winnt\system32\Regedt32.exe and display the parameters under this path (noting that Session Manager is the entry with a space between the words, not SessionManager):

If the Registry Editor window is not split into left and right panes, click on the View menu, and make sure Tree and Data is checked.

2. In the right pane of the Registry window, double-click on the SystemPages value.

3. In the DWORD Editor window, select Decimal in the Radix box.

4. In the Data box, type 50000.

5. Click OK.


CurrentControlSetControl

Session ManagerMemory Management

Host Configuration with HP D8602A (Tachlite) HBA 4-13

4

4-14


6. Go back to the Services level (the fourth line below), then follow the path as shown:

7. In the right pane of the Registry window, double-click on the NumberOfRequests value.

8. In the DWORD Editor window, select Decimal in the Radix box.

9. In the Data box, type 128.

10. Click OK.

11. Exit the Registry Editor, then reboot the host. (This is necessary for the changes to take effect.)




Recognizing LUNs Because Tachlite uses the volume set addressing mode on Symmetrix, disk devices must be addressed in a similar manner as SCSI devices. Each target ID can have 8 LUNs behind it; for example, 00 through 07, 10 through 17, and so on. Unlike SCSI HBAs, Tachlite does not reserve Target ID 7 for itself.

Refer to Appendix C for the available addressing modes.


The first time a disk appears on a Windows NT system, the Windows NT Disk Administrator writes a signature to that disk. The signature



HHBA5100Parameters

Device "n"



is a unique 32-bit number for Windows NT to use as an internal identification number for that disk. Windows NT uses the signature to associate drive letters with a disk and disks with volume sets. The Disk Administrator can reassociate the drive letter with the correct disk even if you reconfigure device channels or change the disk target and LUN.




Host Configuration with HP D8602A (Tachlite) HBA 4-15

4

4-16


Host Configuration with Qlogic HBAsThis section describes the procedures required to install one or more Qlogic QLA2100F-EMC or QLA2200F-EMC host bus adapters into a Windows NT host and configure the host for Symmetrix Fibre Channel. (Refer to Table 4-1 on page 4-3 for approved HBAs.)



Installing the HBA Most of the Fibre Channel host bus adapters supported by EMC do not require any special hardware configuration settings. However, the Qlogic HBA has an on-board utility called Fast!UTIL that is used to configure the adapter for use. In addition, I/O driver software installation is required.

1. With host system power removed, install the HBA. The card installs into a single PCI bus slot.

2. Install the cable connections between the host and Symmetrix.

3. Reapply power and allow the system to boot normally.

EMC NVRAM Settings

EMC recommends configuring the Qlogic BIOS settings with the EMC-approved NVRAM settings file. This file contains all of the BIOS settings for the Qlogic adapters that have been tested and approved for connection to Symmetrix.

You can also change the Qlogic BIOS settings manually, but this can cause undesired results if set incorrectly. Refer to Configuring the HBA on page 4-17.

To set the Qlogic BIOS using the NVRAM file:

1. Format a 3.5-inch diskette and copy all files from the BIOS directory on the Qlogic CD-ROM to the diskette.

2. Reboot your Windows NT host system using a DOS diskette.



3. At the A:\> prompt, insert the diskette that contains the Qlogic BIOS files (created in step 1), and type QL2XUTIL.EXE /L /F <Enter>, to run the flash utility with the /L and /F parameters.

Do not attempt to run this procedure from a command prompt window.

4. When the procedure has finished, remove the diskette and reboot the host.

Configuring the HBA During system boot, a banner is displayed for each Qlogic adapter present in the system. Perform the following procedure to configure each Qlogic HBA.

This procedure applies to BIOS version 1.18 or higher.

CAUTION!Any time the default settings for the adapter are chosen via Fast!Util, the NVRAM settings specific to EMC are overwritten, and the above procedure must be repeated. EMC recommends that you do not select the default adapter settings option from Fast!Util.

1. Press <Alt><Q> when prompted Press <ALt-Q> for

Fast!UTIL.

2. After the Fast!UTIL program loads, the display will depend on whether there are multiple Qlogic HBAs installed:

• If there is only one Qlogic HBA, a Fast! UTIL Options menu will be displayed.

• If there are multiple Qlogic HBAs, a list of addresses occupied by those HBAs will be displayed. Using the arrow keys, select the desired HBA and press <Enter>. The Fast!UTIL Options menu will then be displayed.

3. Select Configuration Settings from the Fast! UTIL Options menu.

4. Select Host Adapter Settings from the Configuration Settings menu.

5. Use the arrow keys to select Host Adapter Bios and press <Enter> to change the setting to Disabled.

Host Configuration with Qlogic HBAs 4-17

4

4-18


6. If performance is a concern, use the arrow keys to select Frame Size and press <Enter> to change the setting. Use the arrow keys again to select the desired frame size, then press <Enter>.

7. Use the arrow keys to select Adapter Hard Loop ID and press <Enter> to change the setting to Disabled.

8. Press <Esc> to return to the Configuration Settings menu.

9. Select Selectable Boot Settings from the Configuration Settings menu. Make sure Selectable Boot Device is Disabled. If it is not, press <Enter> to change the setting.


11. Select Advanced Adapter Settings from the Configuration Settings menu.

12. If the HBA’s BIOS is version 1.32 or higher, go to step 13. If the BIOS is a lower version, press <Alt><Q> at the Advanced Adapter Settings menu to enter edit mode.

13. Use the arrow keys to select LUNs per Target. Press <Enter> and use the arrow keys to select the number of LUNs you will be accessing, then press <Enter> again.

The current Symmetrix/Qlogic Fibre Channel implementation supports a maximum of 128 LUNs.

14. Select Enable LIP Full Login and press <Enter> to change the setting to Yes.

15. Select Enable Target Reset and press <Enter> to change the setting to Yes.

16. If performance is a concern, select Execution Throttle and press <Enter> to change the setting. Enter a numeric value up to 256 in the red box under New.


18. Press <Esc> to return to the Fast! UTIL Options menu.

19. When prompted to save changes made to the current adapter, select Save Changes.

20. If you have more adapters to configure, choose Select Host Adapter and repeat steps 2 through 19 for each adapter.

21. Press <Esc> to exit Fast!UTIL.



22. Reboot the host.


To use Symmetrix disks with a Windows NT host, you need a Fibre Channel host adapter driver. The driver must be installed and configured prior to partitioning the Symmetrix disks.

Where to Find theDriver

The driver for Qlogic HBAs on Windows NT hosts is located in the \NT directory on the Qlogic CD-ROM that accompanied the Fibre Channel HBA.

You can find driver updates on the Qlogic website, www.qlc.com.

1. From the main page, click on the Adapter drivers & utilities download box.

2. On the Host Adapter Drivers & Utilities page, click on the adapter type you want to download.

3. Scroll down the displayed list and click on EMC Approved Drivers.

4. On the list of EMC drivers, click on Windows NT Driver.

5. Download the driver.

Installation Procedure To install the driver, follow these steps:




4. Click on the Add button to display the SCSI Adapter Drivers database.


6. Enter the drive letter of the location of the driver, followed by \nt; for example, if installing from a CD-ROM in drive D, type d:\nt <Enter>.

7. Select the driver for the Qlogic adapter and click on OK to install it.



4

4-20


After rebooting, you can verify that the driver installed and started by checking the Control Panel, SCSI Adapter, Drivers window for a statement similar to the following:

SCSI driver for Qlogic Fibre Channel Adapter (Started)


Modifications for Service Pack 4 or 5

Windows NT 4.0 Service Packs 4 and 5 have added support configuration for large numbers of devices. If Service Pack 4 or 5 has been installed, it is necessary to make a registry change to prevent the Qlogic driver from trying to handle Large LUN configurations (and allow Windows NT to handle Large LUN configurations).

To disable LargeLuns support:

1. Edit the registry for the Qlogic adapter driver. Run Winnt\system32\Regedt32.exe and display the device parameters under the following path.

2. Locate registry value LargeLuns in the right pane of the registry window.

3. If the value of LargeLuns is not 0, double-click LargeLuns to change the value to 0.

4. Exit the registry editor and reboot the host (necessary for the changes to take effect).






Ql2100 (or Ql2200)Parameters

Device "n"




Note that your actual target/LUN assignment will vary depending on unique system configuration requirements. Be sure that existing and new configurations are well documented before upgrading to Fibre Channel Directors.

The first time a disk appears on a Windows NT system, the Windows NT Disk Administrator writes a signature to that disk. The signature is a unique 32-bit number for Windows NT to use as an internal identification number for that disk. Windows NT uses the signature to associate drive letters with a disk, and disks with volume sets. The Disk Administrator can reassociate the drive letter with the correct disk even if you reconfigure device channels or change the disk target and LUN.





4

4-22


Host Configuration with Emulex HBAsThis section describes the procedures required to configure one or more Emulex host bus adapters in a Windows NT host for connection to Symmetrix over Fibre Channel arbitrated loop. (Refer to Table 4-1 on page 4-3 for approved HBAs.) Emulex LP7000E-EMC, LP8000-EMC, and LP850-EMC all use the same driver in a Windows NT host. The procedures described in this section apply to all three HBA types.



Installing the HBA 1. Set the jumpers on an LP7000E-EMC or LP8000-EMC as shown in Figure 4-1 to enable it for use with Windows NT. The LP850-EMC has no user-configurable jumpers.

Figure 4-1 LP7000E-EMC and LP8000-EMC Jumpers

Note that JX1 and JX2 are in opposite locations on the two HBA types.

1 321 32

JX1JX2

1 32 1 32

JX1 JX2 LP8000-EMC

LP7000E-EMC



2. With host system power removed, install the HBA and make the necessary cable connections. The card installs into a single PCI bus slot.

3. Re-apply power and allow the system to boot normally.

Updating the Flash Firmware/BIOS

Each Emulex Fibre Channel controller has a flash upgradable firmware and BIOS. In most instances, it is necessary to keep only the firmware up to date, since the BIOS is applied only when using connected storage as a boot device.

The CD-ROM contains the EMC-approved firmware files at the time of this document’s release. Updated firmware, if available, can be found on the Emulex web site:

http://www.emulex.com/ts/fc/index.htm

From this site, select the adapter onto which you are installing the firmware, then download the correct firmware file. The firmware is typically a .ZIP file, and must be extracted to another location. Extract the downloaded file to a diskette and follow the upgrade procedure below.

Upgrade Procedure The following procedure is used to upgrade the flash firmware for the Emulex LP7000E-EMC, LP8000-EMC, and LP850-EMC.

1. Boot the computer using a DOS/WIN95/WIN98 bootable diskette.

2. Insert the diskette containing the flash utility (LP6DUTIL.EXE).

3. At the A:\> prompt, type lp6dutil <Enter> to start the utility.

The utility performs diagnostic tests on the installed adapter(s). You may be required to press <Enter> after each test so the program can move on the to the next. Once the diagnostics are complete, the Main Menu appears.

4. Type 5 to select Maintenance, and press <Enter>.

5. Type 1 to select Upgrade Firmware, and press <Enter>.

6. Enter the range of adapters to flash; for example: 1–4 (for four adapters).

7. Enter the Firmware Image filename, including the path. The firmware image file should be on the same disk as the LP6DUTIL.EXE program file.

Host Configuration with Emulex HBAs 4-23

4

4-24


8. When prompted, enter 1 to proceed with the upgrade for the first controller.

9. When prompted, enter 1 to reset the adapter after loading is complete.

10. Repeat steps 8 and 9 for each adapter in the range entered in step 6.

11. When all adapters have been loaded, enter 0 at the Maintence menu to return to the Main Menu.

12. Enter 7 from the Main Menu to exit the flash utility.



Obtain the LatestDriver

The CD-ROM that accompanies the adapter kit contains the latest EMC-approved driver as of the creation date of the CD-ROM. Drivers are occasionally updated, however, so contact your EMC representative to confirm the latest driver version.

• If the CD-ROM contains the latest driver version, follow the procedure under Install the Driver later on this page.

• If a newer driver is available, download it from the Emulex website, as described in the following procedure.

To download the driver:

1. Access this file: http://www.emulex.com/ts/fc/index.htm

2. Click on the adapter you are installing:

• LP7000E-EMC• LP8000-EMC• LP850-EMC

3. Extract the downloaded file to a formatted 3.5-inch diskette, or to the hard disk on the Windows NT host.



Install the Driver To install the driver, follow these steps:

Refer to release notes provided with the driver for information that might be unique to new driver revisions.

1. Boot the host (if necessary) with Windows NT 4.0.





6. Locate the disk/directory with the OEMSETUP.INF file for the Emulex driver and click OK.

7. Select the appropriate driver for your configuration. For example:

• For direct-connect arbitrated loop configurations, select Emulex LightPulse, Arbitrated Loop, Automap SCSI Devices.

• For hub configurations (EMC Volume Logix), select Emulex LightPulse, Public Loop, Automap SCSI Devices.


9. After rebooting, verify that the driver is installed and has started by checking the Control Panel, SCSI Adapter, Drivers window for a statement similar to the following:

Emulex LightPulse, Arbitrated Loop, Automap SCSI Devices (Started)


10. Edit the c:\boot.ini file and add the /PCILOCK switch to the boot entry. Below is an example of the updated entry:

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Server Version 4.00" /pcilock



4

4-26


Changing the Registry

EMC requires a change to the Windows NT registry if using Emulex Fibre Channel controllers. The OEMCode value with the Emulex registry key must be set to the correct value.

1. Click Start, then Run.

2. In the Open box, type REGEDT32.EXE and click OK.

3. Follow this path to the Emulex registry key:

4. In the right pane of the registry editor, double-click the OEM Code variable.

5. In the DWORD Editor windows, change the value in the data box to 1 and click OK.


Using the Emulex Configuration Tool

Before using the configuration tool, follow the procedure under Changing the Registry on page 4-26.

Once the Emulex driver has been installed, a new icon appears under Start -> Programs. This shortcut points to the Emulex Configuration Tool, which is a small graphical user interface (GUI) that allows the user to make setup changes to installed Emulex adapters. This tool is not necessary for most installations, and can cause errors and/or poor performance if used incorrectly.

1. Start the Emulex Configuration Tool by selecting Start -> Programs -> Emulex Configuration Tool.

2. A window similar to Figure 4-2 on page 4-27 appears, displaying the available adapters in the upper left corner. Click on the adapter you wish to modify. (This activates all items that can be altered for that adapter.)



Elxsli2



Figure 4-2 Emulex Configuration Tool Window

Table 4-3 on page 4-28 lists the recommended settings.

You can enable or disable the various Adapter Controls by checking or "unchecking" the associated boxes, and you can change the parameter values in the small windows across the bottom by clicking on a window and typing in the desired value. However, EMC recommends changing only the Maximum Number of LUNs, from the default of 32 to 128.


4

4-28


For reference, Table 4-3 lists the recommended settings.

a. For host systems running EMC PowerPath, Wait Ready Timer must be 10 seconds.

3. Once all changes have been made to a selected adapter, click the Apply button in the lower left corner to save changes for that adapter.

4. Repeat steps 1 through 3 for any other adapters you want to change.

5. When all changes are complete, reboot the host.



Follow the instructions for configuring and partitioning Symmetrix devices under Windows NT Environment in the Symmetrix Open Systems Environment Product Guide.

Table 4-3 Emulex Configuration Tool Settings for Arbitrated Loop

Adapter Controls

Automatically Map SCSI Devices Enabled (checked)

Allow Multiple paths to SCSI Targets Enabled (checked)

All other Adapter Controls Disabled (unchecked)

Other Parameters

Maximum Number of LUNs 128

Maximum Queue Depth 8

Wait Ready Timer 60 sec (or 10 sec a)

E_D_TOV 1000 ms

R_A_TOV 100 sec

AL_TOV 15 ms

ARB_TOV 1000 ms








Once all disk signatures are written, devices are ready to be used by Windows NT. (Follow the instructions for configuring and partitioning Symmetrix devices under Windows NT Environment in the Symmetrix Open Systems Environment Product Guide.)


4

4-30



5

This chapter provides information specific to Silicon Graphics (SGI) Challenge hosts. The chapter includes the following sections:

• SGI Challenge Fibre Channel Environment...................................5-2• Host Connectivity ..............................................................................5-3• Symmetrix Configuration .................................................................5-4• Host Configuration with Prisa HBA ...............................................5-6


SGI Challenge Host onArbitrated Loop

SGI Challenge Host on Arbitrated Loop 5-1

5

5-2

SGI Challenge Host on Arbitrated Loop

SGI Challenge Fibre Channel EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the SGI Challenge host environment.

Hub Support Hubs are not supported.


Addressing If you attempt to access existing devices previously interfaced via SCSI, your raw device addressing may be changed after upgrading to Fibre Channel Directors.


5SGI Challenge Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with the SGI hosts shown in Table 5-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.

The Fibre Channel adapter driver functions as a device driver layer below the standard SCSI adapter driver. The Fibre Channel interface is therefore transparent to the SGI disk administration system.

Table 5-1 HBAs for SGI Challenge Hosts

Host TypeMinimum OS Version Host Bus Adapter Driver Version

Max LUNs

Challenge IRIX 6.2 with July 1998 patch set

Prisa HIONETFX-64 HIO

1.3 with patches 28 and 29

128


5

5-4


Symmetrix ConfigurationSymmetrix configuration is done by an EMC Customer Engineer (CE) through the Symmetrix service processor. The CE will configure your Symmetrix with the following settings for each Fibre Channel port.

Table 5-2 Symmetrix Configuration for SGI Challenge Hosts

Parameter Setting

Disk Array Mode (A-bit) Disabled

Volume Set Addressing (V-bit) Disabled


Loop ID 00





Disabled




Host Configuration with Prisa HBAThis section describes the tasks required to install one or more Prisa host bus adapters into an SGI Challenge host and configure the host for Symmetrix Fibre Channel. (Refer to Table 5-1 on page 5-3 for approved HBAs.)

EMC recommends that the system disk in the host have at least 50 MB of available disk space.

Installing NetFX Software

The NetFX software is distributed on 4mm tape.

Follow this procedure on the host to install the NetFX software:

1. At the # prompt, type cd /usr/tmp <Enter>, to go to the temporary directory:

2. Create and go to a NetFX directory:

a. Type mkdir netfx <Enter>.

b. Type cd netfx <Enter>.

3. Extract the NetFX software:

• If the tape device is local:

Type tar xvf /dev/tape <Enter>.

• If the tape device is remote:

Type tar xvf guest@<REMOTEHOST>:/dev/tape <Enter>.

4. The tape will extract data into subdirectories 53 and 62, which represent versions of IRIX. Since EMC supports only version 6.2 and higher, type cd 62 <Enter>, to go to subdirectory 62.

5. Use SGI’s inst utility to install the software:

a. At the # prompt, type inst <Enter>.

b. At the inst> prompt, type from images <Enter>.

c. At the inst> prompt, type go <Enter>.

d. At the inst> prompt, type quit <Enter>.

6. Type autoconfig -f <Enter>, to reconfigure the IRIX kernel to include the newly installed drivers.

Host Configuration with Prisa HBA 5-5

5

5-6


7. Type shutdown -y -g0 <Enter>, to shut down the host.

Installing an HBA Prisa NetFX-HIO64 adapters plug into IO4 expansion slots in the SGI Challenge host. Each NetFX-HIO64 contains two Fibre Channel ports, and an IO4 board supports up to two NetFX-HIO64s. (The NetFX adapter has no user-configurable jumpers or switches.)

Figure 5-1 SGI IO 4 Card with NetFX-HIO64

Refer to NetFX user documentation for information on installing the card.

Configuring and Enabling Software Files

Before the adapter can access devices, the NetFX drivers require that four files be modified and the drivers enabled.

CAUTION!Be careful when modifying these files; the drivers are extremely sensitive to syntax and data consistency.

ModifyingConfiguration Files

/etc/NLPorts

This file defines the World-Wide Number (WWN), Channel I/O, Loop ID, and N_Port name for each Fibre Channel interface.



The format of the file is as follows:

<WWN> <Channel ID>, <Loop ID> <NPName> <NPalias (optional)>

Note that the fields are all on the same line, and are separated by spaces, except for the comma separating <Channel ID>,<Loop ID>:

The fields are described below:

Here is a sample /etc/NLPorts entry for a two-loop configuration:

/etc/config/netfx.options

This file defines the physical location of the NetFX-HIO64 within the SGI host.

There are two keywords defined in this file:

• adapt — Type of board and the physical location of that board.• chan — Defines the properties a particular port on that board.

Field Description

<WWN> A 64-bit value expressed as a sequence of eight hexadecimal values separated by periods. The manufacturer’s ID portion of the World-Wide Number is 00.60.77 for the Prisa NetFX card. The /var/adm/SYSLOG file contains the <WWN> field for the HIO card; use the Symmetrix E1 command to obtain the <WWN> field for the Symmetrix interface.

<Channel ID> Identifies each distinct channel. If multiple machines share this file (via rdist, for example), the channel ID specifies which N_ports can talk to each other. N_Ports with the same Channel ID are assumed to be on the same loop.

<Loop ID> A hexadecimal value in the range 0 to 7d that is the unique network identifier for a given port. (This is also known as a Select ID for disks.) For the Symmetrix, the Loop ID should be set to 0 in the Director Configuration Menu of Auto Install.

<NPName> Arbitrary text name for the N_Port, up to 256 characters.

<NPalias> Any other equivalent name(s) for the N_Port. This field is optional.

10.0.0.60.77.0.23.2e 1,0x7d P1A (Port 1 on the HBA)10.0.0.60.77.0.23.2f 2,0x7d P1B (Port 2 on the HBA)1.0.0.60.48.0.0.00 1,0 SYMM1A (Port 1-A on the Symmetrix)1.0.0.60.48.0.0.10 2,0 SYMM1B (Port 1-B on the Symmetrix)


5

5-8


The fields are described below:

Field Description

adapt Keyword starting adapter configuration. Different adaptor types are:gio_singlegio_dualhio_singlehio_dualpci32_single

slot Identifies the physical slot in which the card is mounted:GIO = 0 (bottom) or 1 (top)HIO = IO4 slot numberPCI = assigned slot number

option Global ’attribute=value’ string to be passed to the adaptor configuration. The string must be within parentheses; for example: option=(-a enable_parity=yes). (There must be no space before or after each ’=’ sign.) There can be multiple option specifiers per adaptor.

position Physical position on board:GIO is always 0HIO: 5 = bottom, 6 = topPCI is always 0

chan Keyword starting channel configuration for an adapter:enable = yes (channel enabled) or no (channel disabled)npname = name of the N_Port, from /etc/NLPortsoverride = yes

port Port on board:GIO: 1 = nearest door, 2 = nearest power supplyHIO: 1 = bottom (when installed), 2 = top

option Channel-specific 'attribute=value' string to be passed to channel configuration. The string must be within parentheses; for example: option=(-a clear_mem=no). (There must be no space before or after each ’=’ sign.) There can be multiple option specifiers per adaptor

nport_option N_Port-specific option list to be passed to the N_Port configuration program. The string to be passed must be within parentheses; for example: nport_option=(-aMFSBQ_buffers=8). (There must be no space before or after each ’=’ sign.)

ip_option IP-specific option list to be passed to the IP configuration program fcipcfg. The string to be passed must be within parentheses; for example: ip_option=(-a arp_WWNSize=8). (There must be no space before or after each ’=’ sign.)

prods List of products (not all need be specified):ip = IPtpt = Transportersi = SCSI initiator



Here is a sample /etc/config/netfx.options file:

Each "chan" entry is shown over several lines due to the space limitation of this document; each of these entries in the file must be one continuous line:

adapt type=hio_dual slot=2 position=5

chan npname=P1A override=yes port=1 ip=no si=yes fsd=no tpt=no enable=yes nport_option=(-a exchanges=8192) nport_option=(-a SEST_entries=8192)

chan npname=P1B override=yes port=2 ip=no si=yes fsd=no tpt=no enable=yes nport_option=(-a exchanges=8192) nport_option=(-a SEST_entries=8192)

/etc/config/fsd.options

This file contains information about the Symmetrix devices configured on each of the Fibre Channel interfaces.

The contents of this file define the devices on a given loop, and the characteristics of that device.

The fields of the file are described below:

Field Description

disk Keyword starting disk configuration

npname Name of the N_Port, from /etc/NLPorts

devname Device name, such as fsd0

lun Logical Unit Number in hex

unit Unit number

option Attribute=value string to be passed to fsdcfg. The string must be within parentheses; for example: option=(-a max_read=4m). (There must be no space before or after each ’=’ sign.) There can be multiple option specifiers per disk. For detailed option descriptions, type man fsd.options <Enter>.


5

5-10


Here is an example of part of an fsd.options file.

Each "disk" entry is shown over two lines due to the space limitation of this document; each of these entries in the file must be one continuous line:

disk npname=SYMM1A devname=fsd0l0 unit=0 lun=0x00000000000000 option=(-a max_tasks=2) option=(-a timeout=60000)

disk npname=SYMM1A devname=fsd0l1 unit=1 lun=0x01000000000000 option=(-a max_tasks=2) option=(-a timeout=60000)

The fields listed above are described below:

/etc/xlvgdisks

This file determines which devices will be used for XLV (SGI’s Logical Volume Manager). Entries in this file are only necessary if you are using XLV.

Field Description

npname NL_Port name as defined in the /etc/NLPorts file.

devname Name of the logical device. This name will be expanded in the /dev/{r}dsk directory to include fsd0l0vh (Volume Header), fsd0l0vol (Volume Directory), fsd0l0s# (Volume slice number).

unit Unit number for the device. This number must be a unique integer.

lun Logical Unit Number, in hex notation.

option Configuration parameters for the device. The two options defined in the file example are:• max_tasks — Command Tag Queue depth

• timeout — Timeout value in milliseconds.The default is 4000 (four seconds). Type man fsdcfg <Enter> to get a description of all options.



This file must be modified only if the customer will be using XLV with the NetFX devices. (XLV is SGI’s version of a Logical Volume Manager.) The fields in this file are described below:

Some sample lines from a /etc/xlvgdisks file are:

1 fsd0l02 fsd0l13 fsd0l24 fsd0l3

The software translates the logical device names to XLV style device names. The system creates the following device files for each entry in the /etc/xlvgdisks file. The slice device file can be used to create concatenated or striped volumes.

• xlg0d1vh (Volume Header)• xlg0d1vol (Volume Directory)• xlg0d1s# (Slice Number)

Enabling the NetFXSoftware

Once all of the configuration files have been modified, the drivers must be enabled before the devices can be accessed.

Use the chkconfig command to enable the software:

1. Type chkconfig netfx on <Enter>.

2. Type chkconfig fsd on <Enter>.

3. Type chkconfig xlv on <Enter> (necessary only if using Prisa with XLV)

4. Type chkconfig xlvgdisk on <Enter> (necessary only if using Prisa with XLV)

The host must be rebooted after the software has been enabled.

Field Description

unit number Logical unique non-zero integer. Numbers should be assigned sequentially starting from one.

disk device Name of the logical disk device taken from the /etc/config/fsd.options file.


5

5-12


If the host does not boot properly, shut it down and boot it to single user-mode. Once the system has booted in single-user mode, you must check all of the configuration files to make sure the information is correct. Remember that the NetFX software is extremely particular to syntax and accurate information in all of the files. Refer to Troubleshooting on page 5-14.

Creating New Devices This section describes how to create newly configured devices.

CAUTION!This section addresses new devices with no existing data. The procedure will destroy any existing data on the devices. If the devices are being migrated from SCSI, refer to Appendix B.

1. Use the fsdx command, which is similar to the IRIX fx command in that it is used to partition NetFX devices.

Some common options used with fsdx are described below:

Here is an example of an fsdx command:

# /usr/NetFX/bin/fsdx -d fsd0l0-N -m9206 -txfs -p7

This example will partition device fsd0l0 with slice 7 (-p7) with type xfs (-txfs) with a size of 9206 cylinders.

Refer to the on-line man page for additional fsdx options.

Option Description

-d Specifies the device name as defined in the /etc/config/fsd.options file.

-N Specifies that this is a new partition thus fsdx will create a new Volume Header. Without the -N option, fsdx will modify the existing Volume Header.

-m Specifies the size of the partition. By default, the size is specified in sectors. You can specify the size in megabytes by entering the option as -mXXXm, where XXX is the size in megabytes. (For example, -m2048m specifies a partition of 2048 megabytes.) Similarly, you can specify the size in gigabytes. For example, -m4g specifies a size of 4 gigabytes.

-t Specifies the type of partition. (The default IRIX partition type is xfs.)

-p Specifies the partition number. This number must be in the range 0–15, except for 8 and 10, which are reserved for the volume header.



2. Type mkfs /dev/rdsk/fsd0l0s7 <Enter>, to make a filesystem from the newly defined partition.

3. Type mount /dev/dsk/fsd0l0s7 /mount-point <Enter>, to mount the new filesystem.

Using SGI’s XLV toDefine Striped or

ConcatenatedVolumes

This section describes how to set up striped or concatenated volumes using XLV with NetFX devices. Refer to Configuring and Enabling Software Files on page 5-6 for information on editing the /etc/xlvgdisks file.

The xlvgdisk facility will translate standard NetFX devices to xlg devices for use with XLV. The naming translation is done through the xlvgdisks file. The standard device (for example, ’fsd0l0’) will now be accessed via ’xlg0d1’ when using XLV.

CAUTION!Do not access the standard device and the xlg device at the same time.

Creating a concatenated volume

1. Use the following commands to concatenate multiple disks to create a larger volume:

a. xlv_make <Enter>

b. vol netfx_1 <Enter>

c. data <Enter>

d. plex <Enter>

e. ve xlg0d1s7 <Enter>

f. ve xlg0d2s7 <Enter>

g. end <Enter>

h. exit <Enter>

Press <Enter> (accepting the default of yes) when prompted:

Newly created objects will be written to disk. Is this what you want? (yes)

2. Type mkfs /dev/rdsk/xlv/netfx_1 <Enter>, to make a filesystem for the device.


5

5-14


3. Type mount /dev/dsk/xlv/netfx_1 /mount-point <Enter>, to mount the device.

Creating a striped volume

1. Use the following commands to create a striped volume:

a. xlv_make <Enter>

b. vol netfx_2 <Enter>

c. data <Enter>

d. plex <Enter>

e. ve -stripe -stripe_unit 256 xlg0d1s7 xlg0d2s7 <Enter>

f. end <Enter>

g. exit <Enter>

Press <Enter> (accepting the default of yes) when prompted:

Newly created objects will be written to disk. Is this what you want? (yes)

2. Type mkfs /dev/rdsk/xlv/netfx_2 <Enter>, to make a filesystem for the device.

3. Type mount /dev/dsk/xlv/netfx_2 /mount-point <Enter>, to mount the device.

For additional information on using XLV, refer to the IRIX System Administrator Guide.

Troubleshooting This section lists some error messages and describes tips for troubleshooting.

"No such device or address"

Volume administrative commands such as mkfs, mount, or prtvtoc fail with the above error when trying to access a device.

Does this error occur for every device on the loop?

• Check the /etc/NLPorts file and verify that the World Wide Name is correct for both the HIO board and the Symmetrix.

• Check the /etc/config/netfx.options file and make sure that the slot and position for this board are correct and that the npname matches with the corresponding entry in the /etc/NLPorts file.



• Check the /etc/config/fsd.options file and make sure that the npname matches with the /etc/NLPorts file for the loop in question.

Does this error occur on one or several devices on the loop? Check the /etc/config/fsd.options file, make sure that the device(s) in question has the correct npname. Also, make sure that the LUN address in this file is in hexadecimal notation (for example, lun=0x4E000000000000). Verify that the unit number for the device is unique in the fsd.options file.

"System hangs during bootup"

Check the World-Wide Number in the /etc/nlports file. It is probably incorrect either for the Symmetrix or for the HIO card.

"No such file or directory"

Check the /etc/config/netfx.options file and verify that the slot number and the position number are correct. Also verify that the npname matches with that in /etc/nlports.


Once the Symmetrix has devices assigned with device addresses and the directors have been switched on line, the host can see all the target Symmetrix devices assigned to that host interface.

Devices accessed via Fibre Channel using the NetFX driver will be addressed behind a single target ID. This differs from existing SCSI device addressing, which may have multiple targets and LUNS.

Format, Partition,Label

Use the fx -x command to partition and label the new devices. The devices will appear when a hinv command is issued.


1. At the root prompt, type fx -x <Enter>.

The host searches for all disks. It generates a display placing all unlabeled disks at the beginning of the listing.


3. At the format> prompt, type label <Enter>.



5

5-16


5. Type di <Enter> at the prompt to display a listing of the disks.

6. Repeat steps 2 through 5 for each remaining Symmetrix disk.

Volume Manager andFilesystems

If you wish to use raw devices, there is no need to create filesystems for each device. However, physical volumes can be managed under XLV in the same manner as devices accessed through a standard SCSI interface. Follow the instructions for volume manager functions and filesystem creation for SGI devices in the Symmetrix Open Systems Environment Product Guide.


If upgrading an existing Symmetrix-to-host SCSI interface to Fibre Channel, perform the procedures described in Appendix B.


6

This chapter provides information specific to Silicon Graphics (SGI) Origin hosts. The chapter includes the following sections:

• SGI Origin Fibre Channel Environment .........................................6-2• Host Connectivity ..............................................................................6-3• Symmetrix Configuration .................................................................6-4• Incorporating Symmetrix..................................................................6-5• Adding Devices On Line...................................................................6-8


SGI Origin Host onArbitrated Loop

SGI Origin Host on Arbitrated Loop 6-1

6

6-2

SGI Origin Host on Arbitrated Loop

SGI Origin Fibre Channel EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the SGI Origin host environment.



Hub Support Hubs are not supported.


Addressing If you attempt to access existing devices previously interfaced via SCSI, your raw device addressing may be changed after upgrading to Fibre Channel Directors. The Fibre Channel driver uses a single Target ID and 64 possible LUN addresses.


6SGI Origin Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with the SGI hosts shown in Table 6-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.

a. Requires copper to optical MIA, since SGI HBAs do not support direct optical connections.

The Fibre Channel adapter driver functions as a device driver layer below the standard SCSI adapter driver. The Fibre Channel interface is therefore transparent to the SGI disk administration system.

Table 6-1 HBAs for SGI Origin Hosts

Host TypeMinimum OS Version Host Bus Adapter

Max LUNs per HBA

Origin 200 (PCI) IRIX 6.4.1 SGI PCI-FC-1P a 64

Origin 2000 (PCI) IRIX 6.4.1 SGI PCI-FC-1P a 64

Origin 2000 (XIO) IRIX 6.4.1 SGI XT-FC-2P a 64


6

6-4




b. The Target ID is seen as 0. (If the Loop ID is set to 1, the Target ID is seen as 1.)

Table 6-2 Symmetrix Configuration for SGI Origin Hosts

Parameter Setting




Loop ID 00 b

Non-participating Mode (NP-bit) Disabled




Disabled




Incorporating SymmetrixAfter all the ports are connected to the Symmetrix Fibre Channel interfaces and the interfaces brought on line, use the following procedure to verify that the host can see all the Symmetrix devices assigned to that host.

CAUTION!Make sure the Symmetrix is off line to the host before connecting the Symmetrix to the host.

1. Power on the SGI host.

2. At the System Maintenance menu on the system console, select 1 Start System. The operating system boots to IRIX.

During the boot process, you may see error messages pertaining to the newly attached disks on the controller. This is normal and you can ignore these errors. If, however, these disks are already configured in the system, you need to determine the cause of the error condition.

3. At the login prompt, log into the system as root.

4. At the prompt, type hinv -v > disk_config <Enter>.

The host checks for all controllers installed in its system and lists them in the file disk_config.

5. At the prompt, type more disk_config <Enter>.

This displays the contents of the disk_config file, similar to the following. Note that unit 0 identifies the target ID:

Integral SCSI Controller 41: Version Fibre Channel AIC-1160, revision 2

Disk drive: unit 0, LUN 3 on SCSI Controller 41Disk drive: unit 0, LUN 2 on SCSI Controller 41Disk drive: unit 0, LUN 1 on SCSI Controller 41Disk drive: unit 0 on SCSI Controller 41

When a LUN is not displayed in the last entry (as shown), LUN0 is implied.

6. Look for the numbers reported for the Integral SCSI controllers and the unit number of the disk drive on those controllers to ensure that all Symmetrix devices configured in the host are recognized by the system.

Incorporating Symmetrix 6-5

6

6-6


Partitioning and Labeling the Devices

Use the fx -x command to partition and label the new devices.

1. At the system prompt, type fx -x <Enter>.

2. At the fx: "device-name" = (dksc) prompt, press <Enter> to select disk devices.

3. At the fx: ctlr # = (0) prompt, enter the number of the Fibre Channel controller for a device (from the hinv command in the previous section).

4. At the fx: drive# = (1) prompt, enter the target ID number for that device.

5. At the fx: lun# = (0) prompt, press <Enter> to select LUN 0, or enter the LUN number of the Symmetrix device you want to partition on the specified controller. (Refer to step 3.)

Drive type = EMC SYMMETRIX (version number) appears.

If the SYMMETRIX header does not appear, the selected disk is not an EMC volume.

A bad label warning should appear along with a message stating a new label was created. If this message does not appear, then the selected disk has already been labeled.

If the message Warning: *Failed to open * /dev/rdsk/... appears, the host does not see the selected drive, or the device entry for that devices does not exist. Check the Symmetrix disk configuration.

WARNING

The following steps will destroy any existing data on the affected drives. Use only when configuring new disks that do not yet have any data on them.

6. At the fx menu prompt, type r <Enter> (repartition).

7. At the fx repartition prompt, type o <Enter> (option drive).

8. FX prompts you to specify a filesystem. Type xfs<Enter>.

9. The system then prompts you to specify whether you want to create a log partition. Type yes <Enter>.



10. Type .. <Enter> (two dots) to create another disk type. Repeat this step to create as many disk types as you need to.

11. Repeat steps 6 through 10 to label all the drives.

12. When you are finished labeling all the drives, type exit <Enter>.

Tag Command Queuing Enabled

Perform the following actions prior to enabling the tag command queueing.

1. Perform steps 1 through 6 of Partitioning and Labeling the Devices on page 6-6.

2. At the fx prompt, type l <Enter> (label).

3. At the fx/label prompt, type se <Enter> (set).

4. At the fx/label prompt, type para <Enter> (parameters).

5. Press <Enter> repeatedly until the message Enable

CTQ=(disabled appears, then type enable <Enter>.

6. Enter the queue depth value of the Symmetrix; for example, CTQ=16 <Enter>.

7. Press <Enter> repeatedly until the prompt About to modify

drive parameter...(OK)? appears, then type yes <Enter>.

If you want to work with filesystems on Symmetrix disk devices, follow the procedures in the SGI/Origin chapter of the Symmetrix Open Systems Environment Product Guide, Volume I.

Incorporating Symmetrix 6-7

6

6-8


Adding Devices On LineWhenever devices are added on line to the Symmetrix unit or device channel addresses are changed, you must perform the actions described below to introduce the new devices to the system.

The EMC PSE Configuration Group can add new devices to the Symmetrix configuration while Symmetrix remains on line to the host.

IRIX version 6.4 and later allow on line configuration. Once the Symmetrix devices have been added:

1. Type hinv <Enter>, to see the I/O buses.

2. Type scsiha -rp bus# <Enter>.

3. Type ioconfig -f /hw <Enter>.

4. Type hinv <Enter>, to see the devices.


7

This chapter provides information specific to IBM RS/6000 and Bull Escala T-series hosts. The chapter includes these sections:

• AIX Fibre Channel Environment .....................................................7-2• Host Connectivity ..............................................................................7-3• Symmetrix Configuration .................................................................7-4• Host Configuration with Emulex HBA ..........................................7-5• AIX Hub Configuration Guidelines ................................................7-6


AIX Host on ArbitratedLoop

AIX Host on Arbitrated Loop 7-1

7

7-2

AIX Host on Arbitrated Loop

AIX Fibre Channel EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the AIX host environment.



Hub Support Hubs are supported as described under AIX Hub Configuration Guidelines on page 7-6.


Addressing • AIX uses SCSI-2 device access protocol in addressing its Fibre Channel devices. The SCSI-3 Array Controller addressing modes are not supported. The peripheral device access mode is supported in Symmetrix to address up to 256 logical devices (in an address range of 0 to 255).



7AIX Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with the AIX hosts shown in Table 7-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.

a. 128 maximum per Symmetrix port.

Refer to your AIX host documentation for specifications relating to PCI bus limitations and adapter location.

The driver functions as a device driver layer below the standard AIX SCSI adapter driver. The Fibre Channel interface is therefore transparent to the AIX disk administration system.

Table 7-1 HBAs for AIX Hosts

Host TypeMinimum OS Version Host Bus Adapter Driver Version Max LUNs

RS/6000 AIX 4.3.0 Emulex LP7000E-N1

devices.pci.df10e51a version 1.2.12.0 or above and devices.pci.df1001f7 version 1.0.1.0 or above

256 a

Bull Escala T Series

AIX 4.3.0 Emulex LP7000E-N1

devices.pci.df10e51a version 1.2.12.0 or above and devices.pci.df1001f7 version 1.0.1.0 or above

256 a


7

7-4




b. Each Symmetrix port in a hub environment requires a different loop ID.

c. Enabled only for PowerPath.

Table 7-2 Symmetrix Configuration for AIX Hosts

Parameter Setting




Loop ID See note b

Non-participating Mode (NP-bit)

Disabled—accept soft- assigned address if hard address is not available




Disabled c

Return BUSY for ABORT (B-bit) Enabled


SCSI 3 (SC3-bit) Enabled

Unique Worldwide Name (UWN-bit)

Enabled


7AIX Host on Arbitrated Loop

Host Configuration with Emulex HBAThe necessary drivers for the Emulex HBA are included with the EMC Fibre Channel Interface for AIX Platforms, which ships with its own manual. Refer to the EMC Fibre Channel Interface Version 1.0 for AIX Platforms Product Guide (part number 300-999-038).


7

7-6


AIX Hub Configuration Guidelines

AIX Hub Support Symmetrix Fibre Channel supports IBM Netfinity hub model 35231RU (7 shortwave ports, no GBICs). Refer to Loops with Hubs on page 1-22 for descriptions of various hub configurations.

AIX Hub Configuration Guidelines

The following paragraphs provide guidelines and limitations for using hubs in an AIX and Symmetrix Fibre Channel storage network.









8

This chapter provides information specific to Siemens hosts running Reliant UNIX v5.44B10 (64-bit OS) or higher. The chapter includes the following sections:

• Siemens Fibre Channel Environment..............................................8-2• Host Connectivity ..............................................................................8-3• Symmetrix Configuration .................................................................8-4• Host Configuration with Siemens HBA .........................................8-5• Siemens Hub Configuration Guidelines....................................... 8-11


Siemens/Reliant UNIXHost on Arbitrated

Loop

Siemens/Reliant UNIX Host on Arbitrated Loop 8-1

8

8-2

Siemens/Reliant UNIX Host on Arbitrated Loop

Siemens Fibre Channel EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to Siemens RM300E, RM400C and RM600E host environments.



Required Software The RAID software package must be loaded to support Symmetrix connection to Siemens host. The correct device name for the Symmetrix is ios0/sraid (not ios0/sdisk).

Hub Support Hubs are supported as described under Siemens Hub Configuration Guidelines on page 8-11.


Addressing • Siemens uses SCSI-3 device access protocol in addressing Fibre Channel devices, and supports peripheral device access mode. Symmetrix peripheral addressing mode allows a Siemens host to address up to 256 logical devices, in the range 0 to 255. Refer to Appendix C for the available addressing modes.

• LUN 0 must be present on every Symmetrix Fibre Channel port that is connected to the host.



8Siemens/Reliant UNIX Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with the Siemens hosts listed in Table 8-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.

a. Reliant UNIX v5.44B10 supports 8 LUNS. Reliant UNIX v5.44C10 supports 128 LUNs. Reliant UNIX v5.45A supports 4096 LUNs.

b. Use autoconf -l to determine the type of Fibre Channel controller (LP6502 or LP8000).

The Fibre Channel adapter driver functions as a device driver layer below the Siemens sraid SCSI adapter driver. The Fibre Channel software consists of Fibre Channel controller firmware, OS-level Fibre Channel software and utilities, and RAID driver software. Most Siemens RM hosts shipped to a customer site do not have the RAID package loaded. Refer to Installing the RAID Software on page 8-5 to verify and load the Siemens RAID package.

Table 8-1 HBAs for Siemens Hosts

Siemens Host Type

Minimum OS Version Host Bus Adapter

Firmware Version

Max LUNs per HBA

RM300E Reliant UNIX v5.44C (64-bit)

Siemens RM300-CF02 FW 2.12 8, 128, or 4096 a

RM400C/E Reliant UNIX v5.44C (64-bit)

Siemens RM400-CF02 FW 2.12 8, 128, or 4096 a

RM600E30/E70 Reliant UNIX v5.44C (64-bit)

Siemens RM6T5-CF10 LP6502 2.12 or LP8000 2.82 b

8, 128, or 4096 a

RM600E40/E80, RM600CS42

Reliant UNIX v5.45A (64-bit)

Siemens RM6T5-CF10 LP6502 2.12 or LP8000 2.82 b

4096


8

8-4


Symmetrix ConfigurationSymmetrix configuration is done by an EMC Customer Engineer (CE) through the Symmetrix service processor. The CE will configure your Symmetrix with the following settings.


b. Enable Environmental Report in Symmetrix Autoinstall must be set to YES.

Table 8-2 Symmetrix Configuration for Siemens Hosts

Parameter Setting




Loop ID 0



Disable Queue Reset on Unit Attention (D-bit) Enabled

Siemens (S-bit) Enabled

Environmental Report to Host (E-bit) Enabled b




Host Configuration with Siemens HBAThis section describes the tasks required to install one or more host bus adapters into a Siemens host and configure the host for Symmetrix Fibre Channel. (Refer to Table 8-1 on page 8-3 for approved HBAs.)

The Fibre Channel HBAs supported in Siemens hosts are not manufactured by Siemens, but are customized for Siemens. Contact Siemens for more information.

CAUTION!The Reliant UNIX operating system must be installed in the host before the host is connected to the Symmetrix.

Installing the RAID Software

Reliant UNIX v5.45A10 for RM600 includes the RAID software as part of the OS installation. The procedure described in this section applies only to earlier versions of Reliant UNIX.

The RAID software package must be loaded into the host to support Symmetrix connection to the Siemens host. Most of the Siemens hosts are shipped without the RAID package loaded.

The RAID package contains three sub-packages called SIraid, SIraidM, and SIdraid.

Verify RAID PackageLoading

To verify whether the RAID package is already loaded, type pkginfo | grep raid <Enter>. The following list should appear:

system SIdraid SINIX Dual RAID Channel 2.4system SIraid RAID Systemsystem SIraidM RAID Manager Language Supplement

Load the RAID package if you do not see the above packages.

Load RAID Packages To load the RAID package:

1. Run the cdinst command.

Substitutes for the <F1> through <F8> keys are <Ctrl-F-1> through <Ctrl-F-8>.

Host Configuration with Siemens HBA 8-5

8

8-6


2. At the Process Products menu, use the arrow key to highlight Products_on_CD – Process Multi-Product CD-ROM, then press <F3> (Enter).

3. At the Process Multi-Product CD-ROM window, press <F3> (Save).

4. At the SINIX_Y 5.44B1002 10/09/98 window, press <F3> (Continue).

5. Use the arrow key to highlight the SIRAID package, then press <F2> (Mark).

6. Press <F3> (Enter) to start loading the package.

7. Use the arrow key to highlight Install – Install Products, then press <Enter>.

8. Press <F3> (Save) to start the installation.

9. Type Y <Enter>.

10. At the prompt ....rebuild the kernel after SIraid installation, type N <Enter>.

11. At the prompt ....rebuild the kernel after SIdraid installation, type Y <Enter>.

12. At the question ....kernel to be a Multi-processor Kernel?, type Y <Enter>.

The SIraid, SIdraid, and SIraidM packages will be loaded and the kernel rebuilt.

If you did not answer Y (yes) to the prompt to rebuild the kernel, you can rebuild it by entering the command /etc/conf/bin/idbuild -M .

13. After the kernel completes recompiling, type sync; init 6 <Enter>, to reboot the host.

Installing an HBA Fibre Channel driver firmware shipped with the host bus adapter might not be the latest version. Make sure you are using the latest qualified driver version. Use autoconf -l (-l is a lowercase letter L) to display the firmware version.

The Fibre Channel host bus adapter (HBA) supported in the Siemens host does not require any special hardware configuration settings.



However, Siemens-coded firmware for the Fibre Channel controller is required.

Most RMxxx hosts that support Fibre Channel should have the correct supported controller firmware loaded. In case it is not loaded, contact Siemens Customer Support for assistance.

The HBA I/O driver firmware is required to interface the Fibre Channel Adapter card to the Siemens operating system. The driver functions at a layer below the Siemens SCSI driver to present Fibre Channel devices to the operating system as if they were standard SCSI devices.

Install the Card Install the adapter card and make cable connections. The adapter card installs into a single PCI bus slot.

Verify the FirmwareRevision

Use the autoconf -l | grep fc command to display the Fibre Channel controller firmware revision. The output is similar to the following:

fc/fc0 FC LP6502-OS [FW 2.12 00], Top.: FC_AL, state: READYfc/fc1 FC LP6502-OS [FW 2.12 00], Top.: UNKNOWN, state: DOWNfc/fc2 FC LP6502-OS [FW 2.12 00], Top.: FC_AL, state: READYfc/fc3 FC LP6502-OS [FW 2.12 00], Top.: FC_AL, state: READY

The above output shows the firmware to be v2.12. See Table 8-1 on page 8-3 for the minimum required Fibre Channel firmware level.



Devices accessed via Fibre Channel using the Siemens driver are addressed behind a single target ID with 8, 128, or up to 4096 LUNs, depending on the operating system version. (Reliant UNIX v5.44B10 supports 8 LUNS, Reliant UNIX v5.44C10 supports 128 LUNs, and Reliant UNIX v5.45A supports up to 4096 LUNs.) This differs from existing SCSI device addressing, which may have multiple targets and LUNS.


8

8-8


Reliant UNIX v5.44Cand Earlier

If the host device is running Reliant Unix v5.44C or earlier, you can run the fcconf utilities to display Fiber Channel controller information. Running fcconf -l and fcconf -lv displays output similar to the following:

#fcconf -l (Note that the first number is the configuration ID):

1:14:1:0:0:0x01000060480000102:11:1:0:0:0x010000604800001b

#/sbin/fcconf -lv:

Verify that fcconf -lv displays the correct SCSI ID for each Fibre Channel connection. On occasion, the SCSI ID is incorrect after cabling up the Fibre Channel connection. If the SCSI ID is incorrect and the state is EXIST, perform the following steps to delete the Fibre Channel configuration data:

1. Disconnect the Fibre Channel cable from the host.

2. Sync and reboot the host.

3. Run fcconf -lv to display the state. The state should be LEFT.

4. Delete the Fibre Channel configuration for that port, by typing fcconf -r -i X <Enter>, where X is the configuration ID displayed in the first column of the fcconf -lv output.

5. Reboot the host.

6. Reconnect the Fibre Channel cable.

FC-SCSI configuration data base format version 21. portname 0x0100006048000010

nodename 0x0100006048000010state 1 EXISTsport_no 14 ac_name=ios0/sport14scsi_id 0 ac_name=ios0/sraid140target_id 0loop_id 0

2. portname 0x010000604800001bnodename 0x010000604800001bstate 2 LEFT sport_no 11 ac_name=ios0/sport11scsi_id 0 ac_name=ios0/sraid110target_id 0loop_id 0



Use autoconf -lv to display the devices and firmware version as below:

Reliant UNIX v5.45Aand Later

The Reliant UNIX fcconf utility is not available (and not necessary) in Reliant UNIX v5.45 and later, because the operating system incorporates Fibre Channel devices automatically. Use autoconf -l to display the list of Fibre Channel devices, as shown in the following examples, where:

• U = Unprotected device• R = RAID device (EMC RAID-S or RAID-R)• M = Mirror device• R1 = Primary RDF• R2 = Secondary RDF• BCV = Business Continuance Volume• WP = Write-protected

PCI Bridge (upper cage) node_id:0xf080 -- Chip Rev DPCI_Bus 00

ios0/scon16 NCR 53C770 chan:64ios0/sport16 Id: 8 DF 16 Bit 10MHz

fc/fc3 FC EMULEX LP6502-OS [FW 2.12 00]ios0/sport14 FCP

ios0/sraid140 EMC-SYMMETRIXios0/sraid140l0 EMC-SYMMETRIX(2208MB) -- ios0/sraid140l1 EMC-SYMMETRIX(2208MB) -- ios0/sraid140l2 EMC-SYMMETRIX(2208MB) -- ios0/sraid140l3 EMC-SYMMETRIX(2208MB) -- ios0/sraid140l4 EMC-SYMMETRIX(2208MB) -- ios0/sraid140l5 EMC-SYMMETRIX(2208MB) -- ios0/sraid140l6 EMC-SYMMETRIX(2208MB) -- ios0/sraid140l7 EMC-SYMMETRIX(2208MB) --

FC_AL: Arbitrated Loop 03, state: READYFC-Port: loop_ID 120, HostportFC-Port: loop_ID 000, state: READY, ULP: FCP


8

8-10


Example 1 — SCSI devices:

Example 2— Fibre Channel devices:

The Fibre Channel device naming convention for Reliant Unix 5.45AXXX and later operating systems has been changed as follows:

a. The letters in bold italics represent numbers as follows:

• PP = SCSI port number• T = Target ID• LL or LLL = LUN number• CC = Fibre Channel controller number• SSSSSS = Symmetrix serial number• E = Slice or partition number (0 through 15)

ios0/scon07 NCR 53C770 chan:2ios0/sport07 Id: 8 DF 16 Bit

ios0/sraid070 EMC-SYMMETRIX 3400ios0/sraid070l0 EMC-SYMMETRIX(8844MB) -- M, R1ios0/sraid070l1 EMC-SYMMETRIX(8844MB) -- M, R1ios0/sraid070l2 EMC-SYMMETRIX(8844MB) -- M, R1

ios0/sraid07f EMC-SYMMETRIX 3400ios0/sraid070l0 EMC-SYMMETRIX(2MB) -- Uios0/sraid070l1 EMC-SYMMETRIX(2MB) -- Uios0/sraid070l2 EMC-SYMMETRIX(2MB) -- U

fc/fc1 FC EMULEX LP6502-OS [FW 2.12 00], Top.: FC_AL, state: READYiof0/sport.11 FCP

iof0/sraid.11. 500082 EMC-SYMMETRIX 3400iof0/sraid.l1. 500082.0 EMC-SYMMETRIX(8802MB) -- BCV, WPiof0/sraid.11. 500082.41 EMC-SYMMETRIX(8802MB) -- R, WPiof0/sraid.11. 500082.234 EMC-SYMMETRIX 3(8802MB) -- R

Table 8-3 Reliant UNIX Fibre Channel Naming Conventions

UNIX Version Device Type

Naming Convention a

SCSI Fibre Channel

5.44Cand earlier

Block /dev/ios0/sraidPPTLLs2 same as SCSI

Character or Raw /dev/ios0/rsraidPPTLLs2 same as SCSI

5.45Aand later

Block /dev/ios0/sraidPPTLLs2 /dev/iof0/sraid.CC.SSSSSS.LLLsE

Character or Raw /dev/ios0/rsraidPPTLLs2 /dev/iof0/rsraid.CC.SSSSSS.LLLsE



Siemens Hub Configuration Guidelines

Siemens Hub Support

Symmetrix Fibre Channel supports Vixel hub model Rapport 1000 (7 shortwave ports, no GBICs). Refer to Loops with Hubs on page 1-22 for descriptions of various hub configurations.

Siemens Hub Configuration Guidelines

The following paragraphs provide guidelines and limitations for using hubs in a Siemens and Symmetrix Fibre Channel storage network.

Reliant UNIXOperating System

The following versions of Reliant UNIX are supported:




Cascaded Hubs Hub-to-hub connections are supported; however, more than two hubs in one cascaded loop are not supported.


Longwave GBICs are not supported.

Multiple Host Systems Up to six hosts can be connected to the loop, as long as there is some consideration for total I/O demand. Estimate each host’s I/O per second using a performance analysis tool such as VmSTAT, SAR, or Symmetrix Manager. Host nodes can be added to the hub loop within the suggested limit of a combined estimated 1000 IOPS (8KB block size).

Reliant UNIX Version Max LUNs

5.44B10 8

5.44C 128

5.45A 4096

Siemens Hub Configuration Guidelines 8-11

8

8-12


Volume Sharing Access to the same Symmetrix device through more than one Fibre Channel-connected host is supported with DRAID.


Software Support Host software and Symmetrix software supported in non-hub Fibre Channel topologies are supported with hubs.




9

This chapter provides information specific to Novell® NetWare hosts connecting to Symmetrix over Fibre Channel arbitrated loop. The chapter includes the following sections:

• NetWare Arbitrated Loop Environment.........................................9-2• Host Connectivity ..............................................................................9-3• Symmetrix Configuration .................................................................9-4• Host Configuration with Qlogic QLA2100F-EMC HBA..............9-5• Hub Connection Guidelines ...........................................................9-12


Netware Host onArbitrated Loop

Netware Host on Arbitrated Loop 9-1

9

9-2

Netware Host on Arbitrated Loop

NetWare Arbitrated Loop EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the NetWare host environment.



Hub Support Hubs are supported as described under Hub Connection Guidelines on page 9-12.


Addressing NetWare SCSI drivers and host adapter drivers use SCSI-2 device access protocol in addressing Fibre Channel devices. SCSI-3 Array Controller addressing modes are not supported. The peripheral device access mode is supported in Symmetrix to address up to 128 logical devices per port. Refer to Appendix C for the available addressing modes.


9Netware Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with the NetWare hosts shown in Table 9-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.

a.Netware NSS filesystem supports a maximum of 120 LUNs per Loop ID.

Driver software for NetWare hosts is provided with each HBA. Standard HAM driver installation procedures enable use of the HBAs.

The Fibre Channel Adapter driver functions as a device driver layer below the standard SCSI adapter driver; therefore, the driver can be installed and configured using the NWConfig utility for NetWare 5.00.

Table 9-1 HBAs for NetWare/FC-AL Hosts

Host TypeMinimum OS Version Host Bus Adapter

BIOS Rev

Driver Version

Max LUNs a

Compaq Proliant 850, 1600, 1850, 2500, 3000, 5000, 5500, 6000, 6500, 7000

NetWare version 5.0.0 with support pack 2

Qlogic QLA2100F-EMC 1.37 2.14g 120

HP Netserver LH-II, LH 3, LH 4, LX, LXr, LXr Pro8, LXr8000



IBM Netfinity 5000, 5500, 5500M10, 7000, 7000M10




9

9-4




Table 9-2 Symmetrix FC-AL Configuration for NetWare Hosts

Parameter Setting




Loop ID 00



Common Serial Number (C-bit) Enabled

Disable Queue Reset on Unit Attention (D-bit) not used




Host Configuration with Qlogic QLA2100F-EMC HBAThis section describes the procedures required to install one or more Qlogic QLA2100F-EMC host bus adapters into a NetWare host and configure the host for Symmetrix Fibre Channel. (Refer to Table 9-1 on page 9-3 for approved HBAs.)

Here is a step-by-step list of the procedures:

1. Prepare the adapter(s) for the NetWare host — Refer to Prepare the Adapter(s) on this page.

2. Install the adapter(s) — Refer to Installing the HBA on page 9-6.

3. If necessary, upgrade the adapter BIOS — Refer to Upgrading QLA2100F BIOS on page 9-7.

4. Configure the adapter(s) — Refer to Configuring an HBA on page 9-8.

5. Install the driver — Refer to Installing the HBA Driver on page 9-10.

6. Configure files for operation with Symmetrix — Refer to Incorporating Symmetrix Fibre Channel on page 9-11.

Prepare the Adapter(s)

Before installing the adapter(s) and driver, make sure the following are present. Once these have been verified, proceed to Installing the HBA on page 9-6.

• Approved host — refer to Table 9-1 on page 9-3.

• One or more Qlogic QLA2100F-EMC host bus adapters.

• QLA2100F ROM BIOS diskette, if you will use this. The diskette contains the following files:

> QL2XUTIL.EXE — Qlogic flash and novram programming utility

> QL21ROM.BIN — BIOS binary file for QLA2100> NVRAMFC.DAT — BIOS setting data> NVRAMFC.DEF — BIOS setting definitions> README.TXT

Host Configuration with Qlogic QLA2100F-EMC HBA 9-5

9

9-6


If you need it, the latest qualified BIOS for Symmetrix is available from either of two sources:

> Qlogic website: http://www.qlc.com

a. Click on ADAPTER DRIVERS & UTILITIES.

b. Click on QLA2100/QLA2000.

c. Click on EMC Approved Drivers.

d. Download ROM BIOS.

> Release Qlogic QLA2100F CD-ROM for EMC Symmetrix. Copy the files in the bios directory to diskette.

• HAM driver for NetWare Operating System diskette or CD-ROM. This diskette/CD contains the following files:

> QL2100.HAM — NetWare HAM driver for supporting Qlogic Fibre Channel PCI QLA2100F HBAs

> QL2100.DDI — Driver description file> README.TXT

If you need it, the latest qualified driver for the NetWare operating system is available from either of two sources:

> Qlogic website: http://www.qlc.com

a. Click on ADAPTER DRIVERS & UTILITIES.

b. Click on QLA2100/QLA2000.

c. Click on EMC Approved Drivers.

d. Download NetWare Driver.

> Release Qlogic QLA2100F CD-ROM for EMC Symmetrix. Copy the files in the NetWare directory to diskette.

Installing the HBA Follow these steps to install one or more QLA2100F-EMC adapters:

1. Remove power from the host and all peripheral devices.

2. Remove the cover from the host.

3. Locate the available PCI slot(s) to be used for the adapter(s).

4. Insert the adapter(s) into the slot(s). Press each adapter down firmly to seat the contacts into the slot connectors, then tighten the screw(s).

5. Replace the cover.



6. Reapply power to the host. During boot-up, watch for the QLA2100F banner (see Figure 9-1) and note the ROM BIOS version. The banner disappears quickly, so watch carefully.

Figure 9-1 QLA2100F-EMC Banner Example

7. Using the appropriate cables, connect the host port(s) to the Symmetrix Fibre Channel port(s), either directly or though a hub.

Refer to Hub Connection Guidelines on page 9-12.

8. The next step depends on the ROM BIOS version:

• If the version displayed in the banner is 1.37, proceed to Configuring an HBA on page 9-8.

• If the display version is not 1.37, upgrade the BIOS as described below, then proceed to Configuring an HBA on page 9-8.

Upgrading QLA2100F BIOS

To upgrade the QLA2100F BIOS, complete these steps:

The following procedures must be done with QLA2100F-EMC HBA(s) installed in the host.

1. Make the ROM BIOS diskette bootable.

2. Boot the host from the BIOS installation diskette.

3. After the host has rebooted, the DOS A: prompt appears. Type Ql2xutil /L /F <Enter>.

The firmware/HBA BIOS upgrade might take a few minutes.

4. After the upgrade is complete, remove the diskette and reboot the host. During boot-up, the QLA2100F banner (see Figure 9-1 on page 9-7) should display BIOS Version 1.37.

Qlogic Corporation

QLA2000, QLA2100 PCI Fibre Channel ROM BIOS Version 1.37

Copyright © Qlogic Corporation 1993-1999 All rights reserved

Press <ALT - Q> for Fast!UTIL

www.qlc.com


9

9-8


Configuring an HBA You can configure a QLA2100F using Fast!UTIL. Follow the steps described below.

1. During system boot, press <Alt><Q> when prompted to Press <ALt-Q> for Fast!UTIL.


• If there is only one Qlogic HBA, a Fast!UTIL Options menu appears.

• If there are multiple Qlogic HBAs, a list of addresses occupied by those HBAs appears. Using the arrow keys, select the desired HBA and press <Enter>. The Fast!UTIL Options menu appears.



5. Set the parameters as shown in Table 9-3.

The first five parameters are listed under Host Adapter Settings, and the rest are under Advanced Adapter Settings.

Table 9-3 QLA2100F BIOS Settings

Parameter Valid Settings Default SettingEMC-Recommended Setting

Host Adapter BIOS Enabled, Disabled Disabled Disabled

Frame Size 512, 1024, 2048 1024 2048

Loop Reset Delay 0 to 15 seconds 5 5

Adapter Hard Loop ID Enabled, Disabled Disabled Disabled a

Hard Loop ID 0 to 125 0 0

Execution Throttle 1 to 256 16 64

Fast Command Posting Enabled, Disabled Enabled Enabled




a. In a hub environment, Adapter Hard Loop ID must be Disabled, since Symmetrix has a hard loop ID setting.

b. The recommended setting depends on the memory size of the host.

c. Select the number of LUNs you want to access. The current Symmetrix/Qlogic Fibre Channel implementation supports a maximum of 128 LUNs.

6. When all of the parameters have been set correctly, press <Esc> to return to the Fast! UTIL Options menu.



9. After all adapters have been configured, press <Esc> to exit Fast!UTIL.


>4GByte Addressing Enabled, Disabled Disabled See Note b

LUNs per Target 0, 8, 16, 32, 64, 128, 256

8 See Note c

Enable LIP Reset Yes, No No No

Enable LIP Full Login Yes, No Yes Yes

Enable Target Reset Yes, No No Yes

Login Retry Count 0 to 255 8 8

Port Down Retry Count 0 to 255 8 30

Driver Load RISC Code Enabled, Disabled Enabled Enabled

Enable Database Updates Yes, No No No

IOCB Allocation 1 to 512 buffers 256 256

Extended Error Logging Enabled, Disabled Disabled Disabled

Table 9-3 QLA2100F BIOS Settings (continued)

Parameter Valid Settings Default SettingEMC-Recommended Setting


9

9-10


After rebooting, you can use the Scan Fibre Channel Devices option in Fast!Util to scan the Fibre Channel loop and list all connected devices by loop ID. This operation displays such useful information as world-wide names (WWNs), device vendor numbers, product names, and revisions.


The procedure for installing the QLA2100F driver differs depending on whether the server is also being installed or is an existing device. This section describes both procedures.

Installing the Driverinto a New Server

Perform the following steps to install the driver into a new NetWare 5.00 server that is also being installed:

1. When the Select a Platform Support Module and Storage Adapter window appears during the installation procedure, select Modify in the Options box.

2. Select the storage adapters, then press <Enter>.

3. The installation program auto-detects most storage adapters.

• If the program does not detect the QLA2100F adapter, go to step 4.

• If the program does detect the adapter, delete it, then go to step 4.

4. Press Insert to select a driver from the list of drivers provided with NetWare. Press Insert again to install the driver from the driver diskette.

5. After the driver is loaded from the diskette, select the driver to modify, then press <Enter>. Select the property to modify; for example, the multiple LUN support option /Lun.

6. When the driver is loaded properly for all QLA2100F adapters, select Continue in the Options box, and finish the NetWare server installation.

Installing the Driverinto an Existing Server

Use the NetWare NWCONFIG utility to install the driver into an existing NetWare 5.00 server, as described below:

1. Boot the host with NetWare 5.00.

2. Load the NWCONFIG utility, and select Driver Options from the Configuration Options menu.



3. Select Configure disk and storage device driver from the Driver options menu, then select Load additional driver.

4. On the list of available drivers, press the <Insert> key to add an unlisted driver from the diskette.

5. To support multiple LUNs, set the parameter LUN SCAN to Yes, then save the change.

6. After the driver is loaded, display the Selected Disk Drivers table under Driver Options. The driver should appear as currently loaded.


Once the Symmetrix has devices assigned with device addresses and the directors have been switched on line, the host can see all the target Symmetrix devices assigned to that host interface. Devices are presented to the host in the same manner as devices accessed through a standard SCSI interface. Follow the instructions for configuring and partitioning Symmetrix devices under Novell Environment in the Symmetrix Open Systems Environment Product Guide (Volume II).


When the HBA is configured for greater more than 8 LUNs, the driver has to map actual LUNs to virtual ID/LUN pairs, since the SCSI CDM modules might not handle more then 8 LUNs correctly.

Note that your actual target/LUN assignment will vary depending on unique system configuration requirements. Be sure that existing and new configurations are well documented before upgrading to Fibre Channel Directors.


9

9-12


Hub Connection GuidelinesSymmetrix Fibre Channel and the Qlogic QLA2100F HBA support hub connections. Refer to Loops with Hubs on page 1-22 for descriptions of various hub configurations.

Host and Symmetrix connections can be added to, or removed from, a hub while all devices are on line. (This is called hot plugging and unplugging.)

CAUTION!Do not remove a Symmetrix connection from a hub while the hosts are actively connected to the Symmetrix.


10

This chapter provides information specific to Solaris X86 hosts connecting to Symmetrix over Fibre Channel arbitrated loop. The chapter includes the following sections:

• Solaris X86 Arbitrated Loop Environment...................................10-2• Host Connectivity ............................................................................10-3• Symmetrix Configuration ...............................................................10-4• Host Configuration with Qlogic QLA2100F-EMC HBA............10-5• Partitioning and Labeling a New Device ...................................10-19• Creating and Mounting a UFS File System ................................10-23• Adding Devices On Line...............................................................10-24• Solaris X86 Hub Configuration Guidelines................................10-25


Solaris X86 Host onArbitrated Loop

Solaris X86 Host on Arbitrated Loop 10-1

10

10-2

Solaris X86 Host on Arbitrated Loop

Solaris X86 Arbitrated Loop EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the arbitrated loop/Solaris X86 host environment.



Software Patches There are no requisite patches for Symmetrix operation in the Solaris X86 environment. Some optional patches have been qualified as not interfering with Symmetrix operation. Consult your EMC Customer Engineer for latest qualified patches.

For a full listing of available patches, refer to http://sunsolve.sun.com.

Hub Support Hubs are supported as described under Solaris X86 Hub Configuration Guidelines on page 10-25.


Addressing If you attempt to access existing devices previously interfaced via SCSI, your raw device addressing may be changed after upgrading to Fibre Channel Directors.


10Solaris X86 Host on Arbitrated Loop

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with Solaris X86 hosts on arbitrated loops as shown in Table 10-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.

Table 10-1 HBAs for Solaris X86 Hosts on Arbitrated Loop

Host TypeQualified OS Version Host BIOS Host Bus Adapter

HBA BIOS

HBA Driver Version

Max LUNs

NCR 4300 Solaris X86 version 7

1.00.10.cd0 Qlogic QLA2100F-EMC 1.37 2.20 128

NCR 4400 Solaris X86 version 7

Phoenix BIOS 4.0 rel. 6

Qlogic QLA2100F-EMC 1.37 2.20 128

Siemens Nixdorf PRIMERGY 7xx

Solaris X86 version 7

4.05 rev 1.07.887 Qlogic QLA2100F-EMC 1.37 2.20 128


10

10-4


Symmetrix ConfigurationSymmetrix configuration is performed by an EMC Customer Engineer (CE) through the Symmetrix service processor. The CE will configure your Symmetrix with the following settings for each Fibre Channel port.


b. The target ID is seen as 0. (If the loop ID is set to 1, the target ID is seen as 1.) Also, each Symmetrix port in a hub environment requires a different loop ID.


Setting up an arbitrated loop environment requires EMC Volume Logix software. The EMC CE configures Volume Logix software after configuring the Symmetrix. For additional information, refer to EMC Volume Logix Product Guide, P/N 300-999-024.

Table 10-2 Symmetrix Configuration for Solaris X86 Hosts

Variable Setting




Loop ID 00 b





Disabled c




Host Configuration with Qlogic QLA2100F-EMC HBAThis section describes the procedures required to install one or more Qlogic QLA2100F-EMC host bus adapters (HBAs) into a Solaris X86 host and configure the host for Symmetrix Fibre Channel. (Refer to Table 10-1 on page 10-3 for approved hosts and HBAs.)

This section includes the following subsections:

• Setup Checklist on page 10-5• Installing the HBA on page 10-7• Configuring Firmware Settings on page 10-7• Verifying the Disk Media on page 10-8• Upgrading HBA Firmware on page 10-9• Installing the HBA Driver on page 10-10• Editing Host Files on page 10-12

Setup Checklist The following is a step-by-step checklist of the procedures used to integrate a Solaris X86 host with the Symmetrix using the Qlogic QLA2100F-EMC HBA. See the references within each step below for specific procedures. Be sure to follow these steps in order as described, to ensure proper setup of the HBA.

This installation should be performed only by personnel having a basic knowledge of Solaris X86 system administration.

1. Verify that the QLA2100F-EMC HBA is installed in the EMC-qualified Solaris X86 host system, and that the Symmetrix is connected to the host.

• For information on the qualified host and HBA, refer to Table 10-1 on page 10-3.

• For information on installing the HBA, refer to the Qlogic Hardware Install Guide QLA2000/2000F/2100/2100F/2200/2200F, which is included with the HBA.

2. Boot the host and verify the correct firmware/HBA BIOS version and firmware settings.

• For information on qualified firmware, refer to Table 10-1 on page 10-3.

• For information on verifying the firmware version and settings, refer to Configuring Firmware Settings on page 10-7.


10

10-6


• For information on upgrading firmware, refer to Upgrading the Firmware/Flash BIOS on page 10-10.

3. Use the scan utility function of the HBA firmware utility to verify that the HBA "sees" the Symmetrix.

• For information on the scan utility function, refer to Verifying the Disk Media on page 10-8.

4. Install the EMC-approved driver for the QLA2100F-EMC HBA.

• For information on qualified HBAs driver versions, refer to Table 10-1 on page 10-3.

• For information on obtaining and installing the latest HBA driver, refer to Installing the HBA Driver on page 10-10.

5. Verify that the files listed below are configured properly. Generally, if any changes are made to these files, the system must be rebooted with the reboot-- -rv command.

• /kernel/drv/qla2100.conf — Refer to qla2100.conf on page 10-12• /kernel/drv/sd.conf — Refer to sd.conf on page 10-16• /etc/system — Refer to etc/system on page 10-18

6. After steps 1 through 5 are complete and the system has been rebooted, you will be able to see all Symmetrix raw devices in the /dev/rdsk/ directory. To see all targets and LUNs in the Symmetrix configuration, use the ls /dev/rdsk/*s0 command. You can also view Symmetrix devices by issuing the format command.

Refer to the Solaris Environment chapter of the Symmetrix Open Systems Environment Product Guide (Volume I) for format command usage.

7. To partition and label raw devices, follow the procedures under Partitioning and Labeling a New Device on page 10-19.

8. To create and mount a file system, follow the procedures under Creating and Mounting a UFS File System on page 10-23.

9. To add a Symmetrix device on line, follow the procedures under Adding Devices On Line on page 10-24.

Adding devices on line is not currently supported in a hub environment.



Installing the HBA To install the QLA2100F-EMC, follow the instructions in the Qlogic Hardware Install Guide QLA2000/2000F/2100/2100F/2200/2200F (P/N FC0151102-00), which is included with the HBA.

Configuring Firmware Settings

After installing all QLA2100F-EMC HBAs into the host, follow these steps for each QLA2100F-EMC. There are some redundant settings between the firmware utility and the driver configuration file (qla2100.conf). However, the driver configuration variable settings supersede the corresponding settings in firmware utility.

Verify the CorrectFirmware Version

Refer to Table 10-1 on page 10-3 for the correct HBA BIOS version. You can determine the firmware (HBA BIOS) version at boot time from the QLA2100 banner or from the QLA2100 Fast!Util options menu.

• To determine the firmware version from the QLA2100 banner, boot the host and watch for the QLA2100F banner (see Figure 10-1). The banner disappears quickly, so watch carefully.

> If the ROM BIOS version is 1.37, continue to Set the Firmware Variables on page 10-8.

> If the ROM BIOS version is not 1.37, upgrade the firmware as described under Upgrading HBA Firmware on page 10-9, then go to Set the Firmware Variables on page 10-8.

Figure 10-1 QLA2100F-EMC Banner Example

• To determine the firmware version from the QLA2100 Fast!Util options menu:

a. Boot the host. As soon as the QLA2100F banner (see Figure 10-1) appears, press <Alt> <Q> to enter the Fast!Util Options menu.

b. Select Configuration Settings from the menu.

c. Select Host Adapter Settings from the Configuration Settings menu.

d. Under Host Adapter Settings, note the BIOS Version:

Qlogic Corporation

QLA2000, QLA2100 PCI Fibre Channel ROM BIOS Version 1.37

Copyright © Qlogic Corporation 1993-1999 All rights reserved

Press <ALT - Q> for Fast!UTIL

www.qlc.com


10

10-8


• If the version is 1.37, continue to Set the Firmware Variables.• If the version is not 1.37, upgrade the firmware as

described under Upgrading HBA Firmware on page 10-9, then go to Set the Firmware Variables.

Set the FirmwareVariables

1. From the Fast!Util options menu, select Configuration Settings.

2. On the Configuration Settings menu, select Restore Default Values.

3. On the Configuration Settings menu, select Advanced Adapter Settings.

4. Change the setting for Max Throttle to 20.

5. Change the setting for Max Luns to 128. (The factory setting is 8, but this must be changed to utilize all 128 LUNs available from the Symmetrix.)

6. Save all changes.

7. Use the Fibre Disk utility to verify the disk media, as described under Verifying the Disk Media on page 10-8.

Verifying the Disk Media

To verify that the HBA can see the Symmetrix, use the Fibre Disk utility to scan and verify disk media.

1. Under the Fast!UTIL Options menu, select FIBRE DISK UTILTY.

This step assumes that you are already in Fast!Util. If you are not, boot the host, and as soon as the QLA2100F banner (see Figure 10-1) appears, press <Alt> <Q> to enter the Fast!Util Options menu.

2. You should see SYMMETRIX in a Fibre Channel device list of all possible 125 targets, as shown below. Page down if necessary to display all targets in the list.

• If SYMMETRIX appears in the list, go to step 3.• If SYMMETRIX does not appear in the list, verify the

following, then start this procedure again at step 1:> that the correct Symmetrix port is connected to the host.> that the Symmetrix is on line.> that the cables are not damaged.

ID VENDOR PRODUCT REV NODE NAME<Hard loop ID> EMC SYMMETRIX <micro code revision> 01000006048___



3. Use the arrow keys to select SYMMETRIX from the list of targets, then press <Enter>.

4. A list of LUNs appears—select any LUN from the list.

5. A Disk Utility Options menu appears. Select VERIFY DISK MEDIA.

6. Select CONTINUE WITH VERIFY.

7. After media verification has completed:

• If the message Media Verification Complete appears, press <Esc> repeatedly to exit Fast!Util and reboot the host, then continue with Installing the HBA Driver on page 10-10.

• If the media verification fails, verify:

> that the Hard Loop IDs are unique between the host bus adapter and the Symmetrix.

> that the cables and connectors are not damaged.

Upgrading HBA Firmware

This procedure is necessary only if you need to upgrade the QLA2100F-EMC firmware/HBA BIOS version. (Refer to Verify the Correct Firmware Version on page 10-7.)

This section contains information specific to creating HBA firmware (flash BIOS) installation disks and upgrading the firmware (flash BIOS) to a host bus adapter.

Creating anInstallation Diskette

To create a QLA2100 firmware/HBA BIOS installation diskette, follow these steps:

1. Obtain the firmware/HBA BIOS:

a. Click ADAPTER DRIVERS & UTILITIES.

b. Click QLA2100/QLA2000.

c. Click EMC Approved Drivers.

d. Click the file containing the firmware (flash BIOS).

e. Save the file to local c:\ root directory.

2. The file is a self-extracting ZIP file that must be extracted to a bootable diskette drive. Use an IBM-formatted diskette on any Microsoft Windows machine to create a bootable diskette:

a. Open a DOS window.


10

10-1


b. At the DOS window, type c:\ <Enter> to go to the root directory.

c. Insert blank diskette into diskette drive.

d. At DOS window type format /s a: <Enter>.

3. When formatting is complete, type (at the C: prompt) (download filename) a: <Enter>, to unzip the firmware programs to the bootable diskette.

Upgrading theFirmware/Flash BIOS

To upgrade the firmware/flash BIOS, complete these steps:

The following procedures must be done with QLA2100F-EMC HBA(s) installed in the host.

1. Insert the installation diskette into the diskette drive.

2. Reboot the host.

3. After the host has rebooted, the DOS prompt appears. Type Ql2xutil /L /F <Enter>.

The firmware/HBA BIOS upgrade might take a few minutes.

4. After the upgrade is complete, remove the diskette and reboot the host. During boot-up, the QLA2100F banner (see Figure 10-1) should display BIOS Version 1.37.


The Solaris X86 operating system interface to the Symmetrix Fibre Channel director requires HBA driver software. The driver functions at a layer below the Solaris SCSI driver to present Fibre Channel devices to the operating system as if they were standard SCSI devices.

Obtaining the LatestDriver

Be sure you have the latest qualified driver software. This is available on the Qlogic website is the Release CD-ROM does not have the latest version:

• From Qlogic website: http://www.qlc.com

a. Click on ADAPTER DRIVERS & UTILITIES

b. Click on QLA2100/QLA2000

c. Click on EMC Approved Drivers

0 Symmetrix Fibre Channel Product Guide


d. Copy the EMC-approved X86 driver to the /tmp directory your Solarix X86 host.

• From the Release CD-ROM:

a. Insert the CD-ROM into the Solaris X86 host. The CD will auto-mount.

b. Change to the directory /cdrom/qlogic/solarx86.

c. Type cp qla2100.Z /tmp <Enter>.

Install the Driver Refer to the release notes provided with the current driver for information that may be unique to new driver revisions.

1. The first step in installing the driver depends on the file format and name:

• If the driver file is not compressed—that is, if its filename extension is not .z or .Z—go to step 3.

• If the filename has an uppercase .Z extension, go to step 2.

• If the file name has an lowercase .z extension, you must make the extension uppercase. Type mv qla2100.z qla2100.Z <Enter>, then go to step 2.

2. Type uncompress <file name.Z> <Enter>.

3. Type pkgadd -d /tmp/qla2100 <Enter>.

4. Type GO <Enter> to start scanning the diskette.

5. When the scan is complete, type 1 <Enter> to select the QLA2100 package.

6. Press <Enter> to place the driver into the default directory.

7. Type Y <Enter> to continue.

8. After the package has been package has been installed successfully, edit the file described under Editing Host Files on page 10-12.

9. Type reboot -- -rv <Enter> to reboot the host with the -r (reconfigure) option.


10

10-1


Editing Host Files To insure smooth integration and maximum performance from the host and Symmetrix, you must edit these files (as described in detail later):

• Qlogic driver configuration file qla2100.conf — Refer to qla2100.conf below

• Host driver configuration file sd.conf — Refer to sd.conf on page 10-16

• System specification file etc/system — Refer to etc/system on page 10-18


qla2100.conf Proper settings in the driver configuration file /kernel/drv/qla2100.conf are crucial for Symmetrix/host integration. Each HBA has its own settings for each of the 17 variables in qla2100.conf.

Each HBA variable line in qla2100.conf corresponds to the instance number of the HBA in the file /var/adm/messages. In the above example, hba0 of hba0-enable-adapter-hard-loop-ID=1 corresponds to instance #0 in /var/adm/messages.

unix: QLogic qla2100 Fibre Channel Driver v2.20 Instance : 0unix: pcplusmp: pci1077,1 (qla2100) instance #0unix: vector 0x10 ioapic 0x4 intin 0x23is bound to cpu 1unix: PCI-device: pci1077,1@4, qla21000unix: qla21000 is /pci@2,0/pci1077,1@4

unix: QLogic qla2100 Fibre Channel Driver v2.20 Instance : 1unix: pcplusmp: pci1077,1 (qla2100) instance #1 unix: vector 0 x11 ioapic 0x4 intin 0x1f is bound to cpu 1unix: PCI-device: pci1077,1@5, qla21001unix: qla21001 is /pci@2,0/pci1077,1@5

Example

In the example below, a separate variable line is dedicated to each HBA (hba0, hba1, and hba2).

# Adapter hard loop ID enable.# 0 = disable, 1 = enabledhba0-enable-adapter-hard-loop-ID=1;hba1-enable-adapter-hard-loop-ID=1;hba2-enable-adapter-hard-loop-ID=1;

# Adapter hard loop ID.# Range: 0 - 126



hba0-adapter-hard-loop-ID=125;hba1-adapter-hard-loop-ID=125;hba2-adapter-hard-loop-ID=125;

Using the same hard loop ID for all HBAs is a valid configuration only in a hubless loop connection.

Editing the File

The driver configuration file contains important information about how the driver should behave. The file is created automatically when the HBA driver is installed.

Table 10-3 lists the required settings for the configuration file variables, and descriptions of the variables follow the table. Verify that all variables are set as shown, and change any if necessary.

Changes to qla2100.conf will not take effect until the host is rebooted.

Table 10-3 /kernel/drv/qla2100.conf Settings for Solaris X86 Host


Required Setting


hba0-frame-payload-size 1024 bytes 1024 bytes 1024 bytes 1024 bytes

hba0-max-iocb-allocation 256 512 512 512

hba0-execution-throttle 16 20 20 20

hba0-login-retry-count 8 5 5 5

hba0-enable-adapter-hard-loop-ID 0 (disable) 1 (enable) 1 (enable) 1 (enable)

hba0-adapter-hard-loop-ID 0 100 see note b 100

hba0-login-timeout 4 (sec) 4 (sec) 4 (sec) 4 (sec)

hba0-enable-extended-logging 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-enable-64bit-addressing 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-enable-LIP-reset 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-enable-LIP-full-login 1 (enable) 1 (enable) 1 (enable) 1 (enable)

hba0-enable-target-reset 0 (disable) 0 (disable) 0 (disable) 0 (disable)



10

10-1


a. PowerPath is not currently supported in a hub environment.

b. In a hub environment, the hard loop ID for each HBA must be unique.

Descriptions of qla2100.conf Variables

hba0-frame-payload-size — Configuration flag (512, 1024 or 2048 bytes) for "maximum frame length."

hba0-max-iocb- allocation — Number of commands (1 to 750) queued internally within the HBA. Exceeding the adapter ’s buffers causes unnecessary retries, which impact performance. The maximum setting might be less, depending on the size of the firmware.

hba0-execution- throttle — Maximum number of commands (1 to 65635) sent to the LUN by the firmware. Exceeding a device’s capabilities causes unnecessary command retries, which impact performance.

hba0-login-retry-count — Maximum number (0 to 255) of retries to attempt when login into a device fails. Large values can cause long delays during initialization.

hba0-enable-adapter-hard-loop-ID — Enables/disables the hard loop ID and activates (if enabled) the setting for variable hba0-adapter-hard-loop-ID. (See the next item.)

hba0-adapter-hard-loop-ID — Sets (if activated) the hard loop ID (in the range 1 to 125) for the HBA during the Loop Initialization Process (LIP). If hba0-enable-adapter-hard-loop-ID and hba0-adapter-hard-loop-ID are not set as shown in Table 10-3, the LIP might fail and the host might not recognize the Symmetrix. These variables become crucial in a hub environment, since no device

hba0-enable-database-storage 0 (disable) 0 (disable) 0 (disable) 0 (disable)

hba0-scsi-reset-delay 5000 (millisec) 5000 (millisec) 5000 (millisec) 5000 (millisec)

hba0-link-down-error 1 (disable) 0 (enable) 0 (enable) 1 (disable)

hba0-port-down-retry-count 30 5 5 5

hba0-loop-down-timeout 60 (sec) 60 (sec) 60 (sec) 60 (sec)

Table 10-3 /kernel/drv/qla2100.conf Settings for Solaris X86 Host (continued)


Required Setting




(Symmetrix target or host bus adapter) can have the same hard loop ID. The host HBA is conventionally assigned the highest Hard Loop ID, starting from 125 and working down (124, 123, 122, etc.). The Symmetrix is conventionally assigned a lowest Hard Loop ID for each port, starting with 0 and working up (1, 2, 3, etc.).

Example: The following example is a configuration for three QLA2100F-EMC HBAs with separate Hard Loop IDs:

# Adapter hard loop ID.# Range: 0 - 126hba0-adapter-hard-loop-ID=125;hba1-adapter-hard-loop-ID=124;hba2-adapter-hard-loop-ID=123;

hba0-login-timeout — Sets the login timeout (in seconds).

hba0-enable-extended-logging — Enables/disables the driver extended error reporting capabilities.

hba0-enable-64bit-addressing — Enables/disables the adapter to directly access memory above 4 gigabytes with 64-bit Direct Memory Access addressing.

hba0-enable-LIP-reset — Enables/disables the adapter to issue a LIP reset during Fibre Channel reset.

Only one of the variables hba0-enable-LIP-reset, hba0-enable-LIP-full-login, and hba0-enable-target-reset should be enabled at the same time.

hba0-enable-LIP-full-login — Enables/disables the adapter to issue a LIP full login reset during Fibre Channel reset. (See the note below hba0-enable-LIP-reset.)

hba0-enable-target-reset — Enables/disables the adapter to issue a LIP target reset during Fibre Channel reset. (See the note below hba0-enable-LIP-reset.)

hba0-enable-database-storage — Enables/disables the driver to save device position on the Fibre Channel bus.

hba0-scsi-reset-delay — Delay after a reset before sending commands to the devices on the Fibre Channel bus.

hba0-link-down-error — Disables (if set to 0) all link_down time out values. The sd driver will not be notified of any and error conditions if the qla2100 driver detects a link_down condition. If the Symmetrix


10

10-1


goes off line or the link with the host is broken for any reason, the qla2100 driver holds all pending I/Os indefinitely until the link is restored or the Symmetrix rejoins the loop. In a Power Path environment, set this variable to 1, so the PowerPath driver will be notified of any error conditions.

hba0-port-down-retry-count — Number of command retries to be done when devices are not responding on the Fibre Channel bus. Large values may cause long delays for fail over software to detect a failing device.

hba0-loop-down-timeout — Time the driver waits for a Fibre Channel loop to come up before reporting the failure. Small values may report transient errors that should be ignored.

sd.conf Symmetrix devices are addressed on the Fibre Channel bus using the Symmetrix Hard Loop ID as a Target ID. There can be only one Target ID per Symmetrix port. A Target ID can have up to 128 luns. By default, Solaris X86 searches only for Target IDs; if LUN addressing is required, you must modify the lower-level driver configuration file /kernel/drv/sd.conf.

Definition lines must be added to sd.conf for every LUN of every target configured to the host in the Symmetrix. In a hubless connection, all Symmetrix ports can have the same port ID. In a hub environment, each Symmetrix port must have a different Hard Loop ID (Target ID).

Device definition files are available on EMC’s FTP server, ftp.emc.com, in /pub/symm3000/solaris. The file sd.conf.fibre is a device definition file for Fibre Channel devices. You can copy/paste the contents of the file into the file /kernel/drv/sd.conf in the Solaris X86 host. Use only those lines from sd.conf.fibre that apply to your host’s configuration.





Example of sd.conf for Arbitrated Loop in a Hubless Environment

The following example is for a hubless loop configuration with a Target ID (Symmetrix Hard loop ID) of 0:

name=”sd” class=”scsi”target=0 lun=0;name=”sd” class=”scsi”target=0 lun=1;...name=”sd” class=”scsi”target=0 lun=126;name=”sd” class=”scsi”target=0 lun=127;

Add only those Target/Lun definitions that are needed. In a direct-connect configuration, it is recommended that all Symmetrix ports be given the same Target ID. If different Hard Loop IDs are used for each port, lines must be added to sd.conf for each LUN of each target. The fewer Target/Lun definitions in sd.conf, the less time it takes to boot.

Example of sd.conf for Arbitrated Loop in a Hub Environment

The following example is for a hub loop configuration with two Target IDs of 0 and 1. Each target has 128 luns. For every Symmetrix port assigned to a host, there must be a target and series of LUNs configured in sd.conf. Targets are determined from the Symmetrix Hard Loop ID.

In this example, 256 separate Target/LUN definitions are added to sd.conf.

name="sd" class="scsi" target=0 lun=0;name="sd" class="scsi" target=0 lun=1;...name="sd" class="scsi" target=0 lun=126;name="sd" class="scsi" target=0 lun=127;name="sd" class="scsi" target=1 lun=0;name="sd" class="scsi" target=1 lun=1;.


10

10-1


.

.name="sd" class="scsi" target=1 lun=126;name="sd" class="scsi" target=1 lun=127;

etc/system The following variables in the file /etc/system should be set to maximize system performance.






3. Set sd_io_time depending on whether PowerPath will be used:

• If no PowerPath, type set sd:sd_io_time = 0x78 <Enter>.• If PowerPath, type set sd:sd_io_time = 0x3C <Enter>.


Bit Mask Meaning


4 0x10 Link enable









Partitioning and Labeling a New DeviceSolaris X86 platform disk partitioning has one more level than that of Solaris for Sparc. On the Solaris Sparc platform, slices are the primary method of partitioning a disk. For the X86 platform, slices are sub-partitions of PC partitions. Using the fdisk command allows up to four PC partitions on a disk device. This is done so that more than one operating system can reside on or be booted from the same disk.

Disk Device File Naming Conventions

Raw disk device filenames take two forms:

• /dev/rdsk/cCtTdDsS • /dev/rdsk/cCtTdDpP

where:

• C is the occurrence of the host adapter board.• T is the SCSI target ID.• D is the logical unit number (LUN) of the disk device.• S is the disk slice number.• P is the fdisk partition number. P can range from 0 to 4. The p0

node corresponds to the whole disk, and the p1 to p4 nodes correspond to partitions displayed by the fdisk command.

The fdisk command works only if device p0 represents the entire device.

Partitioning and Slicing Symmetrix Devices

To partition and slice a Symmetrix device for the use of Solaris x86, log in as root and follow the procedure below for each new device. Once the Symmetrix and the host have been integrated there will be raw device files in the /dev/rdsk/ directory representing the target and LUNs specified by the EMC customer engineer.



The host searches for all disks and displays a list, placing all unlabeled disks at the beginning of the listing. Here is an example:

AVAILABLE DISK SELECTIONS:0. c0t0d0 <DEFAULT cyl 5512 alt 2 hd 8 sec 193> /pci@1,0/pci9004,8178@a/sd@0,01. c1t0d0 <DEFAULT cyl 4093 alt 2 hd 15 sec 64> /pci@0,0/pci9004,8478@8/sd@0,02. c1t0d1 <DEFAULT cyl 4093 alt 2 hd 15 sec 64> /pci@0,0/pci9004,8478@8/sd@0,1Specify disk (enter its number):

Partitioning and Labeling a New Device 10-19

10

10-2


2. At the Specify disk prompt, enter the number of the first EMC drive. The following menu appears:

3. At the format> prompt, type the word type and press <Enter>. The following menu appears:

Type 0 <Enter>. A display similar to the following appears:

clt3d6: configured with capacity of 1.05GB<EMC-SYMMETRIX-5265 cyl 2296 alt 2 hd 15 sec 64>

Format>

FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk fdisk - run the fdisk program repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quitformat>

AVAILABLE DRIVE TYPES: 0. Auto configure 1. DEFAULT 2. DEFAULT 3. DEFAULT 4. OtherSpecify disk type (enter its number)[3]:



4. At the format> prompt, type fdisk <Enter>.

• If no PC partition table exists on the Symmetrix, a message similar to the following appears:

No fdisk table exists. The default partition for the disk is:a 100% "SOLARIS System" partitionType y to accept the default partition, otherwise type n to

edit the partition table.

You must create a default partition or specify the initial table values. Type Y <Enter> to accept the default option. This allocates 100% of the disk for the Solaris X86 system and makes the Solaris X86 system partition active.

• If a partition table already exists, the command program displays a partition table and a menu as shown below, with options allowing you to modify the table:

Figure 10-2 Solaris X86 fdisk Menu Example

CAUTION!Changing the partition table results in loss of any previous data.

> If Type is Solaris and Status is Active, type 4 <Enter> (Exit), then proceed to Step 5.

> If Type is Solaris and Status is not Active, type 2 <Enter>. When prompted for the partition to activate or boot from, enter the number of the Solaris X86 system

CylindersPartition Status Type Start End Length % ========= ====== ===== ===== ===== ====== ===

1 Active Solaris 1 4094 4094 100

SELECT ONE OF THE FOLLOWING:

1. Create a partition2. Specify the active partition3. Delete a partition4. Exit (update disk configuration and exit)5. Cancel (exit without updating disk configuration)

Enter Selection:

Partitioning and Labeling a New Device 10-21

10

10-2


partition. If the fdisk main menu (see Figure 10-2) shows a Solaris X86 partition with a status of Active, type 4 <Enter>, then proceed to Step 5.

> If there is an unwanted partition, type 3 <Enter>. When prompted for the partition to delete, enter the number and press <Enter>. When prompted to verify the deletion, press <Y>, then proceed to Step 5.

> If you want to create a Solaris system partition, type 1 <Enter>. When prompted with a list of partition types, type 1 <Enter> to select Solaris system partition.

When prompted for the percentage of the disk you want to use for the partition, type 100 <Enter>. If 100% of the disk is not available, use all of the disk that is available.

When prompted to activate the partition, type Y <Enter>, then proceed to Step 5. (Solaris X86 partitions are accessible only if they are in the Active state.)



7. When prompted to display a listing of the disks, type di <Enter>.

8. Repeat steps 2 through 7 for each remaining Symmetrix disk.



Creating and Mounting a UFS File System To create standard UNIX file systems under the Solaris X86 operating system, log in as root and proceed as described in this section for each previously labeled device.

Create a New File System

Once you have formatted, partitioned, and labeled each Symmetrix disk device (see Partitioning and Labeling a New Device on page 10-19), create a new file system for each Symmetrix device. To do this, use the newfs command in a statement similar to the following:

newfs /dev/rdsk/c1t0d0s2 <Enter>

When prompted to confirm the construction of a new file system, type Y <Enter>.

For default labels, always use slice 2 for mounted file systems. The example above creates a new file system for the Symmetrix disk connected to SCSI controller 1, target ID 0, lun 0, slice 2.

Create a Mount Directory

Once you have created the file systems for each Symmetrix device, create a mount directory for each device. Type a statement similar to the following for each Symmetrix device:

mkdir /fs/c1t0d0s0 <Enter>

where /fs/c1t0d0s0 is the complete path for the new file system directory.

The /fs directory must exist prior to creating the mount directories.

Mount the Filesystem

To mount each filesystem, type a statement similar to the following:

mount -F ufs /dev/dsk/c1t0d0s2 /fs/c1t0d0s2 <Enter>

This action mounts the raw device c1t0d0s2 onto the mount point /fs/c1t0d0s2.

Creating and Mounting a UFS File System 10-23

10

10-2


Adding Devices On LineWhenever devices are added to the Symmetrix while it is on line, or device channel addresses are changed, perform the steps described below to introduce the new devices to the system.

Before performing an on-line upgrade, verify that the targets and LUNs being added are defined in /kernel/drv/sd.conf as described under sd.conf on page 10-16. If the LUNs being added are not specified in /kernel/drv/sd.conf, add the definitions and reboot the host to incorporate the changes.

1. Use the Online Upgrade feature at the Symmetrix service processor to add/map new drives to the host channel. Consult your EMC CE for this procedure.

2. Execute the following three utilities in order to detect and create symbolic links for new devices:

• drvconfig • disks -C • disks

3. Follow the instructions in Partitioning and Labeling a New Device on page 10-19 to introduce new devices to the host environment.



Solaris X86 Hub Configuration GuidelinesThis section provides guidelines and limitations for using hubs in a Solaris X86/Symmetrix Fibre Channel storage network.

Refer to Loops with Hubs on page 1-22 for descriptions of various hub configurations.

Solaris OperatingSystem

Solaris version is 7 is required.


• 1 to 6 HBA connections• 1 to 6 Symmetrix Fibre Channel port connections


Hub-to-hub connections are not supported.

Adding Devices Adding devices on-line is not supported.

Multiple Host Systems Up to six HBAs on up to to six hosts (six HBAs total) can be connected to the loop, as long as there is some consideration for total I/O demand. Estimate each host’s I/O per second using a performance analysis tool such as SAR or Symmetrix Manager. Host nodes can be added to the hub loop within the suggested limit of a combined estimated 1000 IOPS (8KB block size).





Solaris X86 Hub Configuration Guidelines 10-25

10

10-2



PART 3

This section describes configuration of the hosts that Symmetrix supports over Fibre Channel fabric. The contents of Part 3 are:

• Chapter 11, Solaris SPARC Host on Fabric

• Chapter 12, Windows NT Host on Fabric

Host Support on Fabric

11

This chapter provides information specific to Solaris SPARC hosts connecting to Symmetrix over a Fibre Channel fabric. (Chapter 3 describes Sun Solaris support over arbitrated loop.) This chapter includes the following sections:

• Solaris Fibre Channel Environment .............................................. 11-2• Host Connectivity ............................................................................ 11-3• Symmetrix Configuration ............................................................... 11-4• Host Configuration with Jaycor HBA........................................... 11-5• Dynamic Reconfiguration in the Ultra Enterprise 10000 ......... 11-22


Solaris SPARC Host onFabric

Solaris SPARC Host on Fabric 11-1

11

11-2

Solaris SPARC Host on Fabric

Solaris Fibre Channel EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the Solaris host environment.




Addressing • Sun uses SCSI-2 device access protocol in addressing its Fibre Channel devices. SCSI-3 Array Controller addressing modes are not supported. The peripheral device access mode is supported in Symmetrix to address up to 128 logical devices (in an address range of 0 to 255). Refer to Appendix C for the available addressing modes.



11Solaris SPARC Host on Fabric

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use on a fabric with the Sun hosts shown in Table 11-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.


The Fibre Channel adapter driver functions as a device driver layer below the standard “sd” Solaris SCSI adapter driver. The Fibre Channel interface is therefore transparent to the Solaris disk administration system.

Table 11-1 HBAs for Sun Hosts on Fabric

Host TypeMinimum OS Version Host Bus Adapter Driver Version Max LUNs

SPARC, UltraSPARC (Sbus)

Solaris 2.5.1 Jaycor FC-1063-EMC, rev H. BIOS version 13.3.5

V2.2.2.EMC 128

Jaycor FC64-1063-EMC, rev C, D, or E; BIOS version 13.3.5

V2.2.2.EMC 128

Jaycor FCIN-1063-EMC, rev B V2.2.2.EMC 128


11

11-4




b. Enabled for Veritas DMP.


Table 11-2 Symmetrix Configuration for Sun Hosts

Parameter Setting



Hard Addressing (H-bit) Disabled



Common Serial Number (C-bit) Disabled b

Disable Queue Reset on Unit Attention (D-bit) Disabled c

Point-to-Point (PP-bit) Enabled



Host Configuration with Jaycor HBAThis section describes the tasks required to install one or more Jaycor host bus adapters into a Sun Solaris host and configure the host for Symmetrix Fibre Channel.

Refer to Table 11-1 on page 11-3 for approved HBAs. Symmetrix Fibre Channel does not currently support the mixing of different types of HBA in a single server.

Planning Zoning and Connections

Before setting up the hardware in a fabric switch configuration with Symmetrix, you should plan an effective zone map. Check the switch manufacturer’s user documentation for help on defining zones.

Table 11-3 shows a planning example.

a. fca is the driver for the 32-bit HBA: FC-1063-EMC. fcaw is the driver for the 64-bit HBA: FC64-1063-EMC.

Installing the HBA Follow the instructions included with your adapter, including installation of all required Solaris system patches. The adapter installs into a single Sbus slot. (The card has no user-configurable jumpers or switches.)

Table 11-3 FC-SW Zoning and Connections

Host HBA a FA Target LUNs Zone

SUN1 fca0 15a 0 0–3 0

15b 1 15–17

SUN2 fcaw0 15a 0 4–6 0

fcaw1 15b 1 18, 20

SUN3 fca0 15a 0 7–9 1

fcaw0 15b 1 19, 21–24


11

11-6



The HBA I/O driver software is required to interface the Fibre Channel Adapter card to the Solaris Operating system. The driver software will provide the SCSI HBA service to the SCSI Disk Target Adapter Driver (sd) through the Sun Common SCSI Architecture transport layer. After the HBA driver software is installed, the user can use any of the Symmetrix volumes just like a normal Sun volume, and can use all of the software normally used in Sun systems, such as Solstice Disk Suite, Veritas, and Powerpath.


1. Be sure you have the latest qualified driver software. If necessary, obtain it on CD-ROM from Jaycor, or FTP the driver from the Jaycor website (currently www.jni.com). Refer to release notes provided with the current driver for information that may be unique to new driver revisions.



from the Jaycor WebSite

Use the following procedure to download the Jaycor fca driver from the Jaycor web site, and perform a first-time install.

1. Use a web browser to access to this link:

http://www.jaycor.com/fibre/ftp/Released/Symmetrix/solaris/v2.2.2.EMC

Type of Installation

Installing From: Go to:

New Web Downloading and Installing a New Driver from the Jaycor Web Site on page 11-6


Upgrade Web Downloading and Installing a Driver Upgrade from the Jaycor Web Site on page 11-8





3. Add the appropriate package:




Use the following procedure to load the fca driver from the Jaycor CD-ROM, and perform a first time install.

1. Insert the JNI CD-ROM, then type volcheck <Enter>.






If HBA is: Enter:




If HBA is: Enter:





11

11-8


3. Add the package:




Jaycor Web Site

Use the following procedure to download the fca driver from the Jaycor web site, and perform a Fibre Channel driver upgrade.

1. Use a web browser to access to this link:




If HBA is: Enter:
















6. Restore the appropriate file:



If HBA is: Enter:




If HBA is: Enter:




If HBA is: Restore file:





11

11-1



CD-ROM

Use the following procedure to load the Jaycor driver from the Jaycor CD-ROM, and perform a Fibre Channel drive upgrade.










If HBA is: Enter:




If HBA is: Enter:




If HBA is: Enter:






6. Edit any necessary files as described under Incorporating Symmetrix Fibre Channel below.



Devices accessed via Fibre Channel using the Jaycor driver will be addressed behind a single target ID with up to 128 LUNs. This differs from existing SCSI device addressing, which may have multiple targets and LUNS.

Edit the HBA DriverConfiguration File

1. The configuration file is created automatically by pkgadd. The file contains important information about how the driver should behave. The file name depends on the HBA:

2. If necessary, edit the configuration file as shown in Table 11-4.

If HBA is: File path and name are:




Table 11-4 Jaycor HBA Configuration File Parameters


fca_nport Specifies whether HBA port is on arbitrated loop (fca_nport = 0) or fabric (fca_nport = 1)

0 a

failover Determines how many seconds PowerPath should wait to fail over if one path fails

60 b

failover_extension Extends a target’s failover period by the number of seconds specified, to perform target rediscovery

0

recovery_attempts Determines how many times the driver should try to log into the Symmetrix after a link failure

5

class2_enable Enables (if 1) or disables (if 0) class 2 exchanges (ACK_1 mode) for devices that support class 2

0

fca_heartbeat Determines the number of microseconds between test frames. (This is used only for debugging.)

0



11

11-1


a. Be sure to set fca_nport to 1.

b. Set failover to 0 if you are not using EMC PowerPath for devices accessed through this Fibre Channel connection.

reset_glm Resets the link before adapter initialization if set to a value other than 0

0

timeout_reset_enable Clears the problem when commands are being timed out:• If 0, driver attempts to clear the command by

sending an ABTS_LS request to the target• If 1, driver attempts to reset the target

0

busy_retry_delay Sets the time delay (in 10-millisecond increments) after the target returns BUSY status

0

link_recovery_delay Sets the time delay (in 10-millisecond increments) between Link Up and Login Recovery, to help ensure link stability before recovery

100

scsi_probe_delay Sets the delay (in 10-millisecond increments) before SCSI probes are allowed to occur during boot.

500

abort_retry_delay Sets the time delay (in 10-millisecond increments) before a command is retried due to an abort from timeout or link recovery condition

100

def_hba_binding Sets the HBA binding for every Target/LUN instance that does not explicitly define one

fcaw* c

def_wwn_binding Sets the 16-digit hexadecimal default world-wide name (WWN) binding for every Target/LUN instance that does not explicitly define one

$xxxxxxxxxxxxxxxx d

def_port_binding Sets the 6-digit hexadecimal default port binding for every Target/LUN instance that does not explicitly define one

xxxxxx e

fca_verbose Determines how many messages are displayed directly to the console.• A setting of 0 quiets the driver messages to the

console, but still prints them to the system message log. (A "boot -v" overrides this setting and makes the driver verbose again.)

• A setting of 1 makes the driver print all messages to the console and to the system message log

1

Table 11-4 Jaycor HBA Configuration File Parameters (continued)




c. An asterisk (*) following an HBA name indicates all instances of that HBA driver. Set this value to fas to disable the default bind to fcaw*.

d. A $ preceding the string indicates that static binding is enabled. An x in place of a digit indicates "don’t care" for that digit. The default value shown means the WWN is static (don’t care). (Note that the default is shown on two lines only because of space limitations.)

e. A $ preceding the string indicates that static binding is enabled. An x in place of a digit indicates "don’t care" for that digit. The default value shown means the port is non-static (don’t care).

Edit the DriverConfiguration File

sd.conf

Understanding Persistent Binding

Matching addresses with their associated devices requires that each Fibre Channel Director port be "bound" to a target number. "Persistent binding" is the method used in the Symmetrix fabric implementation.

From the Solaris and Jaycor driver perspective, there is a major difference between device addressing on a fabric and addressing in an arbitrated loop.

• Arbitrated Loop — The Fibre Channel Director port is bound to the target number that matches the Director port’s arbitrated loop physical address (AL-PA).

• Fabric — There is no concept of an AL-PA, so version 2.2.0 and later of the Jaycor Solaris driver includes a persistent binding function, which provides the ability to specify (in the sd.conf file) the target number to which each Fibre Channel Director port is always bound.

Persistent binding also provides the ability to specify, on an individual LUN basis, which Jaycor drivers probe for specific LUNs. Always use persistent binding when implementing a fabric that provides connectivity between Symmetrix devices and Sun Solaris servers.

CAUTION!Before implementing persistent binding, be sure you understand the effects.

What Happens Without Persistent Binding

Without a persistent binding mechanism, the host cannot maintain persistent logical routing of the communication from a device address (/dev/rdsk/cNtNdNsN) across the fabric to a Symmetrix volume. If the physical configuration of the switch is changed (for


11

11-1


example, the cable is swapped or the host is rebooted), the logical route becomes inconsistent, causing possible data corruption if the user application is modifying data through inconsistent logical routing of the communication from the driver entry point to a volume in a Symmetrix across the fabric.

Jaycor Persistent Binding Implementation

Jaycor persistent binding in a Solaris environment is implemented through the addition of two new string parameters to the target LUN definition line of the sd.conf file. The new parameters, hba and wwn, are used only by the Jaycor driver, and are ignored by all other SCSI drivers.

There are also settings to enable persistent binding. These settings must be present in the Jaycor configuration file (fca.conf or fcaw.conf). The mechanism of the persistent binding is implemented like a filter inside the Jaycor HBA driver. The Jaycor driver uses the parameter set in sd.conf to maintain the persistent binding.

The hba parameter is appended to the end of a target LUN definition line to specify the Jaycor adapter that will probe for that target and LUN address. This parameter should be specified for all target LUN addresses that are to be bound to a Jaycor adapter. The following examples illustrate target LUN definition lines with the hba parameter.

name="sd" class="scsi" target=0 lun=0 hba="fca0";name="sd" class="scsi" target=1 lun=5 hba="fcaw0";name="sd" class="scsi" target=3 lun=10 hba="fca-pci0";

The first definition illustrates the parameter for a Jaycor FC-1063-EMC adapter. The fca0 adapter driver will probe for target 0 LUN 0. The second definition is for an FC64-1063-EMC adapter. The fcaw0 adapter driver instance will probe for target 1 LUN 5. The third definition is for an FCIN-1063-EMC adapter. The fca-pci0 adapter driver instance will probe for target 3 LUN 10.

The wwn parameter is used to specify the world-wide port name of a Symmetrix FA port that is to be bound to a specific target. The WWPN is a 16-digit hexadecimal number that uniquely identifies a port in a fabric. This concept is similar to the media access layer (MAC) address that is used to uniquely identify every network card port in an Ethernet network.



The following example illustrates the parameter on a target LUN definition line in the sd.conf file.

name="sd" class="scsi" target=1 lun=0 hba="fca0" wwn="50080482B8912B8E";name="sd" class="scsi" target=1 lun=1 hba="fca0" wwn="50080482B8912B8E";name="sd" class="scsi" target=2 lun=8 hba="fca0" wwn="50080482B8912B9E";name="sd" class="scsi" target=2 lun=9 hba="fca0" wwn="50080482B8912B9E";

In this example, the FA port with the WWPN of 50080482B8912B8E will be bound to target 1 and the FA port with the WWPN of 50080482B8912B9E will be bound to target 2. The wwn parameter is only required to be specified on the first LUN of a specific target in order to bind the target for all LUNs.

Target Numbers

Another issue to consider is the target number assigned to each Fibre Channel Director port within the sd.conf file. In the loop environment, the target number is bound to the Fibre Channel Director port’s AL-PA, and is consistent across all servers in a loop. In a fabric implementation, the same port can be bound to a different target number on each server. It is recommended that a common target number be used for the same port across multiple servers. Although this requires the customer to track target numbers and potentially communicate across group boundaries, it should help in managing the overall environment.

Target numbers cannot go beyond 128. If a fabric grows beyond 128 Symmetrix Fibre Channel Director ports, a convention for sub-dividing the target numbers will have to be devised.

Case Study

This case study consists of an environment that includes three Sun SBUS servers connected through an EMC Connectrix ED-1032 Enterprise Director to two Symmetrix Fibre Channel Director ports, as shown in Figure 11-1.


11

11-1


Figure 11-1 Fabric Switch Case Study

SUN1 has a single 32-bit Jaycor HBA that resides in a zone with Fibre Channel Directors (FA) 15a and 15b. SUN2 is configured with two 64-bit Jaycor HBAs. The first HBA (fcaw0) is configured in a zone with FA15a, and the other HBA (fca1) is in a zone with FA15b. SUN3 is configured with a 32-bit HBA that is in a zone with FA15a and a 64-bit HBA that resides in a zone with FA15b.

Table 11-5 lists the desired target LUN mapping for each HBA. EMC Volume Logix may also be implemented on the Symmetrix to provide the maximum level of LUN access control.

SUN 3

Symmetrix

ED-1032

fcaw0

SUN 2

FA15aWWN = 50080482B8912B8E

fca0

fca0

fcaw1

fcaw0

LUN15LUN16

LUN18LUN17

LUN19

LUN21LUN20

LUN22

LUN24LUN23

LUN0LUN1

LUN3LUN2

LUN4

LUN6LUN5

LUN7

LUN9LUN8

SUN 1

FA15bWWN = 50080482B8912B9E

Table 11-5 Case Study LUN Mapping

Host HBA FA Target LUNs Zone

SUN1 fca0 15a 0 0–3 0

15b 1 15–17

SUN2 fcaw0 15a 0 4–6 0

fcaw1 15b 1 18, 20

SUN3 fca0 15a 0 7–9 1

fcaw0 15b 1 19, 21–24



Following are the sd.conf file entries for each server in the case study. It is important to note that, on each server, LUN 0 definitions on targets 0 through 15 are included at the beginning of the sd.conf file. These line definitions do not include hba or wwn. These definitions will be used by any non-Jaycor SCSI adapters, and must be included in the sd.conf file. These definitions will be ignored by all Jaycor drivers, since default hba binding is disabled in the fc*.conf. Also, SUN3 will have a fca.conf file and a fcaw.conf file in the /kernel/drv directory. The fca_nport, fca_hba_binding, and fca_verbose flags (described earlier) should be set in both files.

SUN1 sd.conf file SCSI definitions:

name="sd" class="scsi" target=0 lun=0;name="sd" class="scsi" target=1 lun=0;..name="sd" class="scsi" target=15 lun=0;

SUN1 sd.conf file Jaycor Fibre Channel definitions:

name="sd" class="scsi" target=0 lun=0 hba="fca0" wwn="50080482B8912B8E";name="sd" class="scsi" target=0 lun=1 hba="fca0" wwn="50080482B8912B8E";name="sd" class="scsi" target=0 lun=2 hba="fca0" wwn="50080482B8912B8E";name="sd" class="scsi" target=0 lun=3 hba="fca0" wwn="50080482B8912B8E";name="sd" class="scsi" target=1 lun=15 hba="fca0" wwn="50080482B8912B9E";name="sd" class="scsi" target=1 lun=16 hba="fca0" wwn="50080482B8912B9E";name="sd" class="scsi" target=1 lun=17 hba="fca0" wwn="50080482B8912B9E";




name="sd" class="scsi" target=0 lun=4 hba="fcaw0" wwn="50080482B8912B8E";name="sd" class="scsi" target=0 lun=5 hba="fcaw0" wwn="50080482B8912B8E";name="sd" class="scsi" target=0 lun=6 hba="fcaw0" wwn="50080482B8912B8E";

name="sd" class="scsi" target=1 lun=18 hba="fcaw1" wwn="50080482B8912B9E";name="sd" class="scsi" target=1 lun=19 hba="fcaw1" wwn="50080482B8912B9E";


11

11-1





name="sd" class="scsi" target=0 lun=7 hba="fca0" wwn="50080482B8912B8E";name="sd" class="scsi" target=0 lun=8 hba="fca0" wwn="50080482B8912B8E";name="sd" class="scsi" target=0 lun=9 hba="fca0" wwn="50080482B8912B8E";

name="sd" class="scsi" target=1 lun=20 hba="fcaw0" wwn="50080482B8912B9E";name="sd" class="scsi" target=1 lun=21 hba="fcaw0" wwn="50080482B8912B9E";name="sd" class="scsi" target=1 lun=22 hba="fcaw0" wwn="50080482B8912B9E";name="sd" class="scsi" target=1 lun=23 hba="fcaw0" wwn="50080482B8912B9E";name="sd" class="scsi" target=1 lun=24 hba="fcaw0" wwn="50080482B8912B9E";

Modifying the SystemSpecification File

etc.system

Some parameters in the file /etc/system must be modified as described in the following steps before operating in a Solaris environment.



2. Include the following entry: set scsi_options = 0x7F8



Bit Mask Meaning


4 0x10 Link enable









3. Type set sd:sd_io_time=0x78 <Enter>.

This setting prevents the host from issuing warning messages while non-disruptive operations are performed on Symmetrix.

Reconfigure theKernel

After installing the I/O driver, editing system parameters and the sd.conf file, you must reboot and rebuild the operating system kernel.

Type reboot -- -r <Enter> to reboot the host with the -r (reconfigure) option. When the system reboots, the Fibre Channel driver is loaded.

Format, Partition,Label

Use the format command to partition and label the new devices. The devices will appear under /dev/dsk and /dev/rdsk as standard SCSI devices.



The host will search for all disks, and will generate a display placing all unlabeled disks at the beginning of the listing.




5. When prompted to display a listing of the disks, type di <Enter>.

6. Repeat steps 2 through 5 for each remaining Symmetrix disks.

If you wish to use raw devices, there is no need to create filesystems for each device. Otherwise, create new filesystems for each device as described in the Symmetrix Open Systems Host Environment Guide.

Manage PhysicalVolumes and Create

Filesystems

Physical volumes can be managed under Solstice DiskSuite or Veritas Volume Manager in the same manner as devices accessed through a standard SCSI interface. Follow the instructions for volume manager functions and filesystem creation for Solaris devices in the Symmetrix Open Systems Environment Product Guide.


If upgrading an existing Symmetrix-to-host SCSI interface to Fibre Channel, see Migrating in Specific Host Environments on page B-5.


11

11-2


ConnectrixConfiguration

Guidelines

EMC Connectrix provides support for 32 ports F-port connections with the high-availability features. For further information about the Connectrix, refer to the EMC Connectrix Enterprise Storage System Topology Guide (part number 300-600-008).

The following paragraphs provide guidelines and limitations for using hubs in a Sun Solaris and Symmetrix Fibre Channel storage network.

Solaris Operating System

Solaris version 2.5.1, 2.6 required (with the latest Jumbo patch).

Connections

Connectrix provides capability to increase the storage capacity by connecting multiple Symmetrix FA ports to a single Fibre Channel HBA port on a single host. On the other hand, the Connectrix also provides capability to allow more hosts to share a Symmetrix FA port by connecting multiple Fibre Channel HBA port on multiple hosts.

Cascaded Connectrix

Not currently supported.

Multiple Host Systems

Up to six hosts can be connected to the switch for each SAF Connectrix, as long as there is some consideration for total I/O demand. Estimate each host’s I/O per second using a performance analysis tool such as VxSTAT, SAR, or Symmetrix Manager. Host nodes can be added to the switch within the suggested limit of a combined estimated 1000 IOPS (8KB block size).

Volume Sharing

Access to the same Symmetrix device through more than one host over Fibre Channel is supported with VERITAS VxVM version 2.4.1.

Cable Lengths

There are no restrictions on the mixing of Fibre Channel cable lengths on a switch. As long as each link does not exceed its allowed length (10 km), links of varying lengths can be mixed.

Software Support

Connectrix software support is provided the Connectrix Manager. Connectrix Manager is a Java-based GUI that can be invoked as local or remote management software. For more information, refer to the



Enterprise Fibre Channel Director Model ED-1032 User’s Guide (part number 300-600-004).

Diagnostics and Maintenance

Repair and system recovery from a Fibre Channel switch failure can be done on line with a properly configured high-availability system.


If upgrading an existing Symmetrix-to-host SCSI interface to Fibre Channel, see Migrating in Specific Host Environments on page B-5.


11

11-2


Dynamic Reconfiguration in the Ultra Enterprise 10000These HBAs are qualified to run Dynamic Reconfiguration in the Ultra Enterprise 10000:

• Jaycor FC-1063-EMC (Sbus, 32-bit)• Jaycor FC64-1063-EMC (Sbus, 64-bit)

These are the minimum requirements for the domain that will run Dynamic Reconfiguration:

• 512 MB minimum RAM in the total domain.

• dr-max-mem must be set to 4096 for both Solaris 2.5.1 and 2.6 operating systems. Refer to the Sun Ultra 10000 Dynamic Reconfiguration document on setting this parameter up in the OBP.

• System Service Processor version 3.1 with the following patches applied:

> 106190-06 SSP 3.1: bringup/obp_helper fixes

> 106241-05 SSP 3.1: snmpd/straps fixes

> 105873-08 SSP 3.1: hpost/redx/PCI fixes.

> 105684-07 SSP 3.1: OBP need to support PCI probing and DR PCI attach/detach

> 107498-01 SSP 3.1: autoconfig fixes

> 106019-03 SSP 3.1: scantool database and interconnect test fixes

> 105683-13 SSP 3.1: sigbcmd/cbe/flash_boot patch

> 106281-02 SSP 3.1: sys_id -m doesn't work in year 2000 or after(Y2K bug)

> 106282-05 SSP 3.1: hostview suppresses trap messages after 1999

> 106465-03 SSP 3.1: power command fixes

> 106617-01 SSP 3.1: cbs still leaks file descriptors

> 106543-01 SSP 3.1: tcl script error on "drain" from drview then "hang"

> 105682-04 SSP 3.1: libdr patch



> 106244-01 SSP 3.1: SSP libraries are not multi-thread safe

> 106206-01 SSP 3.1: In two-to-one mode "sys_clock" command reports CPU frequency

> 106195-01 SSP 3.1: VerExec - only checks the second character -

> 106201-01 SSP 3.1: bringup of domain A arbstopped domain B

These are the requirements for the the Jaycor FC-1063-EMC and FC64-1063-EMC HBAs:

• Firmware revision: 13.3.5. Contact your EMC field engineer for more information on upgrading to revision 13.3.5.

• Hardware revision:

> 32-bit HBA (FC-1063-EMC): Rev H> 64-bit HBA (FC64-1063-EMC): Rev C, D, or E

PowerPath version 1.5 is the version that has been tested with Solaris 2.5.1 and 2.6 to support Dynamic Reconfiguration.

To enable dynamic reconfiguration of the fca and fcaw, edit the file /etc/system and add the following lines:

set dr:detach_safe.list1 = "fcaw fca"set hswp: suspend_safe_list1 = "fcaw fca"

Refer to the release.txt file inside the CD-ROM for more information on dynamic reconfiguration.

Dynamic Reconfiguration in the Ultra Enterprise 10000 11-23

11

11-2



12

This chapter provides information specific to Windows NT hosts connecting to Symmetrix over Fibre Channel fabric. (Chapter 4 describes Windows NT support over arbitrated loop.)

• Windows NT Fibre Channel Environment...................................12-2• Host Connectivity ............................................................................12-3• Symmetrix Configuration ...............................................................12-5• Host Operating System Configuration .........................................12-6• Planning for Zoning and Connections..........................................12-7• Host Configuration with Qlogic HBA ..........................................12-9• Host Configuration with Emulex HBAs.....................................12-14


Windows NT Host onFabric

Windows NT Host on Fabric 12-1

12

12-2

Windows NT Host on Fabric

Windows NT Fibre Channel EnvironmentThis section lists some Symmetrix Fibre Channel support information specific to the arbitrated loop/Windows NT host environment.


Refer to Table 12-1 on page 12-3, and to Host Operating System Configuration on page 12-6.

Supported Hardware Symmetrix Fibre Channel supports up to eight Fibre Channel HBAs per host (depending on the number of available PCI slots). Refer to Table 12-1 on page 12-3 for supported HBAs.


Addressing Windows NT SCSI drivers and host adapter drivers use SCSI-2 device access protocol in addressing Fibre Channel devices. SCSI-3 Array Controller addressing modes are not supported. The peripheral device access mode is supported in Symmetrix to address up to 128 logical devices per port. Refer to Appendix C for the available addressing modes.


12Windows NT Host on Fabric

Host ConnectivityAs of the current revision of this manual, Symmetrix Fibre Channel is qualified for use with the Windows NT hosts shown in Table 12-1. Contact your EMC representative for the latest information on supported hosts and HBAs, as updates are frequent.


Table 12-1 HBAs for Windows NT Hosts

Host TypeMinimum OS Version a Host Bus Adapter

Firmware/BIOS Rev

Driver Version

Max LUNs

Compaq Proliant 5000, 5500, 6000, 6500, 7000


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

Dell PowerEdge 6100/6300 Windows NT 4.0 with SP 3, 4, or 5

Qlogic QLA2200F-EMC See note c See note c 128

Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

HP Netserver LH, LH3, LH4, LH-II, LXr, LXR Pro8, LXr8000


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

IBM Netfinity 5500, 5500M10, 5500M20, 7000/, 7000M10


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

Siemens PRIMERGY 7xx b, 8xx Windows NT 4.0 with SP 3, 4, or 5

Qlogic QLA2100F-EMC 1.37 6.16 128

Emulex LP7000E-EMC 2.20 1.22 128



12

12-4


a. SP stands for Service Pack.

b. Requires PRIMERGY firmware 1.07.887 version 4.05.

c. Contact your EMC representative.

Driver software for Windows NT hosts is provided with each HBA. Standard Windows NT driver installation procedures enable use of the HBAs.

The Fibre Channel Adapter driver functions as a device driver layer below the standard SCSI adapter driver; therefore, the Fibre Channel interface is transparent to the Windows NT disk administration system.

Siemens PRIMERGY 7xx, 8xx (continued)


Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

Unisys Aquanta QS/2V Windows NT 4.0 with SP 3, 4, or 5


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

NEC Express 5800/140 Ma Windows NT 4.0 with SP 3, 4, or 5


Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

NCR WorldMark 4300, 4380, 4400



Emulex LP7000E-EMC 2.20 1.22 128

Emulex LP8000-EMC 2.82 1.22 128

Emulex LP850-EMC 1.00 1.22 128

Table 12-1 HBAs for Windows NT Hosts (continued)

Host TypeMinimum OS Version a Host Bus Adapter

Firmware/BIOS Rev

Driver Version

Max LUNs





Table 12-2 Symmetrix Fabric Configuration for Windows NT Hosts

Parameter Setting



Hard Addressing (H-bit) Disabled

Loop ID not used




Disable Queue Reset on Unit Attention (D-bit) not used

Point-to-Point Mode (PP-bit) Enabled

Symmetrix Configuration 12-5

12

12-6


Host Operating System ConfigurationConnecting a Windows NT host to Symmetrix over Fibre Channel requires editing the Windows NT registry, as follows:

1. Run Winnt\system32\Regedt32.exe and display the device parameters under the following path.

2. Look for the TimeOutValue entry in the right pane of the registry editor window:

• If the TimeOutValue exists, double-click it, then go to step 3.

• If the TimeOutValue does not exist:

a. Select Add Value from the Edit menu.

b. In the Value Name box, type TimeOutValue (exactly as shown).

c. For the data type, select REG_DWORD from the pull-down menu.

d. Click OK, then go to step 3.

3. In the DWORD Editor window:

a. Click decimal in the radix box.

b. Change the value in the data box to 60.

4. Click OK.


6. Reboot the host.



Disk



Planning for Zoning and ConnectionsPlan for the switch topology, target to hosts mapping, and the zone. Draw the connectivity between the hosts, switch and the symmetrix for a verification of the the fabric configuration. After the user has decided on the desired connections, the user must configure the zone capability in the switch before proceeding. Refer to the EMC Connectrix Enterprise Storage Network System Topology Guide (part number 300-600-008) for information on the zone configuration.

Understanding Persistent Binding

Persistent binding is the mechanism to create a persistent logical route from a storage device object in the Windows NT host to a volume in the Symmetrix across the fabric. There are two methods of persistent binding available to a Windows NT HBA, and a third method if the HBA is one of the supported Emulex HBAs:

• EMC Volume Logix — Provides the persistent binding method through the centralized control by the Symmetrix Fibre Channel fabric ports. The information regarding to this method is available in the EMC Volume Logix Product Guide (part number 300-999-024)

• Switch zone mapping — Provides the persistent binding method through the centralized control by the switch. Refer to the EMC Connectrix Enterprise Storage Network System Topology Guide.

• (Emulex HBAs only) Emulex configuration tool manual mapping, provides the persistent binding method through the centralized control by the Emulex host adapter. This requires the user to modify the mapping manually.

EMC Volume Logix provides persistent binding in the granularity of the LUNs. On the other hand, the switch provides the persistent binding on the granularity of the HBA and Symmetrix ports. The least, the emulex provides the persistent binding on the granularity of the targets.

CAUTION!Before implementing persistent binding, be sure you understand the effects.

Planning for Zoning and Connections 12-7

12

12-8


What Happens Without Persistent Binding

Without a persistent binding mechanism, the host cannot maintain persistent logical routing of the communication from a storage device object across the fabric to a Symmetrix volume. If the physical configuration of the switch is changed (for example, the cable is swapped or the host is rebooted), the logical route becomes inconsistent, causing possible data corruption.

Figure 12-1 Recommended Connections Example

Host 3

Symmetrix

ED-1032

HBA 1

Host 2

Host 1

HBA 0

HBA 0

HBA 1

HBA 0

LUN15LUN16

LUN18LUN17

LUN19

LUN21LUN20

LUN22

LUN24LUN23

LUN0LUN1

LUN3LUN2

LUN4

LUN6LUN5

LUN7

LUN9LUN8

Table 12-3 Recommended Connections Example

Host HBA FA Target LUNs Zone

1 HBA 0 15a 0 0–3 0

15b 1 15–17

2 HBA 0 15a 0 4–6 0

HBA 1 15b 1 18, 20

3 HBA 0 15a 0 7–9 1

HBA 1 15b 1 19, 21–24



Host Configuration with Qlogic HBAThis section describes the procedures required to configure one or more Qlogic QLA2200F-EMC host bus adapters in a Windows NT host for connection to Symmetrix over Fibre Channel fabric. (Refer to Table 12-1 on page 12-3 for approved HBAs.)


Installing the HBA 1. With host system power removed, install the HBA. The card installs into a single PCI bus slot.

2. Install the cables from the host to the switch, and from the switch Symmetrix Fibre Channel ports.


EMC NVRAM Settings

EMC recommends configuring the Qlogic BIOS settings with the EMC-approved NVRAM settings file. This file contains all of the BIOS settings for the Qlogic adapters that have been tested and approved for connection to Symmetrix.

You can also change the Qlogic BIOS settings manually, but this can cause undesired results if set incorrectly. Refer to Configuring the HBA on page 12-10.

To set the Qlogic BIOS using the NVRAM file:

1. Format a 3.5-inch diskette and copy all files from the BIOS directory on the Qlogic CD-ROM to the diskette.

2. Reboot your Windows NT host system using a DOS diskette.

3. At the A:\> prompt, insert the diskette that contains the Qlogic BIOS files (created in step 1), and type QL2XUTIL.EXE /L /F <Enter>, to run the flash utility with the /L and /F parameters.

Do not attempt to run this procedure from a command prompt window.

4. When the procedure has finished, remove the diskette and reboot the host.


12

12-1


Configuring the HBA During system boot, a banner is displayed for each Qlogic adapter present in the system. Perform the following procedure to configure each Qlogic HBA.

This procedure applies to BIOS version 1.18 or higher.

CAUTION!Any time the default settings for the adapter are chosen via Fast!Util, the NVRAM settings specific to EMC are overwritten, and the above procedure must be repeated. EMC recommends that you do not select the default adapter settings option from Fast!Util.

1. Press <Alt><Q> when prompted Press <ALt-Q> for

Fast!UTIL.


• If there is only one Qlogic HBA, a Fast! UTIL Options menu will be displayed.

• If there are multiple Qlogic HBAs, a list of addresses occupied by those HBAs will be displayed. Using the arrow keys, select the desired HBA and press <Enter>. The Fast!UTIL Options menu will then be displayed.



5. Use the arrow keys to select Host Adapter Bios and press <Enter> to change the setting to Disabled.

6. If performance is a concern, use the arrow keys to select Frame Size and press <Enter> to change the setting. Use the arrow keys again to select the desired frame size, then press <Enter>.

7. Use the arrow keys to select Adapter Hard Loop ID and press <Enter> to change the setting to Disabled.




9. Select Selectable Boot Settings from the Configuration Settings menu. Make sure Selectable Boot Device is Disabled. If it is not, press <Enter> to change the setting.


11. Select Advanced Adapter Settings from the Configuration Settings menu.

12. If the HBA’s BIOS is version 1.32 or higher, go to step 13. If the BIOS is a lower version, press <Alt><Q> at the Advanced Adapter Settings menu to enter edit mode.

13. Use the arrow keys to select LUNs per Target. Press <Enter> and use the arrow keys to select the number of LUNs you will be accessing, then press <Enter> again.

The current Symmetrix/Qlogic Fibre Channel implementation supports a maximum of 128 LUNs.

14. Select Enable LIP Full Login and press <Enter> to change the setting to Yes.

15. Select Enable Target Reset and press <Enter> to change the setting to Yes.

16. If performance is a concern, select Execution Throttle and press <Enter> to change the setting. Enter a numeric value up to 256 in the red box under New.


18. Press <Esc> to return to the Fast! UTIL Options menu.



21. Press <Esc> to exit Fast!UTIL.



12

12-1



To use Symmetrix disks with a Windows NT host, you need a Fibre Channel host adapter driver. The adapter kit includes an EMC-approved driver, which must be installed and configured prior to partitioning the Symmetrix disks.

Where to Find theDriver

The driver for Qlogic HBAs on Windows NT hosts is located in the \NT directory on the Qlogic CD-ROM that accompanied the Fibre Channel HBA.

You can find driver updates on the Qlogic website, www.qlc.com.

1. From the main page, click on the Adapter drivers & utilities download box.

2. On the Host Adapter Drivers & Utilities page, click on the adapter type you want to download.

3. Scroll down the displayed list and click on EMC Approved Drivers.

4. On the list of EMC drivers, click on Windows NT Driver.

5. Download the driver.

Installation Procedure To install the driver, follow these steps:




4. Click on the Add button to display the SCSI Adapter Drivers database.


6. Locate the disk with the OEMSETUP.INF file for the Qlogic driver and click OK.

7. Select Qlogic QLA2200 PCI Fibre Channel Adapter.



Qlogic QLA2200 PCI-Fibre Channel Adapter (Started)





Once the Symmetrix has devices assigned with device addresses and the directors have been switched on line, the host can see all the target Symmetrix devices assigned to that host interface. Devices are presented to the host in the same manner as devices accessed through a standard SCSI interface. Follow the instructions for configuring and partitioning Symmetrix devices under Windows NT Environment in the Symmetrix Open Systems Environment Product Guide.








12

12-1


Host Configuration with Emulex HBAsThis section describes the procedures required to configure one or more Emulex host bus adapters in a Windows NT host for connection to Symmetrix over Fibre Channel fabric. (Refer to Table 12-1 on page 12-3 for approved HBAs.) The Emulex LP7000E-EMC, LP8000-EMC, and LP850-EMC all use the same driver in the Windows NT environment. The procedures described in this section apply to all three HBA types.


Installing the HBA 1. Set the jumpers on an LP7000E-EMC or LP8000-EMC as shown in Figure 12-2 to enable it for use with Windows NT. The LP850-EMC has no user-configurable jumpers.

Figure 12-2 LP7000E-EMC and LP8000-EMC Jumpers

Note that JX1 and JX2 are in opposite locations on the two HBA types.

2. With host system power removed, install the HBA. The card installs into a single PCI bus slot.

3. Install the cables from the host to the switch, and from the switch to Symmetrix Fibre Channel ports.


1 321 32

JX1JX2

1 32 1 32

JX1 JX2 LP8000-EMC

LP7000E-EMC



Updating the Flash Firmware/BIOS

Each Emulex Fibre Channel controller has a flash upgradable firmware and BIOS. In most instances, it is necessary to keep only the firmware up to date, since the BIOS is applied only when using connected storage as a boot device.

The CD-ROM contains the EMC-approved firmware files at the time of this document’s release. Updated firmware, if available, can be found on the Emulex web site:

http://www.emulex.com/ts/fc/index.htm

From this site, select the adapter onto which you are installing the firmware, then download the correct firmware file. The firmware is typically a .ZIP file, and must be extracted to another location. Extract the downloaded file to a diskette and follow the upgrade procedure below.

Upgrade Procedure The following procedure is used to upgrade the flash firmware for the Emulex LP7000E-EMC, LP8000-EMC, and LP850-EMC.

1. Boot the computer using a DOS/WIN95/WIN98 bootable diskette.

2. Insert the diskette containing the flash utility (LP6DUTIL.EXE).

3. At the A:\> prompt, type lp6dutil <Enter> to start the utility.

The utility performs diagnostic tests on the installed adapter(s). You may be required to press <Enter> after each test so the program can move on the to the next. Once the diagnostics are complete, the Main Menu appears.

4. Type 5 to select Maintenance, and press <Enter>.

5. Type 1 to select Upgrade Firmware, and press <Enter>.

6. Enter the range of adapters to flash; for example: 1–4 (for four adapters).

7. Enter the Firmware Image filename, including the path. The firmware image file should be on the same disk as the LP6DUTIL.EXE program file.

8. When prompted, enter 1 to proceed with the upgrade for the first controller.

9. When prompted, enter 1 to reset the adapter after loading is complete.


12

12-1


10. Repeat steps 8 and 9 for each adapter in the range entered in step 6.

11. When all adapters have been loaded, enter 0 at the Maintence menu to return to the Main Menu.

12. Enter 7 from the Main Menu to exit the flash utility.



Obtain the LatestDriver

The CD-ROM that accompanies the adapter kit contains the latest EMC-approved driver as of the creation date of the CD-ROM. Drivers are occasionally updated, however, so contact your EMC representative to confirm the latest driver version.

• If the CD-ROM contains the latest driver version, follow the procedure under Install the Driver later on this page.

• If a newer driver is available, download it from the Emulex website, as described in the following procedure.

To download the driver:

1. Access this file: http://www.emulex.com/ts/fc/index.htm

2. Click on the adapter you are installing:

• LP7000E-EMC• LP8000-EMC• LP850-EMC

3. Extract the downloaded file to an IBM-formatted 3.5-inch diskette, or to the hard disk on the Windows NT host.

Install the Driver To install the driver, follow these steps:

Refer to release notes provided with the driver for information that might be unique to new driver revisions.

1. Boot the host (if necessary) with Windows NT 4.0.







6. Locate the disk/directory with the OEMSETUP.INF file for the Emulex driver and click OK.

7. Select Emulex LightPulse, Point-to-Point, Automap SCSI Devices.



Emulex LightPulse, Switch Fabric, Automap SCSI Devices (Started)


10. Edit the c:\boot.ini file and add the /PCILOCK switch to the boot entry. Below is an example of the updated entry:

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Server Version 4.00" /pcilock


Changing the Registry

EMC requires a change to the Windows NT registry if using Emulex Fibre Channel controllers. The OEMCode value with the Emulex registry key must be set to the correct value.

1. Click Start, then Run.

2. In the Open box, type REGEDT32.EXE and click OK.

3. Follow this path to the Emulex registry key:

4. In the right pane of the registry editor, double-click the OEM Code variable.



Elxsli2


12

12-1


5. In the DWORD Editor windows, change the value in the data box to 1 and click OK.


Using the Emulex Configuration Tool

Before using the configuration tool, follow the procedure under Changing the Registry on page 12-17.

Once the Emulex driver has been installed, a new icon appears under Start -> Programs. This shortcut points to the Emulex Configuration Tool, which is a small graphical user interface (GUI) that allows the user to make setup changes to installed Emulex adapters. This tool is not necessary for most installations, and can cause errors and/or poor performance if used incorrectly.

1. Start the Emulex Configuration Tool by selecting Start -> Programs -> Emulex Configuration Tool.

2. A window similar to Figure 12-3 on page 12-18 appears, displaying the available adapters in the upper left corner. Click on the adapter you wish to modify. (This activates all items that can be altered for that adapter.)

Figure 12-3 Emulex Configuration Tools and Settings for Fabric



You can enable or disable the various Adapter Controls by checking or "unchecking" the associated boxes, and you can change the parameter values in the small windows across the bottom by clicking on a window and typing in the desired value. However, EMC recommends changing only the Maximum Number of LUNs, from the default of 32 to 128. For reference, Table 12-4 lists the recommended settings.

a. For host systems running EMC PowerPath, Wait Ready Timer must be 10 seconds.

3. Once all changes have been made to a selected adapter, click the Apply button in the lower left corner to save changes for that adapter.

4. Repeat steps 1 through 3 for any other adapters you want to change.

Table 12-4 Emulex Configuration Tool Settings for Fabric

Adapter Controls

Automatically Map SCSI Devices Enabled (checked)

Point to Point Enabled (checked)

Allow Multiple paths to SCSI Targets Enabled (checked)

Register for State Change Enabled (checked)

Use Name Server after RSCN Enabled (checked)

Use PLOGI instead of PDISC after LIP Enabled (checked)

All other Adapter Controls Disabled (unchecked)

Other Parameters

Maximum Number of LUNs 128

Maximum Queue Depth 8

Wait Ready Timer 60 sec (or 10 sec a)

E_D_TOV 1000 ms

R_A_TOV 100 sec

AL_TOV 15 ms

ARB_TOV 1000 ms


12

12-2


5. When all changes are complete, reboot the host.


Once the Symmetrix has devices assigned with device addresses and the directors have been switched on line, the host can see all the target Symmetrix devices assigned to that host interface. Devices are presented to the host in the same manner as devices accessed through a standard SCSI interface. Follow the instructions for configuring and partitioning Symmetrix devices under Windows NT Environment in the Symmetrix Open Systems Environment Product Guide.








PART 4

The contents of Part 4 are:

• Appendix A, Specifications

• Appendix B, Migrating from SCSI to Fibre Channel

• Appendix C, Addressing Symmetrix Devices

• Glossary

• Sales and Service Locations

• Index

Appendixes andBack Matter

A

This appendix contains various specifications related to the Symmetrix Fibre Channel implementation.

Fibre ChannelStandards

Table A-1 lists some approved Fibre Channel standards. Copies of these and other ANSI standards are available from Global Engineering, 15 Inverness Way East, Englewood, CO 80112-5704. (This is the address at the time of printing of this manual.)

Appendi x ASpecifications

Table A-1 ANSI Fibre Channel Standards

ANSI Standard Title

X3.230-1994 Fibre Channel Physical and Signalling Interface (FC-PH)

X3.230:AMI-1996 Fibre Channel Physical and Signalling Interface (FC-PH) Errata

X3.254-1994 Fibre Channel HiPPI Framing Protocol (FC-FP)

X3.269-199x Fibre Channel Protocol for SCSI (FCP)

X3.271-1996 Fibre Channel Single-Byte Command Code Sets (FC-SB)

X3.272-1996 Fibre Channel Arbitrated Loop (FC-AL)

X3.297-1997 Fibre Channel Physical and Signalling Interface-2 (FC-PH-2)

X3.287-1996 Fibre Channel Link Encapsulation (FC-LE)

X3.288-1996 Fibre Channel Generic Services (FC-GS)

X3.289-1996 Fibre Channel Fabric Generic (FC-FG)

Specifications A-1

A

A-2

Specifications

Data Transfer Rate The maximum effective data rate as defined by the Fibre Channel specification (ANSI X3.269-199x) is 100 Mbyte/second. The defined standard rate of 1062.5 megabaud includes sufficient bandwidth to cover data with 8B/10B encoding and framing protocol overhead.

Connectivity/Topology

• Switched fabric (FC-SW) and arbitrated loop (FC-AL).

• 5 to 500 meters between ports.

• Two ports per Symmetrix Fibre Channel Director.

Arbitrated LoopAddressing

Physical addressing (AL_PA) Loop ID 0 through 126 mapped to AL_PA 00 through EF in accordance with FC-AL Annex K.

Addressing options:

• Soft Assign — Acquire during Loop Initialization.

• Hard Assign — Configure in Symmetrix Service Processor. Required for HP interface.

Interface Mapping SCSI-3 command set mapping (SCSI-3 FCP).

Queue Tags • Simple queuing — Reorder commands to optimize performance

• Ordered queuing

• Head of queue

Fiber OpticTransceiver

• Optics module — Shortwave laser

• Optics data rate — 1062.5 Mbits per second

• Wavelength — 780 nm

• Open Fiber Control not implemented (Non-OFC)

Cables • 50/125-µm Multimode Fiber (62.5/125-µm cable supported, but not supplied by EMC)

• 5, 10, 30, 50, 100-meter cables currently available from EMC

• 101 to 500 meter cable available form AMP, Inc.

• SC Duplex Connectors

Microcode • FC-AL requires microcode level 5264 or above

• FC-SW requires microcode level 5265 or above


B

This appendix describes the procedures used to migrate the configuration when a Symmetrix SCSI Director is replaced with a Fibre Channel Director.

• Introduction ....................................................................................... B-2• Running Inquiry................................................................................ B-3• Migrating in Specific Host Environments ..................................... B-5• EMC Migration Scripts..................................................................... B-8

Migrating from SCSI toFibre Channel

Migrating from SCSI to Fibre Channel B-1

B

B-2

Migrating from SCSI to Fibre Channel

IntroductionA Symmetrix SCSI Director has four ports, and a Fibre Channel Director has two. When replacing a SCSI Director with a Fibre Channel Director, you must follow certain procedures to assure that the hosts will know which devices are connected to which Symmetrix ports after the replacement. This appendix describes the procedures for migrating to the new configuration.

For Windows NT hosts, there is no need to migrate the configuration, since Windows NT maintains disk identity through disk "signatures."

For all other supported hosts, EMC provides a utility that automates much of the migration process.

The migration procedure can be summarized as follows:

1. Run the Symmetrix Inquiry utility (inq) to identify the configuration before changing the hardware.

2. Perform any host-specific operations for the following host types:

• Sun Veritas VxVM Environment on page B-5• Sun Solstice DiskSuite Environment on page B-5• HP LVM Environment on page B-6

3. Run the appropriate EMC script:

• Sun, SGI Challenge, AIX hosts: emc_s2f on page B-8• HP hosts: emc_s2f_hp on page B-10• Windows NT hosts: not applicable

Each script must be run before and after changing the hardware, as described in the appropriate sections. Run the "before" section as described.

4. Change the hardware.

5. Run the "after" parts of the appropriate EMC script (emc_s2f, emc_s2f_hp, then the host-specific steps (if applicable).


BMigrating from SCSI to Fibre Channel

Running InquiryYou must identify the Symmetrix devices before making the hardware change. To do this on a Sun, SGI Challenge, AIX, or Siemens host, run the Inquiry utility (inq). This displays information you can use to determine which Symmetrix volume is associated with a particular device as seen by the host.

The Inquiry utility will not work on HP devices with the NIO driver. This driver does not accept the SCSI passthrough commands that are needed by Inquiry. If you are going to run the emc_s2f utility (see emc_s2f on page B-8) under these circumstances, be sure to create pseudo devices.

An executable copy of the inq command for each of the supported hosts can be found on EMC’s anonymous FTP server, ftp.emc.com, in the /pub/sym3000/inquiry directory. Each file has a host-specific suffix (for example, inq.AIX). (Refer to Connecting to EMC’s FTP Server on page B-4.)

Figure B-1 shows a sample output of inq when run from the host console.

Figure B-1 Sample Inquiry Display

The output fields are as follows:

• DEVICE = UNIX device name (full pathname) for the SCSI device• VEND = Vendor Information• PROD = Product Name• REV = Revision number — for a Symmetrix, this will be the

microcode version

Inquiry utility, Version 4.91Copyright (C) by EMC Corporation, all rights reserved.------------------------------------------------------------DEVICE :VEND :PROD :REV :SER NUM :CAP :BLKSZ-----------------------------------------------------------/dev/rdsk/c0t2d0s2 :SEAGATE :ST34371W SUN4.2G:7462 :9719D318 :4192560 :512/dev/rdsk/c0t3d0s2 :SEAGATE :ST34371W SUN4.2G:7462 :9719E906 :4192560 :512/dev/rdsk/c10t0d0s2 :EMC :SYMMETRIX :5264 :14000280 :224576 :512/dev/rdsk/c10t0d1s2 :EMC :SYMMETRIX :5264 :14001280 :224576 :512/dev/rdsk/c10t0d2s2 :EMC :SYMMETRIX :5264 :14002280 :224576 :512/dev/rdsk/c10t0d3s2 :EMC :SYMMETRIX :5264 :14003280 :224576 :512/dev/rdsk/c10t0d4s2 :EMC :SYMMETRIX :5264 :14004280 :224576 :512/dev/rdsk/c10t0d5s2 :EMC :SYMMETRIX :5264 :14005280 :224576 :512

Running Inquiry B-3

B

B-4


• SER NUM = Serial number, in the format SSVVVDDP, where:> SS = last two digits of the Symmetrix serial number> VVV = Logical Volume number> DD = Channel Director number> P = port on the channel director

• CAP = Size of the device in kilobytes• BLKSZ = Size in bytes of each block

Connecting to EMC’s FTP Server

Perform the following steps to connect to EMC’s anonymous FTP server:

1. At the host, log in as root and create the directory /usr/ftp_emc by typing mkdir /usr/ftp_emc.

2. Type cd /usr/ftp_emc <Enter>, to change to the new directory.

3. Type ftp ftp.emc.com <Enter>, to connect to the FTP server:

4. At the FTP server login prompt, log in as anonymous

5. At the password prompt, type your e-mail address.

You are now connected to the FTP server. To display a listing of FTP commands, type help <Enter> at the prompt.



Migrating in Specific Host Environments

Sun Veritas VxVM Environment

Sliced Volumes with Veritas Slice Tags will automatically be “rediscovered” at reboot. Simple Volumes (Veritas on s2) will not.

1. Type umount -a <Enter>, to unmount all file systems.

2. Stop all volumes and “deport” the volume group:

a. Type vxvol -g (DiskGroup) stopall <Enter>.

b. Type vxdg deport (DiskGroup) <Enter>.

3. Run the EMC migration script. (See emc_s2f on page B-8.) As described in that procedure, make the hardware changes at the appropriate time.

4. Import and recover the Disk Group:

a. Type vxdg import (DiskGroup) <Enter>.

b. Type vxrecover -g (DiskGroup) <Enter>.

Sun Solstice DiskSuite Environment

1. Type copy /etc/opt/SUNWmd/md.tab <Enter>, to back up the current DiskSuite configuration.

2. Record the output from metastat and metadb -I.

3. Make sure all ‘sd’ device links are recorded in md.tab. If they are not, add them and reboot.

4. Type umount -a <Enter>, to unmount all file systems.

5. Replace each replica currently configured per device:

a. Type metadb -d -f device <Enter>.

b. Type metadb -a -f -c x new_device <Enter>.

6. Edit /etc/opt/SUNWmd/md.tab, replacing each old device with its corresponding new device link.

7. Use metaclear to delete all volumes except the boot volume.

8. Use metainit to recreate all meta-devices.

Migrating in Specific Host Environments B-5

B

B-6


HP LVM Environment If you can remove PV/Links from the equation, it will make the migration significantly easier.

1. Type vgcfgbackup <Enter>, to back up the existing LVM configuration:

2. Modify the /etc/lvmrc file to disable Automatic Volume Group Activation.

3. As a safety measure, you can create mapfiles containing the vgid of the existing volume groups. To do so, type vgexport -p -s -m mapfile vg_name <Enter>.

4. Move the etc/lvmtab file to a backup file; for example, old.lvmtab.

Moving ‘rootvg’ on HPLVM

When reducing the number of channels, you should first move rootvg to the remaining channels so that it does not fail VG quorum check on reboot.

CAUTION!rootvg must be SCSI.

1. Identify the rootvg volumes.

2. Remap those volumes to the remaining SCSI channels on the Symmetrix.

3. Create a PV/Links association for each volume to the new channel using vgextend.

4. Remove the old mapping of the device from PV/Links using vgreduce.

SGI Challenge Environment

When xlv_assemble is called from the xlv_make command, it writes a unique signature on the volumes that make up the volume groups. The xlv_assemble command generates volume groups based on the signature.

1. Back up the volumes that will be migrated to Fibre Channel.

2. In Auto Install, map the desired devices to the appropriate Fibre Channel director. Be sure to use the correct naming convention for Fibre Channel devices.



3. Modify the /etc/config/fsd.options file to include the correct information for that device. Refer to Modifying Configuration Files on page 5-6.

4. Reboot the system.

After the machine is rebooted, the devices can be accessed via the Fibre Channel interface.

Migrating in Specific Host Environments B-7

B

B-8


EMC Migration Scripts

emc_s2f This utility is used for most SCSI-to-Fibre Channel migration situations. An EMC shell script provides snapshots of the configuration before and after the director is replaced, so you can see where devices were reassigned.

If using volume groups and/or PV Links on an HP host, use emc_s2f_hp on page B-10.)

Usage The syntax of the utility is:

emc_s2f <option> [-fp] [-all]

where:

CAUTION!If the operating system’s device name is not uniquely identified by its basename, you must use the -fp flag.

Limitations Note the following limitations of emc_s2f:

• The comparison will not be accurate if the host is connected to multiple Symmetrix devices and the last two digits in the serial number of one Symmetrix are the same as the last two digits of the serial number of another Symmetrix.

• If multiple paths exist to the host before and after the migration, the "before" and "after" groups of devices will be displayed, but there will be no way to tell how the devices match each other.

option: -b Specify when running emc_s2f before converting to Fibre Channel.

-a Specify when running emc_s2f after converting to Fibre Channel.

-c Specify to compare the "before" and "after" configurations.

-fp Shows the full path of each device name.

-all (valid only if <option> is -c) Displays all information even if there is no change.



• The Inquiry utility will not work on HP devices with the NIO driver. This driver does not accept the SCSI passthrough commands that are needed by Inquiry. Before running emc_s2f under these circumstances, be sure to create pseudo devices.

Procedure 1. Unmount the filesystems.

2. Type emc_s2f -b <Enter>, to take a snapshot of the configuration before you change the hardware. The information is displayed, and written to a file named emc_s2f.b.

3. Replace the necessary hardware, then bring the Symmetrix back on line.

4. Type emc_s2f -b <Enter>, to take a snapshot of the new hardware configuration. The information is displayed, and written to a file named emc_s2f.a.

5. Type emc_s2f -c <Enter>, to compare the two files. The information is displayed, and written to a file named emc_s2f.c.

Here is a sample output, from a Symmetrix with a serial number ending in 65:

The explanation is:

• Before, dev #002 was seen through two ports; after, it is seen through two different ports.

• Before, dev #040 was seen as c9t3d0; after, the device is not visible to the host.

• Before, dev #047 was seen as c9t3d7; after, it is seen as c4t3d7.

• Before, dev #048 was seen as c9t4d0; after, there is no change. (This is shown only if the -all flag was used.)

65 002 B c8t0d2 c9t8d2

A c1t0d2 c4t8d2

65 040 B c9t3d0

A not_found

65 047 B c9t3d7

A c4t3d7

65 048 B c9t4d0

A no_change

EMC Migration Scripts B-9

B

B-10


emc_s2f_hp This utility is a special version of emc_s2f that handles volume groups, PV Links, pseudo devices, and NIO drivers in an HP host environment.

CAUTION!This script depends on another script, vgnode.ksh, that is shipped in the same distribution package as emc_s2f_hp. Verify that vgnode.ksh is present.

Usage The syntax of the utility is:

emc_s2f_hp <option>

where option can be:

-b Specify when running emc_s2f_hp before converting to Fibre Channel.

-e Build a script to automate vgexport.

-a Specify when running emc_s2f_hp after converting to Fibre Channel.

-c Specify to compare the "before" and "after" configurations to plan vgimport.

-i Build a script to automate vgimport.

Limitations Note the following limitations of emc_s2f_hp:

• The comparison will not be accurate if the host is connected to multiple Symmetrix devices and the last two digits in the serial number of one Symmetrix are the same as the last two digits of the serial number of another Symmetrix.

• If multiple paths exist to the host before and after the migration, the "before" and "after" groups of devices will be displayed, but there will be no way to tell how the devices match each other.

• The Inquiry utility does not work on HP devices with the NIO driver, because the driver does not accept the SCSI passthrough commands needed by Inquiry. Before running emc_s2f_hp under these circumstances, you must create pseudo devices.



• HP does not allow an export of the root volume group. If the group is on devices that will be affected by the migration, you must remove any mention of the group from the import/export scripts that emc_s2f_hp creates.

• emc_s2f_hp does not work correctly if you map some of a SCSI port’s devices to one Fibre Channel port and the rest to a different Fibre Channel port. All of the devices on a SCSI port must be mapped to a single Fibre Channel port. (If you need to map a SCSI port’s devices to multiple Fibre Channel ports, use emc_s2f.

Procedure 1. Unmount the filesystems.

2. Type emc_s2f_hp -b <Enter>, to take a snapshot of the configuration before you change the hardware. The information is displayed, and written to a file named emc_s2f_hp.b.

3. Type emc_s2f_hp -e <Enter>, to create a shell script that will export all of the volume groups.

It is the user’s responsibility to review the script to ensure it is exporting the correct volume groups.

4. Run the export script created in step 3.

5. Replace the necessary hardware, then bring the Symmetrix back on line. Make a note of how the SCSI ports are mapped to the Fibre Channel ports.

6. Create a text file named emc_s2f_hp.ref, which should contain director and port assignments before and after the hardware change(s). For example, if devices originally accessed through SA 15a-a and 15a-b are now accessed through 16b-a, the text of emc_s2f_hp.ref should be:

15a-a:16b-a15a-b:16b-a

CAUTION!This file assumes an n:1 mapping of SCSI ports to Fibre Channel ports. The emc_s2f_hp script will not work correctly if you map some of a SCSI port’s devices to one Fibre Channel port and the rest to a different Fibre Channel port.

7. Type emc_s2f_hp -a <Enter>, to take a snapshot of the new hardware configuration. The information is displayed, and written to a file named emc_s2f_hp.a.

EMC Migration Scripts B-11

B

B-12


8. Type emc_s2f_hp -c <Enter>, to compare the two files. The information is displayed, and written to a file named emc_s2f_hp.c.

Check the "compare" file for missing information. If any device is missing an old or new device name, or xx is displayed instead of a device name, it means that emc_s2f_hp could not gather all the necessary information. Make sure all the devices are ready and available to the host, then rerun emc_s2f_hp.

Here is a sample output, from a Symmetrix with a serial number ending in 65:

The explanation is:

• Before, two "old" devices were seen as c2t5d6 and c2t5d7. They were not part of a volume group. The devices are now named c9t1d6 and c9t1d7 respectively.

• Volume group vg04 used to have two primary paths, c6t3d4 and c6t3d5, with alternate links c2t6d0 and c2t6d1. After the migration, the new primary paths are c6t3d4 and c6t3d5, with alternates c9t2d0 and c9t2d1. The Import script created by s2f_hp -i will pass this information on to the vgimport command, which will be able to sort everything out and bring back the volume groups.

9. Type emc_s2f_hp -i <Enter>, to create a shell script that will import all of the volume groups, with the new names, in the correct order, preserving the primary/alternate relationships.

It is the user’s responsibility to review the script to ensure it is importing the volume groups correctly.

NEW=c9t1d6 OLD=c2t5d6 VG=N/A (NO-VG)

NEW=c9t1d7 OLD=c2t5d7 VG=N/A (NO-VG)

NEW=c6t3d4 OLD=c6t3d4 VG=/dev/vg04 (PRIMARY)

NEW=c6t3d5 OLD=c6t3d5 VG=/dev/vg0 (PRIMARY)

NEW=c9t2d0 OLD=c2t6d0 VG=/dev/vg04 (ALTERNATE)

NEW=c9t2d1 OLD=c2t6d1 VG=/dev/vg04 (ALTERNATE)


C

This appendix describes the methods of addressing Symmetrix devices on arbitrated loops or fabrics:

• Arbitrated Loop Addressing ...........................................................C-2• Fabric Addressing ............................................................................. C-4• SCSI-3 FCP Addressing.................................................................... C-5

Appendi x CAddressing SymmetrixDevices

Addressing Symmetrix Devices C-1

C

C-2

Addressing Symmetrix Devices

Arbitrated Loop AddressingThe Fibre Channel arbitrated loop (FC-AL) topology defines a method of addressing ports, arbitrating for use of the loop, and establishing a connection between Fibre Channel NL_Ports (level FC-2) on HBAs in the host and Fibre Channel Directors (via their adapter cards) in Symmetrix. Once loop communications are established between the two NL_Ports, device addressing proceeds in accordance with the SCSI-3 Fibre Channel Protocol (SCSI-3 FCP, level FC-4).

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

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

Symmetrix Fibre Channel Director parameter settings, shown in Table C-1, control how Symmetrix responds to the Loop Initialization Process.


CAddressing Symmetrix Devices

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

A host initiating I/O with Symmetrix uses the AL_PA to request an open loop between itself and the Symmetrix port. Once the arbitration process has established a logical connection between Symmetrix and the host, addressing specific logical devices is done through the SCSI-3 FCP.

Table C-1 FC-AL Addressing Parameters

Parameter Bit Description Default

Disk Array A If enabled, the Fibre Channel Director presents the port as a disk array. See Table C-2 on page C-6 for settings for each addressing mode.

Enabled

Volume Set V If enabled and Disk Array is enabled, Volume Set Addressing mode is enabled. See Table C-2 for settings for each addressing mode.

Enabled

Use Hard Addressing

H If enabled, entering an address (00 through 7D) in the Loop ID field causes the port to attempt to get the AL_PA designated by the Loop ID. If the port does not acquire the AL_PA, Symmetrix reacts based on the state of the non-participating (NP) bit. If the NP bit is set, the port switches to non-participating mode and is not assigned an address. If non-participating mode is not selected, or if the H-bit was not set, the Symmetrix port accepts the new address that is soft-assigned by the host port.

Enabled

Hard Addressing Non-participating

NP If enabled and the H-bit is set, the director uses only the hard address. If it cannot get this address, it re-initializes and changes its state to non-participating. If the NP-bit is not set, the director accepts the soft-assigned address.

Disabled

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

00

Third-party Logout Across the Port

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

Disabled

Arbitrated Loop Addressing C-3

C

C-4


Fabric AddressingEach port on a device attached to a fabric is assigned a unique 64-bit identifier called a Worldwide Port Name (WWPN). These names are factory-set on the HBAs in the hosts, and are generated on the Fibre Channel Directors in the Symmetrix.

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

Note: The ANSI standard also defines a Worldwide Node Name (WWNN), but this name has not been consistently defined by the industry.

When an N_Port (host server or storage device) connects to the fabric, a login process occurs between the N_Port and the F_port on the fabric switch. During this process, the devices agree on such operating parameters as class of service, flow control rules, and fabric addressing. The N_Port’s fabric address is assigned by the switch and sent to the N_Port. This value becomes the Source ID (SID) on the N_Port's outbound frames and the Destination ID (DID) on the N_Port's inbound frames.

The physical address is a pair of numbers that identify the switch and port, in the format s,p, where s is a domain ID and p is a value associated to a physical port in the domain. The physical address of the N_Port can change when a link is moved from one switch port to another switch port. The WWPN of the N_Port, however, does not change. A Name Server in the switch maintains a table of all logged-in devices, so N_Ports can automatically adjust to changes in the fabric address by keying off the WWPN.

The highest level of login that occurs is the process login. This is used to establish connectivity between the upper-level protocols on the nodes. An example is the login process that occurs at the SCSI FCP level between the HBA and the Symmetrix.


CAddressing Symmetrix Devices

SCSI-3 FCP AddressingThe Symmetrix director extracts the SCSI Command Descriptor Blocks (CDB) from the frames received through the Fibre Channel link. Standard SCSI-3 protocol is used to determine the addressing mode and to address specific devices.

Symmetrix supports three addressing methods based on a single-layer hierarchy as defined by the SCSI-3 Controller Commands (SCC).

• Peripheral Device Addressing• Logical Unit Addressing• Volume Set Addressing

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

For Logical Unit and Volume Set addressing, the Symmetrix port will identify itself as an Array Controller in response to a host’s Inquiry command sent to LUN 00. This identification is done by returning the byte 0x0C in the Peripheral Device Type field of the returned data for Inquiry. If Symmetrix returns the byte 0x00 in the first byte of the returned data for Inquiry, Symmetrix is identified as a Direct Access device.

Upon identifying the Symmetrix as an Array Controller device, the host should issue a SCSI-3 Report LUNS command (0xA0), in order to discover the LUNS.

The three addressing modes, contrasted in Table C-2, differ in the addressing scheme (Target ID, LUN and Virtual Bus) and number of addressable devices.

SCSI-3 FCP Addressing C-5

C

C-6


a. Bits 7-6 of byte 0 of the address.

b. The actual number of supported devices may be limited by the type host or host bus adapter used.

Note: The addressing modes are provided to allow flexibility in interfacing with various hosts. In all three cases the received address is converted to the internal Symmetrix addressing structure. Volume Set addressing (used by HP 9000 hosts) is the default for Symmetrix. Choose the addressing mode that is appropriate to your host.

Table C-2 Symmetrix SCSI-3 Addressing Modes

Addressing Mode Codea

“A” Bit

“V” Bit

Response to “Inquiry”

LUNDiscovery Method

Possible Addresses

Maximum Logical Devicesb

Peripheral Device

00 0 X 0x00Direct Access

Access LUNs directly

16,384 256

Logical Unit 10 1 0 0x0CArray Controller

Host issues “Report LUNS” command

2,048 128

Volume Set 01 1 1 0x0CArray Controller

Host issues “Report LUNS” command

16,384 512


Glossary

This glossary contains terms related to Fibre Channel. Many of these terms are used in this manual.

8B/10B Coding A method of encoding each 8-bit byte of data by adding two bits of special code that minimizes transmission errors. (Each 10-bit character is called a Transmission Character.) The data is decoded back to the original 8-bit bytes at the destination. In Fibre Channel, all information is transmitted using 8B/10B coding.

AAdapter A card that provides the physical interface between the Symmetrix

director and disk devices.

AL_PA See Arbitrated Loop Physical Address.

Arbitrated Loop A Fibre Channel topology structured as a loop and requiring a port to successfully negotiate to establish a circuit between itself and another port on the loop.

Arbitrated LoopPhysical Address

AL_PA, a one-byte value used to identify a port in an arbitrated loop topology. Symmetrix AL_PA may be set by entering a Loop Identifier to designate a specific physical address. The value of the AL_PA corresponds to bits 7 to 0 of the 24-bit Native Address Identifier in the frame header. Also see Loop_ID.

Arbitration WaitTimeout Value

The minimum time that an L_Port waits while arbitrating before originating a loop initialization.

Glossary g-1

g-2

Glossary

BBasic Link Services Single-frame messages that handle high-priority disruptive

operations; e.g., ABTS – Abort Sequence.

CClose A protocol used to terminate an arbitrated loop circuit.

EError Detect Timeout

ValueThe minimum time that an L_Port waits for Sequence completion before initiating recovery.

ESCON The fiber optic derivative of the IBM Original Equipment Manufacturer’s Interface (OEMI).

Exchange One or more non-concurrent related sequences, organized to handle some operation. Each exchange is identified by an Originator Exchange ID (OX_ID) in the frame header, and possibly by a Responder Exchange ID (RX_ID).

Extended LinkServices

Link services that implement complex operations, usually with a whole exchange. Some examples are: Fabric Login (FLOGI), Logout command (LOGO), and Abort Exchange (ABTX).

FFabric One or more switching devices that interconnect Fibre Channel

N_Ports, and route Fibre Channel frames based on destination IDs in the frame headers.

Fabric Login Sequences interchanged between an N_Port and the Fabric to determine the service parameters.

FC-AL The Fibre Channel Arbitrated Loop standard.

FC-SW The Fibre Channel Fabric standard.

FCP Fibre Channel Protocol. The mapping of SCSI-3 operations to Fibre Channel.

F_Port Fabric Port; a physical interface within the fabric that attaches to an N_Port through a point-to-point full-duplex link connection.


Glossary

Frame A data structure used to transport information from one Fibre Channel port to another.

Full Duplex A mode of communications allowing simultaneous transmission and reception of frames on the same link.

GGigabit Link Module

(GLM)A transceiver component capable of receiving and transmitting on the Fibre Channel interface at rates up to 1062.5 megabits/second.

G_Port Generic Port; a physical interface within the fabric, capable of acting either as an F_Port or an E_Port (depending on the port type at the other end of the link).

HHalf Duplex A mode of communication that allows transmission or reception of

frames on a link, but not both at the same time (other than link control frames, which are always permitted).

Hard Address The Arbitrated Loop Physical Address (AL_PA) that an NL_Port attempts to acquire in the Loop Initialization Hard Address (LIHA) sequence.

HBA Host Bus Adapter.

Host Bus Adapter A card in the host device that provides a connection to a Fibre Channel loop.

IInternet Protocol (IP) The TCP/IP standard protocol that defines the IP datagram as the

unit of information passed across an internet and provides the basis for connectionless, best-effort packet delivery service. IP includes the ICMP control and error message protocol as an integral part.

IP Address A unique string of numbers that identifies a device on a network. The address is in dotted decimal format, which consists of four groups of numbers delimited by periods; that is, nnn.nnn.nnn.nnn, where nnn is a decimal in the range 000 to 255. Every resource on the network must have an IP address.

Glossary g-3

g-4

Glossary

LLIFA Loop Initialization Fabric Address.

LIHA Loop Initialization Hard Address.

Link A connection between two Fibre Channel ports consisting of a transmit fibre and a receive fibre.

Link Services Frames, sequences and exchanges used by the Fibre Channel protocol itself for control purposes. Also see Basic Link Services and Extended Link Services.

LIPA Loop Initialization Previous Address.

LISA Loop Initialization Soft Address.

Logical UnitAddressing

One of the three SCSI-3 addressing modes supported by Symmetrix Fibre Channel. When the director port is set for Logical Unit Addressing, Symmetrix responds to a host’s Inquiry command as an Array Controller (0x0C returned in the Peripheral Device Type Field). The host discovers the Logical Unit Numbers (LUNs) assigned to the port by issuing an Report LUNs command. Symmetrix returns a list of LUNs that can be accessed by the host. Symmetrix Logical Unit Addressing supports up to 128 logical devices per port, addressed by LUN (0–15), Target ID (0–15), and Virtual Bus (0–7). Also see Peripheral Device Addressing and Volume Set Addressing.

Logical Unit Number An encoded three-bit identifier for a logical device. (Logical devices are recognized by software as separate entities, even if they are not individual physical entities.)

Loop Circuit A temporary point-to-point path that allows bidirectional communications between ports on a loop.

Loop_ID A set of 7-bit values, numbered consecutively from 0 to 7D hex (0 to 125 decimal), that represent the 126 legal Arbitrated Loop Physical Address (AL_PA) values on a loop. (Not all of the 256 possible AL_PAs are used in FC-AL.)

Loop InitializationProcess

A process that transmits a set of sequences around a loop, assigning a physical address (AL_PA) to each NL_Port in the loop.


Glossary

L_Port A Node or Fabric port capable of performing Arbitrated Loop functions and protocols.

LUN See Logical Unit Number.

NName Server The program facility that allows N_Ports to register and discover

Fibre Channel attributes.

Network Address A name or address that identifies a managed product, such as a fabric switch. The Network Address can be either an IP address in dotted-decimal notation, or a domain name service (DNS) name as administered on a customer network. All DNS names have a hostname component and, if fully qualified, a domain component, such as host1.abcd.com. In this example, host1 is the hostname and abcd.com is the domain component.

N_Port Node Port; a physical interface within an end device (node) that can attach to an F_Port or directly to another N_Port, through a point-to-point link connection.

N_Port Login Sequences interchanged between two N_Ports in a similar manner to the protocol carried to a Fabric.

N_Port Logout A request from an N_Port for removal of its service parameters from another port.

Node An entity with one or more N_Ports or NL_Ports.

Non-L_Port A Node or Fabric port that is not capable of performing the Arbitrated Loop functions and protocols.

Non-ParticipatingMode

A mode within an L_Port that inhibits that port from participating in loop activities. L_Ports in this mode continue to retransmit received transmission words, but are not permitted to arbitrate or originate frames. An L_Port in the non-participating mode may or may not have an Arbitrated Loop Physical Address.

OObject Database

ManagerThe ODM is a data manager that controls the storage of AIX and HP-UX system data. All devices, volume groups, logical volumes, physical volumes, physical partitions, and logical partitions have an

Glossary g-5

g-6

Glossary

entry in the ODM. ODM also contains information on commands that are initiated via SMIT (System Manager Interface Tool) and SAM (System Administrator Manager).

ODM See Object Database Manager.

Open An Arbitrated Loop protocol used to establish a loop circuit.

Ordered Set A specific combination of four Transmission Characters, used as a Frame Delimiter, Primitive Signal, or Primitive Sequence.

PPeripheral Device

AddressingOne of the three SCSI-3 addressing modes supported by Symmetrix Fibre Channel. When the director port is set for Peripheral Device Addressing, Symmetrix responds to a host’s Inquiry command as a Direct Access Device (0x00 returned in the Peripheral Device Type Field). The host discovers the LUNs assigned to the port by accessing the LUN directly. Symmetrix Peripheral Device Addressing supports up to 128 logical devices per port, addressed by LUN (0 - 15) and Target ID (0 - 15) (Virtual Bus address is not used). Also see Logical Unit Addressing and Volume Set Addressing.

Port_Name A unique 64-bit identifier assigned to each Fibre Channel port, and communicated during the login and port discovery processes.

Preferred Address The Arbitrated Loop Physical Address that an NL_Port attempts to acquire first during loop initialization.

Previously AcquiredAddress

During loop initialization, the Arbitrated Loop Physical Address that was in use prior to receipt of LIP (Loop Initialization Protocol). Immediately following power-on and between the time one loop initialization completes and the next one begins, an NL_Port may not have the previously acquired address unless it remembers it while power is removed.

Primitive Sequences A series of three consecutive transmission words of the same value, used to transmit control information between ports. The following are some important Primitive Sequences: NOS (Not Operational Ordered Set), OLS (Offline Ordered Set), LR (Link Reset), LRR (Link Reset Response), LIP (Link Initialization Protocol), LPE (Loop Port Enable), LPB (Loop Port Bypass).


Glossary

Primitive SequenceProtocols

Low-level handshaking and synchronization for link failure, link initialization, and/or link reset.

Primitive Signals A single transmission word used to transmit control information between ports. The following are some important Primitive Signals: Idle, R_RDY (Receiver Ready), ARB (Arbitrate), OPN (Open), CLS (Close), MRK (Mark).

Protocols Interchanges of specific sets of data for performing certain defined functions.

Private Loop DirectAttach

A technical report that defines a subset of the relevant standards suitable for the operation of peripheral devices such as disks and tapes on a private loop. A private NL_Port. An NL_Port that does not attempt login with the fabric and only communicates with other NL_Ports on the same loop.

Public NL_Port An NL_Port that attempts login with the fabric and can observe the rules of either public or private loop behavior. A public NL_Port may communicate with both private and public NL_Ports.

SSCSI-3 Small Computer System Interface version 3. SCSI is a an ANSI

parallel-interface standard for attaching peripheral devices to computers.

Sequence A set of related data frames transmitted unidirectionally. Each sequence is identified by a sequence ID (SEQ_ID). The frames within the sequence are identified using a sequence count (SEQ_CNT).

TTopology An interconnection scheme that allows multiple Fibre Channel ports

to communicate.

TPRLO Third-party Process Logout, an FC-AL addressing parameter that allows a third party to log ot a session between two FC-4 processes. (FC-4 is the Fibre Channel functional level that deals with the mapping of existing I/O interfaces for use on Fibre Channel by using the tools available in Fibre Channel.) TPRLO can be used during error recovery in multi-initiator environments to free resources associated with a failed port in an image pair.

Glossary g-7

g-8

Glossary

TransmissionCharacter

A 10-bit character encoded according to the rules of the 8B/10B algorithm. See 8B/10B Coding.

Transmission Word A 40-bit group consisting of four 10-bit transmission characters.

VVolume SetAddressing

One of the three SCSI-3 addressing modes supported by Symmetrix Fibre Channel. When the director port is set for Volume Set Addressing, Symmetrix responds to a host’s Inquiry command as an Array Controller (0x0C returned in the Peripheral Device Type Field). The host discovers the LUNs assigned to the port by issuing an Report LUNs command. Symmetrix returns a list of LUNs that can be accessed by the host. Symmetrix Volume Set Addressing supports up to 512 logical devices per port, addressed by LUN (0–7), Target ID (0–15), and Virtual Bus (0–32). Also see Logical Unit Addressing and Peripheral Device Addressing.

WWWN (World Wide

Name)Uniquely identifies a switch, even on global networks. This is a 64-bit number (nn:nn:nn:nn:nn:nn:nn:nn).

ZZoning Allows an administrator to group several devices by function or by

location. All devices connected to a fabric switch can be configured into one or more zones. Devices in the same zone can see each other, while devices in different zones cannot.

Zone Set A set of zones.


Sales and ServiceLocations

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 American Salesand 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-1077

Sales and Service Locations s-1

s-2


Houston, TX 713-621-9800Indianapolis, IN 317-577-9766Inglewood, CA 310-364-1222Irvine, 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 0000



Lyon, France (33) 7 860 1330Marseille, 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 s-3

s-4



Index

Numerics8B/10B coding g-1

AAdapter (Fibre Channel director) 1-36Adding devices on line

SGI Origin 6-8Solaris x86 10-24

Addressingfabric C-4FC-AL C-2SCSI-3 C-5

AIX host 7-1Arbitrated loop 1-21

CCables 1-38Capacity topology 1-27Coding, 8B/10B g-1Compaq HBA, in Windows NT host on arbitrated

loop 4-8Configuration examples, Fibre Channel/SCSI 1-4Configuring Symmetrix

for AIX host on arbitrated loop 7-4for HP 9000 host on arbitrated loop 2-4for NetWare host on arbitrated loop 9-4for SGI Challenge host on arbitrated loop 5-4for SGI Origin host on arbitrated loop 6-4for Siemens host on arbitrated loop 8-4for Solaris SPARC host on arbitrated loop

3-4for Solaris SPARC host on fabric 11-4

for Solaris X86 host on arbitrated loop 10-4for Sun Enterprise host on arbitrated loop

3-4for Windows NT host on arbitrated loop 4-6for Windows NT host on fabric 12-5

Consolidation topology 1-30

DData transfer specification A-2Direct access device C-5Director 1-35

board 1-35data paths 1-36interconnects 1-36operator panel functions 1-37slot locations 1-37total supported 1-35

Distance topology 1-25

Eemc_s2f B-8emc_s2f_hp B-10Emulex HBA

in AIX host on arbitrated loop 7-5in Sun Enterprise host on arbitrated loop

3-25in Windows NT host on arbitrated loop 4-22in Windows NT host on fabric 12-14

Enable/Disable switch 1-37

i-1Index

i-2

Index

FFC-AL 1-21FC-SW 1-7Fiber optic cables 1-38Fiber optic transceiver A-2Fibre Channel

adapter 1-35director 1-35mux 2-8overview 1-2port types 1-20topologies 1-2, 1-21

HHard addressing C-3Hardware 1-35HBA, installing. See individual manufacturer’s nameHewlett Packard. See HPHosts, supported 1-8

AIX on arbitrated loop 7-1HP 9000 on arbitrated loop 2-1NetWare on arbitrated loop 9-1SGI Challenge on arbitrated loop 5-1SGI Origin on arbitrated loop 6-1Siemens/Reliant on arbitrated loop 8-1Solaris SPARC on arbitrated loop 3-1Solaris SPARC on fabric 11-1Solaris X86 on arbitrated loop 10-1Windows NT on arbitrated loop 4-1Windows NT on fabric 12-1

HP 9000 Host on arbitrated loop 2-1HP A5246A HBA, in Windows NT host on

arbitrated loop 4-10HP D8602A HBA, in Windows NT host on

arbitrated loop 4-12Hubs 1-7

comparison to switches 1-23HP 2-6IBM (for AIX host) 7-6Sun 3-38Vixel (for Siemens host) 4-2, 8-11

IIBM hub (for AIX host) 7-6Interface mapping A-2

JJaycor HBA

in Solaris SPARC host on arbitrated loop 3-5in Solaris SPARC host on fabric 11-5

LLEDs for Directors 1-37LIP C-2Logical unit addressing C-5Loop Identifier C-3Loop initialization process C-2

MMicrocode levels required 1-3Migrating from SCSI to Fibre Channel B-1

HP host B-6SGI Challenge host B-6Sun Solaris host B-5

Mux 1-7HP 2-8

NNetware host 9-1NT. See Windows NT

OOperator panel functions 1-37

PPeripheral device addressing C-5Ports

maximum 1-35standard configuration 1-21total supported 1-35

Prisa HBA, in SGI Challenge host on arbitrated loop 5-5

PV Link 2-5

QQlogic HBA

in NetWare host on arbitrated loop 9-5in Solaris SPARC host on arbitrated loop

3-15


Index

in Solaris X86 host on arbitrated loop 10-5in Sun Enterprise host on arbitrated loop

3-15in Windows NT host on arbitrated loop 4-16in Windows NT host on fabric 12-9

Queue tags A-2

SSCSI-3 FCP C-2SCSI-MUX 1-7SGI Challenge host on arbitrated loop 5-1SGI Origin host on arbitrated loop 6-1Siemens HBA, in Siemens host on arbitrated loop

8-5Siemens/Reliant UNIX host on arbitrated loop

8-1Solaris Enterprise host on arbitrated loop 3-1Solaris SPARC host

on fabric 11-1Solaris SPARC host on arbitrated loop 3-1Solaris X86 host on arbitrated loop 10-1SPARC. See Solaris SPARCSpecifications A-1Sun hub, configuration guidelines 3-38, 10-25Sun Solaris SPARC. See Solaris SPARCSupport information, where to find 1-8Switches 1-7

comparison to hubs 1-23Symmetrix configuration

for AIX host on arbitrated loop 7-4for HP 9000 host on arbitrated loop 2-4

for NetWare host on arbitrated loop 9-4for SGI Challenge host on arbitrated loop 5-4for SGI Origin host on arbitrated loop 6-4for Siemens host on arbitrated loop 8-4for Solaris SPARC host on arbitrated loop

3-4for Solaris SPARC host on fabric 11-4for Solaris X86 host on arbitrated loop 10-4for Sun Enterprise host on arbitrated loop

3-4for Windows NT host on arbitrated loop 4-6for Windows NT host on fabric 12-5

Symmetrix models 1-3

TTACHYON 1-35Tag Command Queuing Enabled 6-7Topologies

connectivity 1-25network 1-22supported 1-3

VVixel hub (for Siemens host) 4-2, 8-11Volume set addressing C-5

WWindows NT host

on arbitrated loop 4-1on fabric 12-1

i-3Index

20999642 Fc Director

Documents

Transcript of 20999642 Fc Director