These metrics are only made available to SMI-S via Unisphere for VMAX and therefore it is necessary to tell SMI-S where a Unisphere installation exists from which to gather these metrics. The final topic I wanted to address with ESA 3.3 concerns a new set of metrics that are not collected by default. As I have it in my environment, this is what it currently looks like: The support should be added in the next release. So it does work, just not in a way where we call out they are Metro devices. We also do not support SRDF Metro (assuming you have it via the RPQ), however these devices are not filtered so you will see them show up as both R1 and R2. Note that we still do not support 3-site (most of these devices should be filtered out). Here is an example of a two-site SRDF group (I have both VMAX3 arrays configured):Ī more extended view is here, where both on the left and right-hand screens you can navigate the topology:
These are most prominently seen in the Inventory Trees. In addition to the reports and views development has done quite a bit of work on SRDF topologies. The reports and views themselves are great, but what I like most about them is the ability to use them as templates to create customized reports and views to suit a customer’s environment. Here is an example of a VMAX3 report, showing the devices: You’ll notice where necessary there are separate reports/views for VMAX and VMAX3 (e.g. We have 3 new reports shown here:Ĭlick to enlarge – use browser back button to return to post
Remedial actions for some alerts for VNX, VNXe, and XtremIO – e.g.Support for VMware VVols on the vVNX (virtual array) – topology and metrics delivered via the VNXe collector.ESA 3.3 posted today on EMC Support and as usual the development team has gone above and beyond for a quarter’s worth of work by both adding to existing platforms and expanding to new ones.
0 kommentar(er)
