Configuring Tivoli SAN Manager with IBM

IBM TotalStorage

Configuring IBM Tivoli SAN Manager withIBM Eserver SAN Products

SC30-4066-00

��

IBM TotalStorage

Configuring IBM Tivoli SAN Manager withIBM Eserver SAN Products

SC30-4066-00

��

First Edition (August 2003)

© Copyright International Business Machines Corporation 2003. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 1Purpose of this document . . . . . . . . . . . . . . . . . . . . . 1Is Tivoli SAN Manager something that I should install?. . . . . . . . . . . 1

Tivoli SAN Manager and IBM Service . . . . . . . . . . . . . . . . 1SAN Manager functions . . . . . . . . . . . . . . . . . . . . . 1

Bonus Pack issues . . . . . . . . . . . . . . . . . . . . . . . . 1Tivoli SAN Manager and other SAN managers. . . . . . . . . . . . . . 2What hardware does this book support? . . . . . . . . . . . . . . . . 2What education should I have before using this document? . . . . . . . . . 2Related publications . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. Overview . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 3. Placing Tivoli SAN Manager components . . . . . . . . . . 7Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Managed hosts . . . . . . . . . . . . . . . . . . . . . . . . . 7Remote console . . . . . . . . . . . . . . . . . . . . . . . . . 8Tivoli SAN Manager decision checklist. . . . . . . . . . . . . . . . . 8Remote access . . . . . . . . . . . . . . . . . . . . . . . . . 11

Collaboration using the Tivoli SAN Manager Remote Console. . . . . . . 11Remote viewing using VNC . . . . . . . . . . . . . . . . . . . 11Windows Terminal Services . . . . . . . . . . . . . . . . . . . 11

Chapter 4. Perform upgrades to your SAN components . . . . . . . . 13Tivoli SAN Manager support Web site . . . . . . . . . . . . . . . . 13Configuring SAN equipment . . . . . . . . . . . . . . . . . . . . 13

Updating your drivers . . . . . . . . . . . . . . . . . . . . . 13Other issues with managed hosts . . . . . . . . . . . . . . . . . 14HBAs on the SAN Volume Controller and Integration Server Master Console 15HBAs on the SAN Volume Controller . . . . . . . . . . . . . . . . 15

Chapter 5. Setting up switches . . . . . . . . . . . . . . . . . . 17Tips by product type . . . . . . . . . . . . . . . . . . . . . . . 17

Brocade . . . . . . . . . . . . . . . . . . . . . . . . . . 17Cisco . . . . . . . . . . . . . . . . . . . . . . . . . . . 17McDATA . . . . . . . . . . . . . . . . . . . . . . . . . . 17INRANGE. . . . . . . . . . . . . . . . . . . . . . . . . . 18

Switches included with the IBM Integration Server . . . . . . . . . . . . 18

Chapter 6. Configuring Tivoli SAN Manager . . . . . . . . . . . . . 19Configuring Tivoli SAN Manager notification . . . . . . . . . . . . . . 19

Forwarding SNMP alerts . . . . . . . . . . . . . . . . . . . . 19Filtering SNMP alerts . . . . . . . . . . . . . . . . . . . . . 20Receiving and filtering SNMP alerts with NetView . . . . . . . . . . . 21Receiving and filtering SNMP alerts with IBM Director . . . . . . . . . 23

Full discovery . . . . . . . . . . . . . . . . . . . . . . . . . 24Application launch. . . . . . . . . . . . . . . . . . . . . . . . 25

Appendix A. Management tips and procedures . . . . . . . . . . . . 27Service tool . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 27AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Removing devices on managed AIX Hosts . . . . . . . . . . . . . . . 27

© Copyright IBM Corp. 2003 iii

Disabling EDFI for SAN maintenance and repair actions. . . . . . . . . . 28

Appendix B. Notices . . . . . . . . . . . . . . . . . . . . . . 29Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iv Configuring Tivoli SAN Manager with IBM Eserver SAN Products

Chapter 1. Introduction

Storage networks provide connectivity allowing for the sharing, virtualization ofstorage, and other advanced features not commonly done with direct attachedstorage. These networks are complex and need management tools to be managedefficiently. Practices for setting up these management tools have been establishedand make best use of their capabilities.

Purpose of this documentPlease read this document if you are configuring with IBM® Storage Area Network(SAN) products to be managed by the IBM Tivoli® Storage Area Network Manager(Tivoli SAN Manager). This books contains specific recommendations on how tomake IBM and IBM-partner SAN hardware and infrastructure software work bestwith Tivoli SAN Manager.

Is Tivoli SAN Manager something that I should install?The SAN Manager is a helpful tool if you have a Storage Area Network thatincludes switches. It has extensive support for Fibre Channel SANs and limitedsupport for iSCSI SANs. This guide covers Fibre Channel SAN configurations. SeeTivoli documentation for iSCSI configuration and installation.

Tivoli SAN Manager and IBM ServiceThe IBM service and support organization uses Tivoli SAN Manager on someproducts to help with SAN problem determination. When a SAN problem occurs,service can use the Tivoli SAN Manager to understand the SAN configuration andto look at the link error history associated with the problem.

v The Tivoli SAN Manager also has a predictive failure analysis function thatrequires constant running to identify suspect links. It is recommended that theTivoli SAN Manager be installed and used for routine SAN monitoring.

SAN Manager functionsv View your SAN topologyv Monitor for SAN errors and eventsv From a central place, look at host and device perspectives of the SANv From a central place, launch applications for products on your SAN that are

Web-based

Bonus Pack issuesIf you do not have the Bonus Pack version of the the Tivoli SAN Manager, skip thissection. The Tivoli SAN Manager Bonus Pack has a 64-switch port limit for theSANs that it will manage. If the SANs that you will manage are fewer than 64 ports,then Bonus Pack will work just fine for you. To manage your SAN with more than64 ports, you can purchase the Tivoli SAN Manager. If you do not plan to purchasethe Tivoli SAN Manager, and you have more than 64 ports on your SAN, then youshould not plan to use the Bonus Pack. Contact your IBM marketing representativefor more information.

