Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Storage Resource Monitor (SRM) > SRM - Knowledgebase Articles > SRM: Enable a HP StorageWorks XP onboard provider

SRM: Enable a HP StorageWorks XP onboard provider

Updated: 11/1/16


This article provides information on enabling the HP StorageWorks XP array with onboard SMI-S provider for use with SRM. The embedded SMI-S provider is a component of Command View and runs as a service. It is automatically installed when Command View is installed in Typical mode.

For further information, contact your vendor or visit HP Customer Support.


  • SRM 6.2+

Credentials required to add the array

Ensure you have the following information:

  • IP address or hostname for the array.
  • Provider username. The default is administrator.
  • Provider password. The default is administrator.
  • 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/hitachi/smis.

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