Enhancing ibm tivoli san manager device availability alerting redp3821

Redbooks Paper
Steve Strutt

Enhancing IBM Tivoli SAN Manager
Device Availability Alerting

Introduction
This Redpaper outlines how it is possible to enhance the real-time alerting of the availability
status of SAN devices with the IBM® Tivoli® Storage Area Network Manager SAN
management solution. The approach outlined here uses the industry standard FC Mgmt MIB
implemented by most SAN devices to report device status information, irrespective of device
type or vendor. The FC Mgmt MIB was originally created for just this task, providing for the
reporting of device events, and monitoring and alerting on device and port status information,
device internal temperature, and the availability of power supplies and fans.

To minimize administrative effort, many organizations use event management consoles to
monitor and manage their whole IT infrastructure on an exception management basis.
Operations personnel can be alerted in real time to all issues relating to application
availability. This also enables the use of a single consistent approach to alert and event
management across the whole of IT, simplifying administration and reducing costs. The
exploitation of the FC Mgmt MIB for the reporting of status and events enables SAN device
availability information to be included as part of end-to-end application management. It helps
ensure storage and application availability and reduces the risk of application outages by
simplifying the job of storage administrators or operations personnel in monitoring and
maintaining SAN devices.

Accompanying scripts are provided to implement the features described in this paper. These
scripts can be downloaded (in a ZIP archive called custom.zip) from the following URL:
ftp://www.redbooks.ibm.com/redbooks/REDP3821/

Alternatively, you can go to the IBM Redbooks™ Web site at:
http://ibm.com/redbooks

Select Additional materials and open the directory that corresponds with the Redpaper form
number, REDP3821.

© Copyright IBM Corp. 2004. All rights reserved. ibm.com/redbooks 1

Tivoli Storage Area Network Manager and availability alerting
IBM Tivoli Storage Area Network Manager centralizes the management of a SAN fabric by
bringing SAN topology discovery, mapping, and availability alerting to a central point. SAN
topology is displayed on the SAN Manager console, which is updated in real time with the
availability of the SAN fabric network. In addition, it provides alerting of changes in SAN
topology and configuration through Simple Network Management Protocol (SNMP) traps and
Tivoli Enterprise™ Console events. These topology change events are an essential part of a
storage availability management solution. They enable administrators to identify changes that
might have an impact on applications and enable rapid identification of the cause of
application failures.

To ensure high availability, many devices include redundant components such as power
supplies and fans, because these electro-mechanical components have a relatively short life
compared to any internal electronics. The individual failure of these components will not
cause device failure, but will increase the exposure to the risk of further failures resulting in
complete device failure, causing a significant SAN failure and availability issue.

Currently, Tivoli Storage Area Network Manager alerts on the availability of the SAN fabric
and the up or down status of the devices of which the fabric comprises. It does not alert on
the health or availability status of individual SAN devices and internal components that are a
working part of the SAN fabric. Only if a device fails will Tivoli Storage Area Network Manager
alert that it has been removed from the fabric. Note that TSNAM does monitor the underlying
health of the Fibre Channel links to predict an impending hard failure of the data transmission
path. This function is the SAN Error Predictor doing Error Detection and Fault Isolation
(ED/FI). The addition of availability status alerting using the FC Mgmt MIB as outlined in this
paper enables the real-time detection of device failures or events that could impact the
availability of a device, but have not yet caused the device to fail. This is particularly critical
where redundant components are concerned.

Figure 1 shows the overall structure of this device availability alerting solution. IBM Tivoli
NetView® receives FC Mgmt MIB traps from devices and forwards these to Tivoli Storage
Area Network Manager and additionally sends formatted FC Mgmt MIB events as SNMP
traps to the NetView event log and as Tivoli Enterprise Console® events to the Tivoli
Enterprise Console. Tivoli Storage Area Network Manager monitors the fabric topology, using
the traps from NetView and in-band fabric events to trigger topology refreshes, and sends
fabric availability events to a Tivoli Enterprise Console and the NetView event log.

Topology/
NetView Configuration TSANM
Event Log events TEC event

FC Mgmt
FC Mgmt TEC event Tivoli
SNMP TSANM Enterprise
SAN FC Mgmt traps Console Console
Switches SNMP
traps Tivoli
NetView TSANM Windows 2000
Mgmt Server

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.

2 Enhancing IBM Tivoli SAN Manager Device Availability Alerting

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 Types of events
component