© Copyright IBM Corp. 2003 1

Tivoli SAN Manager and other SAN managersConfigurations with Tivoli SAN Manager and other SAN managers running againstthe same SAN or on the same server are not supported. Tivoli SAN Manageragents should not be run on the same server as other SAN managers or other SANmanager agents.

What hardware does this book support?This document is intended to be used with Tivoli SAN Manager Version 1.2 and isintended as a configuration guide for the following list of hardware. The SANManager does support other products. For the complete set of products that aresupported, see the product support matrix at:

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

v iSeries™ servers Models 8xx and above– 2765 FC Tape Adapter– 2766 FC Disk Adapter

v pSeries™ servers (43P-150 minimum)

Note: These minimums apply only if an agent is installed on the platform.– 6227 Fibre Channel Adapter– 6228 Fibre Channel Adapter

v xSeries™ servers (Pentium® 3 400 MHz minimum, Microsoft® Windows® or Linuxoperating system)

Note: These minimums apply only if an agent is installed on the platform.– Qlogic 2200 Fibre Channel Adapter– Qlogic 23xx Fibre Channel Adapter– IBM Netfinity® FAStT Host Adapter (00N6881)

v IBM TotalStorage™ Enterprise Storage Server® (ESS) 2105 Models 800, E10,E20, F10 and F20

v IBM TotalStorage FAStT 200, 500, 600, 700, 900 Storage Serverv IBM TotalStorage Scalable Tape Library 3584 (Native Fibre Channel Support)v IBM TotalStorage 3590 Tape Drives Models Exx (Native Fibre Channel Support)v IBM TotalStorage SAN Volume Controller 2145v IBM TotalStorage Integration Server 2146v IBM TotalStorage SAN Switch 2109 Models S08, S16, F16, F32, M12v IBM TotalStorage SAN Switch 3534 Model F08v INRANGE FC/9000-64, FC/9000-128, FC/9000-256 SAN directorsv McDATA ED-5000, Intrepid 6064, Intrepid 6140, Sphereon 3016, Sphereon 3032,

Sphereon 4500, Sphereon 3232 SAN switches and directors, and Sphereon 3216v Cisco MDS 9509 Director, MDS 9216 Fabric Switch

For the latest online information, see the Tivoli SAN Manager support site at:

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

What education should I have before using this document?This document assumes a basic knowledge of servers, storage, and storagenetworks. For beginners to storage area networks, a good Redbook® to read wouldbe the IBM SAN Survival Guide, SG24-6143.

2 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

For those new to Tivoli SAN Manager, another good book to read would be IBMTivoli Storage Area Network Manager: A Practical Introduction, SG24-6848. TheseRedbooks can be found at:

www.redbooks.ibm.com

Related publicationsThe IBM Tivoli Storage Area Network Manager Planning and Installation Guide,SC23-4697, and the IBM Tivoli Storage Area Network Manager User’s Guide,SC23-4698, are referred to in this document. They can be found on the Web bygoing to:

publib.boulder.ibm.com/tividd/td/tdprodlist.html

and clicking on the IBM Tivoli Storage Area Network Manager link.

Chapter 1. Introduction 3


Chapter 2. Overview

Review and then follow the following steps when installing and configuring TivoliSAN Manager.

1. Verify that the SAN is fully operational. Your SAN should be stable before youinstall Tivoli SAN Manager.

2. Review the “Planning for installation” of the IBM Tivoli Storage Area NetworkManager Planning and Installation Guide.

3. Decide how you want to deploy Tivoli SAN Manager. See Chapter 3, “PlacingTivoli SAN Manager components”, on page 7.

4. Perform any necessary upgrades and installations to your SAN components.See Chapter 4, “Perform upgrades to your SAN components”, on page 13.

a. Review the compatibility matrix and compare it with what you have in yourSAN. See “Tivoli SAN Manager support Web site” on page 13.

b. Based on the compatibility matrix review, update your storage and switchversions to obtain the desired level of function.

c. On host platforms that will have an agent, update your HBA drivers. This isvery important on those host platforms where you are planning on runningan agent on your SAN. See “Updating your drivers” on page 13.

5. Set up your switches to work with the SAN Manager. See Chapter 5, “Setting upswitches”, on page 17.

6. Install SAN Manager and the latest appropriate PTFs. You can obtain the latestPTfs at the following Web site:


If you have a SAN Volume Controller or SAN Integration Server with a MasterConsole with SAN Manager Bonus Pack pre-installed, follow the appropriatesteps in the IBM TotalStorage SAN Integration Server 2146 Administrator’sGuide, SC26-7556.

It is recommended that, as part of your installation procedure, you enable EDFIas explained in the IBM Tivoli Storage Area Network Manager Planning andInstallation Guide.

7. Configure SAN Manager for correct event notification. See Chapter 6,“Configuring Tivoli SAN Manager”, on page 19.



Chapter 3. Placing Tivoli SAN Manager components

Tivoli SAN Manager helps you manage your resources by providing networkresource discovery and management capabilities.

Tivoli SAN Manager manages all of your SAN resources, including devicesconnected to host systems through fiber-based hubs, bridges, switches, routers,gateways, and directors.

With Tivoli SAN Manager, one system acts as the manager, and, if you haveagents, one or more other systems are the managed hosts on which its agentsreside.

ManagerThe manager performs the following functions:

v Gathers data from agents on managed hosts and switches, such as descriptionsof SANs, logical unit numbers (LUNs), and file system and host information

v Provides graphical displays of SAN topology

v Generates events when a change is detected in the SAN fabric

