PowerStore Manager Administration and Monitoring
This domain checks whether you can navigate PowerStore Manager, interpret what it reports, and pick the right tool: the UI, the REST API, the CLI, or CloudIQ.
Interface map
- Dashboard: capacity, performance, alert summary, and overall system health in one view.
- Hardware: nodes, drives, I/O modules, power supplies, and the identify/LED function used to locate a component in the rack.
- Monitoring: Alerts (state-based conditions with Critical, Major, Minor, and Info severities), Events (a chronological log of what happened), and Jobs (running, scheduled, and completed tasks).
- Storage, Hosts, Protection: provisioning and data-protection objects.
- Settings: users and roles, AD/LDAP, DNS/NTP, SMTP, SNMP, syslog, certificates, licenses, and network configuration.
- Support: SupportAssist, CloudIQ onboarding, support materials collection, and upgrades.
Access and roles
Built-in accounts include admin and service; role-based access control covers Administrator, Storage Administrator, VM Administrator, and Read-Only. Authentication is local or through AD/LDAP with group-to-role mapping. The REST API and pstcli authenticate with the same accounts and can automate anything the UI can do, which is why the UI and API never disagree about state.
Monitoring practice
Forward alerts out of the array: email, SNMP v2c or v3 traps, and syslog. A failed drive or a broken replication session should produce a notification, not a discovery during the next audit. CloudIQ adds forecasting and anomaly detection, but only once SupportAssist connectivity exists.
Worked example
A Major alert reports a degraded drive. Reasoning: open Monitoring > Alerts to read the component and severity, go to Hardware > Drives to confirm the state, and use the identify LED so the technician pulls the correct carrier. Watch Monitoring > Jobs for the rebuild, and verify that the proactive spare has not already been consumed, because a second failure during rebuild is the real exposure.
Traps
- Confusing alerts with events: alerts have an active/cleared lifecycle, events are historical entries.
- Expecting CloudIQ data without SupportAssist connectivity.
- Checking only the dashboard and missing node-level or component-level detail.
- Assuming SNMP or syslog is enabled by default; nothing is forwarded until you configure it.