Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Storage Manager (STM) > SRM Profiler Administrator Guide > Appendices > Configure storage arrays > IBM DS 6000 8000 or ESS provider

IBM DS 6000 8000 or ESS provider

Table of contents

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 correct IBM Provider to install is based on Model and Firmware.

For documentation and downloads, visit the IBM support site.

  • For any DS 6000, 8000 or ESS, install the IBM Provider.
  • For any DS 3k, 4k, or 5k array, install the LSI Provider

Troubleshoot IBM

The following section details FAQs for the IBM SMI-S Provider.

Q: Is IBM Shark supported?

A: Yes. Add it as an "IBM DS 6K/8K Series" device

Q: What is the default username/password for the IBM provider?

A: superuser / passw0rd

Q: What is service name for the IBM provider in windows?

A: "IBM System Storage CIM Agent for DS Open API x.y Pegasus Server", where x.y is the version.

Q: Where are the logs located?

A:

<install path>\logs

<install path>\pegasus\log

<install path>\pegasus\logs

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

A: <install path>\bin\dscimcli mkdev <ip> -type <ds|ess> -user <username> -password <password>

Example: dscimcli mkdev 192.168.0.1 -type ds -user superuser -password passw0rd

Note: the user and password combination are that of the Control Station

Q: How do I remove an array from the provider?

A: <install path>\bin\dscimcli rmdev <ip> -type <ds|ess>

Example: dscimcli rmdev 192.168.0.1 -type ds

Q: I try to add an array, but it fails with error 'Array is already added'?

A: The password for the Control Station user may be expired, which can be verified in the <install path>\pegasus\log\providerdebug.log. If expired, the password can be reset in the Control Station.

Q: Where can I find more usage details on the dscimcli command?

A: In the Reference Install guides at the IBM support site. There are install/ref guides for 5.2, 5.3, 5.4 versions of the provider

Q: What user/password do I use when configuring the array in SRM Profiler (in the monkey wrench page)?

A: Use the default username/password (superuser/passw0rd).

Other user-ids/passwords can be created using the dscimcli command. You can list what users are configured by doing 'lsuser'

Q: What username/password do I use when adding array to the provider?

A: The username/password used for the Control Station (similar to how there is username/password to Unisphere). The user should know this information

Q: In what release did the CIM Agent become embedded in the HMC (Hardware Management Console)?

A: Starting with Release 2.4 (Bundle 6.2.400.64) of the DS8000, the CIM agent was embedded into the HMC. Up to Release 4 (Bundle 62.0.175.0) by default, it comes disabled

Q: How does the embedded CIM Agent get Enabled?

A: In order to use the CIM agent, the customer must contact IBM support to have the CIM agent enabled.

Q: How does the embedded CIM Agent get configured?

A: The Customer must download the dscimcli tool and install it on a separate server, i.e. the TPC server or laptop, to configure the CIM agent. dscimcli is a small utility that runs on the same platforms that the proxy CIM agent runs on, but does not consume a lot of CPU or memory, so it should be able to run on any reasonable server or laptop. You can download the dscimcli tool at the download site for the version of CIM agent that is running on the HMC. Please refer to the install documentation for more details.

Q: How do I enable the embedded CIM agent on the HMC?

A: For releases prior to DS8000 release 4.1, the CIM agent is NOT automatically enabled. You must enable the CIM agent on the HMC before you can use it. For DS8000 release 4.1 and later, the CIM agent is enabled by default. You do not have to enable the CIM agent unless it has been disabled.

Enabling DS8000 CIM Agent on DS8000 bundles 6.2.400.64, 6.2.400.66, 6.2.400.76, and 6.2.410.30 requires assistance from IBM Technical Support.

Perform the following steps to enable the HMC CIM agent:

  1. From the HMC Welcome page, click HMC Management. The HMC Management window is displayed.
  2. Click Start/Stop CIM Agent. The HMC CIM Agent window is displayed with the current state of the CIM agent.
  3. Select Start CIM Agent and click Apply. The CIM agent is started and the state is updated.

Q: How do I configure the embedded CIM agent for HMC?

A: For DS8000 release 4.0 and earlier, the CIM agent administrator and storage administrator are required to create and maintain user passwords for both the CIM agent and the DS8000 management applications. For DS8000 release 4.1 and later, the embedded CIM agent does not require configuration changes to manage DS8000 devices.

The DS8000 device user names and passwords are used to authenticate CIM client requests. The DS8000 administrator must create user names and passwords that CIM clients can use to attach to the CIM agent. Each user that is created must be in the administrator group. Users that are created in any group other than the administrator group cannot function with DS8000 release 4.1 and 4.2 CIM agents. The DS8000 administrator can use the DSCLI or the HMC console GUI to create the user names and passwords

Q: How do I verify the CIM agent connection to the HMC outside of SRM Profiler?

A: You must verify that the CIM agent software connects to the storage unit that you identified during configuration by issuing the following commands:

  • dscimcli -s https://<hmc_ip>:6989 -u <DS8000user> -p <DS8000password> lsdev -1
  • <hmc ip> is the IP address of the HMC, <DS8000user> is the user name that is used to log into the DS8000 SRM Profiler, and <DS8000password> is the password that is used to log into the DS8000 SRM Profiler.

Q: How do I setup SRM Profiler to connect to the embedded HMC CIM agent?

A: SRM Profiler should be configured with the same ports and credentials that were used to verify the HMC connection with the dscimcli:

  • HTTP Port: 6988 - This is the typical default port
  • HTTPS Port: 6989 - This is the typical default port
  • Provider IP: Use the HMC IP Address
  • Username – An administrator user, preferably the one used to verify the connection to the CIM agent
  • Password – The corresponding password to the user with administrator privileges used to connect to the CIM agent.
  • Identifier – Example: ibm.2107-75z9271 - This can be found in the SRM Profiler SMI-S logs or by using the "Confirm Provider" button in the Array configuration page of SRM Profiler.

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

Tags

Classifications

Public