v Forwards events to the Tivoli Enterprise Console® or an SNMP console

Managed hostsAn agent resides on each managed host. The agents on managed hosts performthe following functions:

v Gather information about the SAN by querying switches and devices for attributeand topology information

v Gather host-level information, such as file systems and mapping to LUNs

v Gather event information and other information detected by HBAs

Figure 1. Tivoli SAN Manager in a SAN environment


Remote consoleThe remote console allows you to access Tivoli SAN Manager from remotelocations across a network or modem. If you have multiple operators that need toview the topology of your environment, having several remote consoles set upprovides easy access for monitoring your environment.

You must have a Windows user ID with administrative authority to install the TivoliSAN Manager console. You must install the console on a Windows 2000 orWindows XP platform. If you have Tivoli NetView® 7.1.3 installed, Tivoli SANManager configures Tivoli NetView, but it does not install it. If you do not have TivoliNetView 7.1.3 installed, Tivoli SAN Manager installs Tivoli NetView. See the IBMTivoli Storage Area Network Manager Planning and Installation Guide for moreinformation on installing and configuring a remote console.

Tivoli SAN Manager decision checklistThe following decision checklist contains specific recommendations for configuringIBM Systems Group-supported configurations as used for SAN problemdetermination by IBM Systems Group Service. Tivoli recommendations aregenerally broader in scope. If for some reason you find these recommendationsrestrictive, check the Tivoli Web site and feel free to use the Tivoli SAN Manager asspecified there; in that case, IBM service is less likely to use the Tivoli SANManager for IBM problem determination.

The following checklist will help you decide how to configure your Tivoli SANManager.

1. SAN size:

If you use Fibre Channel but do not have a switch in your system, using theTivoli SAN Manager is not recommended. If you only have a single 8- or16-port switch, a Tivoli SAN Manager might not be needed; you might considerusing the switch tools instead. For larger SANs, use of this Tivoli SAN Manageris recommended. Remember that the Bonus Pack version has a 64-port licenserestriction. An upgrade is available. Contact an IBM marketing representative forinformation on an upgrade.

2. Switches and Tivoli SAN Manager – Can Tivoli SAN Manager manage myswitches?

Compare your current switch firmware versions with the minimum levels listed inTable 1 on page 9. If your switch meets the minimum level and is recommendedfor use with Tivoli SAN Manager, then installing Tivoli SAN Manager with yourSAN is supported by this configuration guide. If the switch is not on the list ordoes not meet the minimum firmware level, then configuring Tivoli SANManager with that switch is not supported by this configuration guide. Yourswitch might still be supported with Tivoli SAN Manager. To install and configurethe SAN manager with the switch, use Tivoli SAN Manager documentation.Check the Tivoli Web site:



Table 1. Supported switches

Switch Minimum level of switch

IBM 2109 S08, S16 2.6.0e

IBM 2109 F16, F32 3.0.2c

IBM 2109 M12 4.0.0c

IBM 3534 F08 3.0.2c

Cisco MDS 9215 1.0.1

Cisco MDS 9509 1.0.1

INRANGE FC/9000-64 3.0.2.9

INRANGE FC/9000-128 3.0.2.9

INRANGE FC/9000-256 3.0.2.9

McDATA ED-5000 4.0

McDATA ES-1000 2.0

McDATA Intrepid 6064 4.0

McDATA Intrepid 6140 Any IBM-supported level

McDATA Sphereon 3032 4.0

McDATA Sphereon 3064 4.0

McDATA Sphereon 4500 Any IBM-supported level



3. Tivoli SAN Manager hardware platform:

There is a minimum processor speed and memory size requirement for TivoliSAN Manager. For Windows platforms, the recommended processor speed is1-GHz minimum speed. For AIX platforms, a machine of equivalent processingspeed should be used. If you do not have access to such a system, do notinstall the Tivoli SAN Manager. If you have a platform that is at the minimumconfiguration, do not install agents.

Notes:

a. If you have a Master Console with a pre-installed SAN Manager, yourhardware platform is adequate.

b. The 1-GHz minimum speed assumes that the SAN manager has adedicated system. If you have additional applications running on the system,you must take them into account.

4. Decisions about managed hosts:

In general, for SAN problem determination we recommend installing no agents.There are some exceptions:

v SAN Volume Controller Master Console – an agent is pre-installed on theMaster Console.

v LUN Access – Adding an agent to the host will give you a LUN-level view ofstorage that host has access to. If LUN views are important, you might wantto consider adding an agent on that host.

v EDFI Function – If you have critical links to your hosts and storage and youneed full predictive failure analysis, you should install an agent that can coverthose links. The agent will cover all storage that it has access to and its ownlink to the switch from the managed host. (Note that most of EDFI function is

Chapter 3. Placing Tivoli SAN Manager components 9

provided by out-of-band data collection and additional information is providedby in-band agents only for the edge connections.)

v Another reason to install an agent is that the McDATA ED5000 and the Cisco9215 and 9509 switches require an in-band agent since they do not supportthe out-of-band management protocols required by the SAN Manager.Because of this limitation, problem determination using the SAN Manager islimited.

Before adding an agent to a host, check to see that it is supported.

Windows NT or Windows 2000: The following text applies to all of theseHBAs:

IBM 00N6881/FC2102IBM FC2/66-19K1246/FC2103IBM FC2/133-24P0960/FC2104QLogic QLA23xxQLogic QLA2200

v It is recommended that you install version Windows 8.2 or higher on yourQlogic 23xx adapters. Version 8.2 is not available for QLA2200 adapters.

v Do not use a driver version older than the 8.0.8 Windows driver for WindowsNT or Windows 2000.

v Using an 8.0.8 driver will work but does not support sending RNID to otherdevices. The agent will not be able to identify devices out on the SAN, andthe icons will remain unknown.

v The 8.1.5.12 Windows driver offers RNID support.

