Symptoms
In order to make a Compliance Alert Policy for a storage group, it has to meet the following restrictions:
- The storage system must run HYPERMAX OS 5977 or PowerMaxOS 5978 and be registered for performance statistics collection.
- The storage group must:
- Be either a child or a standalone. Parent storage groups are not supported.
- Be associated with a service level other than optimized.
- Contain volumes other than gatekeepers.
- Be in a masking view.
- Not have a policy currently associated with it.
In this case, the customer has 6+ storage groups that met the above restrictions and could make the Compliance Alert Policies in their emgmt Unisphere. This was not the case for their standalone Unisphere. Their standalone had at least 2 local arrays and they wanted to manage them both through the standalone instance where more control and service monitoring can occur.
The first local array, to be referenced as "Array 1", was able to make the Compliance Alert Policies for their storage groups. The second local array, to be referenced as "Array 2", did not list any storage groups when making a Compliance Alert Policy. Since the same storage groups on Array 2 were available for Compliance Alert Policies in their EMGMT Unisphere, this appeared to be a problem with the standalone instance.
Services were restarted and eventually, Unisphere was re-installed but the issue persisted.
Cause
In troubleshooting, it was found that the storage groups in Array 2 had the EXACT same name as those in Array 1. Because the storage groups had the same name Unisphere saw that an alert policy was already in place and removed the storage groups from the list of available when in the Compliance Alert Policy create wizard.
Resolution
The workaround is to rename the storage groups differently than the others. Once the names are different the storage groups become available.
Permanent fix: is in Unisphere for PowerMax 10.0 and above
This was found in Unisphere 9.2.3.4 and 9.2.3.15
Affected Products
Unisphere for PowerMax