Cluster Check
Introduction
After a PowerScale cluster has been added to Eyeglass, it should be periodically checked to confirm it remains reachable, is being inventoried correctly, and is free of configuration replication errors. This section covers the checks available directly in Eyeglass for a managed cluster, outside of full DR failover readiness validation.
For a complete Access Zone, IP Pool, DFS type, and SyncIQ readiness assessment for failover, see the Readiness Guide.
Verify Cluster Connectivity and Inventory
- Open the Inventory View icon on the Eyeglass desktop.
- Click the Refresh button (bottom right).
- Confirm the cluster status is not stuck showing Adding... and that Access Zones, SyncIQ policies, shares, exports, and quotas are visible in the inventory tree.
If a cluster's inventory fails to refresh or continues to show Adding..., this indicates a discovery error, most commonly caused by network reachability issues between Eyeglass and the cluster.
Check for Configuration Replication Job Errors
- Click Jobs to open the Jobs module.
- Review the State column for each Configuration Replication job associated with the cluster. Expected states include
OK,User Disabled, andPending. - If a job displays an
Errorstate, expand the job to view the error message associated with the failure.
A new SyncIQ policy detected on a cluster creates a job with Job Type None and raises an alarm until an administrator sets its type. See Eyeglass Jobs for details on job types and the None job alarm.
Review Eyeglass Reports for the Cluster
Eyeglass automatically generates a cluster configuration report (Inventory Report) that can be used to review a cluster's current configuration and detect day-over-day configuration drift.
-
To enable or disable the Inventory Report schedule:
igls admin schedules set --id InventoryReport --enabled <true|false> -
To change the reporting interval (valid values:
1M,2M,3M,4M,5M,6M,10M,15M,20M,30M,1H,2H,3H,4H,6H,8H,12H,1D,7D,31D):igls admin schedules set --id InventoryReport --interval <interval>
Because a cluster's configuration diff report can take a long time to run on clusters with a large configuration, the daily report only sends a full report when configuration differences are detected; otherwise it sends a basic summary.
Check Active Alarms for the Cluster
Review the Alarms icon in the Eyeglass Web UI for any cluster-related alarms, such as readiness warnings or new/unconfigured policy alerts, and confirm they are resolved or acknowledged as expected.