Docu59090 VNX Family Monitoring and Reporting 2.2 User Guide
Docu59090 VNX Family Monitoring and Reporting 2.2 User Guide
User Guide
P/N 300-014-420
08
Copyright 2016 EMC Corporation. All rights reserved. Published in the USA.
Published February 2016
EMC 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. EMC Corporation 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 EMC software described in this publication
requires an applicable software license.
EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and
other countries. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support
(https://support.emc.com).
Contents
Preface
Chapter 1
Introduction
Summary of VNX Family Monitoring and Reporting ........................................ 8
Dashboards and Reports......................................................................... 9
Database and Analytics......................................................................... 10
Administration ...................................................................................... 10
Architectural Overview ................................................................................ 10
Chapter 2
Installing
Environment and system requirements ....................................................... 12
Host system requirements..................................................................... 12
Browser Requirements .......................................................................... 12
Supported Platforms ............................................................................. 13
Supported Languages ........................................................................... 13
Installing on Windows ................................................................................ 13
Installing on Linux ...................................................................................... 14
Deploying as a vApp.................................................................................... 14
Upgrading the vApp .................................................................................... 15
Pre-requisites........................................................................................ 15
Update Linux Components .................................................................... 16
Stage VNX Family M & R components on the VNX M & R VM deployed using
the vApp Installer .................................................................................. 16
Configuring the user process limits for Linux
(Linux binary installs only) ........................................................................... 16
System start................................................................................................ 17
Uninstalling ................................................................................................ 18
Upgrading................................................................................................... 18
Version 1.x to 2.x .................................................................................. 18
Version 1.x to 1.x and 2.x to 2.x ............................................................ 19
Chapter 3
Administration tasks
About Home Page .......................................................................................
Managing licenses ......................................................................................
Managing User Accounts.............................................................................
Viewing Storage Systems ............................................................................
Adding/Editing a System.............................................................................
Registered Systems Page ......................................................................
Configuring Mail..........................................................................................
Alerting.......................................................................................................
Data Enrichment .........................................................................................
Chargeback...........................................................................................
Backing up your system ..............................................................................
Backing up the database.......................................................................
Backing up the configuration files .........................................................
Retention parameters..................................................................................
Chapter 4
22
23
24
26
26
27
27
28
31
31
35
35
35
36
Viewing Reports
The web portal ............................................................................................ 38
Search for components ............................................................................... 40
Display options ........................................................................................... 41
Contents
Chapter 5
43
44
45
46
47
Troubleshooting
Common Issues .......................................................................................... 50
Resetting Alerts........................................................................................... 50
Resetting the Alert email text................................................................. 51
Appendix A
Appendix B
Index
Communication Ports
53
55
55
56
Preface
PREFACE
As part of an effort to improve its product lines, EMC periodically releases revisions of its
software and hardware. Therefore, some functions described in this document might not
be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function properly or
does not function as described in this document.
Note: This document was accurate at publication time. Go to EMC Online Support
(http://support.emc.com) to ensure that you are using the latest version of this document.
Purpose
This document describes how to configure and use the EMC Monitoring and Reporting
Suite.
Audience
This document is intended for VNX and VNXe storage administrators and IT generalists
who will be involved in managing VNX Family Monitoring and Reporting.
DANGER indicates a hazardous situation which, if not avoided, will result in death or
serious injury.
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.
CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not
avoided, could result in minor or moderate injury.
NOTICE is used to address practices not related to personal injury.
Note: A note presents information that is important, but not hazard-related.
Preface
IMPORTANT
An important notice contains information essential to software or hardware operation.
Typographical conventions
EMC uses the following type style conventions in this document:
Bold
Italic
Monospace
Use for:
System output, such as an error message or script
System code
Pathnames, filenames, prompts, and syntax
Commands and options
Monospace bold
[]
{}
...
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications. Send your opinions of this document to:
[email protected]
CHAPTER 1
Introduction
This introduction includes the following topics:
Introduction
Introduction
Introduction
Out-of-the box Dashboards summarize information in the form of graphs, charts, and
tables. Dashboards enable you to quickly pinpoint utilization and performance
problems. From this top perspective, you can drill down to underlying reports to get
more detailed views of a selected component. Individual users can arrange the layout
of the dashboard to suit business requirements.
Reports can run on-demand. Report options include graphs and tables and output formats
include CSV, XLS, XML, and PDF.
Built-in dashboards and reports include:
VNX Block Reports
Cache performance
Introduction
Administration
The Administration area is where the Monitoring and Reporting administrator manages
day-to-day tasks from a simple web interface. This allows you to manage user roles and
profiles, monitor the health of the Monitoring and Reporting server, see the status of
servers, execute tasks, configure Alerts and Chargeback, and perform install and upgrade
operations.
Architectural Overview
The Monitoring and Reporting architecture includes the following components:
The Data Collector
Stores the data collected from the data sources. The database module is
self-maintaining and provides multiple automations. For example, data
aggregation is performed for report acceleration and data retention is
managed for storage optimization.
Please refer to Appendix B, Communication Ports, for the list of ports used by the
application.
10
CHAPTER 2
Installing
This chapter discusses information and procedures for the following topics:
Installing
12
14
17
18
18
11
Installing
2-3 systems
Up to 10 systems
Browser Requirements
The VNX Family Monitoring and Reporting web portal is compatible with the following
browsers:
12
Firefox (latest)
Chrome (latest)
Installing
Supported Platforms
VNX Family Monitoring and Reporting is compatible with array products listed in the
following table:
Model
VNXe 3200
Operating Environment
VNXe OE 3.0
VNXe OE 3.1.0, 3.1.1
FLARE OE 4.30
Supported Languages
The VNX Family Monitoring Reporting software is available in the following languages:
English
French
For more information on setting user language preferences, refer to Edit user settings.
Installing on Windows
To install Monitoring and Reporting on Windows:
1. Double-click the install icon.
2. On the Welcome screen, click Next.
3. Read the license agreement and click I Agree.
4. Confirm the default location of the program files or click Browse to choose a different
location.
5. When the installation completes successfully, click Next.
6. Click Finish to close the set up wizard and to launch Monitoring and Reporting.
Installing on Windows
13
Installing
Installing on Linux
To install Monitoring and Reporting on Linux:
1. Open a terminal session with the root user on your server.
2. Locate the installation package you downloaded.
3. Change the permissions of the installer so you can execute it. This example is for Linux
64 bit:
# chmod +x setup-linux-x86_64-v22.sh
5. Read the EULA and press y to accept it. To scroll through the EULA, use the space bar.
6. Press Enter to accept the default directory or enter another location and y to confirm.
Enter the installation directory [/opt/VNX]:
7. Press Enter to accept the default account name or enter another one if you prefer.
Enter the user account we should create and use [vnx]:
8. Press Enter to accept the default location of service scripts or enter another location.
Enter the service scripts directory [/etc/init.d]:
9. Press Enter to accept the default location of runlevels scripts or enter another location.
Enter the runlevels base directory (containing rc[0-6].d/) [/etc]:
Deploying as a vApp
Note: Some of the vSphere menu navigation options described in this guide may vary
slightly from the options you see in vSphere. Refer to the VMware documentation for
details.
1. Download the VNX Family Monitoring and Reporting vApp files from EMC Online
Support.
2. Open the vSphere Client and connect to the vCenter server that manages your VMware
environment.
3. Select the resource pool where you want to deploy the VMs for VNX Family Monitoring
and Reporting.
4. Select File > Deploy OVF template to launch the Deploy OVF Template wizard.
5. On the Source screen, locate the M & R ovf file and click Next.
Sample: VNX_MnR_2.2.0_1VM_vApp.ovf
6. On the OVF Template Details screen, review the details and click Next.
7. Review the license agreement, click Accept, then click Next.
14
Installing
Take snapshots of the VNX M & R VM. Ensure that the datastore where the VM is
running has sufficient free space for the snapshots. Consult your VMware
administrator for more information.
1. Download the updated VNX Family Monitoring and Reporting vApp files from EMC
Online Support.
2. Validate that the checksum matches by clicking the Checksum link on the download
page and using a local utility such as md5sum to generate the checksum.
Note: Any changes that were made to the default firewall configuration by editing
etc/sysconfig/SuSEfirewall2.d/services/mr will be overwritten during the
upgrade with the original default configuration. Make a copy of this file so that you can
again make the firewall configuration updates using the
15
Installing
Stage VNX Family M & R components on the VNX M & R VM deployed using the vApp
Installer
1. Log into the VM as root.
2. Navigate to the usr/MnR_Source directory and run the post-install script:
./post_install_sh
3. Answer the questions presented in the wizard.
Installing
vnx
vnx
vnx
vnx
hard
soft
hard
soft
nofile 65534
nofile 65534
nproc 65534
nproc 65534
System start
At the end of the installation process, system services are started and your default
browser is opened to the URL where you can start configuring your system for data
collection.
If you installed VNX Family Monitoring and Reporting on a Linux server, your browser will
not open automatically. Point your browser to http://<server-name>:58080/VNX-Config to
access the configuration page, replacing <server-name> with the name or IP address of the
server where you installed the software. Monitoring and Reporting is a web application.
You can access the web portal from systems on the network that can communicate with
the Monitoring and Reporting server at this URL: http://<server-name>:58080/VNX-MR.
IMPORTANT
The first time you log in, the default user name is admin and the default password is
changeme.
See Chapter 3, Administration tasks, for detailed information on how to configure and
troubleshoot your system.
System start
17
Installing
Uninstalling
To uninstall Monitoring and Reporting for Windows:
1. Go to Start > Control Panel > Uninstall a program.
2. Double-click on the program icon. Proceed through the uninstall wizard.
2. Stop services
./manage-modules.sh service stop all
3. Remove services
./manage-modules.sh service remove all
Upgrading
IMPORTANT
If your Naviseccli files are installed in a custom location other than the default [Example:
C:\Program Files (x86)\EMC\Navisphere\bin\naviseccli], ensure you have reset the path to
the correct custom location after an upgrade. See the Registered Systems Page for more
information.
In-place upgrade
The in-place upgrade for 1.x to 2.x versions of Monitoring and Reporting will preserve
custom configuration settings including system settings, alerts, users, and scheduled
reports, but will not preserve historical data collected by the 1.x version of Monitoring and
Reporting.
1. Download Monitoring and Reporting for the VNX Family 2.0 from EMC Online Support.
18
Installing
2. Follow the procedures for installation for your host system, as described in English
or Installing on Linux.
3. Reconfigure Chargeback, if previously set up on the 1.x instance.
IMPORTANT
Historical data from 1.x will be preserved on the 1.x host system in the following
location: Databases/MySQL/Default/data/apg_bak. This data will not be fully
readable by the 2.x instance of Monitoring and Reporting, but can be later moved to
and accessed by a host system running Monitoring and Reporting 1.x. As this folder
can take up considerable file space, it is recommended that you remove or archive
this folder if you do an in-place upgrade to 2.x.
Fresh Installation
Fresh installation of Monitoring and Reporting 2.x will require a separate host system from
that which is running Monitoring and Reporting 1.x. Running Monitoring and Reporting 1.x
and 2.x on two separate systems is recommended if you need to preserve and access
historical data from 1.x. You can discontinue use of the first host running 1.x once the 2.x
instance has collected sufficient historical data for your system(s).
1. On the 1.x host system, stop the VNX Collector service. Leave all other services
running.
2. On a new system, download Monitoring and Reporting 2.x from EMC Online Support.
3. Follow the procedures for installation for your host system, as described in English
or Installing on Linux.
4. Reconfigure all previously customized settings, including system settings, alerts, user
settings, Chargeback, and scheduled reports.
Upgrading
19
Installing
20
CHAPTER 3
Administration tasks
This chapter discusses administration tasks including:
22
23
24
26
26
28
31
35
36
These functions are available only to the VNX Family Monitoring and Reporting
administrator
Administration tasks
21
Administration tasks
The navigation on the left allows you to quickly go to the page dedicated to the specific
action.
22
Home
View system status, system storage consumption, and service statuses. From the
service section, you can click a given service to start or stop it.
Licenses
Systems
List configured systems with their main properties. From this section, you can
click on a given system to edit it.
Add New
Create a new system entry and open the corresponding configuration page.
Administration tasks
The home page also shows data storage usage and allows you to control the services
required to operate the application. The following table lists the system services and their
functions.
Alerting
Backend
Receives raw data from the collection service and prepares data to be
stored in the database.
Collecting
Database
Database service.
Event Processing
Gateway
Scheduler
Web Portal
Managing licenses
When you first install Monitoring and Reporting software, temporary licenses allow you to
work for 90 days. During this period, you must request permanent licenses and install
them for continuous monitoring and reporting of your storage systems.
From the management page, click Licenses on the navigation tree to access licensing
options.
From the licensing page, you can Request Permanent Licenses, Upload Licenses that you
have received, see which licenses are installed, and Delete licenses if needed. The search
box allows you to look for specific words in the license names or descriptions.
To add a license
To delete a license
1. Click the corresponding checkbox to select the license, or use All / Invert / None to
refine your selection.
2. Click Delete.
Managing licenses
23
Administration tasks
1. To add a new user, navigate to the Administration page and click Users.
2. Click New User.
3. Enter the required User Data fields. Note that Title, First Name, Last Name, and Email
Address are optional fields. In order for a user to receive automated emails from
Monitoring and Reporting, such as Schedule Reports, the Email Address field must be
complete.
Description
Edit
Copy
Copy a user to a new row. You will be required to enter the User Data.
Test User
Test and preview user settings by logging in as if you were that user.
Disable
Delete
IMPORTANT
To reset user passwords, follow the instructions in Edit an existing user to update the
password fields under User Data.
24
Administration tasks
25
Administration tasks
Adding/Editing a System
The Adding a System and Editing a System pages are where you specify the information
required in order for Monitoring and Reporting to access your storage systems. You need
to specify a unique name that will be used to identify this storage system and the type of
data collection - Integrated Unified, Unified, Block-only or File-only - that should be
applied to this unit. For Gateway systems, the data collection type should be File. Unified
data only applies to integrated VNX systems that contain both block storage (SAN) and file
storage (NAS) hardware components. Integrated Unified systems applies only to
Next-Generation VNXe systems (VNXe3200). Mandatory fields are indicated with a red
asterisk. Supported legacy CLARiiON CX4 and Celerra NS systems can also be added from
this screen.
Note that it can take a few minutes before you can see information from a newly added
system in the reporting portal. The software needs to poll the new system at least once to
add metric information to the database.
When adding a system to Monitoring and Reporting, a Block or VNXe user account with the
role of Operator is required to collect the configured Block data. A File local user account
(such as nasadmin) is required to collect the configured File data. The selected user must
be able to connect to the system using ssh for the collection mechanism to work, using
group (role) administrator, fullnas, root, or storage. The VNX or CLARiiON array must be
configured with Statistics logging enabled in order to provide all metrics to VNX
Monitoring and Reporting.
Block Collecting Information:
SP A/B IP
User Scope
Naviseccli Username
Naviseccli Password
26
Control station IP
Username
Password
Administration tasks
Username
VNXe username.
Password
VNXe password.
Configuring Mail
VNX Family Monitoring and Reporting offers the option of emailing reports and alerts to
users. This requires configuration of a valid SMTP (mail) server.
1. In the main configuration page, click the Global Settings button.
2. In the SMTP Host box, enter the name or IP address of the mail server. This may
require the help of your local system administrator, especially if the default port 25
does not work or if the mail server requires a specific authentication scheme.
IMPORTANT
In order to receive emails, user profiles must include a valid email address.
Configuring Mail
27
Administration tasks
Alerting
There are a variety of predefined alerts, which you can configure to trigger based on when
certain performance thresholds are violated. You can also configure the alerts to trigger for
only certain components, such as specific LUNs or SPs. Alerts are sent to Monitoring and
Reporting users by email or captured by SNMP trap.
For example, for the LUN Response Time alert, you can set up an alert to trigger whenever
a LUN response time is greater than 1 millisecond. Although the alerts are pre-defined, the
threshold value and operator are set by the user. You can further configure this alert to
trigger only when this threshold is surpassed for specific LUNs on specific systems.
There are five main components to configuring alerts: Configurable Data Filtering, where
you can apply the alert to only certain components, Constant Comparator Operation,
where the threshold condition is configured, Mail Action, where the email action is
configured, SNMP v1Trap: SNMP Trap - Set, where the SNMP trap information is set, and
SNMP v1 Trap: SNMP Trap - Clear, where the SNMP information is re-entered in order to
clear the trap when the alert condition is no long occurring.
Note: Monitoring and Reporting does not support customization of community strings.
The community string is enforced as default.
IMPORTANT
In order to receive email alerts, you must have email configured. Refer to Registered
Systems Page for more information.
Enabling Alerts
Configuring Alerts
1. Click on the alert name on the Alert Definitions page and select Configure. You can
also click on the alert name in the alert tree to go to the configuration page for that
alert.
2. In the Configurable Data Filtering section, you can enter the specific components
to which to apply the alert threshold.
a. To apply the an alert to all components, leave the Selection drop-down option set
to all.
28
Administration tasks
b. To apply the alert to only certain components, set the Selection drop-down to
some. Click the Add values button. A pop up window will appear, displaying all
components to which you can apply the alert. Use the checkboxes to select the
components and click Ok. This window also has a search bar which enables you to
search for your components more quickly.
For example, for the LUN Response Time alert, you can select which LUNs to which
you want to apply the alert.
3. In the Constant Comparator Operation section, enter the Constant value of the
threshold condition and the Operator. For the list of available operators, refer to
Table 2, Available Operators,. For the list of constant value units for each alert,
refer to Table 3, Alert Constant Value Units,.
Table 2 Available Operators
Operator
Description
<
Less than
<=
Equal to
>
Greater than
>=
!=
Not equal to
4. In the Mail Action section, enter the email address of the user(s) to whom the alert
should be sent. Recipient email addresses should be separated by a comma.
Alerting
29
Administration tasks
5. In the SNMP v1 Trap: SNMP Trap - Set section, enter the Host IP address and Port
for the SNMP Trap.
6. In the SNMP v1 Trap: SNMP Trap - Clear section, reenter the Host IP address and
Port. This will clear the trap when the alert condition is no longer being met.
7. Click Save.
IMPORTANT
Generally, you should not change the default Message template for the Alert emails. The
contents of the message are designed to tell you exactly where the alert condition has
been violated and the actual value which triggered the alert. For information on how to
reset the Alert email message, refer to Resetting the Alert email text on page 51.
Available Alerts
Table 3 Alert Constant Value Units
30
Alert Name
Unit
milliseconds
Administration tasks
Data Enrichment
Data Enrichment allows you to add metadata to the metrics collected by Monitoring and
Reporting in order to enhance, or enrich, the data. Data Enrichment is located on the
Administration page under Centralized Management.
Chargeback
Chargeback is a feature which uses Data Enrichment to determine the data cost-of-service
of a business unit or application and displays it in the form of Chargeback Reports. There
are two main components to configuring Chargeback: Business Unit and Cost. You can
associate particular LUNs on an array with a business unit, application, and application
owner. You then assign a cost value per gigabyte used for LUNs belonging to a certain RAID
type and tier. Optionally, you can also specify cost per LUNs of a certain RAID type and tier
on a specific array model. Chargeback will apply this cost to each gigabyte of data used by
a LUN that meets the criteria you have defined for each business unit.
For example, logical unit number (LUN) 0 can be associated with the Development
Business Unit. In the Cost section, you can configure any LUNs on a VNX5700 array with a
RAID5 RAID Type which are part of the Performance Tier to incur a cost of $3.14 per GB
used. If LUN 0 is a RAID5 LUN on the Performance tier on a VNX5700 array, the
cost-of-service of the Development Business Unit will be $3.14 per GB used. The
Chargeback Reports display the cost of service over time.
Multiple LUNs can be associated with a single business unit. Chargeback reports calculate
the total cost-of-service of each business unit. For example, if a business unit is configured
to have multiple LUNs, the cost per GB of each of those LUNs will be added to the total
cost of service of the business unit.
You can also associate mixed LUNs with a particular business unit. Chargeback will
calculate cost based on the percentage of storage allocated for that LUN by tier and RAID
type.
There are several Chargeback reports which represent cost-of-service. These include Top
10 Applications by Cost, Top 10 Applications by capacity, Cost distribution by business
unit, Cost per Business Unit, and Cost per Business Unit and Application.
To add a new Business Unit or Application to Chargeback:
1. Go to the Administration page.
2. Select Data Enrichment under Centralized Management.
3. Click localhost :: Default :: Data-Enrichment from the navigation tree on the left.
4. Expand the Business Unit section.
5. Add a new row by clicking the add/delete rows icon in the left-most column of an
existing row and selecting Insert before or Insert after, depending on your
preference
Data Enrichment
31
Administration tasks
Value
System Name
Object Name
Add the name of the LUN. Use the format Logical Unit
Number X where X is the LUN number.
Business Unit
Application Name
Application Owner
7. Click Save.
To enter Cost:
1. Expand the Cost section. Rows will be pre-populated for each RAID Type and Tier
combination. You will need to update the System Model and Cost column entries
for each row.
2. Click an existing row in the System Model column. Enter the device model of the
array. To apply the same Chargeback costs to each RAID type and tier for all array
models, leave the default value of .* in this column.
32
Administration tasks
3. Click an existing row in the Cost column. Edit the default value to the appropriate
cost per GB for that RAID type on that tier.
Note: Cost values cannot include decimals.
Value
System Model
Data Enrichment
33
Administration tasks
Value
RAID Type
Enter the RAID Type of the LUNs to which you are applying a cost
value:
RAID5
RAID6
RAID10
Tier Name
Enter the Disk Type of the LUN to which you are applying a cost
value:
Capacity
Performance
Extreme Performance
Cost
Enter the cost value per gigabyte used by LUNs on that model
and Tier with that RAID type.
3. Click Save.
IMPORTANT
If you are configuring Chargeback for mixed LUNs, be sure to associate costs with each tier
and RAID type combination for those LUNs in the Cost section.
Do not use the delete buttons to remove any existing columns from Chargeback. Doing so
may prevent the Chargeback reports from working correctly. Do not use the New Tagging,
Add new key or Add new property buttons.
34
Administration tasks
apg
master
storage
topology
Databases
Custom
Backing up these two directories will back up the following configuration files:
Retention parameters
Collector configurations
Filters
Listener configurations
Databases connection strings
Third party connections parameters
Scripts
Logs
Temporary files
35
Administration tasks
Retention parameters
Monitoring and Reporting collects new metrics every 5 minutes. This raw data is
accumulated in hourly, daily and weekly aggregates that are used to display data on
various time horizons. The retention policy for raw data and aggregates can be found in
the table below. For example, Monitoring and Reporting allows you to report on weekly
data for up to four years in the past.
36
Accumulation period
Retention period
15 days
hourly
92 days
daily
365 days
weekly
4 years
CHAPTER 4
Viewing Reports
This chapter discusses the following topics:
38
40
41
43
44
47
These features are available to all VNX Family Monitoring and Reporting users.
Viewing Reports
37
Viewing Reports
The menu bar on the top right of your display offers a collection of tools:
38
Display options
Export reports
Report tools
Viewing Reports
Links to other reports in the template section of the report tree. You can add
favorites as you browse the tree.
Scheduled Reports
My Reports
39
Viewing Reports
1. In the Search box, type the keywords for the component and press Enter.
2. Click on the name of the system or component, or click Show all, and then the name of
the system or component for which you want to view reports.
40
Viewing Reports
Display options
Information is presented in pre-configured graphics or tabular reports. The Display menu
on the top of the dashboard allows you to change the display options for finer
examination.
To change the report display options
1. From the Time Selection area, choose the type of aggregation the report uses and the
time range it covers.
2. From the Display ___ values list, choose an aggregate time period.
Real-time values are aggregated as they are collected. Other aggregation time periods
are available. The defaults can be changed by your administrator. The defaults are:
3. From the Using ___ Aggregation list choose the type of aggregation you want to use.
4. From the time range list, select the time period the report will cover. You can use the
Time Range Quick Switch arrows to choose the previous or next periods.
5. Choose a value from the Over field if you are using a custom range.
Previous: selects the entire previous range. For example, the previous day is from
midnight to the midnight the day before, and the previous one month includes the
entire month's time, so if it is now September 10th the period would include all of
August.
Last: selects one range back from now. For example, the last day extends from the
current time back 24 hours, and the last month extends from the current day back
a period of one month.
Current: selects the current range. For example, the current day extends from the
last midnight through to the current time and forward to the next midnight, and the
current month extends from the first of the current month to the last day of the
month.
6. From the second field, select a time range. You can choose a pre-defined value or
period. For greater accuracy, you can select custom or calendar.
For calendar, specify the start and end times of the report.
Display options
41
Viewing Reports
For custom, specify a duration using numbers and units. There is no limit to the
number of units, but each unit can be present only once. For example, 1h45m is
translated as 1 hour and 45 minutes.
7. To lock the time frame, click the lock icon. If you lock the time frame, the time
selection parameters that you chose are applied to every report you view during the
current session. This can be used for obtaining snapshots-in-time in order to compare
equivalent graphs for a device.
8. From the Actions area, choose the actions you want to take. Click Apply or your
changes will not take effect.
Choose View in Full Page to display only the contents of the reports currently in the
page area in a new browser tab or window. Other user interface elements,
including the report menu, do not appear.
Choose Revert to Default to revert the report to its default settings. The Revert to
Default option can also be used to refresh the report that is currently displayed.
Note: For Heat Map reports, you cannot click directly on the graphical interface to change
the view or parameters. The default view is static.
42
Viewing Reports
Export reports
Reports can be exported into various formats. The export formats available will vary
slightly from report to report. Unavailable export options will be greyed-out.
To export a report
1. Select the node for the report you want to export.
2. On the Report menu, click Export.
Export formats
PDF document
Creates a PDF and opens it in a window where you can save it or print it.
CSV format
Exports the report in a CSV file. If this is a multipart report, each part is
prepended with a commented line containing the tile of the part. For
graphs, data is exported according to the graph type.
XLS format
PNG, JPEG or SVG image Creates an image of the report's first graph. If there is no graph on the
exported report, an empty image is generated.
XML format
Export reports
43
Viewing Reports
Report tools
The Tools menu gives you access to the Report Wizard and has tools for printing, emailing
reports and adding them to your Favorites.
44
Report Wizard
Opens the Report Wizard from which you can create a new report.
Replaces the current URL with the complete report URL. This enables
you to create a bookmark for this page or directly link to it.
Adds the current report to the Favorite Reports. These reports are
listed on the top of the tree for quick access.
Viewing Reports
2. From the View Type list select a view type. The available views are defined by the
systems administrator.
3. In the Available Elements area, select elements to filter on. You can click the filter icon
and start typing the name of an element to filter the list. Continue to choose elements
until you define all the elements you want included.
4. If you can select more metrics to add to the report, the Add Metrics button becomes
available. You can click it and repeat steps 3 and 4 until you have all the metrics you
want to add to your report.
5. Click Run to generate the report.
Report tools
45
Viewing Reports
3. Click Run. You can save the report to My Reports to rerun it.
46
Viewing Reports
Scheduling Reports
Reports can be scheduled to be generated at specific times and delivered by email to
recipients as PDFs. Whenever a report is scheduled to be generated, it queries the
database for the latest data.
To schedule a report:
1. Browse to the report you would like to schedule using the Report Tree.
2. Go to Tools > Schedule this Report.
3. On the Scheduling tab of the New Scheduled Report window, enter the name of the
scheduled report, select how frequently the scheduled report should generate,
and select the time zone.
Scheduling Reports
47
Viewing Reports
4. On the Email tab, enter the email addresses of the recipients for the scheduled
report.
5. Click Save.
Note: Scheduled reports maintain the default display settings. To schedule a report with
modified display settings, such as a custom time range, click Save modified report rather
than Save.
Modifying a
scheduled report
1. In the report tree, click Scheduled Reports. A list of scheduled reports will display
in the main window.
2. Click on the name of the report you want to modify. A list of several options will
appear, including Edit. Click Edit to modify the report settings.
3. On the Editing Scheduled Report screen, update the report name, schedule, and
email recipients as needed. Click Save.
48
CHAPTER 5
Troubleshooting
The content of this document describes the paragraph tags, character tags, and
cross-reference formats supported in this chapter template.
Troubleshooting
49
Troubleshooting
Common Issues
The following table lists common issues:
Ensure that:
No firewall is blocking access between the server running data
collection and storage systems
All Monitoring and Reporting services are up and running,
Database storage has disk capacity
The server date and time are accurate
Your storage systems are available and accessible for the
application
Ensure that:
You are accessing the right URL and port:
http://portal_ip:58080/VNX-MR
All passwords are case sensitive. Confirm that you do not have
CAPS LOCK on and that you are entering your password with the
correct case.
Ensure that:
All Monitoring and Reporting services are up and running
You tried the portal IP instead of its hostname in the URL
Your browser proxy settings are correct (check with your local
administrator)
Resetting Alerts
Resetting alerts can be used to reset the configuration for all alerts, including the alert
email template. To reset only the alert email text, refer to Resetting the Alert email text
on page 51.
IMPORTANT
Resetting the alerts will remove any existing alert configuration. For example, if you have
configured some alerts to trigger for only certain components, such as only certain LUNs,
this configuration will be removed when you reset all alerts.
On Linux:
1. Remove the existing alert configuration file:
rm/opt/VNX/Backends/Alerting-Backend/Default/conf/alerting.xml
3. Stop and restart Alerting services. From the Monitoring and Reporting Home page,
Select Alerting > Stop Process.
4. Select Alerting > Start Process.
50
Troubleshooting
On Windows
1. In Windows Explorer, navigate to Program Files > VNX > Backends > Alerting-Backend >
Default > conf.
2. Delete the existing alert configuration xml file alerting.xml.
3. Create a new alert configuration file by opening a command prompt window and
entering the following command:
/opt/VNX/bin/manage-modules.sh update alerting-backend
4. Stop and restart Alerting services. From the Monitoring and Reporting Home page,
Select Alerting > Stop Process.
5. Select Alerting > Start Process.
3. Click Save.
Description
Example
device
System Name
Array 123
parttype
Component type
LUN
part
Specific component
LUN 101
unit
Resetting Alerts
51
Troubleshooting
52
APPENDIX A
Available reports and metrics
VNX Block/CLARiiON (All Reports)
Parent
Report Name
Description
Storage Processor
Utilization (%)
Storage Processor
Utilization (%)
Dynamic
expansion on all
controllers
Block Usable
Capacity
Distribution by
Model
Distribution by
Version
Dynamic
expansion on all
arrays
Inventory
Inventory
Dynamic
expansion on
device types
Performance
Performance
Performance
LUN Performance
Bottleneck
Performance
Storage Processor
Write Cache
Performance
Performance
Performance
Disk Utilization
Heat Map
Performance
SP Utilization Heat
Map
Capacity Planning
53
54
Parent
Report Name
Description
Capacity Planning
Space Capacity
Planning
Capacity Planning
Storage Pool
Capacity Planning
This report shows when you should expect an array to reach its
full disk capacity.
Health
Health
Arrays Compliance
Forecast
This report shows disk arrays availability and offers SLA results
for the last month.
Health
Broken Disks
Chargeback
Reports
Chargeback Reports
Top 10 Application
by Cost
Chargeback Reports
Top 10 Application
by Capacity
Chargeback Reports
Cost distribution
by Business Unit
Chargeback Reports
This report displays the cost per business unit over the last four
months.
Chargeback Reports
This report displays the cost per business unit, application, and
application owner over the last four months.
Report Name
Description
Dynamic expansion
on all servers
Protocol Overview /
DM
Protocol Overview / DM
Dynamic expansion
on all servers
Dynamic expansion
on serial numbers
Capacity
Capacity
All Filesystems
Capacity
Deduplication
Capacity
Filesystems and
Savvol Utilization
Capacity
Filesystsm Used
Forecast
Capacity
Savvol
Performance
Performance
CIFS open
Connections
Performance
Performance
CIFS Ops/s
Performance
NFS Ops/s
Performance
Performance
Inventory
Inventory
Data Movers
Inventory
FileSystems
Inventory
NFS Shares
Inventory
CIFS Shares
Inventory
ControlStation
Inventory
System
55
56
Parent
Report Name
Description
VNXe
Capacity
Capacity
Raw Capacity
Capacity
Usable Capacity
Capacity
Capacity
Capacity
Capacity
Parent
Report Name
Description
Capacity
Capacity
Capacity
Capacity
Performance
NAS Servers
Performance
LUN / Summary
Performance
Disks / Summary
Performance
Storage Pools
Performance
Performance
Throughput
Performance
Shares
Performance
Performance
Performance
FAST VP / Summary
57
58
APPENDIX B
Communication Ports
The following table lists IP ports used by VNX Family Monitoring and Reporting services.
TCP port 58080 must be open between browsers and the VNX Family Monitoring and
Reporting server for browsers to access the application.
Port
Service
TCP/2000
Backend
TCP/2001
Backend
TCP/48443
Gateway
TCP/53306
Database
TCP/58080
Web Portal
The following table lists IP ports used by VNX Family Monitoring and Reporting to access
arrays. These ports need to be opened from Monitoring and Reporting to VNX and VNXe
arrays.
Port
Technology
TCP/443
TCP/22
Communication Ports
59
Communication Ports
60
INDEX
administrative tasks 22
Alerting 28
architecture 10
backup 35
time drift
display options 41
time frame 42
lock 42
tools 44
tree
minimize 39
Troubleshooting 49
C
Chargeback 31
D
Data Enrichment 31
display options
apply change 42
drift 41
full page 42
E
Export 43
F
Favorite reports 39
full page, report 42
U
URL 17
user name 17
V
VNX Block Reports 9
VNX File Reports 9
VNX Monitoring and Reporting 8
VNX System
add 26
edit 26
H
hardware requirements 12
I
Installation 13, 14
L
licenses 23
lock time frame 42
P
password 17
R
refresh 42
report
display options 42
full page 42
Report Wizard 45, 46
search 40
view in full page 42
report tree 38, 39
Report Wizard 45, 46
Index
61
Index
62