v The 8.2 Windows driver offers full support for EDFI.

Note: Before updating your current firmware levels, verify that the newerversion is also supported by your SAN components.

AIX: The following text applies to both of these HBAs:

IBM 6227IBM 6228

Note: Be aware that putting the Tivoli SAN Manager agent on your server willresult in logs to your error log in non-error cases. It is not recommendedthat you put the agent on systems where you have a pager or livereporting mechanism tied to logging events. The most commonoccurrence of this phenomenon is an entry for SAN devices that reject aRNID Extended Link Service request issued by the Tivoli SAN Manageragent. This error is logged by the device driver.

Minimum required operating system versions that support agent configurations:AIX 5.1G and 5.2B. Check the Web site if your level is not supported. It mighthave been added since this document was published. Any driver level for theIBM 6227 and IBM 6228 adapters released with those levels will work.

Linux: Tivoli SAN Manager does support Linux in some cases, but Linux is notsupported in this guide. See the Tivoli support Web site.

5. Managed host configuration decisions:


If you are planning to run an agent on a managed host, be sure to look through“Other issues with managed hosts” on page 14 to check for issues specific toyour HBA. Also, be aware that each agent addition does add additionalprocessor requirements to the Tivoli SAN Manager. Do not add agents to asystem that just meets the minimum configuration requirements.

Remote access

Collaboration using the Tivoli SAN Manager Remote ConsoleThe Tivoli SAN Manager Remote Console allows multiple parties to look at thesame SAN management data at the same time. This can be helpful when doingproblem determination and discussing a SAN over the phone.

Be aware that the remote console requires 512 MB of memory.

Remote viewing using VNCVirtual Network Computing (VNC) is an application that allows remote control of acomputer using a different machine and platform over the network. This software,available without cost, is another way to access Tivoli SAN Manager remotely. VNCdoes not come packaged with Tivoli SAN Manager. The VNC server adds aconsiderable load on the SAN Manager machine. It should be used sparingly anddisabled when not needed to diagnose problems.

Windows Terminal ServicesWindows Terminal Services does not work with Tivoli Remote Console or Tivoli SANManager. Do not use these together on the same system. Windows TerminalServices can be used for other processes on the manager or remote consolemachine, but it will not work correctly with SAN Manager itself.

Chapter 3. Placing Tivoli SAN Manager components 11


Chapter 4. Perform upgrades to your SAN components

Tivoli SAN Manager support Web siteTo look for product specific support information, it is important to visit the Tivolidevice compatibility Web site at:


This site is also a good place to go if you want to understand the level of supportthat you will get for a given SAN component. Here are some things to check for:

v The level of Fibre Channel product support for SAN management is alwaysimproving. Compare the supported firmware versions or patches listed on theWeb site with the versions installed on your SAN devices. A more recent versionof firmware or code might be available with improved capability over what youare currently running.

v Look for the latest EDFI rule set and add it if appropriate. Refer to the IBM TivoliStorage Area Network Manager Planning and Installation Guide for information.

v It is particularly important to get your switch levels up to the minimum supportlevels as shown in Table 1 on page 9.

Configuring SAN equipmentThe purpose of this section is to help you set up your SAN equipment to work bestwith Tivoli SAN Manager.

Updating your driversThe purpose of this section is to tell you how to best set up host bus adapters(HBAs) for SAN management on host systems where you plan to install a TivoliSAN Manager agent. “Other issues with managed hosts” on page 14 provides a setof tips for installing the proper HBA drivers on some platforms.

AttentionIt is essential that you perform the following steps even if you have alreadyinstalled the HBA drivers.

1. Link to:


Also, link to:


From there, check hints and tips and and support flashes for information aboutyour host bus adapters.

2. From the Web site:

a. The Web site will indicate what level of driver you should be running foroptimal SAN manager support. You can compare that level with your currentdriver level and upgrade the driver, if appropriate.

b. Go to the appropriate Web site for the HBA and get the recommendeddrivers.


c. Obtain and install the correct level of your driver.

d. Sometimes you need an additional software package to help with thein-band management interface (called the HBA API). If necessary, obtainand install this software package. This is explained on the Tivoli supportWeb page for your particular adapter.

e. Sometimes you need operating systems patches or fix levels. If necessary,obtain and install these patches and fix levels.

Other issues with managed hostsThe supported level of host bus adapter varies by product. Tivoli has arecommended level as well. Be sure to check the support lists for the products youare connected to before making any driver updates.

IBM Fibre Channel Host Adapter (00N6881/FC2102) on WindowsThe Fibre Channel Host Adapter has some limitations in event notification. Thisaffects how you set up your switches. If all the agents in your SAN are connectedby means of this type of adapter, it is especially important to set up your SimpleNetwork Management Protocol (SNMP) alerts from the switches in your SAN,because you will not receive event notification from the agent.

IBM 6227 and 6228 HBAs for pSeries serversThe following links are useful when configuring IBM host bus adapters (HBAs) andinstalling associated device drivers for pSeries servers.

pSeries support Web page:

techsupport.services.ibm.com/server/mdownload/download.html

pSeries download page:

techsupport.services.ibm.com/server/mdownload/download.html - device

QLogic QLA2200 WindowsThe Qlogic QLA2200 has some limitations in event notification. This affects how youset up your switches. If all the agents in your SAN are connected by means of thistype of adapter, it is especially important to set up your SNMP alerts from theswitches in your SAN, because you will not receive event notification from theagent. See “Configuring Tivoli SAN Manager notification” on page 19 for moreinformation.

QLogic QLA23xx WindowsNo issues.

IBM FC2/66-19K1246/FC2103No issues.

IBM FC2/133-24P0960/FC2104No issues.


HBAs on the SAN Volume Controller and Integration Server MasterConsole