Storage device

Tape storage (3494, 359x) Device - Tape Availability

Disk storage (ESS, SVC, FAStT) Device - Disk Availability

SAN switches Device - SAN Availability

Storage application

Tivoli NetView Device - SAN Availability
Device FC Mgmt traps

Tivoli Storage Area Network Manager Storage Network Availability

Tivoli Storage Area Network Manager - Device - SAN Errors
SAN Error Predictor

Tivoli Storage Resource Manager LUNs Availability

File systems Availability, Utilization

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.

The alerting solution
The FC Mgmt MIB definition includes four SNMP traps to indicate significant device events or
a change in status of the device. The events and the information they impart are:
Device state and status: Online/Offline, OK/Warning/Failed
Environmental Sensors: Temperature, Power Supplies, Fans: OK/Warning/Failed
Port Status: Online/Offline, OK/Warning/Failure
Device Events: Internal device event details

The FC Mgmt MIB trap information, as received by NetView, is largely as integer values to
represent status information, not a textual description. In some cases, only the bare minimum
of information is passed in the trap and is insufficient to completely identify the failing
component or the severity of the event. To be useful, the integer values have to be converted
to readable text and additional information retrieved from the device to make an alert that is
easily readable and contains sufficient information to help determine the severity of the
problem. This solution performs these functions, interpreting the events and querying the
devices for more information to make the events more descriptive and useful.

A number of elements on the Tivoli Storage Area Network Manager management server are
used to implement this availability monitoring and alerting solution. As shown in Figure 1, the

Enhancing IBM Tivoli SAN Manager Device Availability Alerting 3

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.

Tivoli Storage Area
Network Manager
4. Execute monitor script
2. FC Mgmt
3. Trap
Trap
Lookup Tivoli Enterprise
Console
NetView
Tivoli
6. Issue Tivoli Enterprise
NetView
NetView Event Log
Console event and
new SNMP trap
1. FC Mgmt
Trap 5. FC Mgmt MIB
Queries

SAN Switch

Figure 2 Overview of the execution flow

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.


Configuring the solution
The following instructions show you the steps to configure NetView to provide detailed
alerting and monitoring using FC Mgmt MIB traps. We refer to the installation package that
you can download with this paper, SANenvmonitor.zip, or just “the package.”

Installing the executables
To install the SANenvmonitor.zip package, simply unzip it. It unzips to the directories
customscripts and custombin. This paper assumes that the package is installed on the C:
drive. Although any drive can be used, several scripts assume installation on the C drive;
therefore, if this is not the case, these scripts will need to be edited to reflect the actual
installation drive.

The package includes an open source version of the Perl interpreter that comes from the
Tivoli Framework installation CD. The executables for Perl are installed in the directory
C:custombin.

The path to the executables needs to be added to the Microsoft® Windows® PATH system
environment variable. Environment variables can be changed from the Control Panel by
selecting System Properties and clicking the Advanced tab. Figure 3 shows the addition of
the directory C:custombin to the path.

Figure 3 Edit the PATH environment variable

This paper assumes that the scripts and other executables required are installed in the
C:customscripts 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.

Loading the FC Mgmt MIB
For NetView to correctly query and interpret the contents of the FC Mgmt MIB on the
monitored devices, the MIB definitions need to be loaded into NetView.

To load the MIB definitions:
1. The MIB loader option is only available if the NetView advanced menus are activated. If
the advanced menus are not already available, from the NetView Console menu, select
Options → Advanced Menu. Stop and restart the console to activate the advanced
menus.
2. Then, from the NetView Console menu, select Tools → MIB → Loader SNMP V1. This
opens the MIB Loader panel, as shown in Figure 4.


Figure 4 NetView MIB Loader panel

3. Click Load. Browse to the directory where the FC Mgmt MIB was installed
(c:customscripts by default). Select the FC Mgmt MIB (v3_0FA.mib), and click Open to
load the MIB.

Triggering automatic execution
A native capability of NetView is to execute commands on the receipt of traps, passing details
of the received traps as variables when the command is executed. This ability is used to
execute the monitoring and alerting script on receipt of one of the FC Mgmt traps. The trap
definitions must be loaded into NetView for it to recognize the traps. Associated with this
definition is the command to be executed and the variables to be passed to it. When
configured, NetView will execute the script on receipt of an FC Mgmt MIB trap.

