Array Capacity Utilization Reports > EMC VPLEX Backend Array Summary
Version 9.2.01
EMC VPLEX Backend Array Summary
Detail reports are related to a specific enterprise object, such as a backup job or SAN fabric. You can only access detail reports through a link presented in the context of a main report, providing additional information that augments the main report. Detail reports cannot be generated, customized, or saved, as they are specific to the report from which they were derived. Therefore, they will not be available in search results.
Use Search to find the main template, report or a dashboard by name. Search is case insensitive, supports partial entries, and will display a list of potential matches.
As you enter the template, dashboard or report name in the Search field, up to 10 potential matches are displayed. If the result is shown, you can select and run it directly from the match list. You can also select All Items to display the full search results page and further filter your results.
You can use the Reports tab to browse through the StorageConsole templates, dashboards and reports. The navigation pane displays templates organized by products along with user created, and system folders. The main report is located here:
This report lists the backend arrays associated with VPLEX clusters. Link to details in the LUN Utilization Summary and the Array Capacity and Utilization reports.
Name of the VPLEX cluster.
Backend Array
Name of the backend storage array.
Backend Array Ports
List of array ports to which VPLEX is connected. This will contain the Port WWN or iSCSI node name.
Backend Controllers
List of controller names. This field will be empty when the firmware doesn't support the array.
# of Logical Units
Number of logical units exported from the array. This drilldown links to the LUN Utilization Summary. This link may be disabled if collection of backend arrays has not been enabled. If the drilldown is active, there may be a discrepancy in the number of LUNs represented in this report and the corresponding LUN Utilization Summary. This discrepancy can occur when the backend array collection is not as current as the VPLEX collection.