The Master Console has Fibre Channel access to the entire SAN associated withthe SAN Volume Controller. This HBA and the associated drivers are pre-configuredto support the Tivoli SAN Manager agent for Microsoft Windows. No updates shouldbe necessary.

HBAs on the SAN Volume ControllerSAN Manager agents are not supported on the SAN Volume Controller.

Chapter 4. Perform upgrades to your SAN components 15


Chapter 5. Setting up switches

The purpose of this section is to give you guidance on setting up your switches tobest work with Tivoli SAN Manager.

Here are some general guidelines:

v Verify that all SNMP error trap destinations for FC switches point to the managerIP address.

v Make sure that the SNMP community names are defined and known. Tivoli SANManager uses the “public” community name by default to access the MIBs.

v If you have your Tivoli SAN Manager configured on AIX, it is not recommendedto send traps from a switch directly to the AIX manager. Instead, it isrecommended that you send them to the remote console, and then useNetView’s trap forwarding to send them to the port on the AIX manager.

v Port 162 is the default port to send SNMP traps to for Tivoli SAN Manager or theTivoli Remote Console.

Tips by product type

BrocadeYou need SNMP enabled:

1. Use the Telnet feature of the switch to get to the command interface.

2. After you are logged on as administrator to the switch, make sure that the FA,FE, and SW MIBs and traps are enabled. You can use the snmpmibcapsetcommand to enable the MIBs. You can type help snmpmibcapset for moredetails.

Forwarding SNMP traps:

1. Use the Telnet feature of the switch to get to the command interface.

2. Use the agtcfgset command to set:

v The SNMP trap destination from the Telnet interface (IP address of TivoliSAN Manager)

v The level of the trap (2)

v The community of the trap receiver (public by default)

3. Use the agtcfgshow command to check the settings.

Note: When doing agtcfgshow, be sure to check for the SNMP ACL at theswitch to make sure that there are no restrictions to the SAN manager’sIP address.

4. You can type help agtcfgset for more information.

CiscoYou might want to have traps forwarded even though Cisco is supported in-bandonly. Refer to your Cisco switch documentation for information on forwarding SNMPtraps.

McDATAv If you are planning to run agents on your SAN, you must have an Open System

Management Server license that has been enabled. Without it, Tivoli SAN


Manager cannot take advantage of much of the in-band information collected byagents on managed hosts. You can still manage a McDATA switch that does nothave this license using out-of-band management methods. It just will not have asmuch detailed information. You can check if this license is installed as follows:From the EFC manager platform switch screen, select the Configure tab, andthen select Features from the drop-down menu.

v There are a number of common ways to set up the SNMP traps:

– McDATA switches can be managed using the EFC manager or from theWeb-based SANpilot interface.

- From the EFC manager platform switch screen, select the Configure tab,and then select SNMP Agent from the drop-down menu. Follow theprompts.

- From the SANpilot main Web screen, select the Management tab, andthen select the SNMP sub-tab and follow the prompts to configure theSNMP traps.

– Using HTTP, you can bring up the more basic, Web-based managementinterface. Enter the IP address of the switch. Select the Management tab,then select the SNMP tab and follow the prompts.

Note: The default Trap Community for Tivoli SAN Manager is public, and the trapaddress should be the IP address of the SAN Manager

Refer to your McDATA documentation for more information.

INRANGEThe IN-VSN Enterprise Manager console can be used to set up trap forwarding onINRANGE switches.

1. From the console, select the switch that you would like to configure.

2. Select the System Configuration tab, and then select Configuration Type ofNetwork from the configuration type pull-down menu.

3. Ensure that the appropriate fields are completed:

v Enable SNMP

v Trap Community (the IBM Tivoli SAN Manager default value is public)

v Trap Address (the address of your SAN Manager)

Refer to INRANGE documentation for more information.

Switches included with the IBM Integration ServerThe IBM Integration Server comes with switches. Be sure to configure them withTivoli SAN Manager as you would that switch if it were in a typical SAN, looking atSNMP traps and MIB reporting as appropriate. See Chapter 5, “Setting up switches”, on page 17 for more information.


Chapter 6. Configuring Tivoli SAN Manager

Configuring Tivoli SAN Manager notificationThe Tivoli SAN Manager can be set up to send you notification of changes orproblems in the SAN. This section describes how to set up the notificationmechanism. There are two primary vehicles for event generation. If using the TivoliEvent Console (TEC), TEC events can be generated. For more information on thistopic, refer to the IBM Tivoli Storage Area Network Manager: A PracticalIntroduction, SG24–6848, or the IBM Tivoli Storage Area Network Manager User’sGuide. The other mechanism is using SNMP alerts.

The following sections tell you how to set SNMP traps for Tivoli NetView and IBMDirector. They also give guidance on how to filter the SNMP alerts.

Forwarding SNMP alertsIf you do not have access to a Tivoli Event Console to use as a notificationmechanism, it is recommended that you consider using the SNMP trap generationcapability built into Tivoli SAN Manager. These traps can be forwarded to theNetView console that comes with Tivoli SAN Manager, or they can be forwarded toanother SNMP management platform, such as IBM Director.

Setting up the SNMP trap destination in Tivoli SAN ManagerTo receive SNMP traps from Tivoli SAN Manager, you need to set up the trapdestination in Tivoli SAN Manager. You can do this by selecting SAN->Set EventDestination from the Tivoli NetView console. A window similar to Figure 2 onpage 20 is displayed.


Type the IP address, port number, and community name of the SNMP managerconsole that you want to use for receiving SNMP traps from the Tivoli SANManager Server. After you type in the information, click Add to add the entry to thelist.

Note: The default port number for NetView and IBM Director is 162.

Filtering SNMP alertsYou do not want to see notification on all alerts generated by the Tivoli SANManager.

Figure 2. Event Destination


You should monitor the following alerts:

