getting started guide - ibmpublib.boulder.ibm.com/tividd/td/tsnm/gc32-0726-00/en_us/pdf/gc… ·...

Tivoli Storage Network ManagerGetting Started GuideVersion 1 Release 1

Tivoli Storage Network Manager Getting Started Guide

Copyright Notice

© Copyright IBM Corporation 2000 All rights reserved. May only be used pursuant to a Tivoli Systems Software LicenseAgreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may bereproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by anymeans, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBMCorporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readabledocumentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No otherrights under copyright are granted without prior written permission of IBM Corporation. The document is not intended forproduction and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed,including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights-Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBMCorporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, DATABASE 2, DB2, DB2 Universal Database, Enterprise StorageServer, MQSeries, NetView, Planet Tivoli, RS/6000, pSeries, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, and TME aretrademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States,other countries, or both.

Lotus is a registered trademark of Lotus Development Corporation.

Microsoft, Windows, Windows NT, Windows 2000 and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Solaris, Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, orboth.

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

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available inall countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended toimply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or otherlegally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, exceptthose expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents orpending patent applications covering subject matter in this document. The furnishing of this document does not give you any licenseto these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,Armonk, New York 10504-1785, U.S.A.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWho Should Read This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Prerequisite and Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Typeface Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Manage Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Manage LUNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Manage File System Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. User Interface Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Tivoli NetView Console Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Standard Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Submap Window Graphical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Submap Window Explorer View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Status Filter Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Online Help in the Tivoli NetView Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Symbols used by Tivoli Storage Network Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Tivoli Console Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Layout of the Tivoli Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Locating and Performing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Embedded User Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Tivoli Console Guided Tour. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3. Starting and Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring the Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring the Polling Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 4. Viewing the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19SAN View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Topology View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

iiiGetting Started Guide

Zone View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Host Centric View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Device Centric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 5. Working with Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Working with Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

The Use of Color to Indicate Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

How Status Propagates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Status in the Submap Graphical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Status in the Submap Explorer View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Clearing the Status History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Status Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Working with Device Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Launching Network Device Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

An Alternate Launching Technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Using the Tivoli NetView Event Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 6. Managing LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Rogue Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Rogue Hosts Displayed on the Tivoli NetView Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Rogue Hosts Displayed on the Tivoli Console (Manage LUNs) . . . . . . . . . . . . . . . . . . . . . . . . 48

Enabling and Disabling Manage LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Using Manage LUNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Displaying Host Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Displaying LUN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Assigning a LUN to a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Sharing a LUN with another Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Unassigning a LUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Reassigning a LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Discovering Hosts and LUNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Removing an Inactive Host from the Tree View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Changing the Polling Interval for Manage LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Viewing Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Displaying Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Displaying LUN Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Unassigning a LUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 7. Managing File System Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

iv Version 1 Release 1

Default Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Defining LUN Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Defining Domain Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Defining Host Group Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Creating New Host Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Editing Existing Host Group Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Defining Host Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Defining Specific File System Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

SAN Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

vGetting Started Guide

vi Version 1 Release 1

Preface

Tivoli Storage Network Manager is a comprehensive SAN management software product.This guide explains how to use Tivoli Storage Network Manager.

Who Should Read This DocumentThis document is intended for Storage Area Network (SAN) administrators and networkoperators who are familiar with the following:¶ Using software on a Windows system¶ Tivoli Kernel Services¶ Tivoli Presentation Services¶ SAN concepts¶ Storage concepts¶ Tivoli NetView¶ SNMP concepts¶ Tivoli Enterprise Console (TEC), if you are displaying TEC events

Prerequisite and Related InformationThe following table contains Web sites to access for additional information.

Table 1. Product Web SitesProduct Web Site

Tivoli Storage Web site www.tivoli.com/storage

Tivoli Storage Network Manager www.tivoli.com/tsnm

Tivoli Storage Network Manager devicecompatibility and SAN components list

www.tivoli.com/support/san/tsnm_devices.hml

Tivoli Storage Network Manger function in relationto ANSI standards compliance in your SAN

www.tivoli.com/support/san/tsnm_functionality.html

Tivoli Storage Network Manger productrequirements and devices supported

www.tivoli.com/support/san/requirements.html

Tivoli Storage Network Manger Screen Team helpsensure successful implementation

www.tivoli.com/support/san/tsnm_experts.html

Tivoli Storage Network Manger technical support www.tivoli.com/support/san/index.html

IBM Universal DB2 Enterprise Edition www.ibm.com/software/data/db2/udb

The following table lists documents you can access for additional information.

Table 2. Related DocumentsDocument Order Number

Tivoli Storage Network Manager Planning and Installation Guide GC26–7380

Introduction to Storage Area Network, SAN SG24–5470

Designing an IBM Storage Area Network SG24–5758

Tivoli NetView for Windows NT User’s Guide GC31–8502

Tivoli NetView for Windows NT Programmer’s Guide SC31–8416

Tivoli NetView for Windows NT Programmer’s Reference SC31–8417

viiGetting Started Guide

Table 2. Related Documents (continued)Document Order Number

Fibre Channel Connection to the Future ISBN 1–878707–45

IBM Enterprise Storage Server SG24–5465

Implementing the Enterprise Storage Server in Your Environment SG24–5420

The following table lists documents that are helpful for planning and installing Tivoli KernelServices. You will find these documents on the Tivoli Kernel Services CD-ROM.

Table 3. Tivoli Kernel Services DocumentsDocument File Name on CD-ROM

Planning for Tivoli Kernel Services tks110_planning

Introducing Tivoli Kernel Services Administration tks110_introducing

Installing Tivoli Kernel Services tks110_installing

Tivoli Kernel Services Command Reference tks110_commands

Typeface ConventionsThis publication uses the following typographical conventions:

Table 4. Typographical ConventionsExample Description

bold Commands, keywords, and other information that you must use literally appear in bold.

italics Variables and new terms appear in italics. Emphasized words and phrases also appear in italics.

Contacting Customer SupportIt is crucial that you install and keep up with the most recent maintenance level for TivoliStorage Network Manager. To obtain maintenance information and downloads for TivoliStorage Network Manager, go to:

http://tivoli.com/support/san/maintenance.html

Before contacting customer support, ensure you have installed the most recent Tivoli StorageNetwork Manager maintenance.

The Tivoli Customer Support Web site is athttp://www.tivoli.com/support/

If you need support for this product or any other Tivoli product, contact Tivoli CustomerSupport in one of the following ways:

¶ Submit a problem management record (PMR) electronically from our Web site at:http://www.tivoli.com/support/reporting/

For information about obtaining support through the folliwng Tivoli Customer SupportWeb site:

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

viii Version 1 Release 1

¶ Submit a PMR electronically through the IBMLink system. For information aboutIBMLink registration and access, refer to the following IBM Web page.

http://www.ibmlink.ibm.com

¶ Send e-mail to:[email protected]

¶ Customers in the U.S. can call:1-800-TIVOLI8 (1-800-848-6548)

¶ Customers outside the U.S. should refer to the Tivoli Customer Web site for customersupport telephone numbers:

http://www.tivoli.com/support/locations.html

When you contact Tivoli Customer Support, be prepared to provide the customer number foryour company so that support personnel can assist you more readily.

The support Web site offers extensive information, including:¶ The Customer Support Handbook (a guide to support services)

You can review the Customer Support Handbook at the following URL:http://www.tivoli.com/support/handbook/

¶ Frequently asked questions (FAQs)¶ Technical information including release notes, redbooks, and white papers

Accessing Publications OnlineYou can access Tivoli publications online, go to

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

The documentation for some products is available in PDF and HTML formats. Translateddocuments are also available for some products.

To access most of the documentation, you need an ID and a password. To obtain an ID foruse on the support Web site, go to

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

Resellers should refer tohttp://www.tivoli.com/support/smb/index.html

for more information about obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” for more information aboutobtaining Tivoli technical documentation.

Ordering PublicationsOrder Tivoli publications online at:

http://www.tivoli.com/support/Prodman/html/pub_order.html

or by calling one of the following telephone numbers:

¶ U.S. customers: (800) 879–2755

¶ Canadian customers: (800) 426–4968

ixGetting Started Guide

x Version 1 Release 1

Introduction

In a Storage Area Network (SAN), storage devices connect to host systems through afibre-based fabric. SAN protocols support this environment. Managing a SAN requires a toolthat understands these protocols and this environment. Tivoli Storage Network Managerfulfills this requirement.

Tivoli Storage Network Manager runs on a Windows 2000™ Advanced Server and interactswith your SAN. See Figure 1. Tivoli Storage Network Manager agents running on themanaged host systems use industry standard inband and outband protocols that enable TivoliStorage Network Manager to provide the following functions:

¶ Manage Networks: This component discovers, displays, and monitors the SAN.

¶ Manage LUNs: This component controls the assignment of SAN storage to the hostsystems.

¶ Manage File System Policies: This component monitors and extends the host filesystems.

TivoliStorageNetworkManager

Database

Host(Agent)

Host(Agent)

Host(Agent)

SAN

Figure 1. Tivoli Storage Network Manager Interacting with a Storage Area Network

1

1Getting Started Guide

1.In

trod

uctio

n

Manage NetworksThe Manage Networks component of Tivoli Storage Network Manager discovers the SANtopology. The topology displays graphically on the Tivoli NetView Console. NetViewenables you to also manage your Internet Protocol (IP)-based LANs and wide area networks(WAN)s. You can view the total physical SAN topology. You can also view the SANlogically from the perspective of devices, hosts, and zones. See “Viewing the Network” onpage 19 for examples of these views.

The Manage Networks component also monitors and displays the properties and status ofSAN devices, supports event forwarding such as forwarding Simple Network ManagementProtocol (SNMP) Trap events to NetView, and enables you to launch vendor devicemanagement applications. All these functions are available from the Tivoli NetView Consoleas described in “Working with Network Devices” on page 33.

Manage LUNsA SAN allows multiple host systems to share disk storage subsystems. Manage LUNsenables you to control the assignment of disk storage subsystem resources (LUNs) to hostsystems in your SAN. The Tivoli console is your interface to this function. See “ManagingLUNs” on page 45 and “Viewing Storage Devices” on page 54.

Manage LUNs supports IBM and non-IBM disk drives. The disk drives supported includeJBODs (Just a Bunch of Disks), RAID devices, and intelligent disk subsystems such as theIBM Enterprise Storage Server (ESS). Check the following uniform resource locator (URL)for the currently supported disk drives: http://www.tivoli.com/support/san

Manage File System PoliciesManage File System Policies enables you to monitor and extend the capacity of filesystems in your SAN. You establish policies at the domain, host, host group, or individualfile system level. You can also cause automatic extension of file systems that are nearingtheir maximum capacity. You do this by defining a threshold for the resource you want tomonitor. See “Managing File System Policies” on page 59 for information on how to managefile systems policies.

2 Version 1 Release 1

User Interface Concepts

You access the Manage Networks function from the Tivoli NetView console. You access allother functions from the Tivoli Console. This chapter provides overviews of both consoles.

Tivoli NetView Console OverviewThe Tivoli NetView Console provides a powerful graphical interface for managing IP-basedLANs and WANs. Tivoli Storage Network Manager extends this interface to the SANenvironment. See Figure 2.

The major elements of the console interface are the:¶ Menu bar¶ Standard Toolbar¶ Submap Window¶ Status Filter Toolbar¶ Status Bar

These are explained on the following pages.

Figure 2. Tivoli NetView Console

2


2.U

serIn

terfaceC

on

cepts

Menu Bar

The menu bar (Figure 3) is at the top of the console. The File, Edit, Object, Submap, View,Monitor, Test, Tools, Options, Windows, and Help selections are standard NetView menuchoices. The Storage Net Mgr menu item provides access to the Tivoli Storage NetworkManager functions, see Figure 4.

SAN PropertiesDisplays properties for a selected SAN device. See “Working with DeviceProperties” on page 38 for examples of using this function.

Launch ApplicationLaunches a vendor management application for a selected SAN device. See“Launching Network Device Applications” on page 39 for examples of using thisfunction.

Configure AgentsTakes you to the Tivoli Storage Network Manager Agent Configuration dialog whereyou can define and observe the agents. For more information, see “Configuring theAgents” on page 15.

Configure ManagerTakes you to the Tivoli Storage Network Manager Configuration dialog where youcan configure the discovery polling operations. For more information, see“Configuring the Polling Information” on page 17.

Help Displays the Tivoli Storage Network Manager online help as described in “OnlineHelp in the Tivoli NetView Environment” on page 7.

Standard Toolbar

The Standard Toolbar (Figure 5) is just below the Menu Bar. There is an input field on theleft side and another on the right. The input field on the left is called the find input field.You use this field to find objects within a submap. The field on the right is called the

Figure 3. Menu Bar

Figure 4. Storage Net Mgr Menu

Figure 5. Toolbar


property tips field. You use it to select the properties displayed when the cursor rests on asymbol in the submap. See “Status in the Submap Graphical View” on page 34, for anexample of using this field

