HP Storage Provisioning Manager (SPM) version 2.3 User Guide

software must be installed. For more information, see “Working with Brocade Fibre Channel
networks” (page 72).
Installation and configuration of HP Matrix OE, HP 3PAR StoreServ Storage Systems, HP EVA disk
arrays, and HP XP/P9000 disk arrays is beyond the scope of this document.
NOTE: This information does not apply to unmanaged arrays or SANs. For more information,
see “Working with unmanaged networks” (page 92) or “Working with unmanaged
arrays” (page 103).
Launching SPM
To start SPM, open a browser window to https://servername:8000, where servername
is the name, or IP address, of the server hosting SPM (the Central Management Server in a Matrix
environment).
NOTE:
• For browser compatibility, see Matrix compatibility documentation, which can be downloaded
from http://www.hp.com/go/matrixoe/docs.
• Microsoft Silverlight must be installed on the client system in order to run the SPM GUI.
• The security certificate for data encryption is generated by SPM at runtime. Therefore, it is not
signed by a Certificate Authority. The browser may display a warning that SPM cannot be
proven to be a trusted site. Follow the instructions on the warning to enable access to launch
SPM.
Logging in to SPM
SPM accepts existing Windows credentials for both logging in and managing access control. The
given credentials must be known to the server running the SPM service. If the server is joined to a
Microsoft Windows Active Directory domain, the domain credentials can also be used. Initially,
only members of the server-specific local Administrators group are able to log in. For additional
information on security settings see Managing security.
To log in, launch SPM, enter the login name and password in the appropriate fields, then click
OK.
NOTE:
• If the logged-in user is idle for more than 30 minutes, SPM session times-out and the user is
required to log in again.
• To specify a domain name when logging in to SPM, specify it in the Login Name field in the
following format: domainName\userName.
Web security with SPM
SPM provides a secure web service using the SSL/TLS technologies typically used to protect sensitive
information. These technologies require that the server present information, known as a certificate,
that uniquely proves its identity. By default, SPM generates a usable certificate once it’s been
installed. Because the certificate is generated, it does not contain any information about who should
trust this certificate. This is known as a self-signed certificate.
When a client, such as a web browser, wants to connect to the server, the server usually displays
a screen indicating that the certificate is not trusted implicitly. The user must decide whether to
continue. Though a self-signed certificate cannot prove identity, it can still be used to provide
encryption to all the data between the client and server.
An SPM administrator can choose to provide their own certificate, which includes the proper trust
information. Doing so ensures that users will not receive the warning from the browser.
Launching SPM 17