ViPR SRM 4.2.1 Support Matrix
ViPR SRM 4.2.1 Support Matrix
ViPR SRM 4.2.1 Support Matrix
Version 4.2.1
Support Matrix
P/N 302-004-836
REV 02
Copyright © 2017-2018 Dell Inc. or its subsidiaries. All rights reserved.
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com
System Requirements 5
System Requirements
Browser requirements
For the following browsers, support varies.
Full support includes report viewing and browsing, plus support for interactive tables
and graphs, topology maps, and administration tasks (user management, enrichment
GUI, alerting GUI, and so on).
Note
22 (CLI via SSH) Opening port 22 on both the frontend host and
the Secure Remote Services VE host is required
for additional communication between the two
components.
Third-party tools
The following tools may be required during installation.
Supported SolutionPacks 9
Supported SolutionPacks
Notes
l Chargeback task is set to run once a day, by default. It can be run on demand, if
data needs to be reflected in reports sooner.
Notes
l For all versions of CMCNE/BNA, ViPR SRM does not support Single Sign On and
Launch-in- Context.
l ViPR SRM does not support Administrative Domains features.
l Performance Metrics will not be collected for Brocade AG Devices and FCoE
ports.
l Discovery support is limited to FC and FCoE ports; discovery of other protocols or
routing is not supported.
l CPU Utilization and Memory Utilization will not be populated for Brocade
switches.
l Name Server Database, Ethernet ports details are not discovered.
l For Alerts to be populated in ViPR SRM, configure the SNMP trap recipient on
each switch. For more information, refer to the ViPR SRM Alerting Guide.
SNMP + SMI-S (Zoning only through SMI-S)
Discover switch topology and performance metrics through SNMP. SNMP does not
support zoning discovery. Restrict SMI-S discovery to zoning details only.
This discovery approach is supported for backward compatibility with previous
versions.
Notes
l Performance Metrics will not be collected for Brocade AG Devices.
l CPU Utilization and Memory Utilization will be populated for Brocade switches
running firmware version FOS 6.3 and above. A Fabric Watch license should be
installed on the switches to fetch CPU and Memory utilization metrics.
l Discovery is limited to FC blades. Discovery supports only the E, F, and G ports on
the blades.
l ViPR SRM does not support Administrative Domains features.
l For all versions of CMCNE/BNA, ViPR SRM does not support Single Sign On and
Launch-in-Context.
l CISCO-NS-MIB
l CISCO-DM-MIB
l CISCO-ENTITY-SENSOR-MIB
l ENTITY-MIB
l CISCO-FC-FE-MIB
l IF-MIB
l CISCO-ENTITY-FRU-CONTROL-
MIB
l CISCO-VSAN-MIB
l CISCO-DM-MIB
l CISCO-ZS-MIB
l CISCO-SYSTEM-EXT-MIB
l SNMPv2-MIB
l CISCO-FCS-MIB
l CISCO-FEATURE-CONTROL-MIB
l CISCO-FC-DEVICE-ALIAS-MIB
Notes
l Some switch models might not have all of the listed MIBs and in that case those
capabilities will not be discovered.
l Discovery is limited to FC and FCoE ports only.
l ViPR SRM discovers Cisco Device Aliases that participates in Active Zoneset.
l ViPR SRM does not support discovery of VDC (virtual device context) and Fabric
extenders.
l Switches running NX-OS 5.2(x) and 6.2(x) code is recommended to upgrade to
5.2(8d) or later and 6.2(11) or later accordingly.
Note
l Archive Tier information is provided via an SNMP agent starting with DD OS 5.7.
This information is displayed only when archive/retention is enabled on the device.
Devices running an earlier version of DD OS, will not be able to display this
information even if archive/retention is enabled on the device.
Notes
l This SolutionPack does not contain reports. You should install the reports from the
SolutionPack for Physical Hosts.
l Only 64-bit versions of Windows is supported.
l Windows 2016 is not supported with EMC Host Interface.
Notes
l Support for the iSCSI protocol in Isilon products was deprecated as of OneFS 8.0.
To maintain support for other protocols across all supported versions of OneFS,
iSCSI performance statistics are also no longer supported as of ViPR SRM 4.0.
Notes
l Topology for ScaleIO on Vmware & Microsoft Hyper-V is not supported.
l For ScaleIO Node server, reports similar to software-only ScaleIO versions are
supported.
Notes
l Systems with FLARE/Operating Environment for Block 05.31 might incorrectly
report CurrentUtilization, ResponseTime, ServiceTime, and QueueLength metrics.
These metrics might not match Unisphere Analyzer because the necessary
counters used to properly compute them are not available in the NaviCLI output
for arrays that are running FLARE 05.31.
l The ResponseTime and QueueLength metrics are not available for disks dedicated
to Storage Pools on systems with FLARE/Operating Environment for Block
version 05.31. This is because the counters that are used to compute these
metrics are not available via Navisphere CLI at these versions.
l There are known issues collecting Disk data from arrays running FLARE/Operating
Environment for Block versions 05.31.000.5.509. It is advised to obtain the latest
software version of 05.31 from EMC Online Support (https://support.emc.com).
l To collect performance data for VNX MetaLUNs with Operating Environment for
Block (“FLARE”) 05.32, version 05.32.000.5.209 or later must be used.
l Navisphere CLI commands are used to communicate with the VNX. EMC
recommends matching Navisphere CLI versions with the Block Operating
Environment versions of VNX systems configured in the SolutionPack. For
example, if the firmware version of the Block side is 05.32.x, Navisphere CLI 7.32.x
or higher should be used. For more information on compatible Block OE and
Navisphere CLI versions, see the VNX OE for Block Release Notes and the
Unisphere Host Agent/CLI and Utilities Release Notes located on EMC Online
Support.
l SSH access to VNX-File/Celerra with an operator user. SSH access is needed
between VNX Collector host and Control Station to download files in /emc-srm via
SFTP via SFTP.
l To collect Quota information correctly, arrays must be running File OE 7.1.70.0 or
later.
l If ALUA (Failover Mode 4) is enabled for one or more hosts attached to a VNX
array and I/O to the associated host LUNs is distributed across more than one
Storage Processor, values for the LUN perfromance metrics
AverageBusyQueueLength, QueueLength, and ResponseTime may be higher than
what is displayed in Unisphere Analyzer, because the Navisphere CLI counters
used to compute these metrics will accumulate for each Storage Processor.
Notes
l SMI-S provider 8.x and 9.x are packaged as part of the Solutions Enabler. For
SMI-S installation, download the Solutions Enabler package from EMC Online
Support.
l eNAS is supported by the SolutionPack for EMC Unity/VNX/VNXe.
l For feature specific compatibility, refer to the Solutions Enabler, SMI-S Provider,
and Unisphere for VMAX documentation.
l SMI-S Provider requires 6 gatekeepers per array fibre-connected to the SE host.
l VMAX arrays discovered through SMI-S cannot get the number of FICON mapped
devices.
l Solutions Enabler 8.3.0.6 should be avoided due to a Non-Disruptive Migration
(NDM) corruption issue. See KB article 496471 for more details. It is
recommended that the latest 8.3 release available be used instead.
SMI-S Notes
9.0 (latest 9.0.x release is Based on the calculations of SE 9.0 Subscribed and
recommended) Oversubscribed values differ from U4V 9.0.
8.3 (latest 8.3 release is Solutions Enabler with SMI-S Provider is required in
recommended) order for Compression and SRP Efficiency details to be
collected and reported. These details are only collected
using SMI-S and are not collected via SYMCLI.
8.2 (latest 8.2 release is required) SMI-S topology collection of VMAX arrays require the
8.2 version to have data equivalence with the SYMCLI
topology collection. Required for support of:
l HYPERMAX OS FAST.X incorporated devices
l HYPERMAX OS SRDF/Metro
l HYPERMAX OS CKD device support
l HYPERMAX OS VVOL device support
l Device reservations
SMI-S Notes
9.0 (latest 9.0.x release is NA
recommended)
8.3 NA
8.2 (latest 8.2 release is SMI-S included in Solutions Enabler 8.2.0.18 is the
recommended) minimum required version.
Notes:
l 100K maximum devices from all arrays, zone to host, where the SMI-S Provider is
installed.
Unisphere support for DMX, VMAX, VMAX3, and VMAX All Flash arrays
Table 29 Collecting performance statistics using SMI-S Provider and UniSphere for VMAX
Unisphere Notes
9.0 (latest 9.0.x release is NA
recommended)
Table 29 Collecting performance statistics using SMI-S Provider and UniSphere for
VMAX (continued)
Unisphere Notes
8.3 8.3
Table 31 Collecting performance statistics, capacity, and topology information using UniSphere
Unisphere Notes
8.4.0.0 Latest 8.4.0.x release is recommended.
Notes
l Do not run VPLEX 5.2sp1 patch 2 with any version of the product as the VPLEX
management server could become unresponsive.
l Backend Arrays supported by this SolutionPack: EMC VMAX, EMC VNX, NetApp,
EMC XtremIO, IBM XIV, Hitachi Device Manager, HP StorageWorks P9000, and
HP 3PAR.
l Backend Arrays not supported by this SolutionPack: ScaleIO, EMC Isilon, and IBM
DS.
Notes
l Only block mode is supported on HUS arrays (not file or object).
l Performance statistics are provided for the HUS VM, VSP, and VSP G through the
Embedded SMI-S Provider. For details about enabling Embedded Performance
Collection for these models, refer to the SolutionPack Installation Guide.
Notes
l Performance statistics are provided for the P9500 through the Embedded SMI-S
Provider. For details about enabling Embedded Performance Collection for this
model, refer to the SolutionPack Installation Guide.
Notes
l SolutionPack for IBM LPAR will collect information only from HMC.
l To discover VIO Server and LPAR information, use SolutionPack for Physical
Hosts.
l INQ is pushed to both VIO Servers and Clients.
l The Live Partition Mobility (LPM) feature on IBM LPAR causes floating CPU and
memory that is not captured by agentless collection scripts. For this reason, the
SolutionPack for IBM LPAR does not support dynamic refresh on LPARs occurring
due to the LPM capability on AIX/Linux LPAR.
l INQ 8.1.0.4 is supported only on 64-bit OS platforms. INQ 7.6.2 needs to be
manually copied onto 32-bit target hosts.
Notes
l Backend Arrays supported by this SolutionPack: EMC VMAX, EMC VNX, IBM XIV,
NetApp, HP 3PAR, and Hitachi Device Manager.
l Backend Arrays not supported by this SolutionPack: EMC XtremIO, HP
StorageWorks P9000, ScaleIO, EMC Isilon, and IBM DS.
l Internal Storage is not supported in the Raw Capacity Usage and the Configured
Usable reports. Service Level and Chargeback is not supported for mdisks (Virtual
Disks) based on internal storage.
l Replication is not supported.
Notes
l This SolutionPack can only be installed on a Windows collector host.
MS-SQL Server > RDM MS-SQL > FS using VPLEX supported for End-to-end
capacity but not supported for topology
Notes
l The cluster management IP must be provided during C-Mode Filer discovery.
Notes
l The SolutionPack for Oracle Database was tested with ojdbc5.jar and ojdbc7.jar on
Oracle 10, 11, and 12g versions respectively.
l Work with your DBA to determine the appropriate JDBC driver based on the
installed version of Oracle. Download the JDBC driver from: www.oracle.com/
technetwork/database/features/jdbc.
l For ASM Disk collection, only Oracle instances running Solaris, Windows 2008 R2
or later, and Red Hat Enterprise Server 5, 6, or 7 are supported.
l FileSystem information is not supported for Vdisks on VMs.
l ASM Disks on Vdisk are not supported.
l Non-admin Windows does not support ASM data.
l Oracle > File System > LUN l Oracle > FileSystem > Datastore
l Oracle > ASM > RDM l Oracle > ASM > VMDK
l Oracle > ASM > LUN l Oracle > ASM or FileSystem using VPLEX supported
for End-to-end capacity but not supported for
topology
Note
l Refer to the ViPR SRM Ports Usage and Worksheet for more information on port
configuration.
l INQ 8.1.0.4 is supported only on 64-bit OS platforms. INQ 7.6.2 needs to be
manually copied onto 32-bit target hosts.
l The PowerPath Support Matrix on EMC Online Support Site provides more
details.
Notes
l ESM rules are not supported for third-party arrays.
l Policy Administration and EMC Support Matrix Administration reports are not
supported in the minimal browse mode.
The ViPR SRM vApp is designed to be a black-box software appliance, to which EMC
provides critical updates, such as security patches and component updates. As such,
users are generally not allowed to install software onto the vApp based VMs. The
exceptions include debugging utilities (man, tcpdump, netcat, net-snmp, sysstat, and
iotop), which are provided by the SRM VM Utilities Manager, and the backup and
restore solutions listed in this chapter.
VMware vSphere Data Protection Advanced Refer to EMC ViPR SRM: vApp Backup and
Restore Using VMware vSphere Data
Protection Advanced for more information.
CommVault Simpana Virtual Server Protection Refer to EMC ViPR SRM: vApp Backup and
Restore Using Commvault Simpana Virtual
Server Protection for more information.
IBM Tivoli Storage Manager Refer to EMC ViPR SRM: vApp Backup and
Restore Using IBM Tivoli Storage Manager
for more information.