Home > OpsMgr > IBM Storage Management Pack For Microsoft System Center Operations Manager

IBM Storage Management Pack For Microsoft System Center Operations Manager

IBM has just released a new management pack for IBM storage system. The IBM Storage Management Pack for Microsoft System Center Operations Manager R2
(SCOM) is a set of software modules, or management packs, which allow you to access and
monitor IBM storage systems using the host‐based Microsoft SCOM interface.
The MP include:

  • IBM Storage SCOM‐control Utility (scomu.cmd) – a stand‐alone command‐line
    interface (CLI) tool for configuration and diagnostics
  • IBM System Storage® DS8000® series management pack
  • IBM Storwize® V7000 management pack
  • IBM System Storage SAN Volume Controller (SVC) management pack
  • IBM XIV® Storage System management pack.

The MP supports the following IBM storage products, and can detect these products over IPv4 connections only.

Storage product Supported version(s)
IBM System Storage DS8000 series 5.4.3, 5.5.1, 5.6.0
IBM DS Open API (DS CIM agent) Embedded DS CIM agent 5.4.3, 5.5.1,5.6.0
Proxy DS CIM agent 5.4.0*
IBM System Storage SAN Volume
Controller (SVC)
5.1.0, 6.1.0
IBM System Storage Storwize V7000 6.1.0
IBM XIV Storage System

10.2.2

This MP can be download from here.

 

IBM XIV® Storage System management pack

Action that must be taken after the import of the MP.

Since we are monitoring XIV Storage through one of our windows server, in my case Operations Manager Server, we need to override the discovery “XIV System Discovery” to allow it to run only on the server where we installed the management pack and tools. another important tip is to change the discovery interval from 1800 (30 minutes) to 86400 (24 hours).

Advertisements
Categories: OpsMgr Tags:
  1. 16/02/2011 at 11:48 PM

    Hey Kobi,

    Have you ever installed this MP? I did today and found some pretty big issues. I will be doing a write up on my blog soon. I am hoping to get a meeting with the developers of this MP from IBM.

    I would tell people, who may want to use this MP, to be very careful and if just monitoring XIV, disable the discovery and over ride enable it for the server with the python scripts. I am thinking the discovery can be disabled all together, because XIV has an embedded OS and I believe, have not looked, that a script runs remotely to pull the config data from the XIV host.

    If you leave the discovery enabled (runs every 30 minutes – hello config churn!), then any agent without the python scripts will throw a nice warning in the SCOM console saying path not found for module…very nice.

    Regards,
    Blake

    • 18/02/2011 at 8:29 AM

      Hi Blake,

      Yes i use this MP.
      i noticed the discovery rule , and (as always) i changed the interval to, at least, one day (86400 secs).

      I don’t remember any warnings about “path not found” but i will take a look at this again after the weekend.

      Thanks for the comment,

      Kobi

      • 23/02/2011 at 1:47 PM

        Hi Blake,

        Since we are monitoring XIV Storage through one of our windows server, in my case Operations Manager Server, we need to override the discovery “XIV System Discovery” to allow it to run only on the server where we installed the management pack and tools. another important tip is to change the discovery interval from 1800 (30 minutes) to 86400 (24 hours).

  2. Thai
    25/10/2011 at 12:20 AM

    IBM Storage Management Pack & Monitoring IBM SVC???

    Has anyone used this MP to monitoring an SVC? I’m having issues with connection

    Example Syntax:
    scomu.cmd –add -t svc –ip 192.0.2.10 –authmode publickey –username usr3 –certpath c:/svc.cert

    <>
    scomu.cmd –add -t svc –ip 192.0.2.10 –authmod publickey –username admin –certpath c:\admin.ppk
    <<
    >>
    Connecting to the device …
    The conneciton to the device could not be established. Checking the input and try again.

    Questions
    1. svc.cert??? > What is this? I used the .ppk file that we created with puttygen and also that we use to access the svc with putty for but that key ends with .ppk not .cert
    2. account??? > I see some instructions that say svc v6.1.0 or earlier require the account be named “admin” What other settings do you need? Role?? > Monitor? (we used monitor) Authenitcation Mode? > local? remote? (we used local)
    3. no password? > why doesn’t the example have –password #$#$@ does it have to be a blank password?

    Can anyone help.

    Thx,
    Thai

  3. 12/03/2012 at 1:18 PM

    The instructions for the V7000 are exactly the same and just as ambiguous. The outputs of puttygen are a private/public key pair. Have no idea what they mean by CERT file.

  4. 12/03/2012 at 3:27 PM

    Okay!!! Figured it all out for Storwize V7000.

    1. Generate a private\public key pair (SSH-2 RSA) using puttygen.exe. You will end up with a PPK and a PUB when saving the public key and the private key. On the puttgen.exe menu select “Export OpenSSH key”. Do not use a passphrase. Export your private key with a .CERT file extention.

    2. Create a user “admin” through the WEB administration console and upload the public key file (PUB) against the user. I am not sure which role group the user should be a member of, but in our scenario it has highest privileges.

    3. As a verification step use putty.exe to open up an SSH command session to the V7000 using the user name “admin” and the private key PPK file. (Specify the PPK file on Connection-> SSH -> Auth -> Private key file for authentication) You should be able to open up a secure session.

    4. Follow the scomu.cmd instructions and specify the CERT file created in step 1. It should now connect with no problems.

    In retrospect if you now read the SCOM MP installation instructions, they make a lot more sense.

  5. Thai Bui
    13/03/2012 at 12:36 AM

    Here is what I found out.

    We don’t need to name the account “Admin” unless your IBM SVC is older than version 6.1.0.0 We created an account called “monitoring” and part of the Monitor Group.

    we also don’t need to rename the .ppk file to .CERT. That was the confusing part because .CERT isn’t an actual suffix. .ppk or .pub

    Basically
    1. Use Puttygen.exe to generate the .pub and .ppk file. Upload the .pub to the “Monitoring” account in the SVC.
    2. Open up the .ppk file in Puttygen and do like wayne said > Conversions > Export Open SSH key. Now use this key as the key in the command.
    3. On the SCOM server type.
    scomu.cmd –add -t svc –ip 10.10.10.10 –authmod publickey –username monitoring –certpath C:\IBM\Monitoring_OpenSSH.ppk –debug

    It worked but what we noticed is that it was kind of useless for the SVC monitoring. It doesn’t show error events on SVC. Just informational so you can’t have it alert on error events. Also if you click on any of the events for details it may take up to 15-20mins to enumerate the details. I was told that this is because it is hashing the entire event log.

    Hopefully the next version does grab more data on error/critial/warning events for the IBM SVC.

    I think only the XIV has full capabilities and allows you to see Critical events for alerting.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: