StorageGuard analyzes the hardening of Dell PowerMax systems by gathering configuration details from Dell Unisphere for PowerMax and optionally Dell Solutions Enabler (SE).  

Before You Begin

Considerations for scanning Dell PowerMax:

• Unisphere provides broad API coverage for PowerMax configuration data and is sufficient for most environments.
• Ensure you are running Unisphere version 10.1 or later (10.3+ recommended).
• Scanning Solutions Enabler (SE) adds deeper visibility and enables additional best‑practice and baseline validations but requires host and CLI access by StorageGuard.
• Use Unisphere for simpler setup; include SE for maximum coverage and validation depth.
• You can add a Solutions Enabler (SE) scan later if needed.
• This article also applies for Dell VMAX systems.

Preparation for Scanning Dell Unisphere for PowerMax

StorageGuard collects configuration data from Dell Unisphere for PowerMax by opening an HTTPS connection to the Unisphere management server and running read-only REST API calls.

The following table lists the requirements for scanning Dell Unisphere for PowerMax:

Creating a User Account for Scanning Dell Unisphere for PowerMax

The following suggested method can be used to create a user account with appropriate privileges:

• Navigate to the User Management section under Settings > Users and Groups in Unisphere.
• Create a new user with the Auditor role.

Preparation for Scanning Dell PowerMax: Solutions Enabler (SE)

StorageGuard can also gather PowerMax configuration data by running read-only SYMCLI commands on a storage management host installed with Solutions Enabler ("SYMCLI host").

The following table lists the requirements for SE-based scan of Dell PowerMax systems:

Creating an SE User Account for Scanning Dell PowerMax

The following suggested methods can be used to create a user account with appropriate privileges:

Method #1 (sudo-based, Linux/Unix only):

Method #2 (based on Dell SE User Management):

• Log in to the Solutions Enabler host with root (Linux) or a user with administrative rights (Windows).
• Edit the daemon_users file and add the following line: sguard <all>
• The file is located by default at /var/symapi/config (Linux) or %PROGRAMFILES%\EMC\SYMAPI\config (Windows)
• Create a assign_user.cmd file and add the following line: assign user sguard to role Auditor;
• For each array SID, run the following command: symauth -sid <sid> -file assign_user.cmd commit
• Edit the sudoers file and add the following line: sguard ALL= NOPASSWD: /bin/cat *, /bin/ls *

FAQ

• The sguard username is provided as an example. Any username can be used.
• If used by your organization, PowerBroker, seSUDO and similar privilege management solutions can be configured instead of native sudo.
• In case eMGMT is used:
  • StorageGuard should be provided with the IP of a SYMCLI client host instead of eMGMT SYMAPI Server IP.
  • The SYMCLI_connect and SYMCLI_CONNECT_TYPE environment variables should be defined for the sguard user on the client host, as follows -
  • Linux:
  • Add the following variable to the sguard .profile file:
  • SYMCLI_CONNECT=SYMAPI_SERVER_NAME
  • SYMCLI_CONNECT_TYPE=REMOTE
  • Windows:
  • Press "Windows Key + Pause", Click Advanced system Settings>Advanced> Environment Variables>User variables for sguard>New
  • Variable Name: SYMCLI_CONNECT Value: SYMAPI_SERVER _NAME
  • Variable Name: SYMCLI_CONNECT Value: REMOTE
  • Note that the SYMAPI_SERVER_NAME should match the name configured in the symapi/config/netcnfg file.