v EDFI device notification, BTAserviceEvent_OID “1.3.6.1.4.1.2.6.173.3.36.”This notification indicates that EDFI has identified a link that will be failing soon.(You should monitor EDFI device notification only if EDFI is enabled.)

v Missing device notification, btamissingDeviceEvent_OID“1.3.6.1.4.1.2.6.173.3.101.” This notification indicates that a device on theSAN is missing.

v Missing relationship notification, btamissingRelationshipEvent_OID“1.3.6.1.4.1.2.6.173.3.103.” This notification indicates that all connectionsbetween a device and a server have failed.

The following traps are routine and should normally be filtered out:

v btamodifiedAttributeEvent 1.3.6.1.4.1.2.6.173.3.102

v btanewDeviceEvent 1.3.6.1.4.1.2.6.173.3.104

v btanewRelationshipEvent 1.3.6.1.4.1.2.6.173.3.106

v btaclearChangesDoneEvent 1.3.6.1.4.1.2.6.173.3.108

v btamodelUpdatedEvent 1.3.6.1.4.1.2.6.173.3.110

v btanormalDeviceEvent 1.3.6.1.4.1.2.6.173.3.112

v btanormalRelationshipEvent 1.3.6.1.4.1.2.6.173.3.114

Receiving and filtering SNMP alerts with NetViewThe Tivoli SAN Manager Server can generate SNMP traps. These traps can beforwarded to some other Tivoli NetView console (forwarding to the same server thatthe SAN Manager is on not allowed) or to another SNMP management console(see Figure 3). A good candidate for receiving the events is a Remote Console.

Setting up the MIB file in Tivoli NetViewFor this scenario, you can use the ITSANM.MIB file from the \misc\utils directory onthe Tivoli Storage Area Network Manager CD. The MIB file should be set up on theTivoli NetView Console that is receiving SAN Manager events. This MIB fileprovides only the trap information.

Figure 3. Tivoli SAN Manager-generated SNMP traps

Chapter 6. Configuring Tivoli SAN Manager 21

The MIB file should be incorporated in your SNMP management console trapdefinition to make sure that traps will display in an appropriate format in the TivoliNetView Event browser. After you have installed Tivoli NetView, you must createtrap entries in the Tivoli NetView trapd.conf file. This is done through a batch filecreated by the Tivoli NetView mib2trap program.

Note: Do not edit the file manually.Follow these steps:

1. Run the mib2trap program on the ITSANM.MIB file. Specify the full path namefor a writable directory when creating the ITSANM.BAT file. For example, runthis command to create the bat file on the directory c:\temp:

mib2trap c:\tmp \ITSANM.MIB c:\tmp \ITSANM.BAT

You can name the BAT file anything that you want. This example creates a filecalled ITSANM.BAT.

2. Run the ITSANM.BAT file.

3. Restart Tivoli NetView, and bring up the monitor to see all the events.

Changing the SNMP community nameThe default SNMP community name that is used in Tivoli SAN Managerimplementation is public.

Note: Tivoli SAN Manager supports only one SNMP community name for SNMPqueries and listening for SNMP event traps. A device can have severalcommunity names, but Tivoli SAN Manager can communicate with only oneof those names. Also, if the SNMP community name entered in thecommand is not a community name on the device, Tivoli SAN ManagerSNMP queries will time out. Tivoli SAN Manager will not be able tocommunicate with the device.

If you want to change the community name, perform the following steps:

On Windows:

1. From a command prompt window on the Tivoli SAN Manager server system,change to the following directory:

\tivoli\itsanm\bin\manager\bin\w32-ix86

2. Enter the following commands:

setenv

srmcp -u <username> -p <password> ConfigService set SNMPCommunityName<community name>,

where <username> and <password> are any valid user on the system. The<community name> field should be set to the value that you want thecommunity name changed to.

On AIX:

1. From a terminal, change to the following directory:

/tivoli/itsanm/bin/manager/aix

2. Enter the following commands:

. ./setenv.sh (note the space between the dots)

./srmcp.sh -u <username> -p <password> ConfigService setSNMPCommunityName <community name>,


where <username> and <password> are any valid user on the system. The<community name> field should be set to the value that you want thecommunity name changed to.

Receiving and filtering SNMP alerts with IBM DirectorAfter installing IBM Director on your system and before starting to receive trapsfrom Tivoli SAN Manager Server, you need to set the trap destination to your IBMDirector. The procedure for this is the same as described in “Setting up the SNMPtrap destination in Tivoli SAN Manager” on page 19.

Next, you need to import the Tivoli SAN Manager MIB into IBM Director. You canuse the ITSANM.MIB file from the \misc\utils directory on the Tivoli Storage AreaNetwork Manager CD. This can be done by right-clicking on SNMP Devices (underAll Groups) and selecting the Compile a new MIB option.

The next step is to define the Tivoli SAN Manager Server system in IBM Director.You can do this by accessing the IBM Director Console as shown in Figure 4.

As you can see, the Tivoli SAN Manager Server system (POLONIUM) is defined asan SNMP-capable device.

If you want to see the SNMP trap events coming from the Tivoli SAN Managerserver, drag the All events task, as shown in Figure 4, from the Tasks windows tothe defined system. A window, similar to Figure 5 on page 24, is displayed.

Figure 4. IBM Director Console


As you can see, there is an event showing that the managed host TUNGSTEN wasshut down.

IBM Director allows you to build event filters that can then be associated withactions, for example, sending an e-mail alert to the system administrator. See“Filtering SNMP alerts” on page 20 for a list of traps that should normally be filteredout.

Full discovery

Note: Full discovery is recommended only when setting up agents in your SANs. Ifyou do not have any agents, this procedure will not help you. Do not enablefull discovery unless you have a machine that has a minimum of 2 GB ofmemory and a 1.6-GHz processor.