Submap Window Graphical ViewNetwork information is stored in submaps. The root (highest level) submap is displayedgraphically in the submap window (Figure 6) when you start Tivoli Storage NetworkManager. As you can see, there are three symbols in the root submap. The IP Internet andSmartSets symbols apply to submaps for your IP-based networks. The Storage AreaNetwork symbol applies to the submap for your SAN.

If you double-click on a symbol in the submap window, its submap (child submap) isopened and displayed in the submap window. You can repeat this process to navigatethrough your entire network. There are many examples of this in “Viewing the Network” onpage 19.

Figure 7 illustrates the Submap Stack and the Child Submap Area portions of the submapwindow. The submap stack runs vertically on left side of the submap window. It containssymbols that represent the parent submaps you have already opened. Double-click on asymbol in the submap stack to cause its submap to be opened again. The bottom symbol inthe submap stack contains the symbol for the currently displayed submap. The child submaparea runs horizontally along the bottom of the submap window. It contains the symbols forthe child submaps previously opened from the currently displayed submap.

Figure 6. Submap Window Graphical View

Figure 7. Submap Stack and Child Submap Area


2.U

serIn

terfaceC

on

cepts

Submap Window Explorer ViewIn addition to the previously described graphical view of the submap, you can open anexplorer view as shown in Figure 8. To open this view, select Window and then SubmapExplorer on the Tivoli NetView console menu.

This window follows the Windows Explorer format. Click on a (+) plus sign in the left paneto expand the items. Click on a (-) minus sign to compress the items. Click on a symbol inthe left pane to cause its submap to appear in the right pane. See “Host Centric View” onpage 25 for examples of using the explorer view.

Status Filter Toolbar

The status filter toolbar (Figure 9) is a series of colored buttons running vertically to theright of the submap window. Each button represents a certain status. Click one of thecolored buttons to cause symbols of that color to be hidden on the submap graphical andexplorer submap views. See “Working with Status” on page 33 for more examples.

Status Bar

Figure 8. Submap Window

Figure 9. Status Filter Toolbar

Figure 10. Status Filter Toolbar


The status bar is located on the bottom of the console. Its contents vary dynamically. It cancontain status of an object, a description of a menu item, or a status message.

Online Help in the Tivoli NetView EnvironmentYou access online help for the Tivoli Storage Network Manager by selecting Storage NetMgr and then Help from the Tivoli NetView console menu. This help is shown in Figure 11.

You access help for a specific Tivoli Storage Network Manager dialog by clicking on theHelp button in that dialog. See Figure 12 for an example of how dialog help is presentedalongside the dialog.

Tivoli NetView also has online help. You access NetView help by selecting Help on theTivoli NetView console menu. See Figure 13 on page 8 for an example of NetView help.

Figure 11. Storage Network Management Help

Figure 12. Storage Network Management Dialog Help


2.U

serIn

terfaceC

on

cepts

You access help for a specific Tivoli NetView dialog by clicking on the Help button in thatdialog. See Figure 14 for an example of NetView dialog help.

Symbols used by Tivoli Storage Network ManagerYou will encounter new symbols as you display more of the network. If you want to see allthe symbols used, right click on any symbol and then click on Object Properties as shownin Figure 15 on page 9.

Figure 13. NetView Help Table Of Contents

Figure 14. NetView Dialog Help


This will bring cause the Object Properties panel to display as shown in Figure 16 . Clickon the Type tab to see all the symbols used by Tivoli NetView and by Tivoli StorageNetwork Manager.

When a symbol is displayed in the submap, its name is displayed along side it as shown inFigure 17

Figure 17 shows two disk devices in the submap graphical view. Notice that they haveunique names. These names are derived from the ASCII information retrieved from thedevices. Also notice that one of the names has (%) percent signs in it. The % sign indicatesthat the retrieved device name information contained an ASCII character that is notdisplayable. The two characters after a % sign are the hexadecimal representation of theundisplayable character.

Figure 15. SAN Symbols

Figure 16. SAN Symbols

Figure 17. Device Name


2.U

serIn

terfaceC

on

cepts

Tivoli Console OverviewThe Tivoli Console is the role-based graphical user interface (GUI) for performing tasks thatuse Tivoli management software. The console presents only the tasks that are relevant toyour particular role. The console enables you to perform tasks without having to understandthe details of the underlying software. The Tivoli Console also provides consistent controlsand behaviors across tasks and includes embedded user assistance.

A role is a job function, such as “software distributor,” that identifies the tasks and theresources that are available to you. If you have multiple duties, you may be assignedmultiple roles. A task represents one or more Tivoli software components that run as anindependent entity to accomplish your work.

Layout of the Tivoli ConsoleFigure 18 shows an example of the Tivoli Console.

The key components of the Tivoli Console include the following:

Banner areaThe area between the title bar and the menu bar that can serve as a Web browser. Asystem administrator can customize this optional area to include relevant informationfor a particular organization. For example, this area could contain a role description,a company logo, or links to Internet sites.

PortfolioA container for the tasks that are relevant for a given role. When open, the portfoliodisplays within the Tivoli Console to the left of the work area. When closed, theportfolio is indicated by the portfolio handle.

Bannerarea

TivoliAssistant

Work area

Taskbutton

Status bar

Portfolio

Taskbar

Figure 18. Key components of the Tivoli Console


Status barA bar located below the work area that is divided into two sections. The section onthe left contains information about the object over which the mouse pointer ishovering. The section on the right contains a progress indicator or status informationabout the task that is running. To lengthen one section of the status bar and shortenthe other, drag the sectional divider to the left or to the right.

TaskbarA bar located at the bottom of the window that contains a button, called a taskbutton, for each running task. When you right-click the background of the taskbar,the context menu for the taskbar opens.

Task buttonA button on the taskbar that represents a task that is running. A task might havemultiple windows associated with it. When you click a task button, the windowassociated with the task opens in the work area. When you right-click a task button,the context menu for that task opens. Each task button also includes a small iconthat conveys the current status of the task.

Work areaThe area in which the GUI for a task is displayed. This area does not include theportfolio and the Tivoli Assistant.

Tivoli AssistantThe place to go for answers to your questions. The Tivoli Assistant is opened by thequestion mark located on the far right of the toolbar or in the upper right of anydetached window. When it is open, the Tivoli Assistant displays within the TivoliConsole to the right of the work area. It provides contextual help information for thetask that you are performing, as well as reference information.

Note: To close the Tivoli Console while a Tivoli Kernel Services Administration task isopen, click the ″X″ (located in the far right corner of the Tivoli Console title bar)once to close the task and click the ″X″ again to close the Tivoli Console itself.

Locating and Performing TasksYour tasks are placed in task groups. The task groups display in the portfolio of the TivoliConsole.

To view the list of tasks in a task group, click the task group. This will cause the task groupto expand. Then, click on a task within that group. Clicking a task opens a dialog thatguides you through an activity.

When presented with a list of resources, you can right–click a resource to open a contextmenu. The context menu displays only those actions that are relevant for that resource.

The menu and the toolbar are task-specific and contain the available menus and tools for thetask that is active in the work area. However, several menu items and tools remain the samefor all tasks.

In addition to the items listed here, some of the applications using the Tivoli Console makeuse of a field description area. However, this area is not being used by Tivoli KernelServices in this release.


2.U

serIn

terfaceC

on

cepts

Embedded User AssistanceThe Tivoli Console offers an important new feature, embedded user assistance through theuse of the Tivoli Assistant.

You can open the Tivoli Assistant by one of the following:

¶ Click the question mark located on the far right of the toolbar of the Tivoli Console orin the upper right of a detached window.

¶ Select Open Tivoli Assistant from the Help menu item.

¶ Press F1.

The Tivoli Assistant replaces the User’s Guide that accompanies most software products.Information about Tivoli Kernel Services, the Tivoli Console, and the Tivoli Assistant itselfis all included in the Tivoli Assistant. When you install an application, applicationinformation is integrated into the Tivoli Assistant as well.

The topic organizes the information in the Tivoli Assistant. When you open the TivoliAssistant, the information topic for your current task will be displayed to the right of thework area. See Figure 19.

You can search the information, review overview information, or view the table of contentsand index. You can also change the window size, detach the window from the work area, orprint the information. You select these tasks from the Tivoli Assistant toolbar. SeeFigure 20on page 13.

Tivoli Assistanttoolbar

TivoliAssistant

Figure 19. Tivoli Console with Tivoli Assistant open


Tivoli Console Guided TourBefore you begin using the Tivoli Console, you might be interested in taking a Web-basedguided tour to reinforce the concepts presented in this chapter. You can download the guidedtour from the following Web site:

http://www.tivoli.com/products/demos

Previous/Next Snap

Table of Contents

Topic Index

Message Index Search

Print

Detach/Reattach

Figure 20. Tivoli Assistant toolbar


2.U

serIn

terfaceC

on

cepts

Starting and Configuring

This chapter provides the basic information on how to start the Tivoli Storage NetworkManager functions and how to configure agent operations.

Starting¶ Start the Manage Networks function.

You access this function by clicking on the Tivoli NetView icon on the Windows 2000desktop. The NetView console will appear. You manage your network from the NetViewconsole.

¶ Start the Manage LUNs and Manage File Systems Policies functions.

You access these functions from the Tivoli Console portfolio. You start the TivoliConsole from the Windows 2000 desktop by clicking on the Tivoli Console icon.

¶ Start the Tivoli Storage Network Manager Agents

The agents run on the managed host systems in your SAN. Please configure each hostsystem so that these agents are always running. See the Tivoli Storage Network ManagerPlanning and Installation Guide for more information about agents.

Configuring the AgentsTivoli Storage Network Manager uses agents to discover your SAN and monitor its status.You can view the agents on the Agent Configuration panel, see Figure 21 on page 16. Youaccess this panel by selecting Storage Net Mgr and then Configure Agents on the TivoliNetView console menu. Notice that the top half of the panel shows the Tivoli StorageNetwork Manager Agents and the bottom half shows the SNMP Agents.

3


3.S

tarting

and

Co

nfig

urin

g

¶ Tivoli Storage Network Manager Agents: These agents discover information abouteach host system and its local storage as well as all of the SAN observable through thatsystem’s host bus adapter. Host bus adapters gather the information. The adapters useinband discovery protocols that flow across the fabric. This panel should show one agenton each host system. Each agent should be in the Contacted state. Refer to the TivoliStorage Network Manager Planning and Installation Guide if you have a system withoutan agent.

¶ SNMP Agents: If your Fibre Channel switch does not support inband discovery, thenyou need to configure Tivoli Storage Network Manger to attempt outband discovery.Outband discovery uses SNMP queries on a TCP/IP connection. Use the following stepsconfigure outband discovery.

1. Click the Add button. This will cause the Enter IP Address or Name dialog toappear, see Figure 22.

2. Type in the IP Address or Name of the switch. In this example, the simpleunqualified name is fabric3a. You can also enter a fully qualified name such asfabric3a.rchland.ibm.com.

3. Click the OK button to update the panel, seeFigure 23 on page 17.

Figure 21. Agent Configuration

Figure 22. Configure SNMP Agent Configuration


Notice that the State field for the SNMP Agent in Figure 23 now shows that the SNMPAgent on fabric3a is Contacted. If you do not see a Contacted state, then verify that theaccuracy of the name or address.. If the name or address is correct, then verify that theswitch actually supports outband discovery.

Do you know if your switch supports inband or outband discovery?The Tivoli web site http://www.tivoli.com/support/san/tsnm_devices.html shows thesupport of many common switches. Contact your vendor if your switch is not on the list.

Configuring the Polling InformationWhen you start Tivoli Storage Network Manager, it discovers the SAN by polling all theagents. You schedule future polling by selecting Storage Net Mgr and then ConfigureManager on the Tivoli NetView console menu. This will bring up the Storage Net MgrConfiguration panel shown in Figure 24 on page 18.

Figure 23. Configure SNMP Agent Configuration


3.S

tarting

and

Co

nfig

urin

g

As shown in Figure 24, you select that polling take place now or in the future. To poll now,click the Poll Now button.

To schedule future polling, make your selections and click the OK button.

To stop future scheduled polling, enter 0 in the Poll Every field.

The Clear History button resets information that is gathered from previous polling. Forexample, if a device is reported as missing because it no longer detected, then clearing thehistory will stop it from being reported as missing. Before using the Clear History functionfor the first time, you should read “Working with Status” on page 33.

Performance Considerations

¶ The time required to complete the polling depends on the size of your SAN.

¶ The topology information is stored in a DB2 database. For peak performance, youshould optimize that database periodically as described in ″Tips on Running with DB2″of the Tivoli Storage Network Manager Planning and Installation Guide.

Figure 24. Storage Net Mgr Configuration Panel


Viewing the Network

When NetView starts, it displays the root submap, see Figure 25. The IP Internet andSmartSets symbols are the standard Tivoli NetView symbols for IP-based submaps.

