ibm.com/redbooks

Front cover

IBM Tivoli Storage Area Network Manager:A Practical Introduction

Charlotte BrooksMichel Baus

Michael BenantiIvo Gomilsek

Urs Moser

Discover, display and monitor your SAN topology, including zones

Historical and real-time monitoring

ED/FI for SAN Error prediction

International Technical Support Organization

IBM Tivoli Storage Area Network Manager: A Practical Introduction

September 2003

SG24-6848-01

© Copyright International Business Machines Corporation 2002, 2003. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

Second Edition (September 2003)

This edition applies to IBM Tivoli Storage Area Network Manager (product number 5698-SRS) and IBM Tivoli Bonus Pack for SAN Management (product number 5698-SRE)

Note: Before using this information and the product it supports, read the information in “Notices” on page xxi.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiiThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiiBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviiSeptember 2003, Second Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Part 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction to Storage Area Network management. . . . . . . . . . . . . . . . . . . 31.1 Why do we need SAN management? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1.1 Storage management issues today . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1.2 Current generation of SAN management: spreadsheets and paper . . . . . . . . . . . . 7

1.2 New tools for SAN management are needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2.1 Storage management components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2.2 Standards and SAN management tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.3 Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2.4 Outband management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.5 Inband management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.6 Why you might use both inband and outband discovery. . . . . . . . . . . . . . . . . . . . 171.2.7 Formal standards for outband management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.8 Formal standards for inband management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.2.9 The future of SAN management standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.2.10 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager . . . . . . . . . . . . 272.1 Highlights: What’s new in Version 1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.1.1 Discovery of iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.1.2 Event Detection and Fault Isolation (ED/FI - SAN Error Predictor). . . . . . . . . . . . 282.1.3 IBM Tivoli Enterprise Data Warehouse (TEDW) . . . . . . . . . . . . . . . . . . . . . . . . . . 282.1.4 IBM Tivoli SAN Manager on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.1.5 Embedded WebSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.1.6 Operating system support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.1.7 Other changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.2 IBM Tivoli SAN Manager overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.2.1 Business purpose of IBM Tivoli SAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.2.2 Components of IBM Tivoli SAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.2.3 Supported devices for Tivoli SAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.3 Major functions of IBM Tivoli SAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.3.1 Discover SAN components and devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.3.2 Deciding how many Agents will be needed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.3.3 How is SAN topology information displayed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

© Copyright IBM Corp. 2002, 2003. All rights reserved. iii

2.3.4 How is iSCSI topology information displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.4 SAN management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2.4.1 Discover and display SAN components and devices . . . . . . . . . . . . . . . . . . . . . . 372.4.2 Log events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.4.3 Highlight faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.4.4 Provide various reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.4.5 Launch vendor management applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.4.6 Displays ED/FI events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.4.7 Tivoli Enterprise Data Warehouse (TEDW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

2.5 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Part 2. Design considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 3. Deployment architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563.2 Fibre Channel standards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.2.1 Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563.2.2 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.3 Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.3.1 Host Bus Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.3.2 Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3.4 Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.4.1 Point-to-point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.4.2 Arbitrated loop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643.4.3 Switched fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

3.5 IBM Tivoli SAN Manager components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.1 DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.2 IBM Tivoli SAN Manager Console (NetView) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.3 Tivoli SAN Manager Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.4 Tivoli SAN Manager Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5.5 SAN physical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

3.6 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.6.1 Inband management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.6.2 Outband management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3.7 Deployment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.7.1 Tivoli SAN Manager Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.7.2 iSCSI management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.7.3 Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.7.4 Tivoli SAN Manager Agent (Managed Host) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3.8 Deployment scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.8.1 Example 1: Outband only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.8.2 Example 2: Inband only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.8.3 Example 3: Inband and outband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.8.4 Additional considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

3.9 High Availability for Tivoli SAN Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.9.1 Standalone server failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.9.2 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Part 3. Installation and basic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 4. Installation and setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954.1 Supported operating system platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964.2 IBM Tivoli SAN Manager Windows Server installation . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.2.1 Lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

iv IBM Tivoli Storage Area Network Manager: A Practical Introduction

4.2.2 Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974.2.3 DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984.2.4 Upgrading DB2 with Fix Pack 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994.2.5 Install the SNMP service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004.2.6 Checking for the SNMP community name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014.2.7 IBM Tivoli SAN Manager Server install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024.2.8 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

4.3 IBM Tivoli SAN Manager Server AIX installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.3.1 Lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.3.2 Installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.3.3 Starting and stopping the AIX manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.3.4 Checking the log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

4.4 IBM Tivoli SAN Manager Agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.4.1 Lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.4.2 Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.4.3 IBM Tivoli SAN Manager Agent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.4.4 Configure the Agent service to start automatically . . . . . . . . . . . . . . . . . . . . . . . 117

4.5 IBM Tivoli SAN Manager Remote Console installation . . . . . . . . . . . . . . . . . . . . . . . . 1194.5.1 Lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194.5.2 Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194.5.3 Installing the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194.5.4 Check if the service started automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

4.6 IBM Tivoli SAN Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264.6.1 Configuring SNMP trap forwarding on devices . . . . . . . . . . . . . . . . . . . . . . . . . . 1264.6.2 Configuring the outband agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.6.3 Checking inband agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324.6.4 Performing initial poll and setting up the poll interval . . . . . . . . . . . . . . . . . . . . . 132

4.7 Tivoli SAN Manager upgrade to Version 1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334.7.1 Upgrading the Windows manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344.7.2 Upgrading the remote console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344.7.3 Upgrading the agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

4.8 Tivoli SAN Manager uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354.8.1 Tivoli SAN Manager Server Windows uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . 1354.8.2 Tivoli SAN Manager Server AIX uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364.8.3 Tivoli SAN Manager Agent uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1364.8.4 Tivoli SAN Manager Remote Console uninstall . . . . . . . . . . . . . . . . . . . . . . . . . 1374.8.5 Uninstalling the Tivoli GUID package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

4.9 Silent install of IBM Tivoli Storage Area Network Manager. . . . . . . . . . . . . . . . . . . . . 1394.9.1 Silent installation high level steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394.9.2 Installing the manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.9.3 Installing the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424.9.4 How to install the remote console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444.9.5 Silently uninstalling IBM Tivoli Storage Area Network Manager . . . . . . . . . . . . . 145

4.10 Changing passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Chapter 5. Topology management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495.1 NetView navigation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

5.1.1 NetView interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505.1.2 Maps and submaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505.1.3 NetView window structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505.1.4 NetView Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515.1.5 NetView Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535.1.6 Object selection and NetView properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Contents v

5.1.7 Object symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555.1.8 Object status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555.1.9 Status propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575.1.10 NetView and IBM Tivoli SAN Manager integration . . . . . . . . . . . . . . . . . . . . . . 157

5.2 Lab 1 environment description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1585.3 Topology views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

5.3.1 SAN view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1625.3.2 Device Centric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1665.3.3 Host Centric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675.3.4 iSCSI discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1685.3.5 MDS 9000 discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

5.4 SAN menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705.4.1 SAN Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

5.5 Application launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745.5.1 Native support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745.5.2 NetView support for Web interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1755.5.3 Non-Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1775.5.4 Launching IBM Tivoli Storage Resource Manager . . . . . . . . . . . . . . . . . . . . . . . 1795.5.5 Other menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

5.6 Status cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805.7 Practical cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

5.7.1 Cisco MDS 9000 discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825.7.2 Removing a connection on a device running an inband agent . . . . . . . . . . . . . . 1845.7.3 Removing a connection on a device not running an agent . . . . . . . . . . . . . . . . . 1875.7.4 Powering off a switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905.7.5 Running discovery on a RNID-compatible device. . . . . . . . . . . . . . . . . . . . . . . . 1935.7.6 Outband agents only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955.7.7 Inband agents only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.7.8 Disk devices discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005.7.9 Well placed agent strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

5.8 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Part 4. Advanced operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Chapter 6. NetView Data Collection, reporting, and SmartSets . . . . . . . . . . . . . . . . . 2076.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

6.1.1 SNMP and MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086.2 NetView setup and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

6.2.1 Advanced Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116.2.2 Copy Brocade MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116.2.3 Loading MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

6.3 Historical reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2156.3.1 Creating a Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2166.3.2 Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2246.3.3 Troubleshooting the Data Collection daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . 2246.3.4 NetView Graph Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

6.4 Real-time reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2276.4.1 MIB Tool Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2286.4.2 Displaying real-time data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2316.4.3 SmartSets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2356.4.4 SmartSets and Data Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2436.4.5 Seed file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Chapter 7. Tivoli SAN Manager and iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

vi IBM Tivoli Storage Area Network Manager: A Practical Introduction

7.1 What is iSCSI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2547.2 How does iSCSI work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2547.3 IBM Tivoli SAN Manager and iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

7.3.1 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2567.3.2 iSCSI discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

7.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Chapter 8. SNMP Event notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2598.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2608.2 Introduction to Tivoli NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

8.2.1 Setting up the MIB file in Tivoli NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2608.3 Introduction to IBM Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

8.3.1 Event forwarding from IBM Tivoli SAN Manager to IBM Director . . . . . . . . . . . . 263

Chapter 9. ED/FI - SAN Error Predictor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2679.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2689.2 Error processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2699.3 Configuration for ED/FI - SAN Error Predictor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2719.4 Using ED/FI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

9.4.1 Searching for the faulted device on the topology map . . . . . . . . . . . . . . . . . . . . 2769.4.2 Removing notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Part 5. Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Chapter 10. Protecting the IBM Tivoli SAN Manager environment . . . . . . . . . . . . . . . 28310.1 IBM Tivoli SAN Manager environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

10.1.1 IBM Tivoli NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28410.1.2 Embedded IBM WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . 28410.1.3 IBM Tivoli SAN Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28410.1.4 IBM Tivoli SAN Manager Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

10.2 IBM Tivoli Storage Manager integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28510.2.1 IBM Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28510.2.2 Setup for backing up IBM Tivoli SAN Manager Server . . . . . . . . . . . . . . . . . . . 28610.2.3 Tivoli Storage Manager server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 28610.2.4 Tivoli Storage Manager client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 28810.2.5 Additional considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

10.3 Backup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29110.3.1 Agent files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29110.3.2 Server files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29310.3.3 ITSANMDB Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

10.4 Restore procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30110.4.1 Restore Agent files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30210.4.2 IBM Tivoli SAN Manager Server files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30510.4.3 ITSANMDB database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

10.5 Disaster recovery procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30910.5.1 Windows 2000 restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31010.5.2 ITSANMDB database restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

10.6 Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Chapter 11. Logging and tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31711.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31811.2 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

11.2.1 Server logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31811.2.2 Manager service commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Contents vii

11.2.3 Service Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32111.2.4 Agent logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32211.2.5 Remote Console logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32311.2.6 Additional logging for NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32311.2.7 ED/FI - SAN Error Predictor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

11.3 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32611.4 SAN Manager Service Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

11.4.1 Exporting (snapshot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32811.4.2 Importing (restore) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Part 6. Tivoli Systems Management Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Chapter 12. Tivoli SAN Manager and TEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33312.1 Introduction to Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33412.2 Lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33512.3 Configuring the Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33612.4 Configuring TEC Event Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34012.5 Event format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34712.6 Configuring Tivoli SAN Manager event forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 348

12.6.1 Set the event destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34812.6.2 Configure NetView-TEC adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

12.7 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35212.8 Sample TEC rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager. . . . . . . . . . . . . . . 35713.1 Introduction to IBM Tivoli Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 35813.2 Inventory to determine who has which version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

13.2.1 Create an inventory profile in Tivoli Framework . . . . . . . . . . . . . . . . . . . . . . . . 35913.3 Software distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

13.3.1 Build software package with Software Package Editor . . . . . . . . . . . . . . . . . . . 37013.3.2 Create software distribution profile in Tivoli Framework . . . . . . . . . . . . . . . . . . 379

Chapter 14. Integration with Tivoli Enterprise Data Warehouse . . . . . . . . . . . . . . . . . 38714.1 Introduction to IBM Tivoli Enterprise Data Warehouse . . . . . . . . . . . . . . . . . . . . . . . 38814.2 IBM Tivoli SAN Manager Data Warehouse Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

Chapter 15. Tivoli SAN Manager and Tivoli Monitoring. . . . . . . . . . . . . . . . . . . . . . . . 39115.1 Introduction to IBM Tivoli Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39215.2 IBM Tivoli Monitoring for IBM Tivoli SAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 39215.3 Daemons to monitor and restart actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

Appendix A. Advanced Topology and Sensor Event Scanners . . . . . . . . . . . . . . . . . 401Advanced Topology Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Sensor Event Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Appendix B. IBM Tivoli SAN Manager backup scripts. . . . . . . . . . . . . . . . . . . . . . . . . 407Tivoli Storage Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408DB2 configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408Stopping the applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

Stopping WebSphere Tivoli SAN Manager application. . . . . . . . . . . . . . . . . . . . . . . . . 409Stopping Tivoli SAN Manager environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Starting the applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409These scripts start up the Tivoli SAN Manager environment in an orderly way. . . . . . . . . 409

Starting WebSphere Tivoli SAN Manager application. . . . . . . . . . . . . . . . . . . . . . . . . . 409Start of IBM Tivoli SAN Manager environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

viii IBM Tivoli Storage Area Network Manager: A Practical Introduction

DB2 ITSANMDB backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410Offline backup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410Online backup script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Appendix C. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

System requirements for downloading the Web material . . . . . . . . . . . . . . . . . . . . . . . 413How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Other resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417Referenced Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

Contents ix

x IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figures

The team - Urs, Mike, Michel, Ivo, Charlotte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv1-1 Storage management issues today . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41-2 Infrastructure growth issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51-3 Manual storage management issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61-4 Current methods of compiling information about storage networks. . . . . . . . . . . . . . . 71-5 Large SAN environment to be managed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91-6 Storage management architecture for a suite of solutions. . . . . . . . . . . . . . . . . . . . . 111-7 Storage networking standards organizations and their standards . . . . . . . . . . . . . . . 131-8 Standards for Interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141-9 SAN Manager — Outband management path over the IP network . . . . . . . . . . . . . . 161-10 SAN Manager — Inband management path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171-11 Inband management services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191-12 The future of standards in SAN management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201-13 SMIS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211-14 SMIS Architecture in relation to SNIA storage model . . . . . . . . . . . . . . . . . . . . . . . . 221-15 CIM/WBEM management model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231-16 CIM Agent & CIM Object Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241-17 SAN management summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252-1 IBM Tivoli SAN Manager V1.2 — New functions and features . . . . . . . . . . . . . . . . . 282-2 IBM Tivoli SAN Manager operating environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . 302-3 IBM Tivoli SAN Manager functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312-4 Functions of IBM Tivoli SAN Manager and Agents . . . . . . . . . . . . . . . . . . . . . . . . . . 322-5 IBM Tivoli SAN Manager — inband and outband discovery paths . . . . . . . . . . . . . . 332-6 Levels of monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342-7 Tivoli SAN Manager — Root menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352-8 Tivoli SAN Manager — explorer display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362-9 iSCSI SmartSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362-10 Tivoli SAN Manager — SAN submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372-11 NetView physical topology display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382-12 Map showing host connection lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392-13 Zone view submap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402-14 Zone members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412-15 Device Centric View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422-16 Device Centric View — explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432-17 Host Centric View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432-18 Host Centric View — logical volumes and LUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442-19 Navigation tree for Tivoli SAN Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452-20 Switch events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462-21 Map Showing Effects of Switch Losing Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472-22 Graph of # Frames Transmitted over 8 ports in a 2 minute interval. . . . . . . . . . . . . . 482-23 Number of Frames Transmitted Over Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492-24 Vendor application launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502-25 Adornment shown on fibre channel switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513-1 Deployment overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563-2 Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573-3 Typical HBAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583-4 Structure of a fiber optic cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593-5 Single mode and multi mode cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

© Copyright IBM Corp. 2002, 2003. All rights reserved. xi

3-6 SC fibre optic cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613-7 LC connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623-8 GBIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623-9 Fibre Channel topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633-10 Fibre Channel point-to-point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633-11 Fibre Channel Arbitrated Loop (FC-AL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643-12 Fibre Channel switched fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653-13 Component placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673-14 Inband scanning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693-15 Outband scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703-16 Components of a manger install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713-17 Level s of Fabric Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723-18 RNID discovered host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743-19 Sample outband requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763-20 Display and configure outband agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773-21 Outband management only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803-22 Sample inband requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813-23 Configure Agents — Inband only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833-24 Inband management only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843-25 Sample inband/outband requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843-26 Inband & outband in Configure Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863-27 Inband and outband management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873-28 HOSTS file placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883-29 Standby server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903-30 Failover process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914-1 IBM Tivoli SAN Manager —supported operating system platforms. . . . . . . . . . . . . . 964-2 Installation of IBM Tivoli SAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964-3 Verifying system host name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974-4 Computer name change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974-5 DB2 services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994-6 Windows Components Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004-7 SNMP install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014-8 SNMP Service Properties panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024-9 Selecting the product to install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034-10 Welcome window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034-11 Installation path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044-12 Port range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044-13 DB2 admin user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054-14 SAN Manager database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054-15 WebSphere Administrator password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064-16 Host authentication password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074-17 NetView install drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074-18 NetView password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084-19 Installation path and size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084-20 Installation progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094-21 Finished installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094-22 Tivoli SAN Manager Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104-23 Agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114-24 Agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124-25 Welcome window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134-26 Installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144-27 Server name and port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144-28 Agent port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

xii IBM Tivoli Storage Area Network Manager: A Practical Introduction

4-29 Agent access password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164-30 Installation size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164-31 Installation finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174-32 Agent Windows service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184-33 Console installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194-34 Start the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204-35 Welcome window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214-36 Installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214-37 Server information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224-38 Console ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224-39 Console access password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234-40 Tivoli NetView installation drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234-41 Tivoli NetView service password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244-42 Installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244-43 Installation finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254-44 Console service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254-45 Configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264-46 SNMP traps to local NetView console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274-47 SNMP trap reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274-48 Trapfwd daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1294-49 SNMP traps for two destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304-50 Agent configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314-51 Outband Agent definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314-52 Login ID definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324-53 Not responding inband agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324-54 SAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1334-55 Uninstalling the SAN Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354-56 Agent uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374-57 Uninstalling remote console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384-58 Uninstalling Tivoli GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1395-1 NetView window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505-2 NetView Explorer option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515-3 NetView explorer window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525-4 NetView explorer window with Tivoli Storage Area Network Manager view . . . . . . 1525-5 NetView toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535-6 NetView tree map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535-7 NetView objects properties menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545-8 NetView objects properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545-9 IBM Tivoli SAN Manager icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555-10 SAN Properties menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1585-11 ITSO lab1 setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595-12 ITSO lab1 topology with zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1605-13 IBM Tivoli NetView root map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615-14 Storage Area Network submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615-15 Topology views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1625-16 Storage Area Network view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1625-17 Topology view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1635-18 Switch submap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1635-19 Interconnect submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1645-20 Physical connections view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1645-21 NetView properties panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1655-22 Zone view submap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1655-23 FASTT zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Figures xiii

5-24 Device Centric View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675-25 Host Centric View for Lab 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1685-26 iSCSI discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695-27 iSCSI SmartSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695-28 SAN Properties menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705-29 IBM Tivoli SAN Manager Properties — Filesystem . . . . . . . . . . . . . . . . . . . . . . . . . 1715-30 IBM Tivoli SAN Manager Properties — Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1725-31 IBM Tivoli SAN Manager Properties — Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1725-32 Changing icon and name of a device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735-33 Connection information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735-34 Sensors/Events information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1745-35 Brocade switch management application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1755-36 NetView objects properties — Other tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1765-37 Launch of the management page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1765-38 PATH environment variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1775-39 NetView Tools menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1785-40 San Data Gateway specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1785-41 Launch Tivoli Storage Resource Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1795-42 IBM Tivoli SAN Manager — normal status cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805-43 Status cycle using Unmanage function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815-44 Status cycle using Acknowledge function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815-45 Lab environment 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825-46 Discovery of MDS 9509 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1835-47 MDS 9509 properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1845-48 MDS 9509 connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1845-49 Trap received by NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1855-50 Connection lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1855-51 Connection restored. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1865-52 Marginal connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1865-53 Dual physical connections with different status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1875-54 Agent configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1885-55 Unsafe removal of Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1885-56 Connection lost on a unmanaged host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895-57 Unmanaged host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895-58 Clear History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905-59 NetView unmanaged host not discovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905-60 SAN lab - environment 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1915-61 Switch down Lab 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925-62 Switch up Lab 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935-63 RNID discovered host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945-64 RNID discovered host properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945-65 RNID host with changed label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955-66 Only outband agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965-67 Explorer view with only outband agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975-68 Switch information retrieved using outband agents . . . . . . . . . . . . . . . . . . . . . . . . . 1975-69 Inband agents only without SAN connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1985-70 Inband agents only with SAN connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1995-71 Switches sensor information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1995-72 Discovered SAN with no LUNS defined on the storage server . . . . . . . . . . . . . . . . 2005-73 MSS zoning display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015-74 MSS zone with CRETE and recognized storage server . . . . . . . . . . . . . . . . . . . . . 2025-75 “Well-placed” agent configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035-76 Discovery process with one well-placed agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

xiv IBM Tivoli Storage Area Network Manager: A Practical Introduction

6-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2086-2 SNMP architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2096-3 MIB tree structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2106-4 Enabling the advanced menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116-5 MIB loader interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2136-6 Select and load TRP.MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2146-7 Loading MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2146-8 NetView MIB Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2156-9 FE-MIB — Error Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2166-10 SW MIB — Port Table Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2166-11 Private MIB tree for bcsi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2176-12 MIB Data Collector GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2176-13 starting the SNMP collect daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2186-14 internet branch of MIB tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2186-15 Private arm of MIB tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2196-16 Enterprise branch of MIB tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2196-17 bcsi branch of MIB tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2206-18 swFCPortTxFrames MIB object identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216-19 Adding the nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216-20 Add Nodes to the Collection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2226-21 Newly added Data Collection for swFCTxFrames . . . . . . . . . . . . . . . . . . . . . . . . . . 2236-22 Restart the collection daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2236-23 Purge Data Collection files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2246-24 Select ITSOSW2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2266-25 Building graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2266-26 Graphing of swFCTxFrames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2276-27 Graph properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2276-28 Real-time reporting — Tool Builder overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2286-29 Enabling all functions in NetView. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2286-30 MIB tool Builder interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2296-31 Tool Wizard Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2296-32 Tool Wizard Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2306-33 SW-MIB — Port Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2306-34 Final step of Tool Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2316-35 New MIB application — FXPortTXFrames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2316-36 Monitor pull-down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2326-37 NetView Graph starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2326-38 Graph of FCPortTXFrames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2336-39 Graph Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2336-40 Polling Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2346-41 Tool Builder with all MIB objects defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2346-42 All MIB objects in NetView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2356-43 SmartSet Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2356-44 Selected Fibre Channel switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2366-45 Defining a SmartSet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2376-46 Advanced window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2386-47 Advanced window with 2109s added. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2396-48 New SmartSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2396-49 New SmartSet — IBM 2109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2406-50 SmartSet topology map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2416-51 ITSOSW1, ITSOSW2 and ITSOSW3 in IBM2109 SmartSet . . . . . . . . . . . . . . . . . . 2426-52 Additional SmartSets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2436-53 IBM2109 SmartSet defined to Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Figures xv

6-54 NetView Graph starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2446-55 IBM2109 SmartSet data collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2456-56 Selected MIB instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2456-57 Graph showing selected instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2466-58 Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2486-59 Server Setup options window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2496-60 Clear Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2496-61 Clear databases warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2496-62 NetView stopping — clearing databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2506-63 With seed file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2506-64 Without seed file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2517-1 iSCSI components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2547-2 Fibre Channel versus iSCSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2558-1 Event notification overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2608-2 SAN Manager generated SNMP traps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2618-3 Event Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2628-4 IBM Director Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2648-5 SNMP event from SAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2659-1 ED/FI - SAN Error Predictor overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2689-2 Failure indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2699-3 Adornment example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2699-4 Error processing cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2709-5 Fault Isolation indication flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2719-6 ED/FI Menu Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2729-7 ED/FI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2739-8 Rule description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2749-9 Adornments on the topology map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2759-10 Devices currently in Notification State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2759-11 Indicated device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2769-12 NetView Search dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2779-13 Found objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2779-14 Found device on topology map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2789-15 Clear the notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2799-16 After clearing the notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2799-17 Topology change after notification clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28010-1 IBM Tivoli SAN Manager components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28410-2 Tivoli Storage Manager integration with Tivoli SAN Manager . . . . . . . . . . . . . . . . . 28510-3 Sample environment: Backing up Tivoli SAN Manager to Tivoli Storage Manager . 28610-4 Procedures used to backup IBM Tivoli SAN Manager. . . . . . . . . . . . . . . . . . . . . . . 29110-5 IBM Tivoli SAN Manager restore procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30210-6 Agent is contacted after restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30410-7 Netview restart failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30610-8 Tivoli Storage Manager restore interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30610-9 IBM Tivoli SAN Manager agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30810-10 IBM Tivoli SAN Manager Disaster Recovery procedures . . . . . . . . . . . . . . . . . . . . 30910-11 Full system restore result. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31010-12 System Objects restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31110-13 System Objects restore results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31110-14 IBM Tivoli SAN Manager interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31310-15 DB2 Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31411-1 IBM Tivoli SAN Manager — Logging and tracing overview . . . . . . . . . . . . . . . . . . . 31811-2 Service Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32211-3 NetView trap reception. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

xvi IBM Tivoli Storage Area Network Manager: A Practical Introduction

11-4 NetView daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32411-5 Enable trapd logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32511-6 Stop and start daemons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32511-7 Recycling daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32512-1 TEC architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33512-2 Tivoli Lab environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33612-3 Active Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33712-4 Import Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33712-5 Import Class Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33812-6 Compile Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33912-7 Load Rule Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33912-8 Restart TEC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34012-9 TEC Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34012-10 Create Event Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34112-11 Create Filter in Event Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34112-12 Event Group Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34212-13 Add Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34212-14 Event Group Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34312-15 Assign Event Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34312-16 Assigned Event Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34412-17 Configured Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34412-18 TEC Console main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34512-19 TEC console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34512-20 General tab of event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34612-21 Event attribute list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34712-22 Set Event Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34812-23 Enable TEC events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34912-24 Configuration GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34912-25 Choose type of adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35012-26 Enter TEC server name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35012-27 TEC server platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35112-28 TEC server port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35112-29 Configure forwardable events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35112-30 Choose SmartSets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35212-31 Configure adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35212-32 Start the adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35212-33 Defective cable from bonnie to itsosw1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35312-34 Events for cable fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35312-35 Condition cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35413-1 Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35913-2 Policy Region tonga-region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36013-3 Managed Resources for Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36013-4 Policy Region Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36113-5 Profile Manager Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36113-6 Inventory Profile Global Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36213-7 Inventory Profile PC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36313-8 Inventory Profile UNIX Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36413-9 Distribute Inventory Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36513-10 Distribute Inventory Profile dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36613-11 Distribution Status Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36713-12 Create Query Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36713-13 Edit Inventory Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36813-14 Output for IBM Tivoli SAN Manager Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Figures xvii

13-15 Output for IBM Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36913-16 Software Package Editor with new package ITSANM-Agent. . . . . . . . . . . . . . . . . . 37013-17 Properties dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37113-18 Add an execute program action to the package . . . . . . . . . . . . . . . . . . . . . . . . . . . 37213-19 Install dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37313-20 Advanced tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37413-21 Add directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37513-22 Remove dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37613-23 Advanced properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37713-24 Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37813-25 Ready-to-build software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37913-26 Policy Region with Profile Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37913-27 Create Software Package Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38013-28 Profile Manager with Profiles and Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38113-29 Import Software Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38213-30 Import and build a software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38313-31 Install a software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38413-32 Install Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38513-33 Remove a Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38614-1 Tivoli Data Warehouse data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38815-1 IBM Tivoli Monitoring Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39215-2 Policy Region tonga-region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39315-3 Profile Manager PM_DM_ITSANM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39415-4 Create Monitoring Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39415-5 Add Parametric Services Model to Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39515-6 Edit Resource Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39615-7 Parameters of Resource Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39715-8 Indications and actions of resource models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39815-9 TEC forwarding of events from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39815-10 Profilemanager for Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39915-11 TEC events from Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400A-1 Sensor Event data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

xviii IBM Tivoli Storage Area Network Manager: A Practical Introduction

Tables

1-1 Differences in discovery capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173-1 SAN Manager using vendor HBAs and switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . 754-1 Procedure to change passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465-1 IBM Tivoli SAN Manager symbols color meaning . . . . . . . . . . . . . . . . . . . . . . . . . . 1555-2 IBM Tivoli NetView additional colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1555-3 Problem determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565-4 Status propagation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157A-1 MIB II OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402A-2 FE MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402A-3 FC-MGMT MIB OIDS used by Advanced Topology Scanner . . . . . . . . . . . . . . . . . 403A-4 FC-MGMT MIB Sensor Event Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

© Copyright IBM Corp. 2002, 2003. All rights reserved. xix

xx IBM Tivoli Storage Area Network Manager: A Practical Introduction

Notices

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

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

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

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

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

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

© Copyright IBM Corp. 2002, 2003. All rights reserved. xxi

TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

AIX®Domino™DB2®^™Enterprise Storage Server®ESCON®IBM®ibm.com®Lotus®

MQSeries®NetView®OS/2®OS/390®Predictive Failure Analysis®pSeries™Redbooks™Redbooks(logo) ™RS/6000®

Tivoli Enterprise™Tivoli Enterprise Console®Tivoli®TotalStorage®TME®WebSphere®xSeries®

The following terms are trademarks of other companies:

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

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

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

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

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC.

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

xxii IBM Tivoli Storage Area Network Manager: A Practical Introduction

Preface

Now that you have installed your SAN, how are you going to manage it? This IBM® Redbook describes the new product, IBM Tivoli® Storage Area Network Manager, an active, intelligent, business-centric management solution for storage resources across the enterprise.

IBM Tivoli Storage Area Network Manager provides effective discovery and presentation of SAN physical and logical topologies and provides multiple views of the SAN, including zones. Through its interface, it can be configured to show historical and real-time monitoring of SAN fabric devices.

With IBM Tivoli Storage Area Network Manager, you will know what's on your SAN, how the devices are connected, and how storage is assigned to the hosts. If something goes wrong, or new devices are added, the topology display automatically updates to show the changed topology. SAN generated events can be displayed on the manager system, or forwarded to another SNMP manager or Tivoli Enterprise™ Console.

This book is written for those who want to learn more about IBM Tivoli SAN Manager, as well as those who are about to implement it.

This second edition of the book is current to IBM Tivoli SAN Manager V1.2.

The team that wrote this redbookThis redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, San Jose Center.

Charlotte Brooks is an IBM Certified IT Specialist and Project Leader for Tivoli Storage Management and Open Tape Solutions at the International Technical Support Organization, San Jose Center. She has 12 years of experience with IBM in the fields of IBM ~ pSeries™ servers, AIX® and storage. She has written nine Redbooks™, and has developed and taught IBM classes in all areas of storage management. Before joining the ITSO in 2000, she was the Technical Support Manager for Tivoli Storage Manager in the Asia Pacific Region.

Michel Baus is an IT Architect for @sys GmbH, an IBM Business Partner in Karlsruhe, Germany. He has eight years of experience in the areas of UNIX®, Linux, Windows® and Tivoli Storage and System Management. He holds several certifications within technical and sales fields and is an IBM Tivoli Certified Instructor. He has developed and taught several storage classes for IBM Learning Services, Germany. He was a member of the team that wrote the redbook Managing Storage Management.

Michael Benanti is an IBM Certified IT Specialist in Tivoli Software, IBM Software Group. In his six years with IBM, he has focused on architecture, deployment, and project management in large SAN implementations. Mike also works with the Tivoli World Wide Services Planning Organization, developing services offerings for IBM Tivoli SAN Manager and IBM Tivoli Storage Resource Manager. He has worked in the IT field for more than 11 years, and his areas of expertise include network and systems management disciplines using Tivoli NetView® and data communications hardware research and development. He was an author of the first edition of this redbook.

© Copyright IBM Corp. 2002, 2003. All rights reserved. xxiii

The team - Urs, Mike, Michel, Ivo, Charlotte

Ivo Gomilsek is an IT Specialist for IBM Global Services, Slovenia, supporting the Central and Eastern European Region in architecting, deploying and supporting SAN/storage/DR solutions. His areas of expertise include SAN, storage, HA systems, IBM ~ xSeries® servers, network operating systems (Linux, MS Windows, OS/2®), and Lotus® Domino™ servers. He holds several certifications from various vendors (IBM, Red Hat, Microsoft®). Ivo was a member of the team that wrote the redbook Designing and Optimizing an IBM Storage Area Network, and contributed to various other Redbooks about SAN, Linux/390, xSeries, and Linux. Ivo has been with IBM for five years and was an author of the first edition of this redbook.

Urs Moser is an Advisory IT Specialist with IBM Global Services in Switzerland. He has more than 25 years of IT experience, including more than 13 years experience with Tivoli Storage Manager and other Storage Management products. His areas of expertise include Tivoli Storage Manager implementation projects and education at customer sites, including mainframe environments (OS/390®, VSE, and VM) and databases. Urs was a member of the team that wrote the redbook Using Tivoli Storage Manager to Back Up Lotus Notes.

Thanks to the following people for their contributions to this project:

The authors of the first edition of this redbook: Michael Benanti, Hamedo Bouchmal, John Duffy, Trevor Foley, and Ivo Gomilsek.

Deanna Polm, Emma Jacobs, Gabrielle VelezInternational Technical Support Organization, San Jose Center

xxiv IBM Tivoli Storage Area Network Manager: A Practical Introduction

Doug Dunham, Nancy Hobbs, Jason Perkins, Todd Singleton, Arvind Surve, IBM Tivoli SAN Manager Development, San Jose

Johanna Hislop, Dave MerbachIBM Tivoli SAN Manager Development, Rochester

Rob Basham, Steve McNeal, Brent YardleyIBM SAN Development, Beaverton

Bill Medlyn, Daniel WolfeIBM Tivoli SAN Manager Development, Tucson

Steve Luko IBM Tivoli SAN Manager Marketing, Tucson

Kaladhar VorugantiAlmaden Research Center

Murthy SamaCisco Systems

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcomeYour comments are important to us!

We want our Redbooks™ to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways:

� Use the online Contact us review redbook form found at:

ibm.com/redbooks

� Send your comments in an Internet note to:

redbook@us.ibm.com

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. QXXE Building 80-E2650 Harry RoadSan Jose, California 95120-6099

Preface xxv

xxvi IBM Tivoli Storage Area Network Manager: A Practical Introduction

Summary of changes

This section describes the technical changes made in this edition of the book and in previous editions. This edition may also include minor corrections and editorial changes that are not identified.

Summary of Changes for SG24-6848-01 for IBM Tivoli Storage Area Network Manager: A Practical Introduction as created or updated on September 9, 2003.

September 2003, Second EditionThis revision reflects the addition, deletion, or modification of new and changed information described below.

New information� Version 1 Release 2 of IBM Tivoli Storage Area Network Manager

– AIX Manager and Linux Agent support – iSCSI Support to integrate iSCSI into SAN management – Performance enhancements by removing previous software requirements – Error Detection and Fault Isolation (ED/F - SAN Error Predictor)

� IBM Tivoli Bonus Pack for SAN Management

© Copyright IBM Corp. 2002, 2003. All rights reserved. xxvii

xxviii IBM Tivoli Storage Area Network Manager: A Practical Introduction

Part 1 Introduction

In Part 1 we talk about why customers need management for their Storage Area Networks, focusing on the costs and challenges of managing it manually today. We then introduce IBM Tivoli Storage Area Network Manager, a new solution for displaying and monitoring physical and logical SAN topologies, receiving events, and reporting on SAN performance statistics and counters.

Part 1

© Copyright IBM Corp. 2002, 2003. All rights reserved. 1

2 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 1. Introduction to Storage Area Network management

Industry needs storage management today in open environments for the same reasons that storage management was needed in the mainframe environment in the early and mid-1980s. Businesses are generating data so fast that data storage and data management capabilities are being overwhelmed. If these capabilities cannot handle the growth, then at some point, “the next transaction” cannot be captured, and the business will stop. Here are two key problems which impact this situation:

� Storage costs are too high.� Storage management costs are too high.

Storage Area Networks (SANs) are increasingly prevalent, but now face the same problems found in traditional IP networking in the 80’s. Two of the key challenges for SANs are to standardize and provide functional, open management tools.

In this chapter:

� We identify the business and technology considerations which caused the development of SAN management tools.

� We describe the big picture of data and storage management, and position SAN management within that context.

� We discuss SAN management, including:

– The benefits of using SAN management tools– The functions that SAN management tools should accomplish

� We consider the impact of standards on SAN management.

In subsequent chapters we introduce a new solution for SAN management, IBM Tivoli Storage Area Network Manager, and discuss deployment architectures, installation and design considerations, operations, and maintenance.

1

© Copyright IBM Corp. 2002, 2003. All rights reserved. 3

1.1 Why do we need SAN management?Storage Area Network management is the set of tools, policies, processes, and organization that provide information about and that monitor the devices in a Storage Area Network (SAN). In conjunction with other storage management tools, this helps ensure the availability of data in a SAN. Cross vendor standardized Storage Area Network management can help users to easily adopt SANs faster.

1.1.1 Storage management issues todayThe major issues in storage management are shown in Figure 1-1.

Figure 1-1 Storage management issues today

GrowthGrowth is being driven by three general trends:

� Business transaction volumes are growing.

� Businesses are using computers to store information that used to be stored only on film or paper.

� There are new data types (such as music, video clips, images, and graphical files) that require significantly more storage per file than older data types like flat files.

The data and storage infrastructure that support this growth is growing dramatically. That growth rate is estimated to range from 50-125% annually, depending on the industry and consultant report of your choice. Consequently, the storage infrastructure must also grow to support the growth in business transactions. See Figure 1-3.

Growth is overwhelming people, tools, and processesbusiness transactions storing new and different data types

(medical records, voice, images, presentations)new data types are larger than the old data types

Unmanaged storage costs too much

Manual storage management costs too much

Multivendor management is hard to master

4 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 1-2 Infrastructure growth issues

Server growthMajor companies have hundreds of large UNIX servers, and sometimes thousands of Windows servers. They are deploying more servers every quarter, and most large companies have a large variety of different hardware and software platforms, rather than standardizing on particular configurations.

Staffing growthWhile we know that storage and data are growing rapidly, support staff numbers are not. This only exacerbates the problem. An average corporate server may be supporting in the order of 3 TB of data in the coming years, yet it is estimated that the typical open systems administrator can manage only 1 TB. Since in today’s economic times, businesses are looking to cut costs, most are cutting rather than increasing their IT departments. Clearly more intelligent and powerful applications will be required to support this environment.

Storage and SAN growthAlthough companies are growing their storage at around 50 to 125% per year on average, larger companies may see even higher growth rates. To handle the growth in storage, storage is being consolidated into Storage Area Networks (SANs). SANs are increasingly being deployed by customers and customers may deploy up to 50% of their disk via SAN in the coming years. But, SANs do not solve the underlying problems of mismanaged data and its explosive growth. SANs concentrate the storage, the data, and the problems, and emphasize the need for SAN management. In fact, the cost of SANs and their management is a major inhibitor to further SAN adoption — SANs are a separate new manageable entity in themselves, along with their associated hardware and software components.

Early adopters who are now expanding the SANs they deployed some time ago are finding a different set of problems from those they had when implementing their first SAN. Early on, the main SAN problems were related to interoperability. With the growth in standardization for SANs, these issues are becoming less significant. Now, business who are trying to expand SANs in the enterprise are constrained by the difficulty in managing large-scale SANs with current processes, which are largely vendor-specific and/or manual.

Infrastructure Growth IssuesInfrastructure Growth Issues

Growth Vector Comment

Server Large companies have thousands of servers - mixture of Windows and different UNIX OS

StaffingEach corporate server may grow to 3TB data by 2004 - a typical open system administrator can look after 1TB

Storage

Average storage growth is 50 to 125% per year - largest companies may see much higher rates. SAN storage will soon be over 50% of total storage.SANs are being increasingly deployed

Chapter 1. Introduction to Storage Area Network management 5

One problem is that SAN management crosses traditional organizational boundaries. Networks are traditionally managed by network management groups. Storage has traditionally been managed by the individual operating system platform groups or by a specialized storage group. SAN managers have to understand both networking and storage. Which group, then, should have the responsibility for managing SANs? As will be seen later in this book, IBM Tivoli Storage Area Network Manager targets exactly this intersection of the two skill areas — using network management techniques to manage the SAN topology, while providing storage management-oriented logical views.

Manual storage management costs too muchThe major issues of infrastructure growth are shown in Figure 1-3.

Figure 1-3 Manual storage management issues

In today’s environments, IT organizations typically manage storage across some or all of these areas:

� OS platform administration — handles disks associated with individual servers� Backup and recovery — tape� Business continuance and Disaster Recovery — disk and tape at Disaster Recovery sites� Networking group — access to NAS and SAN devices, often the overall design� Storage group — any of the previous functions, cross-platform

In large companies, these disciplines often each have separate teams. Coordinating these different teams is a major issue. In small corporations, these functions are usually handled by a single person, who is typically highly skilled and overworked. All the groups have their own spreadsheets, home-grown reports, personal databases, and Visio diagrams, etc., to manage their particular environments. And typically each area monitors and manages in isolation, not coordinating with the other functions.

IT organizations have historically been organized by operating system platform. A UNIX platform administrator managed the server, communications, disk and tape, and SANs, that is, everything to do with UNIX. The same applied to the Windows administrator.

Large corporations - different teams involvedUNIX platform management

Windows platform management

UNIX backup

Windows backup

Business Continuance and Disaster Recovery

Networking

Each of the above teams has its ownSpreadsheets

Home-grown reports

Personal databases

System or network diagrams

Coordination is problematicEach group develops its own policies

Policies not coordinated with each other, or with the mainframe group

Small corporations - the "one person who does it all" is spread too thinQuick notes in a personal notebook

Only resource which knows the infrastructure

6 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Centralizing storage management makes it possible to apply the same tools and processes to all business units within the company. For this reorganization to work effectively, new tools and new procedures are needed to support the new organizational structure.

IBM Tivoli SAN Manager is one of the key underlying new tools that support this movement towards a more consistent, more efficient, use of resources — that is, people, storage, and money.

For example, a company with 500 NT servers and 300 UNIX servers across different business units might have 2100 LUNs to be managed (1.5 x 500 + 4.5 x 300 = 2100). Managing that many filesystems manually is difficult. A growing percentage of companies have consolidated storage into Fibre Channel (FC) SANs, but they still have to manage the same number of LUNs. The LUNs are still associated with individual application servers, and storage on the FC storage frame is still logically segregated.

Some companies have a mix of FC storage pools, network-attached (NAS, iSCSI) storage pools, and direct-attached storage environments. Each FC storage pool is managed by its own storage manager. Each NAS pool has its own manager. Each small group of 25-30 (typically) direct-attached storage servers has its own platform administrator.

These administration costs can be at the user department level, at the division IT level, or at the corporate IT level. The costs are hard to aggregate, but are large.

1.1.2 Current generation of SAN management: spreadsheets and paperIn Figure 1-4, we consider current methods of storage management.

Figure 1-4 Current methods of compiling information about storage networks

When a user calls and says “my application stopped working!”, administrators (storage administrators, network administrators, application administrators or platform administrators) have to research, narrow down the possible causes, and make an educated guess as to the root cause of the problem. If the problem is confirmed as related to storage, may have to access several individual components in the storage infrastructure (for example, HBA, disk controller, disk system, microcode), one component at a time, sometimes several times for each component, as they try to identify the root cause.

The current approach to managing storage networks typically involves manual processes and point (that is, vendor-specific, non-interoperable) solutions.

Storage Network TopologyVisio diagram, typically out of date, or

Sometimes a hand-drawn diagram

Sometimes on an eraseable whiteboard

Switch Inventory and connectionsSpreadsheet, PC database, or WP document

Page in a personal notebook

Storage Frame Layout (logical-to-physical)Maintained by vendor, or

Customer-maintained in spreadsheet or management application

Server Information

Spreadsheet, PC database, or WP document

Chapter 1. Introduction to Storage Area Network management 7

Information concerning inventory, topology, and components is typically manual. Today’s tools are point-solutions, usually managing one single component, or components from a single vendor. If you need to look at 4 or 5 switches to track down a problem, you might need to log on to 4 or 5 switches, each with its own management software.

Here are some frequently encountered scenarios:

� The topology of the SAN is maintained on a Visio diagram somewhere, which was last updated some months ago “before we added those last 2 departments, and deployed several new switches, and I just didn’t have the time to update the diagram!”

� The server inventory (a spreadsheet or a PC database) was updated “in a consultant study 12 months ago”. Each platform group has its own inventory, which is kept separately from the other groups. Rarely does a company have an enterprise view of its infrastructure.

� The revision levels for all the Operating Systems, the patches, the HBA drivers, etc., is in a spreadsheet, which is somewhat up-to-date (“except for the last 3 rounds of server upgrades!”)

� The logical layout of the storage frames is kept either by the storage vendor themselves or on a spreadsheet which needs to be manually updated.

If a problem does arise, then the following tools and methods are typically used to identify and resolve the problem:

� To manage a switch, the administrator has to consult his spreadsheet to find the address, user ID and password of the switch, log on to the switch, run the switch management package (different for each brand of switch), and scan the menus to understand the SAN architecture, and write down what he needs to know on a piece of paper.

� To manage the storage frame, the administrator has to log on to the frame, and run its point-solution software (again, different for each manufacturer) to understand the storage frame.

� Then the administrator has to mentally or manually build a map of the SAN infrastructure.

� Then the administrator maps the specific problem to the infrastructure, forms an hypothesis, and tries to solve the problem.

� This is an iterative process.

With a small and stable SAN (for example, 2 switches, 12 servers, and 1 storage frame with 4 storage ports), managing the components via spreadsheets, PC databases, and point solution tools can be fairly effective for simple problems. In this environment, there are only 2 primary storage tools to learn (the switch tool and the storage frame tool), with only 2 switches and 1 frame to manage.

In this small environment, the administrator generally has the architecture in his head, knows all the components, and can usually identify and fix problems within a reasonable amount of time.

Note however that there is probably only one person in the organization who is familiar enough with the layout of the network to be able to do this. What happens if that person takes vacation, is ill, or leaves the organization?

With a complex SAN, the number of components to manage exceeds the ability of current tools and administrators to manage in a timely fashion. Just the discovery process alone can be very time-consuming.

8 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 1-5 shows a typical large storage network.

Figure 1-5 Large SAN environment to be managed

In this large storage network, there are many components, and many points of management:

� Infrastructure components:

– Each switch has its own management software:

• There are 2 different switch vendors.• There are at least 8 switches, each with 16 or 32 ports.

– Each storage frame has its own management tool:

• There are 4 different frames, each with 4-16 storage ports and 50 disks.• There are 2 frame vendors.

– Servers, file systems, and HBAs each have their own management tools:

• There are 300 servers (many not shown), each with 2 or more mount points or shares, each with 2 HBAs.

• There are 5 different platform operating systems (Windows 2000, NT, HP-UX, Solaris, AIX).

• There are different vendor HBAs (Emulex, JNI, IBM).

� Component management:

– Storage administrators manage the storage in the storage frame.– The storage vendor sometimes manages the logical-to-physical conversion (file system

to LUN) for the storage.– Platform administrators manage servers, file systems, and HBAs.– Backup and recovery are managed by yet a different group.– The client-facing IP network is managed by the network group, who also try to manage

the SAN as a whole.

The Scope of the SAN Management ProblemThe Scope of the SAN Management Problem

Chapter 1. Introduction to Storage Area Network management 9

To manage the physical infrastructure, the IT organization would have to individually manage each component of the SAN infrastructure. That is:

� 4 * 32 + 8 * 16 = 256 switch ports� 2 different switch management packages� 40 storage frame ports, approximately� 200 disks� 600 shares or mount points� 600 HBAs� 300 instances of 4 different operating systems� TOTAL NUMBER OF OBJECTS TO MANAGE = 1996

When a problem arises in this complex environment, administrators turn to the manual documents and point-solution tools to help them narrow the focus of their investigation. Considering the state of the documents and the information with which they are working, their task is “challenging”, and the business exposure is high. Mission-critical servers cannot afford hours of downtime just to find a root cause, much less additional time to fix the problem. Mission-critical storage, servers, and applications, by definition, need to be available 24x7.

Trying to manage these 2000-odd components manually cannot be done consistently over time.

Summary� Storage and data are growing rapidly.

� SANs are growing, and are too big to manage manually.

� Manual storage management costs a lot.

� Companies cannot continue to manage storage and data “the old way” (managing individual components), and be successful. Companies MUST adopt new tools to manage storage and data.

1.2 New tools for SAN management are neededClearly, new tools for SAN management are needed.

Customers want the following capabilities from SAN management software:

� To manage their SAN properly� To be able to extend the benefits of a SAN to the enterprise� To do so in a cost-effective fashion (both storage, and administration)

Given the multi vendor infrastructure environment, storage components and storage management tools must be based on standards. Standards in Storage management promise the following benefits:

� Ensure interoperability� Protection of Investment� Freedom of choice:

– Is vendor-independent– Drives pricing towards commodity pricing– Results in attempts by manufacturers to add value above the standards

10 IBM Tivoli Storage Area Network Manager: A Practical Introduction

1.2.1 Storage management componentsFigure 1-6 shows the storage management infrastructure functions from the low level device solutions all the way up to the business management level. The current set of Tivoli solutions already provide much of the functions in the Business Management section (that is, Systems Management, Storage Management and Security Management).

IBM Tivoli Storage Manager, IBM Tivoli Storage Resource Manager and IBM Tivoli SAN Manager provide the functionality for the middle Storage Resource Management layer. They interoperate with and utilize the lower level storage infrastructure layer applications. These are often vendor-specific solutions, such as individual Element Managers or Replication Solutions. These also encompass some upcoming products, such as for Virtualization.

Figure 1-6 Storage management architecture for a suite of solutions

SAN management tools were developed to help address the issues described in the previous section — to consolidate into one place all the information needed to manage the components of a SAN so that storage administrators can keep the physical and logical storage environment operating all the time.

With the right SAN management tools, from one console, storage administrators should be able to see all that happens in their storage infrastructure:

� By hosts in the SAN� By devices in the SAN� By topology of the SAN

These are some of the benefits of using SAN management tools:

� Technical benefits:

– Effective discovery and presentation of SAN physical and logical topologies for small or large SANs

– Continuous real-time monitoring, with rapid Error Detection and Fault Isolation

Comprehensive Architecture for a Suite of Comprehensive Architecture for a Suite of Storage Management SolutionsStorage Management Solutions

BusinessManagement

StorageResource

Management

StorageInfrastructure

Security ManagementStorage ManagementSystems Management

Applications

Business Processes

Policy Based Automation

ReplicationSubsystemReporting

ElementManagers

VirtualizationMedia

Managers

FileSystemsVolume

Mgrs

Devices

Backup & Recovery / Advanced SAN Management

Enterprise Policy Based Automation

Monitoring

Reporting

Operations

PerformanceAvailabilityEventAssetCapacity

SANFibre ChanneliSCSI

NASDAS TAPE

Chapter 1. Introduction to Storage Area Network management 11

– Support for open SAN standards– Minimize storage and SAN downtime– Provide a framework to extend the SAN to the enterprise

� Business benefits:

– Increase revenue by improving availability for applications hosted on the SAN– Reduce costs (both administration & storage)

These are the main attributes of a good SAN management tool:

� Standards based

� Strong architecture:

– Centralized repository– Based on an enterprise database– Discovers all components of a SAN– Integrated with an enterprise console– Identifies errors and isolates faults– Thresholds for reporting and actions

� Easy to navigate, understand

� Flexible and extensible:

– Provides topology views (physical) views — host-centric and switch-centric– Viewing a single SAN, or all SANs, in an organization– Ability to launch vendor-provided management applications from single console– Reporting, both standard, and customizable

1.2.2 Standards and SAN management toolsFor the storage networking community (both vendors and buyers), standards form the basis for compatibility and interoperability.

� Standards enable buyers to pick the solutions they want to implement with the knowledge that today’s solution will be interoperable with tomorrow’s solution, and that existing hardware investments will be protected as the environments are extended.

� For vendors, standards give the confidence that a wide market exists for their solutions, and lowers the costs of compatibility testing.

Today, there are at least 10 organizations involved in creating standards for storage, storage management, SAN management, and interoperability. Figure 1-7 shows the key organizations involved in developing and promoting standards relating to storage, storage management, and SAN management, and the relevant standards for which they are responsible.

12 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Standards organizations and standardsFigure 1-7 shows some of the main SAN management standards organizations.

Figure 1-7 Storage networking standards organizations and their standards

Industry organizations, such as the Storage Networking Industry Association (SNIA) and the Fibre Alliance, have taken a leading role in facilitating discussions among vendors and users. Members chair working groups, looking at a wide range of subjects relating to storage and SANs such as discovery and management, backup and disaster recovery. Developments by these organizations are considered de-facto standards. Recommendations from these organizations are submitted to the officially recognized standards bodies (IETF, ISO and ANSI) for consideration as a formal standard.

A key standard is contained in the FC-MI (Fibre Channel — Methodologies for Interconnects) technical report published by the ANSI T11 standards committee. Taken as a whole, the FC-MI report addresses multi-vendor interoperability for Storage Area Networks. The next generation of the standard FC-MI-2 is already in development.

This report describes a required set of common standards for device and management interoperability in both loop and switched fabric environments. Compliance to the standards defined by the FC-MI allows for operational interoperability between hosts, storage devices, and fabric components over a wide variety of Fibre Channel topologies. It also provides for a common approach to SAN device discovery and management.

Storage Networking Industry Association (SNIA)SAN umbrella organizationIBM participation: Founding member Board, Tech Council, Project Chair

Internet Engineering Task Force (IETF)Formal standards for SNMP and MIBs

Fibre Channel Industry Association (FCIA)Sponsors customer eventsIBM participation: Board

American National Standards Institute (ANSI)X3T11 for FC/FICON standardsX3T10 for SCI standardsIBM participation

Marketing

SAN Management Standards Bodies

Jiro (StoreX)Sun consortium

Fibre AllianceEMC consortium

National StorageIndustry ConsortiumPre-competitiveconsortium

SCSI Trade AssociationTechnology roadmapsIBM participation:Member

International Organization forStandardization (ISO)International standardizationIBM Softwaredevelopment ISO Certified

Distributed Management Task Force (DMTF)Development of CIMIBM participation

De-facto Standards Formal Standards

Chapter 1. Introduction to Storage Area Network management 13

ANSI has defined all the principal standards relating to physical interfaces, protocols, and management interfaces that would be exploited by the hardware vendors:

� FC-PH specifies the physical and signaling interface. FC-PH-2 and PC-PH-3 specify enhanced functions added to FC-PH.

� FC-FG, FC-SW, FC-GS-2, FC-GS-3, FC-SW-2, FC-FS, and draft standards for FC-GS-4 (target announcement date, August 2003) and FC-FS-2 are all documents relating to switched fabric requirements.

� FC-AL specifies the arbitrated loop topology.

FC-MI builds on these standards and groups device interoperability into four areas, shown in Figure 1-8.

Figure 1-8 Standards for Interoperability

A single device may have to comply with all four standards. Taken together, these standards define a set of common specifications that a device must adhere to in order to be compliant with FC-MI compliant devices at both the operational and management levels.

SAN management using FC-MISAN management requirements are defined in the discovery and management section of the FC-MI report. This section outlines the ANSI and other standards that Fibre Channel devices must comply with to ensure that all devices, irrespective of vendor or type of device, can be discovered using FC-MI compliant management tools.

Adherence to the existing standards defined in the FC-MI report enables a consistent approach for managing storage and SAN components, whether hosts, storage systems, or fabric components such as switches, gateways, or routers. The standards also provide a basis for advanced management capabilities, such as error detection and fault isolation (ED/FI), and predictive analysis of reported errors to identify pending component failures.

Storage Network Management - Storage Network Management - Standard Behaviors for InteroperabilityStandard Behaviors for Interoperability

Management Behaviors The set of standards required to be interoperable at the management level

Loop Behaviors The set of standards required to create interoperable Arbitrated Loops

Fabric Behaviors The set of standards required to create interoperable Switched Fabrics. A switched fabric is defined as being either a single switch, or 2 or more switches connected via E-ports

FC Port Behaviors The set of standards that end-point ports must support for devices to be interoperable in the defined switched fabrics and arbitrated loops

14 IBM Tivoli Storage Area Network Manager: A Practical Introduction

The following is a partial list of the current standards that different SAN components, end points (hosts, storage subsystems, gateways, etc.), Host Bus Adapter (HBA) drivers, and fabric components must support to be compliant with FC-MI for SAN management:

� Name Server, as defined in ANSI FC-GS-3

� Management Service, as defined in FC-GS-3:

– Configuration Server– Unzoned Name Server– Fabric Zone Server

� Fabric event reporting — These are Extended Link Services (ELS) commands defined in the FC-FS (Framing and Signaling Interface) for notification of fabric events

– RSCN — Registered State Change Notification– RLIR — Registered Link Incident Record

� HBA drivers must support an API (such as the SNIA SAN management HBA API) that must be capable of:

– Issuing Name Server, Fabric Management Server, and end point queries, and – Notifying the driver (or other recipient) of fabric events

� SNMP Monitoring, using the IETF FC Management MIB (previously known as the Fibre Alliance MIB) and trap

� Respond to end point queries

– RNID — Request Node Identification Data– RLS — Read Link Error Status Block

Taken together, these different discovery and reporting mechanisms allow a complete SAN topology to be determined and monitored, along with advanced capabilities such as performance analysis and error detection and fault isolation.

1.2.3 DiscoveryDiscovery uses two approaches for discovering SAN device information:

� Outband queries — over an IP network via standardized MIBs, which typically are loaded only onto the managed switches. IBM Tivoli SAN Manager gathers SNMP-collected information from outband agents.

� Inband queries — using Fibre-Channel protocols. In the case of IBM Tivoli SAN Manager, an Agent loaded onto the target server queries a standard HBA API loaded onto the managed host, which then queries reachable devices in the SAN. The information obtained is returned to the Manager.

Tivoli SAN Manager stores the results of inband and outband discoveries through the Agents in its database, co-relates it to look for duplication, and uses the information to draw or re-draw the topology map.

Chapter 1. Introduction to Storage Area Network management 15

1.2.4 Outband managementFor outband management, the following sequence occurs, shown in Figure 1-9. Note that all outband communications occur over the IP network.

Figure 1-9 SAN Manager — Outband management path over the IP network

Outband management uses the MIB(s) available for the target switches. The purpose of loading a MIB is to define the MIB objects that the SAN management application will track. These are the items that we want to collect data about, such as number of transmitted or received frames, and error conditions. The objects are defined in the relevant MIBs.

Outband management is used during polling, which is the process of scanning devices to collect the SAN topology. The SNMP Agent solicits the appropriate information from the devices, and returns it to the SAN Manager through the inbuilt SNMP Manager provided in NetView. The switches in this case are configured to send their trap to the SNMP Manager.

SAN management events are also communicated using outband methods. From time to time, events will be triggered from the Agent on the switch to the SAN Manager. The SAN Manager will log these events and respond accordingly. For example, an event could be sent, indicating that a switch port is no longer functioning. The SAN Manager would update its topology map to reflect this.

1.2.5 Inband managementInband management is shown in Figure 1-10.

Inband management works by discovering devices over the Fibre Channel network using Fibre Channel protocols and standards. The data collected is then sent to the Manager over the TCP/IP network, hence the Manager does not have to be connected to the SAN.

SAN Manager

SNMP Manager

Switch

SNMP Agent

SAN Manager Server

Managed Switch

IP NetworkSNMPQuery

SNMPTrap

SNMPTrapforward

Data store in the database

16 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 1-10 SAN Manager — Inband management path

In the case of IBM Tivoli SAN Manager, an Agent is installed on hosts to be managed and is configured to communicate with a Manager system. The polling process for topology discovery sends queries inband through the SAN. Specifically, the HBA API on the managed Agent issues its own query to the FC switch. Topology information is retrieved from the switch, including information about other switches and their attached end-point devices. This is because in a cascaded switch configuration, topology information is shared and replicated among all switches. End-point devices (which do not have an Agent installed), such as storage systems, gateways, and other hosts, respond to RNID and SCSI queries for device and adapter information. Fabric components, such as switches, respond to queries of the Management Server and the Name Server via the HBA API. Switches are not end-point devices.

The Agent returns all collected information to the SAN Manager over the IP network. This information is co-related and consolidated (since other Agents also return possibly duplicate information) and stored on the Manager. It uses this information (combined with information returned by outband Agents, if deployed) to build the topology map and submaps.

1.2.6 Why you might use both inband and outband discoveryBoth of these methods have a valid role in SAN management. Both are being actively developed, and offer different technology benefits.

One practical benefit of using both methods is that, with 2 discovery methods, should one network or the other become unavailable for some reason, the manager can always fall back on the alternate monitoring method.

Multi-protocol management using both inband and outband methods is expected to be the most common implementation of SAN management capabilities. Table 1-1 shows the different capabilities for inband and outband management methods.

Table 1-1 Differences in discovery capability

SAN Manager

Switch Switch

Inband Agent

HBA API

FC Storage

IP Network

Managed Host

FC Storage

Gateway

End points fabric elements

fibre channel connected

Managed host

Scan request

FC QuerySCSIQuery

HBA RNID Query

Returned data

Function Inband (uses fibre network)

Outband(uses IP network)

Device discovery X X

Topology mapping X X

Chapter 1. Introduction to Storage Area Network management 17

One advantage of inband discovery is that inband compliant devices can discover and report errors for adjoining devices. The capability has other associated benefits:

� Agents can use this method to discover and manage the physical and logical connections from the switch to the fibre-attached disk.

� Agents can also use this method to discover and manage fibre-attached hosts through contact with their HBAs.

One advantage of outband discovery is that, in the event that a FC path is down, the management server can still receive errors from the IP path. Another advantage of outband discovery via SNMP is that outband discovery is not affected by zoning. Currently, zoning limits inband requests from management agents to discovering only those end-points within the zone. (The ANSI FC-GS-4 compliance should remove this limitation for inband management.)

1.2.7 Formal standards for outband managementIn the early days of SANs, the FC Management MIB was developed as a de-facto standard by the Fibre Alliance organization to provide basic SAN management capability quickly, and with broad device coverage, using the well-established and easy-to-implement SNMP protocol. This management MIB (current release 4.0) is in the process of being adopted by the IETF as a formal standard. The Fibre Alliance fully supports the efforts of ANSI and other standards bodies to provide formal standards for outband SAN management. The FC Management MIB is exploited by the FC-MI.

The other standard that exists for outband discovery and management is the Fabric Element SNMP MIB, defined by the IETF. Some vendors are also providing their own SNMP MIBs for monitoring different parameters (for example, performance data) in the switch.

The SAN industry benefited greatly from experience gained in both wide-area and local-area networking, and applied that experience in developing FC-GS-3 standard for inband management.

Topology monitoring X X

SAN identification X

Element Manager launch X

Unit level events X

Zone discovery X

End point identification X

LUN identification X

Device status X

Node and link level events X

End point port statistics X X

Logical device-centric and host-centric views

X

Function Inband (uses fibre network)

Outband(uses IP network)

18 IBM Tivoli Storage Area Network Manager: A Practical Introduction

1.2.8 Formal standards for inband managementFormal standards for inband SAN management currently provide more information than that provided by outband management standards. ANSI FC-GS-3 defines a number of inband management services that are useful for SAN discovery. They are shown in Figure 1-11.

Figure 1-11 Inband management services

In conjunction with the Name Server, Management Services allow management applications to determine the configuration of the entire SAN fabric.

Name serverThis provides registry and name services for hosts and devices on the fabric network. This is the basis for soft, or World Wide Name (WWN) zoning. The list of devices is segregated by zone. When a host logs into the SAN, the Name Server tells it which devices it can see and access over the network.

Management agents using only the Name Server are limited to device discovery and queries within the same zone as the management agent.

Fabric configuration serverThis server provides fabric configuration and topology information and registration services for platforms (hosts, storage subsystems, etc.) in the SAN. Platforms in the SAN can register information such as their logical name, platform name, and management address. This allows determination of device type — host, storage subsystem, gateway, or storage access device.

The Fabric Configuration Server enables discovery of the host (and identification as a host) without the need for an agent on the host, or for manually typing the host name next to the WWN in the configuration table.

Management address information allows determination of the device’s outband management interface, IP address, and management protocols (SNMP, HTTP, or CIM).

Fabric Zone ServerThis server defines a mechanism for zoning discovery and control via a standard interface.

Unzoned Name ServerThis provides management applications with name services for device discovery across the entire SAN, uninfluenced by switch zone configuration. A single agent can then discover all devices and end points within the network, irrespective of zoning.

Name Server, and

Management Services, comprised of Fabric Configuration Server, and the Fabric Zone server, and theUnzoned Name Server.

In-band Query Interface

Chapter 1. Introduction to Storage Area Network management 19

Inband Query InterfaceThe final part of the FC-MI definition is an interface to perform in-band queries, discover HBAs, and to retrieve adapter information. This is provided by the SNIA HBA Management API. This API is supported by many HBA vendors.

1.2.9 The future of SAN management standardsIn this section we consider the future of SAN management standards (see Figure 1-12).

Figure 1-12 The future of standards in SAN management

Today, several different standards exist for discovering management information, and for managing devices. Each standard made sense at the time it was adopted. But the industry has learned a lot, and is now attempting to develop a single management model, the Common Information Model (CIM), for managing hosts, storage subsystems, and storage networking devices.

CIM was developed as part of the Web-Based Enterprise Management (WBEM) initiative by the Desktop Management Task Force (DMTF) to simplify management of distributed systems. It uses an object-oriented approach to describe management information, and the description (data model) is platform- and vendor-independent. CIM profiles have already been developed for some devices, such as Fibre Channel switches, and NAS devices. IBM’s intent is to support CIM-based management as and when device manufacturers deliver CIM-based management interfaces.

SNIA regards CIM-based management as the future for multi-protocol SAN management. In 1999, SNIA demonstrated a prototype common Enterprise Storage Resource Manager (ESRM) using WBEM and CIM technology from a number of different vendors (including IBM, Sun, Microsoft, and HDS). This prototype demonstrated management of different storage subsystems (EMC, IBM, StorageTek, Compaq, HDS, and Sun) from a single common management platform.

In 2002, IBM, along with other vendors, presented a new piece of technology code-named Bluefin, to SNIA, which was accepted in August 2002. Bluefin employs CIM and WBEM technology to discover and manage resources in multi-vendor SANs using common interfaces. When implemented in management products, Bluefin will improve the usefulness of SAN and storage management applications and provide for greater management interoperability.

Storage Management Initiative Specification - SMISIn mid-2002 the Storage Networking Industry Association (SNIA) launched the Storage Management Initiative (SMI) to create and develop the universal adoption of a highly functional open interface for the management of storage networks. The SMI was launched as a result of the SNIA’s adoption of the Bluefin SAN management interface specification and the term Bluefin is no longer in use. The SMI’s goal is to deliver open storage network

Storage Management Initiative Specification - SMIS

Enhancements to inband management

Enhancements to outband management

SAN management applications

20 IBM Tivoli Storage Area Network Manager: A Practical Introduction

management interface technology in the form of an SMI Specification (SMIS). The Figure 1-13 below illustrates the SMIS architectural vision.

Figure 1-13 SMIS Architecture

For today’s management applications, to achieve really comprehensive management of SANs and network storage the application, need to communicate with different interfaces of multiple device vendors. Standards compliance varies by individual vendors. In such an environment it is hard to achieve good management with one application, especially with limited development resources. Use of so many different management protocols also slows down the integration of new devices into management scheme as this each new device to be individually tested and ratified for support.

These factors cause users to prefer individual specialized management tools rather than one centralized solution.

The idea behind SMIS is to standardize the management interfaces so that management applications can utilize these and provide cross device management. This means that a newly introduced device can be immediately managed as it will conform to the standards.SMIS is based on Common Information model (CIM) and Web Based Enterprise Management (WBEM) standards. SMIS is providing new features which extend CIM/WBEM technology. In Figure 1-14 you can see how the SMIS system architecture is related to the SNIA storage model.

Architecture of SMI SpecificationArchitecture of SMI Specification

Management Tools

Storage Resource Management

Performance Capacity Planning

Resource Allocation

Container Management

Volume Management Media Management

Other…

Data Management

File System Database Manager

Backup & HSM

Storage Management Interface Specification

Managed Objects

Physical Components

Removable Media Tape Drive

Disk Drive Robot Enclosure

Host Bus Adapter Switch

Logical Components

Volume Clone

Snapshot Media Set

Zone Other…

Users Management FrameworksGraphical User Interface

Chapter 1. Introduction to Storage Area Network management 21

Figure 1-14 SMIS Architecture in relation to SNIA storage model

SMIS extensions to WBEM are:

� A single management transport

Within the WBEM architecture, the CIM-XML over HTTP protocol was selected for this transport in SMIS

� A complete, unified, and rigidly specified object model.

SMIS defines “profiles” and “recipes” within the CIM that enables a management client to reliably utilize a component vendor’s implementation of the standard such as the control of LUNs and Zones in the context of a SAN

� Consistent use of durable names

As a storage network configuration evolves and is reconfigured, key long-lived resources like disk volumes must be uniquely and consistently identified over time

� Rigorously documented client implementation considerations

SMIS provides client developers with vital information for traversing CIM classes within a device/subsystem and between devices/subsystems such that complex storage networking topologies can be successfully mapped and reliably controlled

� An automated discovery system

SMIS compliant products when introduced in a SAN environment will automatically announce their presence and capabilities to other constituents

� Resource Locking

SMIS compliant management applications from multiple vendors can exist in the same SAN and cooperatively share resources via a lock manager

The models and protocols in the SMIS implementation are platform-independent, enabling application development for any platform, and enabling them to run on different platforms. The SNIA will also provide interoperability tests which will help vendors to test their applications and devices if they conform to the standard.

SMIS Architecture in relation to SNIA storage modelSMIS Architecture in relation to SNIA storage model

File/record layer

Database(dbms)

File system(fs)

Storage devices

Block aggregation

Application

Network

Host

Device

Bluefin Management

Services

Storage domain

22 IBM Tivoli Storage Area Network Manager: A Practical Introduction

CIM/WBEM technology uses a powerful human and machine readable language called the managed object format (MOF) to precisely specify object models. Compilers can be developed to read MOF files and automatically generate data type definitions, interface stubs, and GUI constructs to be inserted into management applications.

SMIS object models are extensible, enabling easy addition of new devices and functionality to the model, and allowing vendor-unique extensions for added-value functionality.

Figure 1-15 shows the components of the SMIS/CIM/WBEM model.

Figure 1-15 CIM/WBEM management model

As this standards are still evolving we can not expect that all devices will support the native CIM interface, and because of this the SMIS is introducing CIM agents and CIM object managers. The agents and object managers bridge proprietary device management to device management models and protocols used by SMIS. The agent is used for one device and an object manager for a set of devices. This type of operation is also called proxy model and is shown in Figure 1-16.

CIM/WBEM management modelCIM/WBEM management model

Integration Infrastructure

Management Application

Object Model Mapping – Vendor Unique Features

Device Types

Tape Library Switch Array Many Other

Vendor UniqueFunction

SMISInterface

CIM/WBEMTechnology

MOF MOF MOF MOF

Auto-generation ofApplication and Infrastructure

Constructs

StandardObject Model perDevice

Platform IndependentDistributedAutomated DiscoverySecurityLockingObject Oriented

Chapter 1. Introduction to Storage Area Network management 23

Figure 1-16 CIM Agent & CIM Object Manager

The CIM Agent or Object Manager will translate a proprietary management interface to the CIM interface. An example of CIM Agent is the IBM CIM agent for the IBM TotalStorage® Enterprise Storage Server®.

When widely adopted, SMIS will streamline the way that the entire storage industry deals with management. Management application developers will no longer have to integrate incompatible feature-poor interfaces into their products. Component developers will no longer have to “push” their unique interface functionality to applications developers. Instead, both will be better able to concentrate on developing features and functions that have value to end-users. Ultimately, faced with reduced costs for management, end-users will be able to adopt storage-networking technology faster and build larger, more powerful networks.

For more information on SMIS/CIM/WBEM, see the SNIA Web site:

http://www.snia.org

Enhancements to inband management:The FC-GS-3 standard already registers platforms with the Fabric Configuration Server. With the FC-GS-4 standard being on its way to formal registration by the ANSI T11 committee, registration would provide more information about the platform, be it host or storage subsystem. Here are 2 examples of how this might work:

� Hosts would now have information such as the LUNs assigned to the hosts, and the LUN location in the storage frame.

� The Fabric Device Management Interface (FDMI) in FC-GS-4 would now register end points in the Fabric Configuration Server. This will provide central registration for all device attributes, status, and statistics. Management applications need query only the fabric

Proxy model (CIM Agent/Object Manager) for Proxy model (CIM Agent/Object Manager) for legacy deviceslegacy devices

Client

Device or Subsystem

Agent

Proxy Model

Proprietary

0…n

0…n

Agent

Embedded Model

0…n

Object Manager

Proxy Model

Device

Proprietary0…n

Lock

Manager

0…n

Directory Server

Directory Agent 0…n

SA

SA

Service Agent (SA)

User Agent

SA

1

1 n

Provider

1

CIMxmlCIM operations over http

TCP/IP

SLPTCP/IP

Device or Subsystem

Device or Subsystem

Client

Device or Subsystem

Agent

Proxy Model

Proprietary

0…n

0…n

Agent

Embedded Model

0…n

Object Manager

Proxy Model

DeviceDevice

Proprietary0…n

Lock

Manager

0…n

Directory Server

Directory Agent 0…n

SA

SA

Service Agent (SA)

User Agent

SA

1

1 n

Provider

1

CIMxmlCIM operations over http

TCP/IP

SLPTCP/IP

Device or Subsystem

Device or Subsystem

24 IBM Tivoli Storage Area Network Manager: A Practical Introduction

management services to build a fabric configuration. This reduces the need for management agents on all hosts, and allows for managing end-points.

The role of the host-based agent is still important. Agents are still required to provide logical device-centric and host-centric views of host-to-device connectivity.

Another future that is expected with the FC-GS-4 standard is a common zone control mechanism that allows setting and managing zones across multiple switch vendors. This will improve security and administrator productivity.

The proposed FC-GS-4 standard has a provision for querying end-points, attributes, and statistics via Extended Link Service (ELS) commands. This includes the ability to retrieve performance and error counters. This information can be used to identify ports with high numbers of transmission or receive errors, and to initiate fault identification processes. Access to performance counters allows analysis of traffic pattern, indications of bottlenecks, and capacity planning of SAN networks. Today with IBM Tivoli SAN Manager, this functionality can already be provided using NetView reporting capabilities. See Chapter 6, “NetView Data Collection, reporting, and SmartSets” on page 207 for more information.

Enhancements to out-of-band managementThe roadmap for inband management of fabric-attached devices via ANSI T11 standards is relatively well-charted. Today, no formally accepted standard exists for managing and controlling storage subsystems. The SNIA, along with many storage vendors, are promoting the use of CIM and WBEM technology to discover and manage storage subsystems. At present, this management would occur via outband management paths.

Using these standards-based approaches will be directly translatable, and often directly re-usable, on other storage networks such as iSCSI, Infiniband, and other devices such as NAS servers.

1.2.10 Summary Here we summarize the main considerations in SAN management (see Figure 1-17).

Figure 1-17 SAN management summary

Business Transactions are growing

More companies are implementing SANs.

SANs are getting bigger.

Traditional manual methods of managing storage no longer work.

New tools are needed to manage storage

New tools have to be based on standards.

Standards are continually evolving.

The new tools will reduce costs of:

discovering and presenting topology

continuous real-time monitoring and fault identification

The new tools will help

reduce costs of managing storage

keep storage available "all the time" for revenue-generating activities

Chapter 1. Introduction to Storage Area Network management 25

In the next chapter we introduce Tivoli’s SAN management application, IBM Tivoli SAN Manager. This chapter presents an overview of its architecture, components, and usage.

In working on this redbook, the team built a lab environment to test certain configurations. We will present this architecture, identify the configurations and functions we tested, and summarize our findings.

Subsequent chapters will go into detailed explanations about deployment considerations, availability issues, installation and setup and operations, and so on.

26 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager

In this chapter we introduce and position IBM Tivoli Storage Area Network Manager (IBM Tivoli SAN Manager) — including existing and new Version 1.2 functionality, architecture, and components. Tivoli SAN Manager complies with industry standards for SAN storage and management.

And it does all this — Tivoli SAN Manager:

� Manages fabric devices (switches) through outband management.

� Discovers many details about a monitored server and its local storage through a IBM Tivoli SAN Manager Agent loaded onto a SAN-attached host (Managed Host).

� Monitors the network and collects events and traps

� Launches vendor-provided specific SAN element management applications from the IBM Tivoli SAN Manager Console.

� Discovers and manages iSCSI devices.

� Provides a fault isolation engine for SAN problem determination (ED/FI - SAN Error Predictor).

� No longer utilizes IBM MQSeries®

� Supports running the Manager on AIX.

� Now runs on WebSphere® Express (smaller footprint and less resources).

� Provides a quick launch feature into IBM Tivoli Storage Resource Manager.

� Is available as a free Bonus Pack for limited fibre channel port management (up to 64 ports).

� Provides integration into IBM Tivoli Enterprise Data Warehouse.

2

© Copyright IBM Corp. 2002, 2003. All rights reserved. 27

2.1 Highlights: What’s new in Version 1.2In this section we summarize new functions, supported platforms, and features of IBM Tivoli SAN Manager Version 1.2. For an introduction to the overall product, see 2.2, “IBM Tivoli SAN Manager overview” on page 29.

Figure 2-1 IBM Tivoli SAN Manager V1.2 — New functions and features

2.1.1 Discovery of iSCSIIBM Tivoli SAN Manager now supports the discovery and management of internet SCSI (iSCSI) devices. The iSCSI discovery is performed independently from the discovery done by IBM Tivoli SAN Manager.

2.1.2 Event Detection and Fault Isolation (ED/FI - SAN Error Predictor)Error Detection/Fault Isolation (ED/FI - SAN Error Predictor) is a new feature that performs problem determination on Fibre Channel optical links. ED/FI performs predictive failure analysis and fault isolation that allows users to identify and take appropriate action for components that may be failing.

2.1.3 IBM Tivoli Enterprise Data Warehouse (TEDW)IBM Tivoli SAN Manager Version 1.2 support for IBM Tivoli Enterprise Data Warehouse (TEDW) Version 1.1 will provide a central repository of historical data for use by Tivoli Service Level Advisor. Tivoli SAN Manager will use the Extract, Transform Load language (ETL1) to pull data from the IBM Tivoli SAN Manager database and write it to the TEDW. In its first release, the TEDW support will extract switch and port status information only. For more information on TEDW, see Chapter 14, “Integration with Tivoli Enterprise Data Warehouse” on page 387.

2.1.4 IBM Tivoli SAN Manager on AIXIBM Tivoli SAN Manager now supports running the Manager component on AIX 5.1. This support does not include Tivoli NetView support on UNIX, therefore the NetView console must still be run on Windows 2000 or Windows XP.

2.1.5 Embedded WebSphereIBM Tivoli SAN Manager now includes WebSphere Express embedded. IBM Tivoli SAN Manager no longer requires a separate WebSphere installation.

New Functions and Features for Version 1.2Discovery of iSCSI

Error Detection and Fault Isolation (EDFI)

Removal of IBM MQSeries

SAN Manager available for AIX

New AIX and Linux managed hosts

Running embedded WebSphere Express

Quick Launch for IBM Tivoli Storage Resource Manager

Integration into IBM Tivoli Enterprise Data Warehouse

28 IBM Tivoli Storage Area Network Manager: A Practical Introduction

2.1.6 Operating system support� Managed host on AIX 5.2 � Managed host on Linux Red Hat Advanced Server version 2.1� Managed host on SuSE Linux Enterprise Server 7.0

2.1.7 Other changes� Dynamic IP addresses (DHCP) instead of static IP addresses are now supported for

managed hosts and remote consoles.� Provides additional event classes for IBM Tivoli Enterprise Console®.� Discovery of Cisco MDS 9000 Series switch.� Removal of IBM MQSeries.� IBM Tivoli NetView has been upgraded to v7.1.3� JRE has been updated to JRE 1.3.1� Silent install option is now available.

2.2 IBM Tivoli SAN Manager overviewIn this section we present the product components, supported platforms, and a high level view of the major functions.

2.2.1 Business purpose of IBM Tivoli SAN ManagerThe primary business purpose of IBM Tivoli SAN Manager is to help the storage administrator display and monitor their storage network resources — to increase data availability for applications so the company can either be more efficient, or maximize the opportunity to produce revenue.

IBM Tivoli SAN Manager helps the storage administrator:

� Prevent faults in the SAN infrastructure through reporting and proactive maintenance.� Identify and resolve problems in the storage infrastructure quickly, when a problem occurs.� Provide fault isolation of SAN links.

In the next several sections of this chapter we identify the components of IBM Tivoli SAN Manager, and discuss some of their uses. We discuss prevention of problems through predictive reporting and proactive maintenance, and show how to identify a fault quickly.

2.2.2 Components of IBM Tivoli SAN ManagerThese are the major components of IBM Tivoli SAN Manager:

� A Manager or Server, running on a (preferably dedicated) SAN management system

� Agents, running on one or more Managed Hosts

� Management Console

– runs by default on a Windows Manager– additional Remote Consoles are also available for Windows (hence a Windows system

is required for NetView display with an AIX Manager

� Outband Agents — consisting of vendor-supplied MIBs for SNMP

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 29

There are two additional components (which are provided by the customer):

– IBM Tivoli Enterprise Console (TEC) which is used to receive Tivoli SAN Manager generated events. Once forwarded to TEC, These can then be consolidated with events from other applications and acted on according to enterprise policy.

– IBM Tivoli Enterprise Data Warehouse (TEDW) is used to collect and analyze data gathered by the IBM Tivoli SAN Manager.

These components are shown in Figure 2-2.

Figure 2-2 IBM Tivoli SAN Manager operating environment

The Tivoli SAN Manager Web site, which includes the most up-to-date list of supported manager and agent operating systems, fabric components and HBAs (Host Bus Adapters) is at

http://www-3.ibm.com/software/tivoli/products/storage-san-mgr/

IBM Tivoli SAN Manager ServerThe manager system can be a Windows 2000 or AIX V5.1 system, with the following components:

� IBM Tivoli SAN Manager code: Controls the SAN management function

� DB2®: Used as a repository for topology and event records

� IBM Tivoli NetView: Presents the topology and event information graphically

� Java™ Virtual Machine: Use of JVM supports portability and completeness

� SNMP Manager: communicates with SNMP Agents on outband-monitored devices

Note: WebSphere Express manages the servlets used by IBM Tivoli SAN Manager for various functions. Its embedded and is not a standalone application.

Tivoli SAN Manager ComponentsTivoli SAN Manager Components

Tivoli SAN Manager

Tivoli SAN Manageragent

Tivoli SAN ManagerRemote Console

NetView

TC

P/IP

Tivoli Data Warehouse

FabricA

FabricB

Storage

Systems

Systems

SP

SAN Data Gateway

Tape

30 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Remote ConsoleOne or more Remote Consoles can be installed to provide a GUI for Tivoli SAN Manager. The Server system automatically includes a console display. Remote Consoles must be Windows 2000 or Windows XP systems with the following components:

� NetView — presents the information graphically

� Remote Console code: allows an administrator to monitor IBM Tivoli SAN Manager from a remote location or locations

Agents or Managed HostsAgents provide inband management capability and are currently available on the following platforms:

� Microsoft Windows NT® and 2000� IBM AIX v5.1, v5.2� Sun Solaris v2.6 or 2.8� Linux SuSE Enterprise Server 7.0� Linux Red Hat Advanced. Server 2.1

Agents consist of the following components:

� The Agent itself: Collects information from various sources and forwards it to the Manager� Java virtual Machine: Use of a JVM supports portability and completeness

SNMP Agent for managed switchesSAN switches can use SNMP to act as outband Agents. Tivoli SAN Manager can use SNMP Management Information Base (MIB) queries to discover information about these switches.

2.2.3 Supported devices for Tivoli SAN ManagerThe list of supported devices, including HBAs, disk systems, tape systems, SAN switches, and gateways is provided at:

http://www-3.ibm.com/software/sysmgmt/products/support/IBM_TSANM_Device_Compatibility.html

Always check here first during planning to see if there are any special considerations for your environment.

2.3 Major functions of IBM Tivoli SAN ManagerIBM Tivoli SAN Manager performs the functions shown in Figure 2-3. These functions are explored in the rest of this chapter.

Figure 2-3 IBM Tivoli SAN Manager functions

Discover SAN components and devices

Display a topology map of the SAN in physical and logical views

Performs error detection and fault isolation

Provide real-time and historical reports (through NetView)

Error detection and fault isolation (ED/FI - SAN Error Predictor)

Discovery of iSCSI devices

Launch vendor-provided applications to manage components

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 31

These functions are distributed across the Manager and the Agent as shown in Figure 2-4.

Figure 2-4 Functions of IBM Tivoli SAN Manager and Agents

2.3.1 Discover SAN components and devicesIBM Tivoli SAN Manager uses two methods to discover information about the SAN — outband discovery, and inband discovery. These discovery paths are shown in Figure 2-5.

In outband discovery, all communication occurs over the IP network:

� IBM Tivoli SAN Manager requests information over the IP network from a switch using SNMP queries on the device.

� The device returns the information to IBM Tivoli SAN Manager, also over IP

In inband discovery, both the IP and Fibre Channel networks are used:

� IBM Tivoli SAN Manager requests information (via IP) from an IBM Tivoli SAN Manager Agent installed on a Managed Host.

� That Agent requests information over the Fibre Channel network from fabric elements and end points in the Fibre Channel network.

� The Agent returns the information to IBM Tivoli SAN Manager over IP.

The Manager collects, co-relates and displays information from all devices in the storage network, using both IP and Fibre Channel. If the Fibre Channel network is unavailable for any reason, monitoring can still continue over the IP network.

Tasks - Tivoli SAN Manager Server and AgentTasks - Tivoli SAN Manager Server and Agent

Tivoli SAN Manager ServerPerforms initial discovery of environment

Gathers and correlates data from agents on managed hostsGathers data from SNMP (outband) agentsGraphically displays SAN topology and attributes

Provides customized monitoring and reporting through NetView

Reacts to operational events by changing its display

(Optionally) forwards events to Tivoli Enterprise Console or SNMP managers

Tivoli SAN Manager AgentGathers information about

SANs by querying switches and devices for attribute and topology information host-level storage, such as filesystems and LUNsevent and other information detected by HBAs

Forwards topology & event information to the Manager

32 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 2-5 IBM Tivoli SAN Manager — inband and outband discovery paths

Following are definitions of some important terms:

Outband discovery is the process of discovering SAN information, including topology and device data, without using the Fibre Channel data paths. Outband discovery uses SNMP queries, invoked over IP network. Outband management and discovery is normally used to manage devices such as switches and hubs which support SNMP.

Inband discovery is the process of discovering information about the SAN, including topology and attribute data, through the Fibre Channel data paths. Inband discovery uses the following general process:

� The Agent sends commands through its Host Bus Adapters (HBA) and the Fibre Channel network to gather information about the switches

� The switch returns the information through the Fibre Channel network & the HBA to the Agent

� The Agent queries the endpoint devices using RNID and SCSI protocols

� The Agent returns the information to the Manager over the IP network

� The Manager then responds to the new information by updating the database and redrawing the topology map if necessary.

iSCSI Discovery Internet SCSI is an Internet Protocol (IP)-based storage networking standard for linking data storage. It was developed by the Internet Engineering Task Force (IETF). iSCSI can be used to transmit data over LANs and WANs.

SAN Manager - Discovery PathsSAN Manager - Discovery Paths

TivoliSAN

Manager

SAN Manager

Agent

HBA

Un-Identified

Device(no Agent)

Switch

Disk

Switch

TCP/IPNetwork

FibreChannel

SAN

Outband(SNMP Query/Trap)

Inband(RNID, SCSI queries)

topology &event data

SAN Manager

Agent

HBA

Fibre ChannelConnections

Query request/Returned dataiSCSI(no

Agent)nvsniffer discovery of

iSCSI devices

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 33

2.3.2 Deciding how many Agents will be neededThe storage network may have dozens of switches, 10-20 storage frames, half a dozen SANs, and hundreds of servers.

How many Agents should the administrator load? The answer to this question depends on what you want to accomplish.

Four different levels of monitoring are possible, as summarized in Figure 2-6. They are discussed in detail in 3.8, “Deployment scenarios” on page 76. We are using the terms inband and outband monitoring as defined in 2.3.1, “Discover SAN components and devices” on page 32.

Figure 2-6 Levels of monitoring

Outband monitoring onlyNo IBM Tivoli SAN Manager Agents are installed on hosts in this scenario. You are managing the switches in your SAN, that is, monitoring the fabric.

IBM Tivoli SAN Manager displays the WWN of an unmanaged host on the topology map, but the device type is unknown.

If anything goes wrong with a switch, a link, or one of the unidentified objects, then the event triggers redrawing the topology map, with the broken component identified in red on the map. No information on storage, LUNs or filesystems is available (no logical views).

Optionally, you can enhance the SAN display by manually identifying SAN elements via NetView.

SAN Network Software Model

Well Placed AgentsInband only

Agents EverywhereInband + Outband

Basic fabric managementOutband only

Manual Indentity of EndpointsOutband only

Levels of SAN ManagementLevels of SAN Management

34 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Inband monitoringIn this scenario, at least some hosts have IBM Tivoli SAN Manager Agents installed. How many you load depends on platform support, functionality required, as well as performance implications. More information about this is given in 5.7.9, “Well placed agent strategy” on page 202. You should load at least one Host per zone (or two hosts for redundancy) for the complete topology display. Use this approach (the well-placed Agent) if you want to manage your switches, and to know the name and identify of your RNID-capable hosts. You will display storage-related information (including logical views) only for the hosts with Agents installed.

If you need the logical or storage-centric views for all eligible hosts (with platform support), then Agents should be installed on all of these. Use this approach where platform support for Agents is provided AND you want to discover and display storage-related information for as many hosts as possible.

Both inband and outband monitoring When you use a combination of inband and outband Agents, you monitor all devices in the fabric across all zones. You also get storage-centric views for hosts with Agents.

This approach therefore provides the highest level of information and monitoring for the SAN. Another benefit of this approach is that if, for some reason, the Fibre Channel network becomes unavailable, you still can monitor using the IP path.

These issues are examined in more detail in 3.8, “Deployment scenarios” on page 76 as well as 5.7, “Practical cases” on page 182.

2.3.3 How is SAN topology information displayed?IBM Tivoli SAN Manager uses IBM Tivoli NetView to display topology information and views, and for monitoring devices. Tivoli NetView discovers, displays, and manages traditional TCP/IP networks.

IBM Tivoli SAN Manager extends this function to the Storage Area Network by providing a new SAN pull-down menu item, as well as a SAN icon on the NetView top-level root map. These are shown in Figure 2-7.

Tivoli NetView, as customized with IBM Tivoli SAN Manager, provides a single integrated platform to manage both traditional IP networks and SANs.

Figure 2-7 Tivoli SAN Manager — Root menu

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 35

Ways to display topologyIBM Tivoli SAN Manager presents topology displays in two different ways — the icon display and the explorer display.

Figure 2-7 is an example of an icon display. The explorer display (named because it is similar to the Windows Explorer file manager), looks like Figure 2-8.

Figure 2-8 Tivoli SAN Manager — explorer display

2.3.4 How is iSCSI topology information displayediIBM Tivoli SAN Manager displays iSCSI devices within the NetView SmartSet. Once IP discovery and the appropriate iSCSI Operation is selected. the iSCSI devices are discovered and a SmartSet is created. An example of an iSCSI SmartSet is displayed in Example 2-9

Figure 2-9 iSCSI SmartSet

2.4 SAN management functionsIBM Tivoli SAN Manager has three primary areas as described in 2.2.1, “Business purpose of IBM Tivoli SAN Manager” on page 29.

36 IBM Tivoli Storage Area Network Manager: A Practical Introduction

� Prevent faults in the SAN infrastructure through reporting and proactive maintenance.� Identify and resolve problems in the storage infrastructure quickly, when a problem occurs.� Provide fault isolation of SAN links.

IBM Tivoli SAN Manager achieves these purposes by providing the following functions as outlined in Figure 2-3 on page 31, and on Figure 2-4 on page 32.

� Discover SAN components and devices.

� Display a topology map of the various fabrics and SANs, giving both physical and logical views.

� Highlight faults.

� Provide report and monitoring capability for SNMP-capable devices.

� Launch vendor-provided applications to manage individual components.

� Displays ED/FI adornments on the topology map for fault isolation and problem resolution.

� Provides reporting into Tivoli Enterprise Data Warehouse

We will give a brief overview of these IBM Tivoli SAN Manager functions, to illustrate how these functions achieve the business purpose of the tool. Chapter 5, “Topology management” on page 149, gives a more detailed exploration of the product capabilities.

2.4.1 Discover and display SAN components and devicesIn its recommended installation, Tivoli SAN Manager uses both inband and outband methods to discover and map the SAN topology. You can go from high-level views down to more specific views, focusing on different parts of the SAN. When you click the Storage Area Network icon shown in Figure 2-7 on page 35, you will see the following submenu (Figure 2-10).

Figure 2-10 Tivoli SAN Manager — SAN submap

The SAN icon on the right (highlighted) takes you down the physical topology displays, while the other two icons (Device Centric View and Host Centric View) provide access to the logical topology displays.

Physical topology displayA typical SAN physical topology display is shown in Figure 2-11.

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 37

Figure 2-11 NetView physical topology display

We reached this display by drilling down from the map shown in Figure 2-10. In this case, one SAN switch is shown with the hosts and devices connected to it. All icons are colored green, indicating they are active and available. Similarly, the connections are black. NetView uses different colors for devices and connections to indicate their status, as explained in 5.1.8, “Object status” on page 155.

38 IBM Tivoli Storage Area Network Manager: A Practical Introduction

If something happens on the SAN (for example, a port on the switch fails), then the topology will be automatically updated to reflect that event, as shown in Figure 2-12. In this case an event is triggered that the port has failed, however, the Server still communicates with the host Agent attached to that port. Therefore the connection line between the switch and host turns red, while the host system remains green.

Figure 2-12 Map showing host connection lost

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 39

Zone viewTivoli SAN Manager can also display switch zones, where supported by the switch API. Figure 2-13 shows two zones configured, FASTT and TSM.

Figure 2-13 Zone view submap

40 IBM Tivoli Storage Area Network Manager: A Practical Introduction

If you click an individual zone, the members of that zone will be displayed. This is shown in Figure 2-14. More information on the Zone View for Tivoli SAN Manager is given in “Zone view” on page 165.

Figure 2-14 Zone members

Logical topology displays

The logical displays provided by Tivoli SAN Manager are the Device Centric View and the Host Centric View. Logical views, unlike the previously shown physical views, do not display the connection information between hosts and SAN fabric devices.

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 41

Device Centric ViewThe Device Centric View displays all the storage devices connected in the SAN, with their relationship to the hosts. The initial Device Centric View map is shown in Figure 2-15. It shows two disk systems, each with their serial numbers. The specific icons displayed depend on how your disk systems are supported by Tivoli SAN Manager.

Figure 2-15 Device Centric View

You can drill down to individual devices, using the icon display, or display all the information in the explorer view. This is usually a more convenient way to display this information as it is more complete. If you select the Explorer icon, you will see the map shown in Figure 2-16.

You can see that the LUNs for both storage systems displayed on the left hand panel. For each LUN, you can drill down to find out which host and Operating System has assigned that LUN. In this example, disk system IT14859668 has five LUNs, and each LUN is associated with one or two named hosts. For example, the first LUN is associated with the hosts SENEGAL and DIOMEDE, running Windows 2000. You can drill down one step further from the Operating System to display the filesystem installed on the LUN. There is one LUN discovered in the other disk system, which is used for the filesystem /mssfs on the AIX system CRETE.

42 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 2-16 Device Centric View — explorer

Host Centric ViewThe Host Centric View displays all the Managed Hosts, and their associated local and SAN-attached storage devices. The explorer Host Centric view is shown in Figure 2-17. You can see that each filesystem associated with each Managed Host or Agent is displayed on the right hand side. The left hand pane shows all the Managed Hosts.

Figure 2-17 Host Centric View

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 43

You can drill down on the Host filesystem entries to show also the logical volume (and LUN if fibre-attached) associated with the filesystem, shown in Figure 2-18.

Figure 2-18 Host Centric View — logical volumes and LUN

Summary display

You can also see a summary or navigation display which holds a history of all the maps which you have navigated in IBM Tivoli SAN Manager. In Figure 2-19, we have opened up all 3 views of IBM Tivoli SAN Manager, and therefore can see a very comprehensive display. This is because we have drilled down a Device Centric View, drilled down a Host Centric View, and finally navigated the physical topology, and then opened the Navigation Tree.

44 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 2-19 Navigation tree for Tivoli SAN Manager

The Figure 2-19 shows:

� (1) SAN View (third row, left, see #1)– Topology View– Zone View

� (2) Device Centric View (third row, middle, see #2)� (3) Host Centric View (third row, right, see #3)

Object PropertiesIf you click any device to select it (from any map), then right-click and select Object Properties from the pop-up menu, this will bring up the specific properties of the object. In Figure 2-20, we selected a switch, and displayed the Properties window, which has seven different tabs. The events tab is shown, listing events which have been received for this switch.

2.4.2 Log eventsTivoli SAN Manager collects events received from devices. Figure 2-20 shows an example of events logged by one of the switches.

1 2 3

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 45

Figure 2-20 Switch events

2.4.3 Highlight faultsEvents about SAN components are communicated to IBM Tivoli SAN Manager by Agents. IBM Tivoli SAN Manager logs the events in a log that looks like Figure 2-20 above. IBM Tivoli SAN Manager then evaluates the event, and decides if the event is (or is not) a fault.

If the event is a fault, IBM Tivoli SAN Manager indicates the change in status by changing the color of the object in the topology map. In 5.7, “Practical cases” on page 182, we show more examples of triggering topology changes. Here is just one example, where we simulate the loss of the switch by powering it off. Other common faults include a Fibre Channel cable breaking, a host crash, and an unavailable storage frame.

Figure 2-21 shows the topology display once it is refreshed. The healthy devices are in green, and the unhealthy devices are in red. We have also circled the devices that turned red for clarity.

� Device #5 — the switch — is obvious. The power went out, so the switch no longer responds.

� All the links (connections) from the switch to the devices also went red.

� The Devices 1,2,3 & 4 went red. These devices have no Agent on them, are known to IBM Tivoli SAN Manager only through the switch nameserver, and are unavailable now that the switch is down. IBM Tivoli SAN Manager’s map displays this accurately.

� The hosts with Agents on them (CRETE, TUNGSTEN, SENEGAL AND DIOMEDE) remain green as they still communicate with the Server via TCP/IP. Only their connection link to the switch turns red.

46 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 2-21 Map Showing Effects of Switch Losing Power

When the switch is fixed, as it powers up, it will send an event back to IBM Tivoli SAN Manager, who will re-query the switch (running both the topology scanner and the attribute scanner). The topology will be refreshed to reflect the switch being back online.

2.4.4 Provide various reportsThe primary business purpose for IBM Tivoli SAN Manager is to keep the storage infrastructure running to support revenue-generating actives. We have already seen how the topology display will automatically update to reflect devices becoming available so that network administrator can quickly respond.

Another way to improve availability is to use monitoring and reports to anticipate devices that are beginning to fail.

Not all failures can be predicted — however, many devices may fail gradually over time, so reporting a history of problems can help anticipate this. For example, if you see a lot of transmission errors occurring over a period of time, you might anticipate a component failure, and schedule maintenance testing or preemptive replacement to minimize impact on generating revenue or other critical applications.

Reporting is provided by NetView and includes historical and real-time reporting, on an individual device, or on a defined group of devices. Reporting capabilities are discussed in detail in Chapter 6, “NetView Data Collection, reporting, and SmartSets” on page 207.

1 2

3

4

5

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 47

With NetView you have a very flexible capability to build your own reports according to your specific needs. The reports we are interested in for IBM Tivoli SAN Manager are reports against the objects in the MIB provided by the switch vendor. In our lab, we used an IBM 2109 16-port switch, so we used the Brocade MIB for the Brocade Silkworm 2800.

The data elements in the MIB can report on status (device working, not working) and performance (x frames were transmitted over this switch port in Y seconds).

Historical reportingWith NetView you can display historical reports based on data collected. Figure 2-22 shows a report of data collected over 8 ports in a two minute interval. You can set up the data collection to look for thresholds on various MIB values, and send a trap when defined values are reached.

Figure 2-22 Graph of # Frames Transmitted over 8 ports in a 2 minute interval

Combining the MIB objects with the canned and customized reporting from NetView provides the storage administrator with the tools needed to help keep the SAN running all the time.

Real-time reportingNetView can also track MIB values in real-time. Figure 2-23 shows real-time monitoring of traffic on switch ports. The graph shows the number of frames transmitted from a specific port on a particular switch over a specified time interval. You can set the polling interval to show how often the graph will update.

48 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 2-23 Number of Frames Transmitted Over Time

You can also create graphs from multiple devices using NetView SmartSets.

2.4.5 Launch vendor management applicationsTivoli SAN Manager provides a launch platform for many individual vendor management applications. In some cases these are automatically discovered, and in other cases they can be manually configured into NetView. These applications might be for a switch, hub, gateway or storage frame. Figure 2-24 shows an example of launching the automatically discovered switch management application.

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 49

Figure 2-24 Vendor application launch

IBM Tivoli SAN Manager provides 3 methods for locating such applications:

� Native support:

For some devices, IBM Tivoli SAN Manager will automatically discover and launch the device-related tool. SAN Manager has an internal set of rules (in XML format) by which it identifies the devices whose tool it can launch.

� Web interface support:

Some devices are not discovered automatically, but have a Web interface. IBM Tivoli SAN Manager can be configured with the URL, so that it can subsequently launch Web interface.

� Non-Web interface support:

Other applications have no Web interface. IBM Tivoli SAN Manager offers you the ability to configure the toolbar menu to launch any locally-installed application from the IBM Tivoli SAN Manager console. Note, these applications must be locally installed on the Tivoli SAN Manager Server.

These options are presented in 5.5, “Application launch” on page 174.

2.4.6 Displays ED/FI eventsIBM Tivoli SAN Manager Version 1.2 uses ED/FI to predict errors on the optical links that are used to connect SAN components. Coverage includes HBA-switch, switch-switch and switch to storage connections). The SAN topology is updated to reflect the suspected components.

50 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 2-25 shows an example of an ED/FI “adornment” on the switch ELM17A110. More information on ED/FI is given in Chapter 9, “ED/FI - SAN Error Predictor” on page 267.

Figure 2-25 Adornment shown on fibre channel switch

2.4.7 Tivoli Enterprise Data Warehouse (TEDW)The Tivoli Data Enterprise Warehouse collects, organizes, and makes data available for the purpose of analysis in order to give management the ability to access and analyze information about its business. IBM Tivoli SAN Manager will provide ETL1 (Extract Translate and Load) code that allows TEDW to pull data from the IBM Tivoli SAN Manager database. In its first release, the TEDW support will extract switch and port status information.

Refer to Chapter 14, “Integration with Tivoli Enterprise Data Warehouse” on page 387 for more information

2.5 SummaryIn this chapter, we introduced IBM Tivoli SAN Manager, whose primary business purpose is to keep the storage infrastructure running to assist revenue-generating activities.

IBM Tivoli SAN Manager discovers the SAN infrastructure, and monitors the status of all the discovered components. Furthermore, it also discovers iSCSI devices and provides the functionality to detect and report on SAN interconnect failures using ED/FI. Through Tivoli NetView, the administrator can provide reports on faults on components (either individually or in groups, or “SmartSets”, of components).

Chapter 2. Introduction to IBM Tivoli Storage Area Network Manager 51

52 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Part 2 Design considerations

In Part 2 we discuss the deployment architectures (including Server, Agents, Remote Console, and inband/outband discovery) for IBM Tivoli SAN Manager.

Part 2

© Copyright IBM Corp. 2002, 2003. All rights reserved. 53

54 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 3. Deployment architecture

In this chapter we provide an overview of Fibre Channel standards, Fibre Channel topologies, IBM Tivoli Storage Area Network Manager (IBM Tivoli SAN Manager), including a component description, as well as Managed Host placement. We cover these topics:

� Fibre Channel standards

� Hardware

� SAN topologies

– Point-to-point – Arbitrated loop– Switched

� Management

– Inband– Outband

� Component description and placement

� Deployment considerations

– Manager– Agents– Deployment scenarios

� High availability

3

© Copyright IBM Corp. 2002, 2003. All rights reserved. 55

3.1 OverviewIn this chapter, we start out by describing the standards and interoperability on which IBM Tivoli SAN Manager is built (Figure 3-1).

Figure 3-1 Deployment overview

The challenges of managing heterogeneous SANs are discussed and how IBM Tivoli SAN Manager manages heterogeneous SANs. We also discuss the different Fibre Channel topologies and SAN fabric components followed by deployment scenarios. We also discuss SAN management as it relates to IBM Tivoli SAN Manager and some scanner details.

3.2 Fibre Channel standardsStandards are desirable in any IT arena, as they provide a means to ensure interoperability and coexistence between equipment manufactured by different vendors. This benefits the customers by increasing their choices.

3.2.1 InteroperabilityInteroperability means the ways in which the various SAN components interact with each other. Many vendors and other organizations have their own labs to perform interoperability testing to ensure adherence to standards. Before going ahead with any purchase decision for a SAN design, it is recommended that you check with the vendor of your SAN components about any testing and certification they have in place. This should be an important input to the decision making process.

Where there are multiple vendors involved this becomes very important — for example, if a storage vendor certifies a particular level of HBA firmware, while a server vendor certifies and supports another level. You need to resolve any incompatibilities to avoid ending up with an unsupported configuration.

Fibre Channel discussion topicsStandards

Fibre Channel hardwareHBAs, cables, GBICs

SAN Topologies

ManagementInband

Outband

IBM Tivoli SAN Manager Components

Deployment ConsiderationsManager and Agent

Deployment scenarios

56 IBM Tivoli Storage Area Network Manager: A Practical Introduction

3.2.2 Standards The SAN component vendors, especially switch makers, are trying to comply to the standards which will allow them to operate together in the SAN environment. The current standard which gives the opportunity to have different components in the same fabric is the FC-SW2 standard from the Technical Committee T11. See this Web site for details:

http://www.t11.org

This standard defines FSPF (Fabric Shortest Path First), Zoning exchange, and ISL (Inter-Switch Link) communication. Not all vendors may support the entire standard. Future standards (for example, FC-SW3, currently under development) will also bring with them functions which will allow the management information to be exchanged from component to component, thus giving the option to manage different vendors’ components with tools from one vendor.

IBM Tivoli SAN Manager employs iSCSI management. The iSCSI protocol is a proposed industry-standard that allows SCSI block I/O protocols to be sent over TCP/IP protocol. See this web site for additional details:

http://www.ietf.org

We have already mentioned Chapter 1, “Introduction to Storage Area Network management” on page 3 that SAN vendors are trying to establish support for the standards which will give them the opportunity to work together in the same SAN fabric. But this is just one view of heterogeneous support. The other view is from the platforms which will participate in the SAN as the users of the resources.

So, when deploying Tivoli SAN Manager it is important that you check that the SAN components you are using are certified and tested with it. This also means that you need to verify which levels of operating systems, firmware, drivers, vendors models are supported by Tivoli SAN Manager. We discuss this later in 3.7, “Deployment considerations” on page 70.

3.3 Hardware overviewIn this section, we introduce various items that can make up a SAN (Figure 3-2). Identifying these components is key to a successful deployment and proper functionality of the Tivoli SAN Manager installation. This includes physical building blocks and protocols.

Figure 3-2 Hardware overview

We will start off by covering items of hardware that are typically found in a SAN. The purpose of a SAN is to interconnect hosts/servers and storage. This interconnection is made possible by the components (and their subcomponents) that make up the SAN itself.

SAN ComponentsHBA

GBICs

Cables

Connectors

Chapter 3. Deployment architecture 57

3.3.1 Host Bus AdapterThe device that acts as the interface between the fabric of a SAN and either a host or a storage device is a Host Bus Adapter (HBA). In the case of storage devices, they are often just referred to as Host Adapters.

The HBA connects to the bus of the host or storage system. It has some means of connecting to the cable or fiber leading to the SAN. Some devices offer more than one Fibre Channel connection. At the time of writing, single and dual ported offerings were available. The function of the HBA is to convert the parallel electrical signals from the bus into a serial signal to pass to the SAN. Some of the more popular vendors of HBA’s include QLogic, Emulex and JNI. Many server or storage vendors also re-sell these adapters under their own brand (OEM). Figure 3-3 shows some typical HBAs.

Figure 3-3 Typical HBAs

3.3.2 CablingThere are a number of different types of cable that can be used when designing a SAN. The type of cable and route it will take all need consideration. The following section details various types of cable and issues related to the cable route.

DistanceThe Fibre Channel cabling environment has many similarities to telecommunications or typical LAN/WAN environments. Both allow extended distances through the use of extenders or technologies such as DWDM (Dense Wavelength Division Multiplexing). Like the LAN/WAN environment, Fibre Channel offers increased flexibility and adaptability in the placement of the electronic network components, which is a significant improvement over previous data center storage solutions, such as SCSI.

Shortwave or longwaveEvery data communications fiber falls into one of two categories:

� Single-mode� Multi-mode

In most cases, it is impossible to visually distinguish between single-mode and multi-mode fiber (unless the manufacturer follows the color coding schemes specified by the Fibre

Typical HBAsTypical HBAs

58 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Channel physical layer working subcommittee — orange for multi-mode and yellow for single-mode), since there may not be a difference in outward appearance, only in core size. Both fiber types act as a transmission medium for light, but they operate in different ways, have different characteristics, and serve different applications.

Single-mode (SM) fiber allows for only one pathway, or mode, of light to travel within the fiber. The core size is typically 8.3 µm. Single-mode fibers are used in applications where low signal loss and high data rates are required, such as on long spans (longwave) between two system or network devices, where repeater/amplifier spacing needs to be maximized.

Multi-mode (MM) fiber allows more than one mode of light. Common MM core sizes are 50 µm and 62.5 µm. Multi-mode fiber is better suited for shorter distance applications. Where costly electronics are heavily concentrated, the primary cost of the system does not lie with the cable. In such a case, MM fiber is more economical because it can be used with inexpensive connectors and laser devices, thereby reducing the total system cost. This makes multi-mode fiber the ideal choice for short distance (shortwave) under 500m from transmitter to receiver (or the reverse).

50/125 micrometers or 62.5/125 micrometers Optical fiber for telecommunications consists of three components:

� Core� Cladding� Coating

Figure 3-4 describes the characteristics of fiber optic cables.

Figure 3-4 Structure of a fiber optic cable

CoreThe core is the central region of an optical fiber through which light is transmitted. In general, the telecommunications industry uses sizes from 8.3 micrometers (µm) to 62.5 micrometers. The standard telecommunications core sizes in use today are 8.3 µm (single-mode), 50 µm (multi-mode), and 62.5 µm (multi-mode).

CladdingThe diameter of the cladding surrounding each of these cores is 125 µm. Core sizes of 85 µm and 100 µm have been used in early applications, but are not typically used today. The core and cladding are manufactured together as a single piece of silica glass with slightly different compositions, and cannot be separated from one another.

Optical Fiber

Core

Amplifier,TresholdDetector

Cladding

ElectricalDriver

DetectorEmitter

Optical Pulses

LaserLight Emitting Diode (LED) Photodiode

Optical fiber cableOptical fiber cable

Chapter 3. Deployment architecture 59

CoatingThe third section of an optical fiber is the outer protective coating. This coating is typically an ultraviolet (UV) light-cured acrylate applied during the manufacturing process to provide physical and environmental protection for the fiber. During the installation process, this coating is stripped away from the cladding to allow proper termination to an optical transmission system. The coating size can vary, but the standard sizes are 250 µm or 900 µm.

Most enterprises today use the 62.5 micron core fiber due to its high proliferation in Local Area Networks (LAN). The Fibre Channel SAN standard is based on the 50 micron core fiber and is required to achieve distances specified in the ANSI Fibre Channel standards. Customers should not use the 62.5 micron fiber for use in SAN applications. It is wise to check with any SAN component vendor to see if 62.5 is supported.Figure 3-16 shows the various cables.

Figure 3-5 Single mode and multi mode cables

CopperThe Fibre Channel standards also allows for fibers made out of copper. There are different standards available:

� 75W Video Coax� 75W Mini Coax� 150W shielded twisted pair

The maximum supported speeds and distances using copper are lower than when using fiber optics.

Plenum ratingA term that is sometimes used when describing cabling is whether a particular cable is plenum rated or not. A plenum is an air filled duct, usually forming part of an air conditioning or venting system. If a cable is to be laid in a plenum, there are certain specifications which need to be met. In the event of a fire, some burning cables emit poisonous gases. If the cable is in a room, then there could be a danger to people in that room. If on the other hand, the cable is in a duct which carries air to an entire building, clearly, there is a much higher risk of endangering life.

Single-mode & Multi-mode cablesSingle-mode & Multi-mode cables

MultiMode Fiber

Core (50 um or 62.5 um)

Cladding (125 um)

Single-Mode Fiber

Core ( 9 um)

Cladding (125 um)

Core (9 um)

60 IBM Tivoli Storage Area Network Manager: A Practical Introduction

For this reason, cable manufacturers will specify that their products are either plenum rated or not plenum rated.

Connectors The particular connectors used to connect a fiber to a component will depend upon the receptacle into which they are being plugged. Some generalizations that can be made. It also is useful to mention some guidelines for best practices when dealing with connectors or cables.

Most, if not all, 2 Gbps devices will be using the Small Form Factor SFF or Small Form Factor Pluggable (SFP) technology, and therefore, use Lucent Connector (LC) connectors. Most Gigabit Interface Converter GBICs (see “GBICs and SFPs” on page 62) and Gigabit Link Module GLMs use industry standard Subscriber Connector (SC) connectors.

SC connectorsThe duplex SC connector is a low loss, push/pull fitting connector. It is easy to configure and replace. The two fibers each have their own part of the connector. The connector is keyed to ensure correct polarization when connected, that is transmit to receive and vice-versa.

See the diagram of an SC connector in Figure 3-6.

Figure 3-6 SC fibre optic cable

LC connectorsThe type of connectors which plug into SFF or SFP devices are called LC connectors. Again a duplex version is used so that the transmit and receive are connected in one step.

The main advantage that these LC connectors have over the SC connectors is that they are of a smaller form factor and so manufacturers of Fibre Channel components are able to provide more connections in the same amount of space. Figure 3-7 shows an LC connector.

Fiber optic cable with SC connector Fiber optic cable with SC connector

Chapter 3. Deployment architecture 61

Figure 3-7 LC connector

GBICs and SFPsGigabit Interface Converters (GBICs) are laser-based, hot-pluggable, data communications transceivers. GBICs are available in copper, and both short wavelength and long wavelength versions, which provide configuration flexibility. Users can easily add a GBIC in the field to accommodate a new configuration requirement or replace an existing device to allow for increased availability. They provide a high-speed serial interface for connecting servers, switches and peripherals through an optical fiber cable. In SANs, they can be used for transmitting data between physical Fibre Channel ports.

The optical GBICs use lasers that enable cost-effective data transmission over optical fibers at various distances (depending on the type) of up to distances of around 100 km.

These compact, hot-pluggable, field-replaceable modules are designed to connect easily to a system card or other device through an industry-standard connector. On the media side, single-mode or multi-mode optical fiber cables, terminated with industry-standard connectors, can be used.

GBICs are usually easy to configure and replace. If they are optical, they use low-loss, push-pull, optical connectors. They are mainly used in hubs, switches, directors, and gateways. A GBIC is shown in Figure 3-8.

SFPs (Small Form-Factor Pluggable) modules are functionally equivalent to GBICs but use LC connectors. They are increasingly more commonly used than GBICs.

Figure 3-8 GBIC

LC connectorLC connector

A typical GBICA typical GBIC

62 IBM Tivoli Storage Area Network Manager: A Practical Introduction

3.4 TopologiesFibre Channel provides three distinct interconnection topologies. This allows an enterprise to choose the topology best suited to its requirements. See Figure 3-9. The three Fibre Channel topologies are:

� Point-to-point� Arbitrated loop� Switched fabric

Figure 3-9 Fibre Channel topologies

3.4.1 Point-to-pointPoint-to-point is the simplest Fibre Channel configuration to build, and the easiest to administer. Figure 3-10 shows a simple point-to-point configuration. If you only want to attach a single Fibre Channel storage device to a server, you could use a point-to-point connection, which would be a Fibre Channel cable running from the Host Bus Adapter (HBA) to the port on the device. Point-to-point connections are most frequently used between servers and storage devices, but may also be used for server-to-server communications.

Figure 3-10 Fibre Channel point-to-point

Fibre Channel TopologiesFibre Channel Topologies

Server Disk

Fibre Channel

100MB/sFull Duplex

Fibre Channel Point to PointFibre Channel Point to Point

Chapter 3. Deployment architecture 63

3.4.2 Arbitrated loop In Fibre Channel arbitrated loop (FC-AL), all devices on the loop share the bandwidth. The total number of devices which may participate in the loop is 126. For practical reasons, however, the number tends to be limited to no more than 10 and 15.

Due to the limitations of FC-AL, it is not typical to build a SAN just around hubs. It is possible to attach a hub to a switched fabric. This allows devices which do not support the switched topology to be utilized in a large SAN.

Hubs are typically used in a SAN to attach devices or servers which do not support switched fabrics, but only FC-AL. They may be either unmanaged or managed. See Figure 3-11 for an FC-AL topology.

Figure 3-11 Fibre Channel Arbitrated Loop (FC-AL)

HUB

Fibre Channel Arbitrated Loop (FC-AL)Fibre Channel Arbitrated Loop (FC-AL)

64 IBM Tivoli Storage Area Network Manager: A Practical Introduction

3.4.3 Switched fabricsSwitches allow Fibre Channel devices to be connected together, implementing a switched fabric topology between them. Unlike in an Arbitrated Loop hub, where all connected devices share the bandwidth, in a switch all devices operate theoretically at full Fibre Channel bandwidth. This is because the switch creates a direct communication path between any two ports which are exchanging data. The switch intelligently routes frames from the initiator to the responder. See Figure 3-12.

Figure 3-12 Fibre Channel switched fabric

It is possible to connect switches together in cascades and meshes using inter Switch links or ISLs. It should be noted that devices from different manufacturers may not inter-operate fully (or even partially) as standards are still being developed and ratified.

As well as implementing this switched fabric, the switch also provides a variety of fabric services and features such as:

� Name services� Fabric control� Time services� Automatic discovery and registration of host and storage devices� Rerouting of frames, if possible, in the event of a port problem� Features commonly implemented in Fibre Channel switches include:

– Telnet and/or RS-232 interface for management– HTTP server for Web-based management– MIB for SNMP monitoring– Hot swappable, redundant power supplies and cooling devices– Online replaceable GBICs/interfaces– Zoning– Trunking– Other protocols in addition to Fibre Channel

Fibre Channel Switch

Fibre Channel Switch

Fibre Channel Switch FabricFibre Channel Switch Fabric

Chapter 3. Deployment architecture 65

3.5 IBM Tivoli SAN Manager componentsEach of the IBM Tivoli SAN Manager components are identified below with a brief description of their function.

3.5.1 DB2IBM Tivoli SAN Manager uses DB2 as its data repository. DB2 should be installed on the server system before installing IBM Tivoli SAN Manager. The installation process automatically creates the required database and tables in the instance.

3.5.2 IBM Tivoli SAN Manager Console (NetView)The IBM Tivoli SAN Manager Console performs the following functions:

� Graphically displays SAN topology — including physical and logical views� Displays attributes of entities on the SAN� Provides a GUI to configure and administer IBM Tivoli SAN Manager� Provides various reporting functions� Provides a launching facility for SAN component management applications� Displays ED/FI status and logs.� Displays status of discovered iSCSI devices.

The IBM Tivoli SAN Manager Console can be local — that is, installed on the manager system itself, and also remote — so that it is available on another system with NetView available. The installation process provides an option to install a remote NetView console See Chapter 4, “Installation and setup” on page 95 for information on installing IBM Tivoli SAN Manager.

3.5.3 Tivoli SAN Manager AgentsThe IBM Tivoli SAN Manager Agents are also referred to as Managed Hosts (MH). Managed Hosts perform the following tasks:

� Gather information about the SAN by querying switches and devices for attribute and topology

� Gather host level information, including filesystems and logical volumes

� Gather event information detected by HBAs.

All the data is gathered and returned to the Managed Host, which forwards it back to the IBM Tivoli SAN Managerr.

3.5.4 Tivoli SAN Manager ServerThe Manager Server manages the functionality of IBM Tivoli SAN Manager and the Managed Hosts running on connected host machines. The Manager does the following:

� Gather data from Agents (such as description of SAN, filesystem information, ED/FI information)

� Provide information to consoles (e.g. graphical display of SAN, reports etc.).

� Forwards events to a Tivoli Enterprise Console (TEC) or any other SNMP Manager. Note that the TEC and external SNMP managers are not supplied with IBM Tivoli SAN Manager.

66 IBM Tivoli Storage Area Network Manager: A Practical Introduction

3.5.5 SAN physical viewThe physical view in Figure 3-13 below identifies the installed IBM Tivoli SAN Manager components (Server, Agents, Console and Remote Console), and allows the physical SAN topology to be understood. A SAN environment typically consists of four major classes of components:

� End-user computers and clients� Servers� Storage devices and subsystems� Interconnect components

End-user platforms and server systems are usually connected to traditional LAN and WAN networks. In addition, some end-user systems may be attached to the Fibre Channel network, and may access SAN storage devices directly. Storage subsystems are connected using the Fibre Channel network to servers, end-user platforms, and to each other. The Fibre Channel network is made up of various interconnect components, such as switches, bridges, gateways.

Figure 3-13 Component placement

Note: The Server system requires an IP connection, but not a Fibre Channel connection (this is optional). Similarly for a Remote Console, and a TEC or SNMP system, since all communication to these systems is sent over TCP/IP. Hosts with Agent code installed require a Fibre Channel attachment (for discovery and monitoring) in addition to the LAN connectivity to the Manager. There will also most likely be additional hosts which are FC attached but do not have the Agent installed. We discuss various deployment options for this in 3.8, “Deployment scenarios” on page 76.

Component placementComponent placement

Eth

erne

t

Tivoli SAN ManagerRemote Console

NetView

Tivoli SAN Manager AgentWin2k

FabricA

Tivoli SAN Manager AgentAIX

Tivoli SAN Manager

DB2

Tivoli SAN ManagerNetView

ESS

Systems

Systems

SP

SAN Data Gateway

Tape

TEC or other SNMPmanager

AIX (no agent)

FabricFabricBB

WebSphere Express

Chapter 3. Deployment architecture 67

3.6 ManagementThe elements that make up the SAN infrastructure include intelligent disk subsystems, tape systems, Fibre Channel switches, hubs. The vendors of these components usually provide proprietary software tools to manage their own individual elements.

For instance, a management tool for a hub will provide information regarding its own configuration, status, and ports, but will not support other fabric components such as other hubs, switches, HBAs, and so on. Vendors that sell more than one element often provide a software package that consolidates the management and configuration of all of their elements. Modern enterprises, however, usually purchase storage hardware from a number of different vendors, resulting in a highly heterogeneous SAN.

Fabric monitoring and management is an area where a great deal of standards work is being focused. Two management methods are used in Tivoli SAN Manager: inband and outband management.

3.6.1 Inband managementThe inband Agent performs its scans directly across the Fibre Channel transport. The collected data from the scan is then sent to the Server via TCP/IP protocol. This is known as Inband management. Inband management is evolving rapidly and reporting on low level interfaces such as Request Node Identification Data (RNID). Tivoli SAN Manager runs two types of inband scanners for gathering Fibre Channel attribute and topology information. They are:

Topology ScannerThe topology scanner receives a request to scan from the manager. It issues FC Management Server commands (FC-GS-3 standard) to the SAN interconnection devices to get the topology information. The specific FC Management Server commands are:

� Get platform information� Get interconnect information

The topology scanner queries every device within each zone that it belongs to. When a scan request is issued from the Server to the Agent, the agents queries the nameserver in the Fibre Channel switch. The nameserver then returns identification information on every device in its database. The symbol label on the topology map is derived from the nameserver. With this information it constructs a complete physical topology map which shows all connections, devices, and zone information.

The topology scanner does not use a database to store results. The discovered data will be translated to XML format and sent back to the IBM Tivoli SAN Manager Server where it is stored in the DB2 repository.

Attribute ScannerThe attribute scanner gets the request from the IBM Tivoli SAN Manager Server to poll the SAN. It uses inband discovery, (specifically the SNI HBA API) to discover endpoint devices. These are Fibre Channel (FC) commands to the endpoint devices to gather attribute information.

Typically, the commands used are:

� SCSI Inquiry� SCSI Read Capacity

68 IBM Tivoli Storage Area Network Manager: A Practical Introduction

When the attribute scanner runs on a system, it first queries the nameserver on the Fibre Channel switch to get a list of storage devices in the SAN. The scanner then verifies if the LUNs are visible to the host by issuing SCSI commands. In most cases the host can see all the LUNs in the SAN even if they are not assigned to a system (if they are not LUN masked).

Since SCSI commands are issued from the Agent, the Agent must have LUNs assigned to the SAN attached storage device to gather the attribute information.

Figure 3-14 shows the inband scanner process.

Figure 3-14 Inband scanning

3.6.2 Outband managementOutband management means that device management data are gathered over a TCP/IP connection such as Ethernet. Commands and queries can be sent using Simple Network Management Protocol (SNMP). Outband management does not rely on the Fibre Channel network. Therefore, management commands and messages can be sent even if a loop or fabric link fails. Integrated SAN management facilities are more easily implemented, especially by using SNMP, when inband agents cannot be deployed because of platform capability or client requirements. Outband agents are defined to Tivoli SAN Manager, and are typically switches with the appropriate MIB enabled. The Advanced Topology Scanner is used for outband discovery:

Note:

� The attribute & topology scanner executables for Windows can be found in \tivoli\itsanm\agent\bin\w32-ix86\

� The attribute & topology scanner executables for AIX can be found in /tivoli/itsanm/agent/bin/aix

Inband scanningInband scanning

Tivoli SAN Manager

Eth

erne

t

AIXAgent

SolarisAgent

Fibre Channel switch fabricB

Fibre Channel switch fabricB

Legend

Inband scanner request fromSolaris and switches

Inband scanner request fromAIX and switches

Fabric A

Fabric B

Storage System

Chapter 3. Deployment architecture 69

Advanced Topology ScannerFor outband discovery, the Advanced Topology Scanner is used to query the MIB of the SNMP agents running to gather Fibre Channel port and switch information. The Advanced Topology Scanner queries the ConnUnitPortTable and ConnUnitLinkTable in the FA-MIB for switch port and link connection data. This data is used in creating the Tivoli SAN Manager topology map.

The outband scanner process is show in Figure 3-15 below. The outband query simply retrieves information from the MIB in the switches — no discovery across links is done, as is the case with inband discovery. The information retrieved is correlated by the Manager and used to draw the topology map.

.

Figure 3-15 Outband scanning

3.7 Deployment considerationsIn the following sections we outline and discuss the requirements of the Server and Agents for Tivoli SAN Manager, and various deployment scenarios.

3.7.1 Tivoli SAN Manager ServerThe most current product requirements for Tivoli SAN Manager are available at the Web site

http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageAreaNetworkManager.html

IBM Tivoli SAN Manager runs on Windows 2000 Server or Advanced Server with Service Pack 3. In addition, it should be running on a system with at least a Pentium® III 600Mhz class processor, 1 GB of RAM, and 1 GB of free disk space. It is also supported on a pSeries or RS/6000® running AIX 5.1, with minimum 375 Mhz processor, 200 MB free disk space, and 1GB RAM.

Outband scanningOutband scanning

LegendManager issues outband scanner

request to switches

Tivoli SAN Manager

Eth

ern

et

AIXAgent

SolarisAgent

fibre channel switch fabricA

fibre channel switch fabric B

70 IBM Tivoli Storage Area Network Manager: A Practical Introduction

It is also recommended that the system be dedicated to running Tivoli SAN Manager, rather than running other key enterprise applications.

The Server system also requires TCP/IP network connection and addressability to the hosts and devices on the SAN. It does not need to be attached to the SAN via Fibre Channel.

At this time, Tivoli SAN Manager requires a single machine install, where all the components (DB2, WebSphere Express, NetView and the manager code itself) are installed and running on the same system. Figure 3-16 shows the components of the Tivoli SAN Manager Server.

Figure 3-16 Components of a manger install

Tivoli SAN Manager requires that the Manager use a fully qualified static TCP/IP host name. You will need to make DNS services accessible to the Tivoli SAN Manager. Agents, however, can now utilize dynamic IP addresses (DHCP) instead of static IP addresses. Other pre-installation checks are given in 4.2, “IBM Tivoli SAN Manager Windows Server installation” on page 96.

Tivoli SAN Manager does not at this time provide built-in cluster support for high availability. If you require a high availability solution for Tivoli SAN Manager without clustering software, we recommend the configuration of a standby server with an identical network configuration and replicate the Tivoli SAN Manager database to that standby server on a regular basis.

3.7.2 iSCSI managementIBM Tivoli SAN Manager provides basic support for discovering and managing iSCSI devices. iSCSI devices are discovered by the NetView component of IBM Tivoli SAN Manager. By default, NetView IP Internet discovery is disabled. This will need to be enabled prior to any iSCSI devices being discovered and managed. See Chapter 7, “Tivoli SAN Manager and iSCSI” on page 253.

Note: Based on actual customer deployments, optimal server sizing for the Tivoli SAN Manager is 2-way (dual) Pentium III class processor with a speed of 800 Mhz (or equivalent pSeries), 2GB of Random Access Memory (RAM), and 1 GB of free disk space

SAN Network Software ModelWebSphere Express

DB2 Repository

Tivoli SAN Manager

Console - NetView

Tivoli SAN Manager ServerTivoli SAN Manager Server

WindowsWindows

WebSphere Express

DB2 Repository

Tivoli SAN Manager

AIXAIX

Console - NetView

WindowsWindows

Chapter 3. Deployment architecture 71

3.7.3 Other considerationsIBM now provides an improved BAROC file for use with IBM Tivoli Enterprise Console. Details of using this are in Chapter 12, “Tivoli SAN Manager and TEC” on page 333.

3.7.4 Tivoli SAN Manager Agent (Managed Host)

The Tivoli SAN Manager Managed Agent is also known as a Managed Host. Consideration needs to given to what functionality is desired from Tivoli SAN Manager. The Agent can be deployed to assist in network management and is also used to collect logical information about filesystems and perform error detection on SAN interconnect links.

Refer to the IBM Tivoli SAN Manager Installation Guide, SC23-4697 for prerequisite checks that should be performed on the target managed host prior to any code installation. Please also refer to 4.4, “IBM Tivoli SAN Manager Agent installation” on page 112.

Levels of SAN managementThe four levels of SAN Management are shown in Figure 3-17. When deploying IBM Tivoli SAN Manager, the customer must decide how much SAN management is required.

Figure 3-17 Level s of Fabric Management

Basic Fabric Management Use this configuration when you want to monitor the SAN and receive event notification of state changes of any of the fabric connections or devices. if you do not require endpoint identification, LUN associations, or endpoint properties, this configuration will provide limited Event Detection and Fault Isolation (ED/FI) capabilities. ED/FI will adorn the Fibre Channel switch with events that are detected. No switch port or host systems will be adorned.

Important: Tivoli SAN Manager Agents should not be installed on any servers that communicate with removable media devices, except where the environment provides the required support. Each time a discovery is run, the agents send SCSI commands to devices to identify their device types. If the target is a removable media device that cannot handle command queuing, a long tape read or write command might time out. This restriction does not apply to AIX Version 5.1 Agents, or certain IBM tape devices. For an up-to-date list of environments where this restriction does not apply, see the Web site

http://www-3.ibm.com/software/sysmgmt/products/support/IBM_TSANM_Device_Compatibility.html

SAN Network Software Model

Well Placed Agents

Agents Everywhere

Basic fabric management

Manual Indentity of Endpoints

72 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Manual Identity of EndpointsMonitor the SAN as described in Basic Fabric Management. In addition, perform a one-time manual identification of all SAN endpoints.

Well Placed Agents Monitor the SAN as described in Basic Fabric Management. In addition, deploy strategically placed agents to help identify endpoints and provide logical information on key SAN attached host systems. ED/FI will have greater fault isolation capabilities when agents are deployed in the SAN. If errors are detected by ED/FI, adornments will be displayed on the host system running the agents and the corresponding switch and switch port to which it is connected.

Agents Everywhere Monitor the SAN as described in Basic Fabric Management, plus deploy the inband Agents to automatically identify as many endpoints as possible. This is useful in a dynamic SAN, where endpoints change often. This will provide the greatest level of ED/FI.

Host systems with HBA, but no SAN connectivityWe tested a scenario where the IBM Tivoli SAN Manager Agent was installed on a host system with a supported HBA, but without connectivity to the SAN (no FC cables attached). The Agent system was discovered and displayed in the Configure Agents window. We saw the messages in Example 3-1 logged in \Tivoli\itsanm\manager\log\msgITSANM.log. To avoid these errors, connect the host to the SAN before installing the agent. Once the FC cables were attached to the host system, the Agent was automatically added to the topology map.

Example 3-1 Host system with HBAs, no SAN connectivity

2003.06.04 13:24:07.391 BTAHM2528I Agent diomede.almaden.ibm.com:9570 has been marked active.com.tivoli.sanmgmt.diskmgr.hostservice.manager.AgentRegistrationListener agentRegistrationHeartbeat 2003.06.04 13:27:20.688 BTAQE1144E An error occurred attempting to run the Topology scanner on the IBM Tivoli Storage Area Network Manager managed host diomede.almaden.ibm.com:9570. com.tivoli.sanmgmt.tsanm.queryengine.InbandScanHandler2003.06.04 13:27:20.875 BTADE1720I Processing has started for the missing devices for scanner ID S0e3.31.1e.71.90.66.11.d7.ba.4e.00.09.6b.92.a6.379570 . com.tivoli.sanmgmt.tsanm.discoverengine.TopologyProcessor process()

Host systems with no HBADeploying a Tivoli SAN Manager Agent to a host system with no HBAs is not a supported configuration. We tested this configuration and discovered that when deploying an Agent to a host system with no HBAs, the Agent code installed successfully and appeared in the Configure Agents window as contacted. We saw the messages in Example 3-2 logged in

Important: Consideration must be given to the number of Agents and how the initial discovery is performed. Depending on the number of endpoints to discover, IBM Tivoli SAN Manager may taken a long time to complete the discovery process. The full discovery options are shown below:

� Never run the full discovery (use topology discovery only).� Only run the full discovery when the user selects Poll Now.� Only run the full discovery during a periodic or scheduled discovery.� Run the full discovery when the user selects Poll Now or during a periodic or scheduled

discovery.

See IBM Tivoli SAN Manager Planning and Installation Guide, SC23-4697.

Chapter 3. Deployment architecture 73

\Tivoli\itsanm\manager\log\msgITSANM.log. Therefore an HBA should be installed in a host before installing the Agent.

Example 3-2 Host system with no HBAs

2003.06.04 14:32:16.922 BTAHM2528I Agent wisla.almaden.ibm.com:9570 has been marked active. 2003.06.04 14:32:52.906 BTAQE1144E An error occurred attempting to run the Topology scanner on the IBM Tivoli Storage Area Network Manager managed host wisla.almaden.ibm.com:9570.com.tivoli.sanmgmt.tsanm.queryengine.InbandScanHandler run

Host and Device Centric ViewsThe Device or Host Centric data views report on local filesystems as well as Fibre-attached assigned LUNs for Managed Hosts. Therefore, if a Managed Host has no Fibre LUNs assigned, only local disks will be reported. Once LUNs are assigned, all SAN attached storage will be presented correctly under Device and Host Centric views. Consideration should be given as to which SAN attached hosts have Agents installed. This concept is known as the well placed agent. Refer to 5.7.9, “Well placed agent strategy” on page 202 for more information.

Request Node Identification (RNID)Request Node Identification (RNID) is supported by Tivoli SAN Manager and the Agents. Refer to the product Web site for a complete listing of the latest drivers and APIs that support RNID.

We found that if one Tivoli SAN Manager Agent was deployed to a SAN attached host with an RNID enabled driver, then the remaining SAN attached hosts without Agents were discovered with the correct symbol type and WWN, providing their HBA also supports RNID. See Figure 3-18 for an RNID discovered unmanaged host. Note that an unmanaged host will not display any information on the logical Device and Host Centric views.

Figure 3-18 RNID discovered host

74 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Table 3-1 gives information on the capabilities of IBM Tivoli SAN Manager depending on the RNID capability of the Agents and other hosts.

Table 3-1 SAN Manager using vendor HBAs and switches

Level of information collected

Level of vendor HBA device driver support

What information can be gathered and shown

Good Not using common API Tivoli SAN Manager can do outband management in this situation. Also, if other inband agents have Better or Best levels of HBAs, then Tivoli SAN Manager can do inband discover through those agents.

Information shown:

Switches with IP connections to the manager.

Topology that can be seen from the switches with IP connections to the manager.

Hosts and other devices shown as Unknown entities in the topology view.

Better Use common API without RNID support

Tivoli SAN Manager can do both outband and inband management. Other inband agents will not be able to obtain RNID information from this HBA. In addition to the Good level of information, you will see:

Managed hosts with agents installed are not shown as Unknown entities in the topology view.

Some storage devices will no longer be shown as Unknown entities in the topology view.

Chapter 3. Deployment architecture 75

3.8 Deployment scenariosWe present the following examples to demonstrate some various deployment possibilities using outband, inband and a combination of outband and inband.

3.8.1 Example 1: Outband onlyThis example describes sample requirements that were compiled based on actual customer requirements. We outline advantages and disadvantages of using an outband only deployment configuration in IBM Tivoli SAN Manager and provide an overview of the install steps. Figure 3-19 describes our requirements.

Figure 3-19 Sample outband requirements

AdvantagesThe major advantage of deploying outband only agents is quick configuration and non intrusive deployment, since no Tivoli SAN Manager Agent code is required on any SAN host. After installing the Tivoli SAN Manager, the discovery is completed in a short amount of time by adding in the IP addresses or hostname of the Fibre Channel interconnect devices to Tivoli SAN Manager. This typically a switch or a director. There are limited Event Detection and

Best Common API with RNID support

Outband, inband and RNID information are fully supported. In addition to the good and better level of information, you will see:

All agents that have HBAs that respond to RNID. Even if the agent is not installed, these hosts will not be shown as Unknown entities in the topology view.

Storage devices that respond to RNID will also no longer be shown as Unknown entities in the topology view.

Note: You should plan what information is required to be displayed when deciding where to deploy the Server and inband and outband Agents.

Level of information collected

Level of vendor HBA device driver support

What information can be gathered and shown

Outband requirementsOutband requirements

Topology map of the SAN

State changes of any of the fabric connections or devices

Network management only

Dedicated console for operations staff

76 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Fault Isolation (ED/FI) capabilities. ED/FI will adorn the fibre channel switch of the events detected.

DisadvantagesThere are no endpoint identifications, LUN associations, or endpoint properties. It provides limited attribute information on the topology map. Once the discovery is complete, the default symbols for SAN attached devices (other than the switches) are displayed as “Unknown” symbols. The World-Wide Name (WWN) is also shown. See Figure 5-67 on page 197 for an example of using outband agents only. This is caused by the limited attribute information retrieved from the Advanced Topology Scanner. Once the discovery is complete, we can then change the symbol properties of the “Unknown” host to their actual symbol type and name. Figure 5-32 on page 173 shows how to change the symbol type and name. Figure 3-20 shows the outband agents defined in the Configure Agents panel of IBM Tivoli SAN Manager. Furthermore, no switch port or host systems will be adorned by ED/FI.

For detailed information on changing the symbol type and symbol name refer to 5.4.1, “SAN Properties” on page 170. No Device or Host Centric views will be available, since these depend on information gathered by the Agents (inband).

Figure 3-20 Display and configure outband agents

Setup procedureWith the above requirements, and noting the limitations, we can set up this scenario.

Chapter 3. Deployment architecture 77

1. We first recommend verifying that the SAN is fully operational and check all the SAN attached devices for compatibilities and incompatibilities. The following URL provides compatibility requirements.

http://www-3.ibm.com/software/sysmgmt/products/support/IBM_TSANM_Device_Compatibility.html

2. Once the SAN attached components have been analyzed, review the Tivoli SAN Manager prerequisite checklist. Please refer to 4.2.2, “Preinstallation tasks” on page 97.

3. Enable the trap destination table on Fibre Channel switches or directors to forward SNMP traps to Tivoli SAN Manager. We demonstrate below the process for enabling the trap forward definitions on an IBM 2109 Fibre Channel switch.

a. Log into the switch as administrator and issue the agtcfgshow command. This command is used for displaying the SNMP community names and trap destination configuration of the FC switch. See Example 3-3 below.

Example 3-3 agtcfgshow output

itsosw3:admin> agtcfgshowCurrent SNMP Agent ConfigurationCustomizable MIB-II system variables: sysDescr = agtcfgset sysLocation = E3-250 sysContact = Charlotte Brooks swEventTrapLevel = 0 authTrapsEnabled = true

SNMPv1 community and trap recipient configuration: Community 1: Secret C0de (rw) No trap recipient configured yet Community 2: OrigEquipMfr (rw) No trap recipient configured yet Community 3: private (rw) Trap recipient: 9.1.38.187 Community 4: public (ro) Trap recipient: 9.1.38.187 Community 5: common (ro) No trap recipient configured yet Community 6: FibreChannel (ro) No trap recipient configured yet

SNMP access list configuration:Entry 0: No access host configured yetEntry 1: No access host configured yetEntry 2: No access host configured yetEntry 3: No access host configured yetEntry 4: No access host configured yetEntry 5: No access host configured yetitsosw3:admin>

Important: In this configuration, Tivoli SAN Manager relies on SNMP traps and polling intervals to determine when the status change of a Fibre Channel switch or director has occurred. It is recommended that SNMP trap destination tables of these devices by configured to point to the Tivoli SAN Manager’s IP address to allow for event driven management.

78 IBM Tivoli Storage Area Network Manager: A Practical Introduction

You can see above that Community 3 and Community 4 have already been assigned IP addresses of an SNMP manager. We highlighted in bold the current IP entries that we will modify. We want to change them to use our Tivoli SAN Manager.

b. We will now show the command to change the Community 3 and Community 4 fields to another IP address. Issue the agtcfgset command from the switch prompt. The agtcfgset command is interactive. To leave an entry unchanged, hit Enter.

c. We hit Enter several times until the 3rd and 4th community name fields are reached. We then entered in the new IP address and hit Enter. Keep hitting Enter until the message Committing Configuration...done is displayed and the command prompt is returned. See Example 3-4 for the output.

Example 3-4 agtcfgset output

itsosw3:admin> agtcfgset

Customizing MIB-II system variables ...

At each prompt, do one of the followings: o <Return> to accept current value, o enter the appropriate new value, o <Control-D> to skip the rest of configuration, or o <Control-C> to cancel any change.

To correct any input mistake:<Backspace> erases the previous character,<Control-U> erases the whole line,sysDescr: [ agtcfgset]sysLocation: [E3-250]sysContact: [Charlotte Brooks]swEventTrapLevel: (0..5) [0]authTrapsEnabled (true, t, false, f): [true]

SNMP community and trap recipient configuration:Community (rw): [Secret C0de]Trap Recipient's IP address in dot notation: [0.0.0.0]Community (rw): [OrigEquipMfr]Trap Recipient's IP address in dot notation: [0.0.0.0]Community (rw): [private]Trap Recipient's IP address in dot notation: [9.1.38.187] 9.1.38.188Community (ro): [public]Trap Recipient's IP address in dot notation: [9.1.38.187] 9.1.38.188Community (ro): [common]Trap Recipient's IP address in dot notation: [0.0.0.0]Community (ro): [FibreChannel]Trap Recipient's IP address in dot notation: [0.0.0.0]

SNMP access list configuration:Access host subnet area in dot notation: [0.0.0.0]Read/Write? (true, t, false, f): [true]Access host subnet area in dot notation: [0.0.0.0]Read/Write? (true, t, false, f): [true]Access host subnet area in dot notation: [0.0.0.0]Read/Write? (true, t, false, f): [true]Access host subnet area in dot notation: [0.0.0.0]Read/Write? (true, t, false, f): [true]Access host subnet area in dot notation: [0.0.0.0]Read/Write? (true, t, false, f): [true]Access host subnet area in dot notation: [0.0.0.0]Read/Write? (true, t, false, f): [true]

Chapter 3. Deployment architecture 79

Committing configuration...done.itsosw3:admin>

4. Install Tivoli SAN Manager. Refer to 4.2, “IBM Tivoli SAN Manager Windows Server installation” on page 96 for more details. When completed, launch NetView from the desktop.

5. Add the outband agents into Tivoli SAN Manager by specifying either IP address or hostname of the Fibre Channel switch in the Configure Agents GUI. See Figure 3-20 on page 77.

6. After being added and committed to the database, the SNMP agents are then automatically queried by the Advanced Topology Scanner and the data is returned where the manger will process and draw the initial SAN topology map. Figure 3-21 shows the outband management topology. Outband agents will continued to be polled at the user defined polling interval. See 4.6.4, “Performing initial poll and setting up the poll interval” on page 132.

7. Remote consoles, if required, can be installed anytime after the Server has been installed. The remote console contains the same functionality as the Server console. Once the console is installed it performs database queries for its topology updates from the Manager.

Figure 3-21 Outband management only

Attention: The initial discovery of any large SAN using outband discovery may take some time. Once complete, full discovery should not need to be run very often after that. Consideration should be given as to when the initial discovery is performed. We recommend scheduling initial discoveries during slower processing times for the business.

Outband managementOutband management

Eth

erne

t

Fibre Channel switch

Tiv oli SAN Manager

Tiv oli SAN Managerremote console

SNMP queries to SNMP agents

Fibre Channel switch

SNMP agent replies

SNMP agent replies

80 IBM Tivoli Storage Area Network Manager: A Practical Introduction

3.8.2 Example 2: Inband onlyIn this example we deploy inband agents instead of outband agents. The deployment of inband agents provides additional functionality over the outband agents. When an inband Agent is deployed, the topology information received at the Manager allows for a more complete picture of the SAN. For example, the host that is running the Agent will always appear with the correct symbol type and hostname for symbol label. Any other hosts running RNID enabled drivers will also be discovered with correct symbol type.

We outline advantages and disadvantages of using inband Agent deployment configuration in Tivoli SAN Manager. We provide an overview of the install steps. Figure 3-22 below describes the sample requirements for this example.

Figure 3-22 Sample inband requirements

AdvantagesAdditional attribute information is returned when inband agents are used. If there are RNID enabled HBAs installed on the SAN attached hosts, then this will allow for a more complete discovery of the SAN. Refer to 3.7.4, “Tivoli SAN Manager Agent (Managed Host)” on page 72 for more details on RNID. With RNID-enabled HBAs running on our host systems, the correct host symbol is used Compare this to the previous scenario with outband agents where they were discovered as unknown. We had other SAN attached hosts with RNID enabled HBA drivers, although without Tivoli SAN Manager Agents. These hosts that were running no agents were discovered correctly.

Inband agents provides logical views of SAN resources — these are the Host and Device centric views for hosts with agents installed. The Device Centric View enables you to see all the storage devices and their logical relation to all the managed hosts. This view does not show the switches or other connection devices. The Host Centric View enables you to see all the managed host systems and their logical relation to local and SAN-attached storage devices.

ED/FI will provide greater fault isolation capabilities when agents are deployed in the SAN. If errors are detected by ED/FI, adornments will be displayed on the host system running the agents and the corresponding switch and switch port that it is connected. See IBM Tivoli SAN Manager Planning and Installation Guide, SC23-4697.

Refer to 5.3.2, “Device Centric View” on page 166 and 5.3.3, “Host Centric View” on page 167 for details on Host and Device Centric Views.

DisadvantagesInband discovery is not available for non-supported Agent Operating Systems. Tivoli SAN Manager supports a limited number of Agent platforms at this time. If your platform is not supported, then an outband strategy may be more appropriate.

The more Agents which are installed, the more processes will run and the more data will be collected and co-related. This requires processing resources and time. The inband agent runs two scanners to collect attribute and topology information. See Figure 3-14 on page 69. The amount of data returned depends on the size of the SAN fabric.

Inband requirementsInband requirementsMore accurate topology map

Logical views of storage and host systems

Chapter 3. Deployment architecture 81

The Agent must be installed on the hosts which takes some CPU/memory resources and disk space.

Running many inband agents will require a corresponding amount of time and processing power to complete the initial discovery.

Setup procedure

With the above requirements, and noting the limitations, we can set up this scenario.

1. Verify that SAN is fully operational. We proceeded with checking all the SAN attached devices for compatibilities and incompatibilities.

2. Since we are installing Agent code on the SAN attached host, check the HBA make and model for compatibility, operating system levels and maintenance, plus the device driver release level and API compatibility. The following URL provides all compatibility requirements.

3. Once the SAN attached components have been analyzed, review the Tivoli SAN Manager prerequisite checklist for the Manager and SAN attached hosts.

4. Install Tivoli SAN Manager Server.

5. Install the Tivoli SAN Manager Agent on the selected hosts. The Agents will automatically populate the Configure Agents interface after installation. Figure 3-23 shows the Configure Agents interface after an inband agent has been deployed and contacted the Manager. Refer to 3.5.3, “Tivoli SAN Manager Agents” on page 66 for more details regarding the Agent installation process.

Important: Tivoli SAN Manager compatibility can be checked at the following URL:

http://www-3.ibm.com/software/sysmgmt/products/support/IBM_TSANM_Device_Compatibility.html

82 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 3-23 Configure Agents — Inband only

6. Launch NetView from the desktop.

7. Navigate to the SAN -> Configure Agents and note the Agents appear in the top half of this panel.

8. The Agents will automatically perform inband discovery to create the topology map. Figure 3-24 shows the inband management process.

Chapter 3. Deployment architecture 83

Figure 3-24 Inband management only

The remote console deployment strategy is the same as described in the outband Example.

3.8.3 Example 3: Inband and outbandFigure 3-25 provides an overview of the requirements for this example. This example differs from the previous examples in that both inband and outband agents are deployed. This configuration provides us with a more robust management environment. We have the ease of deployment of outband agents and leverage the additional functionality provided by the inband agents. The major difference is in the robustness of IBM Tivoli SAN Manager ability to discover and manage the topology. We outline advantages and disadvantages of using a combination of both types of agents, and provide an overview of the install steps.

Figure 3-25 Sample inband/outband requirements

This is the recommended approach — install at least one Agent per zone (preferably two for redundancy), and configure all capable switches as outband Agents.

AdvantagesBy default, Tivoli SAN Manager will work with inband and outband agents. With this combination we are assured of getting the most complete topology picture with attribute, topology and advanced scanner data being correlated at the Manager to create a full SAN topology.

We will continue to leverage RNID enabled drivers on SAN attached hosts for a more complete topology.

Inband managementInband management

Tivoli SANManager

Eth

erne

t

Fibre Channel switch

AIX

Storage system

Tivoli SANManager

Agent

FC FC

Inband & Outband requirementsInband & Outband requirements

More accurate and complete topology map

Management redundancy

Logical views of host and storage systems

Reduced single point of failure

84 IBM Tivoli Storage Area Network Manager: A Practical Introduction

The Host Centric and Device Centric logical views are available in addition to the topology display.

Zone information can be displayed where it is supported by the switch API.

It reduces the risk of single point of failure as both Fibre and IP links are used

Redundant and more complete information will be gathered and used to draw the topology map.

DisadvantageThe inband Agent install remains intrusive to the SAN attached host and there are potential performance implications for discovery if a large number of Agents are deployed.

Setup procedure

With the above requirements, and noting the limitations, we set up this example based on the steps below.

1. Verify that the SAN is fully operational. We proceeded with checking all the SAN attached devices for compatibilities and incompatibilities.

2. Since we are installing Agent code on the SAN attached host, check the HBA make, model and driver release levels for compatibility, operating system levels and maintenance.

3. Once the SAN attached components compatibility has been confirmed, review the Tivoli SAN Manager prerequisite checklist for our Manager and Agents.

4. Install the Tivoli SAN Manager Server.

5. Install inband agents.

6. Launch NetView from the desktop.

7. Navigate to SAN --> Configure Agents. The top half of the window displays the inband agents that are currently installed — which have been automatically added. Click Add to add outband agents. Figure 3-26 shows the Configure Agents interface with both inband and outband agents deployed. For more details on this, see 5.7.6, “Outband agents only” on page 195 and 5.7.7, “Inband agents only” on page 197.

Chapter 3. Deployment architecture 85

Figure 3-26 Inband & outband in Configure Agents

The Manager will perform another discovery of the SAN. Figure 3-27 shows the Agent deployment and management process.

86 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 3-27 Inband and outband management

The remote console deployment strategy is the same as described in 3.8.1, “Example 1: Outband only” on page 76.

3.8.4 Additional considerationsFinally, here are some additional considerations and pointers for deploying Tivoli SAN Manager. Check the manual IBM Tivoli Storage Area Network Manager: Planning and Installation Guide, SC23-4697 for more information on these tips.

Deploying Tivoli SAN Manager using a HOSTS fileAlthough the Installation Guide mentions that DNS must be used, we discovered that Tivoli SAN Manager installs and functions using a HOSTS file on the Manager and Agent. Figure 3-28 provides a view of the HOSTS file placement.

Inband & Outband managementInband & Outband management

Tivoli SANManager

Ethe

rnet

Fibre Channel switch

AIX Storage system

Agent

O U T B AN D via SNMP

I N B A N D via FC protocol

FC FC

Chapter 3. Deployment architecture 87

Figure 3-28 HOSTS file placement

Before installing the Manager, we updated the \system32\drivers\etc\HOSTS file to include entries for the Manager and all Agents. We then updated the HOSTS file on each Agent to include entries for the Manager and all other Agents. We then installed the Manager.

Tivoli SAN Manager with Remote Console� IBM Tivoli SAN Manager now supports Windows XP, in addition to Windows 2000 Server,

Advanced Server as a supported platform type for running the Remote Console

� If possible, start with a pristine machine (re-install if necessary) for the Manager and NetView Remote Console.

� Before installing the Remote Console, modify the HOSTS file to include the IP address LONGNAME SHORTNAME as the first entry as shown in “Change the HOSTS file” on page 97.

� Verify the screen resolution is at least 800x600 on the Manager

� Verify a range of seven sequential TCP/IP port numbers (starting with 9550-9556, these are the default ports assignments during install) are available. Use the netstat command to verify free ports. These ports are required by the Manager to run Tivoli SAN Manager related services.

� Verify that SNMP is installed and running as a service on the Manager and Remote Console.

Tivoli SAN Manager Agents� Make sure you have installed the appropriate HBA cards and device drivers.

� Run the common API setup program for the HBA on each managed host. This common API program is in addition to the required drivers for the HBA. For example, for a QLogic

Tivoli SANManager

Fibre Channel switch

Fibre Channel switchE

the

rnet

LocalHOSTS

File

AIXSAN Manager

Agent

WindowsSAN Manager

Agent

LocalHOSTS

File

LocalHOSTS

File

Tivoli SAN Manager using HOSTS fileTivoli SAN Manager using HOSTS file

88 IBM Tivoli Storage Area Network Manager: A Practical Introduction

HBA, you must run the EUSDSetup program. Contact your HBA manufacturer if you do not have this program.

� For Windows 2000, Windows NT, Solaris, or Linux, if using QLogic HBAs, specific versions of the QLogic and Device Driver are required for RNID support. Both API and Driver are packaged as one file. See the QLogic Web site (http://www.qlogic.com) for updates. The required API and Device Driver levels are listed for different QLogic HBAs at

http://www-3.ibm.com/software/sysmgmt/products/support/IBM_TSANM_Device_Compatibility.html

� The agent operating system must be at a level that supports JRE 1.3.1 or later for AIX and Solaris.

� For AIX 5.1 and 5.2 there are required patches that can be downloaded. See the readme.txt file for Tivoli SAN Manager for details of these.

Fibre Channel Switches� If using the IBM 2109 (Brocade Silkworm family of switches), the firmware level should be

as specified on the support Web site:

http://www-3.ibm.com/software/sysmgmt/products/support/IBM_TSANM_Device_Compatibility.html

� Make sure all FC MIBs are enabled. On the IBM 2109, all MIBs are disabled by default. You can use the snmpmibcapset command to enable the MIBs while logged on as administrator to a IBM 2109 switch. (refer to 6.2.3, “Loading MIBs” on page 212).

General� Verify all FC switch SNMP trap destinations point to the Tivoli SAN Manager IP address� The Tivoli SAN Manager and all agents must have static IP addresses� Your network should use DNS� The remote DNS server must know the static IP address of each machine� Verify forward and reverse lookup is working via DNS� Issue nslookup to confirm fully qualified host names of the Manager and Managed Host

systems.

3.9 High Availability for Tivoli SAN ManagerIn this section we discuss how to protect the Tivoli SAN Manager Server. In such a setup the Tivoli SAN Manager server is installed on the Windows 2000 platform using a central database repository. Our standby server uses a similar hardware configuration.

3.9.1 Standalone server failoverSince we are only protecting the Tivoli SAN Manager Server, one possible scenario is to have a standby server in the event that the primary Tivoli SAN Manager Server fails. The standby server could be a test Tivoli SAN Manager server with Agents belonging to the primary Tivoli SAN Manager domain. This setup is shown in Figure 3-29.

Chapter 3. Deployment architecture 89

Figure 3-29 Standby server

Here are the steps we followed:

1. We started with a fully deployed Tivoli SAN Manager Server.

2. We then installed Tivoli SAN Manager on the standby server, using the same system settings as the primary server.

3. We then stopped the IBM HTTP Administration Server, IBM HTTP Server and IBM WS Admin 4.0 services on the standby server and changed their startup to manual.

4. Backing up the Tivoli SAN Manager database on the primary server is optional. If you do not have customized data (topology symbol types and symbol names) saved, then you can omit this step. Otherwise, use the DB2 control center to select and backup the ITSANMDB database. See 10.2.2, “Setup for backing up IBM Tivoli SAN Manager Server” on page 286 for details.

5. We then simulated a failure on the primary server by stopping the Tivoli SAN Manager application on the WebSphere Application Server. We then stopped the services IBM HTTP Administration Server, IBM HTTP Server and IBM WS Admin 4.0

6. We then updated the DNS entry for the primary server, changing the IP address of the primary server hostname to that of the standby server hostname and leaving the hostname of the primary server associated with the IP address of the standby server. We could also update the HOSTS file for these changes if DNS is not used.

Stand-by Fail OverStand-by Fail Over

Fibre Channel switch

Fibre Channel switch

Eth

erne

t

StandbyTivoli SANManager

Tivoli SANManager

AIXSAN Manager

Agent

WindowsSAN Manager

Agent

Belongs to PrimarySAN Manager

Services stoppedIBM HTTP Administration Server

IBM HTTPIBM WS AdminServer 4.0

90 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Example 3-5 Agent HOSTS file

9.1.38.189 tungsten.almaden.ibm.com tungsten9.1.38.186 polonium.almaden.ibm.com polonium9.1.38.192 palau.almaden.ibm.com palau9.1.38.191 crete.almaden.ibm.com crete9.1.38.166 senegal.itsrmdom.almaden.ibm.com senegal9.1.38.165 diomede.itsrmdom.almaden.ibm.com diomede#9.1.38.186 lead.almaden.ibm.com lead

7. We then used the DB2 control center to restore our backed up database. See 10.5.2, “ITSANMDB database restore” on page 312

8. We then started IBM HTTP Administration Server, IBM HTTP Server and IBM WS Admin 4.0 on the standby server, and verified that Tivoli SAN Manager was running on the WebSphere Application server using the WebSphere Administration Console. See 4.2.8, “Verifying the installation” on page 110.

9. Finally we re-started the Agents. The failover process is summarized in Figure 3-30.

Figure 3-30 Failover process

Note: In our testing we used a HOSTS file on the Manager and all the Agents. For the HOSTS file on each Agent and Manager, we modified the IP address of the primary server in the HOSTS file to point to the IP address of the standby server. We then commented out the standby server HOSTS file entry. In Example 3-5 IP address 9.1.38.186 is the address of the standby server and polonium.almaden.ibm.com is the hostname of the primary server. We then commented out the entry for 9.1.38.186 lead.almaden.ibm.com, since this is the original entry that pointed to the standby server before failover

Fibre Channel switch

Fibre Channel switch

Eth

ern

et

StandbyTivoli SANManager

Tivoli SANManager

AIXSAN Manager

Agent

WindowsSAN Manager

Agent

1Server fails

2Stop agents

DNS

3update DNS

4Start services

IBM HTTP AdministrationIBM HTTP

IBM WS AdminServer 4.0

5Start agents

Failover processFailover process

Chapter 3. Deployment architecture 91

3.9.2 SummaryIn this chapter, we discussed fibre channel standards, SAN topologies in how they apply to IBM Tivoli SAN Manager. We also introduced inband and outband management as it relates to IBM Tivoli SAN Manager. Finally, we presented various deployment scenarios using IBM Tivoli SAN Manager.

92 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Part 3 Installation and basic

operations

In Part 3 we describe how to install, configure, and uninstall IBM Tivoli SAN Manager. We then cover, in detail, the basic functions, including the different topology displays.

Part 3

© Copyright IBM Corp. 2002, 2003. All rights reserved. 93

94 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 4. Installation and setup

This chapter provides information about installing IBM Tivoli SAN Manager in various environments. We discuss:

� Installation of the Server and Agent components and also installation of the remote console.

� Setup of the environment after installation, including adding devices to monitor (via SNMP) and adding managed Agents. We show how to set up the monitoring parameters, such as the polling interval.

We do not cover every possibility of installation here — for complete details, consult IBM Tivoli Storage Area Network Planning and Installation Guide, SC23-4697.

4

© Copyright IBM Corp. 2002, 2003. All rights reserved. 95

4.1 Supported operating system platformsIBM Tivoli SAN Manager has three major components:

� Server� Agents� Remote console

Figure 4-1, shows the supported platforms for each component, as at the time of publication.

Figure 4-1 IBM Tivoli SAN Manager —supported operating system platforms

4.2 IBM Tivoli SAN Manager Windows Server installationThis section describes how to install IBM Tivoli SAN Manager Server. The steps are summarized in Figure 4-2 for the Windows Server.

Figure 4-2 Installation of IBM Tivoli SAN Manager

4.2.1 Lab environmentWe installed the Server on a system named LOCHNESS, with Windows 2000 Server with Fix Pack 3.

Supported Manager platformsWindows 2000 SP3 (Server, Advanced Server or Professional) with SNMP service installed

AIX 5.1 Maintenance Level 2 with APAR IY34030

Supported Agent platformsWindows NT 4 SP6A

Windows 2000 SP2 (Server, Advanced Server or Professional) each with SP3

AIX 5.1 (with APAR IY34030) or 5.2 with support for JRE 1.3.1

Solaris 2.6 or 2.8 with support for JRE 1.3.1

Linux Red Hat Advanced Server 2.1 (32 Bit) Kernel 2.4.9

SuSE Linux Enterprise Server Version 7.0 (32 Bit) Kernel 2.4.7

Supported Remote Console platformsWindows 2000 SP3 (Server, Advanced Server or Professional) with SNMP service installed

Windows XP

InstallationStatic IP required, seven contiguous free ports required

Fully qualified hostname required

Install DB2 7.2 and FP8

Upgrade DB2 JBDC drivers to version 2

Install the SNMP service (if not installed)

Install the Server code Embedded install of the IBM WebSphere Application Server V5.0 Tivoli NetViewTivoli SAN Manager Server

96 IBM Tivoli Storage Area Network Manager: A Practical Introduction

4.2.2 Preinstallation tasksBefore starting the installation you need to ensure that the following requirements are met.

Fully qualified host nameTivoli SAN Manager requires a fully qualified hostname. You can verify your computer host name setting by right-clicking My Computer on the desktop and selecting Properties. When the window opens, click Network Identification and you will see information like Figure 4-3.

Figure 4-3 Verifying system host name

If you do not have a full computer name, including domain name, change it by clicking Properties and supply the fully qualified domain name (FQDN) as shown in Figure 4-4.

Figure 4-4 Computer name change

After this change, you need to reboot the system for it to become effective.

Change the HOSTS fileOn Windows 2000 systems with Fix Pack 3 installed you must edit the HOSTS file to resolve the long host name. Normally, the address resolution protocol (ARP) returns the short name

Chapter 4. Installation and setup 97

rather than the fully qualified host name. This can be changed in the hosts tables on the DNS server and on the local computer. For a Windows 2000 system, edit the HOSTS file in %SystemRoot%\system32\drivers\etc. The %SystemRoot% is the installation directory for Windows 2000, usually WINNT. The long name should appear before the short name as in Example 4-1.

Example 4-1 POLONIUM HOSTS file

9.1.38.167 lochness.almaden.ibm.com lochness9.1.38.166 senegal.almaden.ibm.com senegal9.1.38.150 bonnie.almaden.ibm.com bonnie127.0.0.0 localhost

Check for existing Tivoli NetView installationIf you have an existing Tivoli NetView 7.1.3 for Windows 2000 installation you can use it with IBM Tivoli SAN Manager Server. If any other version is installed, you must uninstall it before installing the IBM Tivoli SAN Manager Server.

4.2.3 DB2 installationAs IBM Tivoli SAN Manager stores its data in a database we need to install DB2 Version 7.2, which is today the only supported database. DB2 needs to be installed on the same system as the IBM Tivoli SAN Manager Server installation — remote databases are not supported.

If you are installing on a system which already has DB2 Enterprise Edition Version 7.2 installed, you need to install fix pack 8 to meet the requirements.

Before installing DB2, you should create a userid with administrative rights, and install DB2 this userid. In our example we created the userid db2admin. If this user does not already exist, it will be created during DB2 installation.

When installing DB2, you only need to select the DB2 Enterprise Edition component. You can then accept all defaults — the only thing you need to change is to select Do not install the OLAP Starter Kit. After installation, reboot the system. When the system restarts, check that the DB2 service was started as shown in Figure 4-5.

Attention: Host names are case-sensitive. The case used for the computer name in Network Identification (Figure 4-3) must be the same as that used in the HOSTS file.

Tip: The database can be also used for other data, but we recommend a dedicated database for IBM Tivoli SAN Manager to avoid any potential performance impact.

Important: Installation can only be performed with a userid with local administrative rights.

98 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-5 DB2 services

4.2.4 Upgrading DB2 with Fix Pack 8Fix Pack 8 is required for the DB2 installation used with IBM Tivoli SAN Manager. You can get the fix pack from:

http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/report

To apply the Fix Pack do the following:

1. Logon to the system with the userid used for DB2 installation, in our example db2admin.

2. Stop all applications accessing DB2 databases, and stop all DB2 services (including DB2 Warehouse if running).

3. Unzip the fix pack file you downloaded.

4. Run the SETUP.EXE. This will install the upgrade over your existing DB2 installation.

5. Reboot the system.

Upgrade JDBC drivers to Version 2To upgrade your DB2 JDBC drivers to Version 2, follow these steps:

1. Close all browser windows.

2. Open a command prompt window and use it to perform all following steps, and monitor error messages.

3. Change the drive and directory to where you installed the DB2 executable files. The default directory is C:\Program Files\SQLLIB.

4. Change to the directory java12.

5. Look for the file inuse. If it exists, and contains JDBC 2.0, the correct JDBC driver is already installed. If the correct driver is not installed, follow these steps:

a. Stop all programs that might be using DB2.

Chapter 4. Installation and setup 99

b. Stop DB2 by issuing the command: db2stop. If DB2 does not stop with this command, you can use db2stop force.

c. Run the batch file usejdbc2.bat. Make sure that there are no error messages. If so, correct the errors and try again.

d. Restart DB2 by issuing the command: db2start.

4.2.5 Install the SNMP serviceTivoli NetView, which is a component of IBM Tivoli SAN Manager, requires the Windows 2000 SNMP service. To install this, select Control Panel -> Add/Remove Programs -> Add/Remove Windows Components as shown in Figure 4-6.

Figure 4-6 Windows Components Wizard

Tip: If you have the problems running usejdbc2.bat check if any Java applications are running. Stop the application and run usejdbc2.bat again.

100 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Select Management and Monitoring Tools and click Details (Figure 4-7).

Figure 4-7 SNMP install

Select Simple Network Management Protocol, and click OK. The installation program will prompt you for the installation CD or location where you have the installation files available.

After completing these steps we are ready to install the IBM Tivoli SAN Manager Server code.

4.2.6 Checking for the SNMP community nameAfter you have installed SNMP or anytime you apply a service pack or fix pack to Windows, you should check the SNMP community name. To do this:

1. Start -> Settings -> Control Panel -> Administrative Tools -> Services.

2. Right–click SNMP Service and select Properties (shown in Figure 4-8)

3. On the General tab, make sure the Startup type is Automatic.

4. On the Security tab, make sure the Community name is public with READ ONLY rights.

Chapter 4. Installation and setup 101

Figure 4-8 SNMP Service Properties panel

4.2.7 IBM Tivoli SAN Manager Server installThe IBM Tivoli SAN Manager Server muse be performed with a userid with Administrative rights — we used db2admin. Follow these steps to successfully install:

1. Run LAUNCH.EXE from the installation directory. Figure 4-9 shows the startup window.

Note: Embedded version of the IBM WebSphere Application Server – Express. The installation process automatically installs the embedded version of WebSphere — you do not have to install it separately. There are some differences between this embedded version and WebSphere Application Server, for example, you will no longer see the WebSphere Administrative Console, it uses less memory, and is easier to install and maintain.

Note: MQSeries is no longer included with (or used by) Tivoli SAN Manager.

102 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-9 Selecting the product to install

2. Select Manager and click Next to continue.

3. Select the language — for example, English and click OK. The Welcome window, shown in Figure 4-10, now displays.

Figure 4-10 Welcome window

4. Click Next to display the license agreement window. Read and accept the license and click Next to continue. You will be prompted for the directory to install Tivoli SAN Manager, shown in Figure 4-11.

Chapter 4. Installation and setup 103

Figure 4-11 Installation path

5. It is recommended that you accept the default directory. Click Next to continue, and the base port selection window will display, as in Figure 4-12.

Figure 4-12 Port range

6. The installation program requires seven consecutive free ports. You only need to define the starting port. In our example we used the default port 9550. Click Next to continue, and you will see the window shown in Figure 4-13.

104 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-13 DB2 admin user

On this window you need to specify the DB2 administrative userid and password. In our example we used db2admin.Click Next to continue and the window in Figure 4-14 displays.

Figure 4-14 SAN Manager database

Note: The database administration userid must exist before installing the IBM Tivoli SAN Manager Server.

Chapter 4. Installation and setup 105

7. Here you specify the name which will be used for the IBM Tivoli SAN Manager Server database, and a userid associated with this database.

This database stores the IBM Tivoli SAN Manager Server information which comes from outband and inband Agents. The DB2 administrator userid specified in the previous step will be used to create the userid entered on this window (db2user1 in our case), which will then be used to access the Server database.

After completing the fields, click Next to continue. The window in Figure 4-15 displays.

Figure 4-15 WebSphere Administrator password

8. Here you need to specify the userid for WebSphere Administration. This should be an existing system userid. In our example we entered wasadmin. Click Next to continue and you will see a window similar to Figure 4-16.

Tip: We recommend using a meaningful name for the database as this can simplify other operations related to the database such as administration and backups. We accepted the default name, ITSANMDB.

Attention: The userid which is specified here must be different from the database administration userid.

Tip: The WebSphere userid specified here must already exist on your system. In our sample we defined an ID, WASADMIN. The password used here should never expire on your system.

106 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-16 Host authentication password

9. Managed systems (Tivoli SAN Manager Agents) have to authenticate to the Server when they send data to it. For this reason, you need to supply an authentication password during installation. The same password will also be used during installation of Agents (see Step 6 on page 116) and Remote Consoles (Step 7 on page 123). After supplying the password, click Next to continue and you will see a window similar to Figure 4-17.

Figure 4-17 NetView install drive

10.Specify a drive letter for installing IBM Tivoli NetView. Click Next to continue and you will see the window in Figure 4-18.

Chapter 4. Installation and setup 107

Figure 4-18 NetView password

11.Here you specify the userid and password for running the NetView service. The installation program will create this userid if it does not exist. Click Next to continue, and the Tivoli SAN Manager Installation summary window, shown in Figure 4-19, will display.

Figure 4-19 Installation path and size

Note: This panel, and the next, will not display if Tivoli NetView Version 7.1.3 is already installed. This is the only version supported to work with IBM Tivoli SAN Manager Server.

108 IBM Tivoli Storage Area Network Manager: A Practical Introduction

12.On this window you can see the installation path which defaults to \tivoli\itsanm\manager and the size of the installed code. Click Next to continue and the installation will start, as shown in Figure 4-20.

Figure 4-20 Installation progress

13.After installation is complete, the window in Figure 4-21 appears.

Figure 4-21 Finished installation

14.Click Next to continue, and you will be prompted to reboot the system (required).

Chapter 4. Installation and setup 109

4.2.8 Verifying the installationAfter restarting the system, you should verify that the IBM Tivoli SAN Manager Server application is running correctly.

Check the SAN Manager service is running. The service can be started or stopped with the Service applet in Administrative Tools (shown in Figure 4-22). If it is not running, right-click the IBM WebSphere Application Server V5 – ITSANM–Manager entry and select Start.

Figure 4-22 Tivoli SAN Manager Windows Service

You should also check the HOSTS file which is modified by the Tivoli NetView installation. The entry shown in Example 4-2 was created in our environment.

Example 4-2 Tivoli NetView HOSTS file entry

## The following entry was created by NetView based on Registry information.#9.1.38.167 lochness lochness.almaden.ibm.com

Tivoli NetView checks the HOSTS file every time it starts and if this exact line is missing it will recreate the entry. This entry could have been inserted before the entry we made for long host name resolution as shown in Example 4-1 on page 98, meaning it takes precedence. To avoid this, check that the lines shown in Example 4-2 are at the end of the HOSTS file (moving them if necessary), so that it looks similar to Example 4-3.

Example 4-3 Correct HOSTS file order

9.1.38.167 lochness.almaden.ibm.com lochness9.1.38.166 senegal.almaden.ibm.com senegal9.1.38.150 bonnie.almaden.ibm.com bonnie127.0.0.1 localhost## The following entry was created by NetView based on Registry information.#9.1.38.167 lochness lochness.almaden.ibm.com

As you can see, the long host name entry precedes the Tivoli NetView entry.

Attention: Host names are case sensitive!

110 IBM Tivoli Storage Area Network Manager: A Practical Introduction

You should also check the log file after installation, which is found in the directory c:\tivoli\itsanm\manager\log\install\*.log. See Chapter 11, “Logging and tracing” on page 317 for more information on logging.

4.3 IBM Tivoli SAN Manager Server AIX installationIn this section we cover installation of the IBM Tivoli SAN Manager Server AIX installation.The installation steps are summarized in Figure 4-24.

Figure 4-23 Agent installation

4.3.1 Lab environmentIn our installation we used AIX 5.1 with ML4 installed.

4.3.2 Installation summary1) Install DB2

2) Upgrade DB2 with FixPak 8. You can get the fix pack from:

http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/report

3) Install Tivoli SAN Manager code

4.3.3 Starting and stopping the AIX manager� To start the service automatically, check the following line has been added to /etc/inittab:

itsanma:2:once://tivoli/itsanm/manager/bin/aix/startSANM.sh > /dev/console 2>&1

InstallationStatic IP required, seven contiguous free ports required

Fully qualified hostname required

Install DB2 7.2 and FP8

Upgrade DB2 JBDC drivers to version 2

Install the SNMP service (if not installed)

Install the Tivoli SAN Manager Server code : Embedded install of the IBM WebSphere Application Server V5.0 Tivoli SAN Manager Server

Important: The AIX installation is almost identical to the Windows installation as described in 4.2, “IBM Tivoli SAN Manager Windows Server installation” on page 96. The major difference is that since Tivoli NetView for AIX is not supported or installed, a separate Windows system with NetView and the remote console installed (as in 4.5, “IBM Tivoli SAN Manager Remote Console installation” on page 119), is required to view the console. Therefore the NetView screens do not appear in the AIX installation. All other installation steps are exactly the same.

Since the installation uses a GUI, an XWindows server session (either native or emulated) is required.

Chapter 4. Installation and setup 111

� To start the manager on AIX, run this command (using the default directory):

/tivoli/itsanm/manager/bin/aix/startSANM.sh

� To stop the manager on AIX, run this command (using the default directory):

/tivoli/itsanm/manager/bin/aix/stopSANM.sh

4.3.4 Checking the log filesAfter you install the manager, check the log /tivoli/itsanm/manager/mgrlog.txt for any errors.

If you find installation errors, check the other logs in the directory /tivoli/itsanm/manager/log/install/ to determine where the problems occurred.

4.4 IBM Tivoli SAN Manager Agent installationIn this section we cover the installation of the IBM Tivoli SAN Manager Agent on supported platforms. You can see a summary of the installation steps in Figure 4-24.

Figure 4-24 Agent installation

4.4.1 Lab environmentIn our lab environment we installed the Agent on the following operating systems:

� AIX 5.1 and 5.2� Solaris 8� Linux Red Hat Advanced 2.1 and SuSE SLES / 7� Windows 2000 Server with Fix Pack 3

4.4.2 Preinstallation tasksBefore starting installation you need to ensure that the following requirements are met.

Fully qualified host nameThe requirements for host name resolution are the same as for the IBM Tivoli SAN Manager Server Manager installation (described in “Fully qualified host name” on page 97) and four contiguous free ports.

4.4.3 IBM Tivoli SAN Manager Agent installIn this section we cover the installation of the IBM Tivoli SAN Manager Agent. The installation has to be performed by a userid with Administrative rights (Windows), or root authority (UNIX). Follow these steps for the installation:

InstallationFour contiguous free ports required

Fully qualified hostname required

Install the Agent code

Setup service to start automatically

112 IBM Tivoli Storage Area Network Manager: A Practical Introduction

1. Run the appropriate file from the agent subdirectory on the CD:

– AIX — ./setup.aix– Solaris — ./setup.sol– Linux — ./setup.lin– Windows — SETUP.EXE

As the installation program is Java based it will look the same on all platforms. Note that you need an XWindows session on all UNIX platforms to perform the installation.

You will first be prompted to select the language for installation. We chose English. Click Next to continue. You will then the Welcome window shown in Figure 4-25.

Figure 4-25 Welcome window

2. Click Next to display the license agreement. Read and accept the agreement, click Next and you will see a window similar to Figure 4-26.

Tips:

� You need 150 MB of free temporary disk space for installation.

� If the installation fails on a Windows system, restart the system so that the failed partial installation will be cleaned up before trying to reinstall the agent. Delete all files below the base installation directory c:\tivoli\itsanm\agent (Windows) or /tivoli/itsanm/agent (UNIX) before reinstalling.

� Before installing the agent on Linux, check the /etc/hosts file and enter the correct IP address in front of the hostname. Linux often automatically creates an entry with the loopback (127.0.0.1) address, which causes the agent to register itself at the IBM Tivoli SAN Manager server under this address and therefore cannot be contacted.

Chapter 4. Installation and setup 113

Figure 4-26 Installation directory

3. Here you can specify the installation directory or just accept the suggested one. Click Next to continue, you will see a window similar to Figure 4-27.

Figure 4-27 Server name and port

4. Enter the IBM Tivoli SAN Manager Server fully qualified host name and the first port number you defined during Server installation, (Step 5 on page 104). We specified 9550.

114 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Click Next to continue, and you will see the window shown in Figure 4-28.

Figure 4-28 Agent port

5. Here you need to specify the starting port for four consecutive ports to be used by the Agent. These ports should not be used by any other application. Click Next to continue, and you will see the window shown in Figure 4-29.

Important: The port number specified here must match the port number specified during Server install.

Chapter 4. Installation and setup 115

Figure 4-29 Agent access password

6. On this window you define the Agent access password which has to be the same as you defined during Server installation (Step 8 on page 106). Click Next — you will see the installation check window, as in Figure 4-30.

Figure 4-30 Installation size

7. This shows the installation directory and size. Click Next to start the installation. When complete, you will see the window in Figure 4-31. Click Finish to complete the installation.

116 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-31 Installation finished

8. Check the log file c:\tivoli\itsanm\agent\log.txt (Windows) or /tivoli/itsanm/agent/log.txt (UNIX) for any errors.

4.4.4 Configure the Agent service to start automaticallyWe recommend starting the Agent service automatically.

AIXThe Agent service is started by running the command tcstart.sh from the directory <install>/bin/aix. Stop the Agent service with tcstop.sh.

To start the service automatically, IBM Tivoli SAN Manager uses the BSD style rc.d directories on AIX. Since the default run-level is 2, it creates the needed start/stop scripts in /etc/rc/rc2.d. There are two scripts:

� S90itsrm_agent - starts the agent, when the run-level is entered (Example 4-4).� K90itsrm_agent - stops the agent, when the run-level is left.

Example 4-4 rc2.d start script: S90itsrm_agent used on AIX

#!/bin/sh

TSNM_DIR=/opt/tivoli/itsanm/agent/bin/aix

if [ -f "$TSNM_DIR/tcstart.sh" ] && [ -r "$TSNM_DIR/tcstart.sh" ] && [ -x "$TSNM_DIR/tcstart.sh" ]then $TSNM_DIR/tcstart.sh > $TSNM_DIR/../../log/S90_tcstart.log 2>&1 &# $TSNM_DIR/tcstart.sh > /dev/null &fi

Chapter 4. Installation and setup 117

SolarisThe Agent service is started by running the command tcstart.sh from the directory <install>/bin/solaris2. Stop the Agent service with tcstop.sh.

The installation program will create a startup script S90itsrm_agent in the directory /etc/rc/rc2.d. This will cause the Agent to start at boot time.

LinuxThe Agent service is started by running the command tcstart from the directory tivoli/itsanm/agent/bin/linux. Stop the Agent service with tcstop.

The installation program will create a startup script S90itsrm_agent in the directory /etc/rc/rc2.d and /etc/rc/rc3.d. This will cause the Agent to start at boot time.

WindowsThe service can be started or stopped with the Service applet in Administrative Tools. When you open the applet you will see the window in Figure 4-32.

Figure 4-32 Agent Windows service

The startup type should be set to Automatic, for the service to start automatically.

You can also use Command Line commands:

� To start — net start “ITSANM-Agent”� To stop — net stop “ITSANM-Agent”

118 IBM Tivoli Storage Area Network Manager: A Practical Introduction

4.5 IBM Tivoli SAN Manager Remote Console installationIn this section we cover installation of the IBM Tivoli SAN Manager Remote Console. The installation steps are shown in Figure 4-33.

Figure 4-33 Console installation

4.5.1 Lab environmentWe installed the Remote Console on a Windows 2000 Server with Fix Pack 3, called WISLA.

4.5.2 Preinstallation tasksBefore starting installation make sure that the following requirements are meet.

SNMP Service installedMake sure that you have installed the SNMP service and have an SNMP community name of Public defined, as described in 4.2.5, “Install the SNMP service” on page 100 and 4.2.6, “Checking for the SNMP community name” on page 101.

Fully qualified host nameThe requirements for the host name resolution are the same as for the IBM Tivoli SAN Manager Server installation described in “Fully qualified host name” on page 97. You also need six contiguous free ports.

Check for existing Tivoli NetView installationIf you have an existing Tivoli NetView 7.1.3 installation you can use it with IBM Tivoli SAN Manager Server installation. If you have any other version installed you must uninstall it before installing IBM Tivoli SAN Manager Console.

4.5.3 Installing the ConsoleThe IBM Tivoli SAN Manager Console remotely displays information about the monitored SAN. The installation must be performed by a userid with Administrative rights. The installation is at the time of writing supported on the Windows 2000 and Windows XP platforms. Follow these steps to successfully install the remote console:

InstallationSix contiguous free ports required

Fully qualified hostname required

Install the SNMP service (in not installed)

Install the Console code

Check if service started automatically

Correct the HOSTS file

Chapter 4. Installation and setup 119

If Tivoli NetView Version 7.1.3 is already installed, ensure these applications are stopped:

� Web Console� Web Console Security� MIB Loader� MIB Browser� Netmon Seed Editor� Tivoli Event Console Adaptor Configurator

1. Run LAUNCH.EXE from the installation directory. The selection window is shown in Figure 4-34.

Figure 4-34 Start the installation

2. Select Remote Console and click Next. The following window prompts you to select the language. We selected English. The Welcome window will display, shown in Figure 4-35.

Tips:

� You need 150 MB of free temporary disk space.

� If the installation fails, restart the system so that the failed partial installation will be cleaned up before trying to reinstall. Delete all files below the base installation directory c:\tivoli\itsanm\console before reinstalling.

Note: The Remote Console can be installed on an existing Agent system.

120 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-35 Welcome window

3. Click Next to continue, and the License window displays. Read and accept the license. Click Next to continue, and you will see a window similar to Figure 4-36.

Figure 4-36 Installation directory

4. Specify the installation directory, click Next, and the window shown in Figure 4-37 displays.

Chapter 4. Installation and setup 121

Figure 4-37 Server information

5. Specify the fully qualified host name of the Server and the Server port which you defined during Server installation (Step 5 on page 104). Click Next to continue with the installation, you will see a window similar to Figure 4-38.

Figure 4-38 Console ports

6. Specify the starting port of a six port range. This ports should not be in use by any other application. Click Next to continue, you will see a window similar to Figure 4-29.

122 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-39 Console access password

7. On this window you define the Console access password which has to be the same as you defined during Server installation Step 9 on page 107. Click Next to continue, you will see a window similar to Figure 4-40.

Figure 4-40 Tivoli NetView installation drive

8. As Tivoli NetView is part of the IBM Tivoli SAN Manager Console install you need to specify the drive letter where it will be installed. Click Next — you will see a window like Figure 4-41.

Chapter 4. Installation and setup 123

Figure 4-41 Tivoli NetView service password

9. Specify the userid and password to be used for the NetView service. The installation program will create this userid if it does not exist. Click Next to display the summary window (Figure 4-42)

Figure 4-42 Installation summary

Note: This panel and the next will not display if NetView Version 7.1.3 is already installed.

124 IBM Tivoli Storage Area Network Manager: A Practical Introduction

10.The summary window shows the selected directory and the size of the installation. Click Next to continue, and the installation will proceed. When it is complete, the window shown in Figure 4-42 displays.

Figure 4-43 Installation finished

11.Click Next to continue and Finish to finish installation. You need to restart the system after installation.

Check the log files c:\tivoli\itsanm\console\log.txt and c:\tivoli\itsanm\console\nv\log\* for any errors.

4.5.4 Check if the service started automaticallyAfter rebooting, should check that the IBM Tivoli SAN Manager Console service has started. Use the Services applet, as shown in Figure 4-44 and look for ITSANM-Console.

Figure 4-44 Console service

If the service was started successfully the status should be Started.

You also need to check the HOSTS file as the Tivoli NetView installation inserts lines similar to Example 4-5.

Chapter 4. Installation and setup 125

Example 4-5 Tivoli NetView entry

# # The following entry was created by NetView based on Registry information. # 9.1.38.169 wisla.almaden.ibm.com wisla

The long name must be resolved before the short name, therefore check there is a suitable long name entry before the lines made by Tivoli NetView, as shown in Example 4-6. Add or edit the line if necessary

Example 4-6 Corrected HOSTS file entry

9.1.38.169 wisla.almaden.ibm.com wisla

## The following entry was created by NetView based on Registry information.#9.1.38.169 wisla.almaden.ibm.com wisla

4.6 IBM Tivoli SAN Manager configurationNow we show the post-installation configuration of IBM Tivoli SAN manager. You can see the configuration steps in Figure 4-45.

Figure 4-45 Configuration steps

After installing the Server, Agent and the Console you need to set up the environment.

4.6.1 Configuring SNMP trap forwarding on devicesThere are several ways to configure Tivoli SAN Manager for SNMP traps.

Method 1: Forward traps to local Tivoli NetView consoleIn this scenario you setup the devices to send SNMP traps to the NetView console which is installed on the Tivoli SAN Manager Server. An example of this setup is shown in Figure 4-46.

Tip: Do not delete the Tivoli NetView entry, as it will be added every time you start IBM Tivoli SAN Manager Console.

Configuration and setupServer install

Agent install (optional)

Console install (optional)

Configuring SNMP trap forwarding on devices

Configuring the outband Agents

Check the inband Agents

Setting up the MIB file in Tivoli NetView

Perform initial poll and setup the poll interval

126 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-46 SNMP traps to local NetView console

NetView listens for SNMP traps on port 162 and the default community is public. When the trap arrives to the Tivoli NetView console it will be logged in the NetView Event browser and then forwarded to Tivoli SAN Manager as shown in Figure 4-47. Tivoli NetView is configured during installation of the Tivoli SAN Manager Server for trap forwarding to the IBM Tivoli SAN Manager Server.

Figure 4-47 SNMP trap reception

NetView forwards SNMP traps to the defined TCP/IP port, which is the sixth port derived from the base port defined during installation, shown in 4.2.7, “IBM Tivoli SAN Manager Server install” on page 102. We used the base port 9550, so the trap forwarding port is 9556.

With this setup, the SNMP trap information will appear in the NetView Event browser and SAN Manager will use it for changing the topology map.

Note: If the traps are not forwarded to SAN Manager, the topology map will be updated based on the information coming from Agents at regular polling intervals. The default IBM Tivoli SAN Manager Server installation (including NetView install) will set up the trap forwarding correctly.

SNMP

Disk array

Disk array

Disk array

Disk array

Disk array

Switch

SAN

Managed Host(Agent)

Managed Host(Agent)

Managed Host(Agent)

IBM Tiv oli Storage Area

NetworkManager

SNMP Trap

Tivoli NetView SAN ManagerTCP162

SAN Manager Server

fibre channel switchtrapfrwd.conf

(trap forwardingto TCP/IP port

9556)

Chapter 4. Installation and setup 127

Existing NetView installationIf you installed Tivoli SAN Manager with an existing NetView, you need to setup trap forwarding. To do this:

1. Configure the Tivoli NetView trapfrwd daemon. Edit the trapfrwd.conf file in the directory \usr\ov\conf. This file has two sections: Hosts and Traps. Modify the Hosts section to specify the host name and port to forward traps to (in our case, port 9556 on host LOCHNESS.ALMADEN.IBM.COM). Modify the Traps section to specify which traps Tivoli NetView should forward. The traps to forward for Tivoli SAN Manager are:

1.3.6.1.2 *(Includes MIB-2 traps (and McDATA ’s FC Management MIB traps)1.3.6.1.3 *(Includes FE MIB and FC Management MIB traps)1.3.6.1.4 *(Includes proprietary MIB traps (and QLogic ’s FC Management MIB traps))

Example 4-7 shows a sample trapfrwd.conf file.

Example 4-7 trapfrwd.conf file

[Hosts]#host1.tivoli.com 0#localhost 1662lochness.almaden.ibm.com 9556[End Hosts][Traps]#1.3.6.1.4.1.2.6.3 *#mgmt1.3.6.1.2 *#experimental1.3.6.1.3 *#Andiamo1.3.6.1.4.1.9524 *#Brocade1.3.6.1.4.1.1588 *#Cisco1.3.6.1.4.1.9 *#Gadzoox1.3.6.1.4.1.1754 *#Inrange1.3.6.1.4.1.5808 *#McData1.3.6.1.4.1.289 *#Nishan1.3.6.1.4.1.4369 *#QLogic1.3.6.1.4.1.1663 *[End Traps]

2. The trapfrwd daemon must be running before traps are forwarded. Tivoli NetView does not start this daemon by default. To configure Tivoli NetView to start the trapfrwd daemon, enter these commands at a DOS prompt:

ovaddobj \usr\ov\lrf\trapfrwd.lrfovstart trapfrwd

To verify trapfrwd is running, run Server Setup from the NetView Options menu, (Figure 4-48).

128 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-48 Trapfwd daemon

After trap forwarding is enabled, configure the SAN components such as switches to send their SNMP traps to the NetView console.

Method 2: Forward traps directly to Tivoli SAN Manager

In this example you configure the SAN devices to send SNMP traps directly to the Tivoli SAN Manager Server. The receiving port number is the primary port number plus six ports as described in “Method 1: Forward traps to local Tivoli NetView console” on page 126. In this case traps are only used to reflect the topology changes and they will not be shown in the NetView Event browser.

Note: This type of setup will give you the best results, especially for devices where you cannot change the number of SNMP recipients and the destination ports.

Note: Some of the devices do not allow changing the SNMP port — they will only send traps to port 162. In such cases this scenario is not useful.

Chapter 4. Installation and setup 129

Method 3: Forward traps to SAN Manager and separate SNMP consoleIn this example you setup the SAN devices to send SNMP traps to both the Tivoli SAN Manager Server and to a separate SNMP console (which you have installed in your organization) as shown in Figure 4-49.

Figure 4-49 SNMP traps for two destinations

The receiving port number for the Tivoli SAN Manager Server is the primary port number plus six ports as described in “Method 1: Forward traps to local Tivoli NetView console” on page 126. The receiving port number for the SNMP console is 162.

In this case traps are used to reflect the topology changes and they will also show in the SNMP console events. The SNMP console in this case could be another Tivoli NetView installation or any other SNMP management application.

For such a setup, the devices have to support setting multiple traps receivers and also changing the trap destination port. As this functionality is not supported in all devices this scenario is not recommended.

4.6.2 Configuring the outband agentsIBM Tivoli SAN Manager Server uses Agents to discover the storage environment and to monitor status. These Agents are setup in the Agent Configuration panel. Start this by selecting Configure Agents from the NetView console SAN menu, as shown in Figure 4-50.

Disk array

Disk array

Disk array

Disk array

Disk array

Switch

SAN

Managed Host(Agent)

Managed Host(Agent)

Managed Host(Agent)

IBM Tivoli Storage Area Network

Manager

SNMPConsoleport 162

130 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-50 Agent configuration

The configuration panel has two parts — for inband and outband agents. The outband Agents are defined in the bottom half of the panel. Here, you define all switches in the SAN you want to monitor. To define such an Agent, click Add and you will see a window as in Figure 4-51.

Figure 4-51 Outband Agent definition

Enter the host name or IP address of the switch and click OK to continue. The Agent will appear in the agent list as shown in Figure 4-50. The state of the Agent must be Contacted if you want IBM Tivoli SAN Manager to get data from it.

To remove an already defined Agent, select it and click Remove.

Defining logon ID for zone informationAt the time of writing, Tivoli SAN Manager can retrieve the zone information from IBM Fibre Channel Switches and from Brocade Silkworm Fibre Channel Switches. To accomplish this, Tivoli SAN Manager uses API calls to retrieve zoning information. To use this API, Tivoli SAN Manager has to login into the switch with administrative rights. If you wish to see zoning information you need to specify the login ID for the Agents you define. This can be done by

Chapter 4. Installation and setup 131

selecting the defined Agent and click Advanced (from the Configure Agents window shown in Figure 4-50). You will see a window like Figure 4-52.

Figure 4-52 Login ID definition

Enter the user name and password for the switch login and click OK to save. You will then be able to see zone information for your switches as described in “Zone view” on page 165.

4.6.3 Checking inband agentsAfter you have installed Agents on the managed systems (as described in 4.4.3, “IBM Tivoli SAN Manager Agent install” on page 112), they should appear in the Agent Configuration with Agent state of Contacted as shown in Figure 4-50. If the Agent does not appear in the panel check the Agent log file for the cause.

You can only remove Agents which are no longer responding to the Server. Such Agents will show a Not responding status, as shown in Figure 4-53.

Figure 4-53 Not responding inband agent

To remove such an Agent, select it and click Remove.

4.6.4 Performing initial poll and setting up the poll intervalAfter you have set up the Agents and devices for use with the SAN Manager Server, the initial poll will be performed. You can manually poll using the SAN Configuration panel, shown in Figure 4-54. To access this panel, select Configure Manager from the NetView SAN menu.

Tip: It is only necessary to enter ID and password information for one switch in each SAN to retrieve the zoning information. We recommend entering this information for at least two switches, however, for redundancy. Enabling more switches than necessary for API zone discovery may slow performance.

132 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-54 SAN configuration

Click Poll Now to perform a manual poll.

If you did not configure trap forwarding for the SAN devices, (as described in 4.6.1, “Configuring SNMP trap forwarding on devices” on page 126), you will need to define the polling interval. In this case, the topology change will not be event driven from the devices, but will be updated regularly at the polling interval.

You can setup the poll interval in the SAN Configuration (Figure 4-54). After specifying the poll interval click OK to save the changes. The polling interval can be specified in:

� Minutes� Hours� Days (you can specify the time of the day for polling)� Weeks (you can specify the day of the week and time of the day for polling)

4.7 Tivoli SAN Manager upgrade to Version 1.2In this section we describe how to upgrade IBM Tivoli SAN Manager components from Version 1.1 (or 1.1.1) to Version 1.2.

To preserve the existing database, you must specify the same database name, DB2 user ID and password that you specified when installing the previous version. These are the changes that occur when upgrading to IBM Tivoli Storage Area Network Manager V1.2:

� JVM 1.3.0 is upgraded to 1.3.1.

� NetView is upgraded from 7.1.1 to 7.1.3 (Windows manager and remote console).

� MQSeries is removed.

� WebSphere Application Server is replaced with Embedded WebSphere Application Server – Express, Version 5.0 on the manager.

Note: Polling takes time and is dependant on the size of the SAN.

Tip: You do not need to configure the polling interval if all your devices are set to send SNMP traps to either the local NetView console or the Tivoli SAN Manager Server.

Chapter 4. Installation and setup 133

4.7.1 Upgrading the Windows manager

To upgrade the Windows manager, do the following:

1. Login using the DB2 administrator ID.

2. If you have not installed DB2 FixPak 8, install it now. See 4.2.4, “Upgrading DB2 with Fix Pack 8” on page 99.

3. If Tivoli NetView 7.1.3 is installed, check these applications are stopped:

– Web Console– Web Console Security– MIB Loader– MIB Browser– Netmon Seed Editor– Tivoli Event Console Adaptor Configurator

4. Ensure Windows 2000 Terminal Services are not running.

5. Insert the Tivoli SAN Manager (Manager and Remote Console) CD into the CD–ROM drive. If Windows autorun is enabled, the installation program should start automatically. If it does not, double–click launch.exeo from the CD drive in Windows Explorer. The Launch panel will be displayed.

6. The installation process is the same as described in 4.2.7, “IBM Tivoli SAN Manager Server install” on page 102.

Follow the steps in the Tivoli Storage Area Network Manager Planning and Installation Guide, SC23-4697.

When the installation has completed, the Successfully Installed panel is displayed.

If the correct version of Tivoli NetView was installed before you installed the manager, you will see the Finish button. (Tivoli NetView will then not be installed with the manager.) If Tivoli NetView was not previously installed and is therefore installed with this installation of the manager, you will see a prompt to restart the system.

After rebooting, check the Tivoli SAN Manager service was started (Figure 4-22 on page 110).

4.7.2 Upgrading the remote consoleFollow these steps to upgrade the remote console:

1. Make sure that the following applications are stopped:

– Web Console– Web Console Security– MIB Loader– MIB Browser– Netmon Seed Editor– Tivoli Event Console Adaptor Configurator

Note: The DB2 default database name for Tivoli SAN Manager Version 1.1 was TIVOLSAN. The new name in Version 1.2 is ITSANMDB. If the database name and user ID and password are not the same as the previous installation, data will not be migrated, therefore, to retain your data, over-ride the default name with the previous database name (for example, TIVOLSAN).

134 IBM Tivoli Storage Area Network Manager: A Practical Introduction

2. Insert the Tivoli Storage Area Network Manager and Remote Console CD into the CD–ROM drive and double–click launch.exe.

3. Follow the steps in the Tivoli Storage Area Network Manager Planning and Installation Guide, SC23-4697.

The installation process will automatically update your NetView Version 7.1.1 to 7.1.3

After rebooting, check to see if the Tivoli SAN Manager console service was started (Figure 4-44 on page 125).

4.7.3 Upgrading the agentsThis section shows how to upgrade Tivoli SAN Manager agents

Run the appropriate setup script from the agent directory on the Agents CD. This is:

� setup.exe - Windows� ./setup.aix - AIX� ./setup.sol - Solaris

Follow the directions on the installation panels as described in the Tivoli Storage Area Network Manager Planning and Installation Guide, SC23-4697. The agent service is automatically started after installation.

4.8 Tivoli SAN Manager uninstallIn this section we describe how to uninstall IBM Tivoli SAN Manager components.

4.8.1 Tivoli SAN Manager Server Windows uninstallTo uninstall IBM Tivoli SAN Manager Server do the following:

1. Close all Tivoli NetView windows.

2. Go to the Add/Remove Programs applet in Control Panel, select IBM Tivoli Storage Area Network Manager - Manager and click Change/Remove as shown in Figure 4-55.

Figure 4-55 Uninstalling the SAN Manager Server

Chapter 4. Installation and setup 135

3. To complete the uninstallation process follow the instructions on the window. Restart the system after uninstallation completes.

4. Delete the directory c:\tivoli\itsanm.

5. If needed, uninstall DB2.

4.8.2 Tivoli SAN Manager Server AIX uninstallTo uninstall the manager, do the followings:

1. From the root directory, enter this command:

/tivoli/itsanm/manager/_uninst/uninstall

2. Follow the steps for Windows uninstallation (4.8.1, “Tivoli SAN Manager Server Windows uninstall” on page 135).

3. A reboot is not required unless you want to reuse the manager ports (9550–9556).

4.8.3 Tivoli SAN Manager Agent uninstallTo uninstall the Tivoli SAN Manager Agent on various platforms, do the following:

AIX or Solaris 1. Stop the Agent service with the command:

/tivoli/itsanm/agent/bin/tcstop.sh/tivoli/itsanm/agent/bin/solaris2/tcstop.sh

2. Check if the agent service is stopped with the command:

ps -aef | grep "java.*tsnm.baseDir"

If you do not see the entry in Example 4-8, the agent service has stopped:

Example 4-8 Output of ps -aef | grep "java.*tsnm.baseDir"

root 96498 158924 0 Aug 17 pts/3 24:53 /tivoli/itsanm/agent/jre/bin/java-Dtsnm.baseDir=/tivoli/itsanm/agent -Dtsnm.localPort=9570-Dtsnm.protocol=http:// -Djlog.noLogCmd=true -classpath /tivoli/itsanm/agent/lib/classes:/tivoli/itsanm/agent/servlet/common/lib/servlet.jar:/tivoli/itsanm/agent/lib/com.ibm.mq.jar:/tivoli/itsanm/agent/lib/com.ibm.mqjms.jar:/tivoli/itsanm/agent/lib/jms.jar:/tivoli/itsanm/agent/lib/ServiceManager.jar::/tivoli/itsanm/agent/servlet/bin/bootstrap.jar-Djavax.net.ssl.keyStore=/tivoli/itsanm/agent/conf/server.keystore-Djavax.net.ssl.keyStorePassword=YourServerKeystorePassword -Dcatalina.base=/tivoli/itsanm/agent/servlet -Dcatalina.home=/tivoli/itsanm/agent/servletorg.apache.catalina.startup.Bootstrap start

Note: This GUID package is not uninstalled when you uninstall IBM Tivoli Storage Area Network Manager. If you plan to reinstall IBM Tivoli Storage Area Network Manager, you should not delete the Tivoli GUID specific files and directories. This can cause IBM Tivoli Storage Area Network Manager to function improperly.

136 IBM Tivoli Storage Area Network Manager: A Practical Introduction

root 471386 448550 1 14:35:03 pts/4 0:00grep java.*tsnm.baseDir

3. Start the uninstallation with the command:

/tivoli/itsanm/manager/_uninst/uninstall

4. Follow the instructions on the screen to complete uninstallation.

Linux1. Stop the Agent service.

2. Start the uninstallation with the command:

/tivoli/itsanm/agent/_uninst/uninstall

3. Follow the instructions on the screen to complete uninstallation process.

WindowsTo uninstall the Windows Agent, select Control Panel -> Add/Remove Programs, select IBM Tivoli Storage Area Network Manager - Agent, and click Change/Remove (Figure 4-56).

Figure 4-56 Agent uninstall

To complete the uninstallation, follow the instructions on the window, and restart the system after uninstallation completes.

4.8.4 Tivoli SAN Manager Remote Console uninstallTo uninstall Tivoli SAN Manager Remote Console select Control Panel -> Add/Remove Programs, select IBM Tivoli Storage Area Network Manager - Console, and click Change/Remove as shown in Figure 4-57.

Chapter 4. Installation and setup 137

Figure 4-57 Uninstalling remote console

To complete uninstallation process follow the instructions on the window. Restart the system after uninstallation completes.

4.8.5 Uninstalling the Tivoli GUID packageThe Tivoli GUID (Global User D) package is used to resolve a computer’s identification. The GUID package gives a computer a global unique identifier. With this identifier the computer can be uniquely identified even if it is running multiple applications, for example IBM Tivoli SAN Manager Agent and IBM Tivoli Storage Manager Client.

You should only uninstall the Tivoli GUID if this would be the last Tivoli application using it and you want to have a clean computer.

To uninstall the Tivoli GUID on various platforms follow these steps.

AIXUninstall Tivoli GUID using SMIT or with the command:

installp -u tivoli.guid

SolarisUninstall Tivoli GUID with the command:

pkgrm TIVguid

WindowsChoose Control Panel -> Add/Remove Programs, select TivGuid, and click Change/Remove as shown in Figure 4-58.

Tip: Do not uninstall the Tivoli GUID package if you are running other Tivoli applications on the system.

138 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 4-58 Uninstalling Tivoli GUID

To complete the uninstallation process, follow the instructions on the window. Restart the system after uninstallation completes

4.9 Silent install of IBM Tivoli Storage Area Network ManagerIn this section we describe how to silently install IBM Tivoli SAN Manager components.

Before installing the manager, make sure you have done the pre-installation planning as outlined in IBM Tivoli Storage Area Network Manager Planning and Installation Guide, SC23-4697.

By modifying the appropriate parameters in the options file for the manager, remote console, or agent, you can then run the included script to install the components.

If you install IBM Tivoli Storage Area Network Manager silently, you must also uninstall it silently.

4.9.1 Silent installation high level stepsThe silent installation of all components (Manager, Agent and Console) is done by:

� Locating the sample option files on the installation media (manager.opt, agent.opt and console.opt) and copying them to local hard disk.

� Editing these files to reflect your environment. See 4.9.2, “Installing the manager” on page 140, 4.9.3, “Installing the agent” on page 142 and 4.9.4, “How to install the remote console” on page 144 for instructions.

� Launching the setup command in the following manner:

– Windows Agent - setup.exe -silent -options <path>\<option file>– AIX Agent - setup.aix -silent -options <path>/a<option file>– Linux Agent - setup.lin -silent <path>/<option file>– Solaris Agent - setup.sol -silent <path>/<option file>t

Chapter 4. Installation and setup 139

Where <option file> is manager.opt for the manager, agent.opt for the agent, and console.opt for the remote console.

4.9.2 Installing the managerBefore installing the manager, set the appropriate parameters in the options file manager.opt. Copy it from the CD to local disk to do this. See Example 4-9.

Example 4-9 Default manager silent installation options file

#########################################################################

# InstallShield Options File Template for Manager silent install## This file can be used to create an options file (i.e., response file) for the# wizard "Setup". Options files are used with "-options" on the command line to# modify wizard settings.## The settings that can be specified for the wizard are listed below. To use# this template, follow these steps:## 1. Specify a value for a setting by replacing the characters ’value’.# Read each settings documentation for information on how to specify its# value.## 2. Save the changes to the file.## 3. To use the options file with the wizard, specify -options filename# as a command line argument to the wizard, where filename is the name# of this options file.# example:# setup.exe -silent -options manager.opt################################################################################------------------------------------------------------------------------------# Select default language# Example:# -P defaultLocale="English"#------------------------------------------------------------------------------#-P defaultLocale="English"#------------------------------------------------------------------------------# Installation destination directory. Specify a valid directory into which the# product should be installed. If the directory contains spaces, enclose it in# double-quotes. For example, to install the product to C:\Program Files\My# Product in Windows, use# -P installLocation="C:\Program Files\My Product"# -P installLocation="C:/tivoli/itsanm/manager"# For Unix# -P installLocation="/tivoli/itsanm/manager"#-------------------------------------------------------------------------------P installLocation="C:/tivoli/itsanm/manager"#------------------------------------------------------------------------------# Base port number for this installation# Example:# -W portNoBean.portNumber=9550#-------------------------------------------------------------------------------W portNoBean.portNumber=9550#------------------------------------------------------------------------------# DB2 administrator user ID# Example:

140 IBM Tivoli Storage Area Network Manager: A Practical Introduction

# -W DBPassword.userID="db2admin"#-------------------------------------------------------------------------------W DBPassword.userID="db2admin"#------------------------------------------------------------------------------# DB2 administrator password## Example:# -W DBPassword.password="password"#-------------------------------------------------------------------------------W DBPassword.password="password"#------------------------------------------------------------------------------# Name of database to be created and used by SANM (SANM database)## Example:# -W SANPassword1.dbName="itsanmdb"#-------------------------------------------------------------------------------W SANPassword1.dbName="itsanmdb"#------------------------------------------------------------------------------# SANM database user ID, must be different than DB2 administrator user ID## Example:# -W SANPassword1.userID="db2user1"#-------------------------------------------------------------------------------W SANPassword1.userID="db2user1"#------------------------------------------------------------------------------# SANM database password# Example:# -W SANPassword1.userID="password"#-------------------------------------------------------------------------------W SANPassword1.password="db2user1"#------------------------------------------------------------------------------# Websphere user ID# Example:# -W WASPassword.userID="wasuser1"#-------------------------------------------------------------------------------W WASPassword.userID="wasadmin"#------------------------------------------------------------------------------# Websphere password for the user above# Example:# -W WASPassword.password="password"#-------------------------------------------------------------------------------W WASPassword.password="wasadmin"#------------------------------------------------------------------------------# Manager, Agent, Console communication password# Example:# -W comPassword.password="password"#-------------------------------------------------------------------------------W comPassword.password="itso_san_jose_pw"#------------------------------------------------------------------------------# Drive Letter where Netview to be installed.# Example:# -W beanNVDriveInput.chcDriveName="C"#-------------------------------------------------------------------------------W beanNVDriveInput.chcDriveName="C"#------------------------------------------------------------------------------# Netview password.# Example:# -W beanNetViewPasswordPanel.password="password"#-------------------------------------------------------------------------------W beanNetViewPasswordPanel.password="netview"

Chapter 4. Installation and setup 141

#------------------------------------------------------------------------------# Property use by installation program. Do not remove or modify.#-------------------------------------------------------------------------------W setWinDestinationBean.value="$P(installLocation)"

� Specify the installation destination directory.

– Windows:

-P installLocation="C:/tivoli/itsanm/manager"

– UNIX:

-P installLocation="/opt/tivoli/itsanm/manager"

� Specify the DB2 administrator user ID

-W DBPassword.userID="db2admin"

� Specify the drive letter where Tivoli NetView will be installed

-W beanNVDriveInput.chcDriveName="C"

� Specify DB2 database name

-W SANPassword1.dbName="itsanmdb"

� Specify password for db2user1

-W SANPassword1.password="xxxxxxx"

� Specify WebSphere admin user

-W WASPassword.userID="wasadmin"

� Specify WebSphere admin password

-W WASPassword.password="xxxxxxx"

� Specify communication password

-W comPassword.password="xxxxxxx"

� Specify NetView admin password

-W beanNetViewPasswordPanel.password="xxxxxxx"

4.9.3 Installing the agent

Before installing the agent, set the appropriate parameters in the options file agent.opt. Copy it from the CD to local disk to do this (Example 4-10).

Example 4-10 Default agent silent installation option file

################################################################################ InstallShield Options File Template for Agent silent install## This file can be used to create an options file (i.e., response file) for the# wizard "Setup". Options files are used with "-options" on the command line to# modify wizard settings.## The settings that can be specified for the wizard are listed below. To use# this template, follow these steps:## 1. Specify a value for a setting by replacing the characters ’value’.# Read each settings documentation for information on how to specify its

Note: This procedure accepts forward or backward slashes for directory paths on a Windows platform.

142 IBM Tivoli Storage Area Network Manager: A Practical Introduction

# value.## 2. Save the changes to the file.## 3. To use the options file with the wizard, specify -options filename# as a command line argument to the wizard, where filename is the name# of this options file.# example:# setup.exe -silent -options agent.opt##################################################################################------------------------------------------------------------------------------# Select default language# Example:# -P defaultLocale="English"#------------------------------------------------------------------------------#-P defaultLocale="English"#------------------------------------------------------------------------------# Installation destination directory:## The install location of the product. Specify a valid directory into which the# product should be installed. If the directory contains spaces, enclose it in# double-quotes. For example, to install the product to C:\Program Files\My# Product in Windows, use# -P installLocation="C:\Program Files\My Product"# -P installLocation="C:/tivoli/itsanm/agent"# For Unix# -P installLocation="/tivoli/itsanm/agent"#-------------------------------------------------------------------------------P installLocation="c:/tivoli/itsanm/agent"#------------------------------------------------------------------------------# Specify full qualified name of remote manager machine:# Example:# -W managerNamePort.managerName="manager.sanjose.ibm.com"#-------------------------------------------------------------------------------W managerNamePort.managerName="manager.sanjose.ibm.com"#------------------------------------------------------------------------------# Specify base port number of remote manager:# Example:# -W managerNamePort.managerPort=9550#-------------------------------------------------------------------------------W managerNamePort.managerPort=9550#------------------------------------------------------------------------------# Base port number for this installation# Example:# -W portNoBean.portNumber=9570#-------------------------------------------------------------------------------W portNoBean.portNumber=9570#------------------------------------------------------------------------------# Manager, Agent, Console communication password# Example:# -W comPassword.password="password"#-------------------------------------------------------------------------------W comPassword.password="itso_san_jose_pw"#------------------------------------------------------------------------------# Property use by installation program. Do not remove or modify.#-------------------------------------------------------------------------------W setWinDestinationBean.value="$P(installLocation)"

Chapter 4. Installation and setup 143

� Specify the hostname of the manager machine

-W managerNamePort.managerName="lochness.sanjose.ibm.com"

� Specify a password for manager, agent, and console communication

-W comPassword.password="xxxxxxx"

4.9.4 How to install the remote consoleBefore installing the console, set the appropriate parameters in the options file console.opt. Copy it from the CD to local disk to do this (see Example 4-11).

Example 4-11 Remote console default silent install option file

################################################################################ InstallShield Options File Template for Remote Console silent install# This file can be used to create an options file (i.e., response file) for the# wizard "Setup". Options files are used with "-options" on the command line to# modify wizard settings.## The settings that can be specified for the wizard are listed below. To use# this template, follow these steps:## 1. Specify a value for a setting by replacing the characters ’value’.# Read each settings documentation for information on how to specify its# value.## 2. Save the changes to the file.## 3. To use the options file with the wizard, specify -options filename# as a command line argument to the wizard, where filename is the name# of this options file.# example:# setup.exe -silent -options console.opt################################################################################------------------------------------------------------------------------------# Select default language# Example:# -P defaultLocale="English"#------------------------------------------------------------------------------#-P defaultLocale="English"#------------------------------------------------------------------------------# Installation destination directory.## The install location of the product. Specify a valid directory into which the# product should be installed. If the directory contains spaces, enclose it in# double-quotes. For example, to install the product to C:\Program Files\My# Product in Windows, use# -P installLocation="C:\Program Files\My Product"# -P installLocation="C:/tivoli/itsanm/console"#-------------------------------------------------------------------------------P installLocation="c:/tivoli/itsanm/console"#------------------------------------------------------------------------------# Specify full qualified name of remote manager machine:# Example:# -W beanManagerLocation.HostName="manager.sanjose.ibm.com"#-------------------------------------------------------------------------------W beanManagerLocation.HostName="lochness.almaden.ibm.com"#------------------------------------------------------------------------------# Specify base port number of remote manager:# Example:

144 IBM Tivoli Storage Area Network Manager: A Practical Introduction

# -W beanManagerLocation.PortNo=9550#-------------------------------------------------------------------------------W beanManagerLocation.PortNo=9550#------------------------------------------------------------------------------# Base port number for this installation# Example:# -W portNoBean.portNumber=9560#-------------------------------------------------------------------------------W portNoBean.portNumber=9560#------------------------------------------------------------------------------# Manager, Agent, Console communication password# Example:# -W comPassword.password="password"#-------------------------------------------------------------------------------W comPassword.password="itso_san_jose_pw"#------------------------------------------------------------------------------# Drive Letter where Netview to be installed.# Example:# -W beanNVDriveInput.chcDriveName="C"#-------------------------------------------------------------------------------W beanNVDriveInput.chcDriveName="C"#------------------------------------------------------------------------------# Netview password.# Example:# -W beanNetViewPasswordPanel.password="password"#-------------------------------------------------------------------------------W beanNetViewPasswordPanel.password="netview"

� Specify the fully qualified name of the remote manager machine

-W beanManagerLocation.HostName="lochness.almaden.ibm.com"

� Specify a password for manager, agent, and console communication

-W comPassword.password="xxxxxx"

� Specify the password for Tivoli NetView

-W beanNetViewPasswordPanel.password="xxxxxxx"

4.9.5 Silently uninstalling IBM Tivoli Storage Area Network ManagerThis section describes how to uninstall IBM Tivoli Storage Area Network Manager if you have installed the product using silent installation.

Uninstalling the manager on WindowsTo uninstall the manager on Windows, from the installation directory, run the following command:

c:\tivoli\itsanm\manager\_uninst\uninstall -silent

Uninstalling the manager on AIX To uninstall the AIX manager, from the installation directory, run this command:

/tivoli/itsanm/manager/_uninst/uninstall -silent

Uninstalling the remote console To uninstall the remote console, run this command from the installation directory:

c:\tivoli\itsanm\console\_uninst\uninstall -silent

Chapter 4. Installation and setup 145

Uninstalling the agentsTo uninstall the Windows agent, from the installation directory, run this command:

c:\tivoli\itsanm\agent\_uninst\uninstall -silent

To uninstall the UNIX agent, from the installation directory, run this command:/tivoli/itsanm/agent/_uninst/uninstall -silent

4.10 Changing passwordsIf you need to change any of the passwords used during the installation process, you should use the procedures described in Table 4-1.

Table 4-1 Procedure to change passwords

UserID/Password

ID/PasswordUsed afterSoftware getsinstalled?

Change of IDallowed?

Change ofPasswordallowed?

How to change User ID/Password?

db2admin No N/A Yes, recommended for security reasons

Change password from the Computer Management Administrative tool.

db2user Yes No Yes 1. Change password from the Computer Management Administrative tool.2. Use following procedure to change password stored inside ITSANM properties file:srmcp ConfigService setPW

Was Admin Yes Yes Yes 1. Change User ID/Password from following file <Install_Location>/apps/was/properties/soap.client.props Modify following entries.com.ibm.SOAP.loginUserid=<User_ID>com.ibm.SOAP.loginPassword=<PASSWORD> Where you need to replace <User_ID> or <PASSWORD>2.Scripts are available from IBM Support for AIX and Windows - contact your local support structure to get them.

NetView password

Yes N/A Yes, recommended for security reasons

1. Change password from the Computer Management Administrative tool.2. Change Logon Password for “Tivoli NetView Service” from Control Panel/Services

146 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Host Authentication Password

Yes N/A Yes, recommended for security reason

1. Change password from the Computer Management Administrative tool.2. Use following procedure to change password stored inside ITSANM properties file.srmcp ConfigService setAuthenticationPw

UserID/Password

ID/PasswordUsed afterSoftware getsinstalled?

Change of IDallowed?

Change ofPasswordallowed?

How to change User ID/Password?

Chapter 4. Installation and setup 147

148 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 5. Topology management

In this chapter we provide an introduction to the features of IBM Tivoli SAN Manager. We discuss the following topics:

� IBM Tivoli NetView navigation overview

� Lab environment description

� Physical and logical topology views:

– SAN view– Host centric view– Device centric view– iSCSI view– MDS 9000

� Object status and properties

� Launch of management applications

� Practical cases

5

© Copyright IBM Corp. 2002, 2003. All rights reserved. 149

5.1 NetView navigation overviewSince Tivoli SAN Manager uses IBM Tivoli NetView (abbreviated as NetView) for display, before going into further details, we give you a basic overview of the NetView interface, how to navigate in it and how IBM Tivoli SAN Manager integrates with NetView. Detailed information on NetView is in the redbook Tivoli NetView V6.01 and Friends, SG24-6019.

5.1.1 NetView interfaceNetView uses a graphical interface to display a map of the IP network with all the components and interconnect elements that are discovered in the IP network. As your Storage Area network (SAN) is a network, Tivoli SAN Manager uses NetView and its graphical interface to display a mapping of the discovered storage network.

5.1.2 Maps and submapsNetView uses maps and submaps to navigate in your network and to display deeper details as you drill down. The main map is called the root map while each dependent map is called a submap. Your SAN topology will be displayed in the Storage Area Network submap and its dependents. You can navigate from one map to its submap simply by double-clicking the element you want to display.

5.1.3 NetView window structureFigure 5-1 shows a basic NetView window.

Figure 5-1 NetView window

submapstack

child submap area

submap window

150 IBM Tivoli Storage Area Network Manager: A Practical Introduction

The NetView window is divided in three parts:

� The submap window displays the elements included in the current view. Each element can be another submap or a device

� The submap stack is located on the left side of the submap window. This area displays a stack of icons representing the parent submaps that you have already displayed. It shows the hierarchy of submaps you have opened for a particular map. This navigation bar can be used to go back to a higher level with one click

� The child submap area is located at the bottom of the submap window. This submap area shows the submaps that you have previously opened from the current submap. You can open a submap from this area, or bring it into view if it is already opened in another window on the window.

5.1.4 NetView ExplorerFrom the NetView map based window, you can switch to an Explorer view where all maps, submaps and objects are displayed in a tree scheme (similar to the Microsoft Windows Explorer interface). To switch to this view, right-click a submap icon and select Explore as shown in Figure 5-2.

Figure 5-2 NetView Explorer option

Figure 5-3 shows the new display using the NetView Explorer.

Chapter 5. Topology management 151

Figure 5-3 NetView explorer window

From here, you can change the information displayed on the right pane by changing to the Tivoli Storage Area Network Manager view on the top pull-down field. The previously displayed view was System Configuration view. The new display is shown in Figure 5-4.

Figure 5-4 NetView explorer window with Tivoli Storage Area Network Manager view

Now, the right pane shows Label, Name, Type and Status for the device. You may scroll right to see additional fields.

152 IBM Tivoli Storage Area Network Manager: A Practical Introduction

5.1.5 NetView Navigation TreeFrom the any NetView window, you can switch to the Navigation Tree by clicking the tree icon circled on Figure 5-5.

Figure 5-5 NetView toolbar

NetView will display, with a tree format, all the objects contained in the maps you have already explored. Figure 5-6 shows the tree view.

Figure 5-6 NetView tree map

You can see that our SAN — circled in red — does not show its dependent objects since we have not yet opened this map through the standard NetView navigation window.

You can click any object and it will open its submap in the standard NetView view.

5.1.6 Object selection and NetView propertiesTo select an object, right-click it. NetView displays a context-sensitive menu with several options including Object Properties as shown in Figure 5-7.

Chapter 5. Topology management 153

Figure 5-7 NetView objects properties menu

The Object Properties for that device will display (Figure 5-8). This will allow you to change NetView properties such as the label and icon type of the selected object.

Figure 5-8 NetView objects properties

Important: As IBM Tivoli SAN Manager runs its own polling and discovery processes and only uses NetView to display the discovered objects, each change to the NetView object properties will be lost as soon as IBM Tivoli SAN Manager regenerates a new map.

154 IBM Tivoli Storage Area Network Manager: A Practical Introduction

5.1.7 Object symbolsIBM Tivoli SAN Manager uses its own set of icons as shown in Figure 5-9. Two new icons have been added for Version 1.2 - ESS and SAN Volume Controller.

Figure 5-9 IBM Tivoli SAN Manager icons

5.1.8 Object statusThe color of a symbol or the connection represents its status. The colors used by IBM Tivoli SAN Manager and their corresponding status are shown in the following table.

Table 5-1 IBM Tivoli SAN Manager symbols color meaning

IBM Tivoli NetView uses additional colors to show the specific status of the devices, however these are not used in the same way by IBM Tivoli SAN Manager.

Table 5-2 IBM Tivoli NetView additional colors

If you suspect problems in your SAN, look in the topology displays for icons indicating a status of other than normal/green. To assist in problem determination, Table 5-3 provides an overview of symbol status with possible explanations of the problem.

Symbol color Connection color Status Status meaning

Green Black Normal The device was detected in at least one of the scans

Green Black New The device was detected in at least one of the scans and a new discovery has not yet been performed since the device was detected

Yellow Yellow Marginal (suspect) Device detected - the status is impaired but still functional

Red Red Missing None of the scans that previously detected the device are now reporting it

Symbol color Status Status Meaning

Blue Unknown Status not determined

Wheat (tan) Unmanaged The device is no longer monitored for topology and status changes.

Dark green Acknowledged The device was Missing, Suspect or Unknown. The problem has been recognized and is being resolved

Gray (used in NetView Explorer left pane)

Unknown Status not determined

Chapter 5. Topology management 155

Table 5-3 Problem determination

Display Agents Device Link Non-ISL explanation

ISL explanation

Any Normal (green)

Marginal (yellow)

One or more, but not all links to the device in this topology are missing.

One or more, but not all links between the two switches is missing

Any Normal (green)

Critical (red)

All links to the device in this topology are missing, while other links to this device in other topologies are normal.

All links between the two switches are missing, but the out-of-band communication to the switch is normal

Any Critical (red)

Critical (red)

All links to the device in this topology are missing, while all other links to devices in other topologies are missing (if any)

All links between the two switches are missing, and the out-of-band communication to the switch is missing or indicates that the switch is in critical condition

Both Critical (red)

Normal (black)

All in-band agents monitoring the device can no longer detect the device. For example, a server reboot, power-off, shutdown of agent service, Ethernet problems, and soon.

This condition should not happen. If you see this on an ISL where switches on either side of the link have an out-of-band agent connected to your SAN Manager, then you are having problems with your out-of-band agent.

Both Critical (red)

Marginal (yellow)

At least one link to the device in this topology is normal and one or more links are missing. In addition, all in-band agents monitoring the device can no longer detect the device

This condition should not happen. If you see this on an ISL where switches on either side of the link have an out-of-band agent connected to your SAN Manager, then you are having problems with your out-of-band agent.

156 IBM Tivoli Storage Area Network Manager: A Practical Introduction

5.1.9 Status propagationEach object has a color representing its status. If the object is an individual device, the status shown is that of the device. If the object is a submap, the status shown reflects the summary status of all objects in its child submap. Status of lower level objects is propagated to the higher submap as shown in Table 5-4.

Table 5-4 Status propagation rules

5.1.10 NetView and IBM Tivoli SAN Manager integrationIBM Tivoli SAN Manager adds a new SAN menu entry in the IBM Tivoli NetView interface, shown in Figure 5-10. The SAN pull-down menu contains the following entries:

� SAN Properties to display and change object properties, such as object label and icon� Launch Application to run a management application � ED/FI Properties to view ED/FI events� ED/FI Configuration to start, stop, and configure ED/FI� Configure Agents to add and remove agents� Configure Manager to configure the polling and discovery scheduling� Set Event Destination to configure SNMP and TEC events recipients� Storage Resource Manager to launch IBM Tivoli Storage Resource Manager � Help

Object status Symbols in the child submap

Unknown No symbols with status of normal, critical, suspect or unmanaged

Normal All symbols are normal or acknowledged

Suspect (marginal) All symbols are suspect orNormal and suspect symbols orNormal, suspect and critical symbols

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

Chapter 5. Topology management 157

Figure 5-10 SAN Properties menu

All those items will subsequently be described in more detail.

5.2 Lab 1 environment descriptionFor demonstration purposes in the following sections, we call this lab lab1. We had the following equipment:

� Two IBM 2109-S08 (ITSOSW1 and ITSOSW2) switches with firmware V2.6.0c

� One IBM 2109-S16 (ITSOSW3) switch with firmware V2.6.0c

� One IBM 2109-F16 (ITSOSW4) switch with firmware V3.0.2

� One IBM 2107-G07 SAN Data Gateway

� One IBM pSeries F50 (BRAZIL) running AIX 4.3.3 ML10 with:

– One IBM 6227 card with firmware 02903291

� One IBM pSeries F80 (SICILY) running AIX 5.1.1 ML2 with:

� Two IBM 6227 cards with firmware 02903291

� One IBM pSeries 6F0 (CRETE) running AIX 4.3.3 ML10 with:

– One IBM 6228 card with firmware 02C03891

� One Sun Enterprise 250 (SOL-E) running Sun Solaris 8 with:

– Two JNI FCI-1063 cards with driver 2.6.11

� Three IBM xSeries 330 (LEAD, RADON, POLONIUM) with:

– One QLogic QLA2200 card with firmware 8.1.5.12

� One IBM xSeries 330 (TUNGSTEN) with:

– Two QLogic QLA2200 card with firmware 8.1.5.12

158 IBM Tivoli Storage Area Network Manager: A Practical Introduction

� One IBM xSeries 330 (GALLIUM) with:

– Two QLogic QLA2300 card with firmware 8.1.5.12

� One IBM Ultrium Scalable Tape Library (3583)

� One IBM TotalStorage FAStT700 storage server

Figure 5-11 shows the SAN topology of our lab environment.

Figure 5-11 ITSO lab1 setup

We also set up various zones within the switch — Figure 5-12 shows these. Note that this is an initial configuration which changed throughout various testing scenarios — examples shown in this book may not represent this exact configuration.

Lab topologyLab topology

BRAZIL

LEAD

BONNIE CLYDE DIOMEDE SENEGAL

CRETE

TUNGSTEN

MSS

FAStT700

SDG

ITSOSW4

ITSOSW3

ITSOSW1 ITSOSW2

LTO 3583

GALLIUMSOL-E SICILY

Chapter 5. Topology management 159

Figure 5-12 ITSO lab1 topology with zones

5.3 Topology viewsThe standard IP-based IBM Tivoli NetView root map contains IP Internet and SmartSets submaps. IBM Tivoli SAN Manager adds a third submap, called Storage Area Network, to allow the navigation through your discovered SAN. Figure 5-13 shows the NetView root map with the addition of IBM Tivoli SAN Manager.

Lab topology with zonesLab topology with zones

BONNIECLYDE DIOMEDE SENEGAL

TUNGSTEN

MSS

ITSOSW4

ITSOSW3

ITSOSW2

SW3 ITSOSW3ALLPORTS

SW1-SW2 TSM

SW4 FAStT

SW1-SW2 FAStT

SW3 MSS

Switches zoning

SOL-E SICILY GALLIUM BRAZIL

FAStT700

LTO 3583

SDG

CRETE

LEADITSOSW1

160 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-13 IBM Tivoli NetView root map

The Storage Area Network submap (shown in Figure 5-14) displays an icon for each available topology view. There will be a SAN view icon for each discovered SAN fabric (three in our case), a Device Centric View icon, and a Host Centric View icon.

Figure 5-14 Storage Area Network submap

Chapter 5. Topology management 161

You can see in this figure that we had three fabrics. They are named Fabric1, Fabric3, and Fabric4, since we have changed their label using SAN -> SAN Properties as explained in “Properties” on page 171.

Figure 5-15 shows the complete list of views available. In the following sections we will describe the content of each view.

Figure 5-15 Topology views

5.3.1 SAN viewThe SAN view allows you to see the SAN topology at the fabric level. In this case we clicked the Fabric1 icon shown in Figure 5-14. The display in Figure 5-16 appears, giving access to two further submaps:

� Topology view� Zone view

Figure 5-16 Storage Area Network view

Tivoli NetView root map

Storage Area Network

SAN view

Topology view

Switches

Elements

Interconnect elements

Elements (switches)

Zone view

Zones

Elements

Device Centric view

Devices

(storage servers)

LUNs

Host

Platform

Host Centric view

Hosts

Platform

Filesystems

Volumes

Topology viewsTopology views

162 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Topology viewThe topology view is used to display all elements of the fabric including switches, hosts, devices, and interconnects. As shown on Figure 5-17, this particular fabric has two switches.

Figure 5-17 Topology view

Now, you can click a switch icon to display all the hosts and devices connected to the selected switch.

Figure 5-18 Switch submap

Chapter 5. Topology management 163

On the Topology View (shown in Figure 5-17) you can also click Interconnect Elements to display information about all the switches in that SAN.

Figure 5-19 Interconnect submap

The switch submap, (Figure 5-18), shows that six devices are connected to switch ITSOSW1. Each connection line represents a logical connection. Click a connection bar twice to display the exact number of physical connections (Figure 5-20).

We now see that, for this example, SOL-E is connected to two ports on the switch ITSOSW1.

Figure 5-20 Physical connections view

164 IBM Tivoli Storage Area Network Manager: A Practical Introduction

When the connection represents only one physical connection (or, if we click one of the two connections shown in Figure 5-20), NetView displays its properties panel (Figure 5-21).

Figure 5-21 NetView properties panel

Zone viewThe Zone view submap displays all zones defined in the SAN fabric. Our configuration contains two zones called FASTT and TSM.

Figure 5-22 Zone view submap

Chapter 5. Topology management 165

Click twice on the FASTT icon to see all the elements included in the FASTT zone.

Figure 5-23 FASTT zone

In lab1, the FASTT zone contains five hosts and one storage server. We have installed Tivoli SAN Manager Agents on the four hosts that are labelled with their correct hostname (BRAZIL, GALLIUM, SICILY and SOL-E). For the fifth host, LEAD, we have not installed the agent. However, it is discovered since it is connected to the switch. IBM Tivoli SAN Manager displays it as a host device, and not as an unknown device, because the QLogic HBA drivers installed on LEAD support RNID. This RNID support gives the ability for the switch to get additional information, including the device type (shown by the icon displayed), and the WWN. The disk subsystem is shown with a question mark because the FAStT700 was not yet fully supported (with the level of code available at the time of writing) and IBM Tivoli SAN Manager was not able to determine all the properties from the information returned by the inband and outband agents.

5.3.2 Device Centric ViewYou may have several SAN fabrics with multiple storage servers. The Device Centric View (accessed from the Storage Area Network view, as shown in Figure 5-14 on page 161), displays the storage devices connected to your SANs and their relationship to the hosts. This is a logical view as the connection elements are not shown. Because of this, you may prefer to see this information using the NetView Explorer interface as shown in Figure 5-24. This has the advantage of automatically displaying all the lower level items for Device Centric View listed in Example 5-15 on page 162 simultaneously, such as LUNs and Host.

166 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-24 Device Centric View

In the preceding figure, we can see the twelve defined LUNs and the host to which they have been allocated. The dependency tree is not retrieved from the FAStT server but is consolidated from the information retrieved from the managed hosts. Therefore, the filesystems are not displayed as they can be spread on several LUNs and this information is transparent to the host. Note that the information is also available for the MSS storage server, the other disk storage device in our SAN.

5.3.3 Host Centric ViewThe Host Centric View (accessed from the Storage Area Network view, as shown in Figure 5-14 on page 161) displays all the hosts in the SAN and their related local and SAN-attached storage devices. This is a logical view that does not show the interconnect elements (and runs across the fabrics). Since this is also a logical view, like the Device Centric View, the NetView Explorer presents a more comprehensive display (Figure 5-25).

Chapter 5. Topology management 167

Figure 5-25 Host Centric View for Lab 1

We see our four hosts and all their local filesystems whether they are locally or SAN-attached. NFS-mounted filesystems and shared directories are not displayed. Since no agent is running on LEAD, it is not shown in this view.

5.3.4 iSCSI discoveryFor this environment we will reference SAN Lab 2 (“Lab 2 environment” on page 190).

Starting discoveryYou can discover and manage devices that use the iSCSI storage networking protocol through IBM Tivoli SAN Manager using IBM Tivoli NetView. Before discovery, SNMP and the iSCSI MIBs must be enabled on the iSCSI device, the Tivoli NetView IP Discovery must be enabled. See 6.4, “Real-time reporting” on page 227 for enabling IP discovery.

The IBM Tivoli NetView nvsniffer daemon will discover the iSCSI devices. Depending on the iSCSI operation chosen, a corresponding iSCSI SmartSet will be created under the IBM Tivoli NetView SmartSets icon. By default, the nvsniffer utility runs every 60 minutes. Once nvsniffer discovers a iSCSI device, it creates an iSCSI SmartSet located on the NetView Topology map at the root level.

The user can select what type of iSCSI device is discovered. From the menu bar, click Tools -> iSCSI Operations menu and select Discover All iSCSI Devices, Discover All iSCSI Initiators or Discover All iSCSI Targets, as shown in Figure 5-26.

For more details about iSCSI, refer to Chapter 7, “Tivoli SAN Manager and iSCSI” on page 253.

168 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-26 iSCSI discovery

Double-click the iSCSI SmartSet icon to display all iSCSI devices.

Once all iSCSI devices are discovered by NetView, the iSCSI SmartSet can be managed from a high level. Status for iSCSI devices is propagated to the higher level, as described in 5.1.9, “Status propagation” on page 157. If you detect a problem, drill to the SmartSet icon and continue drilling through the iSCSI icon to determine what iSCSI device is having the problem. Figure 5-27 shows an iSCSI SmartSet.

Figure 5-27 iSCSI SmartSet

5.3.5 MDS 9000 discoveryThe Cisco MDS 9000 is a family of intelligent multilayer directors and fabric switches that have such features as: virtual SANs (VSANs), advanced security, sophisticated debug analysis tools and an element manager for SAN management.

IBM Tivoli SAN Manager has enhanced compatibility for the Cisco MDS 9000 Series switch. Tivoli NetView displays the port numbers in a format of SSPP, where SS is the slot number and PP is the port number. The Launch Application menu item is available for the Cisco switch. When the Launch Application is selected, the Cisco Fabric Manager application is started. For more details, see 5.7.1, “Cisco MDS 9000 discovery” on page 182.

Chapter 5. Topology management 169

5.4 SAN menu optionsIn this section we describe some of the menu options contained under the SAN pull-down menu option for IBM Tivoli SAN Manager.

5.4.1 SAN PropertiesAs shown in Figure 5-28, select an object and use SAN -> SAN Properties to display the properties gathered by IBM Tivoli SAN Manager. In this case we are selecting a particular filesystem (the root filesystem) from the Agent SOL-E.

Figure 5-28 SAN Properties menu

This will display a SAN Properties window that is divided into two panes. The left pane always contains Properties, and may also contain Connection and Sensors/Events, depending on the type of object being displayed. The right pane contains the details of the object.

These are some of the device types that give information in the SAN Properties menu:

� Disk drive� Hdisk� Host file system� LUN� Log volume� OS� Physical volume� Port� SAN

170 IBM Tivoli Storage Area Network Manager: A Practical Introduction

� Switch� System� Tape drive� Volume group� Zone

PropertiesThe first grouping item is named Properties and contains generic information about the selected device. The information that is displayed depends on the object type. This section shows at least the following information:

� Label: The label of the object as it is displayed by IBM Tivoli SAN Manager. If you update this field, this change will be kept over all discoveries.

� Icon: The symbol representing the device type. If the object is of an unknown type, this field will be in read-write mode and you will be able to select the correct symbol.

� Name: The reported name of the device.

Figure 5-29 shows the Properties section for a filesystem. You can see that it displays the filesystem name and type, the mount point, and both the total and available space. Since a filesystem is not related to a port connection and also does not return sensor events, only the Properties section is available.

Figure 5-29 IBM Tivoli SAN Manager Properties — Filesystem

Figure 5-30 shows the Properties section for a host. You can see that it displays the hostname, the IP address, the hardware type, and information about the HBA. Since the host does not give back sensor related events, only the Properties and Connections sections are available.

Chapter 5. Topology management 171

Figure 5-30 IBM Tivoli SAN Manager Properties — Host

Figure 5-31 shows the Properties section for a switch. You can see that it displays fields including the name, the IP address, and the WWN. The switch is a connection device and sends back information about the events and the sensors. Therefore, all three item groups are available (Properties, Connections, and Sensors/Events).

Figure 5-31 IBM Tivoli SAN Manager Properties — Switch

172 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-32 shows the properties for an unknown device. Here you can change the icon to a predefined one by using the pull-down field Icon. You can also change the label of a device even if the device is of a known type.

Figure 5-32 Changing icon and name of a device

ConnectionThe second grouping item, Connections shows all ports in use for the device. This section appears only when it is appropriate to the device displayed — switch or host.

On Figure 5-33, we see the Connection tab for one switch where six ports are used. Port 0 is used for the Inter-Switch Link (ISL) to switch ITSOSW2. This is a very useful display, as it shows which device is connected on each switch port.

Figure 5-33 Connection information

Sensors/EventsThe third grouping item, Sensors/Events, is shown in Figure 5-34. It shows the sensors status and the device events for a switch. It may include information about fans, batteries, power supplies, transmitter, enclosure, board, and others.

Chapter 5. Topology management 173

Figure 5-34 Sensors/Events information

5.5 Application launchMany SAN devices have vendor-provided management applications. IBM Tivoli SAN Manager provides a launch facility for many of these.

5.5.1 Native supportFor some supported devices, IBM Tivoli SAN Manager will automatically discover and launch the device-related administration tool. To launch, select the device and then click SAN -> Launch Application.

This will launch the Web application associated with the device. In our case, it launches the Brocade switch management Web interface for the switch ITSOSW4, shown in Figure 5-35.

174 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-35 Brocade switch management application

5.5.2 NetView support for Web interfacesFor devices that have not identified their management application, IBM Tivoli NetView allows you to manually configure the launch of a Web interface for any application, by doing the following:

� Right-click the device and select Object Properties from the context-sensitive menu. � On the dialog box, select the Other tab (shown in Figure 5-36).� Select LANMAN from the pull-down menu.� Check isHTTPManaged.� Enter the URL of the management application in the Management URL field.� Click Verify, Apply, OK.

Chapter 5. Topology management 175

Figure 5-36 NetView objects properties — Other tab

After this, you can launch the Web application by right-clicking the object and then selecting Management Page, as shown in Figure 5-37.

Figure 5-37 Launch of the management page

Important: This definition will be lost if your device is removed from the SAN and subsequently rediscovered, since it will be a new object for NetView.

176 IBM Tivoli Storage Area Network Manager: A Practical Introduction

5.5.3 Non-Web applicationsYou can also configure the NetView toolbar menu to launch a locally installed management application from the NetView console. Here we show you how to configure NetView to launch the management application for the IBM SAN Data Gateway. You can use the same procedure for any other application that is installed on the NetView server.

1. Create a file in the directory \usr\ov\registration\c\. You can call it anything with a .REG extension, for example, here, SanDG.reg. Insert the lines shown in Example 5-1. If you have other management applications to insert, create different .REG files in the same directory, as NetView will automatically scan this directory for extra items.

Example 5-1 File to enable launch of non-Web application from NetView console

Application "SDG Specialist"{ Description {

"SDG Specialist" }

Command "C:\\Program Files\\IBM StorWatch\\IBM ClientLaunch.exe"; MenuBar "Tools"

{ <55> "SDG Specialist"_G f.action "aSDG";

}Action "aSDG" {

Command "C:\\Program Files\\IBM StorWatch\\IBM ClientLaunch.exe";}

}

2. Stop NetView

3. To be sure that the application can be automatically launched, update the PATH variable on your server and add the path to the program directory.

� My Computer -> Properties, select the Advanced tab -> Environment Variables. � Under System Variables, select PATH.� Include the full pathname of the application in the PATH variable (Figure 5-38).

Figure 5-38 PATH environment variable

4. Re-start NetView.

After this, you will be able to launch the SAN Data Gateway application by selecting it from the Tools menu as shown in Figure 5-39.

Chapter 5. Topology management 177

Figure 5-39 NetView Tools menu

This will launch the SAN Data Gateway Specialist application (Figure 5-40).

Figure 5-40 San Data Gateway specialist

Note: The application must be locally installed on the server where the NetView console runs (either IBM Tivoli SAN Manager Server or Remote Console).

178 IBM Tivoli Storage Area Network Manager: A Practical Introduction

5.5.4 Launching IBM Tivoli Storage Resource ManagerThe IBM Tivoli Storage Resource Manager interface can be started by using Tivoli SAN Manager’s NetView console. To do this, select SAN -> Storage Resource Manager, as shown in Figure 5-41.

Figure 5-41 Launch Tivoli Storage Resource Manager

The user properties file contains an SRMURL setting that defaults to the fully qualified host name of Tivoli Storage Area Network Manager. This default assumes that both Tivoli Storage Resource Manager and Tivoli Storage Area Network Manager are installed on the same machine. If IBM Tivoli Storage Resource Manager is installed on a separate machine, you can modify the SRMURL value to specify the host name of the IBM Tivoli Storage Resource Manager machine. For instructions on how to do this, please refer to the manual IBM Tivoli Storage Area Network Manager User’s Guide, SC23-4698.

If the following conditions are true, you can start the Tivoli Storage Resource Manager graphical interface from the Tivoli NetView console:

� IBM Tivoli Storage Resource Manager or the Tivoli Storage Resource Manager graphical interface is installed on the same machine as Tivoli Storage Area Network Manager, or the SRMURL value specifies the hostname of IBM Tivoli Storage Resource Manager.

� The Tivoli Storage Area Network Manager is currently running.

For more information on Tivoli Storage Resource Manager, please see the redbook IBM Tivoli Storage Resource Manager: A Practical Introduction, SG24-6886.

5.5.5 Other menu optionsFor the other options on the SAN pull-down menu, Configure Agents is covered in 4.6.2, “Configuring the outband agents” on page 130 and 4.6.3, “Checking inband agents” on page 132, Configure Manager is discussed in 4.6.4, “Performing initial poll and setting up the poll interval” on page 132, Set Event Destination is covered in Chapter 8, “SNMP Event notification” on page 259, and ED/FI Properties and ED/FI Configuration are covered in Chapter 9, “ED/FI - SAN Error Predictor” on page 267.

Chapter 5. Topology management 179

5.6 Status cyclesFigure 5-42 shows the typical color change status cycles which reflect normal operation as a device goes down and comes up. Table 5-1 and Table 5-2 on page 155 list the meanings of the different colors.

Figure 5-42 IBM Tivoli SAN Manager — normal status cycle

If you do not manually use NetView capabilities to change status, the status of a Tivoli SAN Manager object goes from green to red and from red to green.

Note that the only difference between an object in the NORMAL/GREEN and NEW/GREEN status is in the Status field under SAN Properties (see Figure 5-30 on page 172 for an example). A new object will have New in the field and a normal object will show Normal. The icon displayed in the topology map will look identical in both cases.

You can encounter situations where your device is down for a known reason such as an upgrade or hardware replacement and you don’t want it displayed with a missing/red status. You can use the NetView Unmanage function to set its color as tan to avoid having the yellow or red status reported and propagated in the topology display. See Figure 5-43.

NEWGREEN

NORMALGREEN

MISSINGRED

Clear History

Device down

Device down

Device up

180 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-43 Status cycle using Unmanage function

However, when a device is unmanaged and you do a SAN -> Configure Manager -> Clear History to remove historical data, the missing device will be removed from the IBM Tivoli SAN Manager database and will no longer be reported until it is up back with a new/green status. If you have changed the label of the device, and it is re-discovered after a Clear History, it will reappear with the default generated name, as this information is not saved. See Figure 5-44.

Figure 5-44 Status cycle using Acknowledge function

You can use the NetView Acknowledge function to specify that you have been notified about the problem and that you are currently searching for more information or for a solution. This will set the device’s color as dark green to avoid having the yellow or red status reported and propagated in the topology display. Subsequently, you can use the Unacknowledge function to return in the normal status and colors cycle. When the device becomes available, it will automatically return to the normal reporting cycle.

IBM Tivoli SAN Manager status cycle (with Unmanage)IBM Tivoli SAN Manager status cycle (with Unmanage)

NORMALGREEN

MISSINGRED

Device down

NORMALTAN

MISSINGTAN

Manage / Unmanage

Manage / Unmanage

NOT DISCOVERED / NOT DISPLAYEDClear History

Clear History

Device up

IBM Tivoli SAN Manager status cycle (with Acknowledge)IBM Tivoli SAN Manager status cycle (with Acknowledge)

Ack/Unack

NORMALGREEN

MISSINGRED

MISSINGDARK GREEN

Device down

Device up

Chapter 5. Topology management 181

5.7 Practical casesWe have re-created some typical errors that can happen in a production environment to see how and why IBM Tivoli SAN Manager reacts to them.

We have also used different configurations of the inband and outband agents and correlated the results with the explanations in 3.8, “Deployment scenarios” on page 76.

5.7.1 Cisco MDS 9000 discoveryIn this section we discuss the discovery of the Cisco MDS 9509, which is part of the MDS 9000 family. Our MDS 9509 is a multilayer switch/director with a 6 slot configuration. We have one 16 port card and one 32 port card running at 2GB/s.

Discovery of the MDS 9509 is performed using inband management. See 3.6.1, “Inband management” on page 68.

See Figure 5-45 for the lab environment used to demonstrate the following discovery. We will call this lab environment 3.

Figure 5-45 Lab environment 3

We first deployed an IBM Tivoli SAN Manager Agent to SANAN. Once the agent was installed, it registered with the IBM Tivoli SAN Manager - LOCHNESS and discovered the CISCO1 (MDS 9509). The topology in Figure 5-46 was displayed after deploying the agent.

Sanxc1

SananITSANM Agent

LochnessSAN Manager

Intranet

Sanxc2

Sanan3

Cisco 9509

182 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-46 Discovery of MDS 9509

To display the properties of CISCO1, right-click the CISCO1 icon to select it and select SAN -> SAN Properties. See Figure 5-47.

Note: In order to discover the MDS 9000, at least one IBM Tivoli SAN Manager Agent must be installed on a host attached to the MDS 9000. Outband management is not supported for the MDS 9000.

Chapter 5. Topology management 183

Figure 5-47 MDS 9509 properties

The Connection option (Figure 5-48) displays information about the slots and ports where the hosts SANXC1, SANXC2 and SANXC3 are connected, as well as the status of each port.

Figure 5-48 MDS 9509 connections

5.7.2 Removing a connection on a device running an inband agentNext, we started with the configuration as shown in 5.2, “Lab 1 environment description” on page 158. We removed the FC link between the host SICILY and the switch ITSOSW1. IBM Tivoli SAN Manager does not show that the device is missing but shows that the connection is missing. As the host was running an in-band management agent, the host continues to report its configuration to the manager using the IP network. However, the attached switch sends a trap to the manager to signal the loss of a link. You can use Monitor -> Events -> All to view the trap received by NetView. Double-click the trap coming from ITSOSW1 to see details about the trap as shown in Figure 5-49.

184 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-49 Trap received by NetView

We see that ITSOSW1 sent a trap to signal that FCPortIndex4 (port number 3) has a status of 2 (which means Offline).

The correlation between the inband information and the trap received is then made correctly and only the connection is shown as missing. You can see in Figure 5-50 that the connection line has turned red, using the colors referenced in Table 5-1 on page 155.

Figure 5-50 Connection lost

We then restored the connection, and following the status cycle explained in Figure 5-42 on page 180, the connections returned to normal.

Chapter 5. Topology management 185

Figure 5-51 Connection restored

Next, we removed one out of the two connections from the host TUNGSTEN to ITSOSW3. One link is lost, so the connection is now shown as suspect (yellow) – Figure 5-52.

Figure 5-52 Marginal connection

NetView follows its status propagation rules in Table 5-4 on page 157. This connection links to a submap with the two physical connections. The bottom physical connection is missing (red), and the other (top) one is normal (black), resulting is propagated status of (yellow) on the parent map (left hand side). See Figure 5-53.

186 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-53 Dual physical connections with different status

5.7.3 Removing a connection on a device not running an agentA device with no agent is only detected via its connection to the switch. If the connection is broken, the host cannot be discovered. In this case, we unplugged the FC link between the host LEAD and the switch ITSOSW2. LEAD is not running either an inband or an outband agent — as we can see using SAN -> Agents configuration, shown in Figure 5-54.

Chapter 5. Topology management 187

Figure 5-54 Agent configuration

After removing the link on LEAD and we received a standard Windows missing device popup (Figure 5-55) indicating it could no longer see its FC-attached disk device.

Figure 5-55 Unsafe removal of Device

IBM Tivoli SAN Manager shows the device as Missing (the icon changes to red — see the color status listing in Table 5-1 on page 155) — as it is no longer able to determine the status of the device. See Figure 5-56.

188 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-56 Connection lost on a unmanaged host

In Figure 5-57, the host is Unmanaged (tan) status since we decided to unmanage it.

Figure 5-57 Unmanaged host

We finally select SAN -> Configure Manager -> Clear History. See Figure 5-58.

Chapter 5. Topology management 189

Figure 5-58 Clear History

After the next discovery, as explained in Figure 5-43 on page 181, the host is no longer displayed (Figure 5-59), since it has been removed from the IBM Tivoli SAN Manager database.

Figure 5-59 NetView unmanaged host not discovered

5.7.4 Powering off a switchIn this test we power off a SAN switch and observe the results.

Lab 2 environmentFor demonstration purposes in the following sections, this lab is referenced as Lab 2. The configuration consists of:

� Two IBM 2109-S08 (ITSOSW1 and ITSOSW2) switches with firmware V2.6.0g

� One IBM 2109-S16 (ITSOSW3) switch with firmware V2.6.0g

190 IBM Tivoli Storage Area Network Manager: A Practical Introduction

� One IBM 2109-F16 (ITSOSW4) switch with firmware V3.0.2

� One IBM 2107-G07 SAN Data Gateway

� Two pSeries 620 (BANDA, KODIAK) running AIX 5.1.1 with :

– Two IBM 6228 cards

� One IBM pSeries F50 (BRAZIL) running AIX 5.1.1ML4 with:

– One IBM 6227 card with firmware 02903291– One IBM 6228 card with firmware 02C03891

� One HP Server running HP-UX 11.0

– One FC HBA

� Four Intel® servers (TONGA, PALAU, WISLA, LOCHNESS)

� Two Intel servers (DIOMEDE, SENEGAL) with:

– Two QLogic QLA2200 card with firmware 8.1.5.12

� One IBM xSeries 5500 (BONNIE) with:

– Two QLogic QLA2300 card with firmware 8.1.5.12

� One IBM Ultrium Scalable Tape Library (3583)

� One IBM TotalStorage FAStT700 storage server

Figure 5-11 shows the SAN topology of our lab environment.

Figure 5-60 SAN lab - environment 2

palau- Win2k Srv sp3

fastT700

NAS 200

PO WERFAUL T DATA AL AR M

sw4

sw1

sw3

iSCSI

Easter - HPUX11

sw2

Senegal - Win2k Srv sp3

brazil - AIX 5.1

diomede- Win2k Srv sp3

lochness Win2k Srv sp3SAN Manager

wisla - Win2k Srv sp3

SDG

LTO 3583

Kodiak - AIX5.1

bonnie - Win2k Srv sp3

clyde - Win2k Srv sp3

banda - AIX 5.1

tonga - Win2k Srv sp3

Chapter 5. Topology management 191

We have powered off the switch ITSOSW4, with managed host SENEGAL enabled. The topology map reflects this as shown in Figure 5-61. The switch and all connections change to red.

Figure 5-61 Switch down Lab 2

The agent running on the managed host (SENEGAL) has scanners listening to the HBAs located in the host. Those HBAs detect that the attached device, ITSOSW4, is not active since there is no signal from ITSOSW4. The information is retrieved by the scanners and reported back to the manager through the standard TCP/IP connection. Since the switch is not active, the hosts can no longer access the storage servers.

The active agent (SENEGAL) sends the information to the manager which triggers a new discovery. Since the switch does no longer responds to outband management, IBM Tivoli SAN Manager will correlate all the information and as a result, the connections between the managed hosts and the switch, and the switch itself, are shown as red/missing. The storage server is shown as green/normal because of a second fibre channel connection to ITSOSW2. ITSOSW2 is also green/normal because of the outband management being performed on this switch.

The active agent host is still reported as normal/green as it sends its information to the Manager through the TCP/IP network. Therefore the Manager can determine that only the agent’s switch connections, not the host itself, is down.

Now, we powered the switch on again. At startup, the switch sends a trap to the manager. This trap will cause the manager to ask for a new discovery. The result is shown in Figure 5-62.

192 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-62 Switch up Lab 2

Now, following the status propagation detailed in 5.6, “Status cycles” on page 180, all the devices are green/normal.

5.7.5 Running discovery on a RNID-compatible deviceAs explained in 3.6.1, “Inband management” on page 68, when you define a host for inband management, the topology scanner will launch inband queries to all attached HBAs. The remote HBAs, if they support RNID, will send back information such as device type. On switch ITSOSW2 (refer to 5.2, “Lab 1 environment description” on page 158), is a Windows host, CLYDE, with a QLogic card at the requested driver level. There is no agent installed on this host. We see however that it is discovered as a host rather than as an Unknown device, as shown in Figure 5-63, because of the HBA RNID support.

Chapter 5. Topology management 193

Figure 5-63 RNID discovered host

You can see under the SAN Properties window, Figure 5-64, that the RNID support only provides the device type (Host) and the WWN. Compare with the SAN Properties window for a managed host, shown in Figure 5-30 on page 172.

Figure 5-64 RNID discovered host properties

To have a more explicit map, we put CLYDE in the Label field (using the method shown in Figure 5-32 on page 173) and the host is now displayed with its new label.

194 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-65 RNID host with changed label

5.7.6 Outband agents onlyPlease refer to 5.2, “Lab 1 environment description” on page 158 for this section.

To see what happens if there are only outband agents, that is, with no IBM Tivoli SAN Manager agents running, we stopped all the running inband agents, cleared the IBM Tivoli SAN Manager configuration, by using SAN -> Configure Agent -> Remove button, and then re-configured the outband agents on the switches ITSOSW1, ITSOSW2, and ITSOSW4 as shown in Figure 5-66.

Chapter 5. Topology management 195

Figure 5-66 Only outband agents

When configuring the agents, we also used the Advanced button to enter the administrator userid and password for the switches. This information is needed by the scanners to obtain administrative information such as zoning for Brocade switches.

IBM Tivoli SAN Manager discovers the topology by scanning the three registered switches. This is shown in Figure 5-67. The information about the attached devices is limited to the WWN of the device since this information is retrieved from the switch and there is no other inband management. Note the ‘-’ signs next to Device Centric and Host Centric Views — this information is retrieved only by the inband agent so is not available to us here.

196 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-67 Explorer view with only outband agents

Figure 5-68 shows the information retrieved from the switches (SAN Properties).

Figure 5-68 Switch information retrieved using outband agents

5.7.7 Inband agents onlyThis section uses the lab described in 5.2, “Lab 1 environment description” on page 158.

For this practical case, we first unplugged all Fibre Channel connections from all agents and we removed all the outband agents from the configuration using SAN -> Configure Agents -> Remove tab. We then forced a new poll. As expected, the agents returned only information

Chapter 5. Topology management 197

about the node and the local filesystems, shown in Figure 5-69. Note the ‘-’ sign in front of /data01 for host SICILY. The filesystem is defined but not mounted, as the Fibre Connections are not active.

Figure 5-69 Inband agents only without SAN connections

We reconnected the Fibre Channel connections to all agents into the switch and forced a new polling. We now see that all agents reported information about their filesystems. Since the agents are connected to a switch, the inband agents will retrieve information from it using inband management. That explains why we see all the devices including those without agents installed. Figure 5-70 shows that:

� Our four inband agents (BRAZIL, GALLIUM, SICILY, SOL-E) are recognized.

� The two switches ITSOSW1 and ITSOSw2 are found, since agents are connected to them.

� Device 1000006045161FF5 is displayed since it is connected to the switch ITSOSW1. The device type is Unknown, as there is no inband nor outband agent on this device.

198 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-70 Inband agents only with SAN connections

We can also display SAN Properties as shown in Figure 5-71.

Figure 5-71 Switches sensor information

We now have no zoning information available since this is retrieved from the switch outband Agent for the 2109 switch. This is indicated by the — sign next to Zone View on Figure 5-70.

Chapter 5. Topology management 199

5.7.8 Disk devices discoveryThis section uses the lab described in 5.2, “Lab 1 environment description” on page 158.

We explained in 3.6.1, “Inband management” on page 68, how the topology scanner will launch inband queries to all attached HBAs. The Attribute scanner will then do a SCSI request to get attribute information about the remote devices. Due to LUN masking, the storage server will deny all requests if there are no LUNs defined for the querying host. Figure 5-72 shows how our SAN topology is mapped when there is an IBM MSS storage server but with no LUNs defined or accessible for the hosts in the same fabric. The storage server is shown as an Unknown device because the inband agents were not allowed to do SCSI requests to the storage servers as they had no assigned LUNs.

Figure 5-72 Discovered SAN with no LUNS defined on the storage server

Figure 5-73 shows that the host CRETE is not included in the MSS zone (we have enabled the outband agent for the switch in order to display zone information). This zone includes TUNGSTEN, which has no LUNs defined on the MSS.

200 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-73 MSS zoning display

We changed the MSS zone to include the CRETE server. We run cfgmgr on CRETE so that it scans its configuration and finds the disk located on the MSS as shown in Example 5-2.

Example 5-2 cfgmgr to discover new disks

# lspvhdisk0 00030cbf4a3eae8a rootvghdisk1 00030cbf49153cab Nonehdisk2 00030cbf170d8baa datavghdisk3 00030cbf170d9439 datavg# cfgmgr# lspvhdisk0 00030cbf4a3eae8a rootvghdisk1 00030cbf49153cab Nonehdisk2 00030cbf170d8baa datavghdisk3 00030cbf170d9439 datavghdisk4 00030cbf8c071018 None

Now, the agent on CRETE is able to run SCSI commands on the MSS and discovers that it is a storage server. IBM Tivoli SAN Manager maps it correctly in Figure 5-74.

Chapter 5. Topology management 201

Figure 5-74 MSS zone with CRETE and recognized storage server

5.7.9 Well placed agent strategyThis section uses the lab described in 5.2, “Lab 1 environment description” on page 158.

The placement of inband and outband agents will determine the information displayed:

� For a topology map, you need to define inband and outband agents on some selected servers and switches in order to discover all your topology. Switch zoning and LUN masking may restrict access to some devices.

� For a complete topology map, including correct device icons, you need to define inband and outband on all servers and switches, except on those supporting RNID.

� For information on zones, you need to define the switches as outband agents and set the user ID and password on the Advanced properties.

� For a complete Device Centric and Host Centric views, you need to place inband agents on all servers you want to be displayed.

Before implementing inband and outband agents, you should have a clear idea of your environment and the information you want to collect. This will help you to select the agents and may minimize overhead caused by inband and outband agents.

In our configuration, we decided to place one agent on GALLIUM which is connected to the two fabrics and has LUNs assigned on the FAStT storage server.

202 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 5-75 “Well-placed” agent configuration

The agent will use inband management to:

� Query the directly attached devices.

� Query the name server of the switches to get the list of other attached devices.

� Launch inband management to other devices to get their WWN and device type (for RNID compatible supported drivers).

� Launch SCSI request to get LUN information from storage servers.

You can see in Figure 5-76 that the agent on GALLIUM has returned information on:

� Directly attached switches (ITSOSW1 and ITSOSW4)� Devices attached to those switches (if they are in the same zones)� LUNs defined on the FAStT for this server� Its own filesystems

Because of the other hosts, only CLYDE runs with RNID compatible drivers, all other devices — excluding switches and FAStT storage server — are displayed with an unknown device icon. However, we have shown how we can get a complete map of our SAN by deploying just one inband agent.

Chapter 5. Topology management 203

Figure 5-76 Discovery process with one well-placed agent

5.8 Summary This chapter provided an overview of Tivoli NetView navigation. We discussed the physical and logical topologies and practical cases when using IBM Tivoli SAN Manager. Topology views of iSCSI and MDS 9000 devices were also presented.

204 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Part 4 Advanced operations

In Part 4 we present more operational concepts. This includes functions to provide:

� Historical and real-time SAN device reporting

� Error prediction

� Integration of IBM Tivoli SAN Manager with other SNMP management applications

Part 4

© Copyright IBM Corp. 2002, 2003. All rights reserved. 205

206 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 6. NetView Data Collection, reporting, and SmartSets

In this chapter we describe how to use the NetView program’s predefined performance applications and how to create your own applications to monitor the Storage Area Network performance. The NetView program helps you manage performance by providing several ways to track and collect fibre channel MIB objects. You can use performance information in any of the following ways:

� Monitoring the network for signs of potential problems� Resolving network problems� Collecting information for trend analysis� Allocating network resources� Planning future resource acquisition

The data collected by the NetView program is based on the values of MIB objects. The NetView program provides applications that display performance information:

� NetView Graph displays MIB object values in graphs.� Other NetView tools display MIB object values in tables or forms.

6

© Copyright IBM Corp. 2002, 2003. All rights reserved. 207

6.1 OverviewThe NetView MIB Tool Builder enables you to create applications that collect, display, and save real-time MIB data. The MIB Data Collector provides a way to collect and analyze historical MIB data over long periods of time to give you a more complete picture of your network’s performance. We will explain the SNMP concepts and standards, demonstrate the creation of Data Collections and the use of the MIB Tool Builder as it applies to SAN network management.

Figure 6-1 lists the topics we cover in this overview section.

Figure 6-1 Overview

6.1.1 SNMP and MIBsThe Simple Network Management Protocol (SNMP) has become the de facto standard for internetwork (TCP/IP) management. Because it is a simple solution, requiring little code to implement, vendors can easily build SNMP agents for their products. SNMP is extensible, allowing vendors to easily add network management functions to their existing products. SNMP also separates the management architecture from the architecture of the hardware devices, which broadens the base of multi vendor support. SNMP is widely implemented and available today.

SNMP network management system contains two primary elements:

� Manager — This is the console through which the network administrator performs network management functions.

� Agents — These are the entities that interface to the actual device being managed. Switches and directors are examples of managed devices that contain managed objects

NetView Reporting OverviewNetView Reporting Overview

Understanding SNMP and MIBs

ConfiguringMIBs (copying and loading)

IBM 2109

NetView

MIB Data Collector

MIB Tool Builder

NetView Graphing tool

Important:

� Currently IBM Tivoli NetView does not support the querying of SNMP V2 MIBs with the MIB Tool Builder and the Data Collection utilities.

� In our configuration, the SNMP manager is NetView and the SNMP agents are IBM 2109 Fibre Channel Switches.

208 IBM Tivoli Storage Area Network Manager: A Practical Introduction

These objects are arranged in what is known as the Management Information Base (MIB). SNMP allows managers and agents to communicate for the purpose of accessing these objects. Figure 6-2 provides an overview of the SNMP architecture.

Figure 6-2 SNMP architecture overview

A typical SNMP manager performs the following tasks:

� Queries agents � Gets responses from agents � Sets variables in agents � Acknowledges asynchronous events from agents

A typical SNMP agent performs the following tasks:

� Stores and retrieves management data as defined by the MIB� Signals an event to the manager

MIBs supported by NetViewNetView supports the following types of MIBs:

� Standard MIB: All devices that support SNMP are also required to support a standard set of common managed object definitions, of which a MIB is composed. The standard MIB object definitions, MIB-I and MIB-II, enable you to monitor and control SNMP managed devices. Agents contain the intelligence required to access these MIB values.

� Enterprise-specific MIB: SNMP permits vendors to define MIB extensions, or enterprise-specific MIBs, specifically for controlling their products. These enterprise-specific MIBs must follow certain definition standards, just as other MIBs must, to ensure that the information they contain can be accessed and modified by agents. The NetView program provides the ability to load enterprise-specific MIBs from a MIB description file. By loading a MIB description file containing enterprise-specific MIBs on an SNMP management station, you can monitor and control vendor devices.

SNMP architectureSNMP architecture

SNMP agent

Tivoli SAN Manager“NetView”

IP StorageiSCSI Target

iSCSIMIB

FC switch MIBFA/FC MIB

FE MIB

2109 Fibre Channel switch

DesktopiSCSI Initiator

Application ServeriSCSI Initiator

Eth

erne

t

SNMP agent

Chapter 6. NetView Data Collection, reporting, and SmartSets 209

MIB tree structureMIB objects are logically organized in a hierarchy called a tree structure. Each MIB object has a name derived from its location in the tree structure. This name, called an object ID, is created by tracing the path from the top of the tree structure, or the root, to the bottom, the object itself. Each place where the path branches is called a node. A node can have both a parent and children. If a node has no children, it is called a leaf node. A leaf node is the actual MIB object. Only leaf nodes return MIB values from agents. The MIB tree structure is shown in Figure 6-3. Note the leaf entry for bcsi which has been added into the tree.

For more information regarding SNMP MIB tree structures. See the following Web sites relating to SNMP RFCs.

http://silver.he.net/~rrg/snmpworld.htmhttp://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/snmp.htm

Figure 6-3 MIB tree structure

6.2 NetView setup and configurationIn this section we provide step by step details for copying and loading the Fibre Channel and iSCSI MIBs into NetView.We then describe the FE MIB and SW MIB in the Brocade 2109 fibre channel switch and also describe the FC (Fibre Alliance) MIB in the IBM TotalStorage IP Storage 200i device.

Note: We are using the Brocade 2.6 enterprise-specific MIBs for SAN network performance reporting and the IBM TotalStorage IP Storage 200i iSCSI MIB

STD (0)

TOP

ISO (1)

ORG (3)

DOD (6)

INTERNET (1)

PRIVATE (4)

ENTERPRISE (1)

CCITT (0)

REG AUTHORITY(1)

MEMBER BODY(2)

JOINT-ISO-CCITT (2)

DIRECTORY (1) MGMT (2) EXPERIMENTAL (3)

MIB (1)

IBM (2) bcsi (1588)RESERVED (0) iSCSI

Note: The FC (Fibre Alliance) MIB is shipped with most fibre channel switch vendors. Brocade Communications provides limited support for the FC MIB.

210 IBM Tivoli Storage Area Network Manager: A Practical Introduction

6.2.1 Advanced MenuIn order to enable certain advanced features in NetView, we must first enable the Advanced Menu feature in the Options pull-down menu as shown in Figure 6-4. Shutdown and restart NetView for the changes to take effect.

Figure 6-4 Enabling the advanced menu

6.2.2 Copy Brocade MIBsBefore MIBs can be loaded into NetView, they must first be copied into the \os\ov\snmp_mibs directory. All vendor specific MIBS are located here.

We accessed the Brocade MIBs from the Web site:

http://www.brocade.com/support/mibs_rsh/index.jsp

We downloaded the MIBs below and copied them to the directory.

� v2_6trp.mib (Enterprise Specific trap)� v2_6sw.mib (Fibre Channel Switch)� v2_6fe.mib (Fabric Element)� v2_6fa.mib (Fibre Alliance)

In Example 6-1 we show the \usr\ov\snmp_mibs directory listing with our newly added MIBs.

Note: If you have unloaded all the MIBs in the MIB description file (\usr\ov\snmp_mibs), you must load MIB-I or MIB-II before you can load any enterprise-specific MIBs. These are loaded by default in NetView.

Chapter 6. NetView Data Collection, reporting, and SmartSets 211

Example 6-1 MIB directory

Directory of C:\usr\ov\snmp_mibs

04/13/2002 09:33a 81,253 v2_6FA.mib08/27/2002 02:45p 79,095 v2_6FE.mib04/13/2002 09:33a 60,139 v2_6SW.mib04/13/2002 09:33a 5,240 v2_6TRP.mib 4 File(s) 225,727 bytes 0 Dir(s) 6,595,670,016 bytes free

C:\usr\ov\snmp_mibs>

6.2.3 Loading MIBsAfter copying the MIBs to the appropriate directory, they must then be loaded into NetView.

IBM 2109The IBM 2109 comes configured to use the MIB II-private MIB (TRP-MIB), FC Switch MIB (SW-MIB), Fibre Alliance MIB (FA-MIB) and Fabric Element MIB (FE-MIB). By default, the MIBs are not enabled. Here is a description of each MIB and their respective groupings.

MIB II-private MIB (v2_6trp.mib or TRP-MIB)The object types in MIB-II are organized into the following groupings:

� The System Group� The Interfaces Group� The Address Translation Group� The IP Group� The ICMP Group� The TCP Group� The UDP Group� The EGP Group� The Transmission Group� The SNMP Group

FC_MGMT (Fibre Alliance) MIB (v2_6fa.mib or FA-MIB)The object types in FA-MIB are organized into the following groupings. Currently Brocade does not write any performance related data into the OIDs for this MIB.

� Connectivity� Trap Registration� Revision Number� Statistic Set

Fabric Element MIB (v2_6fe.mib or FE-MIB)The object types in FE-MIB are organized into these groupings:

� Configuration� Operational� Error� Accounting� Capability

FC Switch MIB (v2_6sw.mib or SW-MIB)The object types in SW-MIB are organized into the following groupings:

� swSystem

212 IBM Tivoli Storage Area Network Manager: A Practical Introduction

� swFabric� swActCfg� swFCport� swNs� swEvent� swFwSystem� swEndDevice

To enable the MIBs for the IBM/Brocade switch, log into the switch via a telnet session, using an ID with administrator privilege (for example, the default admin ID). We enabled all four of the above MIBS using the snmpmibcapset command. The command can either disable or enable a specific MIB within the switch. Example 6-2 shows output from the snmpmibcapset command.

Example 6-2 snmpmibcapset command on IBM 2109

itsosw2:admin> snmpmibcapsetThe SNMP Mib/Trap Capability has been set to support FE-MIB SW-MIB FA-MIB SW-TRAP FA-TRAP SW-EXTTRAPFA-MIB (yes, y, no, n): [yes]SW-TRAP (yes, y, no, n): [yes]FA-TRAP (yes, y, no, n): [yes]SW-EXTTRAP (yes, y, no, n): [yes]no changeitsosw2:admin>

NetViewThe purpose of loading a MIB is to define the MIB objects so the NetView program’s applications can use those MIB definitions. The MIB you are interested in must be loaded on the system where you want to use the MIB Data Collector or MIB Tool Builder. Some vendor’s specific MIBs are already loaded into NetView.

Since we want to collect performance MIB objects types for the Brocade 2109 switch, we will load its MIB. On the NetView interface, select Tools -> MIB -> Loader SNMP V1. This will launch the MIB Loader interface as shown in Figure 6-5.

Figure 6-5 MIB loader interface

Chapter 6. NetView Data Collection, reporting, and SmartSets 213

Each MIB that you load adds a subtree to the MIB tree structure. You must load MIBs in order of their interdependencies. We loaded the v2_6TRP.MIB first by clicking Load then selecting the TRP.MIB from the \usr\ov\snmp_mibs directory — see Figure 6-6.

Figure 6-6 Select and load TRP.MIB

Click Open and the MIB will loaded into NetView. Figure 6-7 shows the MIB loading indicator.

Figure 6-7 Loading MIB

We then loaded the v2_6 SW.MIB, v2_6FE.MIB and v2_6FA.MIBs in turn using the same process. You must load the MIBs in order of their interdependencies. A MIB is dependent on another MIB if its highest node is defined in the other MIB.

After the MIBs are loaded, we now verify that we are able to traverse the MIB tree and select objects from the enterprise-specific MIB. We used the NetView MIB Browser to traverse the branches of the above MIBs. Click Tools --> MIB --> Browser SNMP v1. to launch the MIB browser and use the Down Tree button to navigate down through a MIB — see Figure 6-8

214 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-8 NetView MIB Browser

6.3 Historical reportingNetView provides a graphical reporting tool that can be used against real-time and historical data. After loading the Brocade (IBM 2109) MIBs into NetView, we demonstrate how to compile historical performance data about the IBM 2109 by using the NetView MIB Data Collector and querying the MIB referred to in 6.2.3, “Loading MIBs” on page 212. This tool enables us to manipulate data in several ways, including:

� Collect MIB data from the IBM 2109 at regular intervals.

� Store MIB data about the IBM 2109.

� Define thresholds for MIB data and generate events when the specified thresholds are exceeded. Setting MIB thresholds enables us to automatically monitor important SAN performance parameters to help report, detect and isolate trends or problems.

Brocade 2109 MIBs and MIB objectsWe now need to understand what MIB objects to collect. The IBM 2109 has four MIBs loaded and enabled, described in 6.2.3, “Loading MIBs” on page 212. We selected the MIB object identifiers in Figure 6-9 because of their importance in managing SAN network performance. SAN network administrators may want to specify other MIB object identifiers to meet their own requirements for performance reporting. You should consult your vendor-specific MIB documentation for details of the objects in the MIB. We will describe how to create a MIB Data Collector for the following object identifiers in the following MIBs, shown in Figure 6-9 and Figure 6-10.

Chapter 6. NetView Data Collection, reporting, and SmartSets 215

Figure 6-9 FE-MIB — Error Group

Figure 6-10 SW MIB — Port Table Group

6.3.1 Creating a Data CollectionOur first Data Collection will target the MIB object swFCPortTxFrames. The swFCPortTxFrames counts the number of Fibre Channel frames that the port has transmitted. It contains group information about the physical state, operational status, performance and error statistics of each Fibre Channel port on the switch for example, F_Port, E_Port, U_Port, FL_Port.

Figure 6-11 describes the MIB tree where this object identifier resides. The root of the tree, bcsi, stands for Brocade Communication Systems Incorporated.

The next several pages describe the step-by-step process for defining a Data Collection on the swFcPortTxFrames MIB object identifier using NetView.

fcFXPortLinkFailures - Number of link failures detected by this FxPort

fcFXPortSyncLosses - Number of loss of synchronization detected by the FxPort

fcFXPortSigLosses - Number of signal losses detected by the FxPort.

FE-MIB Error GroupFE-MIB Error Group

swFcPortTXWords - Number of FC words transmitted by the port

swFcPortRXWords - Number of FC words received by the port

swFcPortTXFrames - Number of FC frames transmitted by the port

swFcPortRXFrames - Number of FC frames received by the port

swFcPortTXC2Frames - Number of Class 2 frames received by the port

swFcPortTXC3Frames - Number of Class 3 frames received by the port

SW-MIB Port Table GroupSW-MIB Port Table Group

216 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-11 Private MIB tree for bcsi

1. To create the NetView Data Collection, select Tools -> MIB -> Collect Data from the NetView main menu. The MIB Data Collector interface displays (Figure 6-12). Select New to create a collection.

Figure 6-12 MIB Data Collector GUI

2. If creating the first Data Collection, you will also see the pop-up in Figure 6-13 to start the Data Collection daemon. Click Yes to start the SNMPCollect daemon.

bcsi (1588)

fcSwitch (1)

Fibre channel (1)

commDev (2)

sw (1)

swFCPort (6)

swFCPortTable (2)

swFCPortEntry (1)

swFCPortTxFrames (13)

IBM 2109IBM 2109private MIB treeprivate MIB tree

Chapter 6. NetView Data Collection, reporting, and SmartSets 217

Figure 6-13 starting the SNMP collect daemon

3. The Data Collection Wizard GUI then displays (Figure 6-14). This is the first step in creating a new Data Collection. By default NetView has navigated down to the Internet branch of the tree (.iso.org.dod.internet). See Figure 6-3 on page 210 for the overall tree structure. Highlight private and click Down Tree to navigate to the private MIB.

Figure 6-14 internet branch of MIB tree

We have now reached the private branch of the MIB tree (.iso.org.dod.internet.private). See Figure 6-15.

218 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-15 Private arm of MIB tree

4. Continue to navigate down the enterprise branch of the tree by clicking Down Tree. Figure 6-16 shows the enterprise branch of the tree (.iso.org.dod.internet.private.enterprise).

Figure 6-16 Enterprise branch of MIB tree

Chapter 6. NetView Data Collection, reporting, and SmartSets 219

5. We reach the bcsi branch of the tree by clicking Down Tree. Figure 6-17 shows the bcsi (Brocade) branch of the tree (.iso.org.dod.internet.private.enterprise.bcsi).

Figure 6-17 bcsi branch of MIB tree

6. We continue to navigate down the tree, using the path shown in Figure 6-11 on page 217, and, as shown in Figure 6-18, eventually reaching: .iso.org.dod.internet.private.enterprise.bcsi.commDev.fibrechannel.fcSwitch.sw.swFCport.swFCPort.swFCPortEnrty.swFCPortTxFrames.

220 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-18 swFCPortTxFrames MIB object identifier

7. We selected swFCPortTxFrames and clicked OK. We received the following pop-up (Figure 6-19) from the collection wizard. This pop-up occurs because this will be the first node added to this collection. NetView then adds the swFCTxFrames MIB Data Collection definition as a valid data collector entry.

Figure 6-19 Adding the nodes

This launches the Add Nodes to the Collection Dialog, which is the second step in creating a new Data Collection. See Figure 6-20.

Chapter 6. NetView Data Collection, reporting, and SmartSets 221

Figure 6-20 Add Nodes to the Collection Dialog

8. We proceeded to customize the section Collect MIB Data from fields, using the following steps:

a. We entered the switch node name for which we wanted to collect performance data (in this case, ITSOSW2.ALMADEN.IBM.COM) and clicked Add Node. You can add a node either by selecting it on the topology map or typing in the field as the IP address or hostname for the device. Also, you can select multiple devices on the topology map and click Add Selected Nodes from Map. This adds all the selected nodes selected on the topology map to the Collect MIB Data From field. We also added several nodes to the collection by adding one device at a time in the Node field and clicking Add Node. To remove the node, just click the node name in the list and click Remove.

b. We then customized the section Set the Polling Properties for these Nodes, using the following steps:

i. We changed the Poll Nodes Every field to 5 minutes. This specifies the frequency in which the nodes are polled.

ii. We checked Store MIB Data. This will store the MIB data that is collected to C:/usr/ov/databases.

iii. The Check Threshold if box was checked. This will define the arm threshold. We want to collect data and signal an event each time more than 200 frames are sent on a particular port. Since we checked this box, we will be required to define the trap value and rearm number fields.

iv. The option then send Trap Number was configured. We used the default setting, which is the MIB-II enterprise-specific trap.

v. We then configured and rearm When. We specified a rearm value of greater than or equal to 75%. of the arm threshold value. This means that a trap will be

Important: Before setting the polling interval, you should have a clear understanding of available and used bandwidth in your network. Shorter polling intervals generate more SNMP data on the network.

222 IBM Tivoli Storage Area Network Manager: A Practical Introduction

generated and sent when the number of TX frames reaches 150. Note that these traps are NetView-specific traps (separate from Tivoli SAN Manager traps) and will therefore be sent to the NetView console.

9. Click OK to create the new Data Collection, shown in Figure 6-21. Select the swFCPortTxFrames Data Collection and click Collect.

Figure 6-21 Newly added Data Collection for swFCTxFrames

10.Click Close and the Stop and restart Collection dialog is displayed as in Figure 6-22. Click Yes to recycle the snmpcollect daemon. At this point the Data Collection status (Figure 6-21 above) should change from Suspended to To be Collected

Figure 6-22 Restart the collection daemon

We are now collecting the data swFCTxFrames on ITSOSW2. Depending upon the level of granularity that is required for your reporting needs, you may want to collect data over shorter or longer periods. In our lab we collected every 5 minutes, but you may want to collect data once every hour for a week or once every hour for a month.

We will now use the NetView Graph tool to display the data collected as described in 6.3.4, “NetView Graph Utility” on page 225.

Note: It could take up to 2 minutes before the newly defined Data Collection is being collected by NetView. To verify that data is being captured, navigate to: c:\usr\ov\databases\snmpcollect. If there are files present, then the Data Collection is functioning properly.

Chapter 6. NetView Data Collection, reporting, and SmartSets 223

6.3.2 Database maintenanceYou can periodically purge the Data Collection entries by selecting Options --> Server Setup, the Files tab page, then select Schedule SNMP Files to Delete from the drop-down list. See Figure 6-23. Select the Purge day at a specific time.

Figure 6-23 Purge Data Collection files

6.3.3 Troubleshooting the Data Collection daemonIf you find data is not being collected, ensure that the snmpCollect daemon is running and that there is space available in the collection file system \usr\ov\databases\snmpcollect. The daemon can stop running if there is no filesystem space.

To verify that the daemon is running type ovstatus snmpcollect from the DOS command prompt. See Example 6-3.

Note: We followed the same procedure to add the remaining metrics for Data Collection swFCRxFrames, swFCTxErrors, and swFCRxErrors. For demonstration purposes we used a of 50 for an arm threshold and a value of 75% for re-arm. Your values for arm/re-arm may differ from what we used.

Important: There are documented steps on how to perform important maintenance of Tivoli NetView. Refer to the IBM Redbook Tivoli NetVIew and Friends, SG24-6019.

224 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Example 6-3 snmpcollect daemon running

C:\>ovstatus snmpcollect object manager name: snmpcollect behavior: OVs_WELL_BEHAVED state: RUNNING PID: 1536 last message: Initialization complete. exit status: -

Done

C:\>

If the snmpcollect daemon is not running, you will see a state value of NOT RUNNING from the ovstatus snmpcollect command as shown in Example 6-4.

Example 6-4 snmpcollect daemon stopped

C:\>ovstatus snmpcollect object manager name: snmpcollect behavior: OVs_WELL_BEHAVED state: NOT RUNNING PID: 1536 last message: Exited due to user request. exit status: -

Done

C:\>

The snmpcollect daemon can be started manually. At a command prompt, we typed in ovstart snmpcollect. You will see the output shown in Example 6-5. We then issued an ovstatus snmpcollect for verification, as shown in Example 6-3.

Example 6-5 snmpcolllect started

C:\>ovstart snmpcollectDone

C:\>

6.3.4 NetView Graph UtilityWe used the NetView graph utility to display the MIB object data that we collected in 6.3.1, “Creating a Data Collection” on page 216.

We used the NetView Graph tool to display the collected data. This provides a convenient way to display numerical performance information on collected data.

We now show how to display the collected data from the previous Data Collection that was built for ITSOSW2 (swFCPortTxFrames). We start by single-clicking ITSOSW2 on the NetView topology map (Figure 6-24).

Note: If no Data Collections are currently defined to the MIB Data Collector tool, the snmpcollect daemon will not run.

Chapter 6. NetView Data Collection, reporting, and SmartSets 225

Figure 6-24 Select ITSOSW2

Select Tools --> MIB --> Graph Data to launch the graph utility This will report on the historical data that has been collected on ITSOSW2. After selecting this, NetView takes some time to process the data and present it in the graphical display. The graph build time depends on the amount of data collected. Figure 6-25 shows the progress indicator.

Figure 6-25 Building graph

After the graph is built, it displays the swFCTxFrames data that was collected (Figure 6-26). Note there are multiple instances of the object ID mapped — that is, swFCPortTxFrames.1, swFCPortTxFrames.2 and so on. In this case they represent the data collected for each port in the switch.

226 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-26 Graphing of swFCTxFrames

For viewing purposes, we adjusted the x-axis for Time by clicking Edit --> Graph Properties in the open graph window. This allowed us to zoom into shorter time periods. See Figure 6-27.

Figure 6-27 Graph properties

Any MIB object identifier that has been collected using the NetView MIB Data Collector can be graphed using the NetView Graph facility using the above process.

6.4 Real-time reportingIn section we introduce the NetView MIB Tool Builder for real-time reporting. Figure 6-28 provides an overview.

Chapter 6. NetView Data Collection, reporting, and SmartSets 227

Figure 6-28 Real-time reporting — Tool Builder overview

Figure 6-29 Enabling all functions in NetView

6.4.1 MIB Tool BuilderIn section we introduce the NetView MIB Tool Builder. The Tool Builder enables you to build, modify, and delete MIB applications. MIB Applications are programs used by NetView to monitor the network. The Tool Builder allows you to build MIB applications without programming. The MIB Application monitors the real-time performance of specific MIB objects on a regular basis and produces output such as forms, tables, or graphs.

Important: Depending on the configuration, some advanced functionality may be initially disabled in NetView under Tivoli SAN Manager. This section requires this functionality to be enabled. To enable all functionality required, in NetView, click Options --> Polling and check the Poll All Nodes field. This is shown in Figure 6-29.

Describe the MIB Tool Builder

Use of the Tool Builderbuild

modify

delete

228 IBM Tivoli Storage Area Network Manager: A Practical Introduction

We will demonstrate how to build a a MIB application that will query the swFCPortTxFrames MIB object identifier in the SW-MIB. This process can used to query any SNMP enabled device using NetView.

With the switch ITSOSW2 selected, we start building the MIB Application by launching the Tool Builder. Select Tools --> MIB --> Tool Builder --> New. The MIB Tool Builder interface is launched — as in Figure 6-30. Click New to create a new Tool Builder entry for collecting data on ITSOSW2.

Figure 6-30 MIB tool Builder interface

The Tool Builder Wizard Step1 window is displayed (Figure 6-31). We entered FCPortTxFrames in the Title field and clicked in the Tool ID field to auto populate the remaining fields. We clicked Next to continue with the wizard.

Figure 6-31 Tool Wizard Step 1

Chapter 6. NetView Data Collection, reporting, and SmartSets 229

The Tool Wizard Step 2 interface displays. You can see our title of FCPortTxFrames has carried over. We are now ready to select the display type. We can choose between Forms, Tables, or Graphs. We will choose Graph and click New as shown in Figure 6-32.

Figure 6-32 Tool Wizard Step 2

The NetView MIB Browser is now displayed. We will use the MIB Browser to navigate down to the FCPortTxFrames object identifier. Use the Down Tree button to navigate through the MIB tree. Figure 6-33 shows the path through the SW-MIB error table. Click OK to add the object identifier.

Figure 6-33 SW-MIB — Port Table

The newly created MIB application is displayed in the Tool Builder Step 2 of 2 window. See Figure 6-34 for the completed MIB Application. Click OK to complete the definition.

SW MIB - Port Table groupSW MIB - Port Table group

private...private...enterprise...enterprise...

bcsi...bcsi... commDev... commDev... fibrechannel... fibrechannel... fcSwitch... fcSwitch... sw... sw... swFcPort... swFcPort... swFcPortTable... swFcPortTable... swFCPortTxFrames swFCPortTxFrames

230 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-34 Final step of Tool Wizard

Now, the final window for the Tool Builder is displayed. It shows the newly created MIB application in the window, Figure 6-35. Click Close to close the window. The new MIB Application has been successfully created.

Figure 6-35 New MIB application — FXPortTXFrames

6.4.2 Displaying real-time dataNow that we have a MIB application, we want to collect real-time data from the switch. Select ITSOSW2 from the NetView topology map by single clicking the ITSOSW2 symbol, then select Monitor --> Other --> FCPortTXFrames. Our MIB application FCPortTXFrames has been added to the menu (shown in Figure 6-36).

Chapter 6. NetView Data Collection, reporting, and SmartSets 231

Figure 6-36 Monitor pull-down menu

Clicking on the FCPortTXFrames option, launches a graph utility, shown in Figure 6-37.

Figure 6-37 NetView Graph starting

The collection of MIB data starts immediately after selecting the swFCPortTXFrames MIB application from the Monitor --> Other menu. Figure 6-38 shows the data being collected and displayed for each MIB instance of the ITSOSW2.

232 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-38 Graph of FCPortTXFrames

The polling interval of the application can be controlled using the Poll Nodes Every field located under Edit --> Graph Properties. See Figure 6-39.

Figure 6-39 Graph Properties

Chapter 6. NetView Data Collection, reporting, and SmartSets 233

This launches a dialog to specify how often NetView Graph receives real-time data for graphing, shown in Figure 6-40. This determines how often the nodes are asked for data.

Figure 6-40 Polling Interval

We continued to use the Tool Builder process defined in 6.4.1, “MIB Tool Builder” on page 228 to build additional MIB applications for real-time performance monitoring. We used the following MIB objects:

� swFcPortTXWords� swFcPortRXC2Frames� swFCPortRXC3Frames� fcFXPortLinkFailures� fcFXPortSyncLosses� fcFXPortSigLosses

Figure 6-41 shows the newly defined MIB Applications as they appear in the Tool Builder.

Figure 6-41 Tool Builder with all MIB objects defined

Figure 6-42 shows all the above MIB objects as they appear in the NetView Monitor pull-down menu. Note we have abbreviated the names of the MIB applications listed in the Monitor --> Other menu for ease of use.

234 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-42 All MIB objects in NetView

6.4.3 SmartSetsWith Tivoli SAN Manager providing the management of the SAN, we can further extend the management functionality of the SAN from a LAN and iSCSI perspective. NetView SmartSets gives us this ability. This section describes the concept of the NetView SmartSet. See Figure 6-43 below. For an overview, we provide details on how to group and mange your SAN attached resources from an TCP/IP (SNMP) perspective.

By default, the iSCSI SmartSet is created by IBM Tivoli SAN Manager when nvsniffer is enabled. SmartSets for iSCSI “initiators” and “targets” can be created using the process described here.

Figure 6-43 SmartSet Overview

In NetView a SmartSet is used to monitor a set of objects (devices). NetView allows for user-defined SmartSets. We use this to define and manage our SAN devices as one item.

SmartSets can be used to group together systems that support a specific operating system, device type or business function. The symbol status displayed for nodes appearing in

What is a SmartSet?

Why SmartSets?

Defining a SmartSet

SmartSets and Data Collections

Chapter 6. NetView Data Collection, reporting, and SmartSets 235

user-defined SmartSets is based solely on the IP status, not Fibre Channel status. You can customize the attributes available for creating a SmartSets. Refer to the manual Tivoli NetView for Windows User’s Guide, SC31-8888 for more information.

With Tivoli SAN Manager using the TCP/IP and Fibre Channel protocols to manage the SAN, we will demonstrate how to complement this by using SNMP to manage the same components of the SAN using SmartSets.

We will demonstrate how to group all the IBM 2109 Fibre Channel switches (ITSOSW1, ITSOSW2 and ITSOSW3) in our configuration, into one SmartSet called IBM2109.

1. On the NetView topology display select the switches ITSOSW1, ITSOSW2 and ITSOSW3. See Figure 6-44 for selected switches. Each symbol can be selected by holding down the Shift-Key and clicking once on each symbol.

Figure 6-44 Selected Fibre Channel switches

2. Select Submap --> New Smartset from the main menu. The Find window is displayed, as in Figure 6-45.

Important: Depending on the configuration, some advanced functionality required for SmartSets may be disabled in NetView in Tivoli SAN Manager. This section requires this functionality to be enabled. To enable all functionality required, in NetView, click Options -> Polling and check the Poll All Nodes field. This is shown in Figure 6-29 on page 228.

236 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-45 Defining a SmartSet

3. Click the Advanced tab — this will allow the selected switches on the topology map to be added to the SmartSet. See Figure 6-46.

Chapter 6. NetView Data Collection, reporting, and SmartSets 237

Figure 6-46 Advanced window

4. Click the Add Selected Objects to add ITSOSW1, ITSOSW2, and ITSOSW3 to the Combined Functions field (Figure 6-47).

238 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-47 Advanced window with 2109s added

5. Click Create SmartSet. This launches the New SmartSet dialog. We entered the name of our SmartSet as IBM2109, and added a description. See Figure 6-48. Note — no spaces are allowed in the SmartSet Name field.

Figure 6-48 New SmartSet

6. At this point, the SmartSet definition is complete. Click the SmartSets tab to verify that the IBM2109 SmartSet was created as shown in Figure 6-49.

Chapter 6. NetView Data Collection, reporting, and SmartSets 239

Figure 6-49 New SmartSet — IBM 2109

Verifying SmartSet creationTo verify that the SmartSet was created successfully, we follow these steps:

1. We go to the NetView root map, shown in Figure 5-13 on page 161, and click the SmartSets icon.

2. We can see the IBM2109 SmartSet that we created (Figure 6-50).

240 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-50 SmartSet topology map

3. Clicking on the IBM2109 SmartSet, we find its members ITSOSW1, ITSOSW2, and ITSOSW3, as shown in Figure 6-51.

Note: Symbols on the topology map have links back to their respective objects, since the same symbol can reside in more than one location in NetView. In the case of the switch discussed here, the same symbol in the SmartSet also resides on the IP Internet map. Propagation of status occurs to all symbols regardless of their location on the topology. For example, if there is a problem with the switch, causing it to change to a critical (RED) status, this will be reflected in both the SmartSet and on the IP Internet map.

Chapter 6. NetView Data Collection, reporting, and SmartSets 241

Figure 6-51 ITSOSW1, ITSOSW2 and ITSOSW3 in IBM2109 SmartSet

SmartSets can be used to group your devices using a logical taxonomy for the enterprise. For our setup, we categorized our SAN resources by Fabric and Operating System. This allows us to easily manage those devices at a high level. Alternatively, we could have grouped the devices by SAN fabric, or by Application or Business Function. We created the following SmartSets, shown in Figure 6-52:

� IBM 2109 — contains all IBM 2109 Fibre Channel switches� SANfabricA_AIX — contains all AIX SAN attached hosts� SANfabricA_HPUX — contains all HP-UX SAN attached hosts� SANfabricA_Solaris — contains all Solaris SAN attached hosts� SANfabricA_Win2k — contains all Windows 2000 SAN attached hosts� TivoliSANManager — contains all the Tivoli SAN Manager hosts.

Now we can manage our SAN attached devices from both SAN and LAN perspectives from a single console.

242 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-52 Additional SmartSets

6.4.4 SmartSets and Data CollectionsSince SmartSets allows us to group objects, we now have additional flexibility when creating Data Collections. See 6.3.1, “Creating a Data Collection” on page 216 for more information on Data Collections. We can now apply a Data Collection against a SmartSet. The IBM2109 SmartSet already defined contains switches ITSOSW1, ITSOSW2 and ITSOSW3, therefore we can now collect the swFCPortTxFrames MIB object from all three switches using one definition.

1. We follow the same process defined in 6.3.1, “Creating a Data Collection” on page 216.

2. At the Collection Wizard Step2 of 2 window, we selected the IBM2109 Smartset from the Add SmartSet pull down menu instead of adding in a new node. See Figure 6-53. We then clicked OK, then closed the MIB Data Collector window.

Chapter 6. NetView Data Collection, reporting, and SmartSets 243

Figure 6-53 IBM2109 SmartSet defined to Data Collection

3. After allowing the Data Collection to collect data, we then graph the data using Tools --> MIB --> Graph Data All. The NetView Graph dialog (Figure 6-54) is displayed while the information is collected — this can take some time, depending on the amount of data returned.

Figure 6-54 NetView Graph starting

4. A window displays, presenting all MIB instances of the swFCPortTxFrames MIB object (Figure 6-55) for all three switches in the SmartSet. Since the total number of entries is greater than 15, we get a message on the menu bar indicating that Maximum Graph Lines Exceeded. The NetView Graph utility can only graph 15 lines at a time.

244 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-55 IBM2109 SmartSet data collected

5. Next, we need to select the desired instance of the MIB object for each switch that we want to graph. We then clicked Add to add the selected MIB labels to the Lines To Graph panel, then we clicked OK. For this example, we chose the first 5 instances for each of the three switches, shown in Figure 6-56. Click OK to start the graph.

Figure 6-56 Selected MIB instances

The NetView Graph for the fifteen MIB instances we selected is shown in Figure 6-57.

Chapter 6. NetView Data Collection, reporting, and SmartSets 245

Figure 6-57 Graph showing selected instances

6.4.5 Seed fileWhen NetView is started for the first time, the default IP management region is the system on which the NetView program is operating, plus any IP networks to which it is attached. The discovery process generates the IP Internet topology map by working outward from the management system.

We re-defined our management region by using a seed file. The seed file contains a listing of the IP addresses for our SAN management domain. This contains all Fibre Channel devices that have IP connectivity. Only nodes listed in this file will be used by netmon daemon for rediscovery. This forces discovery to be strictly limited to the contents of the seed file. Using a seed file forces the discovery process to generate the topology map beginning from nodes other than the management system. We wanted our management domain to be limited to our IP connected SAN devices, thus the use of the seed file.

NetView uses the default template located in \usr\ov\conf\netmon.seed. We modified the netmon seed file to include the specific IP addresses of all the LAN attached SAN devices. for more details on the seed file please refer to the comments section of the \usr\ov\conf\netmon.seed. Example 6-6 shows a partial listing of the seed file.

Note: iSCSI discovery requires that IP discovery in Tivoli NetView that is shipped with IBM Tivoli SAN Manager be enabled. Be aware that when you turn on IP discovery, there can be a lot of network activity depending on how many devices are in your IP network. For this reason we advise the use of the seed file.

246 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Example 6-6 Modified seed file for limited discovery

## All seed file errors are logged in the \usr\OV\log\nv.log file. Any# entry that is invalid will be ignored.## If the <SystemRoot>\system32\drivers\etc\networks file has entries# for subnets that are contained in your network, the network names# as specified in the file will appear on the map instead of the network# numbers.#############################################################################9.1.38.1889.1.38.1849.1.38.1869.1.38.1879.1.38.1899.1.38.1539.1.38.1549.1.38.1919.1.38.1559.1.38.1529.1.38.1579.1.38.1589.1.38.1599.1.38.201!*

Once the seed file is updated and saved, we then need to clear out the NetView databases where the current topology information is stored. Start Server Setup by clicking Options --> Server Setup as in Figure 6-58.

The Server Setup options window (Figure 6-58) displays.

Important: Performing the Clear Databases on NetView will delete all previously saved NetView object and topology information only. This does affect the Tivoli SAN Manager and WebSphere Application Server databases.

Chapter 6. NetView Data Collection, reporting, and SmartSets 247

Figure 6-58 Server Setup

Now we want to configure NetView to use the updated seed file. Click the Discovery tab in The Server Setup options window. Under discovery, check Use Seed File, shown in Figure 6-59 and click OK.

248 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-59 Server Setup options window

Click the Databases tab. Click the pull-down, select Clear Databases, shown in Figure 6-60, and click OK. This starts the process to clear the databases.

Figure 6-60 Clear Database

NetView prompts one last time to verify that you want to clear the databases. Click Yes. Figure 6-61 shows the warning message.

Figure 6-61 Clear databases warning

Chapter 6. NetView Data Collection, reporting, and SmartSets 249

Clearing the databases typically takes a minute, however, this will vary depending on the size of the NetView databases being cleared. The NetView console will automatically shut down and restart when complete. See Figure 6-62.

Figure 6-62 NetView stopping — clearing databases

When NetView restarts, it will discover and display the nodes that we defined in our netmon.seed file, shown in Figure 6-63.

Figure 6-63 With seed file

To demonstrate the difference in the discovered IP topologies, Figure 6-64 shows the NetView display without using a seed file for discovery. In this case, NetView discovers itself and all other nodes on the subnet.

250 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 6-64 Without seed file

This completes our demonstration of how existing NetView capabilities can be leveraged to further extend the capabilities of Tivoli SAN Manager.

Chapter 6. NetView Data Collection, reporting, and SmartSets 251

252 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 7. Tivoli SAN Manager and iSCSI

IBM is a leader in the development and delivery of iSCSI technology and storage products. IBM, as well as other network and storage vendors, is working closely with the Internet Engineering Task force (IETF) in developing iSCSI standards.

This chapter provides an overview of the Small Computer Systems Interface over IP (iSCSI) standard and how IBM Tivoli SAN Manager discovers and monitors iSCSI devices. We cover these topics:

� What is iSCSI?� How does iSCSI work?� IBM Tivoli SAN Manager and iSCSI

– Functional Description– iSCSI Discovery

7

© Copyright IBM Corp. 2002, 2003. All rights reserved. 253

7.1 What is iSCSI?Internet Small Computer Systems Interface (iSCSI) is a proposed industry standard that allows SCSI block I/O protocols (commands, sequences and attributes) to be sent over a network using the TCP/IP protocol. The iSCSI proposal was made to the Internet Engineering Task Force (IETF) standards body jointly by IBM and Cisco.

http://www.ietf.org/

7.2 How does iSCSI work?The iSCSI protocol is used on servers and workstations called (initiators), and storage devices (called targets). The client initiator issues the commands to the storage server (target). The storage server (target) then fulfills the request. The initiator and targets are identified by their world wide unique iSCSI names.

Figure 7-1 shows the basic components of iSCSI.

Figure 7-1 iSCSI components

iSCSI uses standard Ethernet switches and routers to move the data from server to storage. It also allows the IP and Ethernet infrastructure to be used for expanding access to SAN storage and extending SAN connectivity across any distance.

Figure 7-2 shows a comparison of fibre channel to iSCSI.

iSCSI Components iSCSI Components

SCSI (Block I/O)Protocol

Client Desktop

Application Server

initiator

initiator

targetIP

Storage

254 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 7-2 Fibre Channel versus iSCSI

Below we list some common iSCSI terms:

iSCSI Adapter - iSCSI Adapters combine the functions of Network Interface Cards (NICs) with the function of a storage Host Bus Adapter (HBA). These adapters take the data in block form, and perform processing on the adapter card with TCP/IP processing engines, and then send the IP packets across an IP network. The implementation of these functions enables users to create an IP based SAN without lowering the performance of the server. I

iSCSI Drivers - before the introduction of iSCSI adapters, some vendors released software versions of iSCSI adapters. These software-enabled adapters accept block level data from applications, but still require CPU cycles for the TCP/IP processing. The advantage of such adapters is that they can work on existing Ethernet NICs. The main disadvantage is that they require heavy CPU utilization for TCP/IP processing.

iSCSI Name - The name of the iSCSI initiator or iSCSI target.

iSCSI Node - This represent either an iSCSI initiator or iSCSI target. The iSCSI node is identified by its iSCSI name.

7.3 IBM Tivoli SAN Manager and iSCSIYou can discover and manage devices that use the iSCSI storage networking protocol through IBM Tivoli SAN Manager using IBM Tivoli NetView.

IBM Tivoli SAN Manager also provides the Internet Storage Name Service (iSNS) MIB, which is a storage management protocol from IETF for managing iSCSI devices. The iSNS provides registration for storage devices and hosts with an iSNS server. Subsequently, the hosts can either query the iSNS server or receive asynchronous updates from the iSNS server on the status of the storage devices.The IBM Tivoli SAN Manager iSCSI support can be used either independently or in conjunction with the iSNS management framework.

FC SAN iSCSI

Fibre Channel vs iSCSI

DatabaseApplication

Block I/O

DatabaseApplication

Block I/O

FC NetworkSCSI Protocols

IP NetworkiSCSI Protocols

PooledStorage

PooledStorage

Chapter 7. Tivoli SAN Manager and iSCSI 255

7.3.1 Functional descriptionThe following is a functional description of iSCSI support in NetView 9as used by Tivoli SAN Manager):

� All iSCSI devices discovered in the IP network are placed in a unique iSCSI SmartSet. Additionally, the user will have the option to create separate SmartSets for iSCSI initiator devices and target devices.

� NetView’s nvsniffer utility performs the discovery of iSCSI devices. The nvsniffer program uses a configuration file which:

– Governs which services to discover.– Determines which service SmartSets to create.– Determines which ports to test for a given service.– Determines whether to use custom tests for discovering and checking the status for a

service.

� The iSCSI MIBs and iSNS MIBs are pre-installed into the c:\usr\ov\snmp_mibs directory. This is performed so that the NetView MIB browser can be used to query the iSCSI MIBs.

� The iSCSI MIB trap definition files are used by Tivoli NetView for event processing.

7.3.2 iSCSI discoveryThe iSCSI discovery is performed separately from the SAN device discovery done by IBM Tivoli SAN Manager. iSCSI discovery is done through the nvsniffer program and can be scheduled to refresh the iSCSI SmartSets at specified intervals.

Before you can perform iSCSI discovery, you must first enable SNMP on the iSCSI device and IP Internet discovery. Be aware that when you turn on the IP network discovery, there can be a lot of activity depending on how many devices you have in your IP network. Before enabling IP discovery, update the netmon seed file - c:\usr\ov\snmpconf\netmon.seed. See 6.4.5, “Seed file” on page 246 for defining a seed file. See 6.4, “Real-time reporting” on page 227 for enabling IP Internet functionality.

In addition to the above mentioned references, IBM Tivoli SAN Manager also requires the following for iSCSI discovery:

� The device must have iSCSI MIB support.� The device should be configured so that the iSCSI MIB support is active.� The iSCSI device must be discovered first as an IP device by NetView before nvsniffer

can discover it as an iSCSI device.

iSCSI MIBsBefore managing the iSCSI device, the MIBs must be loaded. By default, the MIBs are not loaded in to Tivoli NetView at installation time. You have to load these MIBs using the NetView MIB loading function.

The purpose of loading a MIB is to define the MIB objects so NetView’s applications can use those MIB definitions. You load the iSCSI MIB files one at a time into Tivoli NetView.

Restriction: Note that IBM Tivoli NetView does not currently support MIB Tool Builder and Data Collections against SNMP V2.

256 IBM Tivoli Storage Area Network Manager: A Practical Introduction

The iSCSI MIBs should loaded in the following order:

� iSCSI MIB - The iSCSI MIB is layered between the SCSI MIB and the TCP MIB, and makes use of the iSCSI Auth MIB

� iSCSI Auth MIB - Each iSCSI target node can have a list of authorized initiators. Each of the entries in this list points to an identity within the Auth MIB that will be allowed to access the target. iSCSI initiator nodes can also have a list of authorized targets. Each of the entries in this list points to an identity within the Auth MIB to which the initiator should attempt to establish sessions. The Auth MIB includes information used to identify initiators and targets by their iSCSI name, IP address, and/or credentials.

� FC_MGMT MIB - This MIB is also know as the Fibre Alliance MIB. The goal of the industry consortium is to develop and implement standard methods for managing heterogeneous Fibre Channel-based networks of storage systems, connectivity equipment and computer servers. The FC_MGMT MIB is organized in the following groups:

– Connectivity– Trap Registration– Revision Number Statistic Set– Service Set

� iSNS MIB - The Internet Storage Name Service iSNS defines a mechanism for IP based storage devices to register and query for other storage devices in the network. The iSNS MIB is designed to allow SNMP to be used to monitor and manage iSCSI devices.

See 6.2.3, “Loading MIBs” on page 212 for detailed instructions on loading MIBs.

7.4 Summary In this chapter, we introduced iSCSI and explained how it functions. We also described how IBM Tivoli SAN Manager performs discovery of iSCSI devices.

Chapter 7. Tivoli SAN Manager and iSCSI 257

258 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 8. SNMP Event notification

In this chapter we describe SNMP trap forwarding, both to Tivoli NetView, and to IBM Director.

8

© Copyright IBM Corp. 2002, 2003. All rights reserved. 259

8.1 OverviewFirst, we describe configuration options for forwarding events to the SNMP managers. We also describe how IBM Director can be integrated via SNMP to Tivoli SAN Manager. Figure 8-1 gives an overview of this chapter.

Figure 8-1 Event notification overview

8.2 Introduction to Tivoli NetViewTivoli NetView is a scalable, comprehensive, distributed network solution that helps provide you with the flexibility to manage mission-critical networks. It helps enable availability of critical business systems and rapid problem resolution. It can also let you discover TCP/IP networks, display network topologies, correlate and manage events and simple network management protocol (SNMP) traps, monitor network health and gather performance data.

In the scenario we are showing here we are assuming that the Tivoli NetView installation already exists in the enterprise. Therefore we will only focus on the configuration.

8.2.1 Setting up the MIB file in Tivoli NetViewThe IBM Tivoli SAN Manager Server can generate SNMP traps. These traps can be either forwarded to the Tivoli NetView console which is installed on the same system or to some other Tivoli NetView or another SNMP management console (Figure 8-2).

SNMP Event Notification OverviewSNMP Event Notification Overview

Introduction to Tivoli NetView

Integration with IBM Tivoli SAN ManagerConfiguring IBM Tivoli SAN Manager

Configuring Tivoli SAN Manager

Introduction to IBM Director

Integration with IBM Tivoli SAN ManagerConfiguring IBM Tivoli SAN Manager

Configuring IBM Director

260 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 8-2 SAN Manager generated SNMP traps

Use the ITSANM.MIB file from the \misc\utils directory on the installation media. This file should be incorporated in your SNMP management console trap definition. This MIB file only provides the trap information.

If you use the Tivoli NetView console as the SNMP console, you need to perform these steps so that traps will be displayed in an appropriate format in the Tivoli NetView Event browser:

1. Copy ITSANM.MIB to the c:\temp directory.

2. Run the mib2trap program on the ITSANM.MIB file. Specify the full path name for a writable directory when creating the ITSANM.BAT file. For example, run this command to create the bat file on the directory c:\temp:

mib2trap c:\temp \ITSANM.MIB c:\temp \ITSANM.BAT

You can name the BAT file anything you want. This example creates a file called ITSANM.BAT.

3. Edit ITSANM.BAT to format the events displayed in NetView. Change the options:

– –c option which is the event type display:

-c LOGONLY

Change to:

-c "Status Events"

– –f option which tells Tivoli NetView how to display the trap:

-F "$E $G $S $#args:$*"

Change to:

-F "$1 $*"

Example 8-1 and Example 8-2 show the ITSANM.BAT file before and after the change.

IBM Tivoli SAN Manager generated SNMP trapsIBM Tivoli SAN Manager generated SNMP traps

Disk array

Disk array

Disk array

Disk array

Disk array

Switch

SAN

Managed Host(Agent)

Managed Host(Agent)

Managed Host(Agent)

IBM Tivoli Storage Area

NetworkManager

SNMP ManagerConsoleport 162

Chapter 8. SNMP Event notification 261

Example 8-1 ITSANM.BAT original file

C:\usr\ov\bin\addtrap -1 btsfsExtendCompleted_-g 6 -s 8 -nbtsfsExtendCompleted -i 1.3.6.1.4.1.2.6.173.3.8 -o A -c LOGONLY -t 0 -S 1-f--F "$E $G $S $#args:$*"

Example 8-2 ITSANM.BAT modified file

C:\usr\ov\bin\addtrap -1 btsfsExtendCompleted_-g 6 -s 8 -nbtsfsExtendCompleted -i 1.3.6.1.4.1.2.6.173.3.8 -o A -c "StatusEvents"-t 0-S 1-f--F "$1 $*"

4. Run the ITSANM.BAT file.

5. Restart Tivoli NetView and bring up the monitor to see all the events.

Setting up the SNMP trap destination in SAN ManagerTo receive SNMP traps from Tivoli SAN Manager you need to set the trap destination. Select SAN -> Set Event Destination from the Tivoli NetView console (Figure 8-3).

Figure 8-3 Event Destination

Type in the IP address, port number and community name of the SNMP Manager console you will use for receiving SNMP traps from SAN Manager Server. After you type in the information click Add to add the entry to the list.

Tip: There are many traps, so use the “Replace All” feature in your editor.

262 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Changing the SNMP community nameThe default SNMP community name which is used in IBM Tivoli SAN Manager implementation is public.

If you want to change the community name, follow these steps:

1. Open a Command Prompt window on the Server system.

2. Change to the following directory:

c:\tivoli\itsrm\manager\bin\w32-ix86

3. Enter the following commands:

setenvsrmcp SANDBParms set SNMPCommunityName=name

Where name is the community name you want to use for SNMP queries. For example, to change the SNMP community name to myname, enter the following command:

srmcp SANDBParms set SNMPCommunityName=myname

8.3 Introduction to IBM DirectorIBM Director is a management product for the systems administrator in small-to- medium-sized companies. IBM Director solves the problem of managing today’s Windows and Intel centric PC and LAN networks and addresses real system management issues, enabling you to focus on managing your primary business.

The IBM Director functions enable you to manage all aspects of the computing infrastructure, including software applications, network operating system (NOS) services, networks, and hardware.

IBM Director provides integrated management across the network, Internet workgroup control and management, and highly automated, almost unattended operation.

For a more detailed description, see the redbook Implementing System Management Solutions using IBM Director, SG24-6188.

In most customer environments, the IBM Director implementation already exists Therefore, in the following sections, we will show a simple configuration for forwarding events to IBM Director.

8.3.1 Event forwarding from IBM Tivoli SAN Manager to IBM DirectorAfter installing IBM Director on your system and before starting to receive traps from IBM Tivoli SAN Manager Server you need to set the trap destination to your IBM Director. The procedure for this is the same as described in “Setting up the SNMP trap destination in SAN Manager” on page 262.

Note: IBM Tivoli Storage Area Network Manager only supports one SNMP community name. A device can have several community names, but IBM Tivoli Storage Area Network Manager can only communicate with one of those names. Also, if the SNMP community name entered in the command is not a community name on the device, IBM Tivoli Storage Area Network Manager SNMP queries will time out. IBM Tivoli Storage Area Network Manager will not be able to communicate with the device.

Chapter 8. SNMP Event notification 263

The next step is to define the IBM Tivoli SAN Manager Server system in IBM Director. You can do this by accessing IBM Director Console as shown in Figure 8-4.

Figure 8-4 IBM Director Console

As you can see from our example, we defined our IBM Tivoli SAN Manager Server system — POLONIUM as an SNMP capable device.

If we want to see the SNMP trap events coming from our IBM Tivoli SAN Manager Server we simply drag the All events task, as shown in Figure 8-4, from the Tasks windows to the defined system. A window similar to Figure 8-5 is shown.

264 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 8-5 SNMP event from SAN Manager

As you can see in our example, there is an event showing that managed host TUNGSTEN was shut down.

IBM Director allows you to build event filters which can be then associated with actions, for example, sending an e-mail alert to the system administrator.

Chapter 8. SNMP Event notification 265

266 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 9. ED/FI - SAN Error Predictor

In this chapter we discuss the new ED/FI feature of IBM Tivoli Storage Area Network Manager (also known as SAN Error Predictor). We discuss how ED/FI operates, how it needs to be setup, and how its features can be utilized to efficiently manage SANs.

9

© Copyright IBM Corp. 2002, 2003. All rights reserved. 267

9.1 OverviewSANs are becoming more and more critical in the corporate infrastructure, therefore they should be made as highly available as possible, just like other IT components.

SANs are complex network environments, with potentially hundreds or even thousands of individual devices. Hardware outages cause disruptions to the business environment, leading to lost revenue and reduced customer satisfaction. Minimizing outages due to hardware failures is therefore a goal of SAN management and one way to do this is by predicting and detecting likely errors before they cause outages.

Typically, servers have multiple redundant paths to devices. Determining a root error cause in such an environment is usually problematic. Some of the most important factors in complex root cause analysis:

� Error data can be inconsistent and sparse� Complexity of error counter implementations� Error indications can be dispersed from the source - they can propagate across the SAN

Error Detection and Fault Isolation (ED/FI - SAN Error Predictor) is implemented in IBM Tivoli SAN Manager Version 1.2 to provide a way to predict errors on the optical links that are used to connect SAN components (including HBA to switch, switch to switch, and switch to storage connections.

ED/FI functions are listed in Figure 9-1.

Figure 9-1 ED/FI - SAN Error Predictor overview

By using Predictive Failure Analysis® (PFA), downtime of SAN components can be significantly decreased as it is possible to remove problematic components before failure. This can significantly reduce operational cost of SANs.

The ED/FI function collects data from IBM Tivoli SAN Manager agents, outband and/or inband as available. The polling interval is every 15 minutes. The data is stored in the ITSANMDB database.This data is then analyzed using various statistical methods and from this future errors are predicted.

The predicted errors are presented in the NetView interface by “adorning” the appropriate icons as shown in Figure 9-2. The adornment means that the exclamation point is superimposed on the icon representing the device where the error is predicted. A TEC event and SNMP trap are also generated.

ED/FI - SAN Error Predictor functionsED/FI - SAN Error Predictor functions

Proactive error prediction

Predictive Failure Analysis (PFA) based on Fibre Channel link counter data

Predict and isolate a potential link failure, giving the oportunity to:

reduce unscheduled downtimereduce scheduled downtime for isolation and resolution

Uses Statictical analyses for determining the cause of the problem (possible use of external rules)

268 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 9-2 Failure indication

Figure 9-3 shows an example of a failing device, in this case, the host SENEGAL. Although in this case, the icon is actually red, indicating a SAN Manager detected failure, note that typically, adorned icons will still show green, indicating they are available. This is because the ED/FI function is designed to flag potential problems before they have escalated to an actual failure. This allows you to replace hardware preemptively at a convenient time, rather than incurring an unplanned outage due to failure.

Figure 9-3 Adornment example

9.2 Error processingED/FI error processing is shown in Figure 9-4.

ED/FI Failure indicationED/FI Failure indicationSending a TEC event

Sending a SNMP trap

Through NetView GUI Adornment

Chapter 9. ED/FI - SAN Error Predictor 269

Figure 9-4 Error processing cycle

Data is collected from the following counters:

� FA MIB Counters� FE MIB Counters� Brocade Switch MIB Counters� HBA APIs (Request Port Status, Read Link Status) - inband only

Predictive Failure Analysis is build on a Stochastic model called Dispersion Frame Technique (DFT), which was developed and tested at Carnegie Mellon University. The method eliminates complexity through simple and effective pattern recognition of error occurrences. DFT involves a set of rules for predicting failures, based on the proximity of error occurrences to each other in time. ED/FI uses a set of these rules to determine when a set of counters exceeding a threshold will indicate an error. While the specific rules are internal to ED/FI, they are used to detect the difference between normal and abnormal behavior by using an increase in error rate and a decrease in time intervals between error occurrences. An example rule might be to trigger if a counter exceeds a threshold 3 times within a defined interval.

When the PFA process sees that counters have changed, along with previous data, it evaluates the counters. If the counter changes meet the criteria using DFT rules, an “indication” is created. An Indication Record is created for each port/counter/rule group. These indications are them passed on to the Fault Isolation process (FI).

The FI process analyzes the indications by further filtering the errors. FI also uses topology and attribute information provided by IBM Tivoli SAN Manager and with this data isolates faults to the specific Fibre Channel (FC) link. If all requirements are met, FI will create a Fault Record.

After a defined number of faults occurs (as defined in the FI rules), a Notification Record will be created. The Notification Record will be presented in NetView by adorning the

Note: Not all the switch vendors collect data on all the defined counters in the MIB schema. This depends on the particular implementation and adherence to the various standards. At the time of writing, the fullest ED/FI functionality is available on Brocade switches. Fewer counters are available for monitoring on other switch vendors.

SAN Error Predictor error processingSAN Error Predictor error processingAgents gather error counters and sends data to Manager

PFA takes counters that have changed along with previous data and evaluates if the counter changes meet the criteria to create an "indication".

Fault isolation looks for "indications" and then runs the data through “Rule sets". If indications match rules criteria a notification is created that results in a user viewable "Adornment" on the Netview GUI.

Manager looks for counters that have changed values

User can use this to perform specific corrective actions

270 IBM Tivoli Storage Area Network Manager: A Practical Introduction

corresponding device as shown in Figure 9-3 on page 269. The Notification Record is permanent and can only be removed with explicit user intervention (via the GUI).

When a user clears the adornment, a Cleared Record will be created in the ITSANMDB database and the device port will be set to a cleared state. If another fault occurs on the same port it may be immediately upgraded to a Notification.

The whole FI flow is shown in Figure 9-5.

Figure 9-5 Fault Isolation indication flow

Fault Isolation will adorn the transmitter of the link (rather than the sender), because it is most likely that the faulty component in the group of link, transmitter, cable and receiver, is the transmitter.

Note: (1) Switches cannot be adorned if inband agents are not active, except in the case of cascaded switches using outband management only. (2) Endpoint devices cannot be adorned if outband agents are not active.

9.3 Configuration for ED/FI - SAN Error PredictorED/FI is an integrated function of IBM Tivoli SAN Manager, and can be accessed from the standard menus. Select SAN -> ED/FI Configuration as shown in Figure 9-6.

Important: Error counters can also change for non error conditions including:

� Rebooting the system� Configuration changes� Clearing of counter manually

As Fault Isolation mechanism will count them as error conditions, it is recommended that Error Detection/Fault Isolation is disabled in such cases to avoid spurious adornments.

Fault Isolation indication flowFault Isolation indication flow

After successful isolation, FI will upgrade a PFA indication to fault

After a number of faults, defined by FI rules, a fault is upgraded to a notification

A notification adorns a device

Notifications can be cleared by users

A cleared notification can be upgraded again by FI if isolation requires

Indication

Fault

Notification

Cleared

FI Upgrade

FI UpgradeUser Input

FI Upgrade

Fault State Diagram

Indication

Fault

Notification

Cleared

FI Upgrade

FI UpgradeUser Input

FI Upgrade

Fault State Diagram

Chapter 9. ED/FI - SAN Error Predictor 271

Figure 9-6 ED/FI Menu Selection

You will see a window similar to Figure 9-7.

272 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 9-7 ED/FI Configuration

In this window you can enable or disable ED/FI using the Enable Error Detection and Fault Isolation radio button.

In the “Rule Set Selection” you can see the available rules and which rules are active. The active rules here are used in error processing as described in 9.2, “Error processing” on page 269. To see the notes for the specific rule select the rule and click View, you will see a window similar to Figure 9-8.

Tip: As stated in the window, it is recommended that you disable the error prediction in case of service actions so that false notifications can be avoided.

Chapter 9. ED/FI - SAN Error Predictor 273

Figure 9-8 Rule description

9.4 Using ED/FIAfter enabling ED/FI, it will start collecting the data required for error prediction. When the collected counters match the requirements from the FI rules, SAN Manager will adorn the corresponding icons similar to Figure 9-9.

274 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 9-9 Adornments on the topology map

In our example we simulated errors by disabling and enabling a port on the switch ITSOSW1 over a period of time.

As well as the graphical display of the adornments, they are also listed under SAN->ED/FI Configuration in the Properties tab as shown in Figure 9-10.

Figure 9-10 Devices currently in Notification State

Chapter 9. ED/FI - SAN Error Predictor 275

This window displays the list of potentially faulty SAN devices, using the following columns:

� Clear - check this box to clear the adornment on a particular device.

� Time - the time when the error was identified by FI rules.

� Faulted Device - the device which was predicted by FI to be failing. The rule here is that the device with the transmitter will be marked as failed, as explained in 9.2, “Error processing” on page 269. If the device has a IBM Tivoli SAN Manager agent installed and running it will appear with its Global Unique Identifier (GUID) similar to the first entry in Figure 9-10. If there is no agent running or the device is a switch, the device will be identified by its node WWN. In our example the fifth entry in Figure 9-10 is a server without an agent and the sixth is a switch.

� Faulted Port - if the device has several ports, the actual faulting port WWN will be displayed here.

� Indicated Device - the device which actually detected the errors. It is identified in the same way as the faulted device. Figure 9-11(which is simply Figure 9-10 scrolled to the right), shows an example.

� Indicated Port - if the device has several ports, the actual port WWN on which errors where detected will be displayed.

� PD Reference - the reference to Problem Determination guides which can be used by IBM Support to diagnose the problem (if it is an IBM-supported piece of hardware).

Figure 9-11 Indicated device

9.4.1 Searching for the faulted device on the topology mapAs we have seen, both the GUID and node and port WWNs are used to identify the notification records. In a medium to large SAN, the topology map is complex and adornment icons may not be readily located, given its GUID or WWN. To make identification easier, you can use the NetView search function to find adorned devices. First you need to identify the faulted device from the devices currently in notification state, as shown in Figure 9-10. As the notifications are persistent (until cleared), you should check the timestamp of the notification before searching to ensure it is still of interest. The device with that port can be found by selecting Edit - > Find from the NetView menus, as shown in Figure 9-12.

276 IBM Tivoli Storage Area Network Manager: A Practical Introduction

To find the object with the corresponding GUID or port WWN, enter it in the Object Name field. NetView uses both GUID and port WWNs for the Object Names. As the GUID and ports are usually uniquely identified by less then the whole numeric string, you can use wildcards, rather than the entire string, as shown in Figure 9-12.

Figure 9-12 NetView Search dialog

In our example we used the last four numbers of the GUID displayed in the first entry shown in Figure 9-10 on page 275. The search string is actually the least significant digits of the GUID, which is truncated in that figure. The full string for the GUID, including the searched string is displayed in Figure 9-15 on page 279. After entering the search string, click OK. The search results are displayed in Figure 9-13.

Figure 9-13 Found objects

If you double-click on a returned object, NetView will open the topology map, highlighting the device, as shown in Figure 9-14. We can see the notification is for the host SENEGAL, which is adorned.

Chapter 9. ED/FI - SAN Error Predictor 277

Figure 9-14 Found device on topology map

Now you can clearly see where the faulted device is located in the SAN, and you can start planning the necessary action to diagnose or repair the faulting device.

ED/FI isolates faults only to the link level. Therefore, either side of the link or the cable itself might be the faulty component. Before replacing hardware, you should consult your service contracts and product problem determination guides for direction. Cleaning, cable seating, and diagnostic execution are some of the steps that might be recommended that lead to a definitive decision on parts repair or replacement. IBM Service can use ED/FI information in conjunction with problem determination guides to advise what/if part replacements are necessary.

If you can identify a component, you should diagnose the problem and repair or replace the component as soon as possible before a permanent failure occurs. If you cannot identify a component, at a minimum you should monitor the link for further errors. In environments where high systems availability is a requirement or service level agreements are in place, you can contact service representatives about replacing the Fibre Channel component.

9.4.2 Removing notificationsAfter the fault has been fixed the notification should be removed, so that the notification lists and topology maps stay current. To remove a notification, access the current device notification list using SAN -> ED/FI Configuration. Select the Properties tag, which will open the current list of device notifications as shown in Figure 9-10 on page 275.

To remove a notification, check the Clear box and click Apply as shown in Figure 9-15.

278 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 9-15 Clear the notification

In Figure 9-16 you can see that the selected entry is now removed.

Figure 9-16 After clearing the notification

The removal is also reflected in the topology map as shown in Figure 9-17. The host SENEGAL is no longer adorned.

Chapter 9. ED/FI - SAN Error Predictor 279

Figure 9-17 Topology change after notification clearance

280 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Part 5 Maintenance

In Part 5 we provide information on keeping your IBM Tivoli SAN Manager environment healthy. First we describe how to back up each component, including the application files and the database repository, then we present the logging and tracing facilities for problem diagnosis provided with the product.

Part 5

© Copyright IBM Corp. 2002, 2003. All rights reserved. 281

282 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 10. Protecting the IBM Tivoli SAN Manager environment

In this chapter we discuss backup and restore strategies to put in place to protect the IBM Tivoli SAN Manager environment. While there are many different backup products available, we choose to focus on IBM Tivoli Storage Manager. We assume you have knowledge of IBM Tivoli Storage Manager, which can be obtained from the following IBM Redbooks:

� IBM Tivoli Storage Management Concepts, SG24-4877� IBM Tivoli Storage Manager Implementation Guide, SG24-5416� Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141� Backing Up DB2 Using Tivoli Storage Manager, SG24-6247

10

© Copyright IBM Corp. 2002, 2003. All rights reserved. 283

10.1 IBM Tivoli SAN Manager environmentIBM Tivoli SAN Manager relies on five main components, shown in Figure 10-1. Each component stores configuration data in text files and/or in databases. In the following sections we describe each component and explain where it stores its configuration information.

Figure 10-1 IBM Tivoli SAN Manager components

10.1.1 IBM Tivoli NetViewNetView stores its configuration in flat files and internal databases in the directory \usr\ov\conf\.

The databases mainly contain information about the current topology and objects properties. From an IBM Tivoli SAN Manager point of view, this information is temporary and will be rebuilt at the next scheduled or event-driven discovery.

10.1.2 Embedded IBM WebSphere Application ServerThe embedded IBM WebSphere stores its configuration:

� In flat files in the directories:

– \tivoli\itsanm\manager\apps\was\properties – \tivoli\itsanm\manager\apps\was\config

10.1.3 IBM Tivoli SAN Manager ServerIBM Tivoli SAN Manager Server stores its configuration in

� flat files in the directories:

– \tivoli\itsanm\manager\conf\ – \tivoli\itsanm\manager\apps\manager.ear

� the ITSANMDB DB2 database

The configuration files contain information including the polling interval, the manager ports, the license key, the database name, user ID and password, and the log format.

The ITSANMDB database contains information about the configured inband and outband agents, the discovered devices and all the information they have reported on polling which is used to create the topology display. As this is the core repository for IBM Tivoli SAN Manager, we focus on the protection of this database.

IBM Tivoli SAN Manager ComponentsIBM Tivoli Netview

embedded IBM WebSphere Application Server

IBM Tivoli SAN Manager manager

IBM Tivoli SAN Manager agent

Note: There is no additional protection for the embedded IBM WebSphere Application Server needed. This has changed with IBM Tivoli SAN Manager Version 1.2, since it uses the embedded IBM WebSphere Application Server version 5.0.

284 IBM Tivoli Storage Area Network Manager: A Practical Introduction

10.1.4 IBM Tivoli SAN Manager AgentsAll inband Agents store their configuration in flat files located in \tivoli\itsanm\agent\conf directory.

10.2 IBM Tivoli Storage Manager integrationIBM Tivoli Storage Manager is an enterprise-wide storage management application for the network. It provides automated storage management services (including backup and restore, archive and retrieve, hierarchical space management, and disaster recovery) to multi-vendor workstations, personal computers, mobile laptops, and servers of all sizes and operating systems, which are connected via WAN, LAN, and SAN. See Figure 10-2.

Figure 10-2 Tivoli Storage Manager integration with Tivoli SAN Manager

10.2.1 IBM Tivoli Storage ManagerIBM Tivoli Storage Manager includes these components:

� Server, which acts as the repository for all backups and maintains the backup policies and schedules

� Clients, which back up data to the Tivoli Storage Manager server

� API, which is available to other applications to allow them to interface to Tivoli Storage Manager

The IBM Tivoli Storage Management solution set also includes the following client programs:

� IBM Tivoli Storage Manager for Databases, IBM Tivoli Storage Manager for ERP, IBM Tivoli Storage Manager for Application Servers, IBM Tivoli Storage Manager for Mail, IBM Tivoli Storage Manager for Hardware — which use the API to provide specialized application backup

� Tivoli Space Manager for hierarchical space management (HSM)

config files

DB2 databases

TSM B/A client

DB2 utility

TSM API

TSM storage pools

Tivoli SAN Manager

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 285

Normal flat files on the Tivoli SAN Manager manager can be backed up using the Tivoli Storage Manager Backup/Archive client for Windows 2000. DB2 has already integrated the Tivoli Storage Manager API code to facilitate database backup. DB2 provides its own backup utility which allows both full database as well as individual tablespace backup. The backup utility can be set up to use Tivoli Storage Manager as the backup repository, as you will see later. Therefore, the two client types (Backup/Archive client for flat files, API client for DB2 backup) work together to provide full data protection for your Tivoli SAN Manager environment.

The API client and the Tivoli Storage Manager Backup/Archive client can run simultaneously on the same DB2 server, however, they are totally separate clients as far as the Tivoli Storage Manager server is concerned and we will configure them separately.

10.2.2 Setup for backing up IBM Tivoli SAN Manager ServerWe will use the following environment for backing up our Tivoli SAN Manager Server system to a Tivoli Storage Manager server (see Figure 10-3):

� Tivoli Storage Manager Server for AIX, V5.2.0 - BANDA� Tivoli Storage Manager Backup/Archive Client for Windows 2000, V5.2.0 - LOCHNESS� Tivoli Storage Manager API client for Windows 2000, V5.2.0� Tivoli Storage Manager Backup/Archive Client for AIX 5.1 V5.2.0 (for agent BANDA)

Figure 10-3 Sample environment: Backing up Tivoli SAN Manager to Tivoli Storage Manager

Here is a summary of the setup steps:

1. Configure the Tivoli Storage Manager server to receive backups from the Tivoli SAN Manager Server

2. Configure the API and Backup/Archive clients on the Tivoli SAN Manager Server

10.2.3 Tivoli Storage Manager server configurationWe assume that:

� The Tivoli Storage Manager server is installed and configured with enough storage.

� The Tivoli Storage Manager Backup/Archive and API client code is installed on the IBM Tivoli SAN Manager Server.

� Appropriate backup policies (policy domain, management classes, copy groups) for non-DB2 backups (that is, flat files) have been implemented. You should be doing

BANDAAIX 5.1 ML4

Tivoli SAN Manager

DB2 V7.2 FP8NetView

TSM Client 5.2.0TSM API 5.2.0

TSM Server 5.2.0

Tivoli SAN AgentTSM Client 5.2.0

Ethernet

LOCHNESSWindows2000 SP3

286 IBM Tivoli Storage Area Network Manager: A Practical Introduction

operating system-level backups of the Windows Server or AIX V5.1 Server which runs the Tivoli SAN Manager code.

We need to specify a management class and copy group within a policy domain for DB2 backups. We recommend defining a separate policy domain for the DB2 backups. We will define a domain called DB2_DOMAIN and register the nodename assigned to the DB2 backup client (in our case, LOCHNESS_DB2) to it.

DB2 places special requirements on the management class. Each DB2 database backup is stored as a unique object in the Tivoli Storage Manager server, by specifying a time stamp as part of the low level qualifier (LL_NAME). This means that the DB2 backups must be manually inactivated. This also means that the management class that the backup objects are bound to should have retention settings that change the inactivated backup objects to be expired immediately. The retention settings for a backup copy group that would provide this is RETONLY=0 and VERDELETED=0.

Example 10-1 shows typical Tivoli Storage Manager commands used to define a suitable environment for DB2 backups. We define a policy domain, policy set, management class, and copy groups for the DB2 environment. We activate the policy set and register our client node to the policy domain. We are using a storage pool called BACK_LTO as the destination for our DB2 backups.

Example 10-1 Definition of Tivoli Storage Manager environment for DB2 backups

DEFINE DOMAIN DB2_DOMAIN DESCRIPTION="Domain for DB2 backups" BACKRETENTION=30 ARCHRETENTION=365

DEFINE POLICYSET DB2_DOMAIN DB2_POLICY DESCRIPTION="DB2 BACKUPS Policyset"

DEFINE MGMTCLASS DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS DESCRIPTION="Mgmtclass for DB2 databases" SPACEMGTECHNIQUE=NONE AUTOMIGNONUSE=0 MIGREQUIRESBKUP=YES

DEFINE COPYGROUP DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS DESTINATION=BACK_LTO FREQUENCY=0 VEREXISTS=1 VERDELETED=0 RETEXTRA=0 RETONLY=0 MODE=MODIFIED SERIALIZATION=SHRSTATIC

DEFINE COPYGROUP DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS TYPE=ARCHIVE DESTINATION=ARCHIVEPOOL RETVER=NOLIMIT SERIALIZATION=SHRSTATIC

ASSIGN DEFMGMTCLASS DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS

ACTIVATE POLICYSET DB2_DOMAIN DB2_POLICY

REGISTER NODE LOCHNESS_DB2 LOCHNESS_DB2 DOMAIN=DB2_DOMAIN ARCHDELETE=YES BACKDELETE=YES USERID=NONE

The following parameters for the backup copygroup were set:

� VEREXISTS=1 to keep only one version of the backup file as the name of each DB2 backup is unique. (There will never be a newer version of the backup image with the same name).

� VERDELETED=0 so that if the backup file has been deleted (via db2adutl), then Tivoli Storage Manager should not keep an inactive version of this file.

� RETEXTRA=0 (the same value as RETONLY) parameter will never be used as you will never have more than one version of the backup file. To prevent confusion set this parameter to the same value as RETONLY.

� RETONLY=0 so that when a backup image file becomes inactive it will be purged from the Tivoli Storage Manager server at the next expiration.

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 287

10.2.4 Tivoli Storage Manager client configurationThe client configuration takes place on the Tivoli SAN Manager Manager, since this will be the Tivoli Storage Manager client. For Tivoli SAN Manager Agents, you should perform regular backups using the Tivoli Storage Manager Backup/Archive client. No special considerations for Tivoli SAN Manager should be necessary.

Tivoli Storage Manager nodenamesThe IBM Tivoli SAN Manager will be known to Tivoli Storage Manager by two different nodenames for non-DB2 backups and DB2 backups respectively. We defined nodenames LOCHNESS (for the Backup/Archive client) in the STANDARD policy domain and nodename LOCHNESS_DB2 (for DB2 backups). Example 10-2 shows the server QUERY NODE command to display currently configured clients.

Example 10-2 Tivoli Storage Manager clients list

tsm: BANDA>query node lochness*

Node Name Platform Policy Domain Days Since Days Since Locked? Name Last Acce- Password ss Set------------------------- -------- -------------- ---------- ---------- -------LOCHNESS WinNT STANDARD <1 6 NoLOCHNESS_DB2 DB2/NT DB2_DOMAIN 1 6 No

DB2 configurationNow, DB2 needs to be configured to use the right user name, password and management class as shown in Example 10-3, which uses the DB2 command line interface.

This can be achieved in two ways. Either define these parameters within DB2 as shown in Example 10-3, or use the information taken from the Tivoli Storage Manager options file and default settings that were defined in 10.2.3, “Tivoli Storage Manager server configuration” on page 286.

Example 10-3 DB2 configuration

db2 => update db cfg for ITSANMDB using TSM_MGMTCLASS DB2_MGMTCLASSDB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.DB21026I For most configuration parameters, all applications must disconnectfrom this database before the changes become effective.

db2 => update db cfg for ITSANMDB using TSM_OWNER LOCHNESS_DB2DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.DB21026I For most configuration parameters, all applications must disconnectfrom this database before the changes become effective.

db2 => update db cfg for ITSANMDB using TSM_NODENAME LOCHNESS_DB2DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.DB21026I For most configuration parameters, all applications must disconnectfrom this database before the changes become effective.

db2 => update db cfg for ITSANMDB using TSM_PASSWORD LOCHNESS_DB2DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.DB21026I For most configuration parameters, all applications must disconnectfrom this database before the changes become effective.

db2 => get db cfg for ITSANMDB.

288 IBM Tivoli Storage Area Network Manager: A Practical Introduction

.

.Number of database backups to retain (NUM_DB_BACKUPS) = 12 Recovery history retention (days) (REC_HIS_RETENTN) = 366

TSM management class (TSM_MGMTCLASS) = DB2_MGMTCLASS TSM node name (TSM_NODENAME) = LOCHNESS_DB2 TSM owner (TSM_OWNER) = LOCHNESS_DB2 TSM password (TSM_PASSWORD) = *****

db2 => quit

In either case you will need to set up some operating system environment variables so that the Tivoli Storage Manager API is able to find the Tivoli Storage Manager options file and knows where to write log files. These environment variables are shown in Example 10-4.

Example 10-4 Tivoli Storage Manager environment variables System wide entries

DSMI_CONFIG=c:\tivoli\tsm\api\db2_dsm.optDSMI_DIR=c:\tivoli\tsm\apiDSMI_LOG=c:\tivoli\tsm\api

Now, configure DB2 for ONLINE backups if required. This is set by the LOGRETAIN parameter. Example 10-5 shows the commands.

Example 10-5 Configure for online backup

db2 => get db cfg for ITSANMDB..Log retain for recovery enabled (LOGRETAIN) = OFF..db2 => update db cfg for ITSANMDB using LOGRETAIN RECOVERYDB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.DB21026I For most configuration parameters, all applications must disconnectfrom this database before the changes become effective.

db2 => quitDB20000I The QUIT command completed successfully.

Tip: We used a different client option file, called DB2_DSM.OPT, to save our DB2 environment. To “inform” our DB2 environment, you have to define all the DSMI_ variables to the system. If you should choose this simpler way, you do not have to add the TSM entries into the DB2 configuration of the database ITSANMDB as shown in Example 10-3, TSM_MGMTCLASS, TSM_NODENAME, TSM_OWNER, TSM_PASSWORD. If you have this entry in the DB2 configuration, you can remove the with the following commands:

update db cfg for ITSANMDB using TSM_MGMTCLASS ‘’

update db cfg for ITSANMDB using TSM_OWNER ‘’

update db cfg for ITSANMDB using TSM_NODENAME ‘’

update db cfg for ITSANMDB using TSM_PASSWORD ‘’

Otherwise define them into the System variables as shown in Example 10-4.

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 289

C:\PROGRA~1\SQLLIB\BIN>db2stop forceSQL1064N DB2STOP processing was successful.

C:\PROGRA~1\SQLLIB\BIN>db2startSQL1063N DB2START processing was successful.

Storing API passwordExample 10-6 shows how to configure these parameters into the Tivoli Storage Manager API client, using the dsmapipw command.

Example 10-6 Configuring DB2 backup password to Tivoli Storage Manager API client

C:\Program Files\SQLLIB\adsm>dsmapipw

************************************************************** Tivoli Storage Manager ** API Version = 5.2.0 **************************************************************Enter your current password:lochness_db2Enter your new password:lochness_db2Enter your new password again:lochness_db2Your new password has been accepted and updated.

Stop and re-start DB2 to allow the changes to take effect (Example 10-7).

Example 10-7 Stop and start DB2

C:\PROGRA~1\SQLLIB\BIN>db2stopSQL1064N DB2STOP processing was successful.

C:\PROGRA~1\SQLLIB\BIN>db2startSQL1063N DB2START processing was successful.

Client option filesYou must now configure the Tivoli Storage Manager API client option file, db2_dsm.opt located in C:\Tivoli\tsm\api\ so that DB2 will point to the correct Tivoli Storage Manager server (Example 10-8).

Example 10-8 API dsm.opt file sample

NODENAME LOCHNESS_DB2TCPSERVERADDRESS banda.almaden.ibm.com

As the DB2 database files are backed up using DB2, they must be excluded from backup by the normal Backup/Archive client. We excluded all DB2 files except the RECOVERY LOG files. You must update the dsm.opt file located in C:\Tivoli\tsm\baclient\ directory (Example 10-9).

Example 10-9 baclient dsm.opt file sample

NODENAME LOCHNESSPASSWORDACCESS GENERATETCPSERVERADDRESS banda.almaden.ibm.com

EXCLUDE C:\DB2\...\*

290 IBM Tivoli Storage Area Network Manager: A Practical Introduction

INCLUDE C:\DB2\...\*.LOG

10.2.5 Additional considerationsThe previous section showed how to perform a basic configuration for Tivoli Storage Manager so that DB2 backups are sent directly to a Tivoli Storage Manager server. However, there are some additional considerations:

� DB2 archive logs are generated on local disk. They must be protected against loss through mirroring or manual archival. You can also activate a user exit to automatically archive DB2 logs to Tivoli Storage Manager.

� Old database backups must be manually deleted from the Tivoli Storage Manager server once they are not needed using the db2adutl utility.

� Depending on your recovery requirements, you may have to configure additional DB2 parameters (such as NUM_DB_BACKUPS and REC_HIS_RETENTN).

See the redbook Backing Up DB2 Using Tivoli Storage Manager, SG24-6247 for detailed information on setting up DB2 backups with Tivoli Storage Manager.

10.3 Backup proceduresWe now describe the procedures for backing up the major components of IBM Tivoli SAN Manager, summarized in Figure 10-4.

Figure 10-4 Procedures used to backup IBM Tivoli SAN Manager

10.3.1 Agent filesThe configuration files on the Tivoli SAN Manager Agent contain relatively static information. Therefore, we recommend using a traditional incremental backup policy (with the appropriate Tivoli Storage Manager Backup/Archive Client) to backup the files. We show backup of an AIX Agent using the Tivoli Storage Manager Backup/Archive Client in Example 10-10. Our example shows a scheduled Tivoli Storage Manager Client backup.

Example 10-10 Backup of agent files

root@banda> dsmc q sessionTivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.0

IBM Tivoli SAN Manager AgentsIncremental backup of files

IBM Tivoli SAN Manager ServerStop of applications : NetView, embedded WebSphere Application Server

Incremental backup of files

Start of applications

IBM Tivoli SAN Manager databaseDB2 backup command

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 291

(C) Copyright IBM Corporation 1990, 2003 All Rights Reserved. Node Name: BANDAPlease enter your user id <BANDA>:

Please enter password for user id "BANDA":

Node Name: BANDASession established with server BANDA: AIX-RS/6000 Server Version 5, Release 2, Level 0.0 Data compression forced on by the server Server date/time: 06/03/03 14:23:51 Last access: 06/03/03 14:23:30

.... <information omitted>Session established with server BANDA: AIX-RS/6000 Server Version 5, Release 2, Level 0.0 Data compression forced on by the server Server date/time: 05/29/03 17:36:25 Last access: 05/29/03 16:06:15

ITSAN Manager backup initiated by TSM scheduler.

05/29/03 16:05:47 The Scheduler is under the control of the TSM Scheduler Daemon05/29/03 16:05:47 Scheduler has been started by Dsmcad.05/29/03 16:05:47 Querying server for next scheduled event.05/29/03 16:05:47 Node Name: BANDA05/29/03 16:05:47 Session established with server BANDA: AIX-RS/600005/29/03 16:05:47 Server Version 5, Release 2, Level 0.005/29/03 16:05:47 Data compression forced on by the server05/29/03 16:05:47 Server date/time: 05/29/03 16:05:47 Last access: 05/29/03 15:59:37Executing scheduled command now.05/29/03 16:05:47 Incremental backup of volume '/'05/29/03 16:05:47 Incremental backup of volume '/usr'05/29/03 16:05:47 Incremental backup of volume '/var'05/29/03 16:05:47 Incremental backup of volume '/home'05/29/03 16:05:47 Incremental backup of volume '/opt'..ANS1898I ***** Processed 28,000 files *****.05/29/03 16:05:57 Normal File--> 0 /opt/tivoli/itsanm/agent/InbandEvents [Sent] 05/29/03 16:05:57 Normal File--> 748 /opt/tivoli/itsanm/agent/agentLog.txt [Sent] 05/29/03 16:05:57 Normal File--> 1,155 /opt/tivoli/itsanm/agent/ibmchanges.txt [Sent] 05/29/03 16:05:57 Normal File--> 2,201 /opt/tivoli/itsanm/agent/ibmchanges.zip [Sent] 05/29/03 16:05:57 Normal File--> 34,799 /opt/tivoli/itsanm/agent/license.txt [Sent] 05/29/03 16:05:57 Normal File--> 8,733 /opt/tivoli/itsanm/agent/log.txt [Sent] 05/29/03 16:05:57 Normal File--> 41 /opt/tivoli/itsanm/agent/setacc.sh [Sent] 05/29/03 16:05:57 Normal File--> 330,209 /opt/tivoli/itsanm/agent/_uninst/uninstall [Sent] 05/29/03 16:05:57 Normal File--> 28,483 /opt/tivoli/itsanm/agent/_uninst/uninstall.dat [Sent] 05/29/03 16:05:58 Normal File--> 4,182,045 /opt/tivoli/itsanm/agent/_uninst/uninstall.jar [Sent]

292 IBM Tivoli Storage Area Network Manager: A Practical Introduction

05/29/03 16:05:58 Directory--> 512 /opt/tivoli/itsanm/agent/bin/aix [Sent] 05/29/03 16:05:58 Directory--> 512 /opt/tivoli/itsanm/agent/bin/aix/en_US [Sent] 05/29/03 16:05:58 Normal File--> 347 /opt/tivoli/itsanm/agent/bin/aix/.toc [Sent] ... <information omitted>Successful incremental backup of '/opt'.05/29/03 16:06:15 Total number of objects inspected: 28,19105/29/03 16:06:15 Total number of objects backed up: 4,25505/29/03 16:06:15 Total number of objects updated: 005/29/03 16:06:15 Total number of objects rebound: 005/29/03 16:06:15 Total number of objects deleted: 005/29/03 16:06:15 Total number of objects expired: 005/29/03 16:06:15 Total number of objects failed: 005/29/03 16:06:15 Total number of bytes transferred: 54.75 MB05/29/03 16:06:15 Data transfer time: 0.22 sec05/29/03 16:06:15 Network data transfer rate: 247,479.37 KB/sec05/29/03 16:06:15 Aggregate data transfer rate: 2,003.16 KB/sec05/29/03 16:06:15 Objects compressed by: 23%05/29/03 16:06:15 Elapsed processing time: 00:00:27

10.3.2 Server filesWe used the standard Tivoli Storage Manager Backup/Archive Windows 2000 Client to execute a daily incremental backup of all the files, including NetView files residing on the Server as shown below. Operating system components, such as the Windows registry, are also backed up. To run our backups, we created and used the following scripts to stop the applications before running backup, then restart them after the backup.

ITSANMstopall The script ITSANMstopall stops all the applications, including NetView and the Tivoli SAN Manager Server application via WebSphere Application Server. This script calls another script, ITSANMstop (Example 10-11).

Example 10-11 ITSANMstopall script

@REM Stop the Netview Application@REM ----------------------------@echo "Stopping Netview"ovstopnet stop "Tivoli Netview Service"

@REM Stop the ITSANM-Manager @REM ------------------------@echo "Stopping the IBM WebSphere Application Server V5 - ITSANM-Manager"call ITSANMstop.bat

ITSANMstopThe script ITSANMstop stops just the Tivoli SAN Manager WebSphere application (Example 10-12).

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 293

Example 10-12 ITSANMstop script

@REM Stop the Application ITSANM-Manager@REM -----------------------------------@echo "Stopping the ITSANM-Manager"net stop "IBM WebSphere Application Server V5 - ITSANM-Manager

ITSANMstartall The script ITSANMstartall re-starts both NetView and the Tivoli SAN Manager Server WebSphere application (Example 10-13). This script calls another script, ITSANMstart.

Example 10-13 ITSANMstartall script

@REM Start the Netview Application@REM ----------------------------@echo "Starting Netview"net start "Tivoli Netview Service"ovstart

@REM Start the ITSANM-Manager @REM -------------------------@echo "Starting the ITSANM-Manager ..."call ITSANMstart.bat

ITSANMstartThe script ITSANMstart starts just the Tivoli SAN Manager WebSphere application (Example 10-14).

Example 10-14 ITSANMstart application

@ECHO ON@REM Start WAS ITSANM-Manager Application@REM ------------------------------------@echo "Starting the ITSANM-Manager ..."net start "IBM WebSphere Application Server V5 - ITSANM-Manager"

Running the backupThe output of the backup procedure, using the scripts just listed, is shown in Example 10-15.

We used the Tivoli Storage Manager scheduler to incrementally all the IBM Tivoli SAN Manager files. When you are using this approach you can specify to run the script ITSANMstopall.bat before the scheduled event stops (using the PRESCHEDULECMD parameter), and to run the script ITSANMstartall.bat at the end of the scheduled event (using the POSTSCHEDULECMD parameter). These two entries can be added into DSM.OPT File of the backup client.

Example 10-15 Backup of server files

C:\bkupscripts>ITSANMstopall"Stopping Netview"

C:\bkupscripts>ovstopDone

C:\bkupscripts>net stop "Tivoli Netview Service".The Tivoli NetView Service service was stopped successfully.

294 IBM Tivoli Storage Area Network Manager: A Practical Introduction

"Stopping the ITSANM-Manager"

C:\bkupscripts>call ITSANMstop.bat"Stopping the ITSANM-Manager"

C:\bkupscripts>net stop "IBM WebSphere Application Server V5 - ITSANM-Manager"The IBM WebSphere Application Server V5 - ITSANM-Manager service was stoppedsuccessfully.

More help is available by typing NET HELPMSG 2186.

C:\bkupscripts>cd C:\Program files\tivoli\tsm\baclient.C:\Tivoli\tsm\baclient>dsmc incIBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.0 (c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: LOCHNESSSession established with server BANDA: AIX-RS/6000 Server Version 5, Release 2, Level 0.0 Server date/time: 05/30/2003 16:45:11 Last access: 05/30/2003 16:20:09

Incremental backup of volume '\\LOCHNESS\C$'

Incremental backup of volume 'SYSTEMOBJECT'Backup System Object: 'COM+ Database'.Backup System Object: 'Event Log'.Backup System Object: 'System and Boot Files'.Backup System Object: 'Registry'.Backup System Object: 'RSM Database'.Backup System Object: 'WMI Database'.

Directory--> 0 \\lochness\c$\ [Sent]

05/29/2003 16:25:32 Normal File--> 1,032,192 \\lochness\c$\DB2\NODE0000\SQL00002\SQLOGDIR\S0000041.LOG [Sent] 05/29/2003 16:25:34 Normal File--> 1,032,192 \\lochness\c$\DB2\NODE0000\SQL00002\SQLOGDIR\S0000042.LOG [Sent] 05/29/2003 16:25:35 ANS1898I ***** Processed 500 files *****05/29/2003 16:25:35 Normal File--> 1,032,192 \\lochness\c$\DB2\NODE0000\SQL00002\SQLOGDIR\S0000043.LOG [Sent] 05/29/2003 16:25:37 Normal File--> 1,032,192 \\lochness\c$\DB2\NODE0000\SQL00002\SQLOGDIR\S0000044.LOG [Sent]05/29/2003 16:45:32 Directory--> 0 \\lochness\c$\tivoli\itsanm\manager\conf\TIVINV [Sent] 05/29/2003 16:45:32 Normal File--> 30 \\lochness\c$\tivoli\itsanm\manager\conf\ATMS.properties [Sent] 05/29/2003 16:45:32 Normal File--> 11,562 \\lochness\c$\tivoli\itsanm\manager\conf\DataStore.defaults [Sent] 05/29/2003 16:45:32 Normal File--> 17,532 \\lochness\c$\tivoli\itsanm\manager\conf\DataStore.properties [Sent] 05/29/2003 16:45:32 Normal File--> 239 \\lochness\c$\tivoli\itsanm\manager\conf\edfi.properties [Sent] 05/29/2003 16:45:32 Normal File--> 44 \\lochness\c$\tivoli\itsanm\manager\conf\internal.properties [Sent] 05/29/2003 16:45:32 Normal File--> 20,955 .\\lochness\c$\usr\ov\snmp_mibs\ibm-midlevelmgr.mib [Sent] 05/29/2003 17:06:08 Normal File--> 9,032 \\lochness\c$\usr\ov\snmp_mibs\ibm-nv6ksubagent.mib [Sent]

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 295

... ... <information omitted>05/29/2003 17:47:25 --- SCHEDULEREC STATUS BEGIN05/29/2003 17:47:25 Total number of objects inspected: 70,94205/29/2003 17:47:25 Total number of objects backed up: 39,53605/29/2003 17:47:25 Total number of objects updated: 005/29/2003 17:47:25 Total number of objects rebound: 005/29/2003 17:47:25 Total number of objects deleted: 005/29/2003 17:47:25 Total number of objects expired: 005/29/2003 17:47:25 Total number of objects failed: 1005/29/2003 17:47:25 Total number of bytes transferred: 3.10 GB05/29/2003 17:47:25 Data transfer time: 4,744.76 sec05/29/2003 17:47:25 Network data transfer rate: 686.56 KB/sec05/29/2003 17:47:25 Aggregate data transfer rate: 653.76 KB/sec05/29/2003 17:47:25 Objects compressed by: 0%05/29/2003 17:47:25 Elapsed processing time: 01:23:0205/29/2003 17:47:25 --- SCHEDULEREC STATUS END

C:\Program files\tivoli\tsm\baclient>cd C:\bkupscripts

C:\bkupscripts>ITSANMstartall"Starting Netview"

C:\bkupscripts>net start "Tivoli Netview Service"The Tivoli NetView Service service is starting.....The Tivoli NetView Service service was started successfully.

C:\bkupscripts>ovstartDone"Starting the ITSANM-Manager server"

C:\bkupscripts>call ITSANMstart.bat"Starting the ITSANM-Manager ..."

C:\bkupscripts>net start "IBM WebSphere Application Server V5 - ITSANM-Manager"

The IBM WebSphere Application Server V5 - ITSANM-Manager service is starting.............The IBM WebSphere Application Server V5 - ITSANM-Manager service was startedsuccessfully.

C:\bkupscripts>

10.3.3 ITSANMDB DatabaseDepending on the availability you require from the IBM Tivoli SAN Manager Server, you can choose between online and offline backups of the DB2 database. Offline backup will require a shutdown of the DB2 database, which implies a shutdown of both the IBM Tivoli SAN Manager WebSphere application. We explain here the basic configuration of DB2 needed to backup the database and how to integrate this with Tivoli Storage Manager.

296 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Offline backupAn offline backup will run only if the database is not currently in use. You must stop the database or at least close all connections. In our case, we do not have to stop the database, since IBM Tivoli SAN Manager is the only application using it. Check this using the DB2 command shown in Example 10-16. We then stop the IBM Tivoli SAN Manager application, which will close all active connections to the ITSANMDB database.

Example 10-16 Active connections to ITSANMDB database

C:\bkupscripts>db2cmd.exe /c /w /i db2 list applications for database itsanmdb

Auth Id Application Appl. Application Id DB # of Name Handle Name Agents

-------- -------------- ---------- ------------------------------ -------- -----DB2USER1 java.exe 70 *LOCAL.DB2.030603221517 ITSANMDB 1DB2USER1 java.exe 85 *LOCAL.DB2.030603221532 ITSANMDB 1DB2USER1 java.exe 86 *LOCAL.DB2.030603221533 ITSANMDB 1DB2USER1 java.exe 87 *LOCAL.DB2.030603221534 ITSANMDB 1DB2USER1 java.exe 88 *LOCAL.DB2.030603221535 ITSANMDB 1DB2USER1 java.exe 89 *LOCAL.DB2.030603221536 ITSANMDB 1DB2USER1 java.exe 92 *LOCAL.DB2.030603221539 ITSANMDB 1DB2USER1 java.exe 93 *LOCAL.DB2.030603221540 ITSANMDB 1DB2USER1 java.exe 94 *LOCAL.DB2.030603221541 ITSANMDB 1DB2USER1 java.exe 95 *LOCAL.DB2.030603221542 ITSANMDB 1DB2USER1 java.exe 96 *LOCAL.DB2.030603221543 ITSANMDB 1

C:\bkupscripts>net stop "IBM WebSphere Application Server V5 - ITSANM-Manager"

C:\bkupscripts>db2cmd.exe /c /w /i db2 list applications for database itsanmdbSQL1611W No data was returned by Database System Monitor. SQLSTATE=00000

You can see that after stopping the application, message SQL1611W is returned by db2 list applications for database itsanmdb, which means that no connections are active on the database.

The backup script, ITSANMBackupOffline, shown in Example 10-17, performs the following operations:

1. Stops the Tivoli SAN Manager WAS application2. Runs a backup of ITSANMDB database.3. Starts the Tivoli SAN Manager WAS application.

Example 10-17 ITSANMBackupOffline — offline backup script for ITSANM database

@REM Stop the Netview Application@REM ----------------------------

Note: Refer to the following documentation for detailed information about DB2 protection and Tivoli Storage Manager integration:

� IBM Redbook, Backing Up DB2 Using Tivoli Storage Manager, SG24-6247

� IBM DB2 Universal Database - Administration Guide: Implementation - Version 7, SC09-2944

� IBM DB2 Universal Database - Command Reference - Version 7, SC09-2951

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 297

@echo "Stopping Netview"ovstop

@ECHO ON@REM Stop the Application ITSANM DB@REM ------------------------------call ITSANMstop.bat

@ECHO ON@REM Get Status and check if Stopped@REM -------------------------------net start | findstr /i "ITSANM-Manager”@if %errorlevel% EQU 0 GOTO BACKUPDB

:NOTSTOPPED@ECHO ON@REM ITSANM not stopped - Backup cannot run@REM --------------------------------------@echo "WAS Application ITSANM Not Stopped !!!"@echo "Backup process cancelled "exit 1

:BACKUPDB@ECHO ON@REM ITSANM is stopped - Backup can run@REM ----------------------------------@echo "Backup of ITSANMDB starting ....."C:\PROGRA~1\SQLLIB\BIN\db2cmd.exe /c /w /i db2 backup database ITSANMDB USE TSM@if %errorlevel% NEQ 0 echo "Backup failed - Please check error messages"

@REM Backup completed - Start ITSANM@REM -------------------------------:STARTITSANMcall ITSANMstart.bat

@ECHO ON@REM Get Status and check if Started@REM -------------------------------net start | findstr /i "ITSANM-Manager"@if %errorlevel% EQU 0 GOTO STARTOK

@REM ITSANM not started @REM ------------------@echo "Application ITSANM Not Started !!!"exit 1

@REM ITSANM started @REM --------------:STARTOK@echo "Application ITSANM started successfully"

@REM Start the Netview Application@REM -----------------------------@echo "Starting Netview"ovstart

exit

298 IBM Tivoli Storage Area Network Manager: A Practical Introduction

The output of the backup script is shown in Example 10-18.

Example 10-18 Offline backup of ITSANMDB output

C:\bkupscripts>ITSANMBackupOffline.bat"Stopping Netview"

C:\bkupscripts>ovstopDone

C:\bkupscripts>call ITSANMstop.bat"Stopping the ITSANM-Manager"

C:\bkupscripts>net stop "IBM WebSphere Application Server V5 - ITSANM-Manager"

The IBM WebSphere Application Server V5 - ITSANM-Manager service was stoppedsuccessfully.

C:\bkupscripts>net start | findstr /i "ITSANM-Manager

"Backup of ITSANMDB starting ....."

C:\bkupscripts>C:\PROGRA~1\SQLLIB\BIN\db2cmd.exe /c /w /i db2 backup database ITSANMDB USE TSM

Backup successful. The timestamp for this backup image is : 20030604163542

C:\bkupscripts>call ITSANMstart.bat"Starting the ITSANM-Manager ..."

C:\bkupscripts>net start "IBM WebSphere Application Server V5 - ITSANM-Manager"The IBM WebSphere Application Server V5 - ITSANM-Manager service is starting.............The IBM WebSphere Application Server V5 - ITSANM-Manager service was startedsuccessfully.

C:\bkupscripts>net start | findstr /i "ITSANM-Manager"IBM WebSphere Application Server V5 - ITSANM-Manager"Application ITSANM started successfully""Starting Netview"

C:\bkupscripts>ovstartDone

C:\bkupscripts>

Online backupAn online backup can run while applications are still accessing the data. DB2 will manage the enqueue process and will use its recovery log to track all changes made to the database during while the backup is running. You database must be configured for online backups (see Example 10-5 on page 289). The database backup procedure, ITSANMBackupOnline, displayed in Example 10-19, includes:

1. List current connections2. Run backup of ITSANMDB database3. List current connections

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 299

Example 10-19 ITSANMBackupOnline script

@ECHO ON@REM List active connections for information@REM ---------------------------------------db2cmd.exe /c /w /i db2 list applications for database ITSANMDB | findstr /i SQL1032N@if %errorlevel% NEQ 0 GOTO BACKUPDB

@REM SQL1032N found - DB is not started@REM ----------------------------------@echo "SQL1032N return - DB2 is not active - Backup cancelled !!!"exit 1

:BACKUPDB@ECHO ON@REM DB2 is active - Backup can run@REM ------------------------------@echo "Backup of ITSANMDB starting ..."db2cmd.exe /c /w /i db2 backup database ITSANMDB ONLINE USE TSM@if %errorlevel% NEQ 0 echo "Backup failed - Please check error messages"

@REM Backup completed - List connections@REM -----------------------------------db2cmd.exe /c /w /i db2 list applications for database ITSANMDB

The output of this script execution is shown in Example 10-20.

Example 10-20 Online Backup of ITSANMDB output

C:\bkupscripts>ITSANMBackupOnline.bat

C:\bkupscripts>db2cmd.exe /c /w /i db2 list applications for database ITSANMDB | findstr /i SQL1032N"Backup of ITSANMDB starting ..."

C:\bkupscripts>db2cmd.exe /c /w /i db2 backup database ITSANMDB ONLINE USE TSM

Backup successful. The timestamp for this backup image is : 20030604105830

C:\bkupscripts>db2cmd.exe /c /w /i db2 list applications for database ITSANMDB

Auth Id Application Appl. Application Id DB # of Name Handle Name Agents-------- -------------- ---------- ------------------------------ -------- -----DB2USER1 java.exe 3 *LOCAL.DB2.030604153831 ITSANMDB 1DB2USER1 java.exe 4 *LOCAL.DB2.030604153849 ITSANMDB 1DB2USER1 java.exe 5 *LOCAL.DB2.030604153850 ITSANMDB 1DB2USER1 java.exe 6 *LOCAL.DB2.030604153851 ITSANMDB 1DB2USER1 java.exe 7 *LOCAL.DB2.030604153852 ITSANMDB 1DB2USER1 java.exe 8 *LOCAL.DB2.030604153853 ITSANMDB 1DB2USER1 java.exe 9 *LOCAL.DB2.030604153854 ITSANMDB 1DB2USER1 java.exe 10 *LOCAL.DB2.030604153855 ITSANMDB 1DB2USER1 java.exe 11 *LOCAL.DB2.030604153856 ITSANMDB 1DB2USER1 java.exe 12 *LOCAL.DB2.030604153857 ITSANMDB 1DB2USER1 java.exe 13 *LOCAL.DB2.030604153858 ITSANMDB 1DB2USER1 java.exe 14 *LOCAL.DB2.030604153859 ITSANMDB 1DB2USER1 java.exe 15 *LOCAL.DB2.030604153900 ITSANMDB 1DB2USER1 java.exe 16 *LOCAL.DB2.030604153901 ITSANMDB 1DB2USER1 java.exe 17 *LOCAL.DB2.030604153902 ITSANMDB 1DB2USER1 java.exe 18 *LOCAL.DB2.030604153903 ITSANMDB 1DB2USER1 java.exe 19 *LOCAL.DB2.030604153904 ITSANMDB 1

300 IBM Tivoli Storage Area Network Manager: A Practical Introduction

DB2USER1 java.exe 20 *LOCAL.DB2.030604153905 ITSANMDB 1DB2USER1 java.exe 21 *LOCAL.DB2.030604153906 ITSANMDB 1DB2USER1 java.exe 22 *LOCAL.DB2.030604153907 ITSANMDB 1DB2USER1 java.exe 23 *LOCAL.DB2.030604153908 ITSANMDB 1DB2USER1 java.exe 24 *LOCAL.DB2.030604153909 ITSANMDB 1DB2USER1 java.exe 25 *LOCAL.DB2.030604153910 ITSANMDB 1DB2USER1 java.exe 26 *LOCAL.DB2.030604153911 ITSANMDB 1DB2USER1 java.exe 27 *LOCAL.DB2.030604153912 ITSANMDB 1DB2USER1 java.exe 28 *LOCAL.DB2.030604153913 ITSANMDB 1DB2USER1 java.exe 29 *LOCAL.DB2.030604153914 ITSANMDB 1DB2USER1 java.exe 30 *LOCAL.DB2.030604153915 ITSANMDB 1

You can check the status of your backups using the db2adutl command, which is only valid for backups done using Tivoli Storage Manager (Example 10-21).

Example 10-21 db2adutl output

C:\PROGRA~1\SQLLIB\BIN>db2adutl query database ITSANMDB

Query for database ITSANMDB

Retrieving FULL DATABASE BACKUP information. 1 Time: 20030604105830 Oldest log: S0000004.LOG Node: 0 Sessions: 1 2 Time: 20030604105106 Oldest log: S0000004.LOG Node: 0 Sessions: 1 3 Time: 20030604103857 Oldest log: S0000004.LOG Node: 0 Sessions: 1 4 Time: 20030529161536 Oldest log: S0000055.LOG Node: 0 Sessions: 1 5 Time: 20030529143040 Oldest log: S0000055.LOG Node: 0 Sessions: 1

Retrieving INCREMENTAL DATABASE BACKUP information. No INCREMENTAL DATABASE BACKUP images found for ITSANMDB

Retrieving DELTA DATABASE BACKUP information. No DELTA DATABASE BACKUP images found for ITSANMDB

Retrieving TABLESPACE BACKUP information. No TABLESPACE BACKUP images found for ITSANMDB

Retrieving INCREMENTAL TABLESPACE BACKUP information. No INCREMENTAL TABLESPACE BACKUP images found for ITSANMDB

Retrieving DELTA TABLESPACE BACKUP information. No DELTA TABLESPACE BACKUP images found for ITSANMDB

Retrieving LOAD COPY information. No LOAD COPY images found for ITSANMDB

Retrieving LOG ARCHIVE information. No LOG ARCHIVE images found for ITSANMDB

We find our two latest backups with timestamps 20030604105106 and 20030604103857.

10.4 Restore proceduresIn this section we give IBM Tivoli SAN Manager restore procedures, as listed in Figure 10-5.

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 301

Figure 10-5 IBM Tivoli SAN Manager restore procedures

We describe now the procedures we have used to recover from:

� A loss of major Agents files� A loss of major Server files� A lost of the IBM Tivoli SAN Manager database

10.4.1 Restore Agent filesIn this restore procedure, we have:

� Deleted the install directory except for the binaries.� Tried to start the agent, which fails.� Restored all deleted directories.� Successfully started the agent.

In Example 10-22, you can see all the steps executed to destroy and recover the agent files.

Example 10-22 Agent restore procedure output

root@banda> cd /opt/tivoli/itsanm/agentroot@banda> mv agent agentoldroot@banda> mkdir agentroot@banda> mkdir agent/binroot@banda> cp -r agentold/bin/* agent/bin/.root@banda> mkdir agent/servletroot@banda> mkdir agent/servlet/binroot@banda> cp -r agentold/servlet/bin/* agent/servlet/bin/.root@banda> cd /opt/tivoli/itsanm/agent/bin/aixroot@banda> ./tcstart.shroot@banda> ./tcstart.sh[36]: ./startup.sh: not found.

root@banda> ps -ef|grep itsanm root 12418 21676 0 14:34:07 pts/1 0:00 grep itsanmroot@banda>

root@banda> dsmc restore /opt/tivoli/itsanm/agent/* -subdir=yes -replace=yes

IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.0 h4(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Restore function invoked.

IBM Tivoli SAN Manager agents Restore of lost files

IBM Tivoli SAN Manager serverStop of applications : NetView, embedded WebSphere Application Server

Restore of lost files

Start of applications

IBM Tivoli SAN Manager databaseDB2 restore command

302 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Node Name: BANDASession established with server BANDA: AIX-RS/6000 Server Version 5, Release 2, Level 0.0 Data compression forced on by the server Server date/time: 06/04/03 14:44:19 Last access: 06/04/03 14:42:07

ANS1247I Waiting for files from the server...Restoring 512 /opt/tivoli/itsanm/agent/_uninst [Done] Restoring 512 /opt/tivoli/itsanm/agent/bin [Done] Restoring 512 /opt/tivoli/itsanm/agent/conf [Done].Restoring 11,224 /opt/tivoli/itsanm/agent/conf/DataStore.defaults [Done] Restoring 17,113 /opt/tivoli/itsanm/agent/conf/DataStore.properties [Done] Restoring 2,871 /opt/tivoli/itsanm/agent/conf/nativelog.properties [Done] Restoring 542 /opt/tivoli/itsanm/agent/conf/services.properties [Done] Restoring 219 /opt/tivoli/itsanm/agent/conf/setup.properties [Done] Restoring 240 /opt/tivoli/itsanm/agent/conf/srmRoles.properties [Done] Restoring 30 /opt/tivoli/itsanm/agent/conf/user.properties [Done] Restoring 0 /opt/tivoli/itsanm/agent/conf/TIVINV/BTSAGT01_01.SIG [Done].... <information omitted>Restoring 3,994 /opt/tivoli/itsanm/agent/servlet/logs/localhost_log.2003-05-28.txt [Done]Restoring 8,390 /opt/tivoli/itsanm/agent/servlet/logs/localhost_log.2003-05-29.txt [Done]..Restore processing finished.

Total number of objects restored: 1,559Total number of objects failed: 0Total number of bytes transferred: 55.23 MBData transfer time: 1.71 secNetwork data transfer rate: 32,933.72 KB/secAggregate data transfer rate: 2,256.77 KB/secElapsed processing time: 00:00:25

root@banda> cd /opt/tivoli/itsanm/agent/bin/aixroot@banda> ./tcstart.shroot@banda> Using CLASSPATH: /opt/tivoli/itsanm/agent/lib/classes:/opt/tivoli/itsanm/agent/servlet/common/lib/servlet.jar:/opt/tivoli/itsanm/agent/lib/jms.jar:/opt/tivoli/itsanm/agent/lib/ServiceManager.jar::/opt/tivoli/itsanm/agent/servlet/bin/bootstrap.jarUsing CATALINA_BASE: /opt/tivoli/itsanm/agent/servletUsing CATALINA_HOME: /opt/tivoli/itsanm/agent/servletUsing JAVA_HOME: /opt/tivoli/itsanm/agent/jre

root@banda> ps -ef |grep itsanm root 20898 12456 1 14:59:59 pts/1 0:29 /opt/tivoli/itsanm/agent/jre/bin/java -Dtsnm.baseDir=/opt/tivoli/itsanm/agent -Djlog.noLogCmd=true -Djavax.net.ssl.trustStore=/opt/tivoli/itsanm/agent/conf/server.keystore -Djavax.net.ssl.keyStorePassword= -Dtsnm.localPort=9570 -Dtsnm.protocol=http:// -ss1m -classpath /opt/tivoli/itsanm/agent/lib/classes:/opt/tivoli/itsanm/agent/servlet/common/lib/servlet.jar:/opt/tivoli/itsanm/agent/lib/jms.jar:/opt/tivoli/itsanm/agent/lib/ServiceManager.jar::/opt/tivoli/itsanm/agent/servlet/bin/bootstrap.jar -Dcatalina.base=/opt/tivoli/itsanm/agent/servlet -Dcatalina.home=/opt/tivoli/itsanm/agent/servlet org.apache.catalina.startup.Bootstrap start start root 22020 21676 0 15:00:37 pts/1 0:00 grep itsanm

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 303

root@banda>

root@banda> cd/opt/tivoli/itsanm/agent/logroot@banda> tail msgITSANM.log2003.06.04 15:00:21.550 BTACS0004I Started service SANAgentInbandChangeAgent. java.lang.Class realStartup2003.06.04 15:00:21.553 BTACS0008I Starting service log (timeout 600 seconds) com.tivoli.sanmgmt.middleware.data.Service startup2003.06.04 15:00:21.661 BTACS0004I Started service log. java.lang.Class realStartup2003.06.04 15:00:21.665 BTACS0017I All autostart services have started. com.tivoli.sanmgmt.middleware.TSNMServiceManager startupAllServices2003.06.04 15:00:21.665 BTACS0024I The properties from file /opt/tivoli/itsanm/agent/conf/setup.properties were successfully read. com.tivoli.sanmgmt.middleware.TSNMServiceManager readConnectionProps2003.06.04 15:00:21.666 BTACS0013I Monitoring services (monitor interval is 10 seconds). com.tivoli.sanmgmt.middleware.TSNMServiceManager monitor2003.06.04 15:00:21.980 BTAHQ2942I Heartbeat started, method: agentHeartbeat on HostManager. com.tivoli.sanmgmt.subagent.hostquery.HostQuery run2003.06.04 15:00:52.388 BTASA1407I The Inband scanner Topology has started. com.tivoli.sanmgmt.subagent.scanner.Scanner invoke2003.06.04 15:00:52.389 BTASA1407I The Inband scanner Attribute has started. com.tivoli.sanmgmt.subagent.scanner.Scanner invoke2003.06.04 15:00:52.417 BTASA1407I The Inband scanner Attribute has started. com.tivoli.sanmgmt.subagent.scanner.Scanner invoke

We then checked in SAN ->Configure Agents configuration menu in the NetView interface, shown in Figure 10-6, to find that the agent, BANDA is Contacted.

Figure 10-6 Agent is contacted after restore

304 IBM Tivoli Storage Area Network Manager: A Practical Introduction

10.4.2 IBM Tivoli SAN Manager Server filesIn this restore procedure, we have:

� Deleted IBM Tivoli SAN Manager, IBM Tivoli NetView directories.� Tried to start the Server which fails.� Restored all deleted directories.� Started successfully the server.

First we have deleted all directories for each component as shown in Example 10-23.

Example 10-23 Delete commands

C:\Tivoli>cd itsanm

C:\Tivoli\itsanm>del *.* /s /qDeleted file - C:\Tivoli\itsanm\manager\apps\was\bin\NTRegistry.dllDeleted file - C:\Tivoli\itsanm\manager\apps\was\bin\Ws50ProcessManagement.dllDeleted file - C:\Tivoli\itsanm\manager\apps\was\installedApps\DefaultNode\itsanm.ear\manager.war\WEB-INF\lib\SANMgrDaemonLB.jarDeleted file - C:\Tivoli\itsanm\manager\apps\was\java\bin\java.exeDeleted file - C:\Tivoli\itsanm\manager\apps\was\java\jre\bin\awt.dllDeleted file - C:\Tivoli\itsanm\manager\apps\was\java\jre\bin\fontmanager.dllDeleted file - C:\Tivoli\itsanm\manager\apps\was\java\jre\bin\hpi.dllDeleted file - C:\Tivoli\itsanm\manager\apps\was\java\jre\bin\java.dllDeleted file - C:\Tivoli\itsanm\manager\apps\was\java\jre\bin\jitc.dllDeleted file - C:\Tivoli\itsanm\manager\apps\was\java\jre\bin\jvmdcf

:\Tivoli>rmdir itsanm /sitsanm, Are you sure (Y/N)? y

C:\Tivoli>cd \usr\ov

C:\usr\ov>del *.* /s /q...C:\usr\ov\www\wwwroot\test\mapserver.htmlAccess is denied.C:\usr\ov\www\wwwroot\test\objectproperties.htmlAccess is denied.C:\usr\ov\www\wwwroot\zh\About.htmlAccess is denied.C:\usr\ov\www\wwwroot\zh\index.htmlAccess is denied...C:\usr\ov>del *.* /s /q...C:\usr\ov\www\wwwroot\test\mapserver.htmlAccess is denied.C:\usr\ov\www\wwwroot\test\objectproperties.htmlAccess is denied.C:\usr\ov\www\wwwroot\test\ovstatus.htmlAccess is denied.C:\usr\ov\www\wwwroot\test\ovwdb.htmlAccess is denied.C:\usr\ov\www\wwwroot\zh\About.htmlAccess is denied.C:\usr\ov\www\wwwroot\zh\index.htmlAccess is denied..C:\usr>rmdir ov /s

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 305

ov, Are you sure (Y/N)? yov\bin\nvservice.exe - Access is denied.

After deleting the directories, we tried to start NetView and IBM Tivoli SAN Manager, but it was unsuccessful, as shown in Figure 10-7 for NetView.

We started the Netview from a command prompt see Example 10-24

Example 10-24 NetView start from Windows Command window

C:\usr>ovstart'ovstart' is not recognized as an internal or external command,operable program or batch file.

Figure 10-7 Netview restart failure

We launched the Tivoli Storage Manager Backup/Archive client interface and started the restore of the deleted directories (Figure 10-8).

Figure 10-8 Tivoli Storage Manager restore interface

IBM Tivoli SAN Manager restarted successfully after the restore.

306 IBM Tivoli Storage Area Network Manager: A Practical Introduction

10.4.3 ITSANMDB databaseIn this restore procedure, we have:

� Stopped IBM Tivoli SAN Manager.� Deleted all rows in the ITSANMDB tables.� Restored an old ITSANMDB database backup.� Reapplied the log till the DELETE commands.� Successfully started the server.

Example 10-25 shows the SQL DELETE commands used to delete the content of the ITSANMDB tables.

Example 10-25 ITSANMDB corruption through DELETE commands

C:\>db2 connect to ITSANMDB

Database Connection Information

Database server = DB2/NT 7.2.6 SQL authorization ID = DB2ADMIN Local database alias = ITSANMDBC:\>db2 "select 'DROP TABLE ITSANM.'||tabname||';' from syscat.tables where tabschema = 'ITSANM'" > drop.sql

C:\>db2 -tf drop.sqlDB20000I The SQL command completed successfully.DB20000I The SQL command completed successfully...DB20000I The SQL command completed successfully.DB20000I The SQL command completed successfully.DB20000I The SQL command completed successfully..DB21007E End of file reached while reading the command.

We restarted IBM Tivoli SAN Manager successfully. A new discovery is automatically launched since the inband agents send new data to the manager. As expected, the outband agents do not appear under SNMP Agents as their configuration has been lost to the Server, as shown in Figure 10-9.

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 307

Figure 10-9 IBM Tivoli SAN Manager agents

We stopped all services and restored the database. Example 10-26 shows the commands used to restore the ITSANMDB database.

Example 10-26 ITSANMDB restore procedure

C:\PROGRA~1\SQLLIB\BIN>db2adutl query db ITSANMDB

Query for database ITSANMDB

Retrieving FULL DATABASE BACKUP information. 1 Time: 20030606161023 Oldest log: S0000027.LOG Node: 0 Sessions: 1 2 Time: 20030605111502 Oldest log: S0000019.LOG Node: 0 Sessions: 1 3 Time: 20030604163542 Oldest log: S0000019.LOG Node: 0 Sessions: 1 4 Time: 20030604162311 Oldest log: S0000017.LOG Node: 0 Sessions: 1 5 Time: 20030604161510 Oldest log: S0000016.LOG Node: 0 Sessions: 1 6 Time: 20030604155946 Oldest log: S0000015.LOG Node: 0 Sessions: 1 7 Time: 20030604105830 Oldest log: S0000004.LOG Node: 0 Sessions: 1 8 Time: 20030604105106 Oldest log: S0000004.LOG Node: 0 Sessions: 1 9 Time: 20030604103857 Oldest log: S0000004.LOG Node: 0 Sessions: 1 10 Time: 20030529161536 Oldest log: S0000055.LOG Node: 0 Sessions: 1 11 Time: 20030529143040 Oldest log: S0000055.LOG Node: 0 Sessions: 1..

C:\>db2 list applications for database ITSANMDBSQL1611W No data was returned by Database System Monitor. SQLSTATE=00000

C:\>db2 restore database ITSANMDB use tsm taken at 20030606161023SQL2539W Warning! Restoring to an existing database that is the same as the backup image database. The database files will be deleted.Do you want to continue ? (y/n) yDB20000I The RESTORE DATABASE command completed successfully.

308 IBM Tivoli Storage Area Network Manager: A Practical Introduction

C:\>db2 rollforward db ITSANMDB to 2003-06-06-23.16.00.000000 and STOP

Rollforward Status

Input database alias = ITSANMDB Number of nodes have returned status = 1

Node number = 0 Rollforward status = not pending Next log file to be read = Log files processed = S0000027.LOG - S0000027.LOG Last committed transaction = 2003-06-06-23.01.10.000000

DB20000I The ROLLFORWARD command completed successfully.

C:\PROGRA~1\SQLLIB\BIN>ovstartDone

C:\PROGRA~1\SQLLIB\BIN>c:\bkupscripts\ITSANMstart.bat

The IBM WebSphere Application Server V5 - ITSANM-Manager service is starting...........The IBM WebSphere Application Server V5 - ITSANM-Manager service was startedsuccessfully.

C:\PROGRA~1\SQLLIB\BIN>

In the ROLLFORWARD command, we specified to which point we want to restore the database. 2003-06-06-23.16.00.000000 is expressed in Coordinated Universal Time (UTC) and is the time just before we started our SQL DELETE commands.

10.5 Disaster recovery proceduresIn this section we describe the procedures we have used to recover from a complete loss of our IBM Tivoli SAN Manager (Figure 10-10).

Figure 10-10 IBM Tivoli SAN Manager Disaster Recovery procedures

IBM Tivoli SAN Manager serverInstall basic Windows 2000 server

Install Windows Service Pack

Install Tivoli Storage Manager client

Restore files

Restore System Objects

Restore embedded WebSphere Application Server environment

Restore ITSANDB DB2 database

Start applications

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 309

10.5.1 Windows 2000 restoreTo restore our IBM Tivoli SAN Manager server, we followed the procedure described in Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141. We did the following:

1. Installed Windows 2000 on the server using LOCHNESS as hostname

2. Installed Windows 2000 Service Pack 3

3. Installed the Tivoli Storage Manager Backup/Archive Client and configured it to use our Tivoli Storage Manager located on BANDA. We used a basic client options file, sufficient for the restore. See Example 10-27.

Example 10-27 Minimal Tivoli Storage Manager client option file

tcpserveraddress banda.almaden.ibm.comnodename lochness

4. Restored all the files on the boot partition (disk C:\) as shown in Figure 10-11.

Figure 10-11 Full system restore result

5. We restored the Windows 2000 System Objects (Figure 10-12).

310 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 10-12 System Objects restore

The restore of the System Objects finished successfully, as shown in Figure 10-13.

Figure 10-13 System Objects restore results

6. We now rebooted the system.

At this time, we are in the situation where all our software and configuration files have been restored. We must now restore the IBM Tivoli SAN Manager and the ITSANMDB databases to their latest available status.

Note: Refer to the redbook, Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141, for detailed information on Windows disaster recovery procedures.

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 311

10.5.2 ITSANMDB database restoreWe used the procedure described in 10.3.3, “ITSANMDB Database” on page 296 to restore the ITSANMDB database. We were able to do a roll forward restore since the DB2 logs were backed up to Tivoli Storage Manager before the crash. They were restored during the step 10.5.1, “Windows 2000 restore” on page 310. Example 10-28 shows the output of the restore process.

Example 10-28 Database restore output

C:\PROGRA~1\SQLLIB\BIN>db2adutl query database ITSANMDB

Query for database ITSANMDB

Retrieving FULL DATABASE BACKUP information. 1 Time: 20030529161536 Oldest log: S0000055.LOG Node: 0 Sessions: 1 2 Time: 20030529143040 Oldest log: S0000055.LOG Node: 0 Sessions: 1..

db2 => restore db ITSANMDB use TSM taken at 20030529161536DB20000I The RESTORE DATABASE command completed successfully.db2 => connect to ITSANMDBSQL1117N A connection to or activation of database "ITSANMDB" cannot be madebecause of ROLL-FORWARD PENDING. SQLSTATE=57019

db2 => rollforward db ITSANMDB to end of logs and stop

Rollforward Status

Input database alias = ITSANMDB Number of nodes have returned status = 1

Node number = 0 Rollforward status = not pending Next log file to be read = Log files processed = S0000055.LOG - S0000058.LOG Last committed transaction = 2003-05-29-23.17.35.000000

DB20000I The ROLLFORWARD command completed successfully.

C:\PROGRA~1\SQLLIB\BIN>

IBM Tivoli SAN Manager is now successfully restarted (Figure 10-14).

312 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 10-14 IBM Tivoli SAN Manager interface

Note that if your DB2 files and directories were never backed up using the standard Backup/Archive client, your DB2 local and system directory will not be synchronized. You will have to uncatalog the ITSANMDB database and recreate the database during the restore as briefly shown in Example 10-29.

Example 10-29 Database restore output with synchronization

C:\PROGRA~1\SQLLIB\BIN>db2 restore db ITSANMDB use TSM TAKEN AT 20030529161536SQL1005N The database alias "ITSANMDB" already exists in either the localdatabase directory or system database directory. SQLSTATE=00000

C:\PROGRA~1\SQLLIB\BIN>db2 uncatalog database ITSANMDBDB20000I The UNCATALOG DATABASE command completed successfully.DB21056W Directory changes may not be effective until the directory cache isrefreshed.

C:\PROGRA~1\SQLLIB\BIN>db2stopSQL1064N DB2STOP processing was successful.

C:\PROGRA~1\SQLLIB\BIN>db2startSQL1063N DB2START processing was successful.

C:\PROGRA~1\SQLLIB\BIN>db2 restore db ITSANMDB use TSM TAKEN AT 20030529161536SQL1036C An I/O error occurred while accessing the database. SQLSTATE=58030

C:\PROGRA~1\SQLLIB\BIN>db2 restore db ITSANMDB use TSM TAKEN AT 20030529161536 to C into ITSANMDBDB20000I The RESTORE DATABASE command completed successfully.

C:\PROGRA~1\SQLLIB\BIN>

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 313

10.6 Database maintenanceAs with every database, basic maintenance should be applied to the IBM Tivoli SAN Manager repository to avoid space and performance problems (Figure 10-15).

Figure 10-15 DB2 Database maintenance

Basic DB2 maintenance should include:

� runstats to update tables statistics� reorgchk to check need for tables reorganization� reorg to rebuild unordered tables and indexes� db2rbind to rebuild packages

The runstats command is not mandatory since the statistics can be updated by the reorgchk command. Moreover, you need to run a runstats command for each table while reorgchk executes over all tables.

Example 10-30 shows the output of the reorgchk command on our ITSANMDB database.

Example 10-30 Output of reorgchk

db2 => connect to itsanmdb

Database Connection Information

Database server = DB2/NT 7.2.6 SQL authorization ID = DB2ADMIN Local database alias = ITSANMDB

db2 => reorgchk on table allDoing RUNSTATS ....

Table statistics:

F1: 100 * OVERFLOW / CARD < 5F2: 100 * TSIZE / ((FPAGES-1) * (TABLEPAGESIZE-76)) > 70F3: 100 * NPAGES / FPAGES > 80

CREATOR NAME CARD OV NP FP TSIZE F1 F2 F3 REORG--------------------------------------------------------------------------------DB2USER1 AGENT2SCANASSP 26 0 3 3 8892 0 100 100 --- DB2USER1 AGENTPEER 10 0 1 1 1740 0 - 100 --- DB2USER1 AIXOSPEER - - - - - - - - --- DB2USER1 CALLBACK 10 0 1 7 2220 0 9 14 -** DB2USER1 CLASS_EXT - - - - - - - - --- DB2USER1 CLASSTABLE 83 0 3 3 8798 0 100 100 --- DB2USER1 DBSCHEMAVPEER - - - - - - - - --- DB2USER1 DEMOIDPEER 216 0 9 16 18360 0 30 56 -** DB2USER1 DESCANNERPEER 26 0 3 3 7228 0 89 100 --- DB2USER1 FABRICPORTPEER 32 1 2 3 4864 3 60 66 -**

Database should be checked for performance usingrunstats

reorgchk

reorg table

db2rbind

314 IBM Tivoli Storage Area Network Manager: A Practical Introduction

DB2USER1 FCENDPORTPEER 12 0 1 2 1728 0 42 50 -** DB2USER1 FCHUBPORTPEER - - - - - - - - --- ...--------------------------------------------------------------------------------

Index statistics:

F4: CLUSTERRATIO or normalized CLUSTERFACTOR > 80F5: 100 * (KEYS * (ISIZE+8) + (CARD-KEYS) * 4) / (NLEAF * INDEXPAGESIZE) > 50F6: (100-PCTFREE) * (INDEXPAGESIZE-96) / (ISIZE+12) ** (NLEVELS-2) * (INDEXPAGESIZE-96) / (KEYS * (ISIZE+8) + (CARD-KEYS) * 4) < 100

CREATOR NAME CARD LEAF LVLS ISIZE KEYS F4 F5 F6 REORG--------------------------------------------------------------------------------Table: DB2USER1.AGENT2SCANASSPDB2USER1 RDBPK_60 26 1 1 6 26 100 - - --- DB2USER1 RDBUI_27 26 2 2 124 26 100 41 104 -** Table: DB2USER1.AGENTPEERDB2USER1 RDBPK_12 10 1 1 6 10 100 - - --- DB2USER1 RDBUI_3 10 1 1 41 10 100 - - --- ...--------------------------------------------------------------------------------

CLUSTERRATIO or normalized CLUSTERFACTOR (F4) will indicate REORG is necessary for indexes that are not in the same sequence as the base table. When multiple indexes are defined on a table, one or more indexes may be flagged as needing REORG. Specify the most important index for REORG sequencing.

The reorgchk command calculates three formulas (F1, F2, F3) for the tables and three formulas (F4, F5, F6) for the indexes to determine if the table or index must be reorganized. Each hyphen displayed in the REORG column indicates that the calculated results were within the set bounds of the corresponding formula, and each asterisk indicates that the calculated result exceeded the set bounds of its corresponding formula.

Table reorganization is suggested when the results of the calculations exceed the bounds set by the formula.

If a reorganization is recommended for a table or an index, this can only be done when no activity is running against the database. This means that IBM Tivoli SAN Manager must be stopped in order to reorganize the tables.

Example 10-31 shows an output of the reorg for a ITSANMDB DB2 table followed by a reorgchk on this table.

Example 10-31 REORG output

db2 => reorg table db2user1.scan2dmoidasspDB20000I The REORG TABLE command completed successfully.db2 => reorgchk on table db2user1.scan2dmoidassp

Attention: Refer to the IBM DB2 Universal Database — Administration Guide: Implementation — Version 7, SC09-2944 for more information about DB2 performance.

Chapter 10. Protecting the IBM Tivoli SAN Manager environment 315

Doing RUNSTATS ....

Table statistics:

F1: 100 * OVERFLOW / CARD < 5F2: 100 * TSIZE / ((FPAGES-1) * (TABLEPAGESIZE-76)) > 70F3: 100 * NPAGES / FPAGES > 80

CREATOR NAME CARD OV NP FP TSIZE F1 F2 F3 REORG--------------------------------------------------------------------------------DB2USER1 SCAN2DMOIDASSP 345 0 31 31 116955 0 96 100 -----------------------------------------------------------------------------------

Index statistics:

F4: CLUSTERRATIO or normalized CLUSTERFACTOR > 80F5: 100 * (KEYS * (ISIZE+8) + (CARD-KEYS) * 4) / (NLEAF * INDEXPAGESIZE) > 50F6: (100-PCTFREE) * (INDEXPAGESIZE-96) / (ISIZE+12) ** (NLEVELS-2) * (INDEXPAGESIZE-96) / (KEYS * (ISIZE+8) + (CARD-KEYS) * 4) < 100

CREATOR NAME CARD LEAF LVLS ISIZE KEYS F4 F5 F6 REORG--------------------------------------------------------------------------------Table: DB2USER1.SCAN2DMOIDASSPDB2USER1 RDBPK_104 345 2 2 6 345 94 58 74 ---DB2USER1 RDBUI_49 345 16 2 122 345 70 68 8 *----------------------------------------------------------------------------------

CLUSTERRATIO or normalized CLUSTERFACTOR (F4) will indicate REORG is necessaryfor indexes that are not in the same sequence as the base table. When multipleindexes are defined on a table, one or more indexes may be flagged as needingREORG. Specify the most important index for REORG sequencing.

Finally, rebuild the packages — if any — that are associated with ITSANMDB using the db2rbind command (Example 10-32).

Example 10-32 DB2 rebind

C:\PROGRA~1\SQLLIB>db2rbind ITSANMDB -l C:\ITSANMDB_RBIND.txt all

Rebind done successfully for database 'ITSANMDB'.

C:\PROGRA~1\SQLLIB>

Important: Note that it is preferable to reorganize a table according its most used index. Refer to the DB2 Administration Guide for tables and indexes reorganization.

316 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 11. Logging and tracing

In this chapter we provide additional details on the logging and tracing that is available for IBM Tivoli SAN Manager. We also include an overview of the contents of the logging directory, and we discuss the SAN Manager Service Tool feature that is new in IBM Tivoli SAN Manager V1.2.

11

© Copyright IBM Corp. 2002, 2003. All rights reserved. 317

11.1 OverviewIn the following sections we provide an overview of the logging files that are available for the Server, Agent, and Remote Console within IBM Tivoli SAN Manager. We describe the default logging parameters that are set within the product and give a high level description of the tracing facility is also provided. Finally, we describe the SAN Manager Service Tool that is used for capturing a snapshot of the managed environment. These concepts are listed in Figure 11-1.

Figure 11-1 IBM Tivoli SAN Manager — Logging and tracing overview

11.2 LoggingLogging for Tivoli SAN Manager is intended to provide information to the end user and is enabled by default. This means logging provides information about your system, such as what components are started, or which exceptions and errors are received during an operation.

To help you track server activity and monitor the system, the messages are logged in text files. These files can be viewed with a standard editing program, such as Windows Wordpad or Notepad.

By default, the log files are located in the <install_dir>\log directory on the Manager, Agent And Remote Console machines. The number, size, type, and format of your message log files is configurable. The following message types are enabled by default:

� Informational messages� Warning messages� Error messages

Refer to the IBM Tivoli Storage Area Network Manager User’s Guide, SG23-4698 for information on configuring logging.

11.2.1 Server logsHere is information about logging in both the Windows and AIX managers.

Windows Managermgrlog.txt - the main installation logging file for IBM Tivoli SAN Manager Server is in c:\tivoli\itsanm\manager\mgrlog.txt. See Example 11-1.

Example 11-1 mgrlog.txt for Tivoli SAN Manager

(May 28, 2003 2:17:58 PM), Setup.product.install, com.tivoli.sanmgmt.install.Mov

LoggingServer

Agent

Remote Console

Additional NetView logging

SAN Error Predictor

Tracing

SAN Manager Service Tool

318 IBM Tivoli Storage Area Network Manager: A Practical Introduction

eFileProdAct, wrn, MoveFileProdAct: c:\tivoli\itsanm\manager\conf does not exists(May 28, 2003 2:18:03 PM), Setup.product.install, com.tivoli.sanmgmt.install.MergePropFileProdAct, wrn, MergePropFileProdAct: c:\tivoli\itsanm\manager\conf.bkp/nativelog.properties does not exists

Other installation logs are located in the directory c:\tivoli\itsanm\manager\\install\. Review these in the event of any problems with installation. Example 11-2 shows its contents.

Example 11-2 Installation logs for Tivoli SAN Manager

Directory of C:\tivoli\itsanm\manager\log\install

06/03/2003 03:54p <DIR> .06/03/2003 03:54p <DIR> ..06/03/2003 03:54p 0 addWASServiceErr.txt06/03/2003 03:54p 272 addWASServiceOut.txt06/03/2003 03:52p 0 CreatePortsstderr.log06/03/2003 03:52p 100 CreatePortstdout.log06/03/2003 03:45p 0 db2createstderr.txt06/03/2003 03:45p 0 db2createstdout.txt06/03/2003 03:46p 63,788 dbcreate.log06/03/2003 03:52p 0 encryptSoapErr.txt06/03/2003 03:52p 0 encryptSoapOut.txt06/03/2003 03:45p 110,942 guidInstalllog.txt06/03/2003 03:45p 0 guidInstallStderr.txt06/03/2003 03:45p 0 guidInstallStdout.txt06/03/2003 03:52p 0 launchITSANMstderr.log06/03/2003 03:54p 6,249 launchITSANMstdout.log06/03/2003 03:50p 170 netview.log06/03/2003 03:51p 71 OvConfstderr.log06/03/2003 03:51p 57,230 OvConfstdout.log06/03/2003 03:54p 0 rmWASServiceErr.txt06/03/2003 03:54p 57 rmWASServiceOut.txt06/03/2003 03:50p 0 temp.log06/03/2003 03:51p 0 wasInstallstderr.log06/03/2003 03:51p 0 wasInstallstdout.log06/03/2003 03:51p 44 wasUnInstallstderr.log06/03/2003 03:51p 0 wasUnInstallstdout.log 24 File(s) 238,923 bytes 2 Dir(s) 710,127,616 bytes free

dbCreate.log - used to log DB2 creation for ITSANMDB. This log is useful if the IBM Tivoli SAN Manager database fails to install. See Example 11-3.

Example 11-3 dbcreate.log for DB2

C:\Tivoli\itsanm\manager\log\install>more dbcreate.log

IBM Tivoli Storage Area Network Manager Database Creation Script

(C) Copyright IBM Corp. 2000, 2001

DB20000I The CREATE DATABASE command completed successfully.DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.DB21026I For most configuration parameters, all applications must disconnectfrom this database before the changes become effective.

Chapter 11. Logging and tracing 319

AIX ManagerThe installation log for the IBM Tivoli SAN Manager Server on AIX is /opt/tivoli/itsanm/manager/mgrlog.txt. If you encounter errors during installation, the logs for problem determination can be found in: /opt/tivoli/itsanm/manager/log/install.

GUID loggingThe Tivoli GUID package is used to resolve a computer’s identification. Computers can have multiple domain names, a dynamic IP address that changes, or a host name that changes. The GUID package gives the computer a global unique identifier (GUID). This assures that one computer that is running multiple applications can be uniquely identified. For example, one computer might be running the Tivoli Storage Manager client and the IBM Tivoli Storage Area Network Manager agent.

The following logs are used for GUID and can be found in c:\Tivoli\itsanm\manager\log\install. For AIX, the GUID will be created in /opt/tivoli/itsanm/manager/guid/aix.

� guidInstalllog.txt� guidInstallStderr.txt� guidInstallStdout.txt

These files contain messages and errors related to installing the GUID package.

11.2.2 Manager service commandsThe Manager service commands let you display or set values in the user properties file (tivoli/itsanm/manager/conf/user.properties) on the IBM Tivoli SAN Manager server. This file contains settings that control host polling, SNMP traps destination, and the monitoring interval for the out-of-band agent. Some of the Manager Service commands are described below. Refer to IBM Tivoli SAN Manager 1.2 User’s Guide, SC23-4698.

There are two types of Service commands. They are:

� Logging service commands – which allow you to configure and turn message logging on and off.

� Manager Service commands – allow you to display or set values in the user properties file. These service commands allow you to display or set the values in the /tivoli/itsanm/manager/conf/user.properties) on the manager server.

Before issuing any service commands, set the environment variables. From a Windows command prompt, issue c:\Tivoli\itsanm\manager\bin\w32-ix86\setenv. From an AIX prompt, issue /opt/tivoli/itsanm/manager/bin/aix/setenv.sh.

Command syntax for the service commands is as follows:

srmcp -u <user_ID> -p <password> [command]

Logging service commandssrmcp log get - This command displays the current properties of the message log file. If you do not specify a parameter for this command, a syntax error message will be displayed.

We demonstrate the use of the filterkey parameter. The filterkey parameter displays the types of messages that are logged in the message log.

srmcp -u db2admin -p db2admin log get -filterkey

Note: This log contains the same logging information as described in Example 11-1.

320 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Example 11-4 Display of filterkey setting

C:\tivoli\itsanm\manager\bin\w32-ix86>srmcp -u db2admin -p itsosj log get -filterkeyIBM Tivoli Storage Area Network Manager Logging ToolkitCommand Line Interface - Version 1 Release 1 Level 0 aFilterkey is set to ALL.C:\tivoli\itsanm\manager\bin\w32-ix86>

Manager service commandssrmcp ConfigService Display - This command displays the values in the user.properties file. We demonstrate how to retrieve the ConfigService parameter. The ConfigService parameter displays the value for a full discovery (FullAttributeScan) property in the user.properties file.

srmcp -u user2 -p password2 ConfigService get FullAttributeScan

Example 11-5 Display of FullAttributeScan value

C:\tivoli\itsanm\manager\bin\w32-ix86>srmcp -u db2admin -p itsosj ConfigService get FullAttributeScan

The value is: PollNowAndTimeBased

C:\tivoli\itsanm\manager\bin\w32-ix86>

11.2.3 Service ManagerThe Service Manager utility allows you to display the status of the IBM Tivoli SAN Manager services. The URL for the Service Manager is:

http://hostname:9550/ITSRM/ServiceManager

In Figure 11-2, the Service Manager displayed all the IBM Tivoli SAN Manager services.

Chapter 11. Logging and tracing 321

Figure 11-2 Service Manager

11.2.4 Agent logsIBM Tivoli SAN Manager logging is also performed on the Agent. The following tables display the default log file locations for the IBM Tivoli SAN Manager Agent. We provide sample output of some of the logs below.

WindowsThe msgITSANM.log contains information for the IBM Tivoli SAN Manager Agent. The log can be found at c:\tivoli\itsanm\agent\install See the Example 11-6 below.

Example 11-6 msgITSANM output

2003.05.28 15:01:11.062 BTACS0024I The properties from file c:\tivoli\itsanm\agent\conf\setup.properties were successfully read. Service readConnectionProps 2003.05.28 15:01:11.156 BTACS0005I Deployed service ConfigService: class=com.tivoli.sanmgmt.dbconnparms.ConfigService, scope=application, autostart=true, static=false, order=1. com.tivoli.sanmgmt.middleware.data.Service deploy 2003.05.28 15:01:11.594 BTACS0005I Deployed service SANAgentHostQuery: class=com.tivoli.sanmgmt.subagent.hostquery.HostQuery, scope=application, autostart=true, static=false, order=2. com.tivoli.sanmgmt.middleware.data.Service deploy

322 IBM Tivoli Storage Area Network Manager: A Practical Introduction

2003.05.28 15:01:11.656 BTACS0005I Deployed service SANAgentScanner:

SolarisThis log contains information for the IBM Tivoli SAN Manager Agent. The log can be found at /tivoli/itsanm/agent/log.

LinuxThis log contains information for the IBM Tivoli SAN Manager Agent. The log can be found at /tivoli/itsanm/agent/log.

AIXThis log contains information for the IBM Tivoli SAN Manager Agent. The log can be found at /tivoli/itsanm/agent/log.

11.2.5 Remote Console loggingLogging is also performed on the IBM Tivoli SAN Manager Remote Console. After installing the remote console, the logs can be reviewed in the default location of c:\tivoli\itsanm\console\log\msgITSANM.log. For an example of the log, see Example 11-7.

Example 11-7 Console log

2003.06.04 09:37:42.406 BTACS0024I The properties from file c:\tivoli\itsanm\console\conf\setup.properties were successfully read. Service readConnectionProps 2003.06.04 09:37:42.906 BTACS0005I Deployed service ConfigService: class=com.tivoli.sanmgmt.dbconnparms.ConfigService, scope=application, autostart=true, static=false, order=1. com.tivoli.sanmgmt.middleware.data.Service deploy 2003.06.04 09:37:43.359 BTACS0005I Deployed service SANManagerDaemon: class=com.tivoli.sanmgmt.tsanm.console.SanManagerDaemon, scope=application, autostart=true, static=false, order=2. com.tivoli.sanmgmt.middleware.data.Service deploy 2003.06.04 09:37:43.375 BTACS0005I Deployed service log: :37:44.891 BTACS0004I Started service ConfigService. java.lang.Class realStartup 2003.06.04 09:37:44.906 BTACS0008I Starting service SANManagerDaemon (timeout 600 seconds) com.tivoli.sanmgmt.middleware.data.Service startup 2003.06.04 09:38:01.516 BTACS0004I Started service SANManagerDaemon. java.lang.Class realStartup 2003.06.04 09:38:01.531 BTACS0008I Starting service log (timeout 600 seconds) com.tivoli.sanmgmt.middleware.data.Service startup 2003.06.04 09:38:01.531 BTACS0004I Started service log. java.lang.Class realStartup 2003.06.04 09:38:01.531 BTACS0017I All autostart services have started.

11.2.6 Additional logging for NetViewBy default NetView has it primary SNMP trap log disabled. The log file is called trapd.log and is located in /usr/ov/log when it is running. This log file contains information on SNMP traffic as it is received on TCP port 162 of the NetView server. In addition to the NetView Event Log, the trapd.log is very useful when trying to confirm if a SNMP trap was received at the NetView server. Figure 11-3 shows the trap reception on NetView.

Note: The following agent platforms contain similar agent logs that are located in the respective directories.

Chapter 11. Logging and tracing 323

Figure 11-3 NetView trap reception

To enable NetView to use the trapd.log, do the following:

1. From the NetView console, select Options -> Server Setup, to bring up the Server Setup window. This lists all the NetView processes. Select the trapd from the process list, and click the pull down menu to select Trap Daemon, as shown in Figure 11-4.

Figure 11-4 NetView daemons

2. This brings up the trap daemon configuration window. Check the box Log Events and Traps, then click OK. See Figure 11-5.

SNMP TrapTrapd.log Event LogTCP

162

NetView Server

fibre channelswitch

Trap Reception Trap Reception

324 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 11-5 Enable trapd logging

3. NetView now prompts for a stop and start of the daemons as shown in Figure 11-6.

Figure 11-6 Stop and start daemons

4. NetView shuts down all daemons, then restarts them. See Figure 11-7.

Figure 11-7 Recycling daemons

11.2.7 ED/FI - SAN Error PredictorIn Figure 11-8 we show the logging entry from the ED/FI function. These entries were logged during ED/FI adornment. For more information on ED/FI, see Chapter 9, “ED/FI - SAN Error Predictor” on page 267.

Important: There are documented steps on how to perform maintenance on the trapd.log in Tivoli NetView. Please refer to the redbook Tivoli NetVIew and Friends, SG24-6019.

Chapter 11. Logging and tracing 325

Example 11-8 SAN Error Predictor log entry

2003.06.07 11:02:55.266 BTAFI1010I PFA Rules Engine fired 4_IN_1_RULE rule for port 210000E08B06C90B on counter LOSSOFSYNCHRONIZATION. EDFILogger PFAStatistics.firWarning 2003.06.07 11:02:55.281 BTAFI0100I Successfully read EDFI properties file: c:\tivoli\itsanm\manager\conf\edfi.properties. EDFILogger EDFIProperties.readPropertiesFile 2003.06.07 11:02:55.469 BTAFI0100I Successfully read EDFI properties file: c:\tivoli\itsanm\manager\conf\edfi.properties. EDFILogger EDFIProperties.readPropertiesFile 2003.06.07 11:02:55.484 BTAFI1010I PFA Rules Engine fired 2_IN_1_RULE rule for port 210000E08B0190EF on counter LOSSOFSIGNAL. EDFILogger PFAStatistics.firWarning

11.3 TracingTracing is intended for Tivoli Support to diagnose problems. This functionality is disabled by default. Tracing can be dynamically enabled using a command and each trace can be turned on or off independently.

The tracing output file is called traceITSANM.log and is located in the <install_dir>\log of the Manager or Agent. By default up to three traceITSANM.log files can exist and each of them can grow to 512KB. however the file size as well as the number of files are configurable. When traceITSANM.log is full, traceITSANM.log will be renamed to traceITSANM2.log and new logs will be written to the empty traceITSANM.log. When traceITSANM.log fills again, traceITSANM2.log will be renamed to traceITSANM.log, and traceITSANM2.log will be renamed to traceITSANM3.log. This is to ensure that traceITSANM.log contains the latest trace information. When traceITSANM.og fills for a third time, the oldest log (traceITSANM3.log) is discarded and the cycle continues.

Once the environment is sourced (setenv). We issued the srmcp -u <uid> -p <password> log list -loggers command to list out the status of the trace loggers. We show the output of this command in Example 11-9.

Example 11-9 IBM Tivoli SAN Manager loggers

C:\tivoli\itsanm\manager\bin\w32-ix86>srmcp -u db2admin -p itsosj log list -loggersIBM Tivoli Storage Area Network Manager Logging ToolkitCommand Line Interface - Version 1 Release 1 Level 0 a

State Filter Handlers Loggeron ALL file.message san.indexLogon WARN file.trace san.ArchiveTableMaintenanceServiceTraceon WARN file.trace san.schedulerTraceon ALL file.message san.SanAgent_ScannerMsgLoggeron ALL file.message san.formatLogon WARN file.trace san.SanAgent_ScannerTraceLoggeron ALL file.message san.schedulerLogon WARN file.trace san.indexTraceon WARN file.trace san.StatusCacheTraceLoggeron WARN file.trace san.ReportMgrTraceon WARN file.trace san.SANlicenseSnmpTrapTrace

Important: By default all trace loggers are enabled. The “filter” mode is what controls the level of tracing. (WARN=high level messages, INFO=detailed messages). When the “filter” mode is changed INFO, this can impact system performance. The “filter” mode should only be changed when recommended by IBM Tivoli Support.

326 IBM Tivoli Storage Area Network Manager: A Practical Introduction

on ALL file.message san.monitorLogon WARN file.trace san.monitorTraceon ALL file.message san.ArchiveTableMaintenanceServiceLogon ALL file.message san.ReportMgrLogon WARN file.trace san.formatTraceon WARN file.trace san.SANAgentHostQueryTraceon WARN file.trace san.SanAgent_InbandChangeAgentTraceLoggeron ALL file.message san.SANAgentHostQueryLogon ALL file.message san.SanAgent_InbandChangeAgentMsgLoggeron ALL file.message san.SanPersistMessageLoggeron WARN file.trace san.SanPersistTraceLoggeron WARN file.trace san.EDFITraceLoggeron ALL file.message san.EDFIMsgLoggeron ALL file.message san.StatusCacheMsgLoggeron ALL file.message san.TSNMServiceManagerLogon WARN file.trace san.TSNMServiceManagerTraceon WARN file.trace san.dbparmsTraceon ALL file.message san.dbparmsLogon ALL file.message san.MessagingServiceLogon WARN file.trace san.MessagingServiceTraceon WARN file.trace san.eventFactoryTraceon ALL file.message san.licenseServiceLogon WARN file.trace san.licenseServiceTraceon ALL file.message san.HostMgrMsgLoggeron WARN file.trace san.HostMgrTraceLoggeron ALL file.message san.SanEventCorrelatorFactoryMsgLoggeron WARN file.trace san.SanEventCorrelatorFactoryTraceLoggeron ALL file.message san.OutbandChangeAgentLoggeron WARN file.trace san.OutbandChangeAgentTraceLoggeron ALL file.message san.SanManagerMsgLoggeron WARN file.trace san.SanManagerTraceLoggeron WARN file.trace san.SanManagerHighLevelPerformanceTraceLoggeron ALL file.message san.JDBCConnectionPoolLogon WARN file.trace san.JDBCConnectionPoolTraceon ALL file.message san.DBMsgLoggeron WARN file.trace san.DBTraceLoggeron ALL file.message san.ChangeMonitorMsgLoggeron WARN file.trace san.ChangeMonitorTraceLoggeron ALL file.message san.tesMsgLoggeron WARN file.trace san.tesTrcLoggeron ALL file.message san.SanManagerDaemonMsgLoggeron WARN file.trace san.SanManagerDaemonTraceLoggeron WARN file.trace san.DBAPITraceon WARN file.trace san.eventTraceon ALL file.message san.eventLogon WARN file.trace san.SanQueryEngineTraceLoggeron ALL file.message san.SanQueryEngineMsgLoggeron WARN file.trace san.LoggingToolkitTraceLoggeron ALL file.message san.LoggingToolkitLoggeron ALL file.message srm.PolicyManagerLogon WARN file.trace srm.PolicyManagerTraceon INFO native.msg.fswpon DEBUG_MAX native.trace.fswpon DEBUG_MAX native.trace.tivguidon DEBUG_MAX native.trace.attributeScanneron DEBUG_MAX native.trace.topologyScanneron DEBUG_MAX native.trace.eventScanneron DEBUG_MAX native.trace.eventAgenton DEBUG_MAX native.trace.brocadeScanner

Chapter 11. Logging and tracing 327

on DEBUG_MAX native.trace.statisticsScanner

11.4 SAN Manager Service ToolThe SAN Manager Service Tool is new with IBM Tivoli SAN Manager V1.2 and is used to collect information to send to the IBM Service organization in case of certain problems. It creates a complete snapshot of the IBM Tivoli SAN Manager environment (including current database contents) which can then be loaded onto another system for problem analysis and determination.

11.4.1 Exporting (snapshot)The service tool is found in the following locations on the SAN Manager.

� Windows: c:\tivoli\itsanm\manager\service\service.bat� AIX: /tivoli/itsanm/manager/service/service.sh

When the service tool script is run, it takes a snapshot of these:

� SAN Manager Database� NetView Logging & Event Data� NetView Topology & Mapping Data� SAN Manager Log files

Once the service tool has completed, it creates ITSANMservice.zip or ITSANMservice.tar in the same directory. The file is typically several megabytes in size. The compressed file contains all the critical files from the log directory as well as the database.

11.4.2 Importing (restore)Before performing the service tool import, it is required that you have IBM Tivoli SAN Manager installed and running.

1. Stop SAN Manager service

2. Unpack the ITSANMservice.zip or tar file in an empty directory on IBM Tivoli SAN Manager server.

3. Modify the \tivoli\itsanm\manager\conf\services.properties. Comment out the below services and save the file.

� SANHostMgr� SANQueryEngine

Note: For a complete review of messaging, refer to the manual IBM Tivoli Storage Area Network Manager Messages, SC32-0953.

Note: Although it is recommended, It is not required to perform a shutdown of the IBM Tivoli SAN Manager application when running the SAN Manager Service Tool.

Important: Always open a zip file on the same manager operating system - there is no interchange possible between AIX and Windows managers. For example, if the snapshot was taken from an AIX manager, it can only be imported to another AIX manager.

328 IBM Tivoli Storage Area Network Manager: A Practical Introduction

� DiscoverEngineService

In Example 11-10 we show the services.properties file.

Example 11-10 service.properties file with commented out services

SM = com.tivoli.sanmgmt.middleware.TSNMServiceManagerConfigService = com.tivoli.sanmgmt.dbconnparms.ConfigService application autostart notstatic 1MessagingService = com.tivoli.sanmgmt.middleware.MessagingService.MessagingService application autostart notstatic 2SANEvent = com.tivoli.sanmgmt.event.SANEventService application autostart notstatic 3SANLicense = com.tivoli.sanmgmt.license.SANLicenseService application autostart notstatic 4#SANHostMgr = com.tivoli.sanmgmt.diskmgr.hostservice.manager.SANDiskMgrHostService application autostart notstatic 5#SANQueryEngine = com.tivoli.sanmgmt.tsanm.queryengine.QueryEngine application autostart notstatic 6SANEventCorrelatorFactory = com.tivoli.sanmgmt.tsanm.eventcorrelator.EventCorrelatorFactory application autostart notstatic 7SANAgentOutbandChangeAgent = com.tivoli.sanmgmt.tsanm.outbandchangeagent.OutbandChangeAgent application autostart notstatic 8#DiscoverEngineService = com.tivoli.sanmgmt.tsanm.discoverengine.DiscoverEngine application autostart notstatic 9SANManagerDaemon = com.tivoli.sanmgmt.tsanm.console.SanManagerDaemon application autostart notstatic 10#PFAService = com.ibm.edfi.pfa.PFAService application autostart notstatic 11#FIService = com.ibm.edfi.fi.FIService application autostart notstatic 12log = com.tivoli.sanmgmt.logging.log application autostart nonstatic 13

4. Import SAN manager database - Open a DB2 command window by typing db2cmd from a Windows command prompt. Change to the directory where you extracted the snapshot files. Execute the db2move command to restore the database. It will replace the current database.

db2move ITSANMDB IMPORT

5. Restart the IBM Tivoli SAN Manager service.

Note: The above services are disabled to prevent the IBM Tivoli SAN Manager from writing to the database at the time of the restore.

Chapter 11. Logging and tracing 329

330 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Part 6 Tivoli Systems Management Integration

In Part 6 we provide information on integrating IBM Tivoli SAN Manager with other Tivoli Systems Management products.

Part 6

© Copyright IBM Corp. 2002, 2003. All rights reserved. 331

332 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 12. Tivoli SAN Manager and TEC

In this chapter, we show how you can enhance an IBM Tivoli SAN Manager installation using IBM Tivoli Enterprise Console (TEC). We assume you have a basic understanding of TEC technology, and the examples are based on a standard pre-existing TEC installation. To learn more about TEC installation and procedures, see the redbook Early Experiences with Tivoli Enterprise Console, SG24-6015.

This chapter covers the following topics:

� Introduction to Tivoli Enterprise Console (TEC)� Configuring Rule Base� Event format� Configuring TEC Event Console� Configuring IBM Tivoli SAN Manager to forward events� Sample TEC rule to reduce the number of events sent to TEC

12

© Copyright IBM Corp. 2002, 2003. All rights reserved. 333

12.1 Introduction to Tivoli Enterprise ConsoleThe IBM Tivoli Enterprise Console (TEC) is a tool for receiving and processing formatted events. It uses a database to store the actual events. This database is divided into two separate tables: one to store the reception log and one to store the processed and probably reformatted events. TEC depends on the Tivoli Enterprise Framework.

There are five processes which make up a TEC server (see Figure 12-1):

1. tec_reception - receives events, places them in a reception buffer and writes them into the database using a Framework RDBMS Interface Module (RIM). After successfully placing the event into the reception log in the database, the status of the event is WAITING.

2. tec_rule - when an event becomes WAITING, this will cause the tec_rule process to pull in the event and place it into its Event Cache. The tec_rule process is configured using a so-called Rule Base. This can be programmed using a Prolog based language. These Prolog files are compiled and loaded into the tec_rule process. Based on the defined rules, the events are treated accordingly. They can be reformatted, matched, related, time-triggered and actions can be executed.

3. tec_dispatch - when the tec_rule process finishes processing an event, it hands it over to the tec_dispatch process. This process stores the events in to the database event repository table using RIM. It then informs the tec_server process about successfully processing the event, and if there are any tasks or actions to be executed, it informs the tec_task process to do it.

4. tec_server - this is the master process of the TEC server. It monitors all the other processes and stops and starts these. Additionally it receives a PROCESSED signal from the tec_dispatch and informs the tec_reception process to change the reception log of an event to PROCESSED. This is stored in the database accordingly.

5. tec_task - this process executes any tasks or actions requested by the rule engine and optionally gives a return code back to it.

334 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 12-1 TEC architecture

A Rule base is divided into event class definitions, which define the attributes of an event; and rules, which define what should be done with an event.

IBM Tivoli SAN Manager ships only a class definition file (so called baroc file) but no rule file.

Events can be received either via Tivoli Enterprise Framework mechanisms (which requires some software to be installed on each event sender) or via a socket connection (which only requires that events are sent according to TEC formats). IBM Tivoli SAN Manager sends its events via a socket connection directly to the TEC server.

In order to view the events and assign them to administrators to be treated, there is a Java based program called the TEC Console. This connects to the event repository using Framework mechanisms (RIM) and a helper process called tec_ui_server. It can be configured to show different views for different administrators. Events can be modified graphically.

12.2 Lab environmentThe setup in our lab environment is shown in Figure 12-2.

Communication Server V2 R10

Master (tec_server)Master (tec_server) tec_task tec_task

RDBMSRDBMS

RIMRIM

tec_rule tec_rule

Event EventCacheCache

ReceptionReceptionBufferBuffer

Status = PROCESSEDStatus = PROCESSED

tec_t_evt_rec_logtec_t_evt_rec_log

EVENT

EVENT

tec_t_evt_reptec_t_evt_rep

tec_dispatchtec_dispatchtec_receptiontec_reception

Chapter 12. Tivoli SAN Manager and TEC 335

Figure 12-2 Tivoli Lab environment

The machines used in the setup are:

� TONGA

– Windows 2000 SP3– Tivoli Management Framework 4.1– Tivoli Enterprise Console 3.8 FP1– Tivoli Configuration Manager 4.2– Tivoli Monitoring 5.1.1 FP3

� PALAU

– Windows 200 SP3– Tivoli Enterprise Data Warehouse 1.1 FP2

All the other machines in the lab are running the Tivoli Light Client Framework (LCF) code, which is the basis for all Tivoli Management activities.

12.3 Configuring the Rule BaseTo receive events from IBM Tivoli SAN Manager in a TEC server, the event class definitions which IBM Tivoli SAN Manager uses must be imported to the TEC server. If you do not import them, events will not show up on your TEC console and parsing errors will appear in the TEC reception log. You can determine if your events are received by the TEC server, but the definitions are not there, by issuing the wtdumprl command on your TEC server. If you see any parsing errors (Example 12-1) on IBM Tivoli SAN Manager events, then you have not imported the class definitions.

Component placementComponent placement

EthernetTivoli Desktop

Tivoli Enterprise Console Console

Tivoli SAN Manager AgentWin2kTivoli SAN Manager Agent

AIX

Tivoli Managed Region Server (TMR) TONGA

DB2

Tivoli Configuration ManagerTivoli Monitoring

Tivoli Enterprise Data Warehouse PALAU

Tivoli SAN Manager AgentWin2k

Tivoli Enterprise Console

Tivoli Light Client Framework (LCF)

Tivoli Light Client Framework (LCF)

Tivoli Light Client Framework (LCF)

336 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Example 12-1 Output of wtdumprl when baroc file has not been imported

1~1556~1~1054253423(May 29 17:10:23 2003)### EVENT ###PhysicalRelationshipEvent;fromObjectLabel='winzone_1_1';toObjectLabel='bonnie.almaden.ibm.com';toObjectType='Host';state='Normal';msg='The association between SAN SAN 1 Zone winzone_1_1 and port 0 is normal';sub_source='SanManagerService';fromObjectType='Soft Zone';messageId='BTADE1732I';toObjectUniqueId=;uniqueId='L210000060691064CFwinzone_1_1210000E08B023629';eventType='normal';hostname='lochness';fromHighLevelDevice='Not Applicable';source='IBM Tivoli Storage Area Network Manager'; entityType='Zone2Port'; severity='HARMLESS';toHighLevelDevice='a3.88.da.60.8d.64.11.d7.9c.f1.00.a0.cc.d9.58.33';fromObjectUniqueId='E510000060691064CFwinzone_1_1';origin='9.1.38.167';END

### END EVENT ###PARSING FAILED

To import the event class definitions, open the Tivoli Desktop and double-click the Event Server icon. In the window (Figure 12-3) you see the defined rule bases, with the active one highlighted by an arrow.

Figure 12-3 Active Rule Base

Choose the active rule base and right-click on it. Select Import (Figure 12-4).

Figure 12-4 Import Rule Base

Chapter 12. Tivoli SAN Manager and TEC 337

Select the check-box Import Class Definitions and enter the fully qualified path to the definitions file. This file is on the IBM Tivoli SAN Manager CD and is called ITSANM_120.baroc.(Our example uses a copy of this file on disk).

The Position to insert depends on how many events you expect to receive from IBM Tivoli SAN Manager and on the hierarchical dependencies inside the class structure. Since the Tivoli SAN Manager classes depend only on the root EVENT, you could put it right after that event class. However, since classes are matched from the top to bottom, put the busiest event classes higher in the hierarchy than less busy classes. We put it at the very bottom, because we do not expect very many events (Figure 12-5).

Figure 12-5 Import Class Definitions

After the class definitions are imported we must compile the rule base to incorporate the changes (as shown in Figure 12-6). To compile, right-click on the active rule base icon and select Compile.

338 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 12-6 Compile Rule Base

Carefully check the output for any compilation errors. If there were none, load the rule base - right-click on the active rule base icon and selecting Load. Select the correct option as in Figure 12-7. You must recycle the event server whenever you make any changes to the class definitions. If you only changed rules, then recycling the event server is not necessary.

Figure 12-7 Load Rule Base

Stop and start the Event Server by right-clicking its icon on the Tivoli Desktop (Figure 12-8).

Chapter 12. Tivoli SAN Manager and TEC 339

Figure 12-8 Restart TEC Server

12.4 Configuring TEC Event ConsoleThe TEC Event Console allows you to view the events the TEC server has received and processed. This is an installable Java GUI installed on desktop machines. You must be assigned as an operator to an Event Console to view events. A Console can be divided into multiple Event Groups, which sort the events into meaningful groups. Each Event Group contains one or more Event Filters to separate events. This example assumes you are working with a Tivoli administrative user ID which is authorized to do configures TEC. In the Console in Figure 12-9, there is an Event Group named All which shows all the events.

To make the changes click select Configuration from the Windows menu.

Figure 12-9 TEC Console Configuration

In the Configuration dialog there are three folders:

� Event Groups� Consoles� Operators

First we have to create an Event Group to specify filters to sort out the IBM Tivoli SAN Manager events. Right-click Event Groups and select Create Event Group (Figure 12-10).

340 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 12-10 Create Event Group

Name the Event Group (for example, ITSANM), right-click it and select Create Filter (Figure 12-11).

Figure 12-11 Create Filter in Event Group

On the resulting dialog, enter a filter description select Add Constraint (Figure 12-12).

Chapter 12. Tivoli SAN Manager and TEC 341

Figure 12-12 Event Group Filter

Choose Class as Attribute and Operator In, then select SANManagerEvent in the Value window (Figure 12-13).

Figure 12-13 Add Constraint

This will add a constraint to our filter ITSANM. If you add multiple constraints, they behave as a boolean AND. If you add more filters to an Event Group they behave as a boolean OR. You can test if your filter matches any events by clicking the Test SQL button on Figure 12-12. If there are no events in the TEC repository, then you will get zero matching events. You can view the constraint in plain SQL by clicking the little arrow above the Help button on Figure 12-12. It will display similar to Figure 12-14.

342 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 12-14 Event Group Filter

After creating the Event Group, we must assign it to a Console. We assume that you already have a Console defined, so right-click on it and select Assign Event Group. The menu in Figure 12-15 appears.

Figure 12-15 Assign Event Group

Select the appropriate roles and click OK. You will see output similar to Figure 12-16.

Chapter 12. Tivoli SAN Manager and TEC 343

Figure 12-16 Assigned Event Groups

Your Console should now have the ITSANM Event Group assigned to it (Figure 12-17).

Figure 12-17 Configured Console

After configuring the Event Console, you can see the results by selecting Summary Chart View from the Windows menu. This displays the actual event viewer, with all configured event groups (Figure 12-18).

344 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 12-18 TEC Console main window

Clicking on a particular event group bar opens the event viewer for that group (Figure 12-19).

The upper half of the window shows the events which are assigned to you to solve. You can acknowledge, close, run tasks or view the details of the selected event.

Figure 12-19 TEC console

If you select an event and click the Details button, the window in Figure 12-20 opens. It describes in plain text the most important details of the selected event.

Chapter 12. Tivoli SAN Manager and TEC 345

Figure 12-20 General tab of event

To see a complete list of all event attributes, select the Attribute List tab (Figure 12-21). There you can get additional information on where the event originated, when it has occurred, when it has been received by the TEC server and other fields.

346 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 12-21 Event attribute list

12.5 Event formatThe event classes IBM Tivoli SAN Manager uses and the format of these are described in Appendix B “Hints and Tips” in IBM Tivoli SAN Manager Planning and Installation Guide, SC23-4697.

Chapter 12. Tivoli SAN Manager and TEC 347

12.6 Configuring Tivoli SAN Manager event forwardingAfter we have prepared the Tivoli Event Console Server (TEC) to receive events from IBM Tivoli SAN Manager, we must enable IBM Tivoli SAN Manager itself to forward events to TEC.

12.6.1 Set the event destinationFrom the NetView console, select SAN -> Set Event Destination (Figure 12-22).

Figure 12-22 Set Event Destination

In the dialog, the only information that is mandatory is the hostname and port of the TEC server. If it is running on Windows the standard port is 5529, for UNIX TEC servers enter 0.

Select Yes to enable TEC logging (Figure 12-23) and click OK.

348 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 12-23 Enable TEC events

12.6.2 Configure NetView-TEC adapterSince Tivoli NetView for Windows does not have a graphical rule builder (unlike NetView for UNIX), it is more difficult to configure additional rules to forward events from NetView to TEC. A program is provided for Tivoli SAN Manager to configure additional SNMP events to be forwarded.

To invoke this, select Start -> Programs -> NetView -> Accessories -> Configure TEC adapter. This opens up a Java GUI as shown in Figure 12-24.

Figure 12-24 Configuration GUI

First, you must decide whether to send events using integrated Tivoli (TME®) mechanisms (this requires you to install a Tivoli Managed Node on the IBM Tivoli SAN Manager) or non-Tivoli communications.

Chapter 12. Tivoli SAN Manager and TEC 349

The main advantage of the Tivoli integrated method is that it caches the events if the TEC server is down. It has also advantages in Firewall configurations, because you can define a single port to cross the firewall and additionally ssl-encrypt the connection. But installing the Managed Node software requires disk and memory on the Manager, and configuration changes in the Tivoli environment, so check with your Tivoli administrators to determine which method to use.

Non-TME communication methodIf you choose the non-TME method, the adapter will simply format the events and send them via a socket connection to the TEC server. Select non TME from the pull-down menu (Figure 12-25).

Figure 12-25 Choose type of adapter

You need to enter the full qualified hostname of your TEC server (Figure 12-26).

Figure 12-26 Enter TEC server name

The next question asks for the platform of your TEC server. If you are using UNIX, then the port will be dynamically assigned using RPC-Portmapper. If you are using Windows, there is a fixed port (Figure 12-27).

350 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 12-27 TEC server platform

Specify the TEC port for the Windows TEC server (Figure 12-28).

Figure 12-28 TEC server port

In the next window you can specify which type of events will be forwarded from NetView on IBM Tivoli SAN Manager to the TEC (Figure 12-29). This will update your trapd.conf file in the NetView installation. With this you will be able to forward received SNMP events from monitored SAN devices without any knowledge of the NetView product (Figure 12-29).

Figure 12-29 Configure forwardable events

After pressing Next, you can specify for each NetView SmartSet, which events should be forwarded to TEC. This gives you the flexibility to suppress events from one group of hosts, but pass them for another one (Figure 12-30).

Chapter 12. Tivoli SAN Manager and TEC 351

Figure 12-30 Choose SmartSets

All the options can be modified later, by starting the configuration program again. After clicking Next, the adapter will be configured (Figure 12-31).

Figure 12-31 Configure adapter

To start TEC forwarding select Yes and Next (Figure 12-32).

Figure 12-32 Start the adapter

After you have followed all the instructions, you should soon receive some events from your IBM Tivoli SAN Manager to TEC.

12.7 ExampleIn this example, we disconnected a Fibre Channel cable between the host BONNIE and the ITSOSW1 FC-switch. After a short while, the IBM Tivoli SAN Manager shows that the

352 IBM Tivoli Storage Area Network Manager: A Practical Introduction

connection between the host and the switch is down, by changing the color of the connection to red (Figure 12-33).

Figure 12-33 Defective cable from bonnie to itsosw1

At the same time some events are sent to TEC (Figure 12-34). There is one Physical Entity Event, indicating that the host is missing and three Physical Relationship Events indicating that the association between the host and the SAN, the zone, and the switch is missing. Depending on how many LUNs and zones are associated with your host, there can be a large number of events for a single cable fault.

Figure 12-34 Events for cable fault

Chapter 12. Tivoli SAN Manager and TEC 353

As soon as the error has been recovered, the respective normal events are sent to TEC (Figure 12-35).

Figure 12-35 Condition cleared

12.8 Sample TEC ruleThe fact that IBM Tivoli SAN Manager sends an event whenever a resource or association with a resource is missing, and another event when each of these resources is reachable again, can lead easily to an overwhelming number of events generated.

In our (minimal) lab environment, we got 100 events when we stopped the IBM Tivoli SAN Manager agent on an AIX machine. When we re-started the agent, we got an additional 100. That makes 200 events just for recycling an agent.

The first thing that comes in mind is: event filtering. But when you look at those events, you will recognize that each one of these gives you important information. What if just one LUN is not reconnected and this LUN contains your most important database files?

Therefore we recommend using TEC’s advanced rule processing capabilities. Since (at the time of writing) IBM Tivoli SAN Manager does not ship with a TEC rule file, we have written a small, but very effective sample rule.

Our goal for this rule was to automatically close events that get a corresponding clearing event (along with the clearing event itself). As an example when this rule is incorporated, after an agent goes down and comes up again, there are only two events left in the TEC console, saying that the agent was down (compared to in the order of 200 events without the rule). If resources remain down, you would get additional events reflecting this. So you only receive the events reflecting the current status of your resources, and you can tell at once which resources are still down.

Otherwise, you would have to go through the 200 events, manually match them accordingly, and close those that are cleared.

Example 12-2 shows the TEC prolog code for the rule.

354 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Example 12-2 Sample TEC rule

rule:close_missing_itsanm_events: ( event: _event of_class within ['PhysicalEntityEvent', 'LogicalEntityEvent', 'PhysicalRelationshipEvent', 'LogicalRelationshipEvent'] where [ status: equals 'OPEN', hostname:_host, eventType: equals 'normal', uniqueId: _uid ] , reception_action: ( all_instances(event: _missing_event of_class within ['PhysicalEntityEvent', 'LogicalEntityEvent', 'PhysicalRelationshipEvent', 'LogicalRelationshipEvent'] where [ status: equals 'OPEN', hostname: equals _host, eventType: equals 'missing', uniqueId: equals _uid ] ), set_event_severity( _missing_event, 'HARMLESS' ) , set_event_status( _missing_event, 'CLOSED' ), set_event_administrator(_missing_event, 'ITSANM_rule'), set_event_administrator(_event, 'ITSANM_rule'), set_event_status( _event, 'CLOSED' ) ) ).

The rule looks for incoming events matching these event classes of IBM Tivoli SAN Manager:

� PhysicalEntityEvent� LogicalEntityEvent� PhysicalRelationshipEvent� LogicalRelationshipEvent

These events must be clearing events (slot eventType equals normal).

When such an event is received, it fires the following actions:

� Look at the event repository. If there are any events with the same classes, which are ’missing’ events (slot eventType equals missing) AND if they have the same uniqueId slot, then do the rest of the actions.

– Set event severity of the ’missing’ events to HARMLESS.

– Close those events.

– Set the event administrator of both events to ITSANM_rule, to easily determine that these events were closed by our rule.

– Close the clearing event as well.

Important: The slot uniqueId, contains a unique event ID describing all the involved resources. That makes sure that the clearing event points to the originating missing event.

Chapter 12. Tivoli SAN Manager and TEC 355

Paste the sample code to a file named ITSANM.rls and import it to your rule base as described in the procedure for the baroc file in 12.3, “Configuring the Rule Base” on page 336. The only differences are to select Import Rule Set instead of Import Class Definitions (Figure 12-5 on page 338) and you do not need to recycle the TEC server, just Load and Activate it (Figure 12-7 on page 339).

356 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager

This chapter shows how to use IBM Tivoli Configuration Manager to distribute IBM Tivoli SAN Manager Agent code.

We assume you have a basic understanding of IBM Tivoli Configuration Manager and a running installation of Tivoli Enterprise Framework V3.7.1 or 4.1 and IBM Tivoli Configuration Manager V4.2. For more information about these products refer to the redbook All About IBM Tivoli Configuration Manager V4.2, SG24-6612.

This chapter covers the following topics:

� Introduction to IBM Configuration Manager

� Inventory to determine who has which version

� Software Distribution - distributing IBM Tivoli SAN Manager Agents and GUI (silent installation)

13

© Copyright IBM Corp. 2002, 2003. All rights reserved. 357

13.1 Introduction to IBM Tivoli Configuration ManagerIBM Tivoli Configuration Manager, Version 4.2, is a solution for controlling software distribution and asset management inventory in a multiplatform environment. It focuses on deploying and managing software in complex, distributed enterprise environments. IBM Tivoli Configuration Manager is a key solution to rapidly and efficiently deploying complex mission-critical or desktop productivity applications to multiple locations from a central point and to gather and maintain the inventory information about hardware and software assets, easily, quickly, and accurately.

Tivoli Configuration Manager consists of the following main components:

� Inventory enables you to gather and maintain up-to-date inventory asset management information in a distributed environment. This helps system administrators and accounting personnel to manage complex, distributed enterprises.

� Software Distribution enables you to install, configure, and update software remotely within your network.

Tivoli Configuration Manager also provides the following services:

� Activity Planner� Change Manager� Resource Manager� Web Interface� Enterprise Directory Query Facility

Activity Planner enables you to define a group of activities that originate from different applications in an activity plan, submit or schedule the plan for running, and monitor the plan while it runs.

Change Manager functions with Activity Planner to support software distribution, inventory, and change management in large networks. It uses reference models to simplify the management of the network environment.

You can use Resource Manager, together with Software Distribution and Inventory, to perform the management operations for pervasive devices.

You can use the Web Interface to install and manage various Tivoli Configuration Manager Web objects. The Web Interface has a server component that pushes software packages, inventory profiles, and reference models from the Tivoli region to the Web Gateway where they are stored until they are pulled by the Web Interface endpoint.

With enterprise directory integration, you can exploit organizational information that is stored in enterprise directories in order to determine a set of targets for a software distribution or an inventory scan. The Enterprise Directory Query Facility enables you to select a specific directory object, or container of directory objects, as subscribers for a reference model or an activity plan.

13.2 Inventory to determine who has which versionTo determine which machine in your environment has which product and version installed, you can use the Inventory part of IBM Tivoli Configuration Manager. The process to query inventory information from your nodes includes four steps:

1. Create an inventory profile in Tivoli Framework2. Distribute profile to endpoints

358 IBM Tivoli Storage Area Network Manager: A Practical Introduction

3. Build a query4. Run the query

13.2.1 Create an inventory profile in Tivoli FrameworkOpen the Tivoli Desktop and navigate to your Inventory Policy Region. In our environment this is done by opening the tonga-region Policy Region (Figure 13-1).

Figure 13-1 Tivoli Desktop

We created separate Policy Regions for each Tivoli product. Double-click Inventory Policy Region (Figure 13-2).

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 359

Figure 13-2 Policy Region tonga-region

Make sure that the Inventory Policy Region contains the InventoryConfig resource as a Managed Resource. To determine if it has been set, right-click the Policy Region and select Managed Resources. The dialog in Figure 13-3 appears.

Figure 13-3 Managed Resources for Inventory

In our environment we created the default Query Libraries with the script inventory_query.sh in the bin/generic/inv/SCRIPTS/QUERIES directory of the Tivoli installation directory and created a Profile Manager called Inventory_default_PM (Figure 13-4). To create a Profile Manager select Create in the top menu and select Profile Manager.

360 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-4 Policy Region Inventory

Double-click the Inventory_default_PM Profile Manager and the following dialog appears (Figure 13-5).

Figure 13-5 Profile Manager Inventory

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 361

Create an Inventory Profile by clicking Create in the top menu and select Profile. Enter the name (P_SoftwareScan in our example), and select InventoryConfig as the Profile type. Then right-click on the newly created Profile and select Properties. The window that appears shows you the global properties of the Inventory Profile (Figure 13-6).

Figure 13-6 Inventory Profile Global Properties

Since we want to create a software only inventory scan, you should deselect all hardware related check boxes. The only ones we need are the PC Software section (Figure 13-7) and the UNIX Software section (Figure 13-8).

362 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-7 Inventory Profile PC Software

There are two possible ways to collect software information from endpoints. One is to scan all the files on a machine and compare them to a predefined list, thus determining an installed product by filename and filesize of a significant file in the software package. IBM Tivoli SAN Manager ships these so called Inventory Signature files with the product. They can be found in the installation directory in the conf/TIVINV subdirectory. The signature files are zero bytes in length and are recognized by filename (BTSMGR01_01.SIG for IBM Tivoli SAN Manager - Manager Version 1.1 and 1.2). The signatures for IBM Tivoli SAN Manager are already incorporated in the latest inventory signature files, which you can download from the IBM Software support web site.

Another way to determine installed software is by querying the native software repository of the operating system. This gives you very fast scans, but relies on the fact that the software actually registers itself in the operating system, rather than just copying files to your machine.

For IBM Tivoli SAN Manager, both methods are available - and your choice depends on the policies of your IBM Tivoli Configuration Manager environment.

In our examples we chose to use the native software query, so we check the Scan Operating System for Product Information boxes in the dialog (Figure 13-8), not the Scan for File Information.

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 363

Figure 13-8 Inventory Profile UNIX Software

Close the dialog with the OK button and then distribute the Inventory Profile to your Endpoints. Right-click the Profile and select distribute (Figure 13-9).

364 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-9 Distribute Inventory Profile

This opens a dialog where you can choose the machines on which the inventory scan should occur. Select the machines and click Distribute & Close (Figure 13-10).

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 365

Figure 13-10 Distribute Inventory Profile dialog

You can determine the status of the inventory scan with a tool called Distribution Status console. If this is installed in your environment, the icon will be on the main screen of your Tivoli Desktop (Figure 13-1 on page 359). Double-click on it to open the console (Figure 13-11).

366 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-11 Distribution Status Console

In the upper window select All Distributions and double-click the P_SoftwareScan Inventory Application. In the lower window select All Nodes. You can see which scans successfully completed, pending, failed etc.

When the scans are complete, you can query the collected information. There are a lot of standard queries, but we want to gather only data for IBM Tivoli SAN Manager. Therefore we create a new query by clicking Create -> Query in the menu (Figure 13-12).

Figure 13-12 Create Query Library

Name the Query and select the inv_query as the repository. This is the Inventory Database RIM object. The table name which contains the native software information is NATIVE_SWARE_VIEW. Select the columns you want and add a filter which says: Column

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 367

name PACKAGE_NAME LIKE ’IBM Tivoli Storage Area Network Manager%’. This will give you an output of all Software Packages whose names begin with IBM Tivoli Storage Area Network Manager. The % is the wildcard in SQL (Figure 13-13).

Figure 13-13 Edit Inventory Query

At the bottom there is a button called Run Query, which runs the query while you are editing it. The output show all the installed IBM Tivoli SAN Manager products including agents, manager and consoles (Figure 13-14).

368 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-14 Output for IBM Tivoli SAN Manager Query

You can also query the Inventory database with a native DB2 client. That enables you to connect to Business Intelligence tools or script based applications.

The query feature is very powerful - there is a lot of other information available. For example, together with the hardware scans you can determine which Fibre Channel cards are installed and which firmware levels and drivers they are using.The following query showed all the IBM software which was on the endpoints (Figure 13-15).

Figure 13-15 Output for IBM Query

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 369

13.3 Software distribution To automatically deploy a large number of IBM Tivoli SAN Manager agents, you can use the Software Distribution component of IBM Tivoli Configuration Manager. The distribution process has four steps:

1. Build software package with the Software Package Editor2. Create software distribution profile in Tivoli Framework3. Import and build software package4. Perform installation/uninstall tasks

We are using the lab setup shown in Figure 12-2 on page 336.

13.3.1 Build software package with Software Package EditorBefore you can use the Software Package Editor you have to install it from the Configuration Manager CD. It must be either installed on a managed node or a Tivoli endpoint. The reason for this is that you can automatically fetch the software package once built on that host. Figure 13-16 shows the Software Package Editor with a new package which we called ITSANM-Agent.

Figure 13-16 Software Package Editor with new package ITSANM-Agent

You can build one package for each platform or all platforms in one. The benefit of separating the packages by operating system is that you prevent having to download all the code to all the endpoints before installation occurs. If temporary space is an issue, you should split into multiple packages. This in turn makes it slightly more complicated in installation tasks, because you have to group the endpoints by operating system. We will give some simple examples here, but if your enterprise has already deployed Configuration Manager, then the design rules will be in place, and you should build the packages according to them.

370 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Right-click the package name and select Properties. You get the dialog shown in Figure 13-17. Enter the package version and a title for your package. Leave all the other parameters at their default values.

Figure 13-17 Properties dialog

For the actual installation we use the silent install procedure described in “Silent install of IBM Tivoli Storage Area Network Manager” on page 139. First copy the installation media to the hard drive and modify the agent.conf file to suit the environment.

After setting the package properties, we add objects to the package. From the window in Figure 13-16, click the tab Execute program as shown in Figure 13-18.

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 371

Figure 13-18 Add an execute program action to the package

With this action you can distribute files to the endpoint, run the provided script and delete the temporary files again.

After selecting the button, the Execute Program Properties dialog appears (Figure 13-19).

Note: Once the installation program finishes, these files are deleted. So be aware that if the setup program spawns other programs and finishes, the other processes cannot access the files and the installation fails.

372 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-19 Install dialog

Initially the Install tab opens, and you have to enter the fully qualified path to the installation setup program. The example shows the installation of the Windows Tivoli SAN Manager agent. This must be the path as it appears after transferring the files to the endpoint, so it could be different from the directory structure on the node where you are building the filepack. Don’t include any arguments — they go into the Advanced dialog (Figure 13-20).

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 373

Figure 13-20 Advanced tab

In the arguments field, enter the parameters for silent installation. In our case the full installation program is:

setup.exe -silent -options agent.opt

Note that we have not included the fully qualified path to the agent.conf file. Instead we used the Working Directory entry to point to the option file. Optionally you can redirect standard out and standard error to files. End this dialog with the OK button.

After specifying the program to execute, we must add the installation files. click Add next to the Co-requisite section on Figure 13-19. Figure 13-21 appears.

374 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-21 Add directory

Select the source files which should be copied to the endpoint and choose the path where they should be copied to. Be sure to check the Descend directories box. Click OK to close.

This should be sufficient for the installation process. Configuration Manager can also do uninstallation — to configure this, select the Remove tab from Figure 13-19 on page 373. The dialog in Figure 13-22 appears.

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 375

Figure 13-22 Remove dialog

This time we do not need any co-requisite files to be copied to the endpoint. A single command is sufficient to remove the software as described in the silent installation chapter “Silent install of IBM Tivoli Storage Area Network Manager” on page 139. The uninstallation program resides in the installation directory of the IBM Tivoli SAN Manager agent. It is specified at installation time in the agent.conf file. We need an argument for the uninstallation program. To open the dialog click Advanced (Figure 13-23).

376 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-23 Advanced properties

The only parameter to specify is -silent. Be sure to add the working directory for the process.

We chose to make just one software package for Windows and AIX machines, so in order to not execute the above program on an AIX machine, you can specify a condition when to run that action. There is a Condition button at the top of right hand corner of Figure 13-22. Figure 13-24 appears.

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 377

Figure 13-24 Condition

Choose os_name from the list box, add an == operator and enter Windows_NT. This will ensure execution only on a certain platform.

Using the same procedure, we added an extra action for the AIX installation, starting from the Execute Program Properties dialog shown in Figure 13-19 on page 373. The actions to define are mainly the same except for the paths and the setup.aix program. Also we added a condition which allows execution only on AIX machines.

The ready-to-build software package is shown in Figure 13-25.

378 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-25 Ready-to-build software package

Save this package to a .sp file on your server and exit the Software Package Editor.

13.3.2 Create software distribution profile in Tivoli FrameworkOpen your Tivoli Desktop and navigate to the Software Distribution policy region. Make sure it has the Software Distribution package as a managed resource in the properties menu. To determine if it has been enabled, click Properties -> Managed Resources and check if the SoftwarePackage resource is on the left side. Then create a Profile Manager for use by IBM Tivoli SAN Manager packages (Figure 13-26).

Figure 13-26 Policy Region with Profile Managers

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 379

Double-click the object PM_SD_ITSANM to open the Profile Manager and create a Profile with the name of your file package including the version (Figure 13-27).

Figure 13-27 Create Software Package Profile

After you have created the Profile, an empty package icon appears in the Profile Manager. Add any subscribers you want to distribute the package to.

380 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-28 Profile Manager with Profiles and Subscribers

Next we need to import the previously defined Software package to the Profile we just created. Right-click the Profile and choose Import (Figure 13-29).

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 381

Figure 13-29 Import Software Package

A dialog appears, where you can select the node on which you have previously created the Package and the path to the .sp file. With Build, you select to include all the source files and programs and actions into one single file (.spb) to be distributed to the target endpoint. Enter the location where you want to store the .spb file. You might want to store it on your software distribution server or on any of your software depot servers. If your are rebuilding it, check the Overwrite box (Figure 13-30).

382 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-30 Import and build a software package

The icon of the package should now be a sealed package, ready to ship to your targets. To install, right-click the package and choose Install (Figure 13-31).

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 383

Figure 13-31 Install a software package

The install dialog, shown in Figure 13-32, lets you select the endpoints to install the software. Our package will work on Windows and AIX servers. Additional checks can be made, whether the software is already installed or with the Change Manager feature, if you are allowed to install the software due to licensing issues. For additional information, see the redbook All About IBM Tivoli Configuration Manager V4.2, SG24-6612.

384 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 13-32 Install Software Package

You can also schedule the installation and query inventory to look for hardware or software constraints. To ensure that every host in your SAN environment has a Tivoli SAN Manager agent, you can use the strategies described in Implementing Automated Inventory Scanning and Software Distribution After Auto Discovery, SG24-6626 to discover new nodes via Tivoli NetView, install an endpoint, perform an inventory query and automatically deploy the IBM Tivoli SAN Manager agent on them.

Another method of identifying hosts to install software on, is querying an LDAP directory like Microsoft Active Directory or IBM Directory with the Enterprise Directory Query facility. Then you would be able to create a machine group for IBM Tivoli SAN Manager, and automatically deploy the software once a machine belongs to the group.

Configuration Manager enables you to remove the software as well. For this function, right-click the package and select Remove (Figure 13-33).

Chapter 13. IBM Tivoli SAN Manager and Configuration Manager 385

Figure 13-33 Remove a Software Package

All the other options like verify, clean, and so on are not defined and will not work.

386 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 14. Integration with Tivoli Enterprise Data Warehouse

This chapter provides general information for the following topics:

� Introduction to IBM Tivoli Enterprise Data Warehouse

� IBM Tivoli San Manager Data Warehouse Pack

14

© Copyright IBM Corp. 2002, 2003. All rights reserved. 387

14.1 Introduction to IBM Tivoli Enterprise Data WarehouseThe Tivoli Enterprise Data Warehouse (TEDW) is an application used to collect and manage data from various Tivoli and non-Tivoli system management applications. The data is imported from the source applications, stored centrally, and further processed to fit the needs of the end users. We describe the basic components of IBM Tivoli Enterprise Data Warehouse in the logical order of the data flow, as shown in Figure 14-1.

Figure 14-1 Tivoli Data Warehouse data flow

The first step to introducing TEDW is enabling the source applications. This means to provide all tools and customizations necessary to import the source operational data into the central data warehouse. All components needed for that task are collected in warehouse packs for each source application.

An important part of the warehouse packs is the ETL programs Extract, Transform, and Load). In principle, ETL programs process data in three steps. First they extract the data from a data source. Then the data is validated, transformed, aggregated, and/or cleansed so that it fits the format and needs of the data target. Finally the data is loaded into the target database.

In TEDW there are two types of ETLs. The central data warehouse ETL pulls the data from the source applications and loads it into the central data warehouse. The central data warehouse ETL is also known as source ETL or ETL1. The second type of ETL is the data mart ETL.

The central data warehouse (CDW) is the database that contains all enterprise-wide historical data (with hour as the lowest granularity). This data store is optimized for the efficient storage of large amounts of data and has a documented format that makes the data accessible to many analysis solutions. The database is organized in a very flexible way, and you can store data from new applications without adding or changing tables.

The data mart ETL extracts a subset of historical data from the central data warehouse that contains data tailored to and optimized for a specific reporting or analysis task. This subset of data is used to create data marts. The data mart ETL is also known as target ETL or ETL2.

Central Data

Warehouse

Control Server:IBM DB2®

DWC

ITM

Inventory

TEC

Source App

ETL

Tivoli

ReportingInterface

Data Marts

Data Marts

Data Marts

Data Marts

ETL

Tivoli Warehouse

Data Marts

Tivoli Reporting Services

IBM

Source Apps

Cognos

BusinessObjects

Business Intelligence Tools

Brio

Data Marts

ETL

ETL

ETL

WarehouseMetadata

388 IBM Tivoli Storage Area Network Manager: A Practical Introduction

A data mart satisfies the needs of a specific department, team, or customer. The format of a data mart is specific to the reporting or analysis tool you plan to use. Each application that provides a data mart ETL creates its data marts in the appropriate format.

TEDW provides a Report Interface (RI) that creates static two-dimensional reports of your data using the data marts. The RI is a role-based Web interface that can be accessed with a Web browser without any additional software installed on the client. You can also use other tools to perform OLAP analysis, business intelligence reporting, or data mining.

The Control server is the system that contains the control database, which contains metadata for Tivoli Enterprise Data Warehouse and from which you manage your data warehouse. The Control server controls communication between the Control server, the central data warehouse, the data marts, and the Report Interface.

The Control server uses the Data Warehouse Center to define the ETL processes and the star schemas used by the data marts. You use the Data Warehouse Center to schedule, maintain, and monitor these processes.

For more information about Tivoli Enterprise Data Warehouse, see Introduction to Tivoli Enterprise Data Warehouse, SG24-6607.

14.2 IBM Tivoli SAN Manager Data Warehouse PackIBM Tivoli SAN Manager Version 1.2 support for IBM Tivoli Enterprise Data Warehouse Version 1.1 will provide a central repository of historical data for use by Tivoli Service Level Advisor. Data from the sources, IBM Tivoli Storage Resource Manager, IBM Tivoli SAN Manager and IBM Tivoli Storage Manager, will be collected and stored in the repository. The IBM Tivoli SAN Manager Version 1.2 release will implement the central data warehouse ETL (ETL1) so data about switch status and port status is available for the Service Level Advisor product to use in its reporting. The ETL will extract the following information:

� Switch status� Port Status

To support handling of switch and port state transition in IBM Tivoli SAN Manager, a set of triggers on the extract tables will be provided that copy transition records into the archive table. These records will be extracted as part of the daily extract. For Release 1.1 of the IBM Tivoli SAN Manager Warehouse Pack, triggers in the DB will be provided to copy switch and state transition to the archive table to be used in data extraction to the data warehouse. Each archive record will have the current UTC timestamp recorded in a new field to provide pruning control of records.

The data mart ETL (ETL2) is not available for IBM Tivoli SAN Manager data at the time of writing.

Chapter 14. Integration with Tivoli Enterprise Data Warehouse 389

390 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Chapter 15. Tivoli SAN Manager and Tivoli Monitoring

This chapter describes some possibilities for using IBM Tivoli Monitoring to ensure proper operation of the IBM Tivoli SAN Manager—Manager machine. We assume you have a basic understanding and a fully running installation of the following products:

� Tivoli Framework 3.7.1 or 4.1� IBM Tivoli Monitoring 5.1.1� IBM Tivoli Enterprise Console 3.8

The following topics are covered:

� Introduction to IBM Tivoli Monitoring� Using Tivoli Monitoring to maintain IBM Tivoli SAN Manager� Daemons to monitor and restart actions

15

© Copyright IBM Corp. 2002, 2003. All rights reserved. 391

15.1 Introduction to IBM Tivoli MonitoringFigure 15-1 presents a high-level overview of the interaction between various components of IBM Tivoli Monitoring 5.1. The IBM Tivoli Monitoring 5.1 profile contains, among other information, a resource model. The resource model is a collection of monitors that correlate between themselves before attempting to perform a notification action. The IBM Tivoli Monitoring 5.1 profile is distributed to the endpoints to monitor one or more resources (examples of typical resources are hard disk space, paging space, and process/service). Based on configuration settings in the IBM Tivoli Monitoring 5.1 profile, the engine runs on the endpoint and performs the necessary monitoring on the resources that are specified in the distributed resource model(s). The Web Health Console obtains logged data from selected endpoints and displays the "health" of the endpoints for their resources.

Figure 15-1 IBM Tivoli Monitoring Architecture

15.2 IBM Tivoli Monitoring for IBM Tivoli SAN ManagerThere are many possibilities to use IBM Tivoli Monitoring to help secure a productive installation of IBM Tivoli Storage Area Network Manager. The base product of IBM Tivoli Monitoring ships with a wealth of predefined resource models, including:

� Filesystems� CPU� Memory� TCP/IP� Network interface� Event log

Display

Rollup

EndpointUNIX/Linux

Defaults

Profile Defaults

Profile

Trend Analysis

TMR

ITMHeartbeat

Data warehouse

Install

DesignCreateDebug

Workbench

Web health console

EndpointNT/W2K

ITM Engine ITM Engine

Distribute

Customize/Distribute

Get Data

ResourceModel

392 IBM Tivoli Storage Area Network Manager: A Practical Introduction

You can use any of these to monitor the basic functions of your operating system. There are numerous additional modules which provide special monitoring capabilities for other software products. These include:

� DB2� WebSphere Application Server� Oracle� Microsoft Active Directory� Apache / IIS

If you want in depth monitoring for your IBM Tivoli Storage Area Network Manager DB2 instance, you can use these additional modules.

In the example in this book, we use the shipped monitor Parametric Services to watch the status of the Windows services, which are required to run IBM Tivoli Storage Area Network Manager. Additionally there is a default action to restart stopped services.

15.3 Daemons to monitor and restart actionsThis section describes how to configure IBM Tivoli Monitoring to monitor the IBM Tivoli SAN Manager Windows services.

Open the Tivoli Desktop and navigate to the Monitoring Policy Region (Figure 15-2).

Figure 15-2 Policy Region tonga-region

Create a profile manager to contain the monitoring profiles. Select Create -> Profile Manager and create a dataless Profile manager. Our example shows a Profile manager called PM_DM_ITSANM (Figure 15-3).

Chapter 15. Tivoli SAN Manager and Tivoli Monitoring 393

Figure 15-3 Profile Manager PM_DM_ITSANM

Open the Profile Manager and select Create -> Profile and choose a Tmw2kProfile (which is the Monitoring profile resource). If this entry doesn’t show up in the list, make sure the Tmw2kProfile is in the managed resources list of the Policy Region. The example shows a Profile called P_DM_ITSANM in Figure 15-4.

Figure 15-4 Create Monitoring Profile

Double-click on the newly created profile and in the window that appears, and click Add with Defaults. This will open up a chooser window, where you can select the resource model you want to add to your profile. In the Category list box choose Windows and select Parametric Services (Figure 15-5).

394 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 15-5 Add Parametric Services Model to Profile

After adding the resource model, we have to edit the model to include the services we want to monitor. Click Edit (Figure 15-6).

Chapter 15. Tivoli SAN Manager and Tivoli Monitoring 395

Figure 15-6 Edit Resource Models

In this window, we can adjust attributes belonging to that resource model. To specify the services to monitor, open the Parameters window (Figure 15-7). You must enter the names of the services exactly as they appear in the Windows Registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. The service names, which IBM Tivoli Storage Area Network Manager needs to run are:

� DB2� IBMWAS5Service - ITSANM-Manager� SNMPTRAP� NetView

396 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Figure 15-7 Parameters of Resource Model

Close this window (Apply Changes and Close) and bring up the next dialog by clicking Indications (from Figure 15-6). As you can see from the definitions, the default action, when a service is stopped or failed is to restart the service automatically. Also, a CRITICAL TEC event is generated (Figure 15-8).

Chapter 15. Tivoli SAN Manager and Tivoli Monitoring 397

Figure 15-8 Indications and actions of resource models

To enable the TEC events globally for this Profile and to specify to which TEC server the events are sent, click the Properties menu in the Profiles main window (Figure 15-4 on page 394) and the window in Figure 15-9 opens.

Figure 15-9 TEC forwarding of events from Monitoring

398 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Select the Send TEC Events check box and choose the event delivery method and TEC server. The TME (Secure) Delivery is (in most cases) the better choice, because it caches events when the Event Server is temporarily unavailable.

Click OK to close windows until you are back in the Profile Manager main window. (Figure 15-10). Subscribe the endpoints running the IBM Tivoli Storage Area Network Manager - Manager with Profile manager -> Subscriber and distribute the Profile using Profile Manager -> Distribute -> Distribute Now.

Figure 15-10 Profilemanager for Monitoring

You can determine if your resource models are running on a particular endpoint by issuing the wdmlseng command on your Tivoli Managed Region (TMR) server, as shown in Example 15-1.

Example 15-1 Determining if resource models are running

bash$ wdmlseng -e lochnessForwarding the request to the engine...

The following profiles are running:

P_DM_Basic_Win#tonga-region TMW_EventLog :Running TMW_PhysicalDiskModel :Running TMW_Services :Running TMW_TCPIP :Running TMW_MemoryModel :Running TMW_Process :Running TMW_Processor :RunningP_DM_ITSANM#tonga-region TMW_ParamServices :Runningbash$

Chapter 15. Tivoli SAN Manager and Tivoli Monitoring 399

For demonstration purposes, we stopped the NetView and the SNMPTRAP services on our manager machine. After a few seconds the following TEC events appear in the TEC console (Figure 15-11).

Figure 15-11 TEC events from Monitoring

IBM Tivoli Monitoring detected the services were stopped and restarted them accordingly.

400 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Appendix A. Advanced Topology and Sensor Event Scanners

In this appendix we provide additional information regarding the SNMP Management Information Base (MIBs) and their corresponding Object Identifiers (OIDs) used during the IBM Tivoli Storage Area Network Manager (Tivoli SAN Manager) outband topology discovery. We cover the Advanced Topology Scanner and the Sensor Events Scanner.

We provide details on the following topics:

� Advanced Topology Scanner

– MIBs and OIDs used by IBM Tivoli SAN Manager– A listing of the OIDs for each MIB– Scanning capabilities

� Sensor Event Scanner

– MIB and OIDs used by Tivoli SAN Manager– The process of retrieving/scanning MIB/OID

A

© Copyright IBM Corp. 2002, 2003. All rights reserved. 401

Advanced Topology ScannerThe Advanced Topology Scanner is used during outband discovery. It queries MIB II, FE-MIB and FC-MGMT MIBs to gather Fibre Channel switch information to build the topology. Tivoli SAN Manager only requires the use of the FC-MGMT MIB or Fibre Alliance MIB (FA-MIB) during outband discovery. It additionally queries the MIB II and FE MIB to collect optional data during discovery. The scanner attempts to query the MIB II for the OIDs shown below. See Table A-1.

Table A-1 MIB II OIDs

The scanner then proceeds to collect the fcFabricName OID from the FE MIB. See Table A-2 below. Also see 3.6.2, “Outband management” on page 69. The fcFabricName is a required object by Tivoli SAN Manager. See Table A-2.

Table A-2 FE MIB

If the OID data cannot be retrieved from the FE-MIB, the scanner proceeds to the FC MIB, where an algorithm runs and derives the fabric name. Tivoli SAN Manager requires all OID data from the FC MIB to draw an accurate topology map. If data is missing, there will be limited functionality and missing topology information. See Table A-3 for a list of the OIDS from the FC MIB used by the Advanced Topology Scanner.

MIB II

Entry Name OID

SysDescr 1.3.6.1.2.1.1.1

sysObjectID 1.3.6.1.2.1.1.2

SysContact 1.3.6.1.2.1.1.4

FE MIB

Entry Name OID

RFC2837 version pre-RFC version

fcFeFabricName 1.3.6.1.2.1.75.1.1.1 1.3.6.1.3.42.2.1.1.1

fcElementName 1.3.6.1.2.1.75.1.1.2 1.3.6.1.3.42.2.1.1.2

fcFeModuleOperStatus 1.3.6.1.2.1.75.1.1.4.1.4 1.3.6.1.3.42.2.1.1.4.1.4

402 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Table A-3 FC-MGMT MIB OIDS used by Advanced Topology Scanner

FC-MGMT MIB - Advanced Topology Scanner

Entry Name OID

Version 3.0 Version 3.1 Version 4.0

systemURL 1.3.6.1.3.94.1.2 1.3.6.1.3.94.1.2

connUnitGlobalId 1.3.6.1.3.94.1.6.1.2 1.3.6.1.2.1.8888.1.1.3.1.2 1.3.6.1.3.94.1.6.1.2

connUnitDomainId 1.3.6.1.3.94.1.6.1.11 1.3.6.1.2.1.8888.1.1.3.1.11 1.3.6.1.3.94.1.6.1.11

connUnitName 1.3.6.1.3.94.1.6.1.20 1.3.6.1.2.1.8888.1.1.3.1.17 1.3.6.1.3.94.1.6.1.20

connUnitType 1.3.6.1.3.94.1.6.1.3 1.3.6.1.2.1.8888.1.1.3.1.3 1.3.6.1.3.94.1.6.1.3

connUnitLocation 1.3.6.1.3.94.1.6.1.24 1.3.6.1.2.1.8888.1.1.3.1.21 1.3.6.1.3.94.1.6.1.24

connUnitProduct 1.3.6.1.3.94.1.6.1.7 1.3.6.1.2.1.8888.1.1.3.1.7 1.3.6.1.3.94.1.6.1.7

connUnitPrincipal 1.3.6.1.3.94.1.6.1.13 1.3.6.1.2.1.8888.1.1.3.1.13 1.3.6.1.3.94.1.6.1.13

connURL 1.3.6.1.3.94.1.6.1.10 1.3.6.1.2.1.8888.1.1.3.1.10 1.3.6.1.3.94.1.10.1.10

connUnitPortWWN 1.3.6.1.3.94.1.10.1.10 1.3.6.1.2.1.8888.1.1.6.1.9 1.3.6.1.3.94.1.10.1.10

connUnitPortUnitId 1.3.6.1.3.94.1.10.1.1 1.3.6.1.3.94.1.10.1.1

connUnitPortNodeWwn 1.3.6.1.2.1.8888.1.1.6.1.20

connUnitPortPhysicalNumber 1.3.6.1.3.94.1.10.1.18 1.3.6.1.2.1.8888.1.1.6.1.17 1.3.6.1.3.94.1.10.1.18

connUnitPortState 1.3.6.1.3.94.1.10.1.6 1.3.6.1.2.1.8888.1.1.6.1.5 1.3.6.1.3.94.1.10.1.6

connUnitLinkPortWwnY 1.3.6.1.3.94.1.12.1.8 1.3.6.1.2.1.8888.1.1.8.1.7 1.3.6.1.3.94.1.12.1.8

connUnitLinkUnitTypeY 1.3.6.1.3.94.1.12.1.12 1.3.6.1.2.1.8888.1.1.8.1.12 1.3.6.1.3.94.1.12.1.12

connUnitLinkPortNumberX 1.3.6.1.3.94.1.12.1.4 1.3.6.1.2.1.8888.1.1.8.1.3 1.3.6.1.3.94.1.12.1.4

connUnitLinkNodeIdY 1.3.6.1.3.94.1.12.1.6 1.3.6.1.2.1.8888.1.1.8.1.5 1.3.6.1.3.94.1.12.1.6

connUnitLinkAgentAddressY 1.3.6.1.3.94.1.12.1.9 1.3.6.1.2.1.8888.1.1.8.1.8 1.3.6.1.3.94.1.12.1.9

connUnitFabricId 1.3.6.1.3.94.1.6.1.29

Appendix A. Advanced Topology and Sensor Event Scanners 403

Sensor Event ScannerThis scanner displays sensors information about the switch and lists events reported by the switch. In order to collect and display Sensors/Events data, the FC MIB must be enabled. 6.2.3, “Loading MIBs” on page 212 describes this process. The Sensor data is only retrieved when the SAN Properties dialog for a switch is opened. When this occurs, an internal API call is issued and the Sensor Event Scanner is invoked to collect the data from the selected switch using SNMP queries to the FC MIB for the below OIDs. The Sensor/Event tab (see Figure A-1 on page 405) in the SAN Properties dialog is only shown if the Sensor Event Scanner successfully obtained the requested data from the switch. This process will work for switches that are discovered via inband or outband.

The Sensor Event MIB OIDs are shown below in the FC MIB. See Table A-4.

Table A-4 FC-MGMT MIB Sensor Event Scanner

FC-MGMT MIB - Sensor Event Scanner

Entry Name OID

Version 3.0 Version 3.1 Version 4.0

connUnitGlobalId 1.3.6.1.3.94.1.6.1.2 1.3.6.1.2.1.8888.1.1.3.1.2 1.3.6.1.3.94.1.6.1.2

connUnitState 1.3.6.1.3.94.1.6.1.5 1.3.6.1.2.1.8888.1.1.3.1.5 1.3.6.1.3.94.1.6.1.5

connUnitStatus 1.3.6.1.3.94.1.6.1.6 1.3.6.1.2.1.8888.1.1.3.1.6 1.3.6.1.3.94.1.6.1.6

connUnitSensorName 1.3.6.1.3.94.1.8.1.3 1.3.6.1.2.1.8888.1.1.5.1.2 1.3.6.1.3.94.1.8.1.3

connUnitSensorStatus 1.3.6.1.3.94.1.8.1.4 1.3.6.1.2.1.8888.1.1.5.1.3 1.3.6.1.3.94.1.8.1.4

connUnitSensorInfo 1.3.6.1.3.94.1.8.1.5 1.3.6.1.2.1.8888.1.1.5.1.4 1.3.6.1.3.94.1.8.1.5

connUnitSensorMessage 1.3.6.1.3.94.1.8.1.6 1.3.6.1.2.1.8888.1.1.5.1.5 1.3.6.1.3.94.1.8.1.6

connUnitSensorType 1.3.6.1.3.94.1.8.1.7 1.3.6.1.2.1.8888.1.1.5.1.6 1.3.6.1.3.94.1.8.1.7

connUnitSensorCharacteristic 1.3.6.1.3.94.1.8.1.8 1.3.6.1.2.1.8888.1.1.5.1.7 1.3.6.1.3.94.1.8.1.8

connUnitEventUnitIndex 1.3.6.1.3.94.1.11.1.2 1.3.6.1.2.1.8888.1.1.7.1.1 1.3.6.1.3.94.1.11.1.2

connUnitREventTime 1.3.6.1.3.94.1.11.1.4 1.3.6.1.2.1.8888.1.1.7.1.2 1.3.6.1.3.94.1.11.1.4

connUnitSEventTime 1.3.6.1.3.94.1.11.1.5 1.3.6.1.2.1.8888.1.1.7.1.3 1.3.6.1.3.94.1.11.1.5

connUnitEventSeverity 1.3.6.1.3.94.1.11.1.6 1.3.6.1.2.1.8888.1.1.7.1.4 1.3.6.1.3.94.1.11.1.6

connUnitEventType 1.3.6.1.3.94.1.11.1.7 1.3.6.1.2.1.8888.1.1.7.1.5 1.3.6.1.3.94.1.11.1.7

connUnitEventObject 1.3.6.1.3.94.1.11.1.8 1.3.6.1.2.1.8888.1.1.7.1.6 1.3.6.1.3.94.1.11.1.8

connUnitEventDescr 1.3.6.1.3.94.1.11.1.9 1.3.6.1.2.1.8888.1.1.7.1.7 1.3.6.1.3.94.1.11.1.9

404 IBM Tivoli Storage Area Network Manager: A Practical Introduction

To display the sensor data, we select (click) on the Fibre Channel switch, then click SAN -> SAN Properties -> Sensors/Events. We show the Sensor Event display in Figure A-1.

Figure A-1 Sensor Event data

Appendix A. Advanced Topology and Sensor Event Scanners 405

406 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Appendix B. IBM Tivoli SAN Manager backup scripts

In this appendix we provide the sample scripts we used:

� To update the Tivoli Storage Manager configuration for DB2 backups� To update the DB2 configuration� To back up the components of the IBM Tivoli SAN Manager server

Those scripts provide basic functionality and should be adapted to your environment if required.

The scripts are available for download as explained in Appendix C, “Additional material” on page 413.

B

© Copyright IBM Corp. 2002, 2003. All rights reserved. 407

Tivoli Storage Manager configurationExample B-1 shows a macro that can be used to configure the TSM environment for DB2 backups. This macro must be adapted to your environment.

Example: B-1 TSM_DB2_config.mac macro

DEFINE DOMAIN DB2_DOMAIN DESCRIPTION="Domain for DB2 backups" BACKRETENTION=30 ARCHRETENTION=365

DEFINE POLICYSET DB2_DOMAIN DB2_POLICY DESCRIPTION="DB2 BACKUPS Policyset"

DEFINE MGMTCLASS DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS DESCRIPTION="Mgmtclass for DB2 databases" SPACEMGTECHNIQUE=NONE AUTOMIGNONUSE=0 MIGREQUIRESBKUP=YES

DEFINE COPYGROUP DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS DESTINATION=BACK_LTO FREQUENCY=0 VEREXISTS=1 VERDELETED=0 RETEXTRA=0 RETONLY=0 MODE=MODIFIED SERIALIZATION=SHRSTATIC

DEFINE COPYGROUP DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS TYPE=ARCHIVE DESTINATION=ARCHIVEPOOL RETVER=NOLIMIT SERIALIZATION=SHRSTATIC

ASSIGN DEFMGMTCLASS DB2_DOMAIN DB2_POLICY DB2_MGMTCLASS

ACTIVATE POLICYSET DB2_DOMAIN DB2_POLICY

REGISTER NODE LOCHNESS_DB2 LOCHNESS_DB2 DOMAIN=DB2_DOMAIN ARCHDELETE=YES BACKDELETE=YES USERID=NONE

DB2 configurationExample B-2 shows a script you can use to update your DB2 database configuration with parameters related to the Tivoli Storage Manager environment. It will also stop and restart your DB2 environment. This script must be adapted to your environment.

Example: B-2 DB2_TSM_config.bat script

echo Database name : %1echo Node name : %2echo Password : %3db2 update db cfg for %1 using TSM_MGMTCLASS DB2_MGMTCLASSdb2 update db cfg for %1 using TSM_OWNER %2db2 update db cfg for %1 using TSM_NODENAME %2db2 update db cfg for %1 using TSM_PASSWORD %3db2stop forcedb2start

Stopping the applicationsThese scripts shut down the Tivoli SAN Manager environment in an orderly way.

408 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Stopping WebSphere Tivoli SAN Manager applicationExample B-3shows the ITSANMstop.bat script used to stop the Tivoli SAN Manager application within WebSphere.

Example: B-3 ITSANMstop.bat script

@REM Stop the Application ITSANM-Manager@REM -----------------------------------@echo "Stopping the ITSANM-Manager"net stop "IBM WebSphere Application Server V5 - ITSANM-Manager"

Stopping Tivoli SAN Manager environmentExample B-4shows the ITSANMstopall.bat script used to stop the complete Tivoli SAN Manager environment including NetView, WebSphere.

Example: B-4 ITSANMstopall.bat script

@REM Stop the Netview Application@REM ----------------------------@echo "Stopping Netview"ovstopnet stop "Tivoli Netview Service"

@REM Stop the ITSANM-Manager @REM ------------------------@echo "Stopping the IBM WebSphere Application Server V5 - ITSANM-Manager"call ITSANMstop.bat

Starting the applications

These scripts start up the Tivoli SAN Manager environment in an orderly way.

Starting WebSphere Tivoli SAN Manager applicationExample B-5shows the ITSANMstart.bat script used to start the Tivoli SAN Manager application within WebSphere.

Example: B-5 ITSANMstart.bat script

@REM Start WAS ITSANM-Manager Application@REM ------------------------------------@echo "Starting the ITSANM-Manager ..."net start "IBM WebSphere Application Server V5 - ITSANM-Manager"

Start of IBM Tivoli SAN Manager environmentExample B-6shows the ITSANMstartall.bat script used to start the complete Tivoli SAN Manager environment including NetView, WebSphere.

Example: B-6 ITSANMstartall.bat script

@REM Start the Netview Application@REM ----------------------------@echo "Starting Netview"

Appendix B. IBM Tivoli SAN Manager backup scripts 409

net start "Tivoli Netview Service"ovstart

@REM Start the ITSANM-Manager @REM -------------------------@echo "Starting the ITSANM-Manager..."call ITSANMstart.bat

DB2 ITSANMDB backupsThese scripts are for backing up the Tivoli SAN Manager DB2 database.

Offline backup scriptExample B-7shows the ITSANMBackupOffline.bat script used to run an offline backup of the ITSANMDB database. It also checks the application status to insure a correct state of the database during backup.

Example: B-7 ITSANMBackupOffline.bat script

@REM Stop the Netview Application@REM ----------------------------@echo "Stopping Netview"ovstop

@ECHO ON@REM Stop the Application ITSANM DB@REM ------------------------------call ITSANMstop.bat

@ECHO ON@REM Get Status and check if Stopped@REM -------------------------------net start | findstr /i "ITSANM-Manager@if %errorlevel% EQU 0 GOTO BACKUPDB

:NOTSTOPPED@ECHO ON@REM ITSANM not stopped - Backup cannot run@REM --------------------------------------@echo "WAS Application ITSANM Not Stopped !!!"@echo "Backup process cancelled "exit 1

:BACKUPDB@ECHO ON@REM ITSANM is stopped - Backup can run@REM ----------------------------------@echo "Backup of ITSANMDB starting ....."C:\PROGRA~1\SQLLIB\BIN\db2cmd.exe /c /w /i db2 backup database ITSANMDB USE TSM@if %errorlevel% NEQ 0 echo "Backup failed - Please check error messages"

@REM Backup completed - Start ITSANM@REM -------------------------------:STARTITSANMcall ITSANMstart.bat

410 IBM Tivoli Storage Area Network Manager: A Practical Introduction

@ECHO ON@REM Get Status and check if Started@REM -------------------------------net start | findstr /i "ITSANM-Manager"@if %errorlevel% EQU 0 GOTO STARTOK

@REM ITSANM not started @REM ------------------@echo "Application ITSANM Not Started !!!"exit 1

@REM ITSANM started @REM --------------:STARTOK@echo "Application ITSANM started successfully"

@REM Start the Netview Application@REM -----------------------------@echo "Starting Netview"ovstart

exit"

Online backup scriptExample B-8shows the ITSANMBackupOnline.bat script used to run an online backup of the ITSANMDB database. It also performs basic checking to insure that DB2 is started and that the backup is successful.

Example: B-8 ITSANMBackupOnline.bat script

@ECHO ON@REM List active connections for information@REM ---------------------------------------db2cmd.exe /c /w /i db2 list applications for database ITSANMDB | findstr /i SQL1032N@if %errorlevel% NEQ 0 GOTO BACKUPDB

@REM SQL1032N found - DB is not started@REM ----------------------------------@echo "SQL1032N return - DB2 is not active - Backup cancelled !!!"exit 1

:BACKUPDB@ECHO ON@REM DB2 is active - Backup can run@REM ------------------------------@echo "Backup of ITSANMDB starting ..."db2cmd.exe /c /w /i db2 backup database ITSANMDB ONLINE USE TSM@if %errorlevel% NEQ 0 echo "Backup failed - Please check error messages"

@REM Backup completed - List connections@REM -----------------------------------db2cmd.exe /c /w /i db2 list applications for database ITSANMDB

Appendix B. IBM Tivoli SAN Manager backup scripts 411

412 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Appendix C. Additional material

This redbook refers to additional material that can be downloaded from the Internet as described below.

Locating the Web materialThe Web material associated with this redbook is available in softcopy on the Internet from the IBM Redbooks Web server. Point your Web browser to:

ftp://www.redbooks.ibm.com/redbooks/SG246848

Alternatively, you can go to the IBM Redbooks Web site at:

ibm.com/redbooks

Select the Additional materials and open the directory that corresponds with the redbook form number, SG246848.

Using the Web materialThe additional Web material that accompanies this redbook includes the following files:

File name DescriptionSG246848scripts.zip Zipped Scripts

System requirements for downloading the Web materialThe following system configuration is recommended:

Hard disk space: 1MB Operating System: Windows 2000Processor: Pentium or higherMemory: 128 MB

C

© Copyright IBM Corp. 2002, 2003. All rights reserved. 413

How to use the Web materialCreate a subdirectory (folder) on your workstation, and unzip the contents of the Web material zip file into this folder.

414 IBM Tivoli Storage Area Network Manager: A Practical Introduction

ronyms

AIX Advanced Interactive eXecutive

ANSI American National Standards Institution

API Application Programming Interface

ARP Address Resolution Protocol

ATL Automated Tape Library

ATM Asynchronous Transfer Mode

BSD Berkeley Software Distribution

CIFS Common Internet File System

CIM Common Information Model

DFT Dispersion Frame Technique

DHCP Dynamic Host Configuration Protocol

DMTF Desktop Management Task Force

DNS Domain Name Resolution

DWDM Dense Wavelength Division Multiplexing

ED/FI Error Detection and Fault Isolation

EGP Exterior Gateway Protocol

ELS Extended Link Services

ESCON® Enterprise System Connection

ESRM Enterprise Storage Resource Manager

ETL Extract-Transform-Load

FC Fibre Channel

FC-AL Fibre Channel Arbitrated Loop

FC-FS Fibre Channel Framing and Signaling Interface

FC-MI Fibre Channel - Methodologies for Interconnects

FCP Fibre Channel Protocol

FC-SW Fibre Channel Switch Fabric

FDMI Fabric Device Management Interface

FI Fault Isolation

FQDN Fully Qualified Domain Name

FSPF Fabric Shortest Path First

FTE Full Time Equivalent

GBIC GigaBit Interface Converter

GLM Gigabit Link Module

GUI Graphical User Interface

GUID Global User ID

Abbreviations and ac

© Copyright IBM Corp. 2002, 2003. All rights reserved.

HBA Host Bus Adapter

HSM Hierarchical Storage Management

HTTP Hyper Text Translation Protocol

I/O Input/Output

IBM International Business Machines Corporation

ICMP Internet Control Message Protocol

IETF Internet Engineering Task Force

ISL Inter Switch Link

ITSO International Technical Support Organization

JAR Java Archive

JBOD Just a Bunch of Disks

JDBC Java Database Connectivity

JRE Java Runtime Environment

JVM Java Virtual Machine

LAN Local Area Network

LAN Local Area Network

LC Lucent Connector

LTO Linear Tape Open

LUN Logical Unit Number

MIB Management Information Base

MM Multi-Mode

MOF Managed Object Format

NAS Network Attached Storage

NFS Network File System

NLS National Language Support

NOS Network Operating System

OEM Original Equipment Manufacture

OID Object Identifier

PD Problem Determination

RAID Redundant Array of Independent Disks

RDBMS Relational Database Management System

RFC Request for Comment

RIM RDBMS Interface Module

RLIR Registered Link Incident Record

RLS Read Link Error Status Block

RNID Request Node Identification Data

415

RSCN Registered State Change Notification

SAN Storage Area Network

SCSI Small Computer System Interface

SFF Small Form Factor

SFP Small Form Factor Pluggable

SM Single Mode

SMI Storage Management Initiative

SMIS Storage Management Initiative Specification

SNIA Storage Networking Industry Association

SNMP Simple Network Management Protocol

SRM Storage Resource Management

SSP Storage Service Provider

STP Shielded Twisted Pair

TCP/IP Transmission Control Protocol/Internet Protocol

TEC Tivoli Enterprise Console

TEDW Tivoli Enterprise Data Warehouse

UDP User Datagram Protocol

UI User Interface

URL Universal Resource Locator

UTC Coordinated Universal Time

UV Ultra Violet

WEBM Web-Based Enterprise Management

XML eXtensible Markup Language

416 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Related publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook.

IBM RedbooksFor information on ordering these publications, see “How to get IBM Redbooks” on page 418.

� Early Experiences with Tivoli Enterprise Console 3.7, SG24-6015

� IBM Tivoli Storage Resource Manager: A Practical Introduction, SG24-6886

� Tivoli NetView V6.01 and Friends, SG24-6019

� Implementing System Management Solutions using IBM Director, SG24-6188

� IBM Tivoli Storage Management Concepts, SG24-4877

� IBM Tivoli Storage Manager: Implementation Guide, SG24-5416

� Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141

� Backing Up DB2 Using Tivoli Storage Manager, SG24-6247

� All About IBM Tivoli Configuration Manager V4.2, SG24-6612

� Introduction to Tivoli Enterprise Data Warehouse, SG24-6607

Other resourcesThese publications are also relevant as further information sources:

� IBM Tivoli Storage Area Network Manager Planning and Installation Guide, SC23-4697

� IBM Tivoli Storage Area Network Manager User’s Guide, SC23-4698

� IBM Tivoli Storage Area Network Manager Messages, SC32-0953

� Tivoli NetView for Windows User’s Guide, SC31-8888

� IBM DB2 Universal Database Administration Guide: Implementation, Version 7, SC09-2944

� IBM DB2 Universal Database Command Reference, Version 7, SC09-2951

Referenced Web sitesThese Web sites are also relevant as further information sources:

� IBM Tivoli Storage Area Network Manager

http://www.ibm.com/software/tivoli/products/storage-san-mgr/

� IBM Tivoli Storage Manager

http://www.ibm.com/software/tivoli/products/storage-mgr/

� Storage Networking Industry Association

http://www.snia.org/

© Copyright IBM Corp. 2002, 2003. All rights reserved. 417

� Brocade

http://www.brocade.com/

� Brocade MIB download

http://www.brocade.com/support/mibs_rsh/index.jsp

� QLogic

http://www.qlogic.com

� SNMP RFC information

http://silver.he.net/~rrg/snmpworld.htm

� SNMP RFC information

http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/snmp.htm

� Technical Committee T11

http://www.t11.org

� DB2 Fix Pack downloads

http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/report

� WebSphere Application Server Fix Pack downloads

http://www-1.ibm.com/support/search.wss?rs=180&tc=SSEQTP&dc=D400

� Internet Engineering Task Force

http://www.ietf.org

How to get IBM RedbooksYou can search for, view, or download Redbooks, Redpapers, Hints and Tips, draft publications and Additional materials, as well as order hardcopy Redbooks or CD-ROMs, at this Web site:

ibm.com/redbooks

Help from IBMIBM Support and downloads

ibm.com/support

IBM Global Services

ibm.com/services

418 IBM Tivoli Storage Area Network Manager: A Practical Introduction

Index

AActive Directory

monitoring 393agents 29AIX 31, 70, 72, 89

inittab 111ANSI 13, 18, 24, 60Apache

monitoring 393API 15, 17, 74, 285application availability 29arbitrated loop 64archive logs 291asset management 358authentication password 116availability 29

Bbackup and recovery 6bandwidth 64–65, 222baroc file 72, 335, 338basic fabric management. 73Bluefin 20boot partition 310Brocade 131, 210business intelligence reporting 389

Ccabling 58

cladding 59coating 60connectors 61copper 60core 59distance limitations 58multi-mode 59plenum rating 60SC connectors 61single-mode 59

Carnegie Mellon University 270CDW 388CIM 19–21

agent 23classes 22object manager 23

CIM-XML 22Cisco 29

MDS 9000 169cladding 59class definition file 335Cleared Record 271clustering 71coating 60

© Copyright IBM Corp. 2002, 2003. All rights reserved.

collect daemon 217configuration for Tivoli SAN Manager 131configuration information 284ConnUnitLinkTable 70ConnUnitPortTable 70Control server 389copper 60core 59cost cutting 5

Ddata mart 388–389data mining 389data types 4Data Warehouse Pack 388

and Tivoli SAN Manager 389DB2 30, 66, 71, 98, 111, 369

archive logs 291, 312backup configuration 287backup environment variables 289backup with TSM 286database backup 286database maintenance 314database restore 307, 312indexes 315install 98install Fix Pack 99LOGRETAIN 289monitoring 393offline backup 296–297online backup 289, 296, 299roll forward restore 312sample scripts 407service 98Tivoli SAN Manager database 106, 284uncatalog database 313user exit 291

DB2 commandsdb2rbind 316db2start 100, 290db2stop 100, 290get db cfg 288–289reorg 315reorgchk 314–315ROLLFORWARD 309runstats 314update db cfg 289

DB2 Warehouse 99DHCP 29, 71directors 208Disaster Recovery 6discovery 11, 32, 168disk system

LUNs 42

419

Dispersion Frame Technique 270Distribution Status console 366DMTF 20DNS 71, 87, 89, 98

EED/FI 14, 28, 66ELS 15, 25Emulex 58encryption 350endpoint 370, 392endpoint devices 17, 33enterprise-specific MIB 209environment variables 289error detection 11, 14–15ESRM 20Ethernet 69, 255ETL 28, 389

Central Data Warehouse 388data mart 388

ETL programs 388ETL1 388ETL2 388EUSDSetup 89event forwarding 215, 349event logging 45, 222Extract 388Extract, Transform and Load

See ETL

FFA-MIB 70, 212, 402fault detection 46fault isolation 11, 14–15, 28, 270Fault Record 270FC Management MIB 18FC Management Server 68FC_MGMT MIB 257FC-AL 14, 64FC-GS-3 24, 68FC-GS-4 24FC-MGMT MIB 402FC-MI 13, 18, 20FCPortTxFrames 230FC-SW2 57FDMI 24FE-MIB 212, 402Fibre Alliance 13, 18Fibre Alliance MIB 257Fibre Channel 32, 55Fibre Channel arbitrated loop 64Fibre Channel attachment 67Fibre Channel cabling 58Fibre Channel MIB 210Fibre Channel network 33Fibre Channel standards 56Fibre Channel topologies 63filesystems 42, 66, 74, 171firewall 350

firmware 89FSPF 57

GGBIC 62growth 4GUI 31GUID 136, 138, 276

HHBA 15, 18, 33, 58, 63, 66, 74, 81, 88, 166

API 15, 17, 68, 74, 88historical reporting 215Host Bus Adapter. See HBAhostname 97HOSTS file 97, 110, 125HTTP 22, 65, 90hub 64

IIBM 348IBM Director 259, 263

event logging 263IBM Directory 385IBM SAN Data Gateway 177IBM Tivoli Configuration Manager see Tivoli Configuration ManagerIBM Tivoli Enterprise Console see TECIBM Tivoli Enterprise Data Warehouse see TEDWIBM Tivoli Monitoring see Tivoli MonitoringIBM Tivoli NetView. See NetViewIBM Tivoli SAN Manager 70IBM Tivoli Storage Area Network Manager. See Tivoli SAN ManagerIBM Tivoli Storage Manager. See Tivoli Storage ManagerIBM WebSphere Express. See WebSphereIETF 13, 18, 254–255IIS

monitoring 393inband discovery 15, 18, 32–33inband management 16–17, 31, 68incremental 291Indication Record 270Infiniband 25interoperability 12, 14, 56inventory 358inventory profile 362Inventory Signature files 363IP network 3, 32, 246IP network management 35iSCSI 7, 25, 28, 33, 71, 253–254

adapter 255Auth MIB 257discovery 168, 256driver 255initiators 254iSNS MIB 257MIB 256

420 IBM Tivoli Storage Area Network Manager: A Practical Introduction

NetView discovery 168, 256SmartSet 169, 235SNMP 168targets 254

ISL 57, 65, 163, 173iSNS 255

MIB 257ISO 13ITSANM.MIB 261ITSANMDB 284

JJava 113, 335, 340JDBC 99JNI 58JRE 29JVM 30–31, 133

LLAN 58LC connectors 61LDAP 385leaf node 210Linux 29, 31, 89Load 388logical topology display 41logical volume 44longwave 59LUN masking 69LUNs 7, 42, 69, 74, 166

Mmanaged hosts 27, 29

Linux 29management applications 7MDS 9000 169mgrlog.txt 318MIB 15–16, 29, 48, 65, 69, 207, 209, 401

applications 228definitions 213enable 213enable in NetView 210enterprise-specific 209, 211, 214iSCSI 256object ID 210, 216, 227, 401objects 210, 215, 225, 228, 245performance objects 213standard 209subtree 214thresholds 215Tivoli SAN Manager 261tree structure 210

MIB-II 212, 222Microsoft Active Directory 385

monitoring 393MOF 23monitoring 392MQSeries 29, 102, 293

multi-mode fiber 59

NNAS 7netmon 246netstat 88NetView 29–30, 35, 66, 71, 83, 98, 100, 108, 110, 119, 150, 260, 284, 293, 349, 400

acknowledge 181Advanced Menu 211arm threshold 222child submap area 151clearing the database 247copying MIB 211data collection 216, 232data collection troubleshooting 224database 247, 284database maintenance 224discovery process 246enable MIB 210event browser 127, 129, 261event forwarding 260, 349event forwarding to TEC 348event logging 222, 323existing installation 128explorer display 36, 151, 166graph 223, 244Graph Properties 233graphs 207, 215, 225historical reporting 48, 208, 215, 226HOSTS file 110, 125icon display 36interface 150iSCSI 256iSCSI discovery 168, 256iSCSI SmartSet 169, 235launch Tivoli Storage Resource Manager 179loading MIB 212–213logging 323Management Page 176maps 150MIB applications 228, 230MIB Browser 214, 230MIB Data Collection 216, 243MIB Data Collector 213, 215, 227MIB Tool Builder 213, 227–228, 234Navigation Tree 153netmon daemon 246Object Properties 153, 175, 284password 108, 124performance applications 207performance data 215, 222polling 228, 233, 236properties panel 165real-time reporting 48, 208, 227, 234reporting 25, 47restricting discovery 246root map 150, 160, 240rule builder 349search function 276

Index 421

seed file 246, 248Server Setup 247service 108, 124SmartSets 160, 168, 235, 243, 256SmartSets and Data Collection 243SNMP trap forwarding 259status propagation 157, 241submap stack 151submap window 151submaps 150, 160supported MIBs 209System Configuration view 152Tivoli Storage Area Network Manager view 152toolbar menu 177topology map 222, 225, 246trap 222trap daemon 324trap forwarding 128, 130trap port 323trapd.conf 351trapfrwd daemon 128traps 126unacknowledge 181unmanage object 180upgrade 133

NetView commandsnvsniffer 168, 235, 256ovaddobj 128ovstart 128ovstart snmpcollect 225ovstatus snmpcollect 224–225

Network Attached Storage. See NASnetwork bandwidth 222network management 6, 208network monitoring 207, 228, 392network problem resolution 207network resource allocation 207NIC 255non-Tivoli applications 388Notification Record 271nslookup 89

Oobject ID 210OEM 58OLAP

analysis 389Oracle

monitoring 393outband agents 29outband discovery 15, 18, 32–33outband management 16, 69

PPentium 70performance metrics 215PFA 268platform administration 6plenum rating 60

point-to-point 63Policy Regions 359polling 16–17polling interval 48, 132port 104, 112, 122, 127port statistics 216Predictive Failure Analysis 28, 268problem determination 28profile

overview 392profile manager 360, 393Prolog 334protocols 65

QQLogic 58, 88–89

RRedbooks Web site 418

Contact us xxvremote console 107removable media devices 72report interface 389reporting 12, 25repository 89resource model 392resource models 392RFC 210RIM 334RLIR 15RLS 15RNID 15, 17, 33, 35, 68, 74, 81, 84, 89, 166root cause analysis 268RSCN 15Rule Base 334–335

SSAN

adoption 5arbitrated loop 14, 64attributes 66bandwidth 64–65basic fabric management 73cabling 58Cleared Record 271components 57connections 38discovery 11, 13, 15, 246endpoint devices 68event logging 45events 16, 30, 66fault detection 46fault isolation 270Fault Record 270heterogeneous support 57historical reporting 208, 226inband management 31, 68interconnects 163

422 IBM Tivoli Storage Area Network Manager: A Practical Introduction

interoperability 56, 65management 10, 56, 68, 235management API 15management costs 5Management Services 19management standards 12, 18monitoring 11, 207, 228Name Server 17nameserver 15navigation 160Notification Record 271performance data 215physical topology 37physical view 67point-to-point 63polling 16–17, 68problem determination 28problem resolution 29protocols 57real-time reporting 208, 227, 234reporting 12, 25, 29root cause analysis 268standardization 5standards 10, 12, 27, 57switch port statistics 216switched fabric 65switches 27topology 8, 12, 16, 37, 55, 63, 150, 161, 163, 241trunking 65zones 35, 40zoning 15, 19, 65

SAN Error Predictor 28SAN management 4

vendor applications 27, 49SC connectors 61scanner 56SCSI 58

protocol 33, 254SCSI Inquiry 68SCSI queries 17seed file 246, 248server growth 5SFF 61SFP 61–62shortwave 58silent install 139silent uninstall 145single-mode fibre 59SmartSet 235SmartSets 160, 168–169, 235, 256SNIA 13, 20, 24–25SNMP 15–16, 18, 29–33, 65, 69, 95, 100, 168, 208, 236, 260

agents 208collect daemon 217, 223–224community name 78, 127, 263console 130events 30manager 66, 208, 260MIB 401

port 129trap 48, 78, 268trap destination 89, 262trap forwarding 126–127, 259traps to IBM Director 264

socket 335software distribution 358software inventory 358Solaris 31, 89SRMURL 179SSL encryption 350staffing growth 5standard MIB 209Stochastic 270Storage Area Network. See SANstorage consolidation 7storage growth 4storage management 3

manual 6standards 10

swFCPortTxFrames 216, 229, 243–244swFCRxErrors 224swFCRxFrames 224swFCTxErrors 224swFCTxFrames 226switch commands

agtcfgset 79agtcfgshow 78snmpmibcapset 89, 213

switch management 14switched fabric 64–65switches 8, 27, 33, 76, 131

administrative rights 131API 40, 85, 131, 404display 163environmentals 173events 404firmware 89login ID 131, 213management applications 49, 174, 208MIB 16, 65, 69nameserver 46, 65, 68–69performance data 215, 222port connections 173port statistics 216query 66sensors 173trap destination 78, 89trap forwarding 126zone information 131, 165

SW-MIB 212, 229systems management issues 6

TT11 57tape 68TCP/IP 254TEC 30, 66, 157, 268, 334

Assign Event Group 343baroc file 335

Index 423

class definition file 335compile rule base 338Console 335Constraint 341event 397Event Console 340Event Filters 340event format 347Event Group 340event processing 334events from Tivoli SAN Manager 348Import Class Definitions 336, 338load rule base 339RIM 334Rule Base 334–336rule processing 354stop or start event server 339Test SQL 342

TEC commandswtdumprl 336

tec_dispatch 334tec_reception 334tec_rule 334tec_server 334tec_task 334tec_ui_server 335TEDW 30, 37, 336, 388–389

control server 389data mart 388Data Warehouse Pack 388–389

Data Warehouse Packand Tivoli SAN Manager 389

ETL 388–389ETL processes 389ETL programs 388source applications 388

telnet 65, 213Tivoli 126

Policy Regions 359Tivoli Configuration Manager 357–358

Activity Planner 358Change Manager 358Enterprise Directory Query Facility 358Inventory 358Inventory Profile 362Inventory Scan 367Profile Manager 360Query 367removing software 385Resource Manager 358Software Distribution 358software distribution 370software distribution profile 379software package 370Web Interface 358

Tivoli Desktop 359, 393Distribution Status console 366profile manager 393

Tivoli endpoint 370Tivoli Enterprise Console see TEC

Tivoli Enterprise Framework 334–335Tivoli Light Client Framework 336Tivoli Managed Node 350Tivoli Managed Region 399Tivoli Monitor

wdmlseng 399Tivoli Monitoring 391–392

engine 392Parametric Services 393–394profile 392resource models 392Web Health Console 392

Tivoli NetView see NetViewTivoli SAN Manager 25, 55, 70, 270–271

Agent access password 116agent address 71agent backup 291agent configuration files 291agent logging 322agent placement 34, 76agent restore 302agent startup 117agents 15, 17, 29, 31, 66–67, 72, 96, 106, 127, 166, 284, 322agents installation 111–112agents uninstall 136AIX 28, 70AIX manager install 111and tape devices 72application discovery 174application launch 49, 66, 174attribute scanner 68, 84authentication 123authentication password 107, 284backup strategies 283baroc file 72, 335, 338change device icon 173change device icon type 154change device label 154, 162, 173, 181class definition file 335Clear History 181cluster support 71component placement 67components 29, 66, 96, 284configuration 126configuration information 284Configure Agents 73, 77, 80, 82, 130, 132, 157, 304configure management application 175Configure Manager 132, 157, 181Connection 173console 27, 29, 50, 66console access password 123console service 125Data Warehouse Pack 389database 30, 33, 80, 98, 106, 268, 284database backup 296database backup environment variables 289database maintenance 314database restore 307database userid 106

424 IBM Tivoli Storage Area Network Manager: A Practical Introduction

deployment considerations 70Device Centric View 41–42, 81, 85, 161, 166device icons 155, 171device label 81, 171device properties 171device support 31, 57disaster recovery 309discovery 32, 76, 80–81, 284, 307display switch connections 173ED/FI 28, 66ED/FI Configuration 157ED/FI Properties 157event forwarding 215, 348–349event forwarding to TEC 348event logging 45events 30, 66events to IBM Director 263fabric ports 173fault detection 46filesystem display 42, 171flat file backup 286functions 31GUI 31, 66GUID 136, 138, 320high availability 89historical reporting 48, 208, 215, 226Host Centric View 41, 43, 81, 85, 161, 167host display 171icons 155, 180Import Class Definitions 338inband and outband 84inband management 68, 81, 83indication record 270initial poll 132installation 95installation directory 103, 114, 121installation id 98–99, 102, 105, 112, 119installation log files 111, 117, 125installation verification 110Inventory Signature files 363iSCSI 33, 255iSCSI discovery 168, 256iSCSi discovery 168ITSANM_120.baroc 338Launch Application 157, 174launch Tivoli Storage Resource Manager 157, 179license 113, 121, 284license agreement 103Linux 29log files 318logging 73–74, 284logging service commands 320logical topology 41logical views 34, 74, 77, 81, 85, 166–167logical volume display 44LUN display 42, 69, 74, 166managed hosts 27, 29, 66, 72, 167manager 28–29message types 318mgrlog.txt 318

MIB 261monitoring 393MQSeries 29navigation display 44Navigation Tree 44, 153NetView 30, 284NetView console 28NetView traps 126Object Properties 45object status 155, 180outband agents 29, 130outband management 69, 76, 80, 401overview 28physical topology 37, 160physical view 67, 161polling 68, 80, 127, 132polling interval 284port selection 104, 114–115, 122, 284Predictive Failure Analysis 28, 268pre-installation checks 97, 112, 119problem determination 28propagation 157real-time reporting 48, 208, 227, 234remote console 29, 31, 66–67, 80, 84, 88, 96, 178, 323remote console installation 119remote console logging 323remote console uninstall 137reporting 47repository 66, 68, 98restore strategies 283, 302RNID 74, 166rule file 354sample scripts 407sample TEC rule 354SAN Error Predictor 28SAN menu 35, 157, 170SAN Properties 157, 162, 170, 180, 405SAN view 162scanners 56, 68, 81Sensor Events Scanner 401, 404Sensors/Events 170, 172–173, 405Server 30, 66–67, 89, 96, 284Server backup 286Server installation 96, 102Server logs 319Server port 114, 122Server requirements 70Server restore 305Server start 294Server stop 293Server uninstall 135–136service commands 320services 393Set Event Destination 157, 262silent install 139silent uninstall 145SNMP agent 31SNMP community name 263SNMP trap forwarding 262

Index 425

start agent service 117start AIX service 111status colors 155status cycle 180status propagation 157, 241submap 157summary display 44supported platforms 31, 81, 96switch display 172switch environmentals 173symbols 74, 77, 81TEC event format 347Tivoli Storage Resource Manager 157topology management 149topology map 33, 35, 37, 46, 66, 68, 70, 77, 80, 83–84, 127, 161, 180–181, 222, 241topology scanner 68–69, 77, 84, 401–402topology view 163, 284tracing 317, 326trap forwarding 126–128, 130, 262uninstall 135uninstall AIX server 136uninstall Windows server 135unknown device 173unknown symbols 77upgrade 133upgrade agents 135upgrade remote console 134WebSphere 28, 102, 284well-placed agent 35, 73–74Windows 2000 70zone display 40, 85, 131, 162, 165

Tivoli SAN Manager commandssetenv 320srmcp 320srmcp log list 326srmcp SANDBParms 263tcstart 117–118tcstop 117–118, 136

Tivoli Service Level Advisor 28Tivoli Storage Manager 285

API 285API password 290Backup/Archive Client 286, 288, 291, 310client configuration 288client options file 289–290, 310clients 285copy group 286disaster preparation and recovery 312dsm.opt 290expiration 287inactivate backups 287include exclude list 290incremental backup 291management class 286, 288nodenames 288policy domain 286RETONLY 287server 285server configuration 286

VERDELETED 287Tivoli Storage Manager commands

db2adutl 287, 291, 301dsmapipw 290QUERY NODE 288

Tivoli Storage Manager for Databases 285Tivoli Storage Resource Manager

launch 157launch from NetView 179

topology display 36, 84Transform 388trap forwarding 126–128, 130trapd.conf 351trapfrwd 128trapfrwd.conf 128traps 222trend analysis 207TRP-MIB 212TSM. See Tivoli Storage Manager

Uultraviolet light 60UTC 389

Vvirtualization 11

Wwarehouse 388warehouse pack 388WBEM 20–21wdmlseng 399Web Health Console 392WebSphere 28, 30, 71, 90

administration ID 106monitoring 393service 110

WebSphere configuration information 284well-placed agent 35, 73–74Windows 2000 31, 70, 89

administrative rights 98, 112, 119boot partition 310registry 293SNMP service 100System Objects 310Wordpad 318

Windows Explorer 36Windows NT 89WWN 19, 34, 74, 77, 166, 276

XXML 50, 68XWindows 111

Zzones 35, 40, 68, 85, 165zoning 19, 65, 131

426 IBM Tivoli Storage Area Network Manager: A Practical Introduction

(1.0” spine)0.875”<->1.498”

460 <-> 788 pages

IBM Tivoli Storage Area Netw

ork Manager:

A Practical Introduction

®

SG24-6848-01 ISBN 0738499978

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

IBM Tivoli Storage Area Network Manager:A Practical Introduction

Discover, display and monitor your SAN topology, including zones

Historical and real-time monitoring

ED/FI for SAN Error prediction

Now that you have installed your SAN, how are you going to manage it? This IBM Redbook describes the new product, IBM Tivoli Storage Area Network Manager, an active, intelligent, business-centric management solution for storage resources across the enterprise.

IBM Tivoli Storage Area Network Manager provides effective discovery and presentation of SAN physical and logical topologies and provides multiple views of the SAN, including zones. Through its interface, it can be configured to show historical and real-time monitoring of SAN fabric devices.

With IBM Tivoli Storage Area Network Manager, you will know what's on your SAN, how the devices are connected, and how storage is assigned to the hosts. If something goes wrong, or new devices are added, the topology display automatically updates to show the changed topology. SAN generated events can be displayed on the manager system, or forwarded to another SNMP manager or Tivoli Enterprise Console.

This book is written for those who want to learn more about IBM Tivoli SAN Manager, as well as those who are about to implement it.

This second edition of the book is current to IBM Tivoli SAN Manager V1.2.

Back cover