Sunday, August 28, 2011

IBM Storage MP for XIV

This blog describes how to configure the Management Pack (MP) Integration for IBM XIV Storage.

In this guide I assume that you'd like to configure (more or less) failover. You would not have failover if you decide to do the steps below on only one Management Server.

1                  Prerequisites

·         Microsoft System Center Operations Manager 2007 R2

·         XIV-User to connect to XIV (Read Only role is enough as long as it is enough to alert for mirroring problems through alert rule instead of alert monitor.)

·        Source File from IBM (ftp://public.dhe.ibm.com/storage/XIV/IBM_Storage_MP_for_SCOM)

2                  Installation

These steps are only necessary during the first-time setup or when an additional Management Server has been added to the Management Group!

2.1             Install the CLI components

Install the integration on each Management Server and on the Root Management Server too. For this simply execute IBM_Storage_MP_for_SCOM-windows-<architecture>-1.1.exe provided by IBM.

2.2             Import the Management Packs

Import the designated MPs from the following path:

C:\Program Files\IBM\Storage\Host\IBMStorageSCOM\mps

2.2.1        Import XIV Management Packs

To monitor XIV Storage the following MPs must be imported:

·         IBM.Storage.Common.mp

·         IBM.Storage.XIV.mp

3                  Configuration

3.1             Implement IBM XIV Storage

3.1.1        Configure IBM Storage SCOM-control Utility

These steps are only necessary every time when a new XIV should be added to the Management Group!

 

Add each XIV Management Interface to the configuration on each (Root) Management Server in the Management Group. For this execute the following command (one line) from the command line:

C:\Program Files\IBM\Storage\Host\IBMStorageSCOM\bin\scomu.cmd --add –t xiv --ip <IP_from_XIV_Interface> --username <XIV_Monitoring_User> --password <Password> --debug

 

There should be the following output  when the connection has been added successfully:

Connecting to the device ...

1 IBM XIV Storage System is found.

device ID: <XIV_Id>, code level: <XIV_Code>

 

The connection is OK.

Trying to add the connection.

New connection is added.

 

Note 1: it is strongly recommended to add each of the interfaces to the configuration. To do this, the command from above has to be executed for each IP address!

 

Note 2: each XIV (with all management interfaces) needs to be configured on each Management Server and on the Root Management Server in the Management Group to enable MS failover!

3.1.2        Configure SCOM Management Pack

These steps are only necessary during the first-time setup!

 

Create the following overrides for the discovery “XIV System Discovery”.

3.1.2.1    Disable the discovery for Agents

 

1.    In the Operations Console go to Authoring, Management Pack Objects, Object Discoveries and search for XIV System Discovery.

2.    Right-click XIV System Discovery and select Overrides > Override the Object Discovery > For all objects of another class…

3.    Select Agent from the target list.

4.    Enable the Enabled override and change the Override Value to False.

5.    Create a new Management Pack for Overrides and call it IBM Storage Overrides.

6.    Apply the changes to the newly created MP.

3.1.2.2    Change the default interval

1.    Right-click XIV System Discovery and select Overrides > Override the Object Discovery > For all objects of class: Windows Server

2.    Enable the IntervalSeconds override, change the Override Value to 86400 (= 24h).

Note: you can change the value to any other that you prefer. Maybe it is a good approach to change the value temporary to (for instance) 60sec to speed up the first time discovery. If so you should not forget to change the value afterwards!

3.    Apply the changes to the MP IBM Storage Overrides created in chapter 5.2.1 step 5.

4                  Monitoring

4.1             Monitoring IBM XIV Storage

4.1.1        Rules

There are two rules for XIV event monitoring. Each of these rules polls the XIV every 600sec (default).

4.1.1.1    XIV Alert Rule

For XIV systems, in addition to alerts generated for health changes, the listed alerts also notify you about critical system events, which are classified by two different severity levels: Critical and Warning.

4.1.1.2    XIV Event Rule

For XIV systems, all event levels are displayed: Information, Error, and Warning

4.1.2        Monitors

There are several monitors for the following XIV components. Each of this monitors polls the XIV every 300sec (default).

4.1.2.1    Logical Components

·         Cluster State

·         Disk State

·         Fibre Channel Port State

·         Host State

·         IP Interface State

·         iSCSI Port State

·         Module State

4.1.2.2    Physical Components

 

·         Host Mapping

·         Mirroring State (Monitoring User must have Administrator privileges on XIV)

·         Storage Pool State

·         XIV System State

·         Volume State

5                  Troubleshooting

5.1             Trace

The IBM CLI Integration has some tracing features.

 

Use the following command in the command line to enable the tracing (in this example for XIV):

scomu.cmd --loglevel -t xiv TRACE

 

Use the following command in the command line to disable the tracing (in this example for XIV):

scomu.cmd --loglevel -t xiv NOTSET

5.2             Logging

Find the following log file on each Management Server that is running the IBM Integration (in this example for XIV):

C:\Program Files\IBM\Storage\Host\IBMStorageSCOM\log\scom_xiv.log

5.3             Event Collection Problems

Check if the following folder exists and contains files if there are no events in the Event View

C:\Documents and Settings\Default User\Application Data\Python-Eggs

5.4             Trace SCOM

1.    Start Command Line

2.    Change to %ProgramFiles%\System Center Operations Manager 2007\Tools

3.    Stop Tracing by StopTracing.cmd

4.    Start Tracing by StartTracing.cmd VER

5.    Wait until the workflow has been fired again (maybe it makes sense to override the interval temporary)

6.    Stop Tracing by StopTracing.cmd

7.    Format the Trace by FormatTracing.CMD; an explorer window opens.

8.    Open the file TracingGuidsNative.log

9.    Search for xpyv.exe to find all workflows running the CLI

 
All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.

0 Comments:

Post a Comment