Configuring IBM Tivoli SAN Manager with IBM Eserver SAN Products

Transcription

1 IBM TotalStorage Configuring IBM Tivoli SAN Manager with IBM Eserver SAN Products SC

2

3 IBM TotalStorage Configuring IBM Tivoli SAN Manager with IBM Eserver SAN Products SC

4 First Edition (August 2003) Copyright International Business Machines Corporation All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Introduction Purpose of this document Is Tivoli SAN Manager something that I should install? Tivoli SAN Manager and IBM Service SAN Manager functions Bonus Pack issues Tivoli SAN Manager and other SAN managers What hardware does this book support? What education should I have before using this document? Related publications Chapter 2. Overview Chapter 3. Placing Tivoli SAN Manager components Manager Managed hosts Remote console Tivoli SAN Manager decision checklist Remote access Collaboration using the Tivoli SAN Manager Remote Console Remote viewing using VNC Windows Terminal Services Chapter 4. Perform upgrades to your SAN components Tivoli SAN Manager support Web site Configuring SAN equipment Updating your drivers Other issues with managed hosts HBAs on the SAN Volume Controller and Integration Server Master Console 15 HBAs on the SAN Volume Controller Chapter 5. Setting up switches Tips by product type Brocade Cisco McDATA INRANGE Switches included with the IBM Integration Server Chapter 6. Configuring Tivoli SAN Manager Configuring Tivoli SAN Manager notification Forwarding SNMP alerts Filtering SNMP alerts Receiving and filtering SNMP alerts with NetView Receiving and filtering SNMP alerts with IBM Director Full discovery Application launch Appendix A. Management tips and procedures Service tool Windows AIX Removing devices on managed AIX Hosts Copyright IBM Corp iii

6 Disabling EDFI for SAN maintenance and repair actions Appendix B. Notices Trademarks Glossary iv Configuring Tivoli SAN Manager with IBM Eserver SAN Products

7 Chapter 1. Introduction Purpose of this document Storage networks provide connectivity allowing for the sharing, virtualization of storage, and other advanced features not commonly done with direct attached storage. These networks are complex and need management tools to be managed efficiently. Practices for setting up these management tools have been established and make best use of their capabilities. Please 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 to make IBM and IBM-partner SAN hardware and infrastructure software work best with 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 that includes switches. It has extensive support for Fibre Channel SANs and limited support for iscsi SANs. This guide covers Fibre Channel SAN configurations. See Tivoli documentation for iscsi configuration and installation. Tivoli SAN Manager and IBM Service The IBM service and support organization uses Tivoli SAN Manager on some products to help with SAN problem determination. When a SAN problem occurs, service can use the Tivoli SAN Manager to understand the SAN configuration and to look at the link error history associated with the problem. SAN Manager functions v v v v v Bonus Pack issues The Tivoli SAN Manager also has a predictive failure analysis function that requires constant running to identify suspect links. It is recommended that the Tivoli SAN Manager be installed and used for routine SAN monitoring. View your SAN topology Monitor for SAN errors and events From a central place, look at host and device perspectives of the SAN From a central place, launch applications for products on your SAN that are Web-based If you do not have the Bonus Pack version of the the Tivoli SAN Manager, skip this section. The Tivoli SAN Manager Bonus Pack has a 64-switch port limit for the SANs 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 than 64 ports, you can purchase the Tivoli SAN Manager. If you do not plan to purchase the Tivoli SAN Manager, and you have more than 64 ports on your SAN, then you should not plan to use the Bonus Pack. Contact your IBM marketing representative for more information. Copyright IBM Corp

