ViPR SRM 18.104.22.168 — SolutionPack for EMC® VIPR® Controller
Table of Contents
- Lists virtual data center names, IP addresses, and number of virtual arrays, virtual pools, hosts, block volumes, and file systems associated with each virtual data center. Click a row to drill into capacity summaries, an inventory list of all components, and a detailed view of capacity available to each virtual array.
- Storage Capacity
- Health Dashboard
- A set of reports showing ViPR Controller health, including:
- Availability is a visual dashboard of availability percentages for each virtual data center. Click a percentage to see a historical trend chart.
- ViPR Nodes shows host name and IP address for each node, along with % availability, % memory usage, system load averages, and disk partition usage.
- Virtual data centers shows availability in addition to committed SLA compared to current and probable SLA.
- A set of reports showing number of read and write requests, bandwidth usage rates for read and write requests, and descriptive details for:
- File systems
- Block volumes
- Storage systems
- Virtual data center
- Virtual pools
- Situations to Watch/Tenants Near Quota
- Shows metrics about tenants whose %Usage is over configured thresholds and number of days until quota. Click a row to drill into details about the tenant.
- Inventory reports
- Lists project names and associated virtual data center, tenant, owner, and information about block and file capacity. Click a project row to drill into details about that project, including provisioned capacity and tables of detailed information about each virtual pool, block volume, and file system associated with the project.
- Lists tenants and associated virtual data center, a description, information about block and file capacity, number of hosts, and number of projects. Click a tenant row to drill into details about that tenant, including provisioned capacity, hosts by type, quota summary, and tables of detailed information about each project, virtual pool, block volume, file system, host, and cluster associated with the tenant.
- Virtual Arrays
- Lists virtual arrays and associated virtual data center, type of SAN zoning, number of virtual pools, subscribed capacity, and used capacity. Click a virtual array row to drill into details, including details about each file system or block volume, virtual pools, and storage ports associated with the virtual array.
- Virtual Pools
- List virtual pools and associated virtual data center, pool type, description, provisioning type, pool assignment type, supported protocols, and virtual subscribed and used capacity, and actual storage pool free, used, and usable capacity. Click a virtual pool row to drill into details, including capacity trending charts and details about each block volume, file system, storage pool, and virtual array associated with the virtual pool.
Supported collection interfaces
For information about supported collection interfaces, refer to the ViPR SRM Support Matrix.Back to Top
The SolutionPack is distributed in the EMC ViPR SRM 3.6.3 Patch1.
- Go to the following URL:
- Click the gray banner at the bottom of the window.
- Provide the requested registration information.
- Download the ViPR SRM 3.6.3 Patch 1 zip file.
- Unzip the file and extract the
emc-vipr-2.2.pkg file to a location accessible to the ViPR SRM Frontend host.
A bundled readme file describes installation scenarios, including upgrades and new installs.
- Log in to the ViPR SRM 3.6.3 Console.
- Click .
- Click Upload in the right pane.
- Click Choose File and navigate to the package file.
The SolutionPack is now available for installation.
Before you begin
- You must have EMC ViPR Controller 2.2.
- You must have ViPR SRM 3.6.3.
- ViPR SRM core modules must be up-to-date in all servers because not all module dependencies are validated during the SolutionPack installation or update process.
- Deploy the vApp as described in the article on installing ViPR SRM as a virtual appliance.
- You need to know the connection details for the instance of ViPR from which you want to collect data. This includes:
- Virtual IPv4 address of the ViPR Controller 2.2.
- Credentials for a ViPR account with the System Monitor and System Auditor Role.
- The core software and license must already be installed.
- You need to know the frontend hostname and admin credentials for the core software instance to which you are adding the SolutionPack.
- Click Administration.
- Click Centralized Management.
- Click SolutionPacks.
- Click SolutionPack Center.
- Select the SolutionPack in the Browse and Install SolutionPacks window.
- Click Install.
- Type the instance name.
- Assign a server for each component.
In a typical four server deployment, the recommended servers are selected automatically.
The window displays a note about Alert Consolidation.
The window displays pre-configured alert details.
- From the Alerting on data collection drop-down menu, select the Primary Backend host.
The window displays data collection details.
- From the
Data collection drop-down menu, select existing settings that have been specified for other components, or select
Add a new data collection.
If you select Add a new data collection, type information about the data collection. In Hostname or IP address to send data to, use localhost on port 2020, which is the Collector host where the Load Balancer Connector is installed.
- From the
Alert Consolidation drop-down menu, select existing settings that have been specified for other components, or select
Add a new Alert consolidation.
If you select Add a new Alert consolidation, type information about the alerting configuration. In Alerting Backend hostname or IP address, specify the Primary Backend host.
- From the
Frontend Web service drop-down menu, select existing settings that have been specified for other components, or select
Add a new Frontend Web service.
If you select Add a new Frontend Web service, type information about the Frontend Web service.
- Leave Enable Topology Backend on data collected checked.
- From the
Topology Service drop-down menu, select existing settings that have been specified for other components, or select
Add a new Topology Service.
If you select Add a new Topology service, provide information about the topology service and the web service. In Topology Service hostname or IP address, specify the Primary Backend.From the Web-Service Gateway drop-down menu, select existing settings that have been specified for other components, or select Add new gateway. If you select Add new gateway, provide information about the web-service gateway where the topology service resides.
- Select Use advanced settings to configure polling settings or to disable a polling type.
- In each polling period drop-down menu, select a polling period or select Disabled to turn off the polling.
The window displays reports settings.
- In Administration Web-Service Instance, select an existing instance or create a custom instance.
- Click Install.
- Click Ok when the installation is complete.
- Click .
- Click ViPR.
- Click Add new device.
- In Server, select the ViPR Collector.
- In Instance, select the ViPR instance.
- For each ViPR server from which you want to collect data, enter a unique name, its public virtual IPv4 address, and credentials for an account with the System Administrator role.
- Click Test to validate the credentials.
- Click Ok, and then Save.