Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM: Enable a Dell PowerVault, IBM DS3xxx, DS4xxx, DS5xxx, LSI or NetApp E-Series array

SRM: Enable a Dell PowerVault, IBM DS3xxx, DS4xxx, DS5xxx, LSI or NetApp E-Series array

Update: 11/1/16

Overview

The article contains information on enabling the LSI SMI-S Provider so that Dell PowerVault, IBM DS3xxx, DS4xxx, DS5xxx, LSI or NetApp E-Series arrays can be monitored by SRM.

For more information, please consult the documentation supplied with your array, or contact your vendor.

Environment

  • SRM 6.0+

Credentials required to add the array 

Ensure you have the following information before adding the provider to SRM

  • IP address or hostname for the array.
  • Provider username.
  • Provider password.
  • Protocol. The default is HTTPS.
  • HTTP port. The default is 5988.
  • HTTPS port. The default is 5989.
  • Interop namespace. The default is: /interop
  • Array namespace. The default is:

/root/IsiArray13

/root/DCIM/MDStorageArray13 if using the Dell 10.34 provider

/root/netApp/santricity if using the NetApp E-Series 10.34 provider

Enable the provider

Before you begin

Before you configure the LSI provider, obtain the following pieces of information about your array.

  • Controller IP Addresses
  • Array/Storage Subsystem Identifier: WWN

    For information on how to obtain the WWN, see Common Array Manager

  • NetApp user account. See Registering with NetApp below.

Register with NetApp

NetApp requires registration and logon before you can access and download the provider. NetApp provides "guest" access so you do not have to be a NetApp customer.

NetApp registration link:

http://support.netapp.com/eservice/public/now.do

If you do not want to register as a NetApp customer, choose the "Guest" option in Step 2.

Serial # is not required.

Download an LSI provider

The download links are located on the NetApp support site. You will need an account to access the download link.

Provider (Eagle 5) downloads are located at: http://support.netapp.com/NOW/apbu/oemcp/protcd/

After logging in to the site, click the SMI-S Providers download link.

SRM-NetApp-E-series-LSI-Provider_02.png

Install the provider (Eagle 2) in Windows or Linux

Windows

  1. Double-click the installer.

  2. Click Next at the Welcome screen.
  3. Accept the License Agreement, and then click Next.
  4. Click Install.


     
  5. Add the IP addresses for the Array Controllers. Save and close Notepad.

  6. Click Finish at the InstallShield Wizard Completed screen.

Linux

  1. Untar the lsi_array_xx.xx.xx.xx.tar file

  2. Execute rpm -i lsi_array_xx.xx.xx.xx.rpm.

Adding a SAN (Eagle 2) in Windows or Linux

Windows

  1. Run the ArrayManagementUtility.exe that came with the SMI-S installation file
    • Use the IP where the SMI-S provider is installed.
    • Use the defaults for the CIMOM Username, Password, and Port.
  2. Enter to Add Array.
  3. Enter the array IP or DNS name.
  4. Enter n to not set a storage array password.

Linux

  1. Edit the /opt/lsi/sbma/data/ArrayHosts.txt file.
  2. Enter the IP address of each array, one per line.
  3. Stop the cimserver with /opt/lsi/pegasus/bin/cimserver-s
  4. Start the cimserver with /opt/lsi/pegasus/bin/cimserver start

Install a legacy provider (Pre-Eagle 2) in Windows or Linux

Windows

  1. Double click the installer.

  2. Click Next at the Introduction screen.
  3. Accept the License Agreement, Click Next.

  4. Choose the Install location, Click Next.

  5. Click Install at the Pre-Installation Summary screen if the summary is correct.

  6. You should see the following screenshot:

  7. Add the IP addresses for the Array Controllers. Click OK.

  8. Click Done at the Install Complete screen.

Linux

  1. Untar the Linux_Installer_xx.xx.xx.xx.tar file.

  2. Execute the install executable.

Add a SAN (Pre-Eagle 2) in Windows, Linux

Windows

  1. Run the <install directory>\SMI_SProvider\bin\ProviderUtil.bat script.
  2. Use the defaults for the CIMOM Username, Password, and Port.
  3. Type 1 for addDevice.
  4. Type the array IP or DNS name.
  5. Type the Array Password.

Linux

  1. Run the /usr/engenio/SMI_SProvider/bin/ProviderUtil script.
  2. Enter the default username, password and Port.

    username - must be a valid user on the local system.

  3. Enter Add for adding a device.
  4. Enter the IP or DNS name.
  5. Enter array password.

FAQ - LSI provider (Eagle 2)

Q: What is the default username/password?

A: admin/admin

Q: What is the default namespace?