The Storage Area Network symbol represents the Storage Area Network submap.

To start graphically displaying your Storage Area Network, click on the Storage AreaNetwork symbol.

If you prefer to view the network in the submap explorer view, click on Window and thenon Submap Explorer in the NetView console menu. Figure 26 on page 20 is an example ofthe explorer view.

Figure 25. Root Submap

4


4.V

iewin

gth

eN

etwo

rk

To see both the graphical view and the explorer view, click on Window and then on TileHorizontally in the console menu. Figure 27 shows both views.

Figure 28 on page 21 shows the submap for the storage area networks. To see this submap,click on the Storage Area Network symbol in Figure 25 on page 19.

Figure 26. Explorer View

Figure 27. Horizontal Tile


Notice that the Storage Area Network submap (Figure 28) contains symbols for thefollowing:

¶ SAN Symbols You will see one symbol for each SAN. In this example there are twoSANs. If you click on one of those symbols, you will begin to explore that SAN. Noticethat we let the cursor rest on the left symbol so that the property tips told us that thesymbol type is TivoliSNM:San. Double-click on the SAN-0006062920100F symbol toview its submap as shown in “SAN View”. The 0006062920100F is actually the SANname as reported by the fabric.

Do you see a Virtual SAN? – If you see a SAN named Virtual SAN:100, that meansTivoli Storage Network Manager inferred the existence of a SAN. This can occur whenthe fabric did not provide enough information. This may also occur if you have recentlycombined two SANs. If that is the case, try clearing the history as described in“Clearing the Status History” on page 36.

¶ Device Centric View Symbol: You may have multiple SANs with many storagedevices. The Device Centric View enables you to see all the storage devices and theirlogical (potential) relation to all the hosts. This view does shown the switches or otherconnection devices. Double-click on the Device Centric View symbol to view itssubmap, see .

¶ Host Centric View Symbol: You may have multiple SANs with many host systems.The Host Centric View enables you to see all the host systems and their logical relationto local and SAN attached storage devices. Double-click on the Host Centric Viewsymbol to view its submap as shown in “Host Centric View” on page 25.

SAN ViewSee Figure 29 on page 22. Notice that you can choose a Topology View or a Zone View ofthe SAN. The Topology View displays the entire SAN while the Zone View displays theSAN as a grouping of zones.

Figure 28. Storage Area Network


4.V

iewin

gth

eN

etwo

rk

Double-click on the symbol for the view you want. The Topology View is described next.For a description of the Zone View see “Zone View” on page 24.

Topology ViewThe topology view (see Figure 30) presents two types of symbols:¶ One symbol (in the center) representing all the SAN connection elements.¶ One symbol for each segment, where a segment consists of a switch and the devices

directly connected to it.

To examine the contents of fabric3a, double-click on its symbol in the submap. See theresults in Figure 31 on page 23.

Figure 29. SAN View

Figure 30. Topology View


Let us examine the display shown in Figure 31.¶ The top portion shows connections to two host systems.¶ The lower left portion shows a connection to a Rogue Host System. A Rogue Host can

compromise the security of your storage because it does not have a Tivoli StorageNetwork Manager agent. You will also see this rogue host when using the ManageLUNs function, see “Displaying Host Information” on page 50.

¶ The lower right portion shows a connection to a switch named fabric2a.¶ Connections to two disk enclosures are shown to the left and right of fabric3a.

If you click on the symbol for the disk enclosure on the right, you will see its disks asshown in Figure 32 on page 24.

Figure 31. Fabric3a Segment Display


4.V

iewin

gth

eN

etwo

rk

As you can see, we have just followed one path through the network topology. At any point,you could pursue another path simply by clicking on one of the symbols in the submapstack.

Zone ViewIf your SAN contains switches that support the Fibre Channel GS-3 standards, then TivoliStorage Network Manager will retrieve and display the configured zones. To select the ZoneView, double-click on the Zone View symbol shown in Figure 29 on page 22. This willdisplay a symbol for each discovered zone, see Figure 33 on page 25.

Not sure if your switch supports Fibre Channel GS-3 Standards?The Tivoli web site http://www.tivoli.com/support/san/tsnm_devices.html shows thesupport of many common switches. If your switch does not support GS-3, you may stillbe able to view its zoning information by launching a switch application, see“Launching Network Device Applications” on page 39.

Figure 32. Ring Segment Display


Figure 33 shows that six zones were discovered for this SAN. To see the contents of a givenzone, double click on its symbol. Figure 34 shows the contents of Zone3onlyn.

Figure 34 shows that this zone consists of a two disks and a host system.

Host Centric ViewThe Host Centric view presents the relationship between host systems and their local andSAN attached storage. This is a ’logical view’ because the intervening switches and otherconnection devices are not shown. Since this is a logical view, you may prefer to observethis relationship with the submap explorer. To access the submap explorer host centric view,

Figure 33. Zone View

Figure 34. Zone View


4.V

iewin

gth

eN

etwo

rk

right click on the Host Centric View symbol, and then click on Explore as shown inFigure 35.

The host centric explorer view is shown in Figure 36. Notice that the right pane shows thatthere are three host systems.

Double-click on the host symbol for sanza.rchland.ibm.com in the right pane of Figure 36to view that host’s operating system, seeFigure 37 on page 27.

Figure 35. Host Centric Explorer View

Figure 36. Host Centric View — Hosts


Double-click on the Windows 2000 operating system symbol in Figure 37 to view the filesystems, see Figure 38.

Notice in Figure 38 that the NTFS file system is installed on all drives of this system.Double-click on a the HostFileSystem: H symbol in the right pane to display its LogicalVolumes, see Figure 39 on page 28.

Figure 37. Host Centric View — Operating System

Figure 38. Host Centric View — File Systems


4.V

iewin

gth

eN

etwo

rk

Click on the Logical Volume: H symbol in the right pane of Figure 39 to view the Diskstorage device, see Figure 40.

Device Centric ViewThe Device Centric view presents the logical relationship between storage devices and hostsystems. This view is referred to as a ’logical view’ because the intervening switches orother connection devices are not shown. Since this is a logical view, you may prefer observeit using the submap explorer as shown in this section. To select the submap explorer devicecentric view, right click on the Device Centric View symbol and then click on Explore asshown in Figure 41 on page 29.

Figure 39. Host Centric View — Logical Volumes

Figure 40. Host Centric View — Disks


As shown in Figure 42, this view contains a symbol for each storage device.

If you double-click on one of the Disk symbols in the right pane in Figure 42, you will seethe associated LUNs as shown in Figure 43.

Figure 41. Device Centric Explorer View

Figure 42. Device Centric View

Figure 43. Device Centric View – LUNs


4.V

iewin

gth

eN

etwo

rk

Double-click on the LUN symbol in the right pane of Figure 43 on page 29 to display theassociated hosts, see Figure 44.

Double-click on the sanxf.rchland.ibm.com host symbol in Figure 44 to display itsoperating systems, see Figure 45.

In Figure 45, notice that this host is running the Windows NT operating system. If youdouble-click on the NtOperatingSystem symbol, you will see its file systems as shown inFigure 46 on page 31.

Figure 44. Device Centric View – Hosts

Figure 45. Device Centric View – Operating System


In Figure 46, notice that this host has NTFS on drives C and D.

Figure 46. Device Centric View — File Systems


4.V

iewin

gth

eN

etwo

rk

Working with Network Devices

“Viewing the Network” on page 19 explained how to navigate through the SAN topology toa specific network device. This section explains how to work with device status andproperties and how to launch device management applications.

Working with Status

The Use of Color to Indicate StatusA symbol’s color reflects its status. For example, the color green indicates normal operation.The color red indicates a critical failure. See Table 5 for the color assignments.

Table 5. Symbol StatusStatus Status Meaning Symbol

ColorConnection Color

Unknown Status not determined. Blue Black

Normal Normal operational state. Green Black

Marginal Impaired, but still functional. Yellow Yellow

Critical Not functioning or missing. Red Red

Unmanaged Not monitored. See explanation below. Wheat (tan) Black

Acknowledged Not monitored. See explanation below. Dark Green Black

¶ Unmanaged: Objects are normally managed, which means that they are monitored forchanges in topology and status. The color assigned to an object symbol according to itsstatus. This status propagates up the submap tree. To stop managing an object, rightclick on its symbol in the submap. Then select Unmanage from the context menu. Itssymbol will change to the color for unmanaged objects and will remain that color for aslong as the object is unmanaged. To start managing the object again, right click on itssymbol and select Manage from the context menu.

¶ Acknowledged: You can change an object’s status to acknowledged while you aretrying to determine why it was reported as critical, or marginal, or unknown. This willtell other people that someone is aware of the problem. To do this, right click on theobject’s symbol in the submap and select Acknowledge from the context menu. Asymbol will remain in acknowledged state until another problem occurs or until youunacknowledge it. To unacknowledge an object, right-click on its symbol in the submapand select Unacknowledge from the context menu.

How Status PropagatesIf the symbol represents a device, then the status shown is that of the device. If the symbolrepresents a submap, then the status shown reflects the status of all the objects in its childsubmaps. Table 6 on page 34 shows the default rules used to propagate status up from the

5


5.W

orkin

gw

ithN

etwo

rkD

evices

child submaps.

Table 6. Default Status PropagationObject Status Condition of Symbols in the Child Submap

Unknown No symbols with status of normal, critical, marginal or unmanaged.

Normal All symbols are normal or acknowledged.

Marginal Any of the following:¶ All symbols are marginal¶ Normal and marginal symbols¶ Normal, marginal and critical symbols

Critical At least one symbol is critical and no symbols are normal.

Status in the Submap Graphical ViewSee Figure 47 for an example of symbol status in the graphical view. If the property tipsselection (upper right corner of the display) is Status as shown here, the status will also bedisplayed in the status bar (bottom of the display) and in the property tips pop up wheneveryou rest the cursor on an object’s symbol. Also if you place the cursor over one of the colorbuttons in the status filter tool bar, the meaning of that color will be displayed.

If your property tips selection is not set to Status, you can select it from the property tipsdrop-down list. See Figure 48 on page 35.

Figure 47. Status in the Submap Graphical View


Status in the Submap Explorer ViewFigure 49 shows status information in the explorer view. This is different than in thegraphical view. For example, the tool tip menu selections do not apply to the explorer view.And, placing the cursor over a symbol will not cause its tool tip to appear. In the explorerview, the status information displays in the right pane.

The status displayed in Figure 49 is optimized for Tivoli Storage Network Manager. Youselect this view from the drop-down menu shown on the left side of Figure 50 on page 36.

Figure 48. Property Tips Selection

Figure 49. Status in the Submap Explorer


5.W

orkin

gw

ithN

etwo

rkD

evices

Clearing the Status HistoryTivoli Storage Network Manager maintains a history of discoveries and uses that history todetermine status. For example, if previously discovered device disappears from the currentdiscovery, that device is assigned critical status. If you want to stop having that devicereported as critical, you need to clear the history. To do this, select Storage Net Mgr andthen Configure Manager on the console menu. This will cause the Storage Net MgrConfiguration dialog to appear, see Figure 51. Then click the Clear History button. Thiswill clear the history for all devices and rebuild the submap views. Note that if a LUN thatis part of a LUN Group (see “Defining LUN Groups” on page 62) is reported as missing andyou clear the history, you will have to reenter that LUN as part of the LUN Group should itappear again.

Status FilteringIf you have many symbols on your screen, you may want to filter some of them out. Thiswill enable you to concentrate on other symbols. For example, you can filter out all the

Figure 50. Toolbar Status Selection

Figure 51. Clearing the History


green (normal) symbols in order to concentrate on the others. To filter out a particular set ofsymbols, click one of the color buttons in the status filter bar or the right side of the display.Click that button again to cause the symbols of that color to appear again. Figure 52 shows asubmap with many symbols.

Click the Normal status button in the filter tool bar. This will filter all the symbols ofnormal (green) status from the submap, see Figure 52.

Figure 52. Filtering Status

Figure 53. Filtering Normal Status


5.W

orkin

gw

ithN

etwo

rkD

evices

Note that symbols on the Host Centric View and the Device Centric view are assigned theUndefined status and color. This is because these are not topological views and status is notmeaningful or propagated in these views.

Working with Device PropertiesTivoli Storage Network Manager stores the information it discovers about devices in theSAN. You access this information by selecting a device (click on its symbol) in the submap.Then select Storage Net Mgr and SAN Properties on the console menu. Figure 54 showsthe properties for a Fibre Channel switch named fabric3a.

Figure 55 shows the switch properties. If you had selected a storage device, then you wouldhave seen the properties unique to a storage device. To get detailed information about theproperty fields displayed, click the Help button in the lower right corner of the propertiesdisplay.

Notice that Figure 55 also contains a Connection selection. If the Connection selection doesnot appear initially, wait a few seconds for the information. Click Connection in the leftpane to see this information, see Figure 56 on page 39.

