Applications Systems
SRM: Enable a Dot Hill AssuredSAN 4xxx/5xxx array
The article contains information on enabling the Dot Hill AssuredSAN 4xxx/5xxx array so that it can be monitored by SRM.
First published date
Last published date
Overview
The article contains information on enabling the Dot Hill AssuredSAN 4xxx/5xxx array so that it can be monitored by SRM. It should be used in conjunction with the Add your storage array for monitoring with SRM topic in the Success Center documentation or online help.
Dot Hill AssuredSAN 4xxx/5xxx arrays communicate with SRM using SMI-S and REST APIs. The Dot Hill provider is running on both controllers of the Dot Hill array. The providers are enabled by default.
For more information, please consult the documentation supplied with your array, or visit the AssuredSAN support site at https://www.seagate.com/support/dothill-san/assuredsan-5000-series/ (© 2019 Seagate Technology LLC, available at https://www.seagate.com/, obtained on June 19, 2019).
Product section
Resolution
Credential required to add the array
Ensure you have the following information before adding the provider to SRM.
- IP address or hostname for the array control station.
- SMI-S username. The default is manage
- SMI-S password. The default is !manage
- API username. The default is manage
- API password. The default is !manage
-
The IP address and credentials are the same for the SMI-S and API access:
- Provider IP Address. The IP Address of one of the controllers
- Provider Credentials. Credentials of an array user with at least Manage level privileges and access for the wbi and smis interfaces.
- Protocol. The default is HTTPS
- HTTP Port. The default is 5988
- HTTPS Port. The default is 5989
- Interop Namespace. The default is /root/interop
- Array Namespace. The default is /root/dhs
- Array API HTTP Port. The default is 80
- Array API HTTPS Port. The default is 443
- API protocol Schema. The default is HTTPS
Enable the array
The Dot Hill provider is running on both controllers of the Dot Hill array. The providers are enabled by default.
The IP address and credentials are the same for the SMI-S and API access:
- Provider IP Address: The IP Address of any one of the controllers
- Provider Credentials: Credentials of an array user with at least Manage level privileges and access for the wbi and smis interfaces.
The default user "manage" can be used or a new user can be created with the required privileges.
The default port used for SMI-S is 5989.
Enable SMI-S
To enable SMI-S using the CLI:
- SSH into the array using the controller management IP address as the user "manage".
- Run the
command. - Check the output to ensure SMI-S is enabled.
- If SMI-S is not enabled, run the
command.
To enable SMI-S using the web interface:
- Log in to the Management Interface:
. - Click
. - Check to see if SMI-S is enabled.
- If SMI-S is not enabled, select the Enable check box under Storage Management Initiative Specification (SMI-S).
In some versions of the management interface, even after enabling SMI-S and saving, the web interface may still show that it is not enabled. Run the command in the CLI to confirm that it is enabled.
Check user privileges
To check user privileges using the CLI, SSH into the array using the controller management IP Address, and then run the command.
To check user privileges using the web interface:
- Log in to the Management Interface:
. - Click
. - Choose the user from the table.
Create a user with SMI-S and API access
To create a user with SMI-S and API access using the CLI:
- SSH into the array using the controller management IP Address.
- Run the
> command. - Run the
command.
To create a user with SMI-S and API access using the web interface:
- Log in to the Management Interface:
. - Click
.
- Enter the user Name and Password.
- Select Manage from the User Roles drop-down list.
- Select the WBI Access check box.
- Select the SMI-S Access check box.
- Click Add User.
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.
Screenshots property of © 2016 Dot Hill.