OpStor

-

Multi-Vendor Storage Management

Monitoring and Management of IBM DS3000 / DS4000 / DS5000 / IBM FastT series storage systems

OpStor provides monitoring and management of IBM DS3000 / DS4000 / DS5000 / IBM FastT series storage systems

Models Supported

  • IBM DS3200
  • IBM DS3300
  • IBM DS3400
  • IBM DS3500
  • IBM DS4000
  • IBM DS4100
  • IBM DS4200
  • IBM DS4300
  • IBM DS4400
  • IBM DS4500
  • IBM DS4700
  • IBM DS4800
  • IBM DS5000 series
  • IBM FastT series
Features supported
Inventory Details Logical Details Monitors Report Details
  • Raid Controllers
  • Raid Controller Ports
  • Disk Drives
  • Enclosure Component Health details
  • Volumes
  • Volume Groups
  • LUN Mappings
  • Host Groups
  • Raid Status
  • Raid Port status
  • Volume status
  • Volume Group status
  • Disk Drive status
  • Capacity Summary
  • Availability
  • Controller statistics
  • Volume statistics
  • Array statistics
Prerequisites for monitoring IBM DS3000 / DS4000 / DS5000 / IBM FastT Arrays
  • OpStor uses command line utility SMcli available as part of IBM DS3000 / IBM DS4000 / DS5000 / IBM FastT Storage Manager
  • SMcli should be installed in the server where OpStor is installed.
  • Include the directory containing SMcli.exe in the PATH system environment variable by going into My Computer -> Properties -> Advanced -> Environmental Variables

    a) For IBM DS3000/DS4000/DS5000 series
    ------------------------------
    Windows : C:\Program Files\IBM_DS4000\client\
    Linux / Unix : /opt/IBM_DS4000/client/

    b) For IBM FASTt series
    ---------------------------
    Windows : C:\Program Files\IBMFastT\client\
    Linux / Unix : /opt/IBMFastT/client/

  • Restart OpStor server for the latest PATH settings to take effect.
  • Ensure thatthe OpStor installed server and the Storage system are connected via Fibre Channel.
SMcli commands to check IBM DS3000 / IBM DS4000 / DS5000 / FastT Array response

OpStor uses command line utility SMcli to fetch IBMDS3000 / IBM DS4000 / DS5000 / IBM FastT Array details

  • Ensure SMcli is set in the system PATH where OpStor is installed
  • Open a command prompt and go to <OpStor Install Dir> and execute the following commands

    SMcli 192.168.1.1 -c "show storagesubsystem profile;"
    SMcli 192.168.1.1 -c "show storagearray profile;"

    where 192.168.1.1 - is the Name of the Storage Subsystem
  • The following response must be got for any one of the above commands with any of the below strings in the command output

    PROFILE FOR STORAGE SUBSYSTEM

    PROFILE FOR STORAGE ARRAY
  • This ensures that device is properly responding for the SMcli commands.
SMcli commands to check Performance monitoring of IBM DS3000 / DS4000 / DS5000 / FastT Arrays

OpStor uses following SMcli commands to fetch performance statistics from IBM DS3000 / DS4000 / DS5000 / IBM FastT Arrays

  • Ensure SMcli is set in the system PATH where OpStor is installed
  • Open a command prompt and go to <OpStor Install Dir> and execute the following commands

SET 1 :

  1. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; show allLogicalDrives performanceStats;”
  2. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; show allVolumes performanceStats;”
  3. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; show storageSubsystem performanceStats;”
  4. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; show storageArray performanceStats;
  5. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storageSubsystem performanceStats file=\\"fileName.txt\\\”;”
  6. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storageArray performanceStats file=\\\"fileName.txt\\”;”
  7. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storagesubsystem performanceStats file=\\\"fileName.txt\\”;”
  8. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storageSubsystem performanceStats file=fileName.txt;”
  9. SMcli -e <IP Address 1> <IP Address 2> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storageArray performanceStats file=fileName.txt;”

Where <IP Address 1> and <IP Address 2> - are the two storage controller IP Addresses

SET 2 :

  1. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; show allLogicalDrives performanceStats;”
  2. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; show allVolumes performanceStats;”
  3. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; show storageSubsystem performanceStats;”
  4. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; show storageArray performanceStats;
  5. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storageSubsystem performanceStats file=\\"fileName.txt\\\”;”
  6. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storageArray performanceStats file=\\\"fileName.txt\\”;”
  7. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storagesubsystem performanceStats file=\\\"fileName.txt\\”;”
  8. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storageSubsystem performanceStats file=fileName.txt;”
  9. SMcli <IP Address> -c "set session performanceMonitorInterval=60 performanceMonitorIterations=1; save storageArray performanceStats file=fileName.txt;”

where <IP Address> - is the IP Address of any of the storage controller

  • This ensures that device performance statistics are properly responding for the SMcli commands
Steps to add IBM DS3000 / DS4000 / DS5000 / IBM FastT in OpStor
  • Navigate to Admin Tab --> Manage Storage Devices link in OpStor client
  • Provide IP Address of IBM Storage system
  • Choose the Device Type as 'RAID'
  • Choose the Vendor as 'LSI'
  • Leave the Username, Password and Comunity as blank
  • If needed, change the Timeout value (default is 5 seconds)
  • Click on Add Device.
  • Repeat the above procedure to add second raid controller, if present.

Note : If the Ping facility is disabled for the device, then please uncheck 'Ping the given IP' field.
Note : In case of non discovery of the device, please follow the troubleshooting tips displayed in the webclient and try re-adding the device.