Tivoli SANergy - IBM

Tivoli SANergyAdministrator’s GuideVersion 2 Release 2

Tivoli SANergyAdministrator’s GuideVersion 2 Release 2

NoteBefore using this information and the product it supports, read the generalinformation under “Notices” on page ix.

Second Edition (November 2000)

This edition applies to Version 2 Release 2 of Tivoli SANergy, 5698–SFS, and to anysubsequent releases. This edition applies until otherwise indicated in new editions. Make surethat you are using the correct edition for the level of the product.

Order publications through your Tivoli representative or the Tivoli branch office that servesyour locality.

Tivoli welcomes your comments. You can send us comments about this book electronically:

¶ Internet: [email protected]

When you send information to Tivoli, you grant Tivoli a nonexclusive right to use ordistribute the information in any way Tivoli believes appropriate without incurring anyobligation to you.

© Copyright International Business Machines Corporation 2000. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSAADP Schedule Contract with IBM Corp.

Contents

Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

About This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiWhat’s New in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Conventions Used in This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Chapter 1. Introducing Tivoli SANergy . . . . . . . . . . . . . . . . . . . 1SANergy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

High Availability Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Operational Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

SANergy Architectural Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Meta Data Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

LAN Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

SAN Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Windows System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Sun Solaris System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Linux (Red Hat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

SGI IRIX UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Compaq Tru64 UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

IBM AIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Data General DG/UX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

iiiTivoli SANergy Administrator’s Guide

Apple Macintosh System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3. Windows Installation and Configuration . . . . 19Device Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Windows MDC Setup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Setting Up the First MDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Windows Host Setup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

SANergy Setup Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Using the Performance Tester Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Using the Select Managed Buses Dialog . . . . . . . . . . . . . . . . . . . . . . . 40

Using the Device Assignment Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Using the Volume Assignment Dialog . . . . . . . . . . . . . . . . . . . . . . . . . 44

Using the Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Using the About Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Uninstalling SANergy on Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 4. UNIX Installation and Configuration . . . . . . . . 53Device Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

UNIX to Windows Networking (LAN Connection) . . . . . . . . . . . . . . . . . . . 55

SAN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Mount the NFS Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Installing SANergy on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Linux and Solaris MDC Setup Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . 60

UFS Hyper-Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

SANergy UNIX Configuration Tool and SANergyconfig Program . . . . . . . . 63

Using the SANergy UNIX Configuration Tool . . . . . . . . . . . . . . . . . . . 64

Using the SANergyconfig Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

iv Version 2 Release 2

Uninstalling SANergy on All UNIX Computers . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 5. Macintosh Installation and Configuration 85Setting Up the Macintosh Network Environment . . . . . . . . . . . . . . . . . . . . . 85

SANergy Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Displaying the SANergy Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Uninstalling the SANergy Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 6. Managing SANergy. . . . . . . . . . . . . . . . . . . . . . . . . . . 95Adding Host Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Removing Host Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Adding Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Deleting Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Renaming Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Repartitioning Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Changing the MDC Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Chapter 7. Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Meta Data Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Data Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

UNIX Systems Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . 113

Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

vTivoli SANergy Administrator’s Guide

Volume Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

MDC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Multiple Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Macintosh Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Chapter 8. High Availability Feature. . . . . . . . . . . . . . . . . . . . 121SANergy and the High Availability Feature . . . . . . . . . . . . . . . . . . . . . . . . 121

High Availability Feature Architectural Overview . . . . . . . . . . . . . . . . . . . . 122

High Availability Feature System Elements . . . . . . . . . . . . . . . . . . . . 122

High Availability Feature System Services and Privileges . . . . . . . . . . 123

High Availability Feature System Operation . . . . . . . . . . . . . . . . . . . . . . . . 124

Usage and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Setting Up Administrative Privileges Before Performing the HighAvailability Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Installing the High Availability Feature . . . . . . . . . . . . . . . . . . . . . . . 127

High Availability Setup Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Using the Standby Assignment Dialog . . . . . . . . . . . . . . . . . . . . . . . . 138

Changing the Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Uninstalling the High Availability Feature . . . . . . . . . . . . . . . . . . . . . 141

UNIX Host High Availability Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

UNIX Host Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Appendix A. SANergy SNMP Management . . . . . . . . . . . . 145

Appendix B. MSCS Configuration . . . . . . . . . . . . . . . . . . . . . . 153Install and Configure an MSCS Cluster for Use with SANergy. . . . . . . . . . 154

vi Version 2 Release 2

Install SANergy on a Single Node using Special Marks . . . . . . . . . . . . . . . 154

Install the SANergy-MSCS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Create SANergy Disk Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Host-side Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Uninstalling SANergy or the SANergy-MSCS Layer . . . . . . . . . . . . . . . . . 158

Appendix C. Enhancing Small File Operations . . . . . . . . 159Major Components and Configuration for Linux and Solaris. . . . . . . . . . . . 162

Host Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

MDC Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

ZOOM Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

ZOOM Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

viiTivoli SANergy Administrator’s Guide

viii Version 2 Release 2

Notices

This information was developed for products and services that areoffered in the U.S.A.

IBM may not offer the products, services, or features that arediscussed in this document in other countries. Consult your localIBM representative for information on the products and servicescurrently available in your area. Any reference to an IBM product,program, or service is not intended to state or imply that only thatIBM product, program, or service may be used. Any functionallyequivalent product, program, or service that does not infringe anyIBM intellectual property right may be used instead. However, it isthe user’s responsibility to evaluate and verify the operation of anynon-IBM product, program, or service.

IBM may have patents or pending patent applications to coversubject matter that is described in this document. The furnishing ofthis document does not give you any license to these patents. Youcan send license inquiries, in writing, to the following address:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information,contact the IBM Intellectual Property Department in your country orsend inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdomor any other country where such provisions are inconsistent withlocal law: INTERNATIONAL BUSINESS MACHINESCORPORATION PROVIDES THIS PUBLICATION ″AS IS″

ixTivoli SANergy Administrator’s Guide

WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITYOR FITNESS FOR A PARTICULAR PURPOSE. Some states do notallow disclaimer of express or implied warranties in certaintransactions; therefore, this statement may not apply to you.

This information could include technical inaccuracies ortypographical errors. Changes are periodically made to theinformation herein; these changes will be incorporated in neweditions of the publication. IBM may make improvements and/orchanges in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites areprovided for convenience only and do not in any manner serve as anendorsement of those Web sites. The materials at those Web sites arenot part of the materials for this IBM product, and use of those Websites is at your own risk.

IBM may use or distribute any of the information you supply in anyway it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it forthe purpose of enabling the following:

¶ The exchange of information between independently createdprograms and other programs (including this one) and

¶ The mutual use of the information which has been exchanged,should contact the person at the following address:

IBM CorporationInformation Enabling RequestsDept. M135600 Cottle RoadSan Jose, CA 95193-0001U.S.A.

Such information may be available, subject to appropriate terms andconditions that include in some cases, payment of a fee.

x Version 2 Release 2

The licensed program described in this document and all licensedmaterial available for it are provided by IBM under terms of thefollowing:

¶ IBM Customer Agreement

¶ IBM International Program License Agreement

¶ Or any equivalent agreement between us.

Information concerning non-IBM products was obtained from thesuppliers of those products, their published announcements or otherpublicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or anyother claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to thesuppliers of those products.

This information is for planning purposes only. The informationherein is subject to change before the products described becomeavailable.

If you are viewing this information in softcopy, the photographs andcolor illustrations may not appear.

TrademarksThe following terms are trademarks or registered trademarks ofTivoli Systems Inc. and the IBM Corporation in the United States, orother countries, or both:

AIX SANergyIBM TivoliRS/6000

Microsoft, Windows, Windows NT, and the Windows logo aretrademarks of Microsoft Corporation in the United States, othercountries, or both.

xiTivoli SANergy Administrator’s Guide

Netscape, Netscape Navigator, and Netscape Communicator aretrademarks or registered trademarks of the Netscape CommunicationsCorporation in the United States and other countries.

ActionMedia, LANDesk, MMX, Pentium and ProShare aretrademarks of Intel Corporation in the United States, other countries,or both.

Sun, Solaris, Java, and all Java-based trademarks, and logos aretrademarks or registered trademarks of Sun Microsystems, Inc. in theUnited States and other countries.

UNIX is a registered trademark in the United States and othercountries licensed exclusively through The Open Group.

Other company, product, and service names may be trademarks orservice marks of others.

xii Version 2 Release 2

About This Book

This publication is for the system administrator or systemprogrammer who is responsible for installing and configuring useraccess to the disk drives. It assumes that you have a workingknowledge of the operating system and networking on: Macintosh,Windows NT, Windows 2000, or UNIX computers. For moreinformation on these operating systems, refer to the documentationthat came with your computer.

The following table indicates which Web site to access for additionalinformation.

Table 1. Product Web SitesProduct Web Site

Tivoli SANergy http://www.tivoli.com/storage

This book in PDF andHTML format

http://www.tivoli.com/support/SANergy

Tivoli Web site http://www.tivoli.com/storage

Netscape Navigator orCommunicator

http://www.netscape.com

xiiiTivoli SANergy Administrator’s Guide

What’s New in this ReleaseThese are improvements to SANergy 2.2 that did not exist inSANergy 2.1.

¶ Red Hat Linux SANergy Host, v 6.2

¶ Red Hat Linux SANergy MDC, v 6.2

¶ DG/UX SANergy Host (special SANergy patch release availablefrom DG)

¶ UNIX MDCs for all hosts including Mac OS, Windows NT, andWindows 2000

¶ Improved SANergy functionality for Mac OS 8 and 9, including:no dongle, LUN support, new DAVE base

¶ ZOOM is a new feature that improves small file readperformance.

¶ Device Ownership function for Windows and UNIX

¶ Heterogeneous LUN masking and protection

¶ Support for try-and-buy and no registration string full productlicense support

¶ Compatibility with SANergy 2.1 existing systems

Other changes:

¶ Name of product: Tivoli SANergy File Sharing 2.1 is now TivoliSANergy 2.2

¶ In 2.1, the computers connected to a SAN were referred to asclients. In 2.2, they are referred to as hosts. With TivoliSANergy installed on the hosts connected to a SAN, anynetwork-capable application can use files from that storage poolas if they were files from a server on the LAN.

xiv Version 2 Release 2

Conventions Used in This PublicationThis publication uses the following typographical conventions:

Table 2. Typographical ConventionsExample Description

bold Boldface type indicates a command,directory name, or file name. Forthe GUI, boldface type indicates awindow name, button, menu item,option, icon, or field. Bold type isalso used for emphasis in the text.

example Monospaced type representsfragments of a program, anexample, or information as it wouldappear on a display screen.

italics Italicized type indicates the name ofan optional parameter or a newterm.

xvTivoli SANergy Administrator’s Guide

xvi Version 2 Release 2

Introducing Tivoli SANergy

Tivoli SANergy is the complete software solution that lets youdeliver shared data access at the speed of a SAN, using FibreChannel, SCSI, or SSA. It gives multiple computers the power todynamically share file and data access on SAN-based storage, usingstandard networks and file systems.

Storage Area Networks (SANs) hold the promise of decreasedoperational costs and increased efficiency. SANergy enables multiplesystems to share the same storage at media speeds, which reducescost by eliminating the need for redundant storage. Most operatingsystems require that only one system access and control any givenphysical storage device. Thus, true SAN-based data sharing was notpossible – until now, with SANergy.

SANergy employs patented technology to combine the simplicity ofLAN-based file sharing with the very high data transfer speeds ofFibre Channel, SCSI, and SSA storage networks. The result ishigh-speed, heterogeneous data sharing, without theperformance-limiting bottlenecks of file servers and traditionalnetworking protocols.

1

1Tivoli SANergy Administrator’s Guide

1.In

trod

ucin

gS

AN

ergy

Table 3. Quick Look at SANergyFeature What it Does What it Means to You

Single filesystem

Uses NTFS, EXT2,UFS, QFS, or any otherTivoli SANergy-enabledthird party file system.

Eliminates the need to managemultiple file systems,regardless of the number ofcomputers connected to theSAN.

LAN-flexible Utilizes any LANhardware and software.

Continues using your existingLAN to handle metadatatraffic and low-bandwidthdata.

SAN-flexible Utilizes any SANhardware and software.

Works equally well with SCSI,SSA, or Fibre Channel SANswith components from anymanufacturer.

Heterogeneousoperation

Supports true filesharing acrossheterogeneous networks.

Works with the mix ofcomputers and operatingsystems you use today.

Enterprisemanagement-ready

Controlled through theWeb and SNMPmanagement.

Enables immediate controlthrough most SANmanagement consoles.

SANergySANergy is unique in that it extends the standard file systems andnetwork services provided by the operating systems that it supports.As an operating system extension built on standard systeminterfaces, SANergy fully supports the user interface, management,access control, and security features native to the host platforms.Therefore, it provides all the file system management, access control,and security you expect in your network. With SANergy, virtuallyany network-aware application can access any file at any time, andmultiple systems can transparently share common data. SANergyensures maximum compatibility with existing and future operatingsystems, applications, and management utilities.

In addition to the SAN, SANergy also uses a standard LAN for allthe metadata associated with file transfers. Because SANergy is

2 Version 2 Release 2

based on standard file systems, if your SAN fails, you can continueto access your data through the LAN.

With SANergy, you can reduce or even eliminate the expense ofredundant storage and the overhead of data synchronization inmulti-host environments utilizing large-scale web, video, or fileservers. Because each system has direct access to the SAN-basedstorage, SANergy can also eliminate your file server as a singlepoint of failure for mission-critical enterprise applications, reducingcostly down time. Additionally, SANergy can readily manage allyour data backup traffic over the storage network, while users enjoyunimpeded LAN access to your existing file servers.

SANergy brings you true collaboration and scalable, cost-effectivenetwork and server expansion, at full SAN speeds. SANergy deliversthe power to share and realizes the full potential of a SANinvestment for today and for the future.

High Availability FeatureHigh Availability is a separately priced feature and is optional. Itprovides extended availability of storage resources by ensuring thatfailovers occur transparently. This layered application eliminatessingle points of failure within the SAN by monitoring the computersthat control access to storage devices. Should one of these systemsfail, a system running the High Availability feature takes over itsoperations.

See “High Availability Feature” on page 121 for information oninstallation and usage of the High Availability feature.

Note: The High Availability feature is available on Windows NTand Windows 2000 MDC systems.

The High Availability feature is also available for UNIXhosts, but only if you are using Windows system as the MetaData Controller (MDC).


1.In

trod

ucin

gS

AN

ergy

Technical SupportIf you are having trouble using SANergy, you should:

1. Retry the action, carefully following the instructions given forthat task in this publication.

2. See “Troubleshooting” on page 101 for the troubleshootinginformation.

3. Try to reproduce the problem and document the exact scenario inwhich it occurs. If possible, save screen captures of all error andevent messages.

4. Try to determine the nature of the problem. Narrow down theproblem by eliminating variables. If it appears to be a hardwareproblem, check the documentation that came with your hardwarefor maintenance or hardware-related issues. Contact yourhardware representative if necessary.

5. Check the Tivoli Web site for any updates that might affect yourspecific configuration. The Web site is:http://www.tivoli.com/storage

6. Please visit the SANergy Technical Support Web site at:http://www.tivoli.com/support/sanergy

to see if your questions or problems can be answered or resolvedbefore calling support. This way you might be able to get ananswer to your question or solve your problem without having tocall and wait for voice support.

7. If you do not find the solution to your problem, contact TivoliCustomer Support (see “Contacting Customer Support” onpage 5).


Contacting Customer SupportFor support for this or any Tivoli product, you can contact TivoliCustomer Support in one of the following ways:

Contact Method Contact Information

Tivoli Storage Managertechnical support Website

http://www.tivoli.com/support/storage_mgr/tivolimain.html

Submit a problemmanagement record(PMR)

IBMSERV/IBMLINK athttp://www2.ibmlink.ibm.com

Submit a problemmanagement record(PMR)

http://www.tivoli.com/support

E-mail [email protected]

Telephone (UnitedStates)

1-800-TIVOLI8 (1-800-848-6548)

Telephone (International) Consult the Web site for customer supporttelephone numbers

You can also review the Customer Support Handbook, which isavailable on our Web site athttp://www.tivoli.com/support/handbook/.

When you contact Tivoli Customer Support, be prepared to provideidentification information for your company so that supportpersonnel can readily assist you. Company identification informationmay also be needed to access various online services available onthe Web site.

The support Web site offers extensive information, including:

¶ a guide to support services (the Customer Support Handbook)

¶ frequently asked questions (FAQs)

¶ documentation for all Tivoli products, including Release Notes,Redbooks, and Whitepapers


1.In

trod

ucin

gS

AN

ergy

The documentation for some product releases is available in bothPDF and HTML formats. Translated documents are also available forsome product releases. You can order documentation by e-mail [email protected]. Please provide the publication number, partnumber, or order number of the desired document. Alternatively, youcan provide the document title, version number, and date ofpublication.

We are very interested in hearing about your experience with Tivoliproducts and documentation. We also welcome your suggestions forimprovements. If you have comments or suggestions about ourdocumentation, please contact us in one of the following ways:

¶ Send e-mail to [email protected].

¶ Complete our customer feedback survey athttp://www.tivoli.com/support/feedback.


Overview

This section provides information on SANergy operation andarchitecture, and the system and network requirements that areneeded to use the software.

Operational OverviewTo set up SANergy on your network, use the following steps:

1. Make sure that your network is correctly configured for LocalArea Networking (LAN) and Storage Area Networking (SAN).

2. Configure your storage system, including disk formatting,partitioning, and volume configuration.

3. Install SANergy on the systems you have chosen to use as MetaData Controllers (MDCs). The systems can be Windows NT,Windows 2000, Solaris, or Linux (Red Hat).

4. Install SANergy on the host systems.

You will notice that the speed increases immediately.

2


2.O

verview

SANergy Architectural OverviewThe basic problem in storage area networking at the file level iskeeping the separate operating systems current with each other’sindependent and asynchronous use of the storage. SANergy is ahybrid of conventional networking and directly attached storage.Conventional networking can easily keep many computers coherent.That is, if one computer has an open view of a directory, andanother changes that directory (adds or deletes a file), the view onall computers will change. Conventional networking allowsadministrators to establish centralized access control lists and otherdata management facilities.

Data about data is called metadata. Examples include file names, filesizes, and access control lists. The SANergy architecture letsmetadata transactions take place over conventional LAN networking.The actual content of files moves on the high-speed direct SANconnection.

SANergy works with Ethernet, asynchronous transfer mode (ATM),or anything else that carries networking protocols. Furthermore, thenetwork operating system can be SMB (on Windows), Appletalk,Network File System (NFS) on UNIX, or a combination. However,only certain protocols and combinations have been tested.


Similarly, SANergy supports any available disk-attached storagefabric. This includes Fibre Channel (FC), SSA, small computersystem interface (SCSI), and any other disk-level connection. It isalso possible for installations to use one set of physical wiring tocarry both the LAN and storage traffic. Fibre channel supports bothInternet Protocol (IP) and SCSI protocols.

When you use SANergy, one computer in the workgroup is used asthe Meta Data Controller (MDC) for a particular volume. You canhave a single computer as the MDC for all volumes, or you canspread the MDC task among several computers. The other computers(hosts) use conventional networking to mount volumes, andSANergy separates the metadata from the raw data automatically.

Figure 1. Hybrid Shared-Storage Networking


2.O

verview

Meta Data ControllerIn any configuration, on a per file system basis, one computer needsto be assigned as the security and Meta Data controller (MDC) forSANergy shared volumes. There can be as many MDCs as there arefile systems, or a single MDC for all file systems (or anything inbetween). Currently, only NT 4.0, Windows 2000, Solaris, and Linuxcan be MDCs. The MDC system also acts as the server for thespecific shared volume or volumes. However, the MDC’s role as aserver is only to manage user authentication, access control, and filesystem locking operations. SANergy redirects I/O directly over theSAN.

Windows shared volumes must be formatted using the NT (NewTechnology) File System with Windows NT 4.0 or Windows 2000.Windows NT 4.0 and Windows 2000 support Microsoft ClusterServer (MSCS) failover.

Solaris MDC shared volumes must be formatted using UFS or QFS.Linux shared volumes must be formatted using EXT2FS.

LAN EnvironmentAll computers must share a common local area network and protocol(for example, TCP/IP over Ethernet), and be able to see each otheron the LAN. This includes an operational LAN network interface(for example, embedded Ethernet or separate Ethernet adapter). Allhost computers must be able to map (mount) the MDC sharedvolumes. This requires that the standard network operating systemsoftware be installed and configured so that each machine can accessa shared volume on the MDC server.

For Windows, use the built-in Windows networking and sharing.

For Mac OS, Thursby’s DAVE software is required to mount theshared Windows NT volumes. Tivoli supplies the appropriateportions of DAVE with each SANergy for Macintosh.

For UNIX systems, use NFS to mount the shared volumes. Tosupport UNIX systems, you also need NFS server software for your


Windows MDC system. For example, the NFS server software isIntegraph’s DiskShare, NetManage’s Chameleon UNIX Link 97,FTP Software’s InterDrive, and Hummingbird Communications NFSMaestro.

If you are going to include Windows and/or Macintosh computers ashosts with your UNIX MDCs, you must install a CIFS package, suchas Samba, on your MDCs to create shares. You must create NFSshares that match the names of the CIFS shares, otherwise they willnot fuse. In addition, the UNIX MDC must start Samba from anaccelerated window in order to have fused access to the volumes.This is not necessary for Windows hosts.

SAN EnvironmentAll systems must share a common storage area network connectionto shared storage devices. Typically, this will be a connection overshared SSA, or Fibre Channel (switched or arbitrated loop) physicalmedia. A SAN host bus adapter (HBA) is also required in eachsystem with appropriate SAN drivers installed. The interconnecttechnology and associated HBA can be SCSI, SSA, or FibreChannel.

All HBAs must support a multi-initiator environment:

¶ SAN network devices (for example, FC-AL hubs, fabric, andswitches)

¶ SAN storage devices (for example, RAID or JBOD arrays)

For Fibre Channel SANs, all systems and drives to be shared mustalso be in a common zone. Zones and fabrics might requireadditional configuration for proper operation.

System Requirements

Note: Check the README file, located on your SANergy CD, forcurrent information on system requirements.

Tivoli SANergy 2.2 supports the following operating systems withthe following functions.


2.O

verview

Operating System Host MDC HA Zoom SNMP

Windows NT 4 X X X – X

Windows 2000 X X X – X

Mac OS 8 + 9 X – – – –

AIX X – – – X

Solaris X X – X X

Tru64 X – – – –

Linux (Redhat) X X – X –

DG/UX X – – – –

Tivoli SANergy Version 2.2 supports the following MDC and Hostcombinations

Hosts MDC

WinNTNTFS

Win2KNTFS

SolarisUFS

SolarisQFS

LinuxEXT2FS

Windows NT 4 X X X X X

Windows 2000 X X X X X

Mac OS 8 + 9 X X X X X

AIX X X X X X

Solaris X X X X X

Tru64 X X X X X

Linux (Redhat) X X X X X

DG/UX X X X X X

Each system in your SAN must meet the following requirements:

¶ 1 PCI slot available for a new host bus adapter

¶ Functional LAN network interface

¶ CD drives for software installation

¶ SAN host bus adapter in each system with appropriate SANdrivers installed


Windows SystemA Windows server and workstation require the following hardwareand software:

¶ Machine: An Intel Pentium processor

¶ Minimum memory and space requirements to run:

v RAM: 64 MB, in addition to the memory required by otherapplications

v Disk space: 20 MB

¶ Operating system (one of the following):

v Windows NT Workstation, Version 4.0, SP4, SP5, or SP6

v Windows NT Server, Version 4.0, SP4, SP5, or SP6

v Windows 2000

To determine the version of Windows you have and the amountof memory that is installed on your system, do the followingsteps:

1. On the desktop, double-click My Computer,

2. Select Help About Windows.

¶ Communication protocol: TCP/IP

¶ If there is a UNIX computer on your SAN, you need one of thefollowing: Integraph’s DiskShare, NetManage’s ChameleonUNIX Link 97, FTP Software’s InterDrive, or HummingbirdCommunications NFS Maestro.

Note:

¶ For Windows NT 4.0 and Windows 2000 MDCs,SANergy supports NTFS formatted volumes only,including New Technology File System (NTFS) softwarestripe sets. SANergy does not currently support NTFSmirroring, software RAID (parity), or volume expansion.

¶ Windows shared volumes must be formatted using theNTFS with Windows NT or Windows 2000.


2.O

verview

¶ Windows NT 4.0 and Windows 2000 support MicrosoftCluster Server (MSCS) failover.

Sun Solaris SystemA Sun Solaris system requires the following hardware and software:

¶ Machine: SPARC systems only


v RAM: 128 MB

v Disk space: 20 MB

¶ Operating system: Solaris version 2.6, 7, or 8.

¶ Sun Solaris NFS installed and operational

¶ Netscape with JavaScript support

¶ Communication protocol: TCP/IP, which comes standard withSun Solaris

Note: For Sun Solaris MDCs, SANergy supports UFS and QFSformatted volumes.

Linux (Red Hat)A Linux system requires the following hardware and software:

¶ Machine: X86 based PC architecture (for example 486) and later


v RAM: 128 MB

v Disk space: 20 MB

¶ Operating system: Linux RedHat 6.2

v Linux kernel 2.2.x

v glibc 2.1.x

v libstdc++ 2.9.x

v X Windows System X11R6 (for end-user GUI only)

¶ NFS installed and operational



¶ Samba, if being used as an MDC to support Windows andMacintosh hosts. Samba is included with Redhat 6.2.

¶ Communication Protocol - TCP/IP, which comes standard withLinux.

SGI IRIX UNIX SystemAn SGI IRIX UNIX system requires the following hardware andsoftware:

¶ Machine: O2, Octane


v RAM: 128 MB

v Disk space: 20 MB

¶ Operating system: IRIX UNIX Release 6.5

¶ ONC3/NFS version 2 or 3 installed and operational (found onthe SGI operating system disks)

¶ The X Windows System X11R6


¶ Communication protocol: TCP/IP, which comes standard withIRIX UNIX.

Compaq Tru64 UNIX SystemA Compaq Tru64 UNIX system requires the following hardware andsoftware:

¶ Machine model: Alpha systems.


v RAM: 128 MB

v Disk space: 20 MB

¶ Operating system: Alpha Tru64 UNIX version 4.0F.

¶ Netscape with JavaScript support.


2.O

verview

¶ Communication protocol: TCP/IP, which comes standard withTru64 UNIX.

IBM AIX SystemAn AIX system requires the following hardware and software:

¶ Machine: RS/6000 system


v RAM: 128 MB

v Disk space: 20 MB

¶ Operating system: AIX version 4.3.2 with PTF FC 4.33.0, or4.3.3


¶ Communication protocol: TCP/IP, which comes standard withAIX

Data General DG/UX SystemEnsure that you contact your local DG reseller to obtain the specialDG revision before installing Tivoli SANergy.

A DG/UX system requires the following hardware and software:

¶ Machine: Model Intel X86 system

¶ Minimum memory and space requirement to run:

v RAM: 128 MB

v Disk space: 20 MB

¶ Operating system: Version R4.20MU05 (plus patch forLD_PRELOAD)


¶ Communication Protocol: TCP/IP, which comes standard withDG/UX.

Apple Macintosh SystemAn Apple Macintosh system requires the following hardware andsoftware:


¶ Machine: PowerPC series systems with PCI bus.


v RAM: 32 MB, in addition to the memory required by otherapplications

v Disk space: 20 MB

¶ Operating system: Macintosh Operating System version 8.6, or9.0. All Macintosh systems on the SAN must be running thesame version of Mac OS.

To determine which version of Mac OS you have and how muchmemory is installed on your system, go to the Apple menu andselect About This Computer.

Network RequirementsSANergy network requirements are:

¶ Access to the World Wide Web for software updates (athttp://www.tivoli.com/storage).

¶ You must have at least one MDC on your SAN. The MDC canbe a Windows, Solaris, or Linux (Red Hat) operating system.

¶ SAN: All computers must be attached directly to the storage youwant to share. The computers must attach not just by IP, but alsoby a SCSI-type connection, which includes SCSI, SSA, or FibreChannel.

¶ MAPPING: You must have each computer map, or mount, theMeta Data Controller volume. This requires general networkinghardware and software (for example, TCP/IP on Ethernet)installed and configured.

With Windows, use conventional Windows networking andsharing.

With UNIX computers (Solaris, Linux, SGI, Tru64, AIX, orDG-UX), use NFS. You will need an NFS server for yourWindows MDC computer. The NFS servers are InterDrive, NFSMaestro, DiskShare, or Chameleon UNIX Link 97.


2.O

verview

On a UNIX MDC that will have Windows and/or Mac hostsattached, you must install Samba.

CompatibilityWhen Tivoli SANergy is installed on a SAN, the SANergy codemust be at the same current release level (V2.2) or one release prior(V2.1) on all machines on which it is installed. However, Macintoshsystems are an exception. Within a SAN, if SANergy V2.2 forWindows or UNIX is installed, you must run SANergy V2.2 on theMac OS systems.

When the High Availability option for SANergy V2.2 is installed, allsystems running SANergy must have V2.2 installed.


Windows Installation andConfiguration

NoteCheck the README file, located on your SANergy CD, forcurrent changes before installing and configuring your system.

You might have to configure a variety of computers to share storagein your SAN. In general, it is best to configure a single computer ata time and build up the workgroup.

Device OwnershipSANergy 2.2 has added the Device Ownership feature to provideincreased security for SANs running mixed Windows and UNIXMDCs. Before you start installing SANergy, you must decide whichcomputer or computers you want to assign as owners of yourdevices. In this version of SANergy, the owner of a device is theonly computer that can change the configuration of drives using DiskAdministrator. Thus, if you want to delete, partition, or stripe drives,you must be assigned as the Device Owner in SANergy. The MDCstill has the capability to format drives, and functions the same as ithas in previous SANergy versions. If you are not using UNIXsystems in your SAN, the following setups are recommended foryour Windows SAN.

3


3.W

ind

ow

sIn

stallation

¶ Assign one computer as the Device Owner so that theadministrative function of configuring devices is only availablefrom a single computer. You can assign the same computer, ordifferent computers to be the MDC of various volumes.

OR

¶ Decide which computers are to be the MDCs and assign theDevice Ownership to match the Volume Assignment for theMDCs.

Note: Important: With Device Ownership, you own a whole device(or disk) within your storage. So, if volumes are stripedacross several devices, the computer you use for striping mustown all of these devices.

Windows MDC Setup ProcedureYou should fully configure just one computer at a time (bothhardware and software).

Start by configuring the Meta Data Controller (MDC) computersfirst. Do one at a time. You can set up a single MDC for allvolumes, or you can spread the MDC task among several Windowscomputers. From the MDC computer, use regular Windows tools toformat your storage. If security and access control are important,configure the necessary parameters on that computer. If youanticipate needing UNIX computers to share those volumes,configure your Windows NFS server on the Windows MDC at thistime.

Later, you can mix MDC types (Windows and UNIX) on a givenSAN. However, for each disk, the entire disk must be one filesystem format or the other (either Windows or UNIX).

See the README file, Known Issues section for currentconfiguration information.


Setting Up the First MDCUse the following steps for the first MDC on Windows:

1. Power off all other computers.

2. Configure the LAN adapter and set up networking.

3. Configure the storage adapter.

4. Install the storage hub and drives.

5. Reboot the computer.

6. Set up partition and volume configuration.

7. Install SANergy.

8. Set up volume sharing.

9. Install an NFS server on the MDC (optional).

A detailed description of these steps follows.

To add other MDCs or hosts, see the related chapters.

Step 1: Power off all other computersPower off all additional computers, except for the first WindowsMDC computer.

Step 2: Configure the LAN adapterBefore you configure your computers for networking, verify that youhave the correct network adapter, cable, and any other necessarynetwork hardware. Install your network adapter by following themanufacturers’ instructions. Configure your systems for networkingby following the Windows documentation or the Windows onlinehelp.

Windows NT Network Setup

Follow these steps for network setup:

1. Select Start -> Settings -> Control Panel.

2. Double-click on the Network icon. If your network is not set upyet, the Setup wizard appears on your screen.


3.W

ind

ow

sIn

stallation

3. Follow the instructions on the Setup wizard to set up yourcomputers for use in a network.

4. Type in a valid TCP/IP address and subnet mask (for example,255.255.255.0). If you are using a corporate LAN and thiscomputer has not yet been on an IP network, you might have tocheck with your network administrator for a proper address andsubnet mask. If this is a new setup, you might choose anyfour-number address group you want (for example, 192.168.0.1).Check with your network administrator for the proper number.

5. Select Enable to enable the network bindings and click on Nexttwice to start the network.

6. Type in a unique name for your Windows computer and aworkgroup name. The default name is Workgroup. Check withyour network administrator for the workgroup name.

Note: Each computer using SANergy must have a unique name.SANergy uses the name to identify the workstation withinthe workgroup. Enter the name from the network setupprogram under Identification.

7. Select the appropriate network services and click Next.

8. Reboot your computer. Your computer is now ready fornetworking.

Windows 2000 Network Setup

To set up networking on Windows 2000 systems, refer to theWindows 2000 operating system documentation or use the onlinehelp that is available.

Step 3: Install and Configure the Storage AdapterThe computer must be attached to the storage technology. Typicaltechnologies include SCSI, SSA, and FC-AL (FibreChannel-Arbitrated Loop). These technologies require a specialadapter card and special drivers for the computer. Refer to thehardware documentation for installation information.


Step 4: Install the Storage Switch and DrivesConnect the computer to the drive system or systems. Typically youmust have an additional piece of hardware between the computer andstorage units, called a switch or hub. (This is not the same as anethernet switch or hub.) Not all technologies require a switch or hub;sometimes with only two or three workstations, you do not need one.Consult with your storage or adapter reseller for more information ifneeded.

Step 5: Reboot the ComputerReboot the computer. Make sure the computer boots up properly anddoes not display hardware or software error messages. If thecomputer does not boot up properly, refer to your manufacturer’sdocumentation. Make sure that the new hardware or software worksaccording to the manufacturer’s documentation.

Step 6: Set Up Partition and Volume ConfigurationAt this point, the MDC must be able to see the actual disk systems.You now need to decide the best way to configure the storage formaximum benefit.

¶ Which computers do you want to assign as the Device Ownersto have device configuration control?

¶ How many volumes do you want?

¶ How do you want to stripe it (if at all)?

¶ Which computers do you want to use as the MDCs and forwhich volumes?

Remember that a device owner is a computer that owns the entiredevice (or disk) within your storage.

Remember that a volume is a logical disk to your computer. Avolume might in fact be smaller than a single disk, or it might spanseveral disks. It is a good idea to create many volumes. The morevolumes you have, the more flexible your volume sharing can be.Spend the time at this point to plan your disk access.


3.W

ind

ow

sIn

stallation

Windows Disk Administrator is a powerful tool and needs to beprotected by your system administrators. Otherwise, it is possible forthe user to reformat drives and destroy data on the shared storage.Set up your partition and volume configuration by following theWindows documentation or the online help.

Note: Refer to the Readme file for any volume configurationlimitations.

Windows NT Partition and Volume ConfigurationProcedure

Use the following procedure to use Disk Administrator onWindows NT.

1. Click Start -> Programs -> Administrative Tools -> DiskAdministrator.

2. Select the first free space or partition of the Shared Volumes.Do not select any local volumes (for example, your hard drive).

3. Click the right mouse button.

4. Select Create Partition, label it, assign a drive letter, and formatit as an NTFS volume.

5. Create additional partitions, name them, assign drive letters, andformat them.

CautionWhen formatting a new partition or stripe group, you mustuse the NTFS file system and assign a volume label at thistime. If you do not, the volumes will not be managed bySANergy and will be corrupted. We specifically do notmanage unnamed volumes because the key to our controlsystem is based on volume names.

Note: If SANergy is running on your computer and you add avolume, the label appears as Unknown. This label will


persist until you bring up the SANergy Setup tool andassign an MDC for the created volume.

6. Reboot the workstation. Be sure you can view the createdvolumes.

Capturing Striping Information (Windows NT Only)If your workgroup has additional Windows computers that access thestriped drives, you must capture the striping information. Use thefollowing steps:

1. From Disk Administrator, select File -> Configuration -> Saveto save the striping information onto a diskette.

2. On the next Windows computer, insert the diskette. From DiskAdministrator, select File -> Configuration -> Restore to copythe striping information to this computer.

CautionDo not change the partition or striping information when thereare host systems that are mapped to the volumes. You risklosing data on those volumes.

Windows 2000 Partition and Volume ConfigurationProcedure

To configure your partitions and volumes on Windows 2000, refer tothe Windows 2000 operating system documentation or use the onlinehelp that is available.

Step 7: Install SANergyBefore installing SANergy, make sure that all your hardware isfunctioning properly and you have configured the computer fornetworking. SANergy will not work unless your computer isproperly configured. To install SANergy, use the following steps:

1. At the first MDC, close all programs and insert the CD-ROMinto the CD-ROM drive.


3.W

ind

ow

sIn

stallation

2. The SANergy Setup window appears.

3. Click Next. The Software License Agreement window appears.

4. Read the Software License Agreement window and click Yesto accept the license agreement. The Filter Driver Warningwindow appears.

5. Click Next and the Choose Destination Location windowappears. The default destination folder is C:\ProgramFiles\SANergy\SANergyFS.

Figure 2. SANergy Setup Window


6. Click Next. The Select Program Folder window appears. Thedefault program folder is Tivoli SANergy.

Figure 3. Choose Destination Location Window


3.W

ind

ow

sIn

stallation

7. Click Next. The User Information window appears. Type inyour name and company name.

Figure 4. Select Program Folder Window


8. Click Next. The Select Components window appears. You canenable or disable the installation of the following componentsby clicking on the check box next to the component:

Program FilesInstalls all necessary files for the SANergy software towork. The default setting is Enabled.

SNMP featureInstalls all necessary files to use the SANergy SNMPfeature. If Simple Network Management Protocol(SNMP) is not installed at this time, you need toreinstall this software. The default setting is Disabled.

Docs Installs the Tivoli SANergy Administrator’s Guide inHTML format to the location where you installed theSANergy software. The default setting is Enabled.

The location is: C:\ProgramFiles\SANergy\SANergyFS\docs. Click on the fileOpenBook.htm.

Figure 5. User Information Window


3.W

ind

ow

sIn

stallation

9. Click Next. The Start Copying Files window appears.

10. Click Next. SANergy software is now being copied to thedestination directory. Once the installation is complete, theSetup Complete window appears.

11. Click Finish. The Select Managed Buses window appears.

Figure 6. Select Components Window


12. Click on the bus name connected to the shared storage in theBuses field. Select only the bus that is shared.

13. Click Change. The Managed field is updated to Y to indicatethat SANergy now manages the bus. If this is an upgradeinstallation, the bus will come up already managed.

14. Click Next. The Device Assignment window appears. Bydefault, the first computer is the present owner of all devices.

Figure 7. Select Managed Buses Window


3.W

ind

ow

sIn

stallation

To change the current computer as the owner of one or moredevices, click on the device(s) and select Assign Owner. Typein the new owner name and click OK.

For more detailed instructions on how to use DeviceAssignment, see “Using the Device Assignment Dialog” onpage 42.

15. Click Next. The Volume Assignment window appears. Bydefault, the first MDC is the present owner of all volumes.

To change the MDC owner, click on the desired volume labeland select Assign Owner. Then type in the new MDC owner ofthe volume and click OK.

Figure 8. Device Assignment Window


Note: The MDC owner can be any Windows computer in yourSAN that has SANergy installed.

16. When the configuration is complete, click Finish. The SANergySetup Tool prompts you to restart your system. Click OK. Yourcomputer will automatically reboot.

Note: If you want to make configuration changes afterinstallation, use the SANergy configuration tools. See“SANergy Setup Tool” on page 38. The configurationtools allow you to manage the bus, assign device owners,and assign MDCs to volumes.

Figure 9. Volume Assignment Window


3.W

ind

ow

sIn

stallation

Step 8: Set Up Volume SharingYou need to set up volume sharing on the MDC for all volumes inyour SAN environment. You might need your Windowsdocumentation for additional instructions.

Windows NT Volume Sharing Setup Procedure

To set up volume sharing, use the following steps for Windows NT:

1. From the My Computer window, right-click on the sharedvolume.

2. Select Sharing, then click on Shared As.

3. Click Apply, then click New Share.

4. Type in the shared volume name.

5. Click Apply, then click OK.

The drive now has a blue sharing hand, indicating that it is shared.Now your host computers can map to the shared volumes andreceive fused access.

Windows 2000 Volume Sharing Setup Procedure

To set up volume sharing, use the following steps for Windows2000:

1. From the My Computer window, right-click on the volume thatyou want to share.

2. Select Sharing, then click Share this folder.

3. From the Share name field, type the shared volume name.

4. (Optional). From the Comment field, type SANergy.

5. Click Apply, then click OK.

The drive now has a blue sharing hand, indicating that it is shared.

Step 9: Install NFS Server on the Windows MDC (Optional)If you are adding a UNIX system to your SAN, you must install theNFS Server. We recommend using one of the following:


¶ Hummingbird NFS Maestro

¶ Integraph DiskShare

¶ NetManage Chameleon UNIX Link 97

¶ FTP Software InterDrive

See the product documentation for installation and setup instructions.

Windows Host Setup ProcedureMDC computers can also be hosts. They can access their own MDCvolumes as well as other volumes that are served by different MDCcomputers. The Windows computer can be strictly a host, an MDC,or both.

At Windows boot time, volumes that are part of the shared storageare mounted only on the computer that is the MDC for that volume.Managed volumes on the MDC appear as regular Windows attacheddisks that you can use as desired.

To set up a Windows host that needs access to volumes managed byan MDC, use the following steps:

1. Set up and configure the Windows MDC computers. See“Windows MDC Setup Procedure” on page 20.

2. Configure the LAN adapter.

3. Install and configure the storage adapter.

4. Connect the cables to the SAN workgroup.

5. Reboot your computer.

6. Install the SANergy software and reboot the computer.

7. For Windows NT only: If the volumes are part of a stripegroup, you must insert the disk where you saved the volumeconfiguration setup. Then perform the restore function in DiskAdministrator and reboot your computer.

8. Use regular Windows networking tools to mount the desiredMDC volume.


3.W

ind

ow

sIn

stallation

The SANergy File System driver automatically acceleratestransactions to that volume.

If you have trouble using Windows’ general networking, see yoursystem administrator. If you are in a small workgroup situation, usethe following list as a simple guide to get you started with Windowsnetworking:

¶ Each computer needs to have the same configuration ofusernames and passwords. You can use the Administratoraccount without any password on all computers.

¶ The target volume that needs to be mapped must be a sharedvolume. Follow the steps given in “Step 8: Set Up VolumeSharing” on page 34. See your Windows documentation if youneed additional instructions.

¶ Windows NT Network Mapping Procedure: On the hostcomputers, map the remote volume. Do one of the following:

v Open Explorer. Click on the Map Network Drive icon inthe Explorer toolbar, locate the MDC name, and double-clickon the volume.

v From the command prompt, enter the following command:net use z: \\<mdc-computer-name>\<share-name>

If you want to mount to drive letter z, your MDC name isProduction, and the volume on that computer is F: (thedefault share name is F$). Enter the following:

net use z: \\Production\F$

Now you can use z: as a regular volume with improvedperformance. You can mount additional drives to other driveletters.


¶ Windows 2000 Network Mapping Procedure: To map avolume using Windows 2000, use the following steps:

1. From the My Computer icon, click Tools\Map NetworkDrive. The Map Network Drive window appears.

2. From the Drive field, select the drive letter you want to usefor the shared volume.

3. Click on Browse. Locate the MDC system and the volumeyou want to map.

4. Click OK, then click Finish.

The My Computer window updates the mapped drive icon andthe drive letter specified.

¶ Alternate Windows 2000 Network Mapping Procedure: Thereis a similar procedure in Windows 2000 that you can use to mapto folders. If you do this, you do not need drive names and arenot limited to the 26 drive letters. To do this:

1. Click the Network Places icon.

2. Select Add Network Place.

3. A wizard appears, and you can map the folder. Click OK,then Next, and you can then rename the mapped folder ifyou wish.

4. Click Finish, and the mapped folder icon will appear onNetwork Places.


3.W

ind

ow

sIn

stallation

SANergy Setup ToolThe SANergy Setup Tool lets you set up your shared storage forfile-level access of all shared volumes. The SANergy Setup Tool isrun from the Start menu. It lets you display a list of all knownsystem buses, device owners, and volume assignments, provides avolume performance testing tool, and controls caching.

To access the tool, select Start -> Programs ->Tivoli SANergy ->SANergyFS Setup Tool. The SANergy Setup Tool displays thePerformance Tester dialog.


Using the Performance Tester DialogUse the following steps to perform read and write tests on the sharedvolumes.

1. Click on the Performance Tester tab. The Performance Testerdialog displays.

2. From the Drive field, click on the shared volume you want torun the test on.

3. Select the desired test to run (Write or Read). You need toperform a Write test before you can perform a Read test.

Figure 10. Performance Tester Dialog


3.W

ind

ow

sIn

stallation

4. You can change the File name, File size, and Record size, ifnecessary.

5. (Optional). Click on the Loop check box. The Loop feature letsyou run the performance test continuously.

6. Click on the Start Test button to begin the performance test onthe selected drive.

The bottom of the window is updated with the results of theWrite/Read test. The Clear Stats button clears the fused statistics atthe bottom right of the window.

Using the Select Managed Buses DialogUse the following steps to view or make changes to the shared busconfiguration.

1. Click on the Select Managed Buses tab.

2. Power off all host computers.


3. In the Buses field, click on the shared bus to be managed, orunmanaged.

4. Click on the Change button. The Managed field is updatedaccordingly.

CautionBe sure to power off all host computers before changing themanagement of shared buses.

Figure 11. Select Managed Buses Dialog


3.W

ind

ow

sIn

stallation

Using the Device Assignment DialogUse the following steps to assign or change device ownership.

1. Click on the Device Assignment tab. All devices are displayed.

2. Highlight a device and click on Tag Device. A window appearsso you can assign a Tag (name) to each device. You can use thisfunction to label the devices for identification on othercomputers.

Note: You can use the Touch Device function to visuallyidentify your devices. Highlight the device you want to

Figure 12. Device Assignment


locate and click Touch Device. The access light on yourdevice will start blinking. This function works as a toggleso it will continue blinking until you click Untouch.Touch Device does not work with hardware RAIDcontroller drives.

3. To assign an owner to one or more devices, highlight thedevice(s) and click Assign Owner. A dialog opens which has thename of your computer as Owner by default. You can either:

¶ Click OK.

¶ Change the name of the Owner to another computer.

Note: You can type any text in this field, so if you areassigning a different computer, make sure you type inthe name exactly. If it is not exact, the computer willnot really be the owner. It is safest to assign deviceowners from the machine you want to own the device.

4. To clear the computer you are currently using as a device owner,highlight the device and click Remove Owner. The Owner fieldupdates to blank.

Note: You cannot remove another different computer on theSAN as Owner unless that system is offline.

5. If you add or remove any devices, click Rescan to update thedisplay.


3.W

ind

ow

sIn

stallation

Using the Volume Assignment DialogTo assign or remove a computer as an MDC, you must use thatcomputer to make these changes. The only time you can removeanother computer as an MDC is when that system is shut down. Usethe following steps to assign or change volume ownership.

1. Click on the Volume Assignment tab. All shared volumes andtheir owners display. If the Meta Data Controller field isblank, then the volume has no owner.

2. Give users ample warning that you will be changing volumeownership.

3. All host computers must:

¶ Close all applications that use the fused volume that ischanging ownership.

¶ Delete all network mappings to that volume.


4. From the computer that is the MDC, click on the volume that ischanging ownership and select Assign Owner. The ChangeMeta Data Controller window is displayed.

5. Highlight and delete the present owner’s name and select OK.The Confirmation window is displayed.

6. Click on the Yes button. The Volume Assignment dialogupdates the MDC field for that volume to blank.

7. Go to the new MDC and click Start -> Programs ->TivoliSANergy -> SANergyFS Setup Tool. The SANergy Setupwindow is displayed.

Figure 13. Volume Assignment Dialog


3.W

ind

ow

sIn

stallation

8. Click on the Volume Assignment tab. The Volume Assignmentdialog appears, displaying all shared volumes and their owners.

9. Click on the volume where you want to gain ownership andselect Assign Owner. The Change Meta Data Controllerwindow is displayed. By default, the present computer’s nameappears in the window as the MDC name.

10. Click OK. The Volume Assignment dialog is updated with thenew MDC name.

11. On the new MDC, set up volume sharing for that volume. See“Step 8: Set Up Volume Sharing” on page 34.

12. Re-establish any host mappings, if necessary. If you receive aTagging Volume error message, make sure all hosts have closedall applications to that volume, then repeat the procedure.

The SAN workgroup is now ready for use.

Note: If you are presently mapped to a volume that changed MDCsand you have not removed the mapping, SANergy displays amessage. Remove the mapped volume to the old MDC, thenremap the volume to the new MDC.

Using the Options DialogThe Options dialog lets you control the SANergy options forWindows hosts. It has no effect on other hosts or MDCs.

To change options, click on the Options tab. The Options dialog isdisplayed. Your options are discussed in the following pages.

Make the necessary changes, then click on Apply. Changes takeeffect immediately. Changes also persist between reboots.

Note: These changes can have significant effects on performance.Only make changes if you understand the consequencesthoroughly, or are guided by a SANergy supportrepresentative.


Figure 14. Options Dialog


3.W

ind

ow

sIn

stallation

You can change the following options:

Fusion Exclusion ListTells SANergy which files to exclude from acceleration.Enter a list of wild-card file names that are separated bysemicolons, for example:*.mov;*.db

This list prevents SANergy from fusing any file with theextensions .mov or .db. Use this option only if youencounter an application incompatible with SANergy. Thisoption is not often used.

Hyperextension Exclusion ListTells SANergy which file to exclude from hyperextension.When SANergy writes to a file, and the file needs to growto hold more data, SANergy hyperextends the file size. Thefile size increases in large chunks. This is useful for mosttypes of file, and imperative for real-time video files. Enter alist of wild-card file names that are separated by semicolons,for example:*.mov;*.db

This list prevents SANergy from hyperextending any filewith the extension .mov or .db. Use this option only if youencounter files that do not benefit from hyperextension. Thisoption is not often used.

Hyperextension SizeTells SANergy the amount to increase the file forhyperextension. 100 MB is a good typical value, usuallygiving only one hyperextension every few seconds for afast-growing video file. You might want to choose a smallervalue for other files, although SANergy makeshyperextensions very quickly.

Enable AVID-NTEnables special processing for volumes that are used withAVID-NT software.


Minimum Fused File SizeTells SANergy the minimum size of a file to accelerate.Some very small files have more metadata than data. Inthose cases, SANergy is less advantageous than regularnetworking. This only affects files that are opened for readand not write access.

Retry Tells SANergy what to do when storage connectivity is lost.You can set the amount of time (in seconds) to keep tryingto reconnect, and set the appropriate action when time is up.The timeout modes are:

¶ Over LAN: The transfer continues over the LAN.

¶ Report Error: The transfer stops, and SANergy reportsan error to the running application.

¶ Disable SAN: The SAN is disabled immediately,allowing LAN transfers to continue. When fibre accessis corrected, reboot your computer to receive fusedaccess.

Cache SettingsNT hosts can perform some file caching. You can selectamong the following modes:

¶ Disabled: No caching takes place. All transactions godirectly to the storage medium.

¶ Read: Only files opened for read-only mode, withoutsharing, can be cached.

¶ Read/Write: The same as read, but also for files withwrite and read-write access, with no sharing.

¶ Aggressive: Cache even those files tagged for writesharing, with any access. This is risky, since SANergydoes not ensure cache coherency for this mode. Use thismode only if you know that your application poses norisk. Note that non-buffered transactions are nevercached, so these settings do not apply.


3.W

ind

ow

sIn

stallation

Cache Exclusion ListTells SANergy which files to exclude from caching. Enter alist of wild-card file names that are separated by semicolons.Note the following example:*.mov;*.db

This list prevents SANergy from caching any file with theextensions .mov or .db.

Cache Line SizeTells SANergy how many lines of cache to give each file.

Cache MemoryTells SANergy how much memory to use for file caches.This memory is non-paged-pool memory.

Using the About DialogThe About dialog shows you the SANergy version number.


Uninstalling SANergy on Windows Systems

WarningOnly uninstall SANergy if you are disconnected from the SANnetwork. This assures that there is no risk of data loss that isordinarily protected by SANergy.

To uninstall SANergy, use the following steps:

1. Select Start -> Settings -> Control Panel

2. Double-click on the Add/Remove Programs icon.

3. From the Install/Uninstall tab, click on SANergy.

4. Click on Add/Remove.

5. Select Yes to uninstall the SANergy software.

6. Follow the instructions on the screen until the uninstall processsuccessfully completes.



3.W

ind

ow

sIn

stallation


UNIX Installation andConfiguration

NoteCheck the README file, located on your SANergy CD, forcurrent changes before installing and configuring your system.

You might have to configure a variety of computers to share storagein your SAN. In general, it is best to configure a single computer ata time and build up the workgroup.

Most UNIX systems can be host computers in a SANergy network,but Solaris and Linux systems can be MDCs as well as hosts. AllUNIX computers need to have a direct SAN connection (forexample, Fibre Channel) and could need some sort ofWindows-to-UNIX LAN networking technology, usually NetworkFile System (NFS). You only need NFS if you are using Windowssystems on your SAN.

To configure UNIX systems to work with SANergy, use thefollowing steps:

1. Set up and configure the MDC computers (Windows, Solaris, orLinux). See “Windows MDC Setup Procedure” on page 20 or“Linux and Solaris MDC Setup Procedure” on page 60.

2. Install and configure your UNIX-to-Windows LAN software andhardware, or both, if necessary.

4


4.U

NIX

Installatio

n

3. Install your SAN hardware and drivers on the UNIX system.

4. Mount the NFS volumes. Make sure that the NFS volumesmount properly and without errors. Test the mounts for desireduser access. If the NFS volumes do not mount properly, see yourNFS documentation or your product manufacturer.

5. Install Netscape. You must have a windows system such asX-window running. Netscape must be available to run theSANergy Configuration Tool.

Note: If Netscape is not available on your computer, you mustuse the SANergyconfig program. See “Using theSANergyconfig Program” on page 78 for additionalinformation.

6. Install and configure SANergy on the UNIX system.

Device OwnershipSANergy 2.2 has added the Device Ownership feature to provideincreased security for SANs running mixed Windows and UNIXdevices. Before you start installing SANergy, you must decide whichcomputer or computers you want to assign as owners of yourdevices. In this version of SANergy, the owner of a device is theonly computer that can change the configuration of drives. Thus, ifyou want to delete, partition, or stripe drives, you must be assignedas the Device Owner in SANergy.

For UNIX platforms, the Device Ownership has been combined withthe MDC function. For Solaris and Linux (the only UNIX systemscapable of fulfilling the MDC function), if you own a device, youare the MDC by default. For other UNIX systems, you can owndevices, but you will not be the MDC. The main reason for anon-MDC computer (SGI, Tru64, AIX, or DG-UX) to own a deviceis to protect it and keep it apart from shared access within SANergy.If you are going to mix UNIX and Windows systems on your SAN,make sure you read “Windows Installation and Configuration” onpage 19 before you start installing SANergy.


UNIX to Windows Networking (LAN Connection)On the Windows MDCs, install the NFS server software (or otherUNIX-to-Windows networking software) and configure it for use bythe UNIX computers. This procedure can vary. See thedocumentation with your networking product. You also need aphysical networking connection (for example, Ethernet) between theWindows and the UNIX computer, although some FCimplementations support conventional networking such as InternetProtocol (IP) over FC.

Experiment with the networking connection to be sure that it worksproperly. Note that performance will be that of a regular LANnetwork until SANergy is enabled. Continue only if you areconfident of the NFS connectivity from the UNIX computer to theMDC. Check for read and write permissions.

SAN ConnectionInstall an FC adapter and the associated drivers, wiring, and hubs.SANergy does not offer any acceleration unless it can correctlyaccess the SAN elements. Pay close attention to all the informationprovided by the SAN adapter manufacturer.

Once you have installed the adapter and verified that the UNIXcomputer can access the storage elements reliably, install SANergy.We recommend that you run a disk exerciser that verifiesperformance and the integrity of the data.

Mount the NFS VolumesSANergy works with networking products such as NFS. Itaccelerates network transactions by intercepting them and reissuingthem over the faster storage area network when possible. SANergyneeds to know about the association of a network mount point andthe equivalent hard mount point of the storage elements. Refer toyour NFS documentation for the specifics on how to mount networkvolumes successfully. Make sure that the NFS volumes mountproperly and without errors. Test the volume mounts for desired user


4.U

NIX

Installatio

n

access. If the NFS volumes do not mount properly, see your NFSdocumentation or product manufacturer.

We recommend using the following options for NFS mounting:Mount -o acregmin=0,acregmax=0,actimeo=0 host:/share/mnt

Otherwise, NFS gets confused by SANergy writing beneath it.

Installing SANergy on UNIX SystemsThis section describes how to install SANergy on all UNIX systemsincluding the Solaris or Linux MDC and all hosts.

First mount the NFS volumes, then run Netscape, and then install theSANergy software. See your NFS and networking documentation forthe specifics on how to mount network volumes.

Note: If you are upgrading your SANergy software, the installerwill prompt you to uninstall before it runs the install script.

Solaris users:

Before installing SANergy, be sure that your maximum sharedmemory is set to 4 MB or greater. To change it, do the following:

1. Open the file /etc/system.

2. Add the line:set shmsys:shminfo_shmmax=0x400000

and Save.

3. Reboot the computer:reboot

AIX users:

Before installing SANergy, be sure to change the Asynchronous I/Osetting from Defined to Available. To change it, enter the following:

/smit/devices/asynchronous IO


Change the status to Available.

Procedure for Installing SANergy

To install SANergy, use the following steps:

1. Locate and mount the CD–ROM in the CD–ROM drive.

2. From a UNIX shell, change the directory to the CD–ROMdrive.

3. From the CD–ROM mount point, enter:cd unix_sanergyfs/

4. From the unix_sanergyfs mount point, enter:./install

5. A confirmation window displays the UNIX operating systemthat was detected. Enter yes. The install script will prompt youto enter the package you want to install. Enter the packagenumber and answer the following questions. The SANergysoftware is now being installed to the /opt (Solaris) or /usr (allother UNIX) directory on your system. When the installcompletes, the SANergy Configuration Tool displays theLicense Agreement window.

Note: If Netscape fails to run at this point, you could need touse the SANergyconfig program. For more informationon SANergyconfig, see “Using the SANergyconfigProgram” on page 78.

6. Read the License Agreement. You need to scroll down to readthe entire License Agreement.

7. Click Accept. The SANergy Configuration Tool appears. TheSANergy Configuration Tool updates the list of the NFSmounted volumes, SANergy statistics, and general information.For additional information, see “SANergy UNIX ConfigurationTool and SANergyconfig Program” on page 63 or click on theHelp button in the Control panel.


4.U

NIX

Installatio

n

8. From the Fused Mount field, enable the desired volume to fuseby clicking in the check box next to the fused mount point.

Figure 15. SANergy UNIX Configuration Tool Window


9. Click Set. Fused access is now available for that volume.Confirm volume fusing by using the Performance Tester. See“The Performance Tester Panel” on page 68.

10. You must do the following to set the key environment variablefor acceleration to occur. For each UNIX window you start, setthe accelerated environment by running one of the following:

¶ For csh and tcsh shells, enter the following:

v For Solaris:# source /opt/SANergy/SANergycshsetup

v For all other UNIX:# source /usr/SANergy/SANergycshsetup

Or you can add the line above to your/(user_directory)/.profile file.

¶ For sh and ksh shells, enter the following:

v For Solaris:# . /opt/SANergy/SANergyshsetup

v For all other UNIX# . /usr/SANergy/SANergyshsetup

Figure 16. Fuse Panel


4.U

NIX

Installatio

n

Linux and Solaris MDC Setup ProcedureYou might have to configure a variety of computers to share storagein your SAN. In general, it is best to configure a single computer ata time and build up the workgroup.

Start by configuring the MDC computers first. Do one at a time. Youcan set up a single MDC for all volumes, or you can spread theMDC task among several computers. If security and access controlare important, configure the necessary parameters on that computer.

Presently, you can mix MDC types on a given SAN. However, on aper-disk basis, the entire disk must be one file system format or theother (either Windows or UNIX). Separate file systems on a disk canhave different MDC owners. UNIX–to–UNIX SANergy users willsee little difference from using a Windows system as the MDC.

See the README file Known Issues section for the currentconfiguration information.

If you are going to include Windows and/or Macintosh computers ashosts with your UNIX MDCs, you must install a CIFS package, suchas Samba, on your MDCs to create shares. You must create NFSshares that match the names of the CIFS shares, otherwise they willnot fuse. In addition, the UNIX MDC must start Samba from anaccelerated window in order to have fused access to the volumes.This is not necessary for Windows hosts.


To configure a Solaris or Linux system as an MDC:

1. Create the file systems on the shared storage. Partition andformat your storage elements. Refer to your UNIXdocumentation for information on how to format disks.

2. Install the SANergy software. See “Installing SANergy on UNIXSystems” on page 56.

3. From the Configuration Tool’s Fuse Panel field, click onOwnership. The Device Ownership window replaces the FusedPanel field and displays all known disks.

Note: To remove a computer as a Device Owner you must usethe computer that owns the device. The only time you canremove another computer as an MDC is when that systemis shut down.

4. Click on the device that you want the computer you are using toown and click Change, then click Go.

5. The name of the computer you are using is the default nameentered as the owner. You can assign a Tag (name) to the device

Figure 17. SANergy Device Ownership


4.U

NIX

Installatio

n

if you want to label the device for identification on othercomputers. You can type any text in this field, so if you areassigning a different computer as Device Owner, make sure youtype in the name exactly. If it is not exact, the computer will notreally be the owner. It is safest to assign device owners from thecomputer you want to own the device.

Note: You can use the Touch Device function to visuallyidentify your devices. Click Touch Device and the accesslight on your device will blink for approximately 20seconds. Touch Device does not work with hardwareRAID controller devices.

6. Click Set!. The Owner name updates to the current computername and the Tag field updates if you entered a Tag.

7. (Optional). Repeat steps 1 through 4 on all devices that you wantthe MDC to own.

8. To return to the Fuse Panel, click on Fuse panel.

Note: If the UNIX MDCs are supporting Mac or Windows hosts,you need to install a CIFS package like Samba.

Note: In the current version of SANergy, the Device Ownershipfunction has been combined with the MDC function. If aSolaris or Linux system owns a device, it is the MDC bydefault. If you assign another type of UNIX system as DeviceOwner, there is no MDC, so the device cannot be sharedwithin SANergy. Only the computer that owns it can accessthis storage.

UFS Hyper-AllocationWhen creating files from a host system, SANergy attempts tooptimize the metadata regarding extending the file. It does this byoverextending a file, and shrinking it once the file is closed.Currently, UNIX UFS MDCs must write zeros to newly allocateddisk blocks. If those blocks are not entirely used, then the process ofwriting zeros wastes time. We suggest that you trim yourhyper-allocation values to smaller numbers. The default value is 10megabytes. Depending on your application, you might need to adjust


the hyper-allocation value in either the SANergy UNIXConfiguration Tool or the SANergyconfig program. For moreinformation, see “Using the SANergy UNIX Configuration Tool” onpage 64 or “Using the SANergyconfig Program” on page 78.

SANergy UNIX Configuration Tool andSANergyconfig Program

There are two ways to set up your shared storage for file-levelaccess of all shared volumes.

¶ SANergy UNIX Configuration Tool: This is the HTML-basedGUI interface and is the preferred method.

¶ SANergyconfig program: This is the command line interface.

The following sections describe how to use the SANergy UNIXConfiguration Tool and the SANergyconfig program.


4.U

NIX

Installatio

n

Using the SANergy UNIX Configuration ToolThe SANergy UNIX Configuration Tool is an HTML-based userinterface for configuring and monitoring the system. This toolrequires a browser (for example, Netscape or Internet Explorer) to beinstalled on the system. This tool does not require a Web server. Thistool provides GUI–based mechanisms for setting and observingsystem status.

To run the SANergy UNIX Configuration Tool:

1. Locate the SANergy directory. Type:

¶ For Solaris:/opt/SANergy/config

¶ For all other UNIX:/usr/SANergy/config

2. This will run the configuration script. You could need to edit thescript to appropriately find Netscape. The SANergy UNIXConfiguration Tool appears.


Figure 18. SANergy UNIX Configuration Tool Window


4.U

NIX

Installatio

n

The SANergy UNIX Configuration Tool window consists of thefollowing group boxes:

Fuse Displays the currently mounted volumes in the system. Thisgroup box lets you:

¶ Run performance tests

¶ View and change ownership of the volumes

¶ Display the disks that are present in the devices directory

¶ Display the status of a device that is considered open

¶ Open a SANergy fused terminal window

Performance StatisticsLets you view the amount of reads and writes on allmounted volumes. On Linux and Solaris, lets you accessZOOM functionality.

GeneralLets you change general configuration settings.

Cache Lets you change the settings for the SANergy CacheManager.

ControlApplies the changes made or restores the default settings tothe General and the Cache panels.

The Fuse PanelThis panel shows all of the currently mounted NFS volumes in thesystem. The left column, Fused, indicates whether the particularvolume is currently in a SANergy fused state. Fuse means thatSANergy attempts to accelerate transactions to that volume.


The Fuse panel consists of the following:

Fused You can enable or disable any volume. Press Set! at anytime to have that change take effect.

MountDisplays the name of the system mount points.

ServerDisplays the owner of the mounted device.

Perf TestsLinks you to a panel that lets you test the performance ofany mounted file system (NFS and local volumes).

Xterm(All UNIX except AIX) Brings up a SANergy fused terminalwindow.

OwnershipDisplays the disks that are present in the devices directoryand the status of a device that is considered open. You canconfigure disk ownership.

Note: If you don’t own disks, you will not see them whenyou issue the format command.

Help Displays online help.

Figure 19. The Fuse Panel


4.U

NIX

Installatio

n

To fuse a volume:

1. Click on the check box next to the volume name. A checked ordepressed box indicates that the volume is selected. Otherwise,the volume is not selected. You can select multiple volumes atthe same time.

2. Press Set!. You now have fused access to that volume. You canselect multiple volumes to fuse.

3. Continue with the remaining volumes to fuse.

The Performance Tester PanelThis panel allows running two simple tests on a specified volume todetermine how fast that volume reads and writes data. When testinga SANergy host volume, you will see the Fused value changeaccordingly on the Statistics panel.

To use the Performance Tester, do the following:

1. From the Fuse panel, click on Perf Tests. The PerformanceTester panel displays.

2. From the Select Volume field, highlight the mount point of thevolume you want to test.

Figure 20. The Performance Tester Panel


3. Click Write. The Performance Statistics panel is updated. Youmust do a write test first for a data file to be present for the readtest.

4. Click Read. The Performance Statistics panel is updated.

Note: The test runs for a predetermined amount of elapsed time(10 seconds) and then reports the results.

5. Click on Clear to clear the current values to zero. The statisticswill continually update as you move files across the SAN. Tostop this, click on Refresh Off. You can manually update thestatistics from this panel by clicking on Update. Click onRefresh ON to display continually updated statistics.

By default, the SANergy statistics are updated automatically. Toturn off automatic updating, click on the Refresh OFF button.When automatic updating is turned off, the following SANergyStatistics window appears.

Figure 21. The SANergy Statistics Window, Refresh ON


4.U

NIX

Installatio

n

Use this panel to determine how statistics will display.

Clear Clears the fused statistics and resets them to zero.

Refresh ONTurns on automatic updating for the fused statistics.

UpdateLets you view an update of the statistics to check fusedperformance after you have performed an operation.

Using ZOOM Stats

¶ To set up the ZOOM feature that improves small file readperformance, see “ZOOM Setup” on page 168.

¶ To check ZOOM statistics, click ZOOM Stats.

¶ The ZOOM Statistics window appears. See “Displaying ZOOMStatistics” on page 75. For more information on ZOOM, see“Enhancing Small File Operations” on page 159.

The Device Ownership PanelUse this panel to display and change ownership of various devices.The select box displays hard-mounted volumes that are available forthe ownership list.

Figure 22. The SANergy Statistics Window, Refresh OFF


From the current owner’s computer, you can select a device and thenselect to either clear the current owner or set this system as theowner. You will not be able to clear another owner if that system isonline. You can only clear yourself as an owner, or a system that isoffline.

See “Linux and Solaris MDC Setup Procedure” on page 60 fordetailed information.

The General Settings PanelThis panel shows various general configuration parameters that canbe useful. Make the desired changes and then click on the Applybutton. Use Cancel to undo any changes that have not yet beencommitted. Use Defaults to return to the original settings.

The General Settings consist of the following:

TracingSpecifies the internal diagnostic reporting level. This valueshould be set to 0 (the default) unless you are specificallyinstructed by a SANergy support person to change it.Tracing consists of several levels, which are as follows:

¶ 0: tracing is turned off.

¶ Levels 1–5: this results in a small amount of file tracinginformation to be presented to the log file.

¶ Level High: this results in a large amount of traceinformation.

Figure 23. The General Settings Panel


4.U

NIX

Installatio

n

To view the trace information, click on Event Log.

Event LogThe Event Log shows errors and is useful for debugging.

Hyper-extend valueSpecifies the value that indicates how much a file should beover allocated while growing. By over-allocating a file, it islikely that the SANergy host will not have to go back to theMDC as often to ask for more extents. At file close time,any over-allocation is trimmed. For typical enterprise andoffice applications, this value should be set to less than 10MB. For high-speed streaming video, set this value to 100MB. The units can end in B, K, or M to specify bytes,kilobytes, or megabytes.

ExcludeSpecifies the files to exclude from hyper-extensionoperations. There are certain types of files that might not beworthwhile to hyper-extend (in rare circumstances). Forexample, a .txt file. Be sure to specify the file list as acomma-separated list with only file extensions, such as .txtor .dat.

Fuse ExcludeSpecifies the file extensions to exclude from using SANergy.This is to be used in rare cases, primarily for debugging.

Min ReadSpecifies the minimum file size to include for fused reads.

Figure 24. Event Log


Files smaller than the size set will be read over your regularEthernet. We suggest setting a minimum file size of 10KB.

Min WriteSpecifies the minimum file size to include for fused writes.Files smaller than the size set will be written over yourregular Ethernet. We suggest setting a minimum file size of100KB.


The Cache Settings PanelUse this panel to change the cache settings for the SANergy CacheManager. These settings are preconfigured at the factory. TheStatistics panel shows values that indicate whether or not the cacheis being effective. Make the desired changes and click on the Applybutton. Use Cancel to undo any changes that have not yet beencommitted.

The Cache Settings consist of the following:

Mode Specifies the current overall cache mode. None means thatcaching is disabled. Read means that only files opened forread-only access will be potentially cached. ReadWritemeans that SANergy will cache files that are opened forread-write access.

Line size (KB)Specifies the internal cache setting. The internal cache is aper-file, per-application cache that is broken up into cacheblocks (or lines). Cache block size is specified by the Line

Figure 25. The Cache Settings Panel


4.U

NIX

Installatio

n

size value. A file will have a limited number of linesallocated per file (currently 3) and so it is best to allow thelines to be reasonably large (1 MB or more).

Total process (MB)Specifies the total amount of cache space that will beallocated per process. The Total process value specifies thetotal amount of cache space that will be allocated perprocess no matter how many files are cached. Once thisvalue is reached, the cache manager will run an algorithm(LSU) to start to reclaim space.

ExcludeSpecifies the file extensions to exclude from caching. Theexclusion list is a comma-separated lowercase list of filesthat will not use caching. Examples of these files are .mov,.tmp, and .doc.

#MapsSpecifies the total number of maps that will be stored in themap cache.

There is a separate cache for file metadata and maps. The#Maps item specifies the total number of maps that will bestored in the map cache. If a map is in the cache, then theSANergy host does not have to go back to the MDC for it.Maps time out, as specified by the Seconds field. For someapplications, such as a file manager, that rapidly keepasking for pieces of files (for display and icon purposes), itcan be useful to have this cache active (nonzero number ofmaps). The default is zero, which disables this feature.Another SAN member can change files. Therefore, maps canbe inaccurate if they are not fetched from the MDC eachtime.

SecondsSpecifies the amount of time before a map times out.



The Control PanelUse this panel to apply changes in the General and Cache panels.

Apply Click to apply your changes

CancelClick to clear any changes you have made before clickingapply.

DefaultsRestores default settings.


Displaying ZOOM StatisticsTo set up ZOOM, see “ZOOM Setup” on page 168. The ZOOMstatistics window values are described below. For more informationon ZOOM, see “Enhancing Small File Operations” on page 159.

Figure 26. Control Panel

Figure 27. ZOOM Statistics Window


4.U

NIX

Installatio

n

Files Total number of files being tracked by ZOOM on thiscomputer.

Trees Total number of directory trees being watched by ZOOM onthis computer. Click on Tree/File List to display the ZOOMtree.

MemoryTotal amount of shared memory (in bytes) being consumedby ZOOM on this computer.

Sent MDC side. Total number of file-change messages sent out toZOOM hosts.

PreviouslyMDC side. Number of file-change messages that would havegone out, but will not, because it is already recorded that thismessage has been sent to the target computer (file is alreadytracked as in a ″changed state″).

ChangesMDC side. The total number of system-wide file changesthat have been detected by the ZOOM technology (but notnecessarily within a watched tree).

Hits MDC side. Total number of file changes that have occurredwithin all the watched trees.

Figure 28. ZOOM Tree


AttemptsHost side. Total number of file-opens that have occurredsystem-wide. This value will increase by using the HTMLtool that displays it (as that results in file-opens itself).

ZOOMedHost side. Total number of file-opens that have hit within awatched tree and are allowed to be accelerated (file is not ina changed state).

UnZOOMedHost side. Total number of file-opens that have hit within awatched tree, and are not allowed to be accelerated due tothe file being in a changed state (or a parent directory).

NomapHost side. Number of files that were about to be acceleratedbut there was no NFS read-only mount mapping established.


4.U

NIX

Installatio

n

Using the SANergyconfig ProgramThe SANergyconfig program is a command-line interface that letsyou control SANergy. It runs automatically at boot time.

Note: Tivoli recommends using the SANergy UNIX ConfigurationTool.

If you are not using the SANergy UNIX Configuration Tool, youmust edit SANergyconfig.txt to access the SANergy driver andreceive accelerated performance. SANergyconfig is a program thatprovides important information to SANergy. It runs at each boottime, to configure SANergy. Typically, the configuration informationis stored in the file SANergyconfig.txt. The system start-up routinesspecify this file as input to SANergyconfig.

You must edit SANergyconfig.txt, entering a fuse command foreach NFS mount point. SANergyconfig also has many othercommands that are described in this section.

When you invoke the SANergyconfig program, it displays thecurrent supported commands, syntax, and examples. If you enter aSANergy command without a parameter value, the current settingsdisplay. The following table defines the SANergy commands inalphabetical order.

Table 4. SANergy CommandsSANergyCommand(not casesensitive)

Syntax Description

bus BUS|device,device,... Sets the list of devices to beEXCLUDED from SANergymanagement. ex: BUS|c0,c1

cache cache|[RD RWOFF](|size(kb)|exlist)(default)RW|1024|.mov

Returns the current cache parameters.The exlist is a comma-separatedlower–case list of files that are not tobe cached. Examples are: .mov, .tmp,and .doc.


Table 4. SANergy Commands (continued)SANergyCommand(not casesensitive)

Syntax Description

clear stats clear stats|fusedwrites|fusedreads Clears the fused write and fused readstatistics.

dram DGRAM|5 Sets the number of MDC datagramthreads to 5.

exclude EXCLUDE|(comma separated list ofextensions)

EXCLUDE by itself prints the currentexclusion list.

exit exit Exits the program.

fuse fuse|/nfs1 Connects the volume to aSANergy–managed volume foraccelerated access. The /nfs1 is thelocal mount point.Note: You must be a root user to fusevolumes.

fused fused Displays a list of fused volumes.

get vol get vol|/aaa Gets the volume information.

help help Reprints this message.

hyper hyper|[on,off]|[amount(B,K,M)]|exclusion_list

This sets the hyper-allocation value inbytes (B), kilobytes (K), or megabytes(M). The default is 10 MB. Theexclusion list is a comma-separated,lowercase list of files that will notfuse. These files will use Ethernet.Examples are .mov, .tmp, and .doc.Example: hyper|on|10M

key key|(Tivoli-supplied registration stringvalue)

Supplies the Tivoli-suppliedregistration string value.


4.U

NIX

Installatio

n


Syntax Description

log log|6|file|1|10 Returns the current log state.

0 Disables logging. You shouldonly turn logging on whenyou encounter problems.

6 Enables logging and writesthe mclog0 file to theSANergy directory. This canbe set from 1–6.

1 Indicates the number of logfiles you want to create. Thiscan be set from 1–9.

10 Indicates the log file size.This can be set up to 200K.

map cache map cache|30(secs)|100(maps) Returns the current map cacheparameters.

minfused MINFUSED|read-size|write-size Sets the internal values for minimumfile size to fuse. Currently, only ’read’is implemented. A zero value meansforce all fused.



Syntax Description

owner owner[|slice|system_name or no value] Assigns or releases volumeownership. Also, lists all UNIXMDCs and the volumes they own.

system_nameAssigns volume ownership(becomes the MDC of volumes).

no value enteredReleases volume ownership.

no value enteredDisplays a list of all UNIXMDCs and the volumes theyown.

quit quit Exits the program.

stats stats|fusedwrites|fusedreads Displays the fused write and fusedread statistics.

toggle TOGGLE|device|timeout Vibrates/blinks a disk for a period oftime. TOGGLE|c1t10d0s2|30

unfuse unfuse|/nfs1 Disconnects the volume from aSANergy-managed volume.

ver ver Displays the SANergy versionnumber.

You can run SANergyconfig as a text line application, or you canpass a script file into it. The following procedures describe bothways to use SANergyconfig.

SANergyconfig is a program that allows you to use script files. Touse it, do one of the following:

¶ Pass it a script file. This is the recommended method. Enter thefollowing command:


4.U

NIX

Installatio

n

# ./SANergyconfig < SANergyconfig.txt

¶ Use single commands (text line application) as command linearguments. Enter the following command:

# ./SANergyconfig "KEY | Value"

Passing SANergy a Script File

To pass SANergy a script file, use the following steps:

1. Edit the SANergyconfig.txt script file for your environment.This includes the registration string value and the shared volumesyou want to fuse. To edit the script, enter the followingcommand:

# vi SANergyconfig.txt

or open the file in a text editor.

2. The SANergyconfig.txt window appears. Enter the followingcommands:

FUSE|/nfs1(Other FUSE commands for other shared volumes you want to fuse)EXIT| (end every script file with the EXIT command)

The /nfs1 is the volume name or local mount point.

3. Save and exit the SANergyconfig.txt script file.

4. Enter the following:# ./(usr or opt)/SANergy/SANergyconfig<SANergyconfig.txt


Using Single Commands

To run a text line application, use the fuse command. This tellsSANergy which logical mount points are to be accelerated, and whatthe associated physical device or devices are.

1. Enter:(usr or opt)/SANergy/SANergyconfig

The Enter Command: prompt appears.

2. Enter:# FUSE|/nfs_mount_point

The nfs_mount_point parameter is the local mount point that youspecified when you issued the NFS mount command.

Pay close attention to any output generated by the fuse command.There are many reasons why the command might fail. If it fails, noacceleration takes place.

Log FilesThe SANergy driver periodically writes important information to alog file called mclogn.txt (n=0–6) which is stored in the SANergyinstall directory (which varies by platform). You can change thefile/directory name with a SANergyconfig command. Check this filefor any accumulating messages. The log file will reset after reachingthe maximum size. You can also turn on the tracing information(using the SANergyconfig program) which writes to this file. Youcan use this to determine how some programs are running in theSANergy environment.


4.U

NIX

Installatio

n

Uninstalling SANergy on All UNIX Computers

Note: Only uninstall SANergy if you are disconnected from theSAN network. This assures that there is no risk of data lossthat is ordinarily protected by SANergy. Before uninstalling,make sure that you are not in the SANergy directory.

To uninstall SANergy on UNIX computers, use the following steps:

1. Bring up the UNIX shell and log in as the superuser. Enter:# su rootPassword: <root_password>

Enter your password at the prompt.

2. Remove all references to SANergy from the .profile and .loginfiles, if you edited them.

3. Do one of the following:

¶ For Solaris, enter the following:# /opt/SANergy/uninstall

¶ For all other UNIX, enter the following:# /usr/SANergy/uninstall


Macintosh Installation andConfiguration

NoteCheck the README file on the CD-ROM for current changesbefore installing and configuring your system.

Setting Up the Macintosh Network EnvironmentMacintosh PowerMac models come complete with a 10BaseTEthernet connection ready to use.

1. Select Apple/Control Panels/TCP IP.

2. Select Connect via Ethernet.

3. Select Configure Manually.

4. Type in a valid TCP/IP address and subnet mask (for example,255.255.255.0). If you are using a corporate LAN and thiscomputer has not yet been on an IP network, check with yournetwork administrator for a proper address. If this is a new setup,you can choose any four number address group you want (forexample, 192.168.0.1). Make sure each machine on the networkhas a different address.

5. Leave all other fields in the Control Panels blank.

6. Close the Control Panels and save the changes.

5


5.M

acinto

shIn

stallation

and

Co

nfig

uratio

n

SANergy InstallationMacintosh computers can only be hosts in a SANergy network. Toset up your Macintosh host, use the following steps:

1. Set up and configure the Meta Data Controller (MDC)computers first. See “Windows Installation and Configuration”on page 19 or “UNIX Installation and Configuration” on

page 53.

2. Connect the cables (fibre channel and Ethernet) to the SANworkgroup.

3. Power up one Macintosh computer.

4. Configure your Macintosh for the storage adapter (FC, SCSI,SSA).

5. Exit all running applications.

6. Remove the SANergy dongle if it was installed with a previousversion of SANergy.

7. Disconnect from any SANergy volumes by dragging the iconsto the trash can.

8. Insert the CD-ROM in the CD-ROM drive. The SANergy 2.2CD-ROM window appears.

9. Double-click on the SANergy Installer icon. The SANergysplash screen appears.

10. Click on Continue. The SANergy License Agreement windowappears.

11. Read and acknowledge the License Agreement and click on theAccept button to accept the license agreement. The Read Mewindow appears.

12. Review the Read Me window for current changes and clickContinue. The SANergy Installer window appears.

13. Click on Install. If you have any applications open, a warningmessage appears.

14. Click on Continue to automatically quit any applications, orclick Cancel to exit the installation process. If you select


Continue, the installer will start copying files to your harddrive. When the installation finishes, you receive a Successwindow.

Notes:

a. If this is an upgrade installation, messages appear to removeour DAVE client and NetBIOS files. It is important toremove both of these files to enable SANergy to functionproperly. Click OK for both messages.

b. If you are installing on OS 9.0 or above, a message appearsregarding Auto-Mounting. In order to enable auto-mountingof volumes, you need to use the Multiple Users function. Ifyou do not currently have Multiple Users on, selectApple/Control Panels/Multiple Users. The Multiple UsersControl Panel appears. Select the On radio button to enablethis function. For more information on this control panel,see the Mac OS 9 documentation.

15. Select Restart. Your computer automatically reboots.

NetBIOS 2.5.3 Setup

Note: If you are upgrading from an earlier version of SANergy, skipthese steps and go to Mount SANergy Volumes on page 90.

1. Select Apple/Control Panels/NetBIOS. The NetBIOS 2.5.3Setup Introduction window appears.

2. Click on the right arrow to go to the Help With TCP/IPSettings panel.

3. Select the radio button for TCP/IP is already configured.

Note: If your TCP/IP settings are not already configured, seeyour Network Administrator.

4. Click on the right arrow to go to the Choosing Your NetworkType panel.

5. Select the Yes radio button if a Windows NT Server is beingused on your network. If there is no Windows NT Server, or ifyou are not sure, select the No radio button.


5.M

acinto

shIn

stallation

and

Co

nfig

uratio

n

6. Click on the right arrow to go to the Choosing a NetBIOSName panel.

7. Type in a name for your computer to be identified as on thenetwork. You may choose any name, but it must be unique.

8. Click on the right arrow to go to the Setting Your Workgrouppanel.

9. Enter the name of the Workgroup used by the Windowscomputers on your network. If you are not sure of the name,ask your Network Administrator.

Figure 29. Choosing a NetBIOS Name


10. Click on the right arrow to go to the Choosing a DescriptionFor Your Computer panel.

11. If you wish, you can enter a description of your computerwhich will be used to identify it to PC users NetworkNeighborhood windows. You can leave this field blank.

12. Click on the right arrow to go to the Review Settings panel.

13. Check the settings as they appear in this panel. If you wish tochange a setting, use the left arrows to go back to theappropriate panel.

14. You could see a Sharing Local Files window at this point.Choose to share or not and select Continue.

15. Click on the right arrow to go to the Setup Complete panel.

Figure 30. Setting Your Workgroup


5.M

acinto

shIn

stallation

and

Co

nfig

uratio

n

16. This is the final panel of the DAVE Setup process.IMPORTANT: Click on the OK button to complete thesetup process. DO NOT click on the right arrow.

17. Reboot your machine. You must reboot at this time or you willget a NetBIOS error message when you try to mount SANergyvolumes.

.

Mount SANergy Volumes

1. Select Apple/Chooser. The Chooser window appears with theSANergy 2.2 icon in the left window.

2. Click on the SANergy 2.2 icon. The Chooser window displaysthe list of all known servers.

Figure 31. Setup Complete


3. Select the server which is the MDC of the volume you want tomount and click OK. The Connect to Server window appears.

4. Type in your User name and Password to get access to the MDCcomputer. The Share window displays the MDC name in theupper-left corner and all known volume and folder shares in thecenter window.

5. Click on the desired volume or folder to share, then select OK.The share now mounts to your desktop. The mount-point on theMacintosh should be blue; this means that it is fused. If it is notblue, the Macintosh was unable to see all the physical disks thatit needs. You will be running at Ethernet speeds.

6. Repeat steps 3 to 5 to mount additional shared volumes.

Figure 32. Connect to Server


5.M

acinto

shIn

stallation

and

Co

nfig

uratio

n

Displaying the SANergy StatisticsTo see the amount of data fused, go to the Control Strip and clickon the SAN cloud icon. The SANergy Statistics window appears onthe desktop temporarily.

The SANergy Statistics window displays:

¶ Amount of data fused for reads and writes.

¶ Amount of data that is transferred by network for reads andwrites. Some number of transactions is normal.

¶ The Clear option, which lets you clear the fused and networktransactions to zero.

Uninstalling the SANergy Software

WarningOnly uninstall SANergy if you are disconnected from the SANnetwork. This assures that there is no risk of data loss that isordinarily protected by SANergy.

To uninstall SANergy on a Macintosh, use the following steps:

1. Insert the CD-ROM in the CD-ROM drive. The SANergy 2.2CD-ROM window appears.

2. Double-click on the SANergy Installer icon. The SANergyinstallation window appears.

3. Click on Continue. The SANergy License Agreement windowappears.

Figure 33. SANergy Statistics Window


4. Read and acknowledge the license agreement and click on theAccept button. The Read Me window appears.

5. Click on Continue. The SANergy Installer window appears.

6. From the Easy Install field (located in the upper-left corner ofthe window), click on the down arrow and select Uninstall.

7. Click on the Uninstall button. A warning message appears; youmust not have any other applications running.

8. Click Continue. The SANergy components are removed fromyour computer and a success window appears.

9. Click OK, then click Quit to close the SANergy installerwindow.


Figure 34. Uninstall


5.M

acinto

shIn

stallation

and

Co

nfig

uratio

n


Managing SANergy

This chapter describes how to make changes to the management ofhosts, volumes, and MDCs in your SANergy environment.

Adding Host ComputersUse the following steps to add more host computers to yourSANergy environment.

1. Follow the instructions given in the chapter for the kind of hostyou are adding. See

¶ “Windows Installation and Configuration” on page 19

¶ “UNIX Installation and Configuration” on page 53

¶ “Macintosh Installation and Configuration” on page 85

2. Fuse the host to the MDC.

Removing Host ComputersUse the following steps to remove host computers from yourSANergy environment.

1. Disconnect the cables from the SAN to the workgroup.

2. Uninstall SANergy. Follow the instructions given in the chapterfor the kind of host you are removing.

3. Power off the computer.

6


6.M

anag

ing

SA

Nerg

y

Adding VolumesUse the following steps to add volumes to your SANergyenvironment. Only the Device Owner can perform this function.

1. Give users ample warning that you are adding a volume.

2. Notify users that you will be shutting down the workgroup toperform maintenance.

3. Shut down all hosts except the one you will use to add thevolume.

4. From SANergy, take device ownership of all affected volumeson the SAN.

5. Close the SANergy setup tool.

6. From Disk Administrator, create the new volume and give it alabel.

7. Exit Disk Administrator.

8. Reboot the system.

9. Upon power up, SANergy displays a message that a volumedoes not have an owner.

10. Take ownership of the new volume and put a share on it.

11. Power up the hosts one at a time.

Deleting VolumesUse the following steps to delete volumes from your SANergyenvironment. Only the Device Owner can perform this function.

1. Give users ample warning that you are deleting a volume.


3. Shut down all hosts except the one you will use to delete thevolume.

4. From SANergy, take device ownership of the volume you wantto delete.



6. From Disk Administrator, delete the volume.

7. Exit Disk Administrator.

8. Shut down and restart the system.

9. Power up hosts one at a time.

Renaming VolumesUse the following steps to rename your volumes in your SANergyenvironment. Only the MDC can perform this function.

1. Give users ample warning that you are renaming a volume.


3. Shut down all hosts except the one you will use to rename avolume.

4. From SANergy, take MDC ownership of the volume you wantto rename.


6. Rename the volume by selecting it in My Computer window,right-clicking on the volume, and selecting Properties.

7. In the Label field, type the new name and close the window.

8. If necessary, delete the old share name and add the new sharename to the new volume.

9. Restart the system.

10. Power up the hosts one at a time.


6.M

anag

ing

SA

Nerg

y

Repartitioning VolumesUse the following steps to repartition the drives in your SANergyenvironment. Only the Device Owner can perform this function.

1. Give users ample warning that you will be repartitioning yourvolumes.

2. On the host computers, delete all network mappings to allvolumes.

3. Notify users that you will be shutting down the SAN to performmaintenance.

4. Shut down all computers except the computer you will use torepartition the drives.

5. Take device ownership of all volumes owned by other Windowssystems.

6. Use Disk Administrator to repartition your drives. See “Step 6:Set Up Partition and Volume Configuration” on page 23.

Note: If SANergy is running, the volume label displays asUnknown until you bring up the SANergy Setup Tool andassign an owner to the volume.

7. Reboot the computer.

8. Run the SANergy Setup tool to assign an MDC.

9. If you are re-striping volumes, do one of the following for eachof the other computers:

WindowsRestart the next computer, following the procedure in“Windows Installation and Configuration” on page 19.

UNIX Restart the next computer, following the procedurein“UNIX Installation and Configuration” on page 53.

MacintoshRestart the next computer, following the procedure in“Macintosh Installation and Configuration” on page 85.


Changing the MDC OwnershipUse the following steps to change the MDC ownership of a volumein your SANergy environment.

1. Give users ample warning that you will be changing volumeownership. All host computers must:

¶ Close all applications to the fused volume that is changingownership.

¶ Delete all network mappings to that volume.

2. From the present MDC, click Start->Programs->TivoliSANergy->SANergyFS Setup Tool. The SANergy Setupwindow appears.

3. Click on the Volume Assignment tab. The Volume Assignmentfolder appears, displaying all shared volumes and their owners.

4. Click on the volume where you want to change ownership andselect Assign Owner. The Change Meta Data Controllerwindow appears.

5. Highlight and delete the present owner’s name and select OK.The Are You Sure confirmation window appears.

6. Click on the Yes button. The Volume Assignment windowupdates the MDC field for that volume to blank. Go to the newMDC and repeat steps 3 to 5. By default, the present MDCnames appear in the Change Meta Data Controller window.Click OK. The Volume Assignment window updates with thenew MDC name.

7. On the new MDC, select sharing on that volume from the MyComputer window. See “Step 8: Set Up Volume Sharing” onpage 34.

8. Re-establish any host mappings if necessary. If you receive aTagging Volume error message, make sure that all hosts haveclosed all applications to that volume and repeat this procedure.

Note: If you are presently mapped to a volume that changedMDCs and have not removed the old mapping, SANergy


6.M

anag

ing

SA

Nerg

y

displays a message. Remove the mapped volume to theold MDC, then map to the new MDC.


Troubleshooting

This chapter lists problems you could encounter with SANergy andthe steps to recover from them. Follow all the steps that match yoursituation. If you still have problems, please contact Tivoli TechnicalSupport at 1-800-TIVOLI8. Please have information about yourproblem and your system configuration ready.

For Windows systems, please furnish the following, wheneverpossible:

¶ Event log

¶ Windows diagnostic system information

¶ Reproducibility procedure

¶ Screen captures of error messages

The SANergy Web-support site for assistance, updates, and reportingissues is:http://www.tivoli.com/storage

To speed up assistance, include a written report with all pertinentinformation (including the SANergy version number, hardwareconfiguration, and applications that are being used).

7


7.Tro

ub

lesho

otin

g

Meta Data ControllersThis section provides solutions to MDC problems with volumes.

Data Volumes

Table 5. MDC Data Volumes Problems and RecoveryProblem Recovery

Not seeing all expecteddrives in DiskAdministrator

Hung SAN/Restart Necessary. You couldhave SAN fabric issues, such as hung drivesor towers, hung FC hubs, bad or wrongadapter firmware. Often, a reboot of theWindows computer corrects this. However,you could need to power-cycle all hardwareelements.

Windows drives do notshow up in the MyComputer Window(continued on next page)

¶ No Name/Label. The partitions were notgiven a name when created andformatted. Check in Disk Administrator.

¶ No Drive Letter. The partitions were notgiven a drive letter when created andformatted. Check in Disk Administrator.

¶ Drives Not Detected. The drives are notpresent or have failed. Run the ControlPanel/SCSI utility. Check for drivesavailable that are connected to theadapter. If no drives are present, recheckthe SAN hardware components, orcontact your reseller or vendorimmediately if the hardware failed.

¶ Not the Device Owner. The machine isnot the machine that striped the drives,and it needs to have the disk stripeinformation updated. Save diskinformation to a floppy disk from theDisk Administrator of the Device Ownerthat created the stripe. Then restore thisinformation on all Windows hostcomputers that need to access the storagearea network drives.


Table 5. MDC Data Volumes Problems andRecovery (continued)Problem Recovery

Windows drives do notshow up in the MyComputer Window(continued)

(continued)

¶ Wrong Adapter Version. The adapterdriver is the wrong version for thefirmware on the adapter card. Consultyour adapter’s product manual ordownload the latest revision from thevendor’s Web site and install it. If it isfabric, be sure you have thefabric-capable driver and firmware for thehost bus adapter (HBA).

¶ Failed LIP. The SAN hardware has had afailed Loop Initialization Protocol (LIP)attempt. Check the adapters, switches,hubs, and other hardware for error lightsor hung operating systems on hosts.Restart and reboot hosts and attachedhardware. Note any system error logmessages for support. Contact yourvendor or reseller immediately if theproblem persists.

Windows Lost DelayedWrite Message

FC Error. This message indicates a hardware(Fibre Channel) error. This happens when thehost bus adapters are not compatible withother HBAs on the SAN or LoopInitialization Protocol conditions.


7.Tro

ub

lesho

otin

g

Windows SystemsThis section provides solutions to problems with Windows Systemson Installation, Volumes, and Performance.

InstallationTable 6. Windows Systems Installation Problems andRecoveryProblem Recovery

Cannot install or reinstallthe SANergy software.

There are two possibilities:

¶ Not Administrator. You are not loggedin to your Windows host withadministrator rights. Only administratorscan install SANergy on anon-administrator computer.

¶ Did not Reboot. You did not reboot yourcomputer after uninstalling the SANergysoftware. Failing to reboot results in apartial installation. If that happens, usethe following steps:

1. Go to the registry and delete:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mcfsand

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SANergysrv


3. Try the installation again.


Volumes

Table 7. Windows Systems Volumes Problems and RecoveryProblem Recovery

Not seeing all expecteddrives in DiskAdministrator.

Hung SAN. You could have SAN fabricissues, such as hung drives or towers, hungFC hubs, bad or wrong adapter firmware.Often, a reboot of the Windows computercorrects this. However, you might need topower-cycle all hardware elements.

Windows drives do notshow up in the MyComputer Window(continued on next page).

¶ No Name. The partitions were not givena name when created and formatted.Check in Disk Administrator. Thepartitions were not given a drive letterwhen created and formatted. Check inDisk Administrator.

¶ Drive Detection. The drives are notpresent or have failed. Run the ControlPanel/SCSI utility. Check for drives thatare connected to the adapter. If no drivesare present, recheck the SAN hardwarecomponents, or contact your reseller orvendor immediately if the hardwarefailed.

¶ Not the Device Owner. The machine isnot the machine that striped the drives,and it needs to have the disk stripeinformation updated. Save diskinformation to a floppy disk from theDisk Administrator of the Device Ownerthat created the stripe. Then restore thisinformation on all Windows hostcomputers that need to access the StorageArea Network drives.


7.Tro

ub

lesho

otin

g

Table 7. Windows Systems Volumes Problems andRecovery (continued)Problem Recovery

Windows drives do notshow up in the MyComputer window(continued).

(continued)

¶ Wrong Adapter Version. The adapterdriver is the wrong version for thefirmware on the adapter card. Consultyour adapter’s product manual ordownload the latest revision from thevendor’s Web site and install it. If it isfabric, be sure you have thefabric-capable driver and firmware for theHBA.

¶ Failed LIP. The SAN hardware has had afailed Loop Initialization Protocol (LIP)attempt. Check the adapters, switches,hubs, and other hardware for error lightsor hung operating systems on hosts.Restart and reboot hosts and attachedhardware. Note any system error logmessages for support. Contact yourvendor or re-seller immediately if theproblem persists.



Host computers cannotmap or fuse to a volume.

There are two possible causes:

¶ Sharing not Setup. Check your MDC tosee if volume sharing is set up. If not, usethe following steps:

1. Go to the My Computer window.

2. Right-mouse click on the volume youwant to share.

3. Select Sharing/New Share.

4. Type the shared name volume.

5. Click on OK.

6. Select Apply.

7. Click on OK.

Now your host computers can map to theshared volumes on the MDC.

¶ Drive Detection. Run SCSI Scan tomake sure that the drives are present.

Cannot see volume labelsor file system informationin Disk Administrator

Not the MDC. This computer is not theMDC for the volumes. You can see that thevolume is part of a stripe group, but not seethe actual file system type. Use one of theSANergy configuration tools to view volumelabels.

Changed the stripinginformation and otherWindows systems do notacknowledge it.

Save Disk Striping. You must perform thesave operation in Disk Administrator on theDevice Owner and then restore on all otherWindows (only) systems.


7.Tro

ub

lesho

otin

g


In Disk Administrator,you do not see a diskentry for every physicaldisk in your SAN.

Drive Detection. The Windows computerdoes not sense the drives. SANergy has noway of preventing drives from beingacknowledged by the Disk Administrator. Ifyou do not see your drives, then somehardware/firmware configuration element isnot correct. See your product documentation.


Performance

Table 8. Windows Host Performance ProblemsProblem Recovery

Not seeing improvedaccess performance.

¶ Not Fusing. The first step is to determineif SANergy is doing any fusing. InWindows only: run the SANergy SetupTool from the Start menu and select thePerformance Tester tab. Note thenumbers, and then do a transaction.

¶ Numbers Change, but PerformanceOff. If the numbers change as expected,but still the performance seems slow,contact Tivoli Technical Support at1-800-TIVOLI8. Please have allinformation regarding your hardware,software, and event log messages relatingto this issue so that the supportrepresentative can log your problemaccurately. The performance problemmight be limited to extremely small filesor activities that count only on certaincaching modes.

¶ Numbers Unchanged. If the numbers donot change, then no fusing is takingplace. The bus or volumes might not beset up correctly, or the computer mightnot see the local (FC) access point for thestorage. Run Disk Administrator toconfirm visibility of the drives. You mightneed to restore striping information onthis system.


7.Tro

ub

lesho

otin

g

UNIX SystemsThis section provides solutions to problems with UNIX Systemsvolumes and performance.

Volumes

Table 9. UNIX Systems Volumes ProblemsProblem Recovery

Hosts cannot map or fuseto a volume.

Error message:

Drive Signature Not Found

¶ Check the HTML SANergyConfiguration Tool. Check the HTMLSANergy Configuration Tool for loginformation.

¶ Sharing not Set Up. Check your MDCto see if volume sharing was set up. Ifnot, use the following steps:




4. Select Apply.

5. Click on OK.

Now your host computers can map to theshared volumes on the MDC.Note: Be sure to set the Windowsvolume shares, or NFS Export points, tothe drive letter; SANergy does notsupport mount points above that.

¶ Privileges and Configuration. Checkyour Network File System (NFS) shareprivileges and configuration, and yourWindows system.


Table 9. UNIX Systems Volumes Problems (continued)Problem Recovery

The fused windowdisplays errors (AIX only).

Asynchronous IO. The Asynchronous IOsetting needs to be changed from Defined toAvailable. Do one of the following:

¶ Run the aixsetup script provided duringthe SANergy installation and reboot thesystem. See “Installing SANergy onUNIX Systems” on page 56.

¶ Use the following steps:

1. From a UNIX shell, type smit andpress Enter.

2. Click on Devices/AsynchronousIO/Change/Show Characteristics ofAsynchronous IO.

3. Change the STATE to Be Configuredat System Restart field to Available.

4. Reboot the system.


7.Tro

ub

lesho

otin

g

Performance

Table 10. UNIX Systems Performance ProblemsProblem Recovery

Not seeing improvedaccess performance.

¶ Not Fusing. Determine whether SANergyis fusing volumes by running the HTMLSANergy statistics tool. From Netscape,enter:

/(pathname)/SANergyStats.html

Note the numbers, then do a transaction.

¶ The Numbers Change, butPerformance is Off. If the numberschange as expected, but performance stillseems unimproved, contact TivoliTechnical Support at 1-800-TIVOLI8.Please have all information regardingyour hardware, software, and event logmessages relating to this issue so that thesupport representative can log yourproblem accurately. The performanceproblem might be limited to extremelysmall files or activities that count only oncertain caching modes.

¶ Check Bus. If the numbers do notchange, then no fusing is taking place.The bus or volumes might not be set upcorrectly, or the computer might not seethe local (FC) access point for thestorage.


UNIX Systems Frequently Asked QuestionsThese are frequently asked questions which can aid introubleshooting SANergy on UNIX systems.

Basic ConfigurationHow do I get into an accelerated state?

You must have the proper environment variables setup inyour process environment. You can source theSANergycshsetup script that resides in the SANergyinstallation directory, if you are running a C-like variant. Oryou can source the SANergyshsetup script if you arerunning a more traditional shell. You can place these scriptsin your .login (or similar) startup location, and even in thesystem startup scripts, if needed. If the SANergyenvironment variables are not set, then you will not haveaccelerated performance.

How do I know if am in a fused window?You must execute one of the supplied SANergy setup scriptsthat configures one or two environment variables. Thevariables are either LD_PRELOAD or _RLD_LISTdepending on your UNIX system. You can issue env | grep-i sanergy to inspect various environment variables that havethe SAN keyword in them.

Is there an error log somewhere?There is an error log that is maintained by the systemper-boot session (it is stored in either /usr/sanergy or/opt/sanergy and dissolves every boot). This configurationtool allows you to examine the current contents of the logfile. Various internal SANergy errors are periodically writtenout to this file. If you set the logging level to somethingother than Off, many diagnostic messages will be written(possibly so many that performance will be compromised).

Should I change any of the configuration settings?Typically you should not change any of the configurationsettings. After careful use and consulting with a SANergyexpert, you might decide that it is useful to decrease thehyper-allocation value or alter some of the cache settings.


7.Tro

ub

lesho

otin

g

Why do I get can’t find libc.a(aio.o) functions (in AIX)?You must run smit and turn on asynchronous I/O.

Can I use a UNIX volume manager?SANergy supports a very limited set of volume managerscurrently. Call your reseller for specific information.

How do I get customer support for SANergy?First, call your reseller. If your reseller is unable to assistyou directly, call Tivoli Technical Support at1-800-TIVOLI8. Please have information about yourproblem and your system configuration ready.

The SANergy Web-support site for assistance, updates, andreporting issues is:http://www.tivoli.com/storage

Volume ConfigurationHow do I see the SAN storage from this system?

Only the SANergy MDC system is allowed to hard-mountthe storage. So, SANergy Host machines must use LANnetworking to gain access. If everything is correctlyconfigured, they will have the same performance as an MDC(by virtue of the SAN fabric connection). You mustremote-mount (via NFS) the volume that you wish to access.Consult your operating system documentation for exportingthe MDC volume and also for mounting it via NFS on theSANergy host.

How do I perform an NFS mount?This can vary greatly from one UNIX variant to another. Thebasic steps are to first export (or share out) a directory orvolume on the MDC machine and then to NFS-mount it onthe host. Consult your operating system documentation fordetails on those operations.

How do I see more volumes on the FUSE panel?The FUSE panel will show all the currently NFS-mountedvolumes in the system. For each of those, it will indicate ifSANergy has been configured to accelerate (or fuse) thatvolume. This is indicated by the check mark on that panel.


You must therefore first perform an NFS mount usingregular UNIX mounting tools. This panel only displaysapproximately 20 volumes.

How can I tell if it is fusing?The easiest and best way to tell if your application is fusingis to run the SANergy UNIX Configuration tool while yourapplication is also running. Then monitor the fused statistics.The panel should be automatically refreshing every fewseconds (and it will probably blink while it does so). If it isnot, click the clear button and this should reactivate it(sometimes a window or panel resize will stop the automaticupdates).

Why do I get Mismatch ID when I attempt a fuse?This means that the local system attempted to find thenecessary disks that that the MDC owns, but could not findthem. This is usually because your system has not beenconfigured correctly with regard to the SAN fabric. Or, itcould be that your hardware adapters didn’t correctly probethe devices at boot time. You might wish to look at theDisks panel to see if your system at least has the expecteddevice entry points configured.

MDC ConfigurationI cannot mount the MDC volume. Why?

You should only be allowed to mount an MDC volume ifyou are the owner of the current machine. If there is noowner or you are not the owner, traditional UNIX mountattempts should fail. This assumes you are running themfrom a window that has the SANergy environment set. Tobecome an MDC, use the Configuration Tool and go into theDevice Ownership panel.

What steps are needed to create an MDC?First, format and label the disk devices (usually you willneed to run the UNIX format command). Then create thefile systems as you wish (use makefs or a similar


7.Tro

ub

lesho

otin

g

command). Finally, go into the Device Ownership panel inthis software and assign a suitable machine to be the MDCfor each file system.

Multiple MachinesI do not see my newly created file from the NFS view. Why?

NFS can cache certain directory and metadata information.Sometimes the creation (or deletion) of a file from onemachine might not be noticed by other machines for 30seconds or longer. Each NFS server can configure thistimeout. Consult your NFS server documentation for details.

Can I mount the same disk on multiple machines?Yes and No. You can only have a single machine as thehard-mount master (called the MDC machine in SANergyterminology). If there is another machine that needs to haveaccess to that volume, you can network it (via NFS) tomount it. If SANergy is properly loaded and configured, thehost systems will have the same performance as the MDC byvirtue of the SAN fabric and SANergy’s acceleration.

Performancedd does not seem accelerated?

On most UNIX platforms, dd is shipped from the OS vendorhard-linked. SANergy can not alter the behavior of ahard-linked program.

How do I tell how fast my drives are?You should know how fast your physical drives are becauseSANergy cannot make them any faster than the speed anative system can access them. There is a performance testpanel built into this tool that you should use to measureperformance. If you are on an MDC of a volume, select thehard mount point (that is, /mnt/mydisk) and perform both awrite and a read test. If you are on a SANergy host system,select the NFS mount point and perform the same tests. Youshould get similar values. For the most part, the values


reported are the most optimistic ones possible (that is, thetest uses very large I/O blocks); real application results canvary.

My applications do not seem to be running faster.There are two typical reasons why applications do not runfaster with SANergy.

¶ The first is by far the most common; you have notconfigured the system correctly and so SANergy is notfusing.

¶ In the second case, fusing is occurring, but performanceis poor. This can sometimes happen with applicationsthat count on particular caching optimizations that mightnot be yet implemented in SANergy. Examine the cachestatistics and consider altering some of the cachingvariables if you know that your application is trying tomake use of caching.


7.Tro

ub

lesho

otin

g

Macintosh HostsThis section provides solutions to problems with Macintosh hostvolumes and performance.

Volumes

Table 11. Macintosh Host Volumes ProblemsProblem Recovery

Hosts cannot map or fuseto a volume.

¶ Sharing Not Set Up. Check your MDCto see if volume sharing was set up. Ifnot, use the following steps:




4. Select Apply.

5. Click on OK.

Now your host computers can map to theshared volumes on the MDC


Performance

Table 12. Macintosh Host Performance ProblemsProblem Recovery

Not seeing improvedaccess performance(continued on next page)

¶ Check Control Strip. First, make surethat SANergy is fusing volumes byrunning the SANergy statistics tool. Fromthe control strip, click on the SAN icon.Note the numbers, then copy a file to ashared drive.

¶ Numbers Change, but PerformanceOff. If the numbers change as expected,but performance still seems unimproved,contact Tivoli Technical Support at1-800-TIVOLI8. Please have allinformation regarding your hardware,software, and event log messages relatingto this issue so that the supportrepresentative can log your problemaccurately. You will also need to provideyour customer number. The performanceproblem might be limited to extremelysmall files or activities that count only oncertain caching modes.

¶ Check Bus. If the numbers do notchange, then no fusing is taking place.The bus or volumes might not be set upcorrectly, or the computer might not seethe local (FC) access point for thestorage.


7.Tro

ub

lesho

otin

g

Table 12. Macintosh Host Performance Problems (continued)Problem Recovery

Not seeing improvedaccess performance(continued).

(continued)

¶ Check if Blue. Check that the SANergymounted volume is marked blue. If it isnot blue, you have no fused access. Tryto remount the SANergy volume.

¶ Scan Drives. Run SCSI Scan to makesure that the drives are present.

¶ Read-Only Shares. The Macintoshsystem does not fuse read-only shares.


High Availability Feature

The High Availability feature is sold separately as an extension toSANergy. It provides extended availability of storage resources. TheHigh Availability feature ensures that storage is accessible in mostnetwork-aware applications, including mission-critical applicationssuch as databases and transaction processing systems. HighAvailability ensures failovers occur transparently. This layeredapplication eliminates single points of failure within the SAN bymonitoring the computers that control access to storage devices.Should one of these systems fail, a system running the HighAvailability feature takes over its operations.

Note: The High Availability feature is available only on WindowsNT or Windows 2000, or for some UNIX host systems thatuse a Windows system as the MDC.

SANergy and the High Availability FeatureSANergy manages the file metadata by means of an MDC. TheMDC is a computer designated as the keeper of metadata for one ormore file volumes. Should this device fail, the metadata for thatvolume could be unavailable. This in turn could result in loss ofaccess to the volume until the MDC is brought back on line.

The High Availability feature complements SANergy by providinghigh availability of shared storage resources. It accomplishes this bymonitoring the health of the computer (or multiple computers) thatare designated as the MDCs within the SANergy network. In the

8


8.H

igh

Availab

ilityF

eature

event that an MDC fails, the computer running the High Availabilityfeature will automatically detect the failure and take over as theMDC. In most cases, this process occurs transparently toapplications, thus enabling them to proceed without interruption.

The High Availability feature should only be installed on computersthat are already running SANergy. It is currently available onWindows and UNIX host systems. The system requirements for thestandby system include:

¶ Windows systems: must run the same SANergy versions (TivoliSANergy and High Availability) that it is monitoring.

¶ UNIX host systems: only available if using a Windows systemas the MDC.

High Availability Feature Architectural OverviewThis section provides a basic description of the High Availabilityarchitecture and operation.

High Availability Feature System ElementsThere are three principal elements in a High Availability system:

¶ MDC. The SANergy Meta Data Controller system. WithSANergy configurations, you can have any number of MDCsand have each one protected by High Availability.

¶ Standby System. This system can be a host with the addedresponsibility of monitoring any number of MDCs. Or thesystem can be idle, monitoring and waiting to become an MDCof particular volumes. You must load the High Availabilityfeature on all standby systems.

¶ Host. This is a typical SANergy host system.

With SANergy, a given system can be both an MDC of volumes anda host to other volumes. Now, with High Availability, a system canalso be a standby system. Consider the following example:


In the above example,

¶ System NT-A is the MDC of two volumes (Vol-1 and Vol-2).

¶ System NT-B has the High Availability feature installed, and isconfigured to monitor Vol-1 and Vol-2. It is the MDC of Vol-3.

¶ Should system NT-A fail, NT-B automatically takes over allMDC responsibilities of the volumes owned by NT-A (Vol-1 andVol-2). Specifically, NT-B will gain the hard-mount for thevolumes. NT-B will then send messages to all activemapped-hosts (NT-C), and automatically remap volumes to thestandby MDC NT-B. All NT shares (shared volumes) for Vol-1and Vol-2 from NT-A’s perspective are inherited by the standbysystem NT-B. This enables the standby system to correctlyre-share the same volumes.

High Availability Feature System Services andPrivileges

High Availability utilizes two software components, or services, toprovide failover support.

MDC

Guard

MDC

Vol-1

Vol-2

Vol-3

NT-A

NT-B

NT-C

MDC for Vol-1 and Vol-2.Needs high-uptime protection.High Availability not installed.

MDC for Vol-3. High Availability installed; configuredto take over Vol-1 and Vol-2.

Not an MDC for any volume.High Availability not installed.Active "maps" to all volumes.

Figure 35. Using High Availability to Create a Standby System


8.H

igh

Availab

ilityF

eature

¶ The SANergysrv service is part of the SANergy product. It isresponsible for maintaining metadata information about files thatsystems access using SANergy. It must have sufficient privilegesto remove any active SANergy host mappings to the failedMDC, and to reestablish them to the new MDC.

¶ SANergyHA service is provided with the High Availabilityfeature. This service transfers Windows networking sharedvolumes from the failed MDC to a local ghost volume. It musthave sufficient privileges to transfer these shared volumes.

Note: Be sure that both of these services are enabled whenlogging on as a user with a real account. This isnecessary so that the service can perform failoveroperations that require administrator privileges. See“Setting Up Administrative Privileges Before Performingthe High Availability Installation” on page 126.

High Availability Feature System OperationThis section provides a basic description of how High Availabilityoperates.

The base SANergy product stores the MDC name on the targetvolume, allowing all systems to have access to the information.Similarly, the High Availability feature stores a table of standbyMDC assignments on the volume. High Availability monitors theMDC constantly by performing a variety of tasks. However,optimizations are in place to reduce impact on running systems, thestorage network, and the LAN. You should first understand the tasksthat High Availability standby systems perform.


The tasks include:

¶ Configuration Information. High Availability reads theconfiguration information stored on the SAN volumes. Thisincludes the current MDC name of each volume and the list ofstandby systems.

¶ Ping. High Availability performs a ping check of all MDCs thisstandby system is monitoring (based on the configurationinformation above).

¶ Transferring Shared Volumes. After a successful ping check,the standby system downloads the list of shared volumes that aredefined on that MDC.

¶ Remapping hosts. High Availability downloads the list ofactively connected hosts to the current MDC. High Availabilityperforms the following operations:

v Makes the ghost version of the volume real (hard mount).

v Sends a message to all SANergy hosts (whether they have theHigh Availability feature installed or not).

v Remaps host’s existing mapped volumes to the standbyMDC.

¶ Transparent. The failover operation is nearly transparent. Mosthosts are unaware that a mapped drive is now targeting adifferent computer. The level of transparency depends on whatfile system activity is in progress when the MDC fails. Files thatare open will continue to do reads and writes until such timethat new metadata is needed (typically at file close time).Applications will experience typical Windows networkdisconnect errors at that time. Similarly, file locks (byte-rangeand operation-locks) are not carried over.

The frequency of task performance can be controlled with the HighAvailability Setup tool. See “High Availability Setup Tool” onpage 137 for more information.


8.H

igh

Availab

ilityF

eature

Usage and Administration

CautionBe extremely careful shutting down or rebooting an MDCwhen installing software or hardware. Rebooting an MDC thatis being monitored by a High Availability system will result ina failover. If that is not desired, it is recommended that youstop the High Availability feature on each standby machinewhile doing routine reboots. It is NOT sufficient to simplychange the configuration information (such as blanking-out anystandby systems) as this information is only refreshed fromdisk at certain intervals.

Setting Up Administrative Privileges BeforePerforming the High Availability Installation

The High Availability feature does not install if the administrativeprivileges are not set properly for the Log On As A Service Right.To check this setting, do one of the following:

Windows NT procedure:

1. Select Start->Programs->Administrative Tools->UserManager. The User Manager window appears.

2. Select Policies\Users Rights. The User Rights Policy windowappears.

3. Highlight the account in the Grant To portion of the windowthat you will use to install the SANergyHA feature.

4. Click in the box next to Show Advanced User Rights.

5. Click on the down arrow key and select Log On as a Serviceand click OK. The User Manager window appears.

6. Click User, then click Exit.

7. Install the High Availability software.


Windows 2000 procedure:

1. Select Start->Settings->Control Panel. The Control Panelwindow appears.

2. Double-click on the Administrative Tools icon.

3. Double-click on Local Security Policy.

4. From Local Security Settings, click on the Local Policiesfolder.

5. Click User Rights Assignment. The User Rights List displayson the right side of the window.

6. Locate and double-click Log On as a Service. The LocalSecurity Policy Settings window appears.

7. Click Add. The Select Users or Groups window appears.

8. Click on the User you want to add to Log On as a ServiceRight.

9. Click Add, then click OK.

10. Install the High Availbility software.

Installing the High Availability Feature

NoteThis section applies to Windows systems only.

Check the README file for current changes before installingand configuring your system.

High Availability can only operate on systems that run SANergy.Before installation, be sure SANergy Version 2.2 or later is alreadyinstalled.


8.H

igh

Availab

ilityF

eature

To install the High Availability feature:

1. Insert the SANergy CD into the target computer.

2. Close all programs, and from My Computer window,double-click on the CD drive.

3. Double-click on the High Availability\SANergyHA 2.2.exe.The Welcome to the High Availability Setup Programwindow appears.

4. Click on the Next button. The Software License Agreementwindow appears.

Figure 36. Welcome to the High Availability Setup Program Window


5. Read and acknowledge the License Agreement and do one ofthe following:

¶ Click on the Yes button to accept the license agreement.

Or:

¶ Click on the No button to exit the High Availabilityinstallation.

6. If you selected Yes, the User Information window appears.Type your Name and Company name.

7. Click the Next button. The Choose Destination windowappears. Tivoli recommends using the default destination folder(C:\Program Files\SANergy\SANergyHA).

Figure 37. User Information Window


8.H

igh

Availab

ilityF

eature

8. Click on the Next button. The Select Program Folder windowappears.

Figure 38. Choose Destination Window


9. Click on the Next button. The Select Components windowappears. You can enable or disable the installation of thefollowing components by clicking on the check box next to thecomponent:

¶ Program Files: installs all necessary files for the HighAvailability feature to work. The default setting is Enabled.

¶ SNMP feature: installs all necessary files to use the HighAvailability SNMP feature. If SNMP is not installed at thistime, you need to reinstall this software. The default settingis Disabled.

Figure 39. Select Program Folder Window


8.H

igh

Availab

ilityF

eature

10. Click on the Next button. The Start Copying Files windowappears.

Figure 40. Select Components Window


11. Click on the Next button. The High Availability feature is nowcopied to the destination directory. Upon completion, theService Account Information window appears.

Figure 41. Start Copying Files


8.H

igh

Availab

ilityF

eature

12. Type in the following:

¶ Account: DomainName\Administrator (that is,Testlab\Administrator, or the computer name if not in adomain environment). By default, the software updates thisfield with the present system logon account.

¶ Password: (none) or administrator password for theaccount.

13. Click on the Next button. Upon completion, the SetupComplete window appears.

Figure 42. Service Account Information Window


14. Click on the Finish button. The Standby Assignment windowappears. This window lets you establish backup MDCs for eachvolume. Should the primary MDC fail, the first standby systemtakes over its responsibilities.

Figure 43. Setup Complete Window


8.H

igh

Availab

ilityF

eature

To establish the standby MDCs, click on the desired volumelabel/labels and select Change.

1. Type in the First Standby MDC and Second Standby MDCnames and click OK.

Note: The First Standby MDC can be any Windows computerin your SAN that has High Availability installed.

Figure 44. Standby Assignment Window


2. When configuration is complete, click on the Finish button. Areboot message appears.

Note: You must reboot your system for the High Availabilityfeature to monitor the MDCs.

IMPORTANT: Configuration changes made in the Setup Tooldo not take effect immediately. If you want immediate changes totake effect, click on the Update Shares button. This ensures100% accuracy with the running High Availability system after aconfiguration change.

3. Click OK. The system reboots.

Note: If you want to make configuration changes afterinstallation, use the “High Availability Setup Tool” (seethe next topic for details). Use the Setup Tool to changestandby MDCs, adjust polling and timeout intervals, andto review the High Availability version number.

High Availability Setup ToolThe High Availability Setup Tool is run from the Start menu. Itlets you assign standby MDCs, adjust polling and timeout intervals,and review the High Availability version number.

To access the High Availability Setup Tool, select Start ->Programs -> SANergy -> SANergyHA Setup Tool. TheSANergyHA Setup Tool appears.

IMPORTANT: Configuration changes made in the setup tool do nottake effect immediately. For immediate changes to take effect, youmust stop the High Availability feature, make the desired changes,and start the High Availability feature. When High Availability startsup, it performs all of its downloads and disk-reading in order toprime its internal structures. This ensures 100% accuracy with therunning High Availability feature after a configuration change.


8.H

igh

Availab

ilityF

eature

Using the Standby Assignment DialogClick the Standby Assignment tab. The Standby Assignmentdialog appears.

To assign or change MDC standby systems, use the following steps:

1. Click the desired volume label to which you want to assign astandby system.


2. Click on the Change button.

3. From the First Standby field, type in the standby system namethat will monitor the MDC.

4. From the Second Standby field, type in the standby systemname that will monitor the First Standby system.

5. Click OK. The Standby Assignment folder updates with thenew standby system names.

Figure 45. SANergyHA Standby Assignment Folder


8.H

igh

Availab

ilityF

eature

Changing the OptionsThe Options portion of the Standby Assignment folder lets youchange the following intervals:

¶ Check all MDC every ____ second(s). The polling intervaldetermines how often standby MDCs ping the MDCs theymonitor. Default value: 10 seconds.

¶ Take over if no response in ____ second(s). The responseinterval determines how long the standby MDC waits for a replybefore taking over for an MDC. Default value: 10 seconds.

¶ Scan for new shares every ____ second(s). The new shareinterval setting indicates how long it takes the standby system todetect newly defined shared volumes or any changes to thecurrent MDC or standby systems. Default value: 300 seconds.

To change the Options settings, do the following:

1. Click in the desired option window.

2. Type the desired setting.

3. Click Apply. All settings are applied, and the Options windowupdates accordingly.

To restore the default values, click on the Restore Defaults button.

Usage Notes¶ Anytime you add, remove, or change a shared volume on the

MDC, it takes a few minutes for that information to be noticedby the standby systems.

¶ The standby systems must be fully active SANergy systems andhave proper disk and striping configuration information loaded.

¶ Be sure that SANergy and High Availability are configured withthe correct account information with administrative privileges. Ifnot, you will receive a Login to service error message.

¶ All hosts must have drive letters on the mounted volumes forfailover to work properly.

¶ Check the event viewer for any error information.


Uninstalling the High Availability FeatureTo uninstall the High Availability feature, perform the followingsteps. If you wish to remove High Availability from more than onecomputer, you must run this procedure on each machine.

1. From the My Computer window, double-click on the ControlPanel icon.

2. Double-click on the Add/Remove Programs icon.

3. From the Install/Uninstall tab, click on SANergyHA.

4. Click on the Add/Remove button.

5. Select Yes to uninstall the High Availability feature.

6. Follow the instructions on the screen until you have completedthe uninstall process successfully.


UNIX Host High Availability SupportThis section describes how to use a UNIX SANergy host system inconjunction with Windows-based (Windows NT or Windows 2000)High Availability (MDC). The High Availability feature for Windowsallows a Windows system to act as a standby system for otherWindows MDCs. Should an MDC fail, the High Availability standbysystem attempts to take over as much of the MDC responsibilities aspossible. The standby system will become the hard-mount file serverfor the volumes. It will also reestablish the Windows shared volumesand attempt to notify the various active SANergy host systems of thechange of ownership.

SANergy Windows host systems receive notification of a failoverevent and will automatically remap any drive mappings to the newhost. UNIX hosts are unable to receive the same type of notification,and so there is a different technique available. This section describesthat technique.


8.H

igh

Availab

ilityF

eature

UNIX Host OverviewIn order to have UNIX hosts with any Windows MDC, the MDCmust have some NFS server software running. Thus, in order for theMDC to failover and continue to correctly support UNIX hosts, theWindows standby system must also have the NFS server softwarerunning and configured identically. Each UNIX system will run adaemon script that periodically monitors each MDC. When it detectsthat an MDC is no longer available, it will dismount the existingmount point and reactivate the mount on the new machine. It mustalso coordinate with SANergy to ensure that the properhousekeeping activities take place during the transition.

The UNIX machines do not have direct access to the HighAvailability database which lists all the MDCs and their associatedstandby machines. Therefore, it is necessary for the administrator toconfigure the UNIX daemons to monitor the proper machines.

There are two scripts that are supplied with the SANergyinstallation:

¶ scriptHA: Pings a particular host and, if the host is down,performs the necessary failover steps.

¶ callscrpt: An example script (it must be edited) that calls thescriptHA script. The administrator can edit either script or bothscripts and add them to a system initialization routine so thatthey run automatically at boot time if desired. The scripts arevery straightforward, and each administrator will probably wantsome customized behavior. Create one script per volume, with adifferent name for each script. For monitoring purposes, youcould keep the volume names and the MDC names in sync(vol-1 with MDC-A, for example).


scriptHA

This script is very straightforward, and documentation in the fileitself describes the behavior, parameters, and customization points.Parameters passed to this script include:

¶ the MDC to monitor

¶ the standby MDC

¶ the share name (NFS export on the MDC systems)

¶ the mount point on the local machine.

When this script determines that the MDC is unavailable, it starts thefailover process:

¶ Tells SANergy that the volume is no longer active.

¶ Forces a dismount of the current mount point.

¶ Attempts to re-mount targeting the new MDC. Because theactual MDC failover might take a little while, the script willattempt this mount in a loop for several minutes.

¶ Tells SANergy that the volume is now available again.

¶ The script then exits.

callscrpt

This is an example script and must be edited by the administrator. Itis extremely short and merely loops, calling the scriptHA script andsleeping between activations. The administrator can choose to havethis script monitor all other MDCs, or only specific MDCs, ormonitor only under certain conditions.


8.H

igh

Availab

ilityF

eature


SANergy SNMP Management

The SANergy simple network management protocol (SNMP) featureallows system administrators to centrally and globally control andmonitor all systems on the SAN.

SANergy does not provide an SNMP GUI tool; refer to theinstructions on how to install the SNMP Service available fromWindows.

To install and use the SNMP feature, do the following:

Windows SNMP Installation:

1. Install the SNMP service (located on the Windows CDnetworking service). Windows supports SNMP version 1.

2. Use all default settings in the SNMP Service Properties tab. TheSNMP Service Properties are:

¶ Agent: Contact location

¶ Traps: default (no entries)

¶ Security: Community public rights Read/Create.

3. If you did not enable SNMP during SANergy initial installation,you will need to reinstall SANergy. When the ComponentSelection window appears, click in the box next to SNMP. Thiswill enable the proper installation of the related MIBs and DLL,which are: SanParent.MIB, SANergy.MIB, and SANagent.dll.

A


A.

SN

MP

Man

agem

ent

4. Click on the Next button. The Start Copying Files windowappears.

5. Continue with the SANergy installation until complete.

Figure 46. Start Copying Files Window


Solaris and AIX SNMP Setup:

By default, the SNMP files (MIBs and daemon) are installed to the/opt/SANergy/snmp directory (for Solaris) and the/usr/SANergy/snmp directory (for AIX). The SNMP files include:sanagent-mib.txt, ibmprod-common-mib.txt, and the snmpddaemon.

1. Copy the snmpd.conf file from /opt/SANergy/snmp (for Solaris)and /usr/SANergy/snmp (for AIX) to /usr/local/share/snmp.Modify the snmpd.conf located in /usr/local/share/snmp to setup your network token and community access permissions toreflect your local network. Refer to the default snmpd.conf filefor details and examples.

2. Copy /opt/SANergy/snmp/mibs (for Solaris) and/usr/SANergy/snmp/mibs (for AIX) directory to/usr/local/share/snmp. This directory includesSANAGENT-MIB.TXT and IBMPROD-COMMON-MIB.TXT.

3. Start up the SNMP daemon in the /opt/SANergy/snmp (forSolaris) and /usr/SANergy/snmp (for AIX) directory with thefollowing: snmpd -p 163 (163 represents the SNMP port, as anexample). Ensure that the SNMP browser tool used has the sameSNMP port setting.


A.

SN

MP

Man

agem

ent

Using the SNMP Browser:

1. Install the desired MIB Browser. Refer to your browser manualfor installation instructions and use.

2. Start your MIB browser and load the SANergy.MIB andIBM.MIB or their compiled versions.

Note: Some MIB browsers might require you to compile theMIBs first. If so, refer to your browser manual forcompile instructions.

3. Confirm that the browser points to the desired Windows system’sIP address under test. Refer to your browser manual for moreinformation.

4. Expand the MIB Tree until you can view the SANergy folder.Now you can contact, walk, or get to any of the SANergyvariables defined in the SANERGY.MIB. Some variables are alsowriteable. You can set these variables through the MIB browser.

The number of variables at the root of the SANergy folderdepends on the total number of Host Adapters, Managed Buses,and Volumes on your SAN. Each variable has numeric valuesdisplayed in KB.

AttentionBe aware of the variable and the effects of that variablebefore making changes using the SNMP feature. See“SANergy Setup Tool” on page 38 for all variable andoption descriptions.

The following figures show:

¶ SANergy Folder Contents, Figure 47 on page 149.

¶ Windows Sample Walk Query, Figure 48 on page 150.

¶ UNIX Sample Walk Query, Figure 49 on page 151.


Figure 47. SANergy Folder Contents


A.

SN

MP

Man

agem

ent

Figure 48. Windows Sample Walk Query


Figure 49. UNIX Sample Walk Query


A.

SN

MP

Man

agem

ent


MSCS Configuration

This section describes how to properly configure SANergy for usewith the Microsoft Cluster Server (MSCS). Configuring andmanaging a cluster server environment is an advanced task, andSANs add a new dimension. Do not install and configure unless youhave a good understanding of MSCS and SANergy details.

WarningPlease read these instructions completely and accurately. Failureto do so may result in a configuration that is difficult to operateor recover from.

These are the steps necessary to install and configure an MSCSCluster:

1. Uninstall MSCS if presently installed.

2. Install and configure an MSCS cluster for use with SANergy.

3. Install SANergy on a single node and use special marks.

4. Install SANergy on remaining nodes.

5. Install the SANergy-MSCS software.

6. Create SANergy Disk Resources.

B


B.

MS

CS

Co

nfig

uratio

n

WarningBoth SANergy and MSCS manage disk resources on a SANfabric, and they can collide if not used correctly. MSCS usesSCSI Reserve commands to block access to disks bynon-cluster nodes (this will prevent SANergy from workingproperly on those disks). Conversely, SANergy protects disksfrom applications and can make MSCS not properly see itsshared resources if not correctly installed.

Install and Configure an MSCS Cluster for Use withSANergy

Follow these steps to install and configure an MSCS Cluster for usewith SANergy.

1. Uninstall MSCS if presently installed on your SAN systems.

2. Install and set up MSCS to work in conjunction with theSANergy software. Do the following:

a. Make the quorum volume an entire disk, not just a partition.

b. All disks must reside in the unshared column during theMSCS install for SANergy and MSCS to work properly.

3. Get the volume serial numbers for all volumes. From thecommand prompt, cd to the desired drive and then type dir.When the directory displays, it lists the volume serial number.Either write the serial numbers down or copy them to a text file.

Install SANergy on a Single Node using SpecialMarks

Follow these steps to install SANergy on a single node using specialmarks.

1. From the first cluster node (the one that owns all the volumes),install SANergy.


a. From the Select Managed Buses window, manage the SANbus. A Y indicates the bus is managed.

b. From the Volume Assignment window, assign the volumeswith the following special names:

¶ Assign the quorum volume with ?FREE.

¶ Assign all other volumes with ?CLUS.

c. Reboot your system.

2. Continue the SANergy installation with the remaining clusternodes.

Install the SANergy-MSCS SoftwareYour SANergy installation CD comes with an additional installer forthe MSCS-SANergy layer. The installer asks which system in thecluster you are currently installing. Ensure that you properly answerthat question, since a different set of files gets installed for the lastsystem installed in a cluster. The cluster server must be runningprior to this step.

Note: Be sure to specify the same installation location on ALLmachines in the cluster (that is, if you choose to install themon C:\SANergyMSCS\ on one machine, you must install tothat location on the remaining systems). This is a restrictionof MSCS.

1. Install the SANergy-MSCS layer on each system.

Note: Before installing on the last cluster node, bring up ClusterAdministrator or the install may fail after login.

2. Install on the final cluster node. When installing on the finalcluster node, select Final Cluster Node Setup.

Note: The Final Cluster Node system displays an additionalinstallation window after the reboot and login window.

3. Click Install to complete the installation.

4. Click Exit to reboot the system.


B.

MS

CS

Co

nfig

uratio

n

Create SANergy Disk ResourcesYou told SANergy which disks to ignore, and let another programmanage them; now you now need to tell MSCS which disksSANergy will manage. It is possible that some of the disks that youwant to be managed by SANergy are configured to be managed byMSCS. If so, delete those disk resources. Then, create new diskresources and select the SANergy Volume Resource as the manager.

Disks that you configure in this manner are special. The MDC forthat disk will be whatever cluster member is currently in control ofthe disk (provided the ?CLUS SANergy owner tag is in place).Should a cluster failover take place, this disk will be automaticallymounted on the new member and will automatically become theSANergy MDC. That is, when the volume is brought on-line bycluster server (or interactively), then the volume will be mountedand available to that node (as a SANergy MDC volume).

All disk resources and share resources must be created under theCluster Group in order for SANergy to work. When creating theSANergy Volume resources, you must enter the serial number of thevolume.

Note: Be sure to remove the hyphen from the serial number beforeentering.

1. Select Start->Programs->Administrative Tools->ClusterAdministrator. The Cluster Administrator window appears.

2. From the Groups folder, open Cluster Group.

3. Right-mouse click on Cluster Group and select New/Resource.The New Resource window appears.

4. From the Name field, type the Volume name.

5. (Optional) Type in a volume description.

6. From the Resource Type field, click on the down arrow keyand select the SANergy volume.

7. From the Group field, select Cluster Group.


8. Click Next. The Possible Owners window appears. Be sure allSANergy systems are in the possible owners field.

9. Click Next. The Dependencies window appears. Ignore thiswindow as there are no dependencies for SANergy volumes.

10. Click Next. The SANergy Volume Parameters windowappears.

11. From the Volume Label field, type the volume name.

12. From the Serial Number field, type the volume serial number(excluding the hyphen).

13. Click Finish. The new volume appears in the ClusterAdministrator window. The default value is offline.

14. Right-mouse click on Cluster Group and select Bring on-line.

15. Set up Sharing for this volume.

16. Repeat the above procedure for all remaining SANergyvolumes.

Host-side ConsiderationsThere are no special host-side considerations. SANergy host systemsthat want to access these disks would do so in the same manner theywould with ordinary LAN clients accessing the cluster as a fileserver. That is, they would map to the global cluster name (and notthe specific system name). SANergy should provide fusedacceleration as it ordinarily would. Any cluster failure events shouldresult in any host systems (LAN or SANergy host systems)automatically noting the new place to retrieve MDC-typeinformation.


B.

MS

CS

Co

nfig

uratio

n

Uninstalling SANergy or the SANergy-MSCS LayerBe very careful when uninstalling either SANergy or theSANergy-MSCS layer.

1. Delete any SANergy volume resources and make them ordinarycluster disk resources.

2. Uninstall the SANergy MSCS layer software.

3. Uninstall the Tivoli SANergy software.


Enhancing Small File Operations

ZOOM is a feature within SANergy that allows certain types ofsmall file operations to operate orders of magnitude faster than baseSANergy. Currently, ZOOM is only available between systems thatare of the exact same platform and file system types and currentlyonly available on Linux and Solaris UNIX platforms.

There are now a number of application areas, such as web serving,that would like to use SANs and a shared file system, but aredominated by small files. Fortunately, some of these significantmarket opportunities mainly want read access to a set of files(possibly a very large set of files) yet still need to occasionallyupdate, write, or create new files in those areas. ZOOM isspecifically designed for this sort of environment.

Change List Management

ZOOM is a pre-filter on top of any other file system in your system(it does not have to be strictly a filter on top of a SANergy networkfile system). With each file open (and read), ZOOM is activated anddetermines if this particular request can be safely and coherentlysatisfied by going to a synonym read-only mount point instead. If so,it will transparently redirect the open to that device without theapplication ever knowing. ZOOM is designed to be activated on aper directory tree basis. It is not practical to use ZOOM on an entirefile system (there are some restrictions on the total number ofchanged-files ZOOM can handle and other considerations describedlater). In general, you should use base SANergy or regular

C


C.

En

han

cing

Sm

allF

ileO

peratio

ns

networking as much as possible, but when you find a particulardirectory or tree that meets the ZOOM requirements, and is causingimportant performance delays when using regular technology alone,ZOOM should be considered.

Thus, on a per ZOOMable file system basis, there needs to be a hardmounted read-only instance of that file system that ZOOM is able toexploit. Through sophisticated ″change-list management″ softwarebuilt into ZOOM, each ZOOM host will know which files it cansafely access directly and which ones need to fall back to theoriginal target. The hallmark of ZOOM is that you will always haveread/write access to your file system from all computers, and have100% coherency and accuracy for each and every file.

Typical ZOOM Examples

A typical ZOOM example is a tree of font files that all tend to bebetween a few hundred bytes and 10KB. The set of applications inuse need heavy access to the font files for a large image processingapplication. There might be several thousand files, and for any onejob a random set of the files is needed (and constantly changing perjob). Given that these are font files, they seldom change. Perhapsonce a day or every few days a new font or family is added, but ingeneral the changes are minimized. This would be an ideal job forZOOM.

A different example would be a scalable web serving application.About 80% of the content retrieved from disk is from static HTMLpages and GIFs and other graphics. The remaining content is eitherdynamically created or highly changeable or fairly large files (videoand audio files well suited for SANergy to begin with). Asadministrator of this system, you are able to organize the ″80%″ filesinto a tree and have ZOOM watch that tree.

Directories

ZOOM works on a directory tree basis. ZOOM can be configured towatch many trees or just a few. Watch means that the real filesystem owner (the MDC typically) will monitor those directories for


changes and it will inform all the ZOOM-attached hosts about thosechanges. The ZOOM hosts will use that change information tocorrectly decide how to handle each and every file open request.Remember, ZOOM only accelerates files that have been opened forread-only access; any open that could possibly result in data beingwritten will bypass ZOOM.

ZOOM has limits. It is possible for the number of files in a changedstate for a given tree to be quite high. So high that the time (orresources required) to check this list could reduce the ZOOMbenefit. Thus, on a per watched-tree-basis, you can set a limit. Oncethe limit is reached (saturated), ZOOM will stop accelerating accessto that tree.

This saturation limit needs to be carefully understood. It is possiblethat there is a ZOOM watch directory that is quite large andgenerally fits the ZOOM requirements (lots and lots of small files,typically opened for read-only). But perhaps there is somesub-directory within that tree that tends to receive a lot of transientdocuments (maybe a mail folder, a staging repository, or the like).That one single directory could result in that whole tree entering asaturated state and thus shutting down ZOOM on the tree. There is,however, a solution.

ZOOM allows you to watch directory trees, and trees within trees.The order that the trees are traversed is critical to work around theabove problem. You would first monitor the directory that isexpected to change frequently (counter to what you would normallywatch with ZOOM) but set a very low saturation level (two or threefiles). Then, you would watch the higher level directory (whichencompasses the first one) with typical ZOOM thresholds (such as500 files). At run time, any file open attempted in the highlychanging directory would likely be un-ZOOMed (due to hittingsaturation), but other file opens in the higher tree will succeed. Ifyou created the watch list the other way around, this behavior wouldnot happen.


C.

En

han

cing

Sm

allF

ileO

peratio

ns

Major Components and Configuration for Linux andSolaris

The ZOOM technology on UNIX brings with it a few importantcomponents that need to be activated and configured. There is aZOOM daemon (called zoomd) that must be up and running on thefile system owning machine (typically the MDC) and on eachZOOM host that expects to have accelerated performance (hosts thatdon’t desire ZOOM do not need this activated). This daemon shouldbe started at system startup time, but it can be activated at any time.

zoomd is used both as a daemon and as a configuration andmonitoring tool. When activated with no special parameters (otherthan the keyword indicating whether to be a host or mdc daemon),the program will quietly wait and process networking and file systemrequests (that is, it will not exit; you can activate zoomd as abackground process if desired).

Running the zoomd program without any parameters will result in itdisplaying all the current activation options.

Basic Invocation

Every invocation of the zoomd program MUST specify either host orMDC as the first parameter. There are many other optionalparameters (described below) but this first one is required anddetermines how the program will map internal memory and how itwill behave. So you would start the daemons at startup as one of thefollowing:


zoomd host& or

zoomd mdc&

Initializing

Typically, when you start the daemon as a true mdc or host daemon(as opposed to running it for configuration or diagnostic purposes)the daemon will initialize all the internal memory structures. If thatis not desired it is critical that you specify the ″-noinit″ flag on thecommand line. This ability is primarily for debugging use and is notexpected to be used by customers.

Statistics

You can activate the zoomd program and specify ″-stats″ which willresult in the program printing out all sorts of useful system statistics.Often this is used to see how well ZOOM is accelerating files.

Print

The ″-print″ option will result in the program printing out all internaltracking information. This includes all the directories that are in awatched state, all the files within those directories that are in achanged state, all known hosts that are being tracked, and variousother information.


C.

En

han

cing

Sm

allF

ileO

peratio

ns

Log Levels

When starting either the host or MDC zoom daemon, you mayoptionally specify the ″-log level″ switch and parameter. The allowedvalues are 0 through 3. Level 0 is for debugging purposes andproduces trace informational that may be too verbose for typicaloperations. Level 1 only presents messages that are deemedinformational in nature; far fewer than with the debug value of 0.Level 2 results in only messages that are considered errors(unplanned for events). If level 3 is specified, only messages thatresult in a panic or shutdown of ZOOM will be presented.

Timeout

The ″-timeout seconds″ option allows you to select how manyseconds ZOOM will wait for a response when communicating toother ZOOM component (this option applies to both the MDC andhost sides independently).

Host SideWatching Directories

ZOOM needs to be told which directories to attempt to accelerate.This is performed on the host side and the directory specified is theregular LAN network directory. The syntax is:zoomd host -watch mountdir maxfiles

ZOOM will attempt to decompose the specified directory into thetrue mount-point and the remaining subdirectory. It will use themount point as a key to the mounted volumes table and determinethe owning host and remote share this mount is attached to. Next, itwill send a request to the mdc-side ZOOM daemon which willvalidate the request. The mdc-side will setup an internal watch onthe equivalent hard mounted directory (and any subsequent changesto that tree will be sent back to the host daemon) and it will issue a″sync()″ command locally to force any and all file systemmodifications out to disk. Finally, the host daemon sets up a watch


on its version of the file system (so that it can accelerate anysubsequent operations performed on the tree).

Typically maxfiles should be set to about 100MB or so. Each andevery file open that hits on that directory tree will have to scan thislist of files.

Configuring the Mappings

Telling ZOOM which directories to monitor is not quite enoughinformation for it to completely do its job. It must also know theequivalent read-only mounts for a given network mount. ZOOMholds a table of these associations (called mappings) and you canconfigure that table with the ″-map″ command as follows:zoomd host -map networkmount readonlymount

You must first have the read-only mount available prior to issuingthis command (that is, you must mount it). Typically you will usethis ″-map″ command before using the ″-watch″ command becauseonce the watches are in place, ZOOM will try to translate to a localmount any hits that result (if it can’t, the transactions will merelyfall back to their default path).

Detaching

There may be times on the host where you want to entirely andgracefully shutdown all the watched directories. You can use the″-detach″ command to do this. You might want to do this if you areseeing that some critical watched directories are saturated and youwish to start with a clean slate. You can do this while the system isup and running and everything will survive. The recommended stepsare:

1. Issue the detach command

2. Unmount the read-only mount; then re-mount it

3. Re-issue the ″-watch″ commands (it is not necessary to re-issuethe ″-map″ commands)


C.

En

han

cing

Sm

allF

ileO

peratio

ns

In some cases you may not be able to unmount the read-only mountpoint. This is typically the case if there are active files opened usingthat device. In such cases, you may wish to re-mount the read-onlydevice under a different directory and then re-issue the ″-map″command to reflect this directory. Later, you may be able toun-mount the first directory.

Unwatch

Similar to the detach command, you may instead want to merelyun-watch a particular directory (possibly for the same reasons givenin the detach section). The syntax is:zoomd host -unwatch dir

Note: Currently, this ″-unwatch dir″ command is not implemented.Instead, there is ″-unwatchall″ which will un-watch all thecurrently watched directories.

Saturation Handler

Whenever the host side receives notification that a watched tree hasbecome saturated, the ZOOM host technology will attempt toactivate a system-specific saturation handler. The handler must be ascript (or executable) named zsaturation. First the current directorythat ZOOM was started from is checked, and if that fails, then thedefault path is used to find the zsaturation program. The program ispassed:Directory-name max-files mdc local-mount-point

The program will typically be created to first issue an ″-unwatchall,″then will attempt to dismount/re-mount the read-only mount point,and then issue a ″-watch″ command to restart the watching process.


MDC SideStat Daemon

The ″-statd seconds″ option tells the MDC to spawn a separatethread for monitoring changes to the watched file system trees. Thisis needed when there is a chance that files could be updated on theMDC and not pass through the SANergy technology. It is expectedthat most processes on the MDC will run with the SANergy libraryactivated, and thus changes to the file system will be realized by theZOOM technology. However, changes that come in through an NFSconnection avoid SANergy, and thus will not be noticed. Using the″statd″ option allows any change to be realized through a pollingmechanism. The administrator needs to decide whether or not toactivate the ″stat″ daemon option.

ZOOM RestrictionsFor this release, there are a number of restrictions (please also seeany Readme documentation that might either add to or reduce thislist).

Last Accessed Dates

When a file is opened on a ZOOM host and has successfully beenaccelerated, the real file-system ″open″ is occurring on a read-onlyfile system. Thus, such things as modifying the ″last accessed″ datestamp on the file can not take place. Most small-file criticalenvironments (like web serving) typically disable updating of thelast-accessed time stamp anyway (for performance reasons).

Post Open Write

ZOOM will only allow a file to be opened on the read-only device ifit is very sure that it is safe to do so (regarding cache coherency).However, once a file is opened and in use, it is possible for anothermachine to open the file for updating (even removal) and thepre-opened hosts will not be aware of this. Generally, the hosts willsee the last known data for that file.


C.

En

han

cing

Sm

allF

ileO

peratio

ns

For now, files or trees that are sensitive to this issue should beexcluded from ZOOM (remember, you can exclude a sub-directoryby actually including it and setting a very low threshold, such as 0).

Stat Daemon

The UNIX implementation has a difficulty on the MDC of knowingeach and every change to a file system (because the ZOOM code isnot part of the kernel). Any application that could possibly result ina file system change on the MDC side should be run with theSANergy logic activated (and thus ZOOM will indeed see andrecord the changes). However, other services such as the NFS serverdaemon are run inside of the kernel and thus will not be able torecord their changes to ZOOM.

To remedy this, ZOOM has an ability to run a ″stat″ daemon. The″-statd seconds″ option to the zoomd program will activate anotherprocess that merely monitors and watches all the watched directoriesfor date changes (sleeping seconds in between checks). When itdetects that a directory has changed, it will run through the directoryand find the files that have changed and self-update its technology.

ZOOM SetupZOOM should be set up on both the MDC and the host.

MDC ZOOM Setup

1. Mount the drive you are going to use for ZOOM and share itout.

2. Open a terminal window and type:

¶ For Solaris:/opt/SANergy/zoomd mdc –statd 1

¶ For Linux:/usr/SANergy/zoomd mdc –statd 1

Note: statd 1 tells it to check every 1 second.


3. If the command is successful, you will get these two returnmessages:date,time,Shared memory has been initializedZOOM statd daemon started, sleep interval 1 seconds

Host ZOOM Setup

1. Hard mount the same drive you did for the MDC, but as readonly.

2. Now map to the drive on the MDC by doing an NFS mount.

Note: You will have the same drive mounted twice; hardmounted as read only, and also network mounted throughNFS.

3. Open a terminal window and start the ZOOM host by typing:

¶ For Solaris:opt/SANergy/zoomd host

¶ For Linux:usr/SANergy/zoomd host

If the command is successful, you will receive a returnmessage of Shared memory initialized. This window shouldbe minimized, since it needs to be open to keep running.

4. Open a new terminal window. You now need to set the watchhost daemon and saturation setting. Type:

¶ For Solaris:/opt/SANergy/zoomd host -watch /nfsmountpoint 10

¶ For Linux:/usr/SANergy/zoomd host -watch /nfsmountpoint 10

This should return three messages:DATE|TIME SendAndReceice 0, replyFunct:-1 reply.result:0DATE|TIME WatchDirectory: Successfully added:/nfsmountpointWatchDirectory result: 0


C.

En

han

cing

Sm

allF

ileO

peratio

ns

5. Now you need to set the mapping of the read only mount pointand the nfs mount point. To do this type:

¶ For Solaris:/opt/SANergy/zoomd host -map /nfsmountpoint /readonlymountpoint

¶ For Linux:/usr/SANergy/zoomd host -map /nfsmountpoint /readonlymountpoint

This should return the message:Result of AddMapping:0


Glossary

F

fabricFibre Channel employs a fabric to connect devices. A fabric can be as simple as asingle cable connecting two devices. The term is most often used to describe a morecomplex network utilizing hubs, switches, and gateways.

failbackA failback occurs when the original MDC becomes active again after a failure andtakes over from the High Availability MDC.

failoverA failover occurs when an MDC fails, and the High Availability MDC takes over asthe MDC. In most cases, this process occurs transparently to applications, thusenabling them to proceed without interruption.

FCSee Fibre Channel.

FC-ALFibre Channel Arbitrated Loop.

Fibre ChannelA high speed, bi-directional, multi-protocol, scalable interconnection betweencomputers peripherals, and networks.

fuseTo connect to a SANergy-managed volume for accelerated access. The successfulcombining of traditional LAN network transmissions with that of the high-speedpayload transmissions of SANergy. You may attempt to fuse any NFS-mountedvolume that also has a direct access path via a SAN technology (such as FibreChannel). If the SANergy technology is working correctly, you will see statistics onFused Transfers increasing when performing operations to the companionNFS-mounted volume.

The terms in this glossary are defined as they pertain to Tivoli SANergy. If you do not find a term youare looking for, you can refer to the IBM Dictionary of Computing, McGraw-Hill, 1994. In the UnitedStates and Canada you can order this publication by calling McGraw-Hill at 1-800-2MC-GRAW.


Glo

ssary

G

gatewayA node on a network that interconnects two otherwise incompatible networks.

H

HBAHost bus adapter. A Fibre Channel HBA connection that allows a workstation toattach to the SAN network.

hubA Fibre Channel device that connects nodes into a logical loop by using a physicalstar topology. Hubs will automatically recognize an active node and insert the nodeinto the loop. A node that fails or is powered off is automatically removed from theloop.

J

JBODJust a bunch of disks.

L

LANA Local Area Network, typically using lower-speed connections.

M

MDCMeta Data Controller. This is the machine on a per-volume (file system) basis thatis responsible for hard-mounting, and controls the security and allocationinformation. Only a single machine can be the MDC of a volume, but lots ofmachines can network-mount that same volume and have full SAN speed accesses ifSANergy is configured.

metadataData about other data. Examples are file names, file sizes, and access control lists.

Meta Data ControllerSee MDC.


MIBManagement Information Base. The physical and logical characteristics of a systemmake up a collection of information called a management information base (MIB).The individual pieces of information that comprise a MIB are called MIB objectsand they reside in the SNMP Agent.

N

Network File System (NFS)A protocol developed by Sun Microsystems, Inc., that allows any host in a networkto mount another host’s file directories. Once mounted, the file directory appears toreside on the local host.

network storageDisk drives and disk arrays shared by all users on a network.

NTFSNew Technology File System or NT File System. The file system used by WindowsNT. It supports multiple file systems, has file recovery for hard disk crashes, usesthe Unicode character set, and provides for file names up to 255 characters long.

P

PCIPeripheral Component Interconnect.

R

RAIDRedundant array of independent disks.

S

SambaSamba is an open source software suite that provides seamless file and printservices to SMB/CIFS clients.

SAN (storage area network)A managed, high-speed network that enables any-to-any interconnection ofheterogeneous servers and storage systems.

SCSISmall Computer Systems Interface.


Glo

ssary

SNMPSimple Network Management Protocol (a TCP/IP protocol). A network managementprotocol that is used to monitor routers and attached networks. This protocol gives auser the capacity to remotely manage a computer network by polling and settingterminal values and monitoring network events. Information on devices managed isdefined and stored in the application’s Management Information Base (MIB).

SSASerial Storage Architecture.

striped setA volume created across more than one physical storage device.

switchA component with multiple entry and exit points (or ports) that provides dynamicconnection between any two of these points.

T

TCP/IPTransmission Control Protocol/Internet Protocol.

U

UFSUniform Filing System.

V

volumeSpace on a storage device that is allocated for a particular use.

Z

ZOOMZOOM is a feature within SANergy that allows certain types of small fileoperations to operate orders of magnitude faster than base SANergy. Currently,ZOOM is only available between systems that are of the exact same platform andfile system types and currently only available on Linux and Solaris UNIX platforms.


Index

Aadding volumes 96administrative privileges for High

Availability 126

Bbus

changing bus configuration 40view shared bus configuration 40

Ccache

changing settings for UNIX 73changing settings for Windows 46exclusion list 50memory for 50settings for UNIX 73settings for Windows 49

cache command 78changing MDC ownership 99clear stats command 79commands

cache 78clear stats 79exit 79fuse 79fused 79get vol 79help 79hyper 79key 79log 80map cache 80

commands (continued)owner 81quit 81stats 81unfuse 81ver 81

compatibility 18configuration tools

SANergy UNIX 64using SANergy setup tool 38using SANergyconfig program 78

configuringLAN adapter on Windows 21on Windows 19storage adapter 22volumes 23

DDAVE software

uninstalling 92deleting volumes 96

Eexit command 79

FFAQs on UNIX systems 113frequently asked questions on UNIX

systems 113fuse command 79


Ind

ex

fused command 79

Gget vol command 79glossary 171

Hhelp command 79High Availability

setup tool 137High Availability feature 121

architectural overview 122installing 127overview 3system operation 124system services and privileges 123uninstalling 141UNIX host support 141

High Availability setup tool 137host computers

adding 95removing 95

hyper-allocation 62hyper command 79

Iinstalling

High Availability feature 127NFS server on Windows 34on UNIX 56on Windows 19, 25storage adapter 22storage hub and drives 23

Kkey command 79

LLAN connection

setting up 55LAN environment 10log command 80log files 83

MMacintosh

system requirements 16Macintosh host

setting up 85troubleshooting 118using 85

managing SANergyadding host computers 95adding volumes 96changing the MDC ownership 99deleting volumes 96removing host computers 95renaming volumes 97repartitioning volumes 98

map cache command 80MDC system

hyper-allocation 62Meta Data Controller (MDC)

changing ownership 99overview 10setup procedure for Windows 20setup procedure on Linux and Solaris 60troubleshooting 102

Microsoft Cluster Server Configuration 153MSCS Configuration 153


Nnetwork environment

setting up for Macintosh 85setting up for UNIX 55setting up for Windows 55

network requirements 17NFS server

installing on Windows 34NFS volumes

mounting 55

Oowner command 81ownership

configuring for Linux and Solaris 70

Ppartition

repartitioning volumes 98setting up on Windows 23

performancetesting for Windows 39testing on UNIX 68

Qquit command 81

Rrenaming volumes 97repartitioning volumes 98

SSAN connection

setting up 55SAN environment 11SANergy

configuring on UNIX 53configuring on Windows 19High Availability feature 121installing on UNIX 53installing on Windows 19Linux and Solaris MDC setup procedure 60Macintosh host installation and

configuration 85managing 95MSCS Configuration 153overview 1, 7setting up Macintosh host 85SNMP management 145system requirements 11technical support 4troubleshooting 101uninstalling on UNIX 84uninstalling on Windows 51UNIX host support 141using a script file 82using single commands 83using the configuration tools 38

SANergy High Availabilityinstalling 127setting up administrative privileges 126system operation 124system services and privileges 123uninstalling 141

SANergy Setup Tool 38SANergy software for Mac

uninstalling 92SANergy statistics

for Macintosh 92for UNIX 68

SANergyconfig programhow to pass a script file 82log files 83using single commands 83

setupZOOM 168


Ind

ex

shared volumessetting up for Windows 2000 34setting up for Windows NT 34

small file operations 159enhancing 159

SNMP management 145statistics

for Macintosh 92for UNIX 68, 75

stats command 81system requirements

for AIX 16for DG-UX 16for Linux (Red Hat) 14for Macintosh 16for SGI IRIX 15for Solaris 14for Tru64 UNIX 15for Windows 13

Ttechnical support 4testing performance

for UNIX 68for Windows 39

toolsusing High Availability Setup Tool 137using SANergy setup tool 38using SANergy UNIX configuration tool 64using SANergyconfig program 78

troubleshootingMacintosh hosts 118meta data controllers 102UNIX systems 110Windows systems 104

UUFS hyper-allocation 62unfuse command 81

uninstallingHigh Availability feature 141SANergy software for Mac 92

uninstalling SANergyDAVE software 92High Availability feature 141on Macintosh 92on UNIX 84on Windows 51

UNIXdisplaying SANergy statistics 68displaying ZOOM statistics 75installing SANergy 53system requirements 15uninstalling SANergy 84using SANergy Configuration Tool 64using SANergyconfig program 78ZOOM setup 168

UNIX hostHigh Availability support 141

UNIX systemtroubleshooting 110

UNIX System frequently asked questions 113

Vver command 81version number

how to view 50volume

assigning on Windows 44changing ownership on Windows 44configuration on Windows 23partitioning on Windows 23

volume sharingsetting up for Windows 2000 34setting up for Windows NT 34


WWindows

installing SANergy 19system requirements 13uninstalling SANergy 51using SANergy setup tool 38

Windows hostchanging cache settings 46setting up 35troubleshooting 104

ZZOOM 159

introduction 159setup 168using 159

ZOOM statisticsfor UNIX 75


Ind

ex


Program Number: 5698–SFS

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC26-7389-01

Date post:	22-Nov-2021
Category:	Documents
Upload:	others
View:	8 times
Download:	0 times

Tivoli SANergy - IBM

Documents