Version 101 of the EMC: VMAX PowerPack adds the ability to discover and monitor VMAX storage groups (device masking groups), updates several Dynamic Applications, and adds Device Tier values to Device Classes.
- Minimum Required SL1 Version: 8.2.0
The "EMC: VMAX" PowerPack uses an older VMAX protocol. For newer VMAX releases, see the "Dell EMC: VMAX and PowerMax Unisphere API" PowerPack.
Before You Install
Ensure that you are running version 8.2.0 or later of SL1 before installing "EMC: VMAX" PowerPack version 101.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
Installation Process
To install version 101 of the EMC: VMAX PowerPack, perform the following steps:
By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.
If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.
To install this PowerPack:
- Familiarize yourself with the Known Issues for this release.
- See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 8.2.0 or later release.
- Download the "EMC: VMAX" version 101PowerPack from the Support Site to a local computer.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. When prompted, import "EMC: VMAX" version 101.
- Click the button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
Features
This release includes the following features:
- Dynamic Applications to discover, model, and monitor performance metrics and collect configuration data for Dell EMC VMAX devices
- Device Classes for each type of VMAX device monitored
- Event Policies that are triggered when VMAX devices meet certain status criteria
- An example credential that you can use as a template to create a Basic/Snippet credential for connecting to VMAX devices
Enhancements and Issues Addressed
The following enhancements and addressed issues are included in version 101 of the "EMC: VMAX" PowerPack:
- The following Dynamic Applications were added to discover and monitor VMAX storage groups (device masking groups):
- EMC: VMAX Storage Group Discovery
- EMC: VMAX Storage Group Stats
- EMC: VMAX Storage Group LUN Config
- A new "EMC: VMAX IO Ports Config" Dynamic Application was added to collect Fibre Channel and Ethernet port information.
- The following Dynamic Applications were updated to add collection labels to presentation objects:
- EMC: VMAX Array Capacity Stats
- EMC: VMAX Array Stats
- EMC: VMAX LUN Stats
- EMC: VMAX Storage Pool Capacity Stats
- The following Dynamic Applications were updated to add support for additional operational statuses:
- EMC: VMAX LUN Configuration
- EMC: VMAX LUN Discovery
- EMC: VMAX Storage Pool Config
- EMC: VMAX Storage Pool Discovery
- The "EMC: VMAX Statistics Cache" Dynamic Application was updated to improve exception handling and debug messaging.
- Device Tier values were added to the Device Classes in the PowerPack.
- An issue was addressed that was causing LUNs to change parent Storage Pools.
Known Issues
The following known issues affect version 101 of the EMC: VMAX PowerPack:
- A "BulkStatsNotSupportedError" error might periodically display for the "EMC: VMAX Statistics Cache" Dynamic Application. If this occurs, "CacheDataIsEmpty" errors might also display for the "EMC: VMAX Array Stats", "EMC: VMAX LUN Stats", and "EMC: VMAX Storage Group Stats" Dynamic Applications.
- When discovering a large number of component devices, the discovery process can cause the appearance of numerous critical events with the message, "Large backlog of asynchronous jobs detected".