Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Storage Manager (STM) > Storage Manager (STM) Documentation > SRM Profiler Administrator Guide > Appendices > Configure storage arrays > IBM SVC V7000 provider

IBM SVC V7000 provider

Updated: June 16, 2017

This information is provided 'as-is' as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor's SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you.

The IBM SAN Volume Controller (SVC) SMI Provider is embedded in the Management Console software.

Older versions of SVC have another CIMOM embedded on the Management Console which is named as the proxy provider. IBM recommends not using this proxy CIMOM due to various performance considerations. SRM Profiler must use the CIMOM on the cluster.

All SVC's are sold with a Management Console in the rack on which the SVC GUI is installed to run the proxy server along with a number of other management tools. The Management Console itself is a CIM Client.

  1. The user can stop it and run it once again, and the profile the user has just created will be selected, then check the default profile check box that will make it a default profile.
  2. If the MAPI Profile is created successfully, then the executable will continue to run and output mailbox information to the command line.
  3. Wait for a few seconds to make sure it is collecting data, then the press Ctrl-C to stop the exe.
  4. Next, start the agent.

Troubleshoot IBM SVC Provider

Q: What is the minimum version of the provider supported?

A: Minimum version supported is 4.3.1

Q: What is the default login and password the cim agent on the cluster?


Login is administrator or superuser

Password is either passw0rd or l0destone

Q: What is the default port used by the cim agent?

A: By default the install uses HTTPS. If the user doesn't remember the ports/protocol used at install, the install directory contains a config file which will tell you: svcconsole\cimom\pegasus\cimserver_current.conf.

Q: Is it possible to upgrade the provider part alone?

A: No. The CIMOM is a core part of the SVC Console so you have to upgrade it as a part of your Console upgrade. The supported upgrade path is that you can run an SVC Console one rev up of the cluster code for migration purposes only. So you can upgrade the SVC Console to one rev up in order to upgrade the cluster, but IBM doesn't support long term management of mismatched SVC Console to Cluster versions.

SVC upgrade for cluster and console is a customer capable task; however, they should contact their IBM support representative to make sure they won't hit any of the known issues.

Q: For SVC 4.3.1 or above, provider exists on the cluster as well as on the host. Which one do I use?

A: From release 4.3.1 and above, there are multiple CIMOMs available; a) embedded CIMOMs in each cluster b) CIMOM on the management console (on the host where the SAN Volume Controller Console is running).

Use the CIMOM on the cluster. There are chances that the use of CIMOM on the management console slows down the SVC GUI operations. CIMOM on the cluster gives better performance than the other since it is embedded in the cluster itself.

Q: How do I find the IP for cluster?


  1. From the SVC GUI.
  2. From TestProvider utility or from Confirm Provider in the SRM Profiler GUI config page(only from SRM Profiler version 4.9.1 or greater)
  3. Connect to the CIMOM on the management Console .
  4. Enumerate CIM_ComputerSystem class. IP of the cluster is part of the identifier for the cluster instance.

Q: How do I monitor multiple clusters?

A: Each cluster has to be configured in SRM Profiler as a SVC device with the correct CIMOM IP and identifier.


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