A: /root/lsiarray13

Q: Where are the log files located?

A: To enable logging, do the following:

Changes to the tracing level requires a restart of the provider to take effect.

  1. Go to the directory where SMI-S Provider is stored:
    • For a Windows operating system, the directory is C:\LSI\.
    • For a UNIX-based operating system, the directory is /opt/lsi/sbma/data/.
  2. Edit the providerTraceLog.properties file.
    Remove the pound sign (#) from the lines containing FILE, LEVEL, and EVENTS.
  3. Save the file, and exit the text editor.
  4. Stop and start the CIM server by using the specific location and name.

Q: How do I change the ports that the provider binds to?

A: Do the following:

  1. Go to the <installPath>\bin directory.
    • For a Windows operating system, the directory is c:\lsi\pegasus28\pegasus\bin
    • For a UNIX-based operating system, the directory is /opt/pegasus28/pegasus/bin/
  2. Run the following commands:
    • cimconfig -s httpPort=<newHttpPort> -p
    • cimconfig -s httpsPort=<newHttpsPort> -p

Q: I keep getting a "Storage array added successfully", but instead of returning the UUID, it returns a "index string out of bounds".

A: Double check the IP address. This is the provider's way of saying, "this host is pingable, but it's not a storage array".

Q: Array does not appear to be added to the provider when editing the arrayhosts.txt file, what should I do?

A: See section above "Adding a SAN" under the "Provider Version Eagle 2 and above" section.

FAQ - LSI legacy provider (pre-Eagle 2)

Q: What are the ports that LSI provider listens on?

A: 5988, 5989 and 2463.
The port 2463 is used to set RPC sessions to the storage controller.

Q: How do I change the port the provider listens on?

A: On the machine running the Provider do the following:

  1. Open the portInfo.properties located (by default):

    C:\Program Files\EngenioProvider\SMI_SProvider\bin

  2. Change the entry CIM-XML=5988 to the desired port which has no conflicts.
  3. Save the changes.
  4. Restart the Engenio SMI-S Provider Server service.

Q: How do I enable logging for debugging the provider, and where is the log located?

A: To enable logging, do the following:

Note: Changes to the tracing level requires a restart of the provider to take effect.

The SMISProvider.log file is created if you have debug tracing enabled. The file could be located in any of the following locations:

  • \Program Files\EngenioProvider\SMI_SProvider\bin\
  • \Windows\System32\
  • \EngenioProvider\SMI_SProvider\bin\

If you are not able to find the SMISProvider.log file then perform the following to enable debug tracing and duplicate the issue so the SMISProvider.log file is created:

  1. Stop the Provider.
  2. Edit the providerTraceLog.properties file located in [Installation Drive]\Program Files\EngenioProvider\SMI_SProvider\bin\
  3. Remove the "#" symbol from the last line of the code, which looks like:
    • #log4j.logger.ProviderLog=DEBUG, File
  4. The line of code should now look like: log4j.logger.ProviderLog=DEBUG, File
  5. Save the file
  6. Restart the Provider

On UNIX: the trace log is in the {install location}/SMI_SProvider/bin directory.

Q: Why, on a minute by minute basis, am I seeing some perf stats as 0.0?

A: Because LSI only polls their arrays on a 10 minute basis. It is too taxing on the array to gather more frequently than that.

Q: How many arrays can be monitored at one time?

A: LSI recommends no more than 4 arrays at once.

The following is an excerpt from their release notes:

"The maximum configuration recommended for the SMI provider is either 3 storage systems or a total of 512 volumes, whichever is reached first. If the limits are exceeded, the provider may not be able to generate performance statistics."

Q: What performance information is available from the LSI array and how is it obtained?

A: See below:

  • Array Performance: smi-s
  • Controller Performance: calculated by Storage Manager. Aggregate the performance values for all the LUNs that belong to specific controller.
  • LUN Performance: smi-s
  • Disk Performance: API. Currently using the Crystal (10.10) version API. In order to ascertain disk performance from an array, the controller firmware minimum version must also be Crystal release (7.10). The 10.10 version of the API was built against jdk 1.4, which matches with the jdk used in the Storage Manager agent at the time of the 4.8 release. The 10.15 (Crystal maintenance) and 10.30 (Emerald) release was compiled against jdk 1.5, and is the reason it is not used.
  • Volume Group Performance: calculated by Storage Manager. Aggregate the performance values for all the LUNs that belong to specific raid group.

Q: Why is disk performance not showing up?

A: The controller firmware must be version 7.10 or greater. We use the API to gather the data, and there is a dependency on the controller firmware to be greater than 7.10. A trap is sent to Storage Manager if the minimum version is not met.

You might hear the controller versions referred to by name, which are:

  • Chromium (no disk perf avail, only in this list to show firmware name)
  • Crystal
  • Crystal maintenance
  • Emerald (which is the xbb2)
  • Crystal/Emerald 4Q08 Maintenance
  • Aurora (2009)
  • 7.60 - Allegheny (2009)
  • Flint (2009)

Q: Is any configuration required to get disk performance to show up?

A: No configuration required on the agent nor from Storage Manager gui. The disk performance uses LSI's API (symsdk.jar) in conjunction with the smi-s provider to ascertain the disk performance. The API requires the IP addresses of the controllers. The IP addresses are obtained from the smi-s provider; therefore, you must have the smi-s settings configured correctly.

Q: How do I get the LSI provider to work on Solaris?

A: For Solaris 10, you will probably need to change the port the lsi provider listens on, as solaris 10 ships w/ a cimom enabled by default that is already bound to 5988.

For solaris 10 do the following:

  1. Install provider following instructions
  2. Stop the provider (/opt/engenio/SMI_SProvider/bin/launch stop)
  3. Change the ports in /opt/engenio/SMI_SProvider/bin/portInfo.properties to something other than 5988 and 5989. CIM-XML is listed twice, so be sure to change both
  4. Check that slp is running (ps -eaf | grep slp)
    1. should see /usr/java/jre/bin/java -Xmx128m -classpath /usr/share/lib/slp/slpd.jar
    2. can also check the slp port is bound to by doing netstat -an | grep 427. Should see port 427 in a listen state
  5. Start slp if not running (/etc/init.d/slpd start)

    slp requires that the /etc/inet/slp.conf file exists. If the file does not exist, then copy the slp.conf.example file (cp /etc/inet/slp.conf.example /etc/inet/slp.conf)

  6. Start the provider (/opt/engenio/SMI_SProvider/bin/launch start)

For solaris 8 or 9, there should be no need to change provider ports. No cimmon should be running on port 5988. Users should still verify the port is not in use by using netstat command netstat -an | grep 5988.

Q: Provider still doesn't work on Solaris, what logs can I look at?

A: You can edit the /opt/engenio/SMI_SProvider/bin/launch script and change the PROVIDER_OUT=/dev/null to PROVIDER_OUT=$PROVIDER_HOME/SMI_SProvider/bin/provider_launch.log

You can then view the provider_launch.log and SMISProvider.log (found in /opt/engenio/SMI_SProvider/bin) to further diagnose issue

PROVIDER_OUT=$PROVIDER_HOME/SMI_SProvider/bin/provider_launch.log

Q: What is the default username/password for provider running on Solaris?

A: You must use a valid username/password that is used to login to the system

Q: How do I add an array to the provider on Solaris?

A: Run /opt/engenio/SMI_SProvider/bin/ProviderUtil

You must provide ip address of the controller, and also a valid username/password that is used to login to the system

Q: Can you use the Windows installer on a 64-bit Windows OS?

A: No. According to the LSI Representative, this will be supported in the next generation of the provider (information is as of 2/6/2009)

Q: How do I obtain the Support Bundle Data from LSI array?

A: To obtain the Support Bundle Data from Santricity/Storage Manager:

  1. From the array management window (AMW), select the Advance drop down menu
  2. Choose Troubleshooting and then Collect All Support Data.
  3. From this screen, specify the location to save.
  4. Click Start,

Q: What files are needed to send a bug to LSI?

A: Any issues related to LSI provider, get the following:

  • Provider logs (See 'How do I enable logging for debugging the provider, and where is the log located' for log file location)
  • ArrayHosts.txt (located in C:\Program Files\EngenioProvider)
  • Support Data (See question 'How do I obtain the Support Bundle Data from LSI array')
  • LSI provider version info

CIMWorkshop

The LSI Provider has CIMWorkshop enabled, located at:

C:\Program Files\EngenioProvider\wbemservices (by default).

Refer to Tools > CIMWorkshop for instructions on how to obtain the Array Identifier in CIMWorkshop.

SANtricity Storage Manager

  1. Log into SANtricity.

  2. Double click on the Storage Array name (You should be taken to the Logical / Physical View, like below).

  3. Right Click on the Storage Array name. Select View > Profile.

  4. Scroll down to Storage array worldwide name (ID) under Summary for All tab.

Common Array Manager

  1. Login to Common Array Manager and click on the Administration - Licensing section and note down the Array WWN as shown below:

  2. Remove the colons for providing the identifier within Storage Manager as shown below:

 

Disclaimer. Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

 

Last modified
11:22, 2 Nov 2016

Tags

Classifications

Public