Figure 54. Displaying SAN Device Properties

Figure 55. Property Display


Click the Help button for a detailed explanation of all the fields in these displays. Forexample, the State field shown in Figure 56 controls the Status as described in followingtable.

Table 7. Connection StatesState Meaning Status

New New device detected. Clear History will change this to Normalstate.

Normal

Normal Clear History was performed on a New device. Normal

Missing Previously detected device is no longer detected. Clear Historyremoves this device from all submaps and displays.

Critical

Suspect Device previously reported as Missing has been detected again.Clear History changes this to Normal state.

Marginal

ModifiedAttribute

One or more attributes have changed. Clear History changes thisto Normal state.

Normal

By default, Tivoli NetView collects information about all devices it can reach on a TCP/IPconnections. For example, if you have a Fibre Channel Switch that also support a TCP/IPconnection, then Tivoli NetView will use TCP/IP to gather information about that switch.You view this information by right clicking on a device’s symbol on the Tivoli NetViewconsole then clicking on Object Properties in the resulting context menu. Note, howeverthat this information will be less accurate as that are gathered by Tivoli Storage NetworkManager.

Launching Network Device ApplicationsSome network devices, such as Fibre Channel switches, contain browser based applicationsto assist in the management and configuration of those devices. To launch a deviceapplication from the console menu, click on its symbol in the submap. Then click onStorage Net Mgr and then Launch Application on the console menu, see Figure 57 onpage 40. If the Launch Application selection is greyed out, the device has not identified amanagement application to Tivoli Storage Network Manager. If you know that the devicehas a management application, there is another way to launch it. See “An AlternateLaunching Technique” on page 41.

Figure 56. Property Display


5.W

orkin

gw

ithN

etwo

rkD

evices

Figure 58 shows the management application launched for a Fibre Channel switch namedfabric3a.

As you can see, this particular application provides several useful functions. For example,click on Fabric Topology. See Figure 59 on page 41.

Figure 57. Launch an Application

Figure 58. Launch an Application


An Alternate Launching TechniqueSome SAN devices have management applications, but do not support the architecture foridentifying their application name. You cannot launch these applications from the LaunchApplications context menu. If you have such a device, you can still get Tivoli NetView tolaunch the application. To do this, right click on a device symbol on the NetView consoleand then select Object Properties from the context menu. This will bring up the ObjectProperties dialog, see Figure 60.

Here are the steps for identifying the management application in Figure 60:1. Click on the Other tab in the upper right corner.2. Select LANMAN from the pulldown in the upper left corner.3. Check the IsHTPManged box.4. Enter the URL for the device’s Application in the Management URL field.5. Click the Verify button, the Apply button, and then the OK button.

You can now launch this application by right clicking on the device’s symbol and thenselecting Management Page from the context menu, see Figure 61 on page 42.

Figure 59. Fabric Application — Topology

Figure 60. Object Properties


5.W

orkin

gw

ithN

etwo

rkD

evices

In this example, if you clicked on Management Page, you would access the sameManagement Application shown in Figure 58 on page 40.

Using the Tivoli NetView Event BrowserYou can use the Tivoli NetView Event Browser to view events in the Tivoli NetView eventdatabase. Since Tivoli NetView can manage both IP-based networks and SANs, the eventdatabase may contain events for both types of networks.

The following types of events may be found in the event data base,¶ Conditions that are detected by NetView, such as a device going to critical status.¶ SNMP traps sent from devices on the IP network, such as from an IP/Token Ring

Bridge.¶ SNMP traps sent from SAN devices, such as from a Fibre Channel Switch.¶ SNMP traps sent from Tivoli Storage Network Manager.

Refer to the Tivoli Storage Network Manager Planning and Installation Guide or the TivoliStorage Network Manager online help for information on how to configure the sending ofSNMP traps. The online help also contains a description of all SNMP traps sent by TivoliStorage Network Manager.

To start the Tivoli NetView Event Browser, select Monitor–>Events–>All on the consolemenu. See Figure 62 on page 43. Note that this display changes as new events occur.

Figure 61. Launching via NetView


To access the basic features of the Event Browser, right click on an event. This will bring upa selection menu, see Figure 63

Click Event Details to see more information about an event, seeFigure 64 on page 44.

Figure 62. Event Browser

Figure 63. Event Browser Features


5.W

orkin

gw

ithN

etwo

rkD

evices

Figure 64. Event Browser Features


Managing LUNs

Manage LUNs allows administrators to create secure, logical connections between hostsystems and disk storage. Administrators can view all of their SAN-attached disk storage asa single, virtual pool. Administrators can dynamically add or subtract storage to or from ahost as needed.

LUN is an acronym for Logical Unit Number. It is provided by a storage device to identifyan addressable portion of the storage device. The LUN is a number that a host uses toaccess a logical drive. For example, a JBOD (Just a Bunch of Disks) could have 8 drawersof disks and would be presented as 8 LUNs. In this case, the LUNs have a one-to-onerelationship with the physical drives. In other cases, that will not be true. For example, in aRAID storage device, 8 disks could be configured to be a single RAID5 composite. In thiscase, it would appear as one LUN.

With Manage LUNs, disk storage resources can be IBM or non-IBM disk subsystems. Thesedisk can be simple JBOD disk drives, RAID (Redundant Array of Independent Disks), orintelligent disk subsystems such as the IBM Enterprise Storage Server (ESS).

For RAID devices, Tivoli Storage Network Manager supports both hardware RAID andsoftware RAID. Hardware RAID LUNs look like ordinary LUNs. Tivoli Storage NetworkManager manages these LUNs like any other LUN. For software RAID, the LUNs whichmake up the RAID device appear as separate LUNs to Tivoli Storage Network Manager.Each LUN must be allocated to the same managed host (or set of managed hosts).

For disk subsystems such as the IBM Enterprise Storage Server (ESS), a LUN is a logicaldisk drive. The ESS can be configured to have many LUNs. If you want Tivoli StorageNetwork Manager to manage ESS LUNs, the ESS must be configured for that support. TheESS LUNs that you want Tivoli Storage Network Manager to manage must be madeavailable to all the managed hosts on the SAN. This is also true for other intelligent storagesubsystems like the EMC Symmetrix. For information on ESS configuration, see the ESSdocumentation. For information on EMC Symmetrix configuration, see the EMCdocumentation.

In order to understand why it is necessary to control access to the storage devices on theSAN, it is important to understand the behavior of operating systems. Operating systemssuch as Windows NT or Windows 2000 take whatever storage devices they see over theirchannels and put their own signature on the disks. This can cause other operating systemssuch as AIX or Solaris (which handle their own storage on the SAN), to lose access to thatdata.

When the storage devices are connected to the SAN, you have five possible choices torestrict access to the devices:

6


6.M

anag

ing

LU

Ns

¶ Hardware zoning¶ Software zoning¶ Hardware LUN masking¶ Software LUN masking¶ A combination of the above

Zoning allows you to partition the various switch ports into groups so that only the devicesattached to those port groups (such as HBAs or disk subsystems) can access each other.

Hardware zoning groups the devices in a zone based on the physical fabric port number. Itdoes not depend on which device is attached but to which port it is attached and in whichzone this device is configured.

Software zoning is the grouping of World Wide Numbers (WWNs). Software zoning isimplemented within the switch’s internal name server using node and port WWNs to definethe members of the zone.

LUN masking controls access to the LUNs themselves by setting up access lists of hosts andLUNs. When a host requests access to a particular LUN, the list is checked and theoperation is permitted or denied.

Hardware LUN masking is a feature provided by some high-end disk subsystems (forexample, the IBM Enterprise Storage Server). The mechanism is specific to that storagesubsystem.

Software LUN masking can be used to control LUN access on all SAN disk devices, notjust those with hardware LUN masking. This is the support provided by the Manage LUNscomponent of Tivoli Storage Network Manager. A Tivoli Storage Network Manager agent(software) must be installed on every host system with access to that storage so that LUNmasking can be enforced on all the hosts. The agent performs local functions such as LUNmasking and inband discovery on the host. A host with a Tivoli Storage Network Manageragent is referred to as a managed host.

Rogue HostsIf you are using Tivoli Storage Network Manager to securely share storage, a Tivoli StorageNetwork Manager agent must be installed and running on every host system with access tothat storage. This is because Tivoli Storage Network Manager uses LUN masking at the hostto control storage access. A system that does not have this agent installed and running iscalled a rogue host. A rogue host can access storage that is assigned to other hosts andcause data corruption.

Tivoli Storage Network Manager considers a host system a rogue host if it is in one of thefollowing states:

1. Tivoli Storage Network Manager cannot identify the device.

2. There is no agent installed and running on the host system.

3. The host name (also known as the platform name) registered with a switch does notmatch the name of the host system.


4. There is an agent running on the host system, but it appears that the LUN maskingsupport is not enabled when it should be. An example of this is if the device driver isinstalled but not active because the managed host was not rebooted.

The Manage Network console displays each host or unknown device that is determined to bea rogue host. Manage LUNs will not display rogue hosts in state 1, 2, or 3 above. ManageLUNs will display rogue hosts in state 4 (LUN masking support is not enabled when itshould be).

There are two levels for a rogue host condition:

¶ Non–critical event: The Tivoli Storage Network Manager agent is not running on thehost. This means that some information is not available within Tivoli Storage NetworkManager. Specifically, host file system level information is not available and potentially,some device information. This is considered a lower level issue and the events generatedby Tivoli Storage Network Manager are warnings.

¶ Critical event: If the agent is running, it means that the rogue host can potentially accessdata on other devices being managed with Manage LUNs. This is considered a moresignificant issue and Tivoli Storage Network Manager generates critical events.

Rogue host warnings are sent out as SNMP traps and TEC events when a rogue hostcondition is detected. A rogue host condition is detected during a discovery operation orManage LUNs polling. Because Manage LUNs cannot secure the devices from systems notrunning the agent, additional severe rogue host alerts are sent when Manage LUNs isenabled. The time required to detect that a rogue host condition exists depends on the time ittakes for discovery processing and on the specified polling intervals.

It is possible for users to want a rogue host (a machine not managed by Tivoli StorageNetwork Manager) on their SAN. In this case, the user needs to manage the rogue host’saccess to storage to prevent data corruption. You can manage access to storage throughzoning, hardware LUN masking, or other means in order to prevent data corruption.

Rogue Hosts Displayed on the Tivoli NetView ConsoleA rogue host on Manage Networks can appear in two different forms. The first Rogue Hosticon shown below is displayed on the Tivoli NetView console if Tivoli Storage NetworkManager detects a host system and one of the following conditions apply:

¶ The Tivoli Storage Network Manager agent is not running on the managed host

¶ Manage LUNs is enabled but the Manage LUNs device driver is not running on themanaged host

The second icon is shown as an Unknown Device icon but should be treated as a rogue host.This device is detected by Tivoli Storage Network Manager but there is insufficientinformation to identify this device. This object could be a host, disk, or some other type ofdevice. This object needs to be treated as a rogue host because this object could be a host,and therefore could access the storage devices controlled by Manage LUNs. An unknown

Figure 65. Rogue Host Icon – Manage Networks


6.M

anag

ing

LU

Ns

device and rogue host are treated in the same way. That is, the events generated are thesame for a rogue host or an unknown device.

Rogue Hosts Displayed on the Tivoli Console (Manage LUNs)Only managed host systems running the Tivoli Storage Network Manager agent aredisplayed on the Manage LUNs console. A rogue host on the Manage LUNs console appearsas:

Enabling and Disabling Manage LUNsWhen Tivoli Storage Network Manager is installed for the first time, the Manage LUNsfunction will be disabled. To use the Manage LUNs function, you must enable it. Enablingor disabling LUN management has serious consequences for your SAN. You should readthrough the following paragraphs to help you understand the consequences of enabling anddisabling Manage LUNs.

If you have an unmanaged host connected to your SAN, your unmanaged host must becontrolled by some other means so that it only has access to those devices that it shouldhave access to. For example, the unmanaged host’s access to the LUNs could be controlledthrough zoning or hardware masking so that it has no access to the LUNs that are beingcontrolled by Manage LUNs.

If you already have hosts which require access to LUNs on the SAN, you must assign thoseLUNs to those hosts using Manage LUNs immediately after enabling Manage LUNs. Failureto do this will result in the host losing access to that LUN once LUN masking is activated(deployed). This is especially important if you have managed hosts which reboot from aremote storage device. Failure to redo the LUN assignments for such hosts will result intheir being unable to reboot when you try to reboot the hosts.

Note that disabling Manage LUNs can also have serious consequences:

¶ All current LUN assignments will be purged from the Tivoli Storage Network Manager’sdatabase. After a reboot, the host will have access to all the LUNs (hosts other thanAIX). AIX hosts will have access to all the LUNs immediately (no reboot is required).

¶ Also, disabling Manage LUNs might allow hosts to access LUNs that have already beenassigned to other hosts. This can lead to file system corruption. You should consider an