In order to get full host view and device views, you must enable full discovery. Thestandard version of Tivoli SAN Manager comes with full discovery enabled bydefault. The Bonus Pack comes with full discovery disabled by default. In order toenable full discovery, use the following procedure.

Note: You can use any valid local system user ID and password on the manageroperating system to execute these commands.

Figure 5. SNMP event from Tivoli SAN Manager


To issue a command on Windows on the Tivoli SAN Manager platform:

1. Open a command prompt window.

2. Change the directory to: <installation directory>\manager\bin\w32-ix86. Thedefault installation directory is tivoli\itsanm\manager\bin\w32-ix86.

3. Enter the following command: setenv.

4. Enter the following commands to turn on full attribute scan upon polling, and toset a polling interval of 20 minutes:

srmcp -u <user_ID> -p <password> ConfigService set FullAttributeScan PollNowAndTimeBasedsrmcp -u <user_ID> -p <password> ConfigService set hostPollingInterval 1200000

5. In order to check the attribute scan value, you can enter the followingcommand:

srmcp -u <user_ID> -p <password> ConfigService get FullAttributeScan

To issue a command on AIX on the Tivoli SAN Manager platform:

1. Open a terminal window.

2. Change the directory to: <installation directory>/agent/bin/aix. The defaultinstallation directory is /tivoli/itsanm/agent/bin/aix.

3. Enter the following command: . ./setenv.sh.

Note: When entering . ./, be sure that there is a space between the dots.

4. Enter the commands to turn on full attribute scan upon polling and to set apolling interval of 20 minutes:

./srmcp.sh -u <user_ID> -p <password> ConfigService set FullAttributeScan PollNowAndTimeBased

./srmcp.sh -u <user_ID> -p <password> ConfigService set hostPollingInterval 1200000

5. In order to check the attribute scan value, you can enter the followingcommand:

./srmcp.sh -u <user_ID> -p <password> ConfigService get FullAttributeScan

Application launchTivoli SAN Manager provides an application launch facility for SAN components. Forsome devices, Tivoli SAN Manager automatically discovers and launches thedevice-related tool. Tivoli SAN Manager has an internal set of rules (in XML format)by which it identifies the devices whose tool it can launch. The following is a list ofproducts that have this level of support:

v ESS – ESS specialist

v IBM 2109 switch – Web tool

v Brocade switches – Web tool

v McDATA Switches – Web tool

Note: Refer to the IBM Tivoli Storage Area Network Manager User’s Guide formore information on application launch.



Appendix A. Management tips and procedures

Service toolTivoli SAN Manager comes with a service tool that will gather all the files andinformation needed by service to help with SAN problem determination. The servicetool is available on agents, managers, and remote consoles, and gathers data forthat particular component. There is a slight variation in what to do for AIX andWindows.

Windows1. Go to the service tool directory. The path to the service tool is usually

c:\tivoli\itsanm \manager\service. (If it is not there, then the Tivoli SANManager was not installed using the default path.)

2. The file in this directory that you want to run is called service.bat. Type servicefrom the windows command line in the directory mentioned above.

3. An ITSANMservice.zip file will be placed in the same directory. Send that file tothe service person as directed.

AIX1. Go to the service tool directory. The path to the service tool is usually

/tivoli/itsanm /manager/service. (If it is not there, then the Tivoli SAN Managerwas not installed using the default path.)

2. The file in this directory to run is called service.sh. Run this script.

3. An ITSANMservice.zip output file will be placed in the same directory. Sendthat file to the service person as directed.

Removing devices on managed AIX HostsThe driver that gets installed with the AIX® agent configures a device [afscsi]associated with each of the fcs adapters:

fcs2 Available 40-58 FC Adapterfscsi2 Available 40-58-01 FC SCSI I/O Controller Protocol Deviceafscsi2 Available 40-58-02 ITSANM Asynchronous Event Protocol Driver

You cannot remove devices of types fcs and afscsi while the agent is running.

Here is an example of what you might see if you do not stop this correctly:

Perform the following procedure to remove devices while the agent is running.

1. Run the following check to verify that the agent is running:

ps -aef |grep ″java.*tsnm.baseDir″ | grep -i ’itsanm\/agent’

2. Execute the following command to stop the agent:

/tivoli/itsanm/agent/bin/aix/tcstop.sh

# rmdev -l fcs2 -d -Rfscsi2 deletedMethod error (/usr/lib/methods/ucfgdevice):0514-062 Cannot perform the requested function because thespecified device is busy.


3. After stopping the agent, execute the following command:

ps -ef | grep -i OpenEvents

If the process is still running, then end it.

4. Remove the devices. Here is an example of what you should see if you did stopit correctly:

5. Execute the following command to restart the agent:

/tivoli/itsanm/agent/bin/aix/tcstart.sh

Disabling EDFI for SAN maintenance and repair actionsIt is important that EDFI be disabled when doing maintenance or repair actions on aSAN. Leaving EDFI enabled has the potential to cause false EDFI notifications.Remember to enable EDFI after the action is complete.

Refer to the IBM Tivoli Storage Area Network Manager User’s Guide for moreinformation on enabling and disabling EDFI.

# rmdev -l fcs2 -d -Rfscsi2 deletedafscsi2 deletedfcs2 deleted


Appendix B. 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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right may beused instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant you anylicense to these patents. You can send license inquiries, in writing, to:

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

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to: IBMWorld Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo106, Japan

The following paragraph does not apply to the United Kingdom or any other countrywhere such provisions are inconsistent with local law: INTERNATIONAL BUSINESSMACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″ WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some statesdo 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 beincorporated in new editions of the publication. IBM may make improvements and/orchanges in the product(s) and/or the program(s) described in this publication at anytime without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseWeb sites. The materials at those Web sites are not part of the materials for thisIBM 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 believesappropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programsand other programs (including this one) and (ii) the mutual use of the informationwhich has been exchanged, should contact:


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

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed material availablefor it are provided by IBM under terms of the IBM Customer Agreement, IBMInternational Program License Agreement or any equivalent agreement between us.

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

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

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

