Monitoring and Management of StorageTek / LSI Logic storage systems

OpStor provides monitoring and management of StorageTek / LSI Logic storage systems

Models Supported

• D Series
• B Series
• Flexline 200 Series
• Flexline 300 Series

Features supported

Prerequisites for monitoring StorageTek / LSI Logic Arrays

• OpStor uses command line utility (SMcli.exe) available as part of SANtricity Storage Manager Client installation
• Ensure that SMcli is installed in the server in which OpStor is installed
• Include the directory containing SMcli.exe in the PATH environment variable.
  • For Windows : C:\Program Files\SM8\client\
  • For Linux / Unix : /opt/SM8/client/
• Ensure that OpStor is restarted (shutdown & started) after including SMcli in the PATH for the latest changes to take effect
• Register OpStor server IP address as snmp trap destination.
• Ensure that, OpStor installed host and the Storage system has a Fibre Channel Connectivity.

SMcli commands to check StorageTek / LSI Array response

OpStor uses command line utility SMcli to fetch StorageTek / LSI 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 StorageTek / LSI Arrays

OpStor uses following SMcli commands to fetch performance statistics from IBM DS 4000 / 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 controllers.

• This ensures that device performance statistics are properly responding for the SMcli commands

Steps to add StorageTek / LSI Logic Array in OpStor

• Navigate to Admin Tab --> Manage Storage Devices link in OpStor client
• Provide IP Address of StorageTek / LSI 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.