Beruflich Dokumente
Kultur Dokumente
Steve Strutt
Select Additional materials and open the directory that corresponds with the Redpaper form number, REDP3821.
ibm.com/redbooks
SAN Switches
Figure 1 Tivoli Storage Area Network Manager and device availability alerting
The addition of this capability to Tivoli Storage Area Network Manager provides an enhanced real-time availability monitoring and alerting solution for SAN fabrics and SAN components.
Tivoli Storage Area Network Manager alerts on the availability of the SAN fabric itself and the FC Mgmt traps on SAN device health and availability. Fabric and SAN availability alerting is only one part of end-to-end storage availability monitoring and management. To provide a comprehensive view of availability, information about all aspects of storage infrastructure that have a bearing on the availability of the LUNs and file systems used by applications must be integrated into a management solution. Table 1 shows the IBM software and hardware products which can be integrated into a single end-to-end storage availability management solution for IBM TotalStorage environments.
Table 1 Components of an IBM end-to-end storage availability monitoring solution Event source Storage device Tape storage (3494, 359x) Disk storage (ESS, SVC, FAStT) SAN switches Storage application Tivoli NetView Device FC Mgmt traps Tivoli Storage Area Network Manager Tivoli Storage Area Network Manager SAN Error Predictor Tivoli Storage Resource Manager Device - SAN Storage Network Device - SAN LUNs File systems Availability Availability Errors Availability Availability, Utilization Device - Tape Device - Disk Device - SAN Availability Availability Availability Storage component Types of events
The solution outlined here using FC Mgmt traps and NetView adds a key component to this, namely the alerting on SAN device availability and status.
NetView instance on the Tivoli Storage Area Network Manager server already performs a number of functions, displaying the SAN topology (as a NetView map) and receiving and forwarding SNMP traps from SAN devices to Tivoli Storage Area Network Manager to trigger automatic topology refreshes. This NetView instance can also receive the device FC Mgmt traps and use these to query the sending device and its sensors status and send more detailed failure alerts to the NetView event log or Tivoli Enterprise Console. Figure 2 shows the execution flow for the monitoring and alerting solution described in this paper.
NetView
Tivoli NetView 1. FC Mgmt Trap 6. Issue Tivoli Enterprise Console event and new SNMP trap 5. FC Mgmt MIB Queries
SAN Switch
The following steps describe the execution flow for the monitoring and alerting solution: 1. NetView receives an FC Mgmt trap from a device that indicates a device event or change in state. 2. NetView forwards this event to Tivoli Storage Area Network Manager to trigger a topology refresh. 3. NetView looks up its definition for FC Mgmt traps. Associated with the trap is a script that should be executed on receipt of the trap. 4. The monitor and alerting script is called and executed. 5. The script executes NetView functions to query the FC Mgmt MIB on the device issuing the trap to return further details from the device. 6. A new SNMP trap or Tivoli Enterprise Console events, or both, are issued. These are in formatted text and show more detailed information. As shown in Figure 2, these new SNMP traps can be displayed in the NetView event log on the Tivoli Storage Area Network Manager server along with the Tivoli Storage Area Network Manager events about the availability of the SAN fabric, or on a Tivoli Enterprise Console.
This paper assumes that the scripts and other executables required are installed in the C:\custom\scripts directory. To issue the event to Tivoli Enterprise Console, a copy of the Tivoli Enterprise Console Version 3.8 version of postemsg.exe is included with the package. This should be compatible with any version of Tivoli Enterprise Console. It is installed in the custom/scripts directory.
3. Click Load. Browse to the directory where the FC Mgmt MIB was installed (c:\custom\scripts by default). Select the FC Mgmt MIB (v3_0FA.mib), and click Open to load the MIB.
The generated batch file (v3_0FA.bat) should then be executed to register the trap definitions. Note that the directory path for the addtrap commands in the created batch file might need to be edited to point to the directory where NetView was installed. A sample output when executing v3_0FA.bat is shown in Example 1.
Example 1 Output of executing v3_0FA.bat C:\Custom\scripts>v3_0fa.bat C:\usr\OV\bin\addtrap -l connUnitEventTrap -g 6 -s 4 -n fcmgmt -i 1.3.6.1.3.94 -o A -c LOGONLY -t 0 -S 1 -f - -F "$E $G $S $# args: $*"
trapd.conf file read Trap has been added. writing trapd.conf file... C:\usr\OV\bin\addtrap -l connUnitSensorStatusChange -g 6 -s 5 -n fcmgmt -i 1.3.6.1.3.94 -o A -c LOGONLY -t 0 -S 1 -f - -F "$E $G $S $# args: $*" trapd.conf file read Trap has been added. writing trapd.conf file... ..
After the batch file has been executed to add the trap definitions for the FC Mgmt MIB to NetView, the trap definition must be altered in NetView to execute the monitor script when the trap is received. This must be performed for each of the four different FC Mgmt MIB traps supported by this solution. The connUnitSensorStateChange trap is used as an example in the screen captions. The process for the other three traps is identical. The four traps are: connUnitEventTrap connUnitPortStatusChange connUnitSensorStateChange connUnitStatusChange To alter the trap definition: 1. From the NetView Console menu, select Options Trap Settings. This opens the Trap Settings panel, as shown in Figure 5.
2. In the top half of the panel (labeled Select an enterprise), highlight the fcmgmt enterprise. On the bottom half of the panel (labeled Select a trap), select the connUnitSensorStatusChange trap. Select Properties to open the Trap Properties panel, as shown in Figure 6.
3. In the Run this command when the trap is received field, enter the directory and name of the script, followed by $A $S $-1 $2 $4, which passes the required variables from the original trap. $A is the source of the trap, $S is the trap number, and the other variables are data presented by the device in the traps. The full string will be:
c:\custom\scripts\fcmgmttraps.bat $A $S $-1 $2 $4
4. In the Run as field, select Hidden Application. This executes the script as a hidden application each time the trap is received. On some NetView instances, it has been found that the script does not execute when set to Hidden Application. If this is the case, the alternative option Console Application can be used. The Display the Trap Category as field is set to Only Log Event, so on receipt, the original unformatted FC Mgmt event is not displayed in the NetView event log, only the new formatted trap. Click OK.
To display the new trap definitions and verify that they have been loaded correctly: 1. From the NetView Console menu, select Options Trap Settings. This opens the Trap Settings panel, as shown in Figure 7.
2. In the top half of the panel (labeled Select an Enterprise), highlight the NetView entry. This opens the list of defined NetView traps. Scroll down to the SAN_Environment trap and click Properties to display the details, as shown in Figure 8.
10
To enable the event to be formatted and displayed on the Tivoli Enterprise Console server, the event class definitions for the events in the san.baroc file found in the scripts directory need to be loaded into the Tivoli Enterprise Console database. Details about how to load a baroc file can be found in Chapter 10, Tivoli SAN Manager and Tivoli Enterprise Console, of the IBM Redbook, IBM Tivoli Storage Area Network Manager: A Practical Introduction, SG24-6848.
11
Figure 9 shows examples of all the events shown on a Tivoli Enterprise Console and also in the NetView event log on the Tivoli Storage Area Network Manager.
Figure 9 Events on Tivoli Enterprise Console and in the NetView event log
If the events are not displayed as expected, the scripts santest.bat and santest.pl in the scripts directory can be used in place of the fcmgmttraps scripts to test that NetView is calling the scripts correctly and is passing the expected variables. If the events are displayed in NetView and on Tivoli Enterprise Console, but do not contain the expected information, the fcmgmttrap.bat file can be executed from a Windows command prompt with the appropriate variables. Samples of the expected variable input can be found in the file testinput.txt. Some of the variables need to be customized to local values for the scripts to retrieve information correctly from the switches and display it in the formatted events. The information displayed by the NetView trap issued by the santest scripts can be used for this purpose.
12
Figure 10 NetView Event Details for FC Mgmt trap from QLogic SANBox2-16switch
The figure shows the Event Details in the NetView event log of a trap received from a QLogic SANBox2-16. Double-click the event in the log to get this view. It is shown unformatted because NetView does not recognize the event. The difference was found in the Enterprise number used by QLogic, which was 1.3.6.1.4.824.1.6. To create the correct set of trap definitions, the addtrap commands generated by the running the mib2trap command against the v3_0FA.mib file had to be edited to specify this new enterprise number before being executed. A new enterprise name of qlogicfcmgmt was used. All references in the batch file generated by the mib2trap command to fcmgmt were changed to qlogicfcmgmt, and the enterprise number was changed from 1.3.6.1.3.94 to 1.3.6.1.4.824.1.6 to reflect the enterprise number under which the traps are issued. Example 4 shows the execution output of the edited batch file.
Example 4 Sample output of v3_0FA.bat edited to recognize QLogic events C:\Custom\scripts>v3_0fa.bat C:\Custom\scripts>C:\usr\OV\bin\addtrap -l connUnitStatusChange -g 6 -s 1 -n qlogicfcmgmt -i 1.3.6.1.4.824.1.6 -o A -c LOGONLY -t 0 -S 1 -f - -F "$E $G $S $# args: $*"
13
This solution was tested with a McData Sphereon 4500. The FC Mgmt MIB definition file with a revision number of 200105080000Z was used. This MIB file was in SNMP v2 format, and a copy can be found in the custom/scripts directory as fcmgmt.mib. This version of the FC Mgmt MIB has to be loaded into NetView using the loadmibv2 program, which is in the usr/ov/bin NetView installation directory. Because the MIB file is in SNMP v2 format, the mib2trap command cannot be used to create the addtrap commands to define the FC Mgmt traps to NetView. A batch file, fcmgmttrapdefsmcdata.bat, is included in the scripts directory containing the correct addtrap commands. After the fcmgmtmcdata.bat batch file has been executed, and the traps have been defined, the trap properties need to be modified similarly to the QLogic devices, as described in Triggering automatic execution on page 6. Two McData specific scripts are included, fcmgmttrapsmcdata.pl and fcmgmttrapsmcdata.bat, which are specific to the McData implementation of the FC Mgmt MIB. As a result, the script to be executed on receipt of an FC Mgmt trap by NetView is fmgmttrapsmcdata.bat. Because McData passes slightly different information in the traps, the details of variables passed on each script are slightly different. For connUnitEventTrap, connUnitPortStatusChange, and connUnitSensorStateChange, it is similar to as before:
c:\custom\scripts\fcmgmttrapsmcdata.bat $A $S $-1 $2 $4
14
Summary
This paper has shown how it is possible to enhance the Tivoli Storage Area Network Manager SAN management solution with real-time device health and availability alerting. This is an important component of an end-to-end monitoring solution for storage availability management. It enables failures which are not yet impacting application availability to be addressed before they can have an impact. Sending these events to a central point and displaying them on an event console such as the Tivoli Enterprise Console provides a single point for administrators to view storage events relating to the entire storage infrastructure. More significantly, this single view allows correlation between events to be performed, enabling more rapid identification of the root cause of failures, as well as reducing administrative effort in monitoring a heterogeneous multivendor storage environment. Figure 12 shows Tivoli Storage Area Network Manager events and the formatted FC Mgmt events as created by this solution displayed on a Tivoli Enterprise Console in conjunction with events from other applications.
Figure 12 Tivoli Storage Area Network Manager and formatted FC Mgmt events on Tivoli Enterprise Console
15
16
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.
17
Send us your comments in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an Internet note to: redbook@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California 95120-6099 U.S.A.
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:
IBM ibm.com NetView Redbooks Redbooks(logo) Tivoli Tivoli Enterprise Tivoli Enterprise Console TotalStorage
The following terms are trademarks of other companies: Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.
18