If you are viewing this information softcopy, the photographs and color illustrationsmay not appear.

TrademarksThe following are trademarks of the IBM Corporation in the United States or othercountries or both:

AIX Netfinity TivoliEnterprise Storage Server NetView Tivoli Enterprise ConsoleIBM pSeries TotalStoragethe IBM logo Redbooks xSeriesiSeries

Intel and Pentium are registered trademarks of Intel Corporation in the UnitedStates, other countries, or both.

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

Other company, product or service names may be trademarks or service marks ofothers.


Glossary

API. application programming interface. A functionalinterface that allows an application program written in ahigh-level language to use specific data or functions ofthe operating system or another program.

connection. One or more links between exactly twoSAN objects, represented graphically by a single line.

device. Storage or other non-host boxes connected tothe storage area network. Note that for EDFI, devicerefers to any entity in the SAN, so be careful to makethat distinction in the EDFI section. The list of devicesis:bridge Fibre Channel to SCSI converters are shown

as bridges. Support for SAN problemdetermination on bridges is not supported inthis guide.

disk Disk drives that are not behind a controller.This is often referred to as JBOD.

ESS ESS is specifically recognized by IBM TivoliSAN Manager and has its own icon.

hub Fibre Channel Hub. Support for SAN problemdetermination on hubs is not supported in thisguide.

SAN Volume ControllerIBM® SAN Volume Controller subsystem.

tape Tape drives and tape libraries are bothrepresented to IBM Tivoli SAN Manager astape.

unknownAny device that has not been identified islabeled as unknown.

DLL. dynamic link library. A file containing executablecode and data bound to a program at load time or runtime, rather than during linking. The code and data in adynamic link library can be shared by severalapplications simultaneously.

EDFI. Error Detection Fault Isolation. A predictiveanalysis function in IBM Tivoli SAN Manager that can beused for monitoring your SAN. More information on thisfunction is provided in the IBM Tivoli Storage AreaNetwork Manager User’s Guide and IBM Tivoli StorageArea Network Manager Planning and Installation Guide.

HBA. host bus adapter. The Fibre Channel adaptersthat are installed in the hosts.

host. Hosts are the servers connected to your SAN.Note that if you do not have an agent on your server, itwill most likely show up as an unknown device.

icon. Icons are graphical objects used by NetView torepresent a SAN. There are different icons to representthe different SAN elements.

interconnect element. This is how IBM Tivoli SANManager talks about switches. In this guide,interconnect elements refer specifically to Fibre Channelswitches.

ISL. Inter-switch list.

links. A link is a single link from one port to another,including the cable. Note that for IBM Tivoli SANManager, you cannot determine whether a linkcorresponds to a connection without going into theproperties and verifying the information.

LUN. logical unit number. An identifier used on a SCSIbus to distinguish among up to eight devices (logicalunits) with the same SCSI ID.

managed vs. unmanaged. Not all entities on a SANare managed by Tivoli® SAN Manager. By default, TivoliSAN Manager manages everything that it can see.However, entities in the SAN can be turned tounmanaged by the user. (See IBM Tivoli Storage AreaNetwork Manager User’s Guide for details.)

MIB. Management Information Base. A definition formanagement information that specifies the informationavailable from a host or gateway and the operationsallowed. The standard hierarchical format of a MIB isstructured using rules provided by SNMP.

multi-ported. Many hosts and devices use more thanone port to attach to the SAN for increased redundancyand performance. Note that from the graphical view youcannot determine which connections are multi-portedand which are not. You have to go into the properties tosee this.

port. A single transmitter/receiver pair used in a FibreChannel network.

RNID. Report Node Identification. A Fibre Channelservice that allows IBM Tivoli SAN Manager to discovera unit and identify it without having the in-band agentsinstalled.

root. Initial level in NetView. It contains Storage AreaNetworks as well as normal networks.

SNMP. Simple Network Management Protocol. Aprotocol used by network hosts to exchange informationused in the management of networks. SNMP networkmanagement is based on the client/server model. Eachhost that is to be managed runs a process called anagent. The agent is a server process that maintains theManagement Information Base (MIB) database for thehost. SNMP is supported by most SAN products andcan also be used for communication between the SANmanager and devices on the SAN.


states. Every component of the SAN is classified byIBM Tivoli SAN Manager into one of three states. Notethat the states here are the state as seen by IBM TivoliSAN Manager the last time it checked the SAN. Thestates are defined below with the default colors providedby NetView (colors are configurable):critical/red state

Component is considered failed.marginal/yellow state

Component is considered partially failed.normal/green state

Component is considered working.

SAN. storage area network. A specific set of switchesthat are interconnected to form a fabric.

trap. In the Simple Network Management Protocol(SNMP), a message sent by a managed node (agentfunction) to a management station to report anexception condition.

VNC. Virtual Node Configuration.

WWN. World Wide Name

WWNN. World Wide Node Name

WWPN. World Wide Port Name


Readers’ Comments — We’d Like to Hear from You

IBM TotalStorageConfiguring IBM Tivoli SAN Manager with IBM Eserver SAN Products

Publication No. SC30-4066-00

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied Very DissatisfiedOverall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied Very DissatisfiedAccurate h h h h h

Complete h h h h h

Easy to find h h h h h

Easy to understand h h h h h

Well organized h h h h h

Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.

Readers’ Comments — We’d Like to Hear from YouSC30-4066-00

SC30-4066-00

��Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM CorpDept. CGFAPO Box 12195Research Triangle Park, NC 27709-9990

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

Printed in U.S.A.

SC30-4066-00

Documents

Configuring Tivoli SAN Manager with IBM