Figure 66. Unknown Device Icon – Manage Networks

Figure 67. Rogue Host Icon – Manage LUNs


alternative means of restricting access to the LUNs before disabling Manage LUNs.Alternative means of restricting access to the LUNs could be the use of zoning orhardware LUN masking.

¶ Disabling Manage LUNs will also disable automatic file system extension (althoughManage File Systems Policies will still be able to monitor file system capacity and issuewarnings when those monitored file systems exceed their thresholds).

For more information on enabling and disabling Manage LUNs, see Tivoli Storage NetworkManager Planning and Installation Guide.

Using Manage LUNsTivoli Storage Network Manager provides an easy to use tool for managing host LUNassignments. You access this tool from the Tivoli Console portfolio. To access the TivoliConsole, double–click the Tivoli Console icon on your desktop and log on. In the portfolio,click Manage Storage Networks, then click Manage LUNs.

As shown in Figure 68, this window displays the hosts and LUNs on your SAN. When youselect a host on the left, the LUNs that are accessible to that host are displayed in theAccessible LUNs table (both assigned and unassigned LUNs). Accessible LUNs means thatall the LUNs that could be assigned to the host are displayed. You can assign, unassign, orreassign LUNs to or from a host. You can also discover hosts and LUNs, refresh the hostsand LUNs view, and remove inactive hosts from the host tree on the left of the pane.

Figure 68. Manage LUNs View


6.M

anag

ing

LU

Ns

Displaying Host InformationTo see information about a host, click on a host in the left portion of the screen. Then clickthe Host Properties button on the right. The host information is displayed in the HostProperties dialog window and provides the following information:¶ Status¶ Current Agent Port¶ Operating System Level¶ Last Status Changed Date¶ Assigned Capacity in MBs¶ Accessible Capacity in MBs

If a rogue host is detected, this will also be displayed in the Host Properties window.

Displaying LUN InformationA LUN is a logical unit number. The LUN IDs are provided by the storage devices attachedto the SAN. This number provides you with a volume identifier that is unique among allhost servers.

The storage that the Tivoli Storage Network Manager manages is the LUN. The LUN is theunit of storage on the SAN which is available for assignment or unassignment to a hostserver.

For RAID devices, a drive group is a set of disk drives that have been configured into oneor more LUNs. For disk subsystems such as the IBM Enterprise Storage Server (ESS), aLUN is a logical disk drive. The ESS can be configured to have many LUNs. If you wantTivoli Storage Network Manager to manage ESS LUNs, the ESS must be configured for thatsupport. The ESS LUNs that you want Tivoli Storage Network Manager to manage must bemade available to all the managed hosts on the SAN. This is also true for other intelligentstorage subsystems like the EMC Symmetrix. For information on ESS configuration, see theESS documentation. For information on EMC Symmetrix configuration, see the EMCdocumentation.

The information about a LUN is composed of the fields listed below. To see informationabout a LUN, click on a LUN in the Accessible LUNs table. Click the LUN Propertiesbutton. The LUN information is displayed in the LUN Properties dialog window andprovides the following information:

Figure 69. Host Properties Window


¶ Vendor ID¶ Product ID¶ Revision Level¶ Serial Number¶ Capacity in MBs

Assigning a LUN to a HostLUNs can be assigned to one or more hosts. If a LUN is assigned to more than one host, itis considered a shared LUN.

To assign a LUN to a host:

¶ Select a host on the left.

¶ Select one or more LUNs that are not assigned to this host from the Accessible LUNstable. These LUNs will have a blank in the Status column. A blank indicates a status ofUnassigned.

¶ Click the Assign LUN button or icon.

The Status column in the Accessible LUNs table will change to Assigned or AssignPending.

Sharing a LUN with another HostA shared LUN is a LUN that has been assigned to two or more hosts. To share a LUN withanother host:

¶ Select a host on the left.

¶ Select the LUN you want to share from the Accessible LUNs table. The Assigned toOther column will indicate Yes if this LUN is already assigned to another host. You cannow share this LUN with the currently selected host.

¶ Click the Assign LUN button or icon.

¶ You will get a message dialog window asking if you want to share the LUN. ClickShare LUN Assignment.

To see a list of hosts that share this LUN:

1. Right–click on the LUN in the Accessible LUNs table.

2. Click Show list of hosts on the pop-up menu.

Unassigning a LUNLUNs can be unassigned from one or more hosts. You can unassign one or more LUNs atone time.

To unassign a LUN:

¶ Select a host from the left pane. The LUNs accessible to that host will be displayed onthe right.

¶ Select the LUN or LUNs you want to unassign.

¶ Check to see that the LUN has a status of Assigned.


6.M

anag

ing

LU

Ns

¶ Click the Unassign LUN button or icon.

The LUN status is changed to Unassigned (blank) or Unassign Pending in the AccessibleLUNs table.

Reassigning a LUNLUNs can be reassigned from one host to another.

Note: You should be aware that when you reassign a LUN from one host to another, thesecond host will be able to view all of the data on the LUN unless you have erasedthe data before reassigning the LUN.

To reassign a LUN to another host:

¶ Select the host in the left pane of the window. The LUNs accessible to the host aredisplayed in the Accessible LUNs table.

¶ Select the LUN you want to reassign.

¶ Click the Reassign LUN button or icon. A Reassign LUN dialog window is displayed.

¶ A list of hosts is displayed in the Reassign LUN dialog window. Select a host you wantto reassign the LUN to in the host drop-down list.

¶ Click Reassign LUN.

The LUN is reassigned to the new host. The LUN status changes as the LUN is unassignedand then assigned to the selected host.

Discovering Hosts and LUNsWhen Tivoli Storage Network Manager is first started, a discovery is done for the hosts andLUNs on the SAN.

If you add or remove hosts and LUNs to or from the SAN, you will want to make sure yourhost and LUN views are current. This operation might take a while depending on thenumber of hosts and LUNs Tivoli Storage Network Manager has to discover. You canrefresh your hosts and LUNs view by clicking View –> Refresh from the menu bar.

To discover any hosts or LUNs that have been added or removed, click Manage LUNs, thenclick Discover Hosts and LUNs from the menu bar. A discovery operation is never reallyconsidered complete. In other words, Tivoli Storage Network Manager is constantlymonitoring the SAN for changes. Whenever changes occur, Manage LUNs is notified of thechanges and the Refresh Manage LUNs View icon is activated. Click the icon to refreshyour hosts and LUNs view. The Refresh icon appears as:

The updated hosts and LUNs are displayed in the Manage LUNs window. This function alsoapplies to the View Storage Devices window.

Figure 70. Refresh Manage LUNs View Icon


Removing an Inactive Host from the Tree ViewYou might want to remove an inactive host from the tree view if the host is no longerfunctioning or required.

Note: Remove an inactive host only if it has been permanently disconnected from the SAN.Do not remove hosts which are temporarily unavailable. Removing an inactive hostfrom the tree view also removes the LUN assignments for that host. These changesare permanent changes in the database.

To remove an inactive host:

1. Click Manage LUNs, then click Remove Inactive Hosts from the menu bar.

2. The Remove Host dialog is displayed. Select one or more hosts.

3. Click Remove. The host or hosts are removed from the tree view.

Changing the Polling Interval for Manage LUNsYou can change the polling interval for Manage LUNs. To change it, follow these steps:

1. Open the Tivoli Console by double-clicking on the Tivoli Console icon on your desktop.

2. Click Administer Management Software, then click Manage ORBs in the portfolio.The Manage ORBs window displays.

3. A list of components is displayed on the right pane of the Manage ORBs window.

Figure 71. Manage ORBs Window


6.M

anag

ing

LU

Ns

4. Select SANConstantData and right-click on it to display the menu.

5. Click Edit Configuration to display the Edit Configuration window.

6. Change the polling interval in the hostPollingInterval field, then click OK. The pollinginterval is in milliseconds.

Viewing Storage DevicesTivoli Storage Network Manager also provides an easy to use tool for viewing storagedevices and associated LUN information. To access this tool from the Tivoli Consoleportfolio, click Manage Storage Network, then click View Storage Devices. The storagedevices and their associated LUNs are displayed in a tree view on the left of the screen.When you select a storage device on the left, the information about the storage device isdisplayed on the right. The storage view for a selected device is displayed in Figure 73 onpage 55.

Figure 72. Edit Configuration Window


When you select a LUN on the left, the Host Attachment table is displayed on the right.This table provides information for each host that the LUN is assigned to. If the LUN isassigned to only one host, this table displays information about one host. If the LUN isshared by two or more hosts, this table displays information about all the hosts.

If Tivoli Storage Network Manager detects a storage device that is not supported, the storagedevice will not be expanded in the tree view. The symbol for an unsupported storage deviceis shown in Figure 74.

The storage view for a selected LUN is displayed in Figure 75 on page 56.

Figure 73. Storage View — Selected Storage Device

Figure 74. Unsupported Storage Device


6.M

anag

ing

LU

Ns

Displaying Device InformationTo see information about a storage device, click on a storage device in the left portion of thescreen. The device information will appear on the right.

You will be provided with the following information:¶ Serial number¶ External label¶ Vendor¶ Type of Storage Device¶ Product ID¶ Vital Product Data (VPD)

Displaying LUN InformationTo see information about a LUN:

1. Click on a LUN in the left portion of the screen.

2. Click the LUN Properties button.

3. The LUN information is displayed in the LUN Properties dialog window.

The LUN Properties dialog window displays the following information:¶ Vendor ID¶ Product ID¶ Revision Level¶ Serial Number

Figure 75. Storage View — Selected LUN


¶ Capacity in MBs

Unassigning a LUNLUNs can be unassigned from a host using the View Storage Devices window. Once a LUNis unassigned, the host is removed from the table. LUNs can only be unassigned one at atime.

Before you unassign a LUN, make sure that the selected host no longer needs the filesystems or files on that LUN.

To unassign a LUN from the storage view:

¶ Select a LUN from the tree view in the left pane.

¶ Click the Unassign LUN button or icon.

The host for the LUN is removed from the host table in the right pane.


6.M

anag

ing

LU

Ns

Managing File System Policies

In addition to making it easy for you to assign and unassign LUNs to hosts, Tivoli StorageNetwork Manager provides a convenient system to automate the process of extending filesystems to help ensure that you never run out of storage space. By using policies youspecify, Tivoli Storage Network Manager can monitor all of the file systems on yourmanaged hosts and automatically extend supported file systems when they exceed athreshold established by that policy. In addition, you can divide your assignable LUNs intoseparate pools to make sure that only certain hosts have access to certain LUNs. Forexample, you can specify a group of RAID-5 compliant LUNs and, by means of policy,assign them for use only by hosts which are implementing RAID-5. For further informationon these policies, see “Default Policies” on page 60.

You can take advantage of Tivoli Storage Network Manager’s ability to help you monitorand extend file systems on your storage network by logging onto the Tivoli Console andmodifying the default policies to match the requirements of your domain. To get started,open the Tivoli Console Portfolio, click Manage Storage Networks, and then click ManageFile System Policies. The policies you set at the domain level will be in effect for all thefile systems on every managed host in your storage network. You can also fine tune yourstorage needs by setting policies for groups of hosts, individual hosts, or specific filesystems.

By default, policies are inherited from the top (or domain) level all the way down to theindividual file systems. From highest to lowest, the four levels of the policy inheritancehierarchy are:

¶ Domain — Policies set at this level affect every managed resource in your storagenetwork. This includes all of the hosts and file systems in your SAN or SANs. (MultipleSANs will be treated as one domain.)

¶ Host group — A logically grouped set of hosts. Changes made at this level willoverride the domain settings for all of the hosts (and their respective file systems)associated with this group.

¶ Host — Policies set at the domain or host group level can be overridden at the hostlevel. Any policies set for a host will be inherited by all of the file systems on that host.

¶ File system — Individual file systems are the lowest level of the hierarchy. Policies setat this level will override, for that specific file system only, policies set at any otherlevel.

Using this hierarchy, you can define policies at any level and have them be automaticallyinherited by the lower levels. For example, you can specify a threshold value of 80%(meaning that you want action to be taken if file systems become 80% full) at the domain

7


7.M

anag

ing

File

System

Po

licies

level and it will be inherited by all other levels. You can override inheritance by explicitlyturning it off at a lower level in the hierarchy and then specifying a new value for thatparticular policy.

The policies you define determine if a file system is monitored, how it is monitored, and ifit should be automatically extended when it reaches its threshold capacity. The followingtable lists the operating systems supported by Tivoli Storage Network Manager and indicateswhich file systems can be automatically extended. While all of the file systems on hostsrunning these operating systems can be monitored to determine if they are nearing theirmaximum capacity, not all file systems support automatic extension.

Table 8. Supported Operating Systems and File SystemsOperating System File Systems on this Operating System which

can be Automatically Extended

Windows NT Server 4.0 with Service Pack 6a N/A

