EMC VPLEX Performance Request

Document v4

Due to the nature of where VPLEX is located in your SAN environment VPLEX
interfaces with hosts, switches and storage-arrays; because of this, VPLEX
performance investigations require analysis of not just VPLEX, but each of these
components. As part of this investigation it is necessary to collect as much detailed
information about your issue and about your environment as possible in order to
ensure a focused and efficient investigation from start to finish.

Please fill out the following fields:

Company:
Date:
Service Request
Number:
Contact Name:
Email/Phone:
VPLEX Serial #:

Impact
Detailed Problem Description:

1 of 3
Version: February 2016
EMC VPLEX Performance Request
Document v4

Business Impact, e.g. users

impacted, jobs running slow,
application crashes, etc.:
Please provide any existing EMC
Service Requests related to this
issue:
How are you measuring the
performance issue?

What are the expectations for your

VPLEX environment in regards to
performance?, e.g. we expect to
see latency under "x" milliseconds
or backups are taking longer than
expected.
Please provide a list of affected
storage-views:

Please provide a list of affected

virtual-volumes. If there are a large
number, please provide the top 5
impacted volumes:

Are the affected devices local or

distributed?
Are the affected volumes protected
by RecoverPoint?
Please provide a list of affected OS
types and levels:

2 of 3
Version: February 2016
EMC VPLEX Performance Request
Document v4

Please provide a list of affected

applications:

What type of multipathing are you

using and what version? e.g.
PowerPath, NMP (Native
Multipathing)

Timing
When did/does the problem
happen [date/time/timezone]?
Is the issue intermittent or
ongoing?

If intermittent does it happen at

predictable intervals, e.g.
everyday from 1300-1700
Please provide the time
difference between affected
hosts and VPLEX.
Environment
Have there been any recent
changes in the environment, e.g.
new equipment, maintenance,
upgrades, migrations, etc.?
If possible, please provide a
topology/network diagram of
your environment. (can be
attached to the SR)
Are there any ongoing
network/SAN issues e.g. WAN link
down, connectivity errors, VPN
issues?

Due to where VPLEX sits in your environment, VPLEX performance investigations

often span multiple products, including hosts, switches, and backend arrays.

The following logs are necessary to Please indicate if the following logs have
investigate VPLEX performance been provided. If not, please provide an
issues ETA for when each log will be uploaded

3 of 3
Version: February 2016
EMC VPLEX Performance Request
Document v4

VPLEX collect-diagnostics
[see KB 13282]

Host grabs from a sample of affected

hosts
[see KB 31922]
If your switches are serviced by EMC,
switch logs (If Cisco, show tech-
support details, if Brocade,
supportsaves) from both the front-end
and back-end of the VPLEX environment
[see KB 8372]

If known, please indicate the storage

arrays involved. Support will provide
further details on collecting appropriate
logs if necessary
Please note: all performance data collected must be uploaded to the EMC Service
Request via EMC Service Center either when creating the Service Request or by
accessing the Service Request using the My Support option. Alternatively, EMC
can provide a FTP link upon request

4 of 3
Version: February 2016
EMC VPLEX Performance Request
Document v4

This page intentionally left blank

5 of 3
Version: February 2016
EMC VPLEX Performance Request
Document v4

---For VPLEX Support Use Only---

Below will be the support notes, next actions and recommendations as they become
available

Edit the dates below as applicable. If this case is received on a turnover or re-queue, please
do not delete information in the fields below, simply add the date, your shift GEO and what
has changed or what was done during your shift. If changes are made, please upload
this document to the SR at the end of your shift.

Current Status/Next Actions:

<01 Jan 2016, AMER Shift>

6 of 3
Version: February 2016
EMC VPLEX Performance Request
Document v4

Case notes/Evidence:

<01 Jan 2016, AMER Shift>

7 of 3
Version: February 2016
EMC VPLEX Performance Request
Document v4

VPLEX Recommendations:

<01 Jan 2016, AMER Shift>

Host Team Recommendations:

<01 Jan 2016, AMER Shift>

Connectivity Team Recommendations:

<01 Jan 2016, AMER Shift>

Array Team Recommendations:

<01 Jan 2016, AMER Shift>

8 of 3
Version: February 2016