Skip to main content
Hardware

HPE MSA

Monitor controllers, enclosures, power supplies, fans, disks, RAID groups, pools and sensors of an HPE MSA storage array through its HTTPS JSON API.

The HPE MSA check monitors the hardware and RAID health of an HPE MSA storage array through its native HTTPS JSON API. It evaluates the system, controllers, enclosures, power supplies, fans, disks, disk groups (RAID) including running background jobs, pools, sensors, and controller redundancy individually. The check runs on an octoja agent on Windows, Linux, or macOS that can reach the MSA management controller over the network, every 5 minutes by default. According to the check description, it was observed on an MSA 2050 SAS; it is not live-validated on an MSA 2060.

Prerequisites

  • You need the Monitoring Check Management permission.
  • The running agent can reach the MSA management controller over HTTPS (port 443).
  • An MSA user for monitoring. A read-only user with the monitor role is sufficient.
  • If the MSA uses its factory self-signed certificate, you need its SHA-256 fingerprint. Verify it independently, for example directly on the MSA, before entering it.

Steps

  1. Go to Devices and open the device whose agent can reach the MSA.
  2. Click the Checks tab → Add Check → HPE MSA.
  3. Enter Host, Username, and Password.
  4. For a self-signed certificate, enter the Certificate SHA-256 fingerprint. Leave the field empty if the MSA's certificate is issued by a trusted certificate authority.
  5. Click Add Check.

After the first check interval, the result appears in the device's Checks tab.

Settings

FieldTypeRequiredDefaultDescription
HostTextYes—Hostname or IP address (including IPv6) of the MSA management controller, without scheme, path, or port
UsernameTextYes—MSA user for monitoring
PasswordPasswordYes—Password of the MSA user
Certificate SHA-256 fingerprintTextNo—SHA-256 fingerprint of the factory self-signed certificate. Colons, hyphens, and spaces are allowed. Leave empty for normal certificate validation

The check never disables TLS verification: without a fingerprint, the certificate must be regularly trusted; with a fingerprint, it must match exactly that fingerprint and be valid. The check does not follow redirects.

Results

The check evaluates each component individually. The overall result is the worst status across all components.

ConditionStatus
All components report a healthy stateOK
A component reports a degraded state, for example a degraded disk group or a running background job such as a rebuild, or a sensor reports a warningWarning
A component, disk group, controller, redundancy, or the partner controller reports a faultCritical
A status is unknown or missing, or a single query failsFailure (for that component)
The configuration is invalid, for example a host with a scheme or port, or a malformed fingerprintFailure
Signing in to the MSA failsFailure

If only some queries fail, the check keeps the findings already collected and marks the affected query as Query failed. Unused ports do not raise alerts.

If the check reports "MSA login failed. Check the credentials and API access.", check the username, password, HTTPS reachability, and — for a self-signed certificate — the fingerprint you entered.

Collected metrics

  • MSA model
  • Per component: kind (for example controller, disk, disk group, sensor), identifier, status, the checked value (for example health, RAID status, background job, sensor status), and the text reported by the MSA

The detail view lists problems first, followed by all components.

Notes

  • The check signs in to the MSA on every run and signs out at the end. If signing out fails, this appears as a separate Logout failed entry.
  • Each request to the MSA has a 15-second timeout.