Dashboard, Health and Cluster Status

The eEKAS dashboard isand Cluster Status view are the first operational viewviews administrators should check after login. ItTogether combinesthey show system runtime, cluster health, node availability, Ceph status, cluster drive status and service counts in one place.counts.

What the DashboardCluster Status View Shows

services

Area	Meaning
SoftwareCluster versionStatus	TheShows installedwhether eEKASCeph releaseis healthy and build.whether Inall thenodes testare cluster this was eEKAS R8 (20260708).online.
OnlineNode sincetable	Runtime of the currentLists node orname, appliancerack, session.status, maintenance action, heartbeat IP, replication IP, Ceph server state and IP groups.
Current Cluster IOMaintenance	CurrentProvides read,a writecontrolled andway totalto clusterswitch throughput.a node into maintenance mode.
ClusterHeartbeat StatusIP	Management/heartbeat network used to monitor node availability.
Replication IP	Cluster name,replication activenetwork nodesused and high-levelfor Ceph health.traffic.
Ceph Health DetailsServer	HealthIndicates state,whether reason,the OSD count, raw usage, PG pressure and failure domain.
Cluster Members	Node list with online status and current load.
Ceph Alerts	Actionableon healththe warnings,node ifare any exist.
Cluster Drives	High-level status of configured cluster drives.
Shares & Targets	Counts for network shares, iSCSI targets and NVMe-oF targets.running.

Normal Healthy State in the Test Cluster

The test cluster showed five nodes online: EEKASBG-1 through EEKASBG-5. Each node reported Ceph Server as Running. Heartbeat addresses used the 192.168.0.x network and replication addresses used the 10.10.10.x network.

A healthy clusteroperational state should normally show all expected nodes online, Ceph healthhealthy, asCeph healthyServer orrunning HEALTH_OK,on all expected OSDs upnodes and in, no actionableunexpected Cephmaintenance alerts and cluster drives in optimal state.

In the test system the dashboard showed 5 active nodes out of 5 and Ceph reported HEALTH_OK. This is the state administrators should expect before creating shares, targets or S3 services for users.mode.

Daily Operational Check

Use this short check at the beginning of an operational review:

1. Confirm that all expected nodes are online.
2. Confirm that Ceph is healthy.
3. Verify that Ceph Server is Running on each expected node.
4. Check OSDsheartbeat up/in/total.and replication IPs for consistency.
5. Review PGwhether pressureany andnode rawis usage.in maintenance mode.
6. CheckContinue whetherwith Ceph AlertsStatus listsif actionableany items.
warning
7. Confirm that cluster drives are optimal.
8. Review service counts for shares and targets.appears.

When to Investigate

Investigate before making configuration changes if onea node is offline, a Ceph Server is not running, a node is unexpectedly in maintenance mode, heartbeat or morereplication nodesIPs are offline,wrong, or Ceph is not healthy, OSDs are not up/in, PG pressure is unexpectedly high, alerts are shown or a cluster drive is no longer optimal.healthy.

Documentation Note

Dashboard and Cluster Status values are point-in-time indicators. For support cases, capture the dashboardpage together with the exact time, affected service and a short description of the observed issue.