Updated 11/1/16
The article contains information on enabling the Dot Hill AssuredSAN 4xxx/5xxx array so that it can be monitored by SRM.
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 Dot Hill support site at https://www.dothill.com/support/.
Ensure you have the following information before adding the provider to SRM.
The IP address and credentials are the same for the SMI-S and API access:
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:
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.
To enable SMI-S using the CLI:
show protocols
command.set protocol smis enabled
command.To enable SMI-S using the web interface:
https://<controller_management_ip_address>
.Configuration > Services > Management
.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 show protocols
command in the CLI to confirm that it is enabled.
To check user privileges using the CLI, SSH into the array using the controller management IP Address, and then run the show user <username>
command.
To check user privileges using the web interface:
https://<controller_management_ip_address>
.Configuration > Users > Modify User
.To create a user with SMI-S and API access using the CLI:
create user level manage <username
> command.set user <username> interface wbi, smis
command.To create a user with SMI-S and API access using the web interface:
https://<controller_management_ip_address>
.Configuration > Users > Add New 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.