Description
Sentry’s HP 3PAR monitoring solutions rely on the HP 3PAR embedded SMI-S Provider (also known as HP 3PAR CIM Server) to collect hardware and performance metrics about HP 3PAR storage systems and bring them into the BMC monitoring platforms.
In some cases, monitoring issues may be related to the HP 3PAR CIM server. This article describes how to verify the configuration and status of the HP 3PAR CIM Server. This will help you identify whether the problem is related to the CIM Server or to the monitoring solution itself.
Verifying the version of the HP 3PAR Storage Server Software
- Launch the HP 3PAR Command Line Interface (CLI). Alternatively, an SSH client can be used to connect to the 3PAR.
- Enter the IP Address of HP 3PAR Storage System, Username and Password (Default Credentials: 3paradm / 3pardata).
- Run the “showversion” command to check the version of the storage server software. The minimum supported version is 3.0.0
Ensuring that the HP 3PAR CIM Server is running
To verify whether the HP 3PAR CIM server is running:
- Run the “showcim” command. The following result should appear:
cli% showcim
-Service- -State- --SLP-- SLPPort -HTTP-- HTTPPort -HTTPS- HTTPSPort PGVer CIMVer
Enabled Active Enabled 427 Enabled 5988 Enabled 5989 2.5.1 2.3.1
- Check the Service Column to see the CIM server status. If the status is “Disabled”, you will have to start CIM server.
Starting the HP 3PAR CIM Server
To start the HP 3PAR CIM Server:
- Launch the HP 3PAR Command Line Interface (CLI). Alternatively, an SSH client can be used to connect to the 3PAR.
- Enter the IP Address of HP 3PAR Storage System, Username and Password (Default Credentials: 3paradm / 3pardata).
- Run the “startcim” command.
Setting the properties of the HP 3PAR CIM Server
Use the command “setcim” to set the properties of the CIM server. This command can also be used to:
- Enable or disable the HTTP and HTTPS ports of the CIM server
- Configure the port numbers associated with HTTP and HTTPs protocols
- Enable or disable the SLP ports.
Known Issue
When attempting to monitor HP 3PAR systems using Active Directory credentials, volume information may not be available. This is due to a bug in the 3PAR SMIS provider. As a result of this, it may be necessary to use a user account local to the 3PAR.