Most SAN devices now support the FC Mgmt or Fibre Alliance (FA) 3.0 MIB and typically a
copy of the MIB is supplied by the SAN device vendor. This solution assumes that the devices
being monitored support this version of the MIB. A sample copy, v3_0FA.mib, is included in
this package for use with the solution. To load the FC Mgmt trap definitions into NetView, the
definitions supplied in the MIB file need to be converted into NetView addtrap commands,
which are then executed to define the traps to NetView.

The NetView mib2trap command is executed to create a batch file containing NetView
addtrap commands to define the traps to NetView:
mib2trap c:customscriptsv3_0FA.mib c:customscriptsv3_0FA.bat

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:Customscripts>v3_0fa.bat

C:usrOVbinaddtrap -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:usrOVbinaddtrap -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: $*"
…………..

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.

Figure 5 NetView Trap Settings panel


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.

Figure 6 NetView Trap Properties for the connUnitSensorStatusChange trap

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:customscriptsfcmgmttraps.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.

Enabling devices to be monitored
Devices to be monitored must be configured to send FC Mgmt traps to NetView. Where the
monitor is implemented on the NetView instance used by Tivoli Storage Area Network
Manager, SAN switches will have already been configured to send their FC Mgmt events to
this instance of NetView, and further configuration is not required. Any other devices to be
monitored in this fashion must also be configured to route their FC Mgmt traps to NetView. In
addition to switches, this can include fibre-to-SCSI gateways, storage arrays, and other SAN
attached devices that also support the FC Mgmt MIB.

Configuration of trap forwarding on devices usually also includes the ability to set the devices’
SNMP community name. All devices must be configured to use the same SNMP community
name with read permissions to the FC Mgmt MIB variables. Make a note of this community
name, because it is used later in the configuration.


Configuring the monitor
A number of variables in the fcmgmttraps.pl script need editing to reflect local values. These
include:
$CommunityName: The SNMP community name used for read access to the FC Mgmt
MIB variables on the monitored devices.
$NV_PATH: NetView installation directory.
$TEC_PATH: Installation path of the monitor script and Tivoli Enterprise Console
configuration file.

By default, the script sends both an SNMP trap and Tivoli Enterprise Console event.
Depending on which event is needed, the script needs editing to specify whether or not to
issue the SNMP trap or Tivoli Enterprise Console event.

Displaying and formatting the events
The new events issued by this solution map directly to the corresponding FC Mgmt MIB traps:
SAN Event: connUnitEventTrap
SAN Port: connUnitPortStatusChange
SAN Environment: connUnitSensorStateChange
SAN State: connUnitStatusChange

Now, we show you how to configure NetView and Tivoli Enterprise Console to display these
new events in the NetView event log and Tivoli Enterprise Console in formatted and readable
text.

Displaying the event in NetView
To enable the new SNMP trap to be displayed in the NetView event log on the Tivoli Storage
Area Network Manager server, a new trap definition is used to display and format the event.
The definitions for these new traps are contained in the file fcmgmttrapdefs.bat in the scripts
directory. The new trap definitions are added to the traps already defined for NetView, using
high trap numbers to avoid conflict with existing trap definitions.
Executing the batch file will define the new traps to NetView so that they can be properly
displayed and formatted. Example 2 shows a sample execution of fcmgmttrapdefs.bat.

Example 2 Sample execution output of fcmgmttrapdefs.bat
C:customscripts>fcmgmttrapdefs

C:>C:usrOVbinaddtrap -l SAN_Environment -g 6 -s 99000001 -n NetView -i
1.3.6.1.4.1.2.6.3 -o A -c "Status Events" -t 0 -S 1 -f - -F $1

C:>C:usrOVbinaddtrap -l SAN_Event -g 6 -s 99000004 -n NetView -i 1.3.6.1.4.1.2.6.3 -o
A -c "Status Events" -t 0 -S 1 -f - -F $1
………………………………..


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.

Figure 7 Trap Settings panel for NetView enterprise

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.

Figure 8 Trap Properties panel


Displaying the event on Tivoli Enterprise Console
To sent the event to a Tivoli Enterprise Console, the tecad_nt.conf file in the scripts directory
needs to be modified to send events to the correct Tivoli Enterprise Console. The statements
shown in Example 3 need to be changed to point to the Tivoli Enterprise Console server and
port in your environment.