Windows 2000 Advanced Server or Professional N/A

AIX 4.3.3 JFS

Solaris 2.7 VxFS (Veritas)

UFS (if created by the Veritas Volume Manager)

Tivoli Storage Network Manager can also automatically extend file systems that make use ofRAID. Hardware RAID is supported on all disk subsystems on all supported operatingsystems. Support for software RAID is limited to the categories shown in the table below.

Table 9. Supported Software RAIDAIX 4.3.3 Solaris 2.7*

RAID-1 (mirror) Concatenation (volume sets)

RAID-0 (stripe)

RAID-1 (mirror)

RAID-5 (striping with distributed parity)

RAID-1 + RAID-0

RAID-0 + RAID-1

Note: *On Solaris 2.7, only software RAID implemented using VxVM version 7 issupported.

If you have enabled LUN management, default policies are established at the domain leveland will be in effect for all of your managed hosts. The following sections describe thedefault policies and explain how to modify them for optimum performance in your domain.

Default PoliciesThe default policies are already in place once the product is installed and LUN managementhas been enabled. If these policies are acceptable, then Tivoli Storage Network Manager isready to manage your file systems right out of the box. The default policy settings areshown in the table below.


Table 10. Default Policy SettingsPolicy Default Setting

Monitor Yes

Extend No

Threshold 90%

Alert Interval 7 days

Maximum File System Size 5000 GB

Lower Bound 1.0 GB

Upper Bound 10.0 GB

LUN Groups Default LUN Group

¶ When Monitor is set to Yes for a particular resource, that means that all of the filesystems under that resource will be monitored and messages regarding them will be sentto the event log. If Monitor is set to No for a particular resource, then its file systemswill not be monitored and none of the other policies will take affect for that resource.

¶ For supported file systems, if Extend is set to Yes then Tivoli Storage Network Managerwill automatically extend file systems under that resource if they exceed their Thresholdvalue. If Monitor is set to Yes but Extend is set to No, then messages will still be sentwhen the threshold is reached, but the file system will not be automatically extended.

Note: Extend should not be enabled at the domain level. If a root file system on amanaged UNIX host is extended onto a remote LUN, then the host may not beable to load its operating system when it attempts to reboot. Extend should onlybe enabled at the individual File System level for these hosts. Even then, Extendshould only be enabled for file systems that are not part of the root file system.

¶ The Threshold is the maximum capacity (0-99%) a file system on this resource canreach before requiring additional storage. The default threshold value is 90%. When amonitored file system reaches its threshold, an alert will be sent. Also, if Extend is setto Yes and the affected file system is of a supported type, then Tivoli Storage NetworkManager will automatically extend this file system.

¶ The Alert interval specifies the number of days that Tivoli Storage Network Managerwill wait before issuing a repeated warning that a file system is becoming full. Bysetting this value to a higher number, you can protect yourself from being inundated bywarning messages. This is especially useful for any file systems in your domain thatcannot be automatically extended.

Note: If you are not using Tivoli Storage Network Manager to automatically extend filesystems, then Monitor, Threshold, and Alert interval are the only policies thatyou need to establish. The remaining policies are only used for the automaticextension of file systems.

¶ The Lower bound and Upper bound are the minimum and maximum sizes (ingigabytes) by which you want to extend a file system. When automatically extending afile system, Tivoli Storage Network Manager will use these values to help it choose anappropriate LUN. Specifically, it will try to assign a LUN that is between the two rangesin size and is as close as possible to the upper bound. If no one LUN is large enough, itwill choose multiple smaller LUNs until it reaches a combined value that is greater thanthe lower bound yet still less than the upper bound. If Tivoli Storage Network Manager


7.M

anag

ing

File

System

Po

licies

cannot find a LUN or set of LUNs that matches these conditions, then it will not make aLUN assignment and will send a message explaining its failure.

¶ The Maximum file system size sets an upper limit (in gigabytes) for a file system.Once this maximum size is reached, the file system will no longer be automaticallyextended regardless of other policy settings. You can take advantage of this policysetting to protect file systems from growing beyond what your operating system canaddress. It can also be used to simply enforce a limit to the maximum growth ofparticular file systems such as users’ personal directories.

¶ You can also choose specific LUN groups to use for extending your file systems. LUNgroups are logical groupings of LUNs that you can create by accessing Manage LUNGroups from the Tivoli Console Portfolio under the Manage Storage Network taskgroup. By setting up and assigning LUN groups, you can ensure that certain file systemsare only extended onto LUNs from a specific pool. If you have not defined your ownLUN groups, then all LUN assignments will be made from the Default LUN Group.

Defining LUN GroupsIf you plan to use Tivoli Storage Network Manager to automatically extend file systems, youmay want to restrict which available LUNs in your storage network can be used to extendspecific file systems. For example, you might have a set of two gigabyte LUNs and a set offive gigabyte LUNs. You might want less active file systems to be automatically extendedusing LUNs from the two gigabyte set and file systems with a faster rate of growth to beextended using LUNs from the five gigabyte set. You can do this by assigning the differentsets of LUNs into different LUN groups and then establishing policies that tell TivoliStorage Network Manager which group to draw from when making LUN assignments. Moreimportantly, if you are making use of RAID devices in your storage network, you will wantto make certain that you have grouped your RAID-compliant LUNs into their own groupsand that those groups are assigned only to hosts that are implementing RAID.

To begin creating LUN groups, open the Tivoli Console Portfolio, click the ManageStorage Network task group to expand it, then click on Manage LUN Groups. This willopen the LUN Group window in the task area as shown in Figure 76 on page 63.


Click on the New button to create a new LUN group. This will open a dialog that willprompt you to name your new LUN group as shown in Figure 77.

Type a name for this LUN group and click OK. Then select your new LUN group andassign LUNs to it by selecting them from the list in the right pane. You can filter this list tomake finding specific LUNs easier. You can select multiple LUNs by holding down theCTRL key while you select LUNs. Click on the Move to selected LUN group button whenyou have finished selecting LUNs. You can repeat this process until you have created all theLUN groups you need. When you first access this dialog, you will see only one LUN group.This is the Default LUN Group. All of your available LUNs are initially assigned to it. Ifyou create your own LUN groups and later delete them, any LUNs assigned to those groups

Figure 76. LUN Groups Panel

Figure 77. New LUN Group Panel


7.M

anag

ing

File

System

Po

licies

will be returned to the Default LUN Group. Defining LUN groups is an optional stepprovided for your convenience. If you choose to skip this step, all LUNs will be assigned tothe Default LUN Group. Tivoli Storage Network Manager will then draw from that groupwhen extending file systems.

You can also delete or rename existing LUN Groups from this panel by selecting a LUNGroup from the list on the left and clicking either the Delete or the Rename button. If youdelete a LUN Group, the LUNs that had previously been assigned to it will be reassigned tothe Default LUN Group.

Defining Domain PoliciesIf the default settings provided with the product do not meet your needs, you can easilymodify them by opening the Tivoli Console Portfolio, clicking Manage Storage Network,and then clicking Manage File Systems Policies. This will open a tree view of your domainin the task area as shown in Figure 78 on page 65. This view provides a visual representationof the policy inheritance hierarchy, allowing you to see at a glance how policiesimplemented at different levels flow down to affect the individual file systems of yourmanaged hosts. This view supports drag-and-drop interactively, so you can perform many ofthe tasks described below without having to leave this view.

To see the current domain default policy settings, click on Domain in the upper left corner.The current default policy settings will appear in the right pane. Whatever you specify atthis level will apply to all file systems in your storage network unless you override thesepolicies by defining other values at the host group, host, or file system level. The defaultpolicies are listed in “Default Policies” on page 60.

In addition to the default policies described above, you can specify a Monitor interval atthe domain level. While all of the other policies can be separately applied to every level ofthe hierarchy, the monitor interval can only be set at the domain. As a result, you can onlyset this value once for all of your managed file systems and cannot override it at a lowerlevel in the hierarchy. The monitor interval determines how often Tivoli Storage NetworkManager checks your managed file systems to see if they have exceeded the threshold youhave defined. By default, this check is performed once every half hour.

Note: For more information about these policies and their possible values, check the onlinehelp. You can access it by clicking on the question mark icon in the upper rightcorner of any dialog.


To edit the default domain policies, follow these steps:

¶ Click in any policy field in the right pane and edit the value in that field.

¶ If you feel you have made a mistake or would like to undo the changes you have made,you can click Product Defaults to return to the out-of-the-box default settings or Resetto change back to your previous settings.

¶ If you are satisfied with the policy changes you have made for your domain, clickApply to save your changes and cause them to take effect.

You can also access the Domain Defaults properties panel by choosing Domain Defaultsfrom the SAN Administration menu. This will launch the panel separate from the policyinheritance hierarchy view as shown in Figure 79 on page 66.

Figure 78. Domain Defaults Properties Panel in the Policy Inheritance Hierarchy View


7.M

anag

ing

File

System

Po

licies

Defining Host Group PoliciesA host group consists of a set of hosts that have some meaningful criteria in common. Forexample, you might create a host group out of all your Accounting servers because all ofthem have similar storage needs. Host groups are useful for applying a single set of policyvalues to a group of related hosts. For example, you might set a default threshold value of90% in your domain but have one group of hosts that, because of their high volume ofactivity, you assign a threshold value of 70%. This would help to make sure that those hostsdo not run out of storage and would give you more time to intervene in the event of aproblem. The policies you set for your host group will override the policies you set at thedomain level for all of the hosts in that host group.

To take advantage of the added management power host groups offer, you must divide thehosts in your domain into logically defined groups, create a host group for each of thosegroups, define policies for them, and assign the appropriate hosts to each of your hostgroups. The following sections on creating and editing host groups will walk you throughthis process.

Creating New Host GroupsTo create a new host group, click Manage Storage Network and then click Manage FileSystems Policies from the Portfolio. The policy inheritance hierarchy view will appear inthe task area. The first time you open this view, no host groups will be displayed because

Figure 79. Domain Defaults Properties Panel


you have not yet defined any. To define a new host group, right-click an existing host orhost group and choose Add New Host Group as show in Figure 80.

This will display the New Host Group Properties dialog in the pane on the right as shownin Figure 81 on page 68.

Figure 80. Right Click a Host or Host Group to Access the Add New Host Group Menu Item


7.M

anag

ing

File

System

Po

licies

In the right pane, follow these steps to create a new host group.

¶ Under Host group, type a name to identify this host group.

¶ Under Description, type in a description that will help you identify and distinguish thishost group.

¶ Notice that by default the host group is inheriting the values you assigned to the domain.If these values are acceptable, simply leave the Inherit check boxes checked. If youwish to override any of these values, uncheck the Inherit box next to that field and typein a new value. The fields on this panel are the same as those presented in the DomainDefaults panel, so you can look at that section above if you need assistance. The onlinehelp can also aid you in understanding these fields.

¶ Under Hosts currently not in a host group, find the hosts you want to add to the hostgroup and add them to the group by checking the check box to the left of the host name.You can select multiple hosts in this manner. If you prefer, you can perform this steplater in the policy inheritance hierarchy view by dragging and dropping hosts into thishost group.

¶ Click Apply to save your changes or Reset to change the values back to their previoussettings.

Repeat these steps until you have created all of the host groups you want to establish inyour domain.

Editing Existing Host Group PoliciesOnce you have established initial policies for your host groups, you can edit them byselecting them in the left pane of the policy inheritance hierarchy view. This will cause the

Figure 81. Creating a New Host Group Through the Policy Inheritance Hierarchy View


policies for the host group you have selected to appear in the right pane as shown inFigure 82.

Find the host group you want to edit from the list on the left side of the panel and select it.Follow these steps to edit the policies of this host group.

¶ Notice that by default the host group is inheriting the values you assigned to the domain.If these values are acceptable, simply leave the Inherit check boxes checked. If youwish to override any of these values, uncheck the Inherit box next to that field and typein a new value. The fields on this panel are the same as those presented in the DomainDefaults panel, so you can look at that section above if you need assistance. The onlinehelp can also aid you in understanding these fields.

¶ Under Hosts currently not in a host group, find the hosts you want to add to the hostgroup and add them to the group by checking the check box to the left of the host name.You can select multiple hosts in this manner.

¶ You can remove a host from the host group by unchecking the checkbox to its left.

¶ Click Apply to save your changes orReset to change the values back to their previoussettings.

You can also manage host groups by clicking the SAN Administration menu on the menubar near the top of the window and choosing Host Groups. This will launch the HostGroups panel as shown in Figure 83 on page 70.

Figure 82. Edit Host Group Policies


7.M

anag

ing

File

System

Po

licies

You can use the Host Groups panel to manage your host groups in one of the followingways.

¶ To delete a host group, select it from the list and click the Delete button. A confirmationdialog will ask if you are sure you want to delete this host group. Click OK to deletethe host group. If you delete a host group, the hosts that had previously been assigned toit will be reassigned to the Hosts currently not in a host group category. These hosts willbe visible just below the domain in the policy inheritance hierarchy view.

