SAN Volume Controller or IBM Storage Virtualize

Add IBM Storage Virtualize storage systems to get performance and asset, capacity, and configuration metadata analyzed so that you can detect performance issues, changes in storage usage, and plan for future storage needs.

In this documentation, IBM Storage Virtualize is used to refer collectively to IBM® SAN Volume Controller, IBM Storage Virtualize for Public Cloud, IBM Storage Virtualize as Software Only, and IBM Storwize® storage systems, and to IBM FlashSystem® devices that run IBM Storage Virtualize.

IBM Storage Virtualize for Public Cloud: Before you add an IBM Storage Virtualize for Public Cloud storage system for monitoring, you must configure it for communication with IBM Storage Insights. For more information, see External link icon

Configuring IBM Storage Virtualize for Public Cloud.

Use the following information to add storage systems so that they can be monitored and that metadata can be collected, analyzed, and presented in the GUI.

Host names or IP addresses

The host names or IP addresses that are used to connect to the storage systems. Use host names if your IP addresses change regularly. Depending on what is supported in your environment, you can enter an Internet Protocol version 4 (IPv4) or IPv6 address. If you enter an IPv6 address, the preferred representation is written as eight groups of four hexadecimal digits. Example: 2001:DB95:0000:1234:0000:0000:5678:ABCD.

Authentication Type

The user name and password or the private Secure Shell (SSH) key that is used to connect to the storage system.

User name and Password

The user name and password for logging in to the storage system.

For IBM Storage Virtualize 8.3.1.2 or later, the user must have the Monitor role or a role that includes monitoring privileges.

If the collection of performance metadata is stopped on the storage system, the role of the storage system user determines whether the collection can be automatically restarted. For example, if the storage system user has the Monitor role and your administrator has stopped the collection on the storage system, the collection must be manually restarted by your administrator before IBM Storage Insights can collect performance metadata. Learn more.
For versions earlier than 8.3.1.2, the user must have the Administrator, or SecurityAdmin role so that the metadata for the storage system can be collected.

Tip: Why not create a dedicated user account to manage the monitoring of your storage systems more efficiently? So, instead of using an existing user account, create a new user account to connect to and collect metadata from your storage resources.

Authenticate with SSH key

When you upload the SSH private key, you must add the SSH user who is associated with that SSH private key when it was created.

SSH key: Upload the new SSH private key that was generated to authenticate with the storage system. The valid file formats for SSH keys are PEM and PuTTY. If the key is in another format such as OpenSSH, it must be converted to PEM or PuTTY before it can be used.; Restriction: PuTTY Private Key version 3 files are not supported. If you use PuTTYgen 0.75 or later to generate keys, ensure that you choose the option to generate version 2 keys. In PuTTYgen, click 2 for PPK file version on the Private Key File Parameters window before you generate the key.; For more information about PuTTYgen, see https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html.
Passphrase: The passphrase that is associated with the SSH key pair. If a passphrase was not created for the SSH key pair, leave the field blank. For SSH keys that use the PuTTY file format, you cannot use a passphrase to protect the private key.
SSH User: The user that was associated with the SSH key when it was created must have an Administrator role so that the metadata that is analyzed and presented in the GUI can be collected.
SSH Password: The password associated with the SSH user. If the password was not created, leave this field blank.