DataCore SANsymphony

The DataCore SANsymphony check monitors SANsymphony nodes, including terraXaler HCI environments. It reads node health, virtual disks, disk pools, paths, mirror recovery, CDP history and open DataCore alerts. It runs on Windows, every 5 minutes by default.

Prerequisites

• A Windows device with the octoja agent and the DataCore PowerShell module installed. The check uses Windows PowerShell 5.1, not PowerShell 7.
• A DataCore account with read access (View role). For Windows authentication, the executing service account must have the corresponding DataCore access; your interactive sign-in does not automatically apply to the agent.
• You can assign checks to the device; configuration packages require Monitoring Check Management.

Steps

1. Open the Windows device and add DataCore SANsymphony under Checks. Use a configuration package for multiple nodes.
2. Enable Show advanced options to reveal the server, credentials and additional settings. Leave DataCore server empty to use the local node. Even when targeting another server, the executing device must have the DataCore module installed.
3. Leave DataCore user and Password empty for Windows authentication, or supply a DataCore account.
4. Adjust the minimum frontend and mirror path counts to your topology. The defaults are not a universal healthy baseline.
5. Save and inspect the nodes, pools and disks after the first run. Configure alerting if needed.

Settings

Troubleshoot

For a missing module, missing permissions or connection errors, check execution on the agent device first. A successful login in your own PowerShell session does not prove that the service account has access. Investigate missing paths and low free pool space in DataCore; the check does not change storage configuration. Zero paths are critical.

Intentionally unused port connections

If a port connection is permanently unused, for example iSCSI, enable Show advanced options in the check configuration and disable Warn about disconnected ports. After the next run, disconnected ports no longer produce a warning.

This setting applies to all port connections, not just iSCSI. Frontend and mirror paths, storage health and DataCore alerts are still evaluated. Other problems can therefore still make the check Warning or Critical; zero frontend or mirror paths remain critical.