¶ To modify policies for a host group, select the host group from the list and click theEdit button. This will launch the Edit Host Group Properties dialog. This dialog isidentical to the properties panel displayed in the right pane of the policy inheritancehierarchy view shown in Figure 82 on page 69 above.

¶ To simply view the policy settings for a host group without the risk of makingaccidental changes, select the host group from the list and click the View Details button.This will launch the View Host Group Properties dialog. This dialog is nearly identicalto the Edit Host Group Properties panel. The difference is that the only availablebutton is Cancel.

¶ Finally, clicking the New button will launch the New Host Group Properties dialog.This dialog is identical to the properties panel displayed in the right pane of the policyinheritance hierarchy view shown in Figure 81 on page 68 above.

Figure 83. Managing Host Groups


Defining Host PoliciesYou can define policies for file systems on a specific host and these policies will overridethose you specified at the domain level and host group level. To define the policies thatapply to the file systems of a specific host, open the Tivoli Console Portfolio, click ManageStorage Network, and then click Manage File Systems Policies from the Portfolio. Thiswill bring up the policy inheritance hierarchy view. In the left pane, select the host whosepolicies you wish to change by clicking on it. Its policies will display in the right pane asshown in Figure 84.

Follow these steps to define policies for your selected hosts.

¶ Notice that by default the host is inheriting the values you assigned to the domain or toits host group. If these values are acceptable, simply leave the Inherit check boxeschecked. If you wish to override any of these values, uncheck the Inherit box next tothat field and type in a new value. The fields on this panel are the same as thosepresented in the Domain Defaults panel, so you can look at that section above if youneed assistance. The online help can also aid you in understanding these fields.

¶ Click Apply to save your changes or click Reset to change the values back to theirprevious settings.

As with host groups, you can also manage your hosts by clicking the SAN Administrationmenu on the menu bar near the top of the window and choosing Hosts. This will launch theHosts panel as shown in Figure 85 on page 72.

Figure 84. Editing Host Properties


7.M

anag

ing

File

System

Po

licies

You can use the Hosts panel to manage all of your hosts outside of the context of the policyinheritance hierarchy. If you have several hosts in your domain, this method may be theeasiest way to find and establish policies for a specific host. In the list of hosts, you canclick on any column heading to sort the list by that heading in either ascending ordescending order. For example, you could sort all of your hosts by name or IP address toquickly find the host you need. groups in one of the following ways

You can also use this panel to view or edit host policies. Just select a host from the list andclick Edit to begin editing its policies or View Details to simply see its current policysettings. Clicking Edit will launch the Edit Host Properties dialog. You can use this dialogto edit host properties in exactly the same way as described under Figure 84 on page 71.

Defining Specific File System PoliciesTo define the policies that apply to a specific file system of a specific host, click ManageStorage Network and then click Manage File Systems Policies from the Portfolio. Thiswill bring up the policy view hierarchy. In the left pane, find the host that uses the filesystem you want to edit. Click on the filled box next to that host to expand it. You shouldnow see all of the file systems connected to that host displayed underneath it. Select the filesystem you want to edit. Its policies will appear in the right pane. Follow these steps to editfile system policies.

¶ Notice that by default the file system is inheriting the values that apply to its host. Ifthese values are acceptable, simply leave the Inherit check boxes checked. If you wishto override any of these values, uncheck the Inherit box next to that field and type in anew value. The fields on this panel are the same as those presented in the Domain

Figure 85. Managing Host Policies


Defaults panel, so you can look at that section above if you need assistance. The onlinehelp can also aid you in understanding these fields.

¶ Click Apply to save your changes or Reset to change the values back to their previoussettings.

If you have completed all of these steps in order, then you have successfully configured yourdomain to automatically extend file systems when necessary. If you want to fine tune yourpolicy settings later, simply repeat the procedures above to adjust your policies.


7.M

anag

ing

File

System

Po

licies

SAN Glossary

This glossary contains terms used in this manual or in the use of the product. For moreinformation on Tivoli terminology, see Tivoli Dictionary of Systems Management athttp://www.tivoli.com/products/documents/glossary/termsm03.

A

Administrative ConsoleThe console that an administrator uses to manage the operations of a Tivoli Kernel Services installation.

agentA software entity that runs on endpoints and provides management capability for other hardware or software. Anexample is an SNMP agent. An agent has the ability to spawn other processes.

ALSee arbitrated loop.

alertAn event designed to be captured by an external system management application.

alert intervalThe amount of time that must pass after an alert is raised before the same alert can be raised again.

allocated storageThe space that is allocated to volumes, but not assigned.

allocationThe entire process of obtaining a volume and unit of external storage, and setting aside space on that storage fora data set.

arbitrated loopA Fibre Channel interconnection technology that allows up to 126 participating node ports and one participatingfabric port to communicate. See also Fibre Channel Arbitrated Loop and loop topology.

arrayAn arrangement of related disk drive modules that have been assigned to a group.

Authentication ServiceThe Tivoli Kernel Services component that validates users and code, providing a security context for theprincipal, which are authenticated users.

Authorization ServiceThe Tivoli Kernel Services component that provides access controls for resources within Tivoli Kernel Services.

B

bandwidthA measure of the data transfer rate of a transmission channel.

bridgeFacilitates communication with LANs, SANs, and networks with dissimilar protocols.

C

client1. A function that requests services from a server, and makes them available to the user.2. A term used in an environment to identify a machine that uses the resources of the network.


SA

NG

lossary

client authenticationThe verification of a client in secure communications where the identity of a server or browser (client) withwhom you wish to communicate is discovered. A sender’s authenticity is demonstrated by the digital certificateissued to the sender.

client-server relationshipAny process that provides resources to other processes on a network is a server. Any process that employs theseresources is a client. A machine can run client and server processes at the same time.

coalesceCombining the configuration data in the preference node trees from the ORBs and ORB sets in the distributedsystem into a single preference node tree. Configuration data for a particular ORB is determined by coalescingthe preference node tree for that ORB with the preference node tree for the ORB sets to which that ORBbelongs.

Configuration ServiceThe Tivoli Kernel Services component that manages the configuration parameters for components within thedistributed system of Tivoli Kernel Services. Components call the Configuration Service, which is a persistentstorage within the distributed system.

consoleA user interface to a server.

D

DATABASE 2 (DB2)A relational database management system. DB2 Universal Database is the relational database management systemthat is Web-enabled with Java support.

deployIn the Tivoli Kernel Services, deploy means to push components from the installation depots to the componentdepots, and from the component depots to the appropriate servers and endpoints. This is based on configurationinformation.

device centric viewA logical topology view presented as a series of screens which display the device-to-host relationship. It is usedto identify the dependencies on a device basis.

device driverA program that enables a computer to communicate with a specific device, for example, a disk drive.

Directory ServiceThe Tivoli Kernel Services component that implements the (Java Naming and Directory Interface) specificationto provide name, object storage, and lookup capabilities to components.

discoveryThe automatic detection of network topology changes such as new and deleted nodes or new and deletedinterfaces.

disk groupA set of disk drives that have been configured into one or more logical unit numbers. This term is used withRAID devices.

domainIn Tivoli Kernel Services, a domain is an organizational division of the distributed system that is based on groupsand hierarchies of components in subsystems. Several different domains can exist within an installation, anddomains can nest within other domains or overlap with other domains. For example, Tivoli Kernel Servicesincludes one or more security domains. Domains are implemented using ORB sets. In Tivoli Storage NetworkManager, a domain is a fibre channel SAN with a network of hosts attached. This is called a SAN domain.


E

endpointIn the Tivoli Kernel Services, an endpoint is a system running a management agent. An endpoint communicatesonly with its assigned gateway. See also gateway.

enterprise networkA geographically dispersed network under the backing of one organization.

ESSSee IBM Enterprise Storage Server.

eventIn the Tivoli environment, any significant change in the state of a system resource, network resource, or networkapplication. An event can be generated for a problem, for the resolution of a problem, or for the successfulcompletion of a task. Examples of events are: the normal starting and stopping of a process, the abnormaltermination of a process, and the malfunctioning of a server.

F

fabricThe Fibre Channel employs a fabric to connect devices. A fabric can be as simple as a single cable connectingtwo devices. The term is often used to describe a more complex network utilizing hubs, switches, and gateways.

FCSee Fibre Channel.

FCSSee Fibre Channel standard.

fiber opticThe medium and the technology associated with the transmission of information along a glass or plastic wire orfiber.

Fibre ChannelA technology for transmitting data between computer devices at a data rate of up to 1 Gb. It is especially suitedfor connecting computer servers to shared storage devices and for interconnecting storage controllers and drives.

Fibre Channel Arbitrated LoopA reference to the FC-AL standard, a shared gigabit media for up to 127 nodes, one of which can be attached toa switch fabric. See also arbitrated loop and loop topology. Refer to American National Standards Institute(ANSI) X3T11/93-275.

Fibre Channel standardAn ANSI standard for a computer peripheral interface. The I/O interface defines a protocol for communicationover a serial interface that configures attached units to a communication fabric. Refer to ANSI X3.230-199x.

file systemAn individual file system on a host. This is the smallest unit that can monitor and extend. Policy values definedat this level override those that might be defined at higher levels.

G

gateway1. In the SAN environment, a gateway connects two or more different remote SANs with each other.2. In Tivoli Kernel Services, a gateway is a component that manages communications and connections between

a group of endpoints and the Tivoli Kernel Services. The gateway converts server protocols to endpointprotocols, and vice versa. A gateway can also be a server on which a gateway component runs.


SA

NG

lossary

H

hardware zoningHardware zoning is based on physical ports. The members of a zone are physical ports on the fabric switch. Itcan be implemented in the following configurations: one to one, one to many, and many to many.

HBASee host bus adapter.

hostAny system that has at least one internet address associated with it. A host with multiple network interfaces canhave multiple internet addresses associated with it. This is also referred to as a server.

host bus adapter (HBA)A Fibre Channel HBA connection that allows a workstation to attach to the SAN network.

host centric viewA logical topology view presented as a series of screens which displays the host-to-device relationship. It is usedto identify the usage on a host basis.

host groupA logical grouping of hosts defined by the administrator. A host can belong to only one host group. The hosts ina host group share a common policy.

hubA Fibre Channel device that connects up to 126 nodes into a logical loop. All connected nodes share thebandwidth of this one logical loop. Hubs automatically recognize an active node and insert the node into theloop. A node that fails or is powered off is automatically removed from the loop.

I

IBM Enterprise Storage ServerProvides an intelligent disk storage subsystem for systems across the enterprise.

inband discoveryPerformed by gathering information from managed host systems from the Tivoli Storage Network Manageragents. The inband discovery gathers host information, logical information (such as volume groups, operatingsystem, logical volume, and so on), device information, topology information and zone information. See alsooutband discovery.

installation depotIt pushes the components to the Tivoli Kernel Services servers.

IPInternet protocol.

J

JavaA programming language that enables application developers to create object-oriented programs that are verysecure, portable across different machine and operating system platforms, and dynamic enough to allowexpansion.

Java runtime environment (JRE)The underlying, invisible system on your computer that runs applets the browser passes to it.

Java Virtual Machine (JVM)The execution environment within which Java programs run. The Java virtual machine is described by the JavaMachine Specification which is published by Sun Microsystems™. Because the Tivoli Kernel Services is basedon Java, nearly all ORB and component functions execute in a Java virtual machine.


JBODJust a Bunch Of Disks.

JRESee Java runtime environment.

JVMSee Java Virtual Machine.

L

Logging ServiceThe Tivoli Kernel Services component that manages the logging of component messages and trace data acrossmultiple JVMs within the distributed system.

logical unit number (LUN)The LUNs are provided by the storage devices attached to the SAN. This number provides you with a volumeidentifier that is unique among all storage servers. The LUN is synonymous with a physical disk drive or a SCSIdevice. For disk subsystems such as the IBM Enterprise Storage Server, a LUN is a logical disk drive. This is aunit of storage on the SAN which is available for assignment or unassignment to a host server.

loop topologyIn a loop topology, the available bandwidth is shared with all the nodes connected to the loop. If a node fails oris not powered on, the loop is out of operation. This can be corrected using a hub. A hub opens the loop when anew node is connected and closes it when a node disconnects. See also Fibre Channel Arbitrated Loop andarbitrated loop.

LUNSee logical unit number.

LUN assignment criteriaThe combination of a set of LUN types, a minimum size, and a maximum size used for selecting a LUN forautomatic assignment.

LUN centric viewDisplays the LUN properties which includes the LUN identification, capacity, and all hosts that the LUN isassigned to.

LUN groupA logical grouping of LUNs defined by the administrator. One or more LUNs can be assigned to a file system.