Example 3 Statements to modify in the tecad_nt.conf file
ServerLocation=sienna
ServerPort=5529

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.

Tivoli Enterprise Console event information
The information available in the FC Mgmt MIB about events, device availability, and status is
fully documented in the v3_0FA.mib file contained in the package. The following fields are
passed as part of the Tivoli Enterprise Console events:
SAN Environment
– UnitSensorName: Power Supply, Fan, Temperature Sensor
– UnitSensorStatus: OK, Failed, Warning
– UnitSensorMSG: More detailed information about sensor state
SAN Port
– Port State: Online, Offline, Bypassed
– Port Status: OK, Failed, Warning, Initializing, Bypassed, Not Participating
– PortHWStatus: Active, Failed, NoMedia, TxFault
SAN Event
– EventDesc: Description of the event
– EventSeverity: Severity
– EventRTime: Time of the event at the device
– EventType: Type of event
– EventIndex: Index to event in device event table
SAN State
– UnitState: Online, Offline
– UnitStatus: OK, Warning, Failed

Testing the final result
The original FC Mgmt traps issued by the devices are not displayed in the NetView event log,
because by default, they are “displayed” by NetView as Only Log Events and not written to
the event log. To test the solution, this can be changed in the Trap Properties panel to Status
Events so that they are displayed in the event log on receipt. It then becomes an easy job to
check that when an original FC Mgmt trap is received the corresponding SAN trap generated
by the script is also displayed. After it has been verified that the new traps are being correctly
issued and displayed, the display category can be changed back to Only Log Event.

If the script does not execute, and the new events issued when the execution mode of the
script in the trap properties is set to Hidden Application, the alternative option, Console
Application, can be used.


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.

QLogic SAN switches
When testing the solution, we found that the traps from Brocade switches and InRange
directors fully follow the trap definitions laid out in the FC Mgmt MIB 3.0 definitions and will
trigger execution of the monitor script. However, QLogic switches, such as the SANBox2-16
(also rebadged by InRange), issue FC Mgmt traps under a different “enterprise,” and a
modified set of trap definitions had to be loaded to trigger execution of the script. This is
shown in Figure 10.


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:Customscripts>v3_0fa.bat

C:Customscripts>C:usrOVbinaddtrap -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: $*"
………………

Setup and usage is the same as previously described.

McData directors and switches
Similarly, McData for their directors and switches use a variation of the standard FC Mgmt
MIB. In this case, both the MIB and the traps use a different enterprise to that used by the
“standard” FC Mgmt MIB. Figure 11 shows the traps generated with the default configuration.


Figure 11 McData FC Mgmt trap with no NetView definition loaded

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:customscriptsfcmgmttrapsmcdata.bat $A $S $-1 $2 “$4”

For connUnitEventTrap, it is:
c:customscriptsfcmgmttrapsmcdata.bat $A $S $-2 $2 “$4”


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


The team that wrote this Redpaper
Steve Strutt is a Certified IT Specialist in the U.K., working in Technical Sales Support. He
holds a bachelor's degree in Electronic Engineering and has more than 18 years of
experience in IBM storage and storage management tools from z/OS to open systems
storage. His areas of expertise include enterprise storage architecture, tape storage systems,
Tivoli Storage Manager, Storage Area Networking, and Storage Resource Management and
systems management.

Thanks to the following people for their invaluable contributions to this and the previous
edition of this Redpaper:

Charlotte Brooks
Emma Jacobs
International Technical Support Organization, San Jose Center

Elizabeth Barnes
International Technical Support Organization, Austin Center

Richard Hine
Tivoli Systems, U.K.


Notices

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

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

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

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

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

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

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

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

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

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

© Copyright IBM Corp. 2004. All rights reserved. 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® Redbooks™ Tivoli Enterprise™
ibm.com® Redbooks(logo) ™ Tivoli Enterprise Console®
NetView® Tivoli® 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.


Enhancing ibm tivoli san manager device availability alerting redp3821

Recomendados

Recomendados

Mais conteúdo relacionado

Destaque

Destaque (7)

Semelhante a Enhancing ibm tivoli san manager device availability alerting redp3821

Semelhante a Enhancing ibm tivoli san manager device availability alerting redp3821 (20)

Mais de Banking at Ho Chi Minh city

Mais de Banking at Ho Chi Minh city (20)

Último

Último (20)

Enhancing ibm tivoli san manager device availability alerting redp3821