8 Tivoli SAN Manager and other SAN managers Configurations with Tivoli SAN Manager and other SAN managers running against the same SAN or on the same server are not supported. Tivoli SAN Manager agents should not be run on the same server as other SAN managers or other SAN manager agents. What hardware does this book support? This document is intended to be used with Tivoli SAN Manager Version 1.2 and is intended as a configuration guide for the following list of hardware. The SAN Manager does support other products. For the complete set of products that are supported, see the product support matrix at: www-3.ibm.com/software/sysmgmt/products/support/ibm_tsanm_device_compatibility.html v v v iseries servers Models 8xx and above 2765 FC Tape Adapter 2766 FC Disk Adapter pseries servers (43P-150 minimum) Note: These minimums apply only if an agent is installed on the platform Fibre Channel Adapter 6228 Fibre Channel Adapter xseries servers (Pentium MHz minimum, Microsoft Windows or Linux operating 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 Server v 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 2145 v IBM TotalStorage Integration Server 2146 v IBM TotalStorage SAN Switch 2109 Models S08, S16, F16, F32, M12 v IBM TotalStorage SAN Switch 3534 Model F08 v INRANGE FC/ , FC/ , FC/ SAN directors v McDATA ED-5000, Intrepid 6064, Intrepid 6140, Sphereon 3016, Sphereon 3032, Sphereon 4500, Sphereon 3232 SAN switches and directors, and Sphereon 3216 v 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 storage networks. For beginners to storage area networks, a good Redbook to read would be the IBM SAN Survival Guide, SG Configuring Tivoli SAN Manager with IBM Eserver SAN Products

9 Related publications For those new to Tivoli SAN Manager, another good book to read would be IBM Tivoli Storage Area Network Manager: A Practical Introduction, SG These Redbooks can be found at: The IBM Tivoli Storage Area Network Manager Planning and Installation Guide, SC , and the IBM Tivoli Storage Area Network Manager User s Guide, SC , are referred to in this document. They can be found on the Web by going to: publib.boulder.ibm.com/tividd/td/tdprodlist.html and clicking on the IBM Tivoli Storage Area Network Manager link. Chapter 1. Introduction 3

10 4 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

11 Chapter 2. Overview Review and then follow the following steps when installing and configuring Tivoli SAN Manager. 1. Verify that the SAN is fully operational. Your SAN should be stable before you install Tivoli SAN Manager. 2. Review the Planning for installation of the IBM Tivoli Storage Area Network Manager Planning and Installation Guide. 3. Decide how you want to deploy Tivoli SAN Manager. See Chapter 3, Placing Tivoli SAN Manager components, on page 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 your SAN. See Tivoli SAN Manager support Web site on page 13. b. Based on the compatibility matrix review, update your storage and switch versions to obtain the desired level of function. c. On host platforms that will have an agent, update your HBA drivers. This is very important on those host platforms where you are planning on running an agent on your SAN. See Updating your drivers on page Set up your switches to work with the SAN Manager. See Chapter 5, Setting up switches, on page Install SAN Manager and the latest appropriate PTFs. You can obtain the latest PTfs at the following Web site: www-3.ibm.com/software/sysmgmt/products/support/ibmtivolistorageareanetworkmanager.html If you have a SAN Volume Controller or SAN Integration Server with a Master Console with SAN Manager Bonus Pack pre-installed, follow the appropriate steps in the IBM TotalStorage SAN Integration Server 2146 Administrator s Guide, SC It is recommended that, as part of your installation procedure, you enable EDFI as explained in the IBM Tivoli Storage Area Network Manager Planning and Installation Guide. 7. Configure SAN Manager for correct event notification. See Chapter 6, Configuring Tivoli SAN Manager, on page 19. Copyright IBM Corp

12 6 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

13 Chapter 3. Placing Tivoli SAN Manager components Tivoli SAN Manager helps you manage your resources by providing network resource discovery and management capabilities. Tivoli SAN Manager manages all of your SAN resources, including devices connected to host systems through fiber-based hubs, bridges, switches, routers, gateways, and directors. Figure 1. Tivoli SAN Manager in a SAN environment Manager Managed hosts With Tivoli SAN Manager, one system acts as the manager, and, if you have agents, one or more other systems are the managed hosts on which its agents reside. The manager performs the following functions: v Gathers data from agents on managed hosts and switches, such as descriptions of 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 An agent resides on each managed host. The agents on managed hosts perform the following functions: v v v Gather information about the SAN by querying switches and devices for attribute and topology information Gather host-level information, such as file systems and mapping to LUNs Gather event information and other information detected by HBAs Copyright IBM Corp

14 Remote console The remote console allows you to access Tivoli SAN Manager from remote locations across a network or modem. If you have multiple operators that need to view the topology of your environment, having several remote consoles set up provides easy access for monitoring your environment. You must have a Windows user ID with administrative authority to install the Tivoli SAN Manager console. You must install the console on a Windows 2000 or Windows XP platform. If you have Tivoli NetView installed, Tivoli SAN Manager configures Tivoli NetView, but it does not install it. If you do not have Tivoli NetView installed, Tivoli SAN Manager installs Tivoli NetView. See the IBM Tivoli Storage Area Network Manager Planning and Installation Guide for more information on installing and configuring a remote console. Tivoli SAN Manager decision checklist The following decision checklist contains specific recommendations for configuring IBM Systems Group-supported configurations as used for SAN problem determination by IBM Systems Group Service. Tivoli recommendations are generally broader in scope. If for some reason you find these recommendations restrictive, check the Tivoli Web site and feel free to use the Tivoli SAN Manager as specified there; in that case, IBM service is less likely to use the Tivoli SAN Manager for IBM problem determination. The following checklist will help you decide how to configure your Tivoli SAN Manager. 1. SAN size: If you use Fibre Channel but do not have a switch in your system, using the Tivoli SAN Manager is not recommended. If you only have a single 8- or 16-port switch, a Tivoli SAN Manager might not be needed; you might consider using the switch tools instead. For larger SANs, use of this Tivoli SAN Manager is recommended. Remember that the Bonus Pack version has a 64-port license restriction. An upgrade is available. Contact an IBM marketing representative for information on an upgrade. 2. Switches and Tivoli SAN Manager Can Tivoli SAN Manager manage my switches? Compare your current switch firmware versions with the minimum levels listed in Table 1 on page 9. If your switch meets the minimum level and is recommended for use with Tivoli SAN Manager, then installing Tivoli SAN Manager with your SAN is supported by this configuration guide. If the switch is not on the list or does not meet the minimum firmware level, then configuring Tivoli SAN Manager with that switch is not supported by this configuration guide. Your switch might still be supported with Tivoli SAN Manager. To install and configure the SAN manager with the switch, use Tivoli SAN Manager documentation. Check the Tivoli Web site: www-3.ibm.com/software/sysmgmt/products/support/ibmtivolistorageareanetworkmanager.html 8 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

15 Table 1. Supported switches Switch Minimum level of switch IBM 2109 S08, S e IBM 2109 F16, F c IBM 2109 M c IBM 3534 F c Cisco MDS Cisco MDS INRANGE FC/ INRANGE FC/ INRANGE FC/ McDATA ED McDATA ES McDATA Intrepid McDATA Intrepid 6140 Any IBM-supported level McDATA Sphereon McDATA Sphereon McDATA Sphereon 4500 Any IBM-supported level McDATA Sphereon 3232 Any IBM-supported level McDATA Sphereon 3216 Any IBM-supported level 3. Tivoli SAN Manager hardware platform: There is a minimum processor speed and memory size requirement for Tivoli SAN Manager. For Windows platforms, the recommended processor speed is 1-GHz minimum speed. For AIX platforms, a machine of equivalent processing speed should be used. If you do not have access to such a system, do not install the Tivoli SAN Manager. If you have a platform that is at the minimum configuration, do not install agents. Notes: a. If you have a Master Console with a pre-installed SAN Manager, your hardware platform is adequate. b. The 1-GHz minimum speed assumes that the SAN manager has a dedicated 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 the Master Console. v LUN Access Adding an agent to the host will give you a LUN-level view of storage that host has access to. If LUN views are important, you might want to consider adding an agent on that host. v EDFI Function If you have critical links to your hosts and storage and you need full predictive failure analysis, you should install an agent that can cover those links. The agent will cover all storage that it has access to and its own link to the switch from the managed host. (Note that most of EDFI function is Chapter 3. Placing Tivoli SAN Manager components 9

16 v provided by out-of-band data collection and additional information is provided by in-band agents only for the edge connections.) Another reason to install an agent is that the McDATA ED5000 and the Cisco 9215 and 9509 switches require an in-band agent since they do not support the out-of-band management protocols required by the SAN Manager. Because of this limitation, problem determination using the SAN Manager is limited. 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 these HBAs: IBM 00N6881/FC2102 IBM FC2/66-19K1246/FC2103 IBM FC2/133-24P0960/FC2104 QLogic QLA23xx QLogic QLA2200 v v v v v It is recommended that you install version Windows 8.2 or higher on your Qlogic 23xx adapters. Version 8.2 is not available for QLA2200 adapters. Do not use a driver version older than the Windows driver for Windows NT or Windows Using an driver will work but does not support sending RNID to other devices. The agent will not be able to identify devices out on the SAN, and the icons will remain unknown. The Windows driver offers RNID support. The 8.2 Windows driver offers full support for EDFI. Note: Before updating your current firmware levels, verify that the newer version is also supported by your SAN components. AIX: The following text applies to both of these HBAs: IBM 6227 IBM 6228 Note: Be aware that putting the Tivoli SAN Manager agent on your server will result in logs to your error log in non-error cases. It is not recommended that you put the agent on systems where you have a pager or live reporting mechanism tied to logging events. The most common occurrence of this phenomenon is an entry for SAN devices that reject a RNID Extended Link Service request issued by the Tivoli SAN Manager agent. 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 might have been added since this document was published. Any driver level for the IBM 6227 and IBM 6228 adapters released with those levels will work. Linux: Tivoli SAN Manager does support Linux in some cases, but Linux is not supported in this guide. See the Tivoli support Web site. 5. Managed host configuration decisions: 10 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

17 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 to your HBA. Also, be aware that each agent addition does add additional processor requirements to the Tivoli SAN Manager. Do not add agents to a system that just meets the minimum configuration requirements. Remote access Collaboration using the Tivoli SAN Manager Remote Console The Tivoli SAN Manager Remote Console allows multiple parties to look at the same SAN management data at the same time. This can be helpful when doing problem determination and discussing a SAN over the phone. Be aware that the remote console requires 512 MB of memory. Remote viewing using VNC Virtual Network Computing (VNC) is an application that allows remote control of a computer using a different machine and platform over the network. This software, available without cost, is another way to access Tivoli SAN Manager remotely. VNC does not come packaged with Tivoli SAN Manager. The VNC server adds a considerable load on the SAN Manager machine. It should be used sparingly and disabled when not needed to diagnose problems. Windows Terminal Services Windows Terminal Services does not work with Tivoli Remote Console or Tivoli SAN Manager. Do not use these together on the same system. Windows Terminal Services can be used for other processes on the manager or remote console machine, but it will not work correctly with SAN Manager itself. Chapter 3. Placing Tivoli SAN Manager components 11

18 12 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

19 Chapter 4. Perform upgrades to your SAN components Tivoli SAN Manager support Web site To look for product specific support information, it is important to visit the Tivoli device compatibility Web site at: www-3.ibm.com/software/sysmgmt/products/support/ibm_tsanm_device_compatibility.html Configuring SAN equipment This site is also a good place to go if you want to understand the level of support that you will get for a given SAN component. Here are some things to check for: v v v The level of Fibre Channel product support for SAN management is always improving. Compare the supported firmware versions or patches listed on the Web site with the versions installed on your SAN devices. A more recent version of firmware or code might be available with improved capability over what you are currently running. Look for the latest EDFI rule set and add it if appropriate. Refer to the IBM Tivoli Storage Area Network Manager Planning and Installation Guide for information. It is particularly important to get your switch levels up to the minimum support levels as shown in Table 1 on page 9. The purpose of this section is to help you set up your SAN equipment to work best with Tivoli SAN Manager. Updating your drivers The 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 Tivoli SAN Manager agent. Other issues with managed hosts on page 14 provides a set of tips for installing the proper HBA drivers on some platforms. Attention It is essential that you perform the following steps even if you have already installed the HBA drivers. 1. Link to: www-3.ibm.com/software/sysmgmt/products/support/ibm_tsanm_device_compatibility.html Also, link to: www-3.ibm.com/software/sysmgmt/products/support/ibmtivolistorageareanetworkmanager.html From there, check hints and tips and and support flashes for information about your host bus adapters. 2. From the Web site: a. The Web site will indicate what level of driver you should be running for optimal SAN manager support. You can compare that level with your current driver level and upgrade the driver, if appropriate. b. Go to the appropriate Web site for the HBA and get the recommended drivers. Copyright IBM Corp

20 c. Obtain and install the correct level of your driver. d. Sometimes you need an additional software package to help with the in-band management interface (called the HBA API). If necessary, obtain and install this software package. This is explained on the Tivoli support Web 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 hosts The supported level of host bus adapter varies by product. Tivoli has a recommended level as well. Be sure to check the support lists for the products you are connected to before making any driver updates. IBM Fibre Channel Host Adapter (00N6881/FC2102) on Windows The Fibre Channel Host Adapter has some limitations in event notification. This affects how you set up your switches. If all the agents in your SAN are connected by means of this type of adapter, it is especially important to set up your Simple Network 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 servers The following links are useful when configuring IBM host bus adapters (HBAs) and installing 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 Windows The Qlogic QLA2200 has some limitations in event notification. This affects how you set up your switches. If all the agents in your SAN are connected by means of this type of adapter, it is especially important to set up your SNMP alerts from the switches in your SAN, because you will not receive event notification from the agent. See Configuring Tivoli SAN Manager notification on page 19 for more information. QLogic QLA23xx Windows No issues. IBM FC2/66-19K1246/FC2103 No issues. IBM FC2/133-24P0960/FC2104 No issues. 14 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

21 HBAs on the SAN Volume Controller and Integration Server Master Console The Master Console has Fibre Channel access to the entire SAN associated with the SAN Volume Controller. This HBA and the associated drivers are pre-configured to support the Tivoli SAN Manager agent for Microsoft Windows. No updates should be necessary. HBAs on the SAN Volume Controller SAN Manager agents are not supported on the SAN Volume Controller. Chapter 4. Perform upgrades to your SAN components 15

22 16 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

23 Chapter 5. Setting up switches Tips by product type The purpose of this section is to give you guidance on setting up your switches to best work with Tivoli SAN Manager. Here are some general guidelines: v Verify that all SNMP error trap destinations for FC switches point to the manager IP address. v Make sure that the SNMP community names are defined and known. Tivoli SAN Manager 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 recommended to send traps from a switch directly to the AIX manager. Instead, it is recommended that you send them to the remote console, and then use NetView 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 the Tivoli Remote Console. Brocade You 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 snmpmibcapset command to enable the MIBs. You can type help snmpmibcapset for more details. 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 Tivoli SAN 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 the switch to make sure that there are no restrictions to the SAN manager s IP address. 4. You can type help agtcfgset for more information. Cisco You might want to have traps forwarded even though Cisco is supported in-band only. Refer to your Cisco switch documentation for information on forwarding SNMP traps. McDATA v 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 Copyright IBM Corp

24 v Manager cannot take advantage of much of the in-band information collected by agents on managed hosts. You can still manage a McDATA switch that does not have this license using out-of-band management methods. It just will not have as much detailed information. You can check if this license is installed as follows: From the EFC manager platform switch screen, select the Configure tab, and then select Features from the drop-down menu. There are a number of common ways to set up the SNMP traps: McDATA switches can be managed using the EFC manager or from the Web-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 the prompts. - From the SANpilot main Web screen, select the Management tab, and then select the SNMP sub-tab and follow the prompts to configure the SNMP traps. Using HTTP, you can bring up the more basic, Web-based management interface. 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 trap address should be the IP address of the SAN Manager Refer to your McDATA documentation for more information. INRANGE The IN-VSN Enterprise Manager console can be used to set up trap forwarding on INRANGE 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 of Network 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 Server The IBM Integration Server comes with switches. Be sure to configure them with Tivoli SAN Manager as you would that switch if it were in a typical SAN, looking at SNMP traps and MIB reporting as appropriate. See Chapter 5, Setting up switches, on page 17 for more information. 18 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

25 Chapter 6. Configuring Tivoli SAN Manager Configuring Tivoli SAN Manager notification The Tivoli SAN Manager can be set up to send you notification of changes or problems in the SAN. This section describes how to set up the notification mechanism. There are two primary vehicles for event generation. If using the Tivoli Event Console (TEC), TEC events can be generated. For more information on this topic, refer to the IBM Tivoli Storage Area Network Manager: A Practical Introduction, SG , or the IBM Tivoli Storage Area Network Manager User s Guide. The other mechanism is using SNMP alerts. The following sections tell you how to set SNMP traps for Tivoli NetView and IBM Director. They also give guidance on how to filter the SNMP alerts. Forwarding SNMP alerts If you do not have access to a Tivoli Event Console to use as a notification mechanism, it is recommended that you consider using the SNMP trap generation capability built into Tivoli SAN Manager. These traps can be forwarded to the NetView console that comes with Tivoli SAN Manager, or they can be forwarded to another SNMP management platform, such as IBM Director. Setting up the SNMP trap destination in Tivoli SAN Manager To receive SNMP traps from Tivoli SAN Manager, you need to set up the trap destination in Tivoli SAN Manager. You can do this by selecting SAN->Set Event Destination from the Tivoli NetView console. A window similar to Figure 2 on page 20 is displayed. Copyright IBM Corp

26 Figure 2. Event Destination Type the IP address, port number, and community name of the SNMP manager console that you want to use for receiving SNMP traps from the Tivoli SAN Manager Server. After you type in the information, click Add to add the entry to the list. Note: The default port number for NetView and IBM Director is 162. Filtering SNMP alerts You do not want to see notification on all alerts generated by the Tivoli SAN Manager. 20 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

27 You should monitor the following alerts: v EDFI device notification, BTAserviceEvent_OID 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 This notification indicates that a device on the SAN is missing. v Missing relationship notification, btamissingrelationshipevent_oid This notification indicates that all connections between a device and a server have failed. The following traps are routine and should normally be filtered out: v btamodifiedattributeevent v btanewdeviceevent v btanewrelationshipevent v btaclearchangesdoneevent v btamodelupdatedevent v btanormaldeviceevent v btanormalrelationshipevent Receiving and filtering SNMP alerts with NetView The Tivoli SAN Manager Server can generate SNMP traps. These traps can be forwarded to some other Tivoli NetView console (forwarding to the same server that the 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. Figure 3. Tivoli SAN Manager-generated SNMP traps Setting up the MIB file in Tivoli NetView For this scenario, you can use the ITSANM.MIB file from the \misc\utils directory on the Tivoli Storage Area Network Manager CD. The MIB file should be set up on the Tivoli NetView Console that is receiving SAN Manager events. This MIB file provides only the trap information. Chapter 6. Configuring Tivoli SAN Manager 21

28 The MIB file should be incorporated in your SNMP management console trap definition to make sure that traps will display in an appropriate format in the Tivoli NetView Event browser. After you have installed Tivoli NetView, you must create trap entries in the Tivoli NetView trapd.conf file. This is done through a batch file created 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 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:\tmp \ITSANM.MIB c:\tmp \ITSANM.BAT You can name the BAT file anything that you want. This example creates a file called 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 name The default SNMP community name that is used in Tivoli SAN Manager implementation is public. Note: Tivoli SAN Manager supports only one SNMP community name for SNMP queries and listening for SNMP event traps. A device can have several community names, but Tivoli SAN Manager can communicate with only one of those names. Also, if the SNMP community name entered in the command is not a community name on the device, Tivoli SAN Manager SNMP queries will time out. Tivoli SAN Manager will not be able to communicate 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 the community 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 set SNMPCommunityName <community name>, 22 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

29 where <username> and <password> are any valid user on the system. The <community name> field should be set to the value that you want the community name changed to. Receiving and filtering SNMP alerts with IBM Director After installing IBM Director on your system and before starting to receive traps from 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 Tivoli SAN Manager on page 19. Next, you need to import the Tivoli SAN Manager MIB into IBM Director. You can use the ITSANM.MIB file from the \misc\utils directory on the Tivoli Storage Area Network Manager CD. This can be done by right-clicking on SNMP Devices (under All 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. Figure 4. IBM Director Console As you can see, the Tivoli SAN Manager Server system (POLONIUM) is defined as an SNMP-capable device. If you want to see the SNMP trap events coming from the Tivoli SAN Manager server, drag the All events task, as shown in Figure 4, from the Tasks windows to the defined system. A window, similar to Figure 5 on page 24, is displayed. Chapter 6. Configuring Tivoli SAN Manager 23

30 Figure 5. SNMP event from Tivoli SAN Manager Full discovery As you can see, there is an event showing that the managed host TUNGSTEN was shut down. IBM Director allows you to build event filters that can then be associated with actions, for example, sending an alert to the system administrator. See Filtering SNMP alerts on page 20 for a list of traps that should normally be filtered out. Note: Full discovery is recommended only when setting up agents in your SANs. If you do not have any agents, this procedure will not help you. Do not enable full discovery unless you have a machine that has a minimum of 2 GB of memory and a 1.6-GHz processor. In order to get full host view and device views, you must enable full discovery. The standard version of Tivoli SAN Manager comes with full discovery enabled by default. The Bonus Pack comes with full discovery disabled by default. In order to enable full discovery, use the following procedure. Note: You can use any valid local system user ID and password on the manager operating system to execute these commands. 24 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

31 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. The default installation directory is tivoli\itsanm\manager\bin\w32-ix Enter the following command: setenv. 4. Enter the following commands to turn on full attribute scan upon polling, and to set a polling interval of 20 minutes: srmcp -u <user_id> -p <password> ConfigService set FullAttributeScan PollNowAndTimeBased srmcp -u <user_id> -p <password> ConfigService set hostpollinginterval In order to check the attribute scan value, you can enter the following command: 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 default installation 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 a polling 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 In order to check the attribute scan value, you can enter the following command:./srmcp.sh -u <user_id> -p <password> ConfigService get FullAttributeScan Application launch Tivoli SAN Manager provides an application launch facility for SAN components. For some devices, Tivoli SAN Manager automatically discovers and launches the device-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 of products 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 for more information on application launch. Chapter 6. Configuring Tivoli SAN Manager 25

32 26 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

33 Appendix A. Management tips and procedures Service tool Tivoli SAN Manager comes with a service tool that will gather all the files and information needed by service to help with SAN problem determination. The service tool is available on agents, managers, and remote consoles, and gathers data for that particular component. There is a slight variation in what to do for AIX and Windows. Windows AIX 1. 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 SAN Manager was not installed using the default path.) 2. The file in this directory that you want to run is called service.bat. Type service from the windows command line in the directory mentioned above. 3. An ITSANMservice.zip file will be placed in the same directory. Send that file to the service person as directed. 1. 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 Manager was 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. Send that file to the service person as directed. Removing devices on managed AIX Hosts The driver that gets installed with the AIX agent configures a device [afscsi] associated with each of the fcs adapters: fcs2 Available FC Adapter fscsi2 Available FC SCSI I/O Controller Protocol Device afscsi2 Available 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: # rmdev -l fcs2 -d -R fscsi2 deleted Method error (/usr/lib/methods/ucfgdevice): Cannot perform the requested function because the specified device is busy. 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 Copyright IBM Corp

34 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 stop it correctly: # rmdev -l fcs2 -d -R fscsi2 deleted afscsi2 deleted fcs2 deleted 5. Execute the following command to restart the agent: /tivoli/itsanm/agent/bin/aix/tcstart.sh Disabling EDFI for SAN maintenance and repair actions It is important that EDFI be disabled when doing maintenance or repair actions on a SAN. 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 more information on enabling and disabling EDFI. 28 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

35 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 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 grant 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 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan 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. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: Copyright IBM Corp

36 IBM Corporation Information Enabling Requests Dept. M Cottle Road San Jose CA U.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 available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. 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. All statements regarding IBM s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. 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. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Trademarks The following are trademarks of the IBM Corporation in the United States or other countries or both: AIX Netfinity Tivoli Enterprise Storage Server NetView Tivoli Enterprise Console IBM pseries TotalStorage the IBM logo Redbooks xseries iseries Intel and Pentium are registered trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product or service names may be trademarks or service marks of others. 30 Configuring Tivoli SAN Manager with IBM Eserver SAN Products

37 Glossary API. application programming interface. A functional interface that allows an application program written in a high-level language to use specific data or functions of the operating system or another program. connection. One or more links between exactly two SAN objects, represented graphically by a single line. device. Storage or other non-host boxes connected to the storage area network. Note that for EDFI, device refers to any entity in the SAN, so be careful to make that distinction in the EDFI section. The list of devices is: bridge disk ESS hub Fibre Channel to SCSI converters are shown as bridges. Support for SAN problem determination on bridges is not supported in this guide. Disk drives that are not behind a controller. This is often referred to as JBOD. ESS is specifically recognized by IBM Tivoli SAN Manager and has its own icon. Fibre Channel Hub. Support for SAN problem determination on hubs is not supported in this guide. SAN Volume Controller IBM SAN Volume Controller subsystem. tape Tape drives and tape libraries are both represented to IBM Tivoli SAN Manager as tape. unknown Any device that has not been identified is labeled as unknown. DLL. dynamic link library. A file containing executable code and data bound to a program at load time or run time, rather than during linking. The code and data in a dynamic link library can be shared by several applications simultaneously. EDFI. Error Detection Fault Isolation. A predictive analysis function in IBM Tivoli SAN Manager that can be used for monitoring your SAN. More information on this function is provided in the IBM Tivoli Storage Area Network Manager User s Guide and IBM Tivoli Storage Area Network Manager Planning and Installation Guide. HBA. host bus adapter. The Fibre Channel adapters that 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, it will most likely show up as an unknown device. icon. Icons are graphical objects used by NetView to represent a SAN. There are different icons to represent the different SAN elements. interconnect element. This is how IBM Tivoli SAN Manager talks about switches. In this guide, interconnect elements refer specifically to Fibre Channel switches. ISL. Inter-switch list. links. A link is a single link from one port to another, including the cable. Note that for IBM Tivoli SAN Manager, you cannot determine whether a link corresponds to a connection without going into the properties and verifying the information. LUN. logical unit number. An identifier used on a SCSI bus to distinguish among up to eight devices (logical units) with the same SCSI ID. managed vs. unmanaged. Not all entities on a SAN are managed by Tivoli SAN Manager. By default, Tivoli SAN Manager manages everything that it can see. However, entities in the SAN can be turned to unmanaged by the user. (See IBM Tivoli Storage Area Network Manager User s Guide for details.) MIB. Management Information Base. A definition for management information that specifies the information available from a host or gateway and the operations allowed. The standard hierarchical format of a MIB is structured using rules provided by SNMP. multi-ported. Many hosts and devices use more than one port to attach to the SAN for increased redundancy and performance. Note that from the graphical view you cannot determine which connections are multi-ported and which are not. You have to go into the properties to see this. port. A single transmitter/receiver pair used in a Fibre Channel network. RNID. Report Node Identification. A Fibre Channel service that allows IBM Tivoli SAN Manager to discover a unit and identify it without having the in-band agents installed. root. Initial level in NetView. It contains Storage Area Networks as well as normal networks. SNMP. Simple Network Management Protocol. A protocol used by network hosts to exchange information used in the management of networks. SNMP network management is based on the client/server model. Each host that is to be managed runs a process called an agent. The agent is a server process that maintains the Management Information Base (MIB) database for the host. SNMP is supported by most SAN products and can also be used for communication between the SAN manager and devices on the SAN. Copyright IBM Corp