LUN maskingThis allows or blocks access to the storage devices on the SAN. LUN masking is provided by the Tivoli StorageNetwork Manager agent on the managed host. Intelligent disk subsystems like the IBM Enterprise Storage Serveralso provide subsystem masking.

M

managed objectA managed resource.

managed resourceA physical element to be managed.

Management Information Base (MIB)A logical database residing in the managed system which defines a set of MIB objects. A MIB is considered alogical database because actual data is not stored in it, but rather provides a view of the data that can be accessedon a managed system.

mapIn NetView, a database represented by a set of related submaps that provide a graphical and hierarchicalpresentation of a network and its systems.


SA

NG

lossary

MIBSee Management Information Base.

MIB objectA MIB object is a unit of managed information that specifically describes an aspect of a system. Examples areCPU utilization, software name, hardware type, and so on. A collection of related MIB objects is defined as aMIB.

N

navigation menuIn the user interface (or the help interface), the area on the left-hand side of the screen, containing selections thatallow a user to quickly link to different areas of the product to perform different tasks. See also title bar and userinterface. This is also referred to as a navigation tree.

network topologyA physical arrangement of nodes and interconnecting communications links in networks based on applicationrequirements and geographical distribution of users.

N_Port node portA Fibre Channel-defined hardware entity at the end of a link which provides the mechanisms necessary totransport information units to or from another node.

NL_Port node loop portA node port that supports arbitrated loop devices.

O

Object Request Broker (ORB)A component in the CORBA programming model that acts as the middleware between clients and servers.Clients can request a service without knowing anything about which servers are attached to the network. ORBs inthe network receive the client requests for objects or services and forward them to the appropriate servers. Theresults are then passed back to the client. The Tivoli Kernel Services ORBs run within a Java Virtual Machine.

open systemA system whose characteristics comply with standards made available throughout the industry, and therefore canbe connected to other systems that comply with the same standards.

ORBSee Object Request Broker.

outband discoveryPerformed by gathering information directly from switches and other devices using SNMP MIB queries. Theoutband discovery gathers device information and topology information. See also inband discovery.

P

point-to-point topologyIt consists of a single connection between two nodes. All the bandwidth is dedicated for these two nodes.

policy inheritanceThe policy inheritance is promoted through a hierarchical structure. Policy inheritance means that policy valuesapplied to the highest level of the hierarchy can be inherited by the lower levels. The four levels of the hierarchyare:1. Enterprise2. Host group3. Host4. File system


portAn end point for communication between applications, generally referring to a logical connection. A portprovides queues for sending and receiving data. Each port has a port number for identification. When the portnumber is combined with an Internet address, it is called a socket address.

port zoningIn Fibre Channel environments, port zoning is the grouping together of multiple ports to form a virtual privatestorage network. Ports that are members of a group or zone can communicate with each other but are isolatedfrom ports in other zones. See also LUN masking and subsystem masking.

portfolioA container for the task groups that are assigned to a specific role. To start tasks, users must open the portfolio.When the portfolio is open, it displays within the Tivoli Console to the left of the workspace.

portfolio handleA tab on the left side of the Tivoli Console that represents the portfolio when the portfolio is closed.

preference nodeIn Tivoli Kernel Services, a collection of configuration data, represented by key-value pairs, that is specific to anORB or ORB set. Preference nodes are associated with one another in preference node trees.

preference node treeA hierarchical representation of the relationships among preference nodes. Preference nodes are named based ontheir location within the preference node tree. By convention, the naming structure of the preference node treemirrors the Java package and class name hierarchy, eliminating name collisions and strengthening the correlationbetween configuration data and the code that uses it.

primary serverThe main server that contains the installation depot.

protocolThe set of rules governing the operation of functional units of a communication system if communication is totake place. Protocols can determine low-level details of machine-to-machine interfaces, such as the order inwhich bits from a byte are sent. They can also determine high-level exchanges between application programs,such as file transfer.

publishTo send a message through Tivoli Event Service based on a topic from a publisher to a subscriber.

R

RAIDRedundant array of inexpensive or independent disks. A method of configuring multiple disk drives in a storagesubsystem for high availability and high performance.

regionAn organizational division of the user’s enterprise that is based on the user’s operations. For example, a branchoffice or a subsidiary is a type of region. The organization of an enterprise into regions is generally constant overtime. The organization of domains (and therefore indirectly the organization of components) within thedistributed system of the Tivoli Kernel Services is based on regions. Contrast with domain.

rogue hostA node that is determined to be a host but has no corresponding entry in the Host Manager agent list. See alsounknown device.

roleA user’s job function. Each user can have one or more roles or access capabilities.

S

SANSee storage area network.


SA

NG

lossary

SAN agentA software program that communicates with the manager and controls the subagents. This component is largelyplatform independent. See also subagent.

SCSISmall Computer System Interface. An ANSI standard for a logical interface to computer peripherals and for acomputer peripheral interface. The interface utilizes a SCSI logical protocol over an I/O interface that configuresattached targets and initiators in a multi-drop bus topology.

serverA program running on a mainframe, workstation, or file server that provides shared services. This is also referredto as a host.

shared storageStorage within a storage facility that is configured such that multiple homogeneous or divergent hosts canconcurrently access the storage. The storage has a uniform appearance to all hosts. The host programs that accessthe storage must have a common model for the information on a storage device. You need to design the programsto handle the effects of concurrent access.

Simple Network Management Protocol (SNMP)A protocol designed to give a user the capability to remotely manage a computer network by polling and settingterminal values and monitoring network events.

SNMPSee Simple Network Management Protocol.

SNMP agentAn implementation of a network management application which is resident on a managed system. Each node thatis to be monitored or managed by an SNMP manager in a TCP/IP network, must have an SNMP agent resident.The agent receives requests to either retrieve or modify management information by referencing MIB objects.MIB objects are referenced by the agent whenever a valid request from an SNMP manager is received.

SNMP managerA managing system that executes a managing application or suite of applications. These applications depend onMIB objects for information that resides on the managed system.

SNMP trapA message that is originated by an agent application to alert a managing application of the occurrence of anevent.

software zoningIs implemented within the Simple Name Server (SNS) running inside the fabric switch. When using softwarezoning, the members of the zone can be defined with: node WWN, port WWN, or physical port number. Usuallythe zoning software also allows you to create symbolic names for the zone members and for the zonesthemselves.

SQLStructured Query Language.

storage administratorA person in the data processing center who is responsible for defining, implementing, and maintaining storagemanagement policies.

storage area network (SAN)A managed, high-speed network that enables any-to-any interconnection of heterogeneous servers and storagesystems.

subagentA software component of SAN products which provides the actual remote query and control function, such asgathering host information and communicating with other components. This component is platform dependent.See also SAN agent.


submapIn NetView, a particular view of some aspect of a network that displays symbols representing objects. Theapplication program that creates a submap determines what part of the network the submap displays.

submap paneIn NetView, the area of a submap window in which the submap is displayed.

submap stackIn NetView, a component of the graphical user interface shown on the left side of each submap window. Thesubmap stack represents the navigational path used to reach the particular submap, and it can be used to select apreviously viewed submap.

submap windowIn NetView, the graphical component that contains a menu bar, a submap viewing area, a status line, and a buttonbox. A user can display multiple submap windows of an open map and an open snapshot at any given time.

subscribeTo register with Tivoli Event Service to receive events that are published on a particular topic.

subsystem maskingThe support provided by intelligent disk storage subsystems like the Enterprise Storage Server. See also LUNmasking and port zoning.

switchA component with multiple entry and exit points or ports that provide dynamic connection between any two ofthese points.

switch topologyA switch allows multiple concurrent connections between nodes. There can be two types of switches, circuitswitches and frame switches. Circuit switches establish a dedicated connection between two nodes. Frameswitches route frames between nodes and establish the connection only when needed. A switch can handle allprotocols.

T

TCPSee Transmission Control Protocol.

TCP/IPTransmission Control Protocol/Internet Protocol.

TECSee Tivoli Enterprise Console.

TESSee Tivoli Event Service.

title barIn the user interface (or the help interface), the area at the top of the screen, containing the product title on theleft, and the Tivoli logo on the right. See also navigation menu, work area, and user interface.

Tivoli AssistantA user assistance mechanism that contains contextual help information for Tivoli software. It is represented by aquestion mark, and can be easily toggled on and off. When the Tivoli Assistant is open, it displays within theTivoli Console to the right of the workspace.

Tivoli ConsoleThe graphical user interface for software that runs on the Tivoli Management Framework.

Tivoli Enterprise Console (TEC)A Tivoli product that collects, processes, and automatically initiates corrective actions for system, application,network, and database events; it is the central control point for events from all sources. The Tivoli Enterprise


SA

NG

lossary

Console provides a centralized, global view of the network computing environment; it uses distributed eventmonitors to collect information, a central event server to process information, and distributed event consoles topresent information to system administrators.

Tivoli Event Service (TES)The Tivoli program that allows Tivoli applications to communicate with each other by using the publish/subscribecommunication model of the Java Message Service.

Tivoli Kernel ServicesTivoli Kernel Services provides a way to manage network computing resources of many different types from asingle point. The products in this environment provide a consistent interface to different operating systems andservices. Tivoli Kernel Services allows administrators to control users, systems, applications, and resources fromone desktop. This environment also provides a streamlined way to automate and delegate routine,time-consuming tasks.

Tivoli Storage Network Manager agentThe software which performs local functions such as LUN masking and inband discovery on a host attached tothe SAN. A host with a Tivoli Storage Network Manager agent is referred to as a managed host.

topicInformation that identifies what a publication is about in TES. Applications publish events to a topic andsubscribe to events from a topic.

topologyAn interconnection scheme that allows multiple Fibre Channel ports to communicate. For example,point-to-point, arbitrated loop, and switched fabric are all Fibre Channel topologies.

Transmission Control Protocol (TCP)A reliable, full duplex, connection-oriented, end-to-end transport protocol running on top of IP.

U

unknown deviceA node that is found but cannot be identified. See also rogue host.

user IDA alpha numeric or some other means of identifying a user.

user interfaceThe area contained within the browser window. The user interface is comprised of the navigation menu, the titlebar, and the work area.

W

WANWide Area Network.

work areaThe area just to the right of the navigation menu, where most work is accomplished. Clicking on a selection inthe navigation menu changes the view in the work area. See also navigation menu, title bar, and user interface.

Z

zone viewA logical topology view presented as a series of screens which display the hosts and devices within a zone.

zoningIn Fibre Channel environments, zoning allows for finer segmentation of the switched fabric. Zoning can be usedto instigate a barrier between different environments. Ports that are members of a zone can communicate witheach other but are isolated from ports in other zones. Zoning can be implemented in two ways: hardware zoningand software zoning.


Index

Aacknowledge object 33agents

configuring 15starting 15

automating file system extension 2, 59

Cchild submap 5Clearing the status history 36colors, use of 33configuring

agents 15context menu 11

Ddefault policies 60Device applications, launching 39Device Centric View 28Device properties 38Device states 39device status 33discovering

hosts 52LUNs 52

discoveryconfiguring 17

displaying information 50domain policies 64

Eediting host groups 68event browser 42explorer 6

Ffile system policies 72file systems

automating extension 59managing policies 59monitoring 59

flyover, status 34functional overview 1

Gglossary 75

HHost Centric View 25host group policies 66host policies 71hosts 50

discovering 52

IIntroduction 1

LLaunching device applications 39LUN groups 62LUNs

assigning to a host 51discovering 52displaying information 50displaying properties 56managing 45reassigning 52sharing 51unassigning 51, 57

Mmanage

file system policies 2LUNs 2networks 2

manage file system policies 59manage object 33managing

LUNs 45storage devices 54


Ind

ex

menu bar 4monitor 33monitoring file systems 2, 59

NNetView Console 3NetView Console status bar 6NetView Event Browser 42network, viewing 19Network View 21new host groups 66

Oobject, acknowledged or unacknowledged 33object, manage or unmanage 33online help 7online help, Tivoli Assistant 12overview

managing LUNs 45overview, user interface 3

Ppolling

configuring 17portfolio

description 10properties

LUN 56storage device 56

property tips 5

Rrogue Host 23rogue hosts 46

SSNMP traps 42starting

agents 15Disk Manager 15File System Policy Automation Manager 15Network Manager 15

status 33

status 33 (continued)device 33propagation 33working with 33

status, flyover 34status, in submap explorer 35status bar, NetView Console 6status filter toolbar 6status flittering 36Status history 36status propagation 33storage devices

displaying properties 56submap explorer 6submap stack 5Switch support for inband discovery 17, 24symbols 8

Ttask groups 11tasks

help information 11locating and performing 11

Tivoli Assistant 11, 12Tivoli Console

closing 11guided tour 13key components of 10

toolbar, NetView 4toolbar, status filter 6Topology View 22

Uunacknowledge object 33unmanage object 33user assistance, embedded 12user interface 3

Vviewing

storage devices 54viewing the network 19

WWorking with device properties 38Working With Network Devices 33
