Vplex

EMC VPLEX
GeoSynchrony
Configuration Guide
P/N 300-012-310
REV 07
Copyright 2010- 2015 EMC Corporation. All rights reserved. Published in the USA.
Published January, 2015
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, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage
Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic
Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra,
Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation
Technology, Common Information Model, Configuration Intelligence, Connectrix, CopyCross, CopyPoint, CX, Dantz, Data Domain,
DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab,
EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File
Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, InputAccel, InputAccel Express, Invista,
Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, OnAlert, OpenScale, PixTools, Powerlink, PowerPath,
PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, SafeLine, SAN Advisor, SAN Copy, SAN
Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix,
Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, Viewlets, Virtual Matrix, Virtual Matrix
Architecture, Virtual Provisioning, VisualSAN, VisualSRM, VMAX, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression,
xPresso, YottaYotta, the EMC logo, and the RSA logo, are registered trademarks or trademarks of EMC Corporation in the United States
and other countries. Vblock is a trademark of EMC Corporation in the United States.
VMware, is a registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.
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 the technical documentation and advisories section on the
EMC online support website.
EMC VPLEXConfiguration Guide
CONTENTS
Chapter 1
Cautions and Warnings
Chapter 2
Preface
Audience................................................................................................. 9
Related documentation ........................................................................... 9
Conventions used in this document ...................................................... 10
Where to get help.................................................................................. 11
Your comments ..................................................................................... 11
............................................................................................................. 11
Chapter 3
Verifying Operations
Verifying operation...................................................................................... 13
Chapter 4
Configuring a VPLEX Local implementation

Overview.....................................................................................................
Setup procedure .........................................................................................
Perform preliminary tasks .....................................................................
Set the public IP address.......................................................................
Reference: Reverting the setup....................................................................
Chapter 5
Configuring a VPLEX Metro or VPLEX Geo implementation

Overview.....................................................................................................
Setup procedure .........................................................................................
Prerequisites.........................................................................................
Reference: Reverting the setup....................................................................
Appendix A
40
40
49
70
Upgrading an Unconfigured System

Before You Begin.........................................................................................
Upgrade the Management Server (no OS Upgrade) ......................................
Upgrade the Management Server (with OS upgrade)....................................
Post Upgrading Tasks ..................................................................................
Appendix B
17
18
18
21
38
71
71
73
77
Reference
VPLEX hardware overview............................................................................ 79
VS1 hardware configurations ................................................................ 79
VS2 hardware configurations ................................................................ 83
IP addresses and component IDs ................................................................ 86
VPLEX VS1 hardware ............................................................................. 87
VPLEX VS2 hardware ............................................................................. 89
Internal cabling........................................................................................... 90
Cabinet power connections ....................................................................... 113
UPS LEDs .................................................................................................. 114
Index
Contents
FIGURES
Title
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Page
SPS LEDs..................................................................................................................... 13
VS1 director LEDS during and after power-up .............................................................. 13
VS2 engine LEDs after power-up.................................................................................. 14
APC UPS...................................................................................................................... 14
Emerson UPS .............................................................................................................. 15
Fibre Channel switch, rear (port side) view .................................................................. 15
Management server power button and LEDs ................................................................ 15
Overview of VPLEX Local configuration tasks ............................................................... 17
Front-end and back-end I/O ports in a VS1 engine....................................................... 19
Front-end and back-end I/O ports in a VS2 engine....................................................... 19
Monitor, keyboard, and mouse ports on rear of management server............................ 21
PuTTY settings for VPLEX_service session .................................................................... 23
PuTTY configuration: SSH protocol .............................................................................. 24
PuTTY settings for logging in to Cluster 1 over the customer network ........................... 27
Unisphere for VPLEX Online Help screen: Provision Storage......................................... 35
Overview of VPLEX Metro and VPLEX Geo configuration tasks ...................................... 40
Front-end and back-end I/O ports in VPLEX VS1 engine ............................................... 42
Front-end and back-end I/O ports in VPLEX VS2 engine ............................................... 42
Monitor, keyboard, and mouse ports on rear of management server............................ 44
PuTTY settings for VPLEX_service session .................................................................... 46
Unisphere for VPLEX Online Help screen: Provision Storage......................................... 67
VPLEX VS1 hardware example: Single-engine configuration......................................... 80
VPLEX VS1 hardware example: Dual-engine configuration ........................................... 81
VPLEX VS1 hardware example: Quad-engine configuration.......................................... 82
VPLEX VS1 Engine components ................................................................................... 82
VPLEX VS2 hardware example: Single-engine cluster................................................... 83
VPLEX VS2 hardware example: Dual-engine cluster ..................................................... 84
VPLEX VS2 hardware example: Quad-engine cluster .................................................... 85
VPLEX VS2 engine modules (front view)....................................................................... 86
Component IP addresses in Cluster 1 .......................................................................... 87
Component IP addresses in VPLEX Metro or VPLEX Geo Cluster 2................................. 88
Component IP addresses in Cluster 1 .......................................................................... 89
Component IP addresses in VPLEX Metro or VPLEX Geo Cluster 2................................. 90
Ethernet cabling in a VPLEX VS1 quad-engine configuration ........................................ 92
Serial cabling in a VPLEX VS1 quad-engine configuration ............................................ 93
Fibre Channel cabling in a VPLEX VS1 quad-engine configuration ................................ 94
AC power cabling in a VPLEX VS1 quad-engine configuration....................................... 95
Ethernet cabling in a VPLEX VS1 dual-engine configuration ......................................... 96
Serial cabling in a VPLEX VS1 dual-engine configuration ............................................. 97
Fibre Channel cabling in a VPLEX VS1 dual-engine configuration ................................. 98
AC power cabling in a VPLEX VS1 dual-engine configuration........................................ 99
Ethernet cabling in a VPLEX VS1 single-engine configuration..................................... 100
Serial cabling in a VPLEX VS1 single-engine configuration ......................................... 100
Fibre Channel cabling in a VPLEX VS1 single-engine configuration............................. 100
EMC VPLEX Configuration Guide
Figures
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
AC power cabling in a VPLEX VS1 single-engine configuration ...................................

Fibre Channel WAN COM connections on VS1 VPLEX hardware ..................................
IP WAN COM connections on VS1 hardware...............................................................
Ethernet cabling in a VPLEX VS2 quad-engine configuration ......................................
Serial cabling in a VPLEX VS2 quad-engine configuration ..........................................
Fibre Channel cabling in a VPLEX VS2 quad-engine configuration ..............................
AC power cabling in a VPLEX VS2 quad-engine configuration.....................................
Ethernet cabling in a VPLEX VS2 dual-engine configuration .......................................
Serial cabling in a VPLEX VS2 dual-engine configuration ...........................................
Fibre Channel cabling in a VPLEX VS2 dual-engine configuration ...............................
AC power cabling in a VPLEX VS2 dual-engine configuration......................................
Ethernet cabling in a VPLEX VS2 single-engine configuration.....................................
Serial cabling in a VPLEX VS2 single-engine configuration .........................................
Fibre Channel cabling in a VPLEX VS2 single-engine configuration.............................
AC power cabling in a VPLEX VS2 single-engine configuration ...................................
Fibre Channel WAN COM connections on VS2 VPLEX hardware ..................................
IP WAN COM connections on VS2 VPLEX hardware ....................................................
Power connectors in a VPLEX cabinet ........................................................................
APC UPS....................................................................................................................
Emerson UPS ............................................................................................................
101
101
102
103
104
105
106
107
108
109
110
111
111
111
112
112
113
113
114
114

The following warnings and cautions pertain throughout this guide.
Warning
Trained service personnel only.
This EMC product has more than one power supply cord. To reduce the risk of electric
shock, disconnect all power supply cords before servicing.
Ground-circuit continuity is vital for safe operation of the machine. Never operate the
machine with grounding conductors disconnected. Remember to reconnect any grounding
conductors removed for or during any installation procedure.
Attention
Resrv au personnel autoris.
Cet appareil EMC comporte plus d'un cordon d'alimentation. Afin de prvenir les chocs
lectriques, dbranchez tous les cordons d'alimentation avant de faire le dpannage.
Un circuit de terre continu est essentiel en vue du fonctionnement scuris de l'appareil.
Ne mettez jamais l'appareil en marche lorsque le conducteur de mise la terre est
dbranch.
Warnung
Nur fr Fachpersonal.
Dieses EMC Produkt verfgt ber mehrere elektrische Netzanschlsse. Zur Vermeidung
eines elektrischen Schlages sind vor Servicearbeiten an der Stromversorgung alle
Netzanschlsse zu trennen.
Kontinuierliche Erdung ist notwendig whrend der gesamten Betriebsdauer des Gertes.
Es ist unzulssig das Gert ohne Erdung zu betreiben. Gert muss geerdet werden, bevor
es am Stromnetz angeschlossen wird.
Additional warnings and cautions

Before attempting to service the EMC hardware described in this document, observe the
following additional warnings and cautions:

The hardware enclosure contains no user-serviceable parts, so it should not be moved or
opened for any reason by untrained persons. If the hardware needs to be relocated or
repaired, only qualified personnel familiar with safety procedures for electrical
equipment and EMC hardware should access components inside the unit or move the
unit.

This product operates at high voltages. To protect against physical harm, power off the
system whenever possible while servicing.

In case of fire or other emergency, isolate the system's power involved and alert
appropriate personnel.

Trained personnel are advised to exercise great care at all times when working on
the EMC hardware.
Remember to:
Remove rings, watches, or other jewelry and neckties before you begin any
procedures.
Use caution near any moving part and any part that may start unexpectedly such as
fans, motors, solenoids, etc.
Always use the correct tools for the job.
Always use the correct replacement parts.
Keep all paperwork, including incident reports, up to date, complete, and

accurate.
Static precautions
EMC incorporates state-of-the-art technology in its designs, including the use of LSI and
VLSI components. These chips are very susceptible to damage caused by static discharge
and need to be handled accordingly.

Before handling printed circuit boards or other parts containing LSI and/or VLSI
components, observe the following precautions:
Store all printed circuit boards in antistatic bags.
Use a ground strap whenever you handle a printed circuit board.
Unless specifically designed for nondisruptive replacement, never plug or

unplug printed circuit boards with the power on. Severe component damage
may result.

Pasting the commands copied from the PDF document to VPLEX CLI could cause some of
the characters to change. It is recommended that you type the command at the CLI
instead.
Preface
As part of an effort to improve and enhance the performance and capabilities of its
product lines, EMC periodically releases revisions of its hardware and software. Therefore,
some functions described in this document may not be supported by all versions of the
software or hardware currently in use. For the most up-to-date information on product
features, refer to your product release notes.
If a product does not function properly or does not function as described in this
document, please contact your EMC representative.
Audience
This document is intended for use by VPLEX customers and/or EMC field personnel as an
aid in setting up a new VPLEX installation.
Persons performing the procedures described in this document should be familiar with
Linux commands and text editors.
Document Change History
Table 1
Revision
Changes since previous revision
AO2
Chapter 3 - Task 27 updated to include path to IP configuration worksheet.

Appendix A - Renamed to reflect content to Upgrading an unconfigured
VPLEX.
A03
Chapter 2 - Added new tasks to Setup procedure section, including task for
establishing call-home connectivity to EMC prior to VPLEX cluster configuration.
Chapter 3 - Added new tasks to Setup procedure section, including task for
establishing call-home connectivity to EMC prior to VPLEX cluster configuration.
Appendix B - Updated Figures 46 and 50.
A04
Added information on Emerson power supplies and fixed defects found in the
document.
A05
Added directions for upgrading an unconfigured system to Release 5.3.
A06
Changes made to support Release 5.4.
A07
Changes made to support Release 5.4.1 and general defect fixes.
Related documentation
Related documents (available on EMC Online Support) include:
EMC VPLEX Release Notes for GeoSynchrony Releases
EMC VPLEX Product Guide
EMC VPLEX Site Preparation Guide
EMC VPLEX Hardware Installation Guide
EMC VPLEX Configuration Worksheet
EMC VPLEX Security Configuration Guide
Preface
EMC VPLEX CLI Reference Guide
EMC VPLEX Administration Guide
VPLEX Management Console Help
EMC VPLEX Element Manager API Guide
EMC VPLEX Open-Source Licenses
EMC VPLEX GPL3 Open-Source Licenses
EMC Regulatory Statement for EMC VPLEX
Procedures provided through the Generator
EMC Host Connectivity Guides
Conventions used in this document

EMC uses the following conventions for special notices.
Note: A note presents information that is important, but not hazard-related.

A caution contains information essential to avoid data loss or damage to the system or
equipment.
IMPORTANT
An important notice contains information essential to operation of the software.
Typographical conventions
EMC uses the following type style conventions in this document:
Normal
Used in running (nonprocedural) text for:

Names of interface elements (such as names of windows, dialog boxes,
buttons, fields, and menus)
Names of resources, attributes, pools, Boolean expressions, buttons,
DQL statements, keywords, clauses, environment variables, functions,
utilities
URLs, pathnames, filenames, directory names, computer names,
filenames, links, groups, service keys, file systems, notifications
Bold
Used in running (nonprocedural) text for:

Names of commands, daemons, options, programs, processes,
services, applications, utilities, kernels, notifications, system call, man
pages
Used in procedures for:
Names of interface elements (such as names of windows, dialog boxes,
buttons, fields, and menus)
What user specifically selects, clicks, presses, or types
10
Preface
Italic
Used in all text (including procedures) for:

Full titles of publications referenced in text
Emphasis (for example a new term)
Variables
Courier
Used for:
System output, such as an error message or script
URLs, complete paths, filenames, prompts, and syntax when shown
outside of running text
Courier bold
Used for:
Specific user input (such as commands)
Courier italic
Used in procedures for:

Variables on command line
User input variables
[]
Square brackets enclose optional values
Vertical bar indicates alternate selections - the bar means or
{}
Braces indicate content that you must specify (that is, x or y or z)
...
Ellipses indicate nonessential information omitted from the example
Where to get help

EMC support and product information can be obtained as follows:
Product information For documentation, release notes, software updates, or information
about EMC products, go to EMC Online Support at:
https://support.emc.com
Technical support Go to EMC Online Support and click Service Center. You will see
several options for contacting EMC Technical Support. Note that to open a service request,
you must have a valid support agreement. Contact your EMC sales representative for
details about obtaining a valid support agreement or with questions about your account.
Online communities Visit EMC Community Network at https://community.EMC.com for
peer contacts, conversations, and content on product support and solutions. Interactively
engage online with customers, partners, and certified professionals for all EMC products.
Your comments
Your suggestions will help to improve the accuracy, organization, and overall quality of the
user publications. Send your opinions of this document to:
DPAD.Doc.Feedback@emc.com
11
Preface
12
CHAPTER 1
Verifying operation
1. Confirm that the LED status on each SPS module is as shown in Figure 1.
On-line enabled (if steady green) or Charging (if blinking green)
On-Battery (if steady amber)
VPLX-000313
Figure 1 SPS LEDs
The SPS On-Battery LED stays on while the SPS units fully charge (which could be
a few minutes or a few hours, depending on the state of the battery). If any amber
LED not related to the SPS recharge remains on for more than 10 minutes, confirm
that the components are cabled correctly.
2. To verify engine operation:
VS1 hardware - At the rear of the cabinet, confirm that the LED status on each
director is as shown in Figure 2.
Steady green
Blinking amber during boot-up

Off during normal operation
Blinking amber during firmware load

Blinking blue during OS load
VPLX-000315
Figure 2 VS1 director LEDS during and after power-up
VS2 hardware - At the front of the cabinet, confirm that the LEDs on each engine
are as shown in Figure 3.
13
PS power LEDs: Steady green
Engine LEDs:
Marker
Power On: Steady blue
Director LEDs:
Power On: Steady green
Marker: Blinking amber during firmware load,
Blinking blue during OS load,
Unsafe to Remove: Blinking amber during boot-up,
VPLX-000275
Figure 3 VS2 engine LEDs after power-up
3. The next two steps depend on whether or not the cluster contains Fibre Channel
switches and UPSs:
If no, proceed to step 5 .
If yes, confirm that the Online LED on each UPS (shown in Figure 4) is illuminated
(green), and that none of the other three LEDs shown in Figure 4 is illuminated.
If the Online LED on either UPS is not illuminated:
a. Push the power button, and confirm that the LED is illuminated before
proceeding.
b. If the LED still does not illuminate, confirm that neither circuit breaker (shown
in Figure 4 for APC UPS and Figure 5 for Emerson UPS) on the rear of the UPS
has triggered. If a circuit breaker has triggered, press it to reset it.
Online LED
Overload LED
UPS: Front view
On battery LED
UPS: Rear view
Power button
AC input indicators Circuit breakers

Figure 4 APC UPS
14
Replace battery LED
VPLX-00121
Overload LED
Online LED
UPS: Front view
On battery
LED
On/off button
Replace battery
LED
UPS: Rear view
AC input indicators
Circuit breakers
VPLX-000559
Figure 5 Emerson UPS
4. At the rear of the cabinet, confirm that the Power and Status LEDs (shown in Figure 6)
on both Fibre Channel switches are steady green.
Status LED
Power LED
VPLX-000114
Figure 6 Fibre Channel switch, rear (port side) view
5. Remove the bezel from the front of the management server.

6. On the front of the management server (Figure 7), confirm that the power LED is
illuminated.
If the LED is not on, press the power button.
Power button
Power LED
VPLX-000083
Figure 7 Management server power button and LEDs
Reinstall the management server bezel.
Verifying operation
15
16
CHAPTER 2
This chapter describes the tasks to set up a VPLEX Local (single-cluster) implementation.
Topics include:
Overview................................................................................................................. 17
Setup procedure ..................................................................................................... 18
Reference: Reverting the setup................................................................................ 38
Overview
Figure 8 lists the main tasks that are required for VPLEX Local configuration.
Set IP address and hostname
Verify the GeoSynchrony version
and upgrade if necessary
Verify the cluster health
Launch the EZ-Setup Wizard
Expose back-end storage *
Cluster 1
Resume the EZ-Setup Wizard

Create a meta-volume and
schedule backups
Complete EZ-setup Wizard
* NOTE: You can use the VPLEX Port

WWN Calculator to expose back-end
storage before you perform the
EZ-Setup.
(Download the calculator from
http://one.emc.com/clearspace/docs/
DOC-29929 to your laptop. Then
launch the calculator and follow the
instructions.)
Enable the front-end ports

Register the cluster
Expose storage to hosts
VPLX-000207_a
Configuration is complete
Figure 8 Overview of VPLEX Local configuration tasks
17
Setup procedure
IMPORTANT
If any command or step in this procedure does not give you the expected result and you
cannot resolve the issue, contact the EMC Support Center.
During the setup procedure, you type some commands in an SSH shell session, and some
commands in a VPlexcli session. To facilitate identification of the applicable session,
many steps in this section include one or both of the following icons. This is especially
useful in tasks where you have multiple SSH sessions opened:
Shell prompt:
VPlexcli prompt: VPlexcli
Shell
Perform preliminary tasks

Verify that four storage devices of at least 78 GB each are available for use as a VPLEX
meta-volume, a mirrored copy, and backups for the meta-volume and mirror. (The
meta-volume will contain RAID and virtual volume metadata.)
Unless only one back-end array is available, the meta-volume and its backup volume
must be on separate arrays, and should be in separate failure domains. This
requirement also applies to the mirror volume and its backup volume.
Note: If the meta-volume is on an EMC CLARiiON array, there must be active and
passive paths to all VPLEX directors from the meta-volume LUN.
Ensure that storage devices selected to support meta-volumes:
Provide a maximum average response time of 10 ms (for random 4K reads).
The best practice is to allocate dedicated spindles on the array for any LUN that will
be used as part of the meta-volume mirror.
Are clean (have zeros written)
Example of how to clean all data from the given disk:
a. Expose disk that will be used for metadata to the Linux host
b. Write zeros to the disk using the following command:

This command will erase all data on the disk.
dd if=/dev/zero of=device name conv=notrunc
For example:
dd if=/dev/zero of=/dev/sdbg conv=notrunc
Verify that all back-end array ports that will be used in the VPLEX implementation are
correctly configured as described in the applicable EMC Host Connectivity Guide.
Verify that redundant fabrics are available for connection to the VPLEX I/O ports.
18
As Figure 9 (VS1 engine) and Figure 10 (VS2 engine) show, each director should
connect to both fabrics with both the front-end and back-end ports. Connecting the
ports as shown prevents data unavailability if a single VPLEX component fails.
IOM B0
IOM B1
Director B
IOM B2
IOM B3
FC00 FC01 FC02 FC03 FC00 FC01 FC02 FC03 FC00 FC01 FC02 FC03 FC00 FC01 FC02 FC03
FE
FE
FE
FE
FE
FE
FE
FE
BE
BE
BE
BE
BE
BE
BE
BE
IOM A0
IOM A1
Director A
IOM A2
IOM A3
FE
FE
FE
FE
FE
FE
FE
FE
BE
BE
BE
BE
BE
BE
BE
BE
IOM B4
IOM B5
IOM = I/O module

FE = Front-end SAN port
BE = Back-end SAN port
IOM A4
IOM A5
= Fabric A
= Fabric B
VPLX-000209
Figure 9 Front-end and back-end I/O ports in a VS1 engine
IOM B0 IOM B1
Director B
FC03
FE
FC03
BE
FC02
FE
IOM B2
IOM B3
IOM A0 IOM A1
FC03
FE
FC03
BE
FC02
BE
FC02
FE
FC02
BE
FC01
FE
FC01
BE
FC01
FE
FC01
BE
FC00
FE
FC00
BE
FC00
FE
FC00
BE
IOM = I/O module

IOM A2
IOM A3
Director A
= Fabric A
= Fabric B
VPLX-000335
Figure 10 Front-end and back-end I/O ports in a VS2 engine
Review the Implementation and Planning Best Practices for EMC VPLEX Technical
Notes, available on EMC Online Support.
Ensure that you have an implementation design that is consistent with the
recommended best practices for VPLEX.
To successfully complete the setup, you should have reviewed best practices for
zoning, high-availability requirements, performance considerations, and other
topics for the specific arrays, hosts, or applications in your environment.
Setup procedure
19
Ensure that you understand the zoning requirements and recommendations of

your SAN switch vendor. If necessary, consult with the appropriate storage
administrator.
Review the EMC VPLEX Simple Support Matrix (available on EMC Online Support) for
specific array requirements.
Look at the VPLEX Release Notes for the release installed on your system.
Ensure that you have a laptop, desktop, PC, or similar device with a keyboard and
graphical interface (for example, a data center crash cart) for connecting to the
VPLEX management server and configuring your VPLEX cluster. For convenience, this
guide uses the term laptop to describe the device.
If you are going to use a laptop, confirm that it has the following:
Fully charged batteries, as well as an AC power cable, for assurance of power
Windows OS
PuTTY, version 0.60 or later
Note: Several tasks in this document use PuTTY for logging in to the management
server. However, you can use any similar Telnet/SSH client, but make sure you use
the SSH protocol Version 2 with any client.
WinSCP or a similar tool, in case you will need to copy files to the VPLEX
management server
If you want to use the VPLEX GUI:
Web browser: Firefox v3.5.5 or v3.5.7, or Internet Explorer 7
Adobe Flash Player 10.0.0 or higher
Download and complete the EMC VPLEX Configuration Worksheet, which is available
with other VPLEX documentation on EMC Online Support. Keep the worksheet handy
for use during the setup procedure.
During the setup procedure, you need to know the port worldwide names (WWNs) of
the Fibre Channel ports that will connect to host and storage array ports. EMC
provides a VPLEX Port WWN Calculator that simplifies this task by generating WWNs
for all I/O ports you select.
If you want to use the WWN calculator, download it from EMC Online Support, and use
it at any time before you start the setup procedure.
20
Install and launch the SolVeDesktop as directed on EMC Online Support. Then follow
the link Troubleshooting > Installation and setup, and generate a troubleshooting
document, for reference if necessary during the configuration procedure.
Set the public IP address

Before you can log in to a VPLEX management server over the customer network, you must
connect to the management server and set the public IP address. There are two possible
ways to do this:
Using a VGA monitor with PS/2 keyboard and mouse - Follow the steps in Connecting
to the console port.
Using a laptop with the hardware and software listed in Perform preliminary tasks, Follow the steps in Connecting to the service port on page 22.
Connecting to the console port

To perform this task from a VGA monitor:
1. Connect the monitor components to the management server as shown in Figure 11, in
the following order: Monitor, keyboard, mouse.
Monitor
PS/2 keyboard port
PS/2 mouse port
VGA port
VPLX-000336
Figure 11 Monitor, keyboard, and mouse ports on rear of management server
2. On the keyboard, press [Enter], and log in to the management server with username
service and password Mi@Dim7T.
3.
Shell From the shell prompt, type the following command, where hostname is a
name that will replace the default name (ManagementServer ) in the shell prompt in
subsequent logins to the management server:

Do not use the Linux OS hostname command to make this change.
sudo /opt/emc/VPlex/tools/ipconfig/changehostname.py -n hostname
4.
Shell
Type the following command, which connects you to the VPlexcli:
vplexcli
Log in with username service and password Mi@Dim7T.

5.
VPlexcli From the VPlexcli prompt, type the following command to configure the IP
address of the management servers public Ethernet port:
To configure IPv4 or IPv6 address, use the following command

For Releases prior to 5.3:
Setup procedure
21
management-server set-ip -i IP_address:netmask -g gateway eth3
For Release 5.3 onwards:

management-server set-ip -i IP_address/netmask -g gateway eth3
Note: ESRS Gateway does not support IPv6. If the unit is being configured with IPv6
addresses, the management server must have an IPv4 address assigned to it apart from
the IPv6 address. This is to enable the management server to communicate with the ESRS
Gateway. This applies to Release 5.3 and above.
6.
Type the following command, and confirm that the output shows the
correct information:
VPlexcli
ll /management-server/ports/eth3
Output example:
Name Value
-------- ------------address 10.243.48.65
gateway 10.243.48.1
net-mask 255.255.255.0
7.
VPlexcli
Shell
Type the following command at the VPlexcli prompt, and again at
the shell prompt:

exit
8. Disconnect the monitor, keyboard, and mouse from the management server.
9. From a laptop or similar device, launch PuTTY, and establish a connection to the
management servers public IP address, to confirm that the address was set correctly.
10. Proceed to Task 1 on page 25.
Connecting to the service port

To perform this task from a laptop:
1. The first step depends on whether the cabinet has a laptop tray (present only on VS2
hardware configurations:
VS2:
a. At the front of the cabinet, remove the filler panel at the U23 position
(38.5 inches up from the floor of the cabinet).
b. Slide the laptop tray out, and place your laptop on the tray.
c. Depress the tab that secures the red service cable to the tray, to loosen the
cable tie.
d. Connect the service cable to the Ethernet port on your laptop. (The other end is
already connected to the VPLEX management server.)
VS1:
a. Locate the red service cable that hangs near the right rear of the cabinet.
22
b. Connect the free end of the cable to the Ethernet port on your laptop. (The other
end is already connected to the VPLEX management server.)
2. Open a web browser on your laptop and navigate to the following URL:
http://128.221.252.2/
Follow the instructions on the web page, and then proceed to step 3.
Note: If you do not see the web page, verify that Dynamic Host Configuration Protocol
(DHCP) is enabled on your laptop.
3. On your laptop, launch PuTTY.exe.
server. However, you can use any similar Telnet/SSH client. Make sure you use SSH
protocol Version 2 with any client.
If you see a PuTTY security alert, read it, and then click yes.
4. Configure the PuTTY Configuration window as shown in Figure 12.
Type:
128.221.252.2
(default)
Type session name:
VPLEX_service
(default)
PuTTY
Figure 12 PuTTY settings for VPLEX_service session
5. Select SSH in the Category list, and ensure that Preferred SSH protocol version is set
to 2, as shown in Figure 13.
Setup procedure
23
SSH protocol
version
putty_ssh
Figure 13 PuTTY configuration: SSH protocol
6. Select Session in the Category list, and click Save in the PuTTY Configuration window
(Figure 12) to save the settings for the session you configured.
7. On the PuTTY Configuration window, click Open to establish a connection to the
management server, and log in with username service and password Mi@Dim7T.
The default shell prompt for username service is service@current_working_directory.
8.
Shell From the shell prompt, type the following command, where hostname is a
name that will replace the default name (service) in the shell prompt the next time you
open an SSH session to the management server:
Note: You can enter long Linux and VPlexcli commands faster by using the Linux tab
feature. If you start typing a command, pressing Tab at any time fills in the command
automatically, up to the point where the command might no longer be unique.
9.
Shell
vplexcli

10. VPlexcli From the VPlexcli prompt, type the following command to configure the IP
address of the management servers public Ethernet port:
For releases prior to 5.3
For Release 5.3 onwards

24
11. VPlexcli Type the following command, and confirm that the output shows the
Output example:
Name Value
-------- ------------address 10.243.48.65
gateway 10.243.48.1
net-mask 255.255.255.0
12. If you want to connect over the customer network to perform the remaining setup
tasks, then follow these steps; otherwise, continue to the next applicable task or to
Task 5 (if you want to connect to the management server over the customer network):
VPlexcli Shell Type the following command at the VPlexcli prompt, and again
at the shell prompt:
exit
Disconnect the red service cable from your laptop (leave the cable connected to
the management server). Then:
If your laptop is on a slide-out tray:
a.Remove your laptop from the tray.
b.Slip the cable back through the cable tie so that only one or two inches
protrude through the cable tie.
c.Tighten the cable tie.
d.Slide the tray back into the cabinet, and re-install the filler panel.
e.Go to the next applicable task.
If no laptop tray is present: Hang the cable near the right rear of the cabinet and
proceed to the next applicable task.
Task 1: (Optional) Establish Call-Home connectivity to EMC prior to VPLEX cluster

configuration
Note: You should perform this task only if you want early call-home connectivity to the
VPLEX cluster box and you know that there will be a delay in fully configuring the cluster. If
you are running EZ-Setup in the near future, then this task is not necessary since EZ-Setup
will configure call-home then.
Setup procedure
25

This procedure is not supported prior to 5.2. For previous releases, you can configure
call-home during EZ Setup or after the system is configured using the configuration
event-notices-reports-config command. Prior to 5.2, running this command before
EZ-Setup will result in EZ-Setup failures.
Prerequisites
To perform this procedure, the following preconditions must occur:
Cluster is in a manufactured state.
Power is applied to all components.
Public IP address is configured.
Procedure to configure Call-Home

1. Start the VPlexcli and execute configuration connect-local-directors.
2. Use the configuration event-notices-reports-config command to configure the cluster
to dial home and/or send system reports.
3. Complete the product registration using the configuration register-product command.
4. Once call-home is enabled, then issue call-home test from the
/notifications/call-home context and confirm that it was successful.
Task 2: Leaving your laptop connected or reconnecting to the management server

For the remaining setup tasks, you can leave your laptop connected directly to the
management server, or you can move to a more-comfortable location and reconnect to the
management server over the customer network:
If you want to leave your laptop connected to the management server, then
proceed to Task 4.
If you want to move your laptop to a different location and reconnect, then proceed
to Task 3.
Task 3: (Optional) Connecting to the management server over the customer network
Note: This task only applies if you want to move your laptop to a desired location, and
then reconnect to your network to configure a cluster. If this is not applicable, then
continue with configuration by proceeding to Task 4: Verify the product version.
1. Prepare for connection to the customer network:
If you want to connect to the network from your laptop, set the laptop to an IP
address on the network.
If you want to connect to the network from a different PC (or similar device):
a. Restore your laptop to the settings it had before you began this procedure
(including re-enabling any network cards).
26
b. Verify that PuTTY is installed on the device, and install it if necessary.

c. Set the device to an IP address on the customer network.
2. Launch PuTTY.exe, and configure PuTTY as shown in Figure 14.
Type the address of the
public Ethernet port on
the management server
in the first cluster you
are configuring
(default)
VPLEX service
Type a name that identifies

the cluster, such as:
VPLEX Cluster 1
(default)
PuTTY2
Figure 14 PuTTY settings for logging in to Cluster 1 over the customer network
SSH protocol
version
putty_ssh
4. Select Session in the Category list, and click Save in the PuTTY Configuration window.
5. Configure a new PuTTY session as shown in Figure 16.
Setup procedure
27

in the second cluster you
are configuring
(default)
VPLEX service
VPLEX Cluster 1

VPLEX Cluster 2
(default)
PuTTY3
8. Select the VPLEX Cluster 1 session and click Load.
9. Click Open, and log in to the management server with username service and
password Mi@Dim7T.
10. Shell From the shell prompt, type the following command to connect to the
VPlexcli:
vplexcli
11. Log in with username service and password Mi@Dim7T.

12. Proceed to the next task.
Task 4: Verify the product version

1.
From the VPlexcli prompt, type the following command to connect to all
local directors:
VPlexcli
configuration connect-local-directors
Note: This command uses the directors default name, for example, director-1-1-A.
2. Type the following command to ensure that all local directors are connected:
ll /engines/**/directors
3.
VPlexcli
version
28
From the VPlexcli prompt, type the following command:
The next step depends on the Product Version in the output:

If the Product Version is lower than the required GeoSynchrony version in the
VPLEX Release Notes, follow the steps in .Appendix A
If the Product Version matches the required GeoSynchrony version in the VPLEX
Release Notes, proceed to the applicable section:
If the VPLEX cluster contains VS1 engines, proceed to Task 7.
If the VPLEX cluster contains VS2 engines, proceed to Task 5.
Task 5: VS2 hardware only: Verify the cluster health

Before launching the EZ-Setup utility on a cluster that contains the VS2 version of VPLEX
hardware, you should verify that all components in the cluster are functioning correctly:
Note: Figure 2 and Figure 3 identify the VS1 and VS2 hardware.
1.
VPlexcli
exit
2.
From the shell prompt, type the following command (where the options are as
described following the command):
Shell
VPlexPlatformHealthCheck [option]
You can include one or more of these options:

-h, which displays the command usage.
-l path, which allows you to specify a path and filename for the health check
output. The default value is /var/log/VPlex/cli/VplexPlatformHealthCheck/.
-v, which turns on verbose mode.
In the output, confirm the following values:
Category
Values
System Information
Correct cluster size: single-engine, dual-engine, or quad-engine
Management Server IP
Connectivity Check
All OK
Local-com FC Connectivity
Check (dual-engine or
quad-engine cluster only)
FC Switch to Director Connectivity Check : OK

COM Port Power Level Check : OK
Setup procedure
29
Category
Values
Management Server
System Check
Process Check : OK
Check Partitions : OK
CPU Check : OK
Configuration Files Presence Check : OK
Baseboard Management Control Check : OK
If the system is a small system, values in this category stays same
as before
Director Health Check for

each director
All OK
Platform Health Check
Platform Health Check Found XX errors
Note: XX is a numeric value and would depend on the

configuration of the unit.
3.
Shell
Type the following command to connect to the VPlexcli:
vplexcli
Task 6: (Optional) Synchronize the time on the cluster(s) with an external NTP server
1.
VPlexcli From the VPlexcli prompt, type the following command, which
synchronizes the time on Cluster 1 with an external NTP server:
configuration sync-time f i IP_address_of_remote_NTP_server
Task 7: Launch the EZ-Setup Wizard

The EZ-Setup Wizard performs several tasks to set up a VPLEX implementation, including:
Configuring call-home notifications
Setting up SNMP for gathering performance statistics (optional)
Configuring VPLEX for authentication directory service (LDAP/AD) (optional)
Configuring VPLEX for a customized login banner using a .txt file provided by the user
(optional)
VPlexcli
Type the following command, and follow the steps in the automated interview:
configuration system-setup
Note: At any time during the interview part of the setup, you can exit EZ-Setup by typing
the command exit. To resume the setup, type the command configuration system-setup
again. EZ-Setup returns to the first step, and any values you already entered now appear
as the new default values.
Note: If you are prompted to enter the Fibre Channel switch password, type Mi@Dim7T.
30
Task 8: Expose back-end storage

To zone storage to VPLEX, you need to know the port WWNs of the back-end VPLEX ports
(the ports that connect to the storage arrays).
1. You can determine the WWNs in either of two ways:
Using the VPLEX Port WWN Calculator If you have not already done this,
download the calculator from EMC Online Support to your laptop. Then launch the
calculator and follow the instructions.
VPlexcli Using the VPlexcli Type the following command to list all director port
WWNs (identified in the command output as addresses):
ll /engines/**/ports -p
where -p enables paging mode, which displays long output one page at a time.
Note: The VPlexcli commands ll (two lowercase Ls) and ls support a paging option
that allows you to display long output one page at a time.
- To enable paging, include the option -p at the end of the command.
- To scroll from one page of the command output to the next, press the space bar.
- To exit paging mode while you are viewing paged output, press q.
(The remainder of the output appears in its entirety.)
Note: As the ll command shows, if you want a single command to affect multiple
entities (for example, directors or ports), you sometimes can use an asterisk as a
wildcard (called command globbing). The VPLEX CLI Guide provides more detail.
2. Zone the storage to the VPLEX back-end ports, following the recommendations in the
Implementation and Planning Best Practices for EMC VPLEX Technical Notes.
Task 9: Resume EZ-Setup

VPlexcli
configuration continue-system-setup
This part of the EZ-Setup finishes by rediscovering the back-end arrays. Wait several
minutes for the rediscovery to complete before you proceed to the next task.
Note: If at any point you need to reset the EZ-Setup steps you have performed, you can
revert the setup as described in Reference: Reverting the setup on page 38.
Task 10: Restart the web server if necessary

VPlexcli If you configured the cluster for authentication directory service (such as
LDAP/AD), type the following command:
webserver restart
Setup procedure
31
Task 11: Create a meta-volume

1.
Type the following command, which lists available storage volumes that
meet the requirements for a meta-volume (78 GB or larger, and unclaimed):
VPlexcli
configuration show-meta-volume-candidates
Output example:
Name
---------------------------------------VPD83T3:60000970000192601714533036464234
VPD83T3:60000970000192601714533036464235
VPD83T3:60000970000192601714533036464236
VPD83T3:60000970000192601714533036464238
VPD83T3:60000970000192601714533036464239
VPD83T3:600616037e202200d03f54035c1fe012
VPD83T3:6006016037202200d13e64035c1fe012
Capacity
-------80.1G
80.1G
80.1G
80.1G
80.1G
85G
85G
Vendor
-------EMC
EMC
EMC
EMC
EMC
DGC
DGC
IO Status
--------alive
alive
alive
alive
alive
alive
alive
Type
---------traditional
traditional
traditional
traditional
traditional
traditional
traditional
Array Name
--------------EMC-SYMMETRIX-192501423
EMC-SYMMETRIX-193601405
EMC-CLARiiON-FNM00083800045
From the output, identify four volumes to be used for the meta-volume, a mirror of the
meta-volume, and backups for both the meta-volume and the mirror. Unless only one
back-end array is visible, the meta-volume and mirror must be on separate arrays, and
should be in separate failure domains. This requirement also applies to the mirror
volume and its backup volume.
2.
VPlexcli
To create the meta-volume and a mirror, type the following command,
where:
meta-volume_name is a name you are assigning to the meta-volume.
storage-volume_1_name is the VPD (Vital Product Data) name of the meta-volume.
storage-volume_2_name is the VPD name of the mirror.
The mirror can consist of multiple storage volumes (which will become a RAID 1), in
which case you would include each additional volume, separated by commas. For
example:
storage-volume_1_name,storage-volume_2_name,storage-volume_3_name
Note: You can copy a storage volume name from the configuration
show-meta-volume-candidates output and paste it into the following command. To do
this, highlight the volume to select it, and then right-click at the point in the command
where you want to paste the volume.
meta-volume create -n meta-volume_name -d storage-volume_1_
name,storage-volume_2_name
Command example:
meta-volume create n c1_meta d
VPD83T3:60000970000192501423533036464234,
VPD83T3:6006016037202200d13e64035c1fe012
3.
VPlexcli
To display the meta-volume status, type the following command:
ll /clusters/cluster-1/system-volumes/meta-volume_name
In the output, verify that the attribute active shows a value of true.
4.
VPlexcli
To display the cluster status, type the following command:
cluster status
32
The meta-volume takes time to resynchronize with the mirror. Wait until the output
from cluster status shows an operational-status of ok before proceeding. Also verify
that there are no health indications in the output.
Cluster cluster-1
operational-status:
ok
transitioning-indications:
transitioning-progress:
health-state:
ok
health-indications:
Task 12: Back up the meta-volume

1.
VPlexcli
To schedule regular meta-volume backups, type the following command:
configuration metadata-backup
2. Answer the prompts to set a day and time to back up the metadata.
VPLEX creates two backup volumes, each named active_meta-volume_name_
backup_timestamp. Note that this process takes up to 10 minutes.
Task 13: Complete EZ-Setup

VPlexcli
configuration complete-system-setup
The EZ-Setup Wizard performs the following steps:
Initialize perpetual monitors on local directors
After the setup script has completed, the VPlexcli prompt appears.
Task 14: Register the cluster

VPlexcli You must register the cluster with EMC in order to receive service. Type the
following command, and follow the instructions:
configuration register-product

Registering this product is the only way to ensure that EMC can provide quality support.
Be sure to complete the registration and email it to EMC.
Task 15: Enable the front-end ports

VPlexcli
Type the following command:
configuration enable-front-end-ports
Setup procedure
33
Task 16: Deploy the cluster on the ESRS if necessary

ESRS must be deployed by EMC personnel. If ESRS will be used in the VPLEX
implementation, then EMC personnel should follow the procedure described in the ESRS
documentation on the GTS website, in the Application Download area, under EMC Secure
Remote Support Gateway > Implementation > Install Procedure.
Task 17: Verify the cluster health

1.
VPlexcli
health-check
2. In the output, confirm the following:

Operational Status and Health State are ok.
Operational Status and Health State of the metadata volumes are ok.
There are no unhealthy storage volumes.
Each storage volume is visible from all directors and with at least two paths.
Task 18: Expose storage to hosts

Use a VPlexcli session or the VPLEX Management Console GUI to perform this task.
Recommendations:
If a storage volume is equal to or larger than the desired virtual volume capacity,
create an extent the size of the desired virtual volume.
If a storage volume is smaller than the desired virtual volume capacity, create a single
extent per storage volume, and then use devices to concatenate or stripe these
extents into a larger device.
Create one view for each set of hosts that require access to the same storage.
You can use the VPlexcli or the Management Console GUI to expose storage. The basic
steps are the same for either:
To use the GUI, proceed to If you are using the GUI
To use the VPlexcli, proceed to If you are using the VPlexcli
If you are using the GUI

To use the GUI:
1. Open a browser and type the following, where mgmt_server_address is the IP address
of the management server's public IP port:
https://mgmt_server_address

Note: If the security message screen was enabled during system setup, a security
message appears. Read the message, and then click Continue.
34
3. Click System Status to view the status of the system, clusters, and directors. Confirm
that the health state and operational status are ok.
4. To begin provisioning and exporting storage, click Provision Storage on the main
screen of the Unisphere for VPLEX Online Help screen (shown in Figure 17).
Figure 17 Unisphere for VPLEX Online Help screen: Provision Storage
Note: To display online help and product information, click the question mark at the upper
right corner of the screen. To display documentation and additional resources for the
current VPLEX release, click Support on the navigation bar.
If you are using the VPlexcli

Note: The VPLEX CLI guide contains details on using VPlexcli commands.
To claim and name a storage volume:
1.
To display a list of available storage volumes, type the following

commands:
VPlexcli
cd /clusters/cluster-Cluster_ID/storage-elements/storage-volumes
ls
2.
VPlexcli
To claim and name a storage volume, type the following command, where:
storage_volume_name is an unique name you are assigning to the volume.

storage_volume_ID is the ID (for example,
VPD43T4:710601808cc0250018f264971e83de10) in the output from step 1 .
storage-volume claim -n storage_volume_name -d storage_volume_ID
Note: If you want to claim multiple storage volumes, separate the volume IDs with
commas or use the command storage-volume claimingwizard, as described in the
VPLEX CLI Guide.
3.
VPlexcli
To create the extent, type the following command:
extent create -d storage_volume_name
In you do not include any arguments, this command creates an extent the size of the
storage volume. However, you can create multiple smaller extents (up to 128 per
storage volume).
Setup procedure
35
Note: Extents are named and claimed automatically.

4.
VPlexcli
To verify that the extent was created, type the following command:
ls /clusters/cluster-Cluster_ID/storage-elements/extents
Output example (partial):

/clusters/cluster-1/storage-elements/extents:
extent_Symm1707_1000_1 extent_Symm1707_1001_1
extent_Symm1707_100C_1 extent_Symm1707_100D_1
5.
VPlexcli
extent_Symm1707_1002_1
extent_Symm1707_100A_1
extent_Symm1707_100E_1
extent_Symm1707_100B_1
extent_Symm1707_100F_1
To create the RAID device, type the following commands:
cd /clusters/cluster-Cluster_ID/devices
local-device create device_name -g[raid-0|raid-1|raid-c] -e
extent,extent
6.
VPlexcli
To create the virtual volume, type the following commands:
cd /clusters/cluster-Cluster_ID/virtual-volumes
create -r device_name
7.
VPlexcli
To list the initiator ports, type the following command:
ll /clusters/cluster-Cluster_ID/exports/initiator-ports

Name
-----------UNREGISTERED-0x10000000c866fff2
port-wwn
-----------------0x10000000c866fff2
node-wwn
type
------------------ ------0x20000000c866fff2 default
UNREGISTERED-0x10000000c866fff3
0x10000000c866fff3
0x20000000c866fff3
default
UNREGISTERED-0x10000000c866ffec
0x10000000c866ffec
0x20000000c866ffec
default
UNREGISTERED-0x10000000c866ffed
0x10000000c866ffed
0x20000000c866ffed
default
8.
36
VPlexcli
Target Port Names

-------------------------P000000003CA00165-A0-FC00,
P000000003CA00183-A0-FC00,
P000000003CB00165-B0-FC00,
P000000003CB00183-B0-FC00
P000000003CA00165-A0-FC01,
P000000003CA00183-A0-FC01,
P000000003CB00165-B0-FC01
P000000003CA00165-A1-FC00,
P000000003CA00183-A1-FC01,
P000000003CB00165-B1-FC00,
P000000003CB00183-B1-FC01
P000000003CA00165-A0-FC01,
P000000003CA00183-A1-FC00,
P000000003CB00165-B0-FC01,
P000000003CB00183-B0-FC01,
P000000003CB00183-B1-FC00
To register each initiator port, type the following commands, where:
initiator_port is the human readable name of the initiator port.

type is the initiator type: hpux, sun-vcs, aix, or default.
cd /clusters/cluster-Cluster_ID/exports/initiator-ports
export initiator-port register -i initiator_port -p portWWN|nodeWWN
-t type
9.
VPlexcli
To create and export the storage view, type the following commands:
cd /clusters/cluster-Cluster_ID/exports
storage-view create -c /clusters/cluster-Cluster_ID/ -n
storage_view_name -p VPLEX_port,VPLEX_port
10. VPlexcli To add each initiator port to the storage view, type the following
commands:
storage-view addinitiatorport -v storage_view_name -i
initiator_port,initiator_port
11. VPlexcli To add the virtual volumes to the storage view, type the following
commands:
storage-view addvirtualvolume -v storage_view_name -o
virtual-volume_name
12. VPlexcli To verify the status of the storage view, type the following commands:
cd /clusters/cluster-Cluster_ID/exports/storage-views
export storage-view summary
View health summary(cluster-1):
view name
health-state exported volumes
ports
----------VMware_view
view1
view2
view3
view4
----4
4
4
4
4
-----------healthy
healthy
healthy
healthy
healthy
---------------2
1311
10
11
10
registered
initiators
---------4
480
2
2
2
Total 5 views, 0 unhealthy.
Task 19: Log out of the SSH sessions

VPlexcli
Shell
Type the following command at the VPlexcli prompt, and again at the
shell prompt:
exit
Setup procedure
37
Task 20: Perform a rescan

Perform a rescan from the host, and verify that the exported virtual volumes are visible.
Reference: Reverting the setup

If at any point you need to cancel all the EZ-Setup steps you have performed, you can
revert to the pre-setup state.
Exceptions: This operation works only if no meta-volume exists and no storage is exposed
to hosts.
The operation returns your system to a pre-configured state, including:
Logically disconnecting the directors from the management server
Disabling call-home notifications if they are enabled
Disabling the front-end ports
Note that although the reset operation erases all configuration entries you have made,
those entries become the new default values when you next perform the EZ-Setup.
VPlexcli
To revert the setup, type the following command from the VPlexcli prompt:
configuration system-reset
38
CHAPTER 3
Configuring a VPLEX Metro or VPLEX Geo
implementation
This chapter describes the tasks to set up a VPLEX Metro or VPLEX Geo implementation.
Topics include:
Overview................................................................................................................. 40
Setup procedure ..................................................................................................... 40
Reference: Reverting the setup................................................................................ 70
Note: Currently, EMC personnel must perform VPLEX Metro and VPLEX Geo setup, as well
as VPLEX Witness (Cluster Witness) deployment.
39
Overview
Figure 18 lists the main tasks that are required for VPLEX Metro or VPLEX Geo
configuration.
On Cluster 1:
On Cluster 2:

Synchronize the time on the clusters


schedule backups
Register Cluster 1

schedule backups
Enable the front-end ports
Register Cluster 2
Connect to Cluster 2 and start at top
Complete EZ-Setup on Cluster 1
Complete EZ-Setup on Cluster 2

Configure the WAN COM connections
Configure the WAN COM connections
Join the clusters

Create a logging volume
Create a logging volume

Verify the health of Cluster 1
Verify the health of Cluster 2

VPLX-000208
Configuration is complete
* You can use the VPLEX Port WWN Calculator to

expose back-end storage before you perform the
EZ-Setup. (Download the calculator from http://one.emc.com/
clearspace/docs/DOC-29929 to your laptop, and then launch
the calculator.)
Figure 18 Overview of VPLEX Metro and VPLEX Geo configuration tasks
Setup procedure
IMPORTANT
If any command or step in this procedure does not give you the expected result and you
cannot resolve the issue, contact the EMC Support Center.
40
Note: You must set up both VPLEX clusters as described in this chapter. You cannot set
each cluster up individually and then join them later.
During the setup procedure, you type some commands in an SSH shell session, and some
commands in a VPlexcli session. To facilitate identification of the applicable session,
many steps in this section include one or two of the following icons. This is especially
useful in tasks where you have multiple SSH sessions opened:
Figure 2-1.
Shell prompt on Cluster 1:
Shell-1
Shell prompt on Cluster 2:
Shell-2
VPlexcli prompt on Cluster 1:
VPlexcli-1
VPlexcli prompt on Cluster 2:
VPlexcli-2
Cluster-nonspecific VPlexcli prompt:
VPlexcli
Note: The icon representing the cluster-nonspecific VPlexcli prompt indicates that you
perform the associated step on whichever cluster you want to accomplish the step.
Task 1: Perform preliminary tasks
Verify that four storage devices of at least 78 GB each are available for use as a VPLEX
meta-volume, a mirrored copy, and backups for the meta-volume and mirror. (The
meta-volume will contain RAID and virtual volume metadata.)
Unless only one back-end array is available, the meta-volume and its backup volume
must be on separate arrays, and should be in separate failure domains. This
requirement also applies to the mirror volume and its backup volume.
Note: If the meta-volume is on an EMC CLARiiON array, there must be active and
passive paths to all VPLEX directors from the meta-volume LUN.
Ensure that storage devices selected to support meta-volumes:
Provide a maximum average response time of 10 ms (for random 4K reads).
The best practice is to allocate dedicated spindles on the array for any LUN that will
be used as part of the meta-volume mirror.
Are clean (have zeros written).
Example of how to clean all data from the given disk:
a. Expose disk that will be used for metadata to the Linux host.
b. Write zeros to the disk using the following command:

Setup procedure
41

For example:
Verify that all back-end array ports that will be used in the VPLEX implementation are
correctly configured as described in the applicable EMC Host Connectivity Guide.
Verify that redundant fabrics are available for connection to the VPLEX I/O ports.
As Figure 19 (VS1 engine) and Figure 20 (VS2 engine) show, each director should
connect to both fabrics with both the front-end and back-end ports. Connecting the
ports as shown prevents data unavailability if a single VPLEX component fails.
IOM B0
IOM B1
Director B
IOM B2
IOM B3
FE
FE
FE
FE
FE
FE
FE
FE
BE
BE
BE
BE
BE
BE
BE
BE
IOM A0
IOM A1
Director A
IOM A2
IOM A3
FE
FE
FE
FE
FE
FE
FE
FE
BE
BE
BE
BE
BE
BE
BE
BE
IOM B4
IOM B5
IOM = I/O module

IOM A4
IOM A5
= Fabric A
= Fabric B
VPLX-000209
Figure 19 Front-end and back-end I/O ports in VPLEX VS1 engine
IOM B0 IOM B1
FC03
FE
FC03
BE
FC02
FE
IOM B2
IOM B3
IOM A0 IOM A1
FC03
FE
FC03
BE
FC02
BE
FC02
FE
FC02
BE
FC01
FE
FC01
BE
FC01
FE
FC01
BE
FC00
FE
FC00
BE
FC00
FE
FC00
BE
Director B
IOM = I/O module

IOM A3
Director A
= Fabric A
= Fabric B
Figure 20 Front-end and back-end I/O ports in VPLEX VS2 engine
42
IOM A2
VPLX-000335
Review the Implementation and Planning Best Practices for EMC VPLEX Technical
Notes, available on EMC Online Support.
Ensure that you have an implementation design that is consistent with the
recommended best practices for VPLEX.
To successfully complete the setup, you should have reviewed best practices for
zoning, high-availability requirements, performance considerations, and other
topics for the specific arrays, hosts, or applications in your environment.
Ensure that you understand the zoning requirements and recommendations of
your SAN switch vendor. If necessary, consult with the appropriate storage
administrator.
Review the EMC VPLEX Simple Support Matrix (available on EMC Online Support) for
specific array requirements.
Review the EMC VPLEX Release Notes (available on EMC Online Support), and keep
them on hand for reference during the configuration procedure.
Ensure that you have a laptop, desktop, PC, or similar device with a keyboard and
graphical interface (for example, a data center crash cart) for connecting to the
VPLEX management server and configuring your VPLEX cluster(s). For convenience,
this guide uses the term laptop to describe the device.
If you are going to use a laptop, confirm that it has the following:
Fully charged batteries, as well as an AC power cable, for assurance of power
Windows OS
PuTTY, version 0.60 or later
FTP client (download from SourceForge.net) and/or PSCP client
If you want to use the VPLEX GUI:
Web browser: Firefox v3.5.5 or v3.5.7, or Internet Explorer 7
Adobe Flash Player 10.0.0 or higher
Download and complete the EMC VPLEX Configuration Worksheet, which is available
with other VPLEX documentation on EMC Online Support. Keep the worksheet on
hand for use during the setup procedure.
During the setup procedure, you need to know the port worldwide names (WWNs) of
the Fibre Channel ports that will connect to host and storage array ports. EMC
provides a VPLEX Port WWN Calculator that simplifies this task by generating WWNs
for all I/O ports you select.
If you want to use the WWN calculator, download it from EMC Online Support, and use
it at any time before you start the setup procedure.
Install and launch the generator as directed on EMC Online Support. Then follow the
link Troubleshooting > Installation and setup, and generate a troubleshooting
document, for reference if necessary during the setup procedure.
Setup procedure
43
Task 2: Set the public IP address

Note: The first cluster you set up will be designated Cluster 1, and the second cluster will
be Cluster 2. Several tasks in this guide refer to the management servers on Cluster 1 and
Cluster 2 as management server 1 and management server 2.
Before you can log in to a VPLEX management server over the customer network, you must
connect to the management server and set the public IP address. There are two possible
ways to do this:
Using a VGA monitor with PS/2 keyboard and mouse - Follow the steps in
Connecting to the console port.
Using a laptop with the hardware and software listed in Task 1 - Follow the steps in
Connecting to the service port on page 45.
Connecting to the
console port
To perform this task from a VGA monitor:

1. Connect the monitor components to the management server on Cluster 1 as shown in
Figure 21, in the following order: Monitor, keyboard, mouse.
Monitor
PS/2 keyboard port
PS/2 mouse port
VGA port
VPLX-000336
Figure 21 Monitor, keyboard, and mouse ports on rear of management server
2. On the keyboard, press [Enter], and log in to the management server with username
service and password Mi@Dim7T.
3.
From the shell prompt, type the following command, where hostname is a
name that will replace the default name (service) in the shell prompt in subsequent
logins to the management server:
Shell-1

4.
Shell-1
vplexcli
44
5.
From the VPlexcli prompt, type the following command to configure the
IP address of the management servers public Ethernet port:
VPlexcli-1


6.
VPlexcli-1
7.
Type the following command at the VPlexcli prompt, and

again at the shell prompt:
VPlexcli-1
Shell-1
exit
8. Disconnect the monitor, keyboard, and mouse from the management server.
9. From a laptop or similar device, launch PuTTY, and establish a connection to the
management servers public IP address, to confirm that the address was set correctly.
10. If desired, repeat the above steps for Cluster 2. You can also opt to do this at a later
time.
11. Proceed to Task 3: (Optional) Establish Call-Home connectivity to EMC prior to VPLEX
cluster configuration.
Connecting to the service port

To perform this task from a laptop:
1. The first step depends on whether the cabinet has a laptop tray (present only on VS2
hardware configurations:
VS2:
a. At the front of the cabinet, remove the filler panel at the U23 position
(38.5 inches up from the floor of the cabinet).
b. Slide the laptop tray out, and place your laptop on the tray.
c. Depress the tab that secures the red service cable to the tray, to loosen the
cable tie.
d. Connect the service cable to the Ethernet port on your laptop. (The other end is
already connected to the VPLEX management server.)
VS1:
a. Locate the red service cable that hangs near the right rear of the cabinet.
Setup procedure
45
b. Connect the free end of the cable to the Ethernet port on your laptop. (The other
end is already connected to the VPLEX management server.)
2. Open a web browser on your laptop and navigate to the following URL:
http://128.221.252.2/
Follow the instructions on the web page, and then proceed to step 3 .
Note: If you do not see the web page, verify that Dynamic Host Configuration Protocol
(DHCP) is enabled on your laptop.
3. On your laptop, launch PuTTY.exe.
server. However, you can use any similar Telnet/SSH client. Make sure you use SSH
protocol, version 2, with any client.
If you see a PuTTY security alert, read it, and then click yes.
4. Configure the PuTTY Configuration window as shown in Figure 22.
Type:
128.221.252.2
(default)
Type session name:
VPLEX_service
(default)
PuTTY
Figure 22 PuTTY settings for VPLEX_service session
46
SSH protocol
version
putty_ssh
6. Select Session in the Category list, and click Save in the PuTTY Configuration window
(Figure 22) to save the settings for the session you configured.
7. On the PuTTY Configuration window, click Open to establish a connection to the
The default shell prompt for username service is service@current_working_directory.
8.
Shell-1 From the shell prompt, type the following command, where hostname is a
name that will replace the default name (ManagementServer ) in the shell prompt the
next time you open an SSH session to the management server:
Note: You can enter long Linux and VPlexcli commands faster by using the Linux tab
feature. If you start typing a command, pressing Tab at any time fills in the command
automatically, up to the point where the command might no longer be unique.

9.
Shell-1
vplexcli

10.
VPlexcli-1 From the VPlexcli prompt, type the following command to configure the
IP address of the management servers public Ethernet port:

Setup procedure
47

management-server set-ip -i IP_address/netmask -g gateway eth3 3
11.
VPlexcli-1
Output example:
Name Value
-------- ------------address 10.243.48.65
gateway 10.243.48.1
net-mask 255.255.255.0
12. If you want to connect over the customer network to perform the remaining setup
tasks, then follow these steps, otherwise, see the Note below and continue to the next
applicable task:
Type the following command at the VPlexcli prompt, and

again at the shell prompt:
VPlexcli-1
Shell-1
exit
Disconnect the red service cable from your laptop (leave the cable connected to
the management server). Then:
If your laptop is on a slide-out tray:
a. Remove your laptop from the tray.
b. Slip the cable back through the cable tie so that only one or two inches
protrude through the cable tie.
c. Tighten the cable tie.
d. Slide the tray back into the cabinet, and re-install the filler panel.
If no laptop tray is present: Hang the cable near the right rear of the cabinet.
Proceed to Task 5 to connect to the management server.
Note: At this point, you may opt to configure the IP address for Cluster 2 by repeating the
above steps or to wait until a later time.
48
Task 3: (Optional) Establish Call-Home connectivity to EMC prior to VPLEX cluster

configuration
Note: You should perform this task only if you want early call-home connectivity to the
VPLEX cluster box and you know that there will be a delay in fully configuring the cluster. If
you are running EZ-Setup in the near future, then this task is not necessary since EZ-Setup
will configure call-home then.

This procedure is not supported prior to 5.2. For previous releases, you can configure
call-home during EZ Setup or after the system is configured, use the configuration
event-notices-reports-config command.
Prerequisites
To perform this procedure, the following preconditions must occur:
Cluster is in a manufactured state.
Power is applied to all components.
Public IP address is configured.
Procedure to configure Call-Home

1. Start the VPlexcli and execute configuration connect-local-directors.
2. Use the configuration event-notices-reports-config command to configure the cluster
to dial home and/or send system reports.
3. Complete the product registration using the configuration register-product command.
4. Once call-home is enabled, then issue call-home test from the
/notifications/call-home context and confirm that it was successful.
5. Repeat the above steps for Cluster 2.
Task 4: Leaving your laptop connected or reconnecting to the management server

For the remaining setup tasks, you can leave your laptop connected directly to the
management server, or you can move to a more-comfortable location and reconnect to the
management server over the customer network:
If you want to leave your laptop connected to the management server, then
proceed to Task 6.
If you want to move your laptop to a different location and reconnect, then proceed
to Task 5.
Setup procedure
49
Task 5: (Optional) Connecting to the management server over the customer network
Note: This task only applies if you want to move your laptop to a desired location, and
then reconnect to your network to configure a cluster. If this is not applicable, then
continue with configuration by proceeding to Task 6: Verify the product version.
1. Prepare for connection to the customer network:
If you want to connect to the network from your laptop, set the laptop to an IP
address on the network.
If you want to connect to the network from a different PC (or similar device):
a. Restore your laptop to the settings it had before you began this procedure
(including re-enabling any network cards).
b. Verify that PuTTY is installed on the device, and install it if necessary.
c. Set the device to an IP address on the customer network.
2. Launch PuTTY.exe, and configure PuTTY as shown in Figure 24.
in the first cluster you
are configuring
(default)
VPLEX service

VPLEX Cluster 1
(default)
PuTTY2
50
SSH protocol
version
putty_ssh
5. Configure a new PuTTY session as shown in Figure 26.
in the second cluster you
are configuring
(default)
VPLEX service
VPLEX Cluster 1

VPLEX Cluster 2
(default)
PuTTY3
8. Select the VPLEX Cluster 1 session and click Load.
Setup procedure
51
9. Click Open, and log in to the management server with username service and password
Mi@Dim7T.
10. Proceed to the next task.
Task 6: Verify the product version

1.
Shell-1
From the shell prompt, type the following command to connect to the
VPlexcli:
vplexcli

3.
local directors:
VPlexcli
4. Type the following command to ensure that all local directors are connected:
ll /engines/**/directors
5.
VPlexcli
version

VPLEX Release Notes, follow the steps in .Appendix A
If the VPLEX cluster contains VS1 engines, proceed to Task 9: Launch the
EZ-Setup Wizard on Cluster 1 on page 54.
If the VPLEX cluster contains VS2 engines, proceed to Task 7: VS2 hardware
only: Verify the cluster health for Cluster 1 on page 52.
Task 7: VS2 hardware only: Verify the cluster health for Cluster 1
hardware, you should verify that all components in the cluster are functioning correctly.
1.
VPlexcli-1
exit
52
2.
From the shell prompt, type the following command (where the options are
as described following the command):
Shell-1
You can include one or more of these options

3. In the output, confirm the following values:
Category
Values
System Information
Connectivity Check
All OK

Management Server
System Check
Process Check : OK
CPU Check : OK
If the system is a small system, values in this category stays same as
before

each director
All OK
Platform Health Check Found xx errors

Note: XX is a numeric value and would depend on the configuration
of the system.
4.
Shell-1
Type the following command to connect to the VPlexcli:
vplexcli
Task 8: (Optional) Synchronize the time on the cluster(s) with an external NTP server
1.
From the VPlexcli prompt, type the following command, which

synchronizes the time on Cluster 1 with an external NTP server:
VPlexcli
configuration sync-time -f -i IP address of remote NTP server
Setup procedure
53
Note: Ignore messages regarding VPN status because VPN is not yet configured at this
stage.
Task 9: Launch the EZ-Setup Wizard on Cluster 1

The EZ-Setup Wizard performs several tasks to set up a VPLEX implementation, including:
Creates Web Server and VPN certificates
Creates a Web Server certificate keystore
Configures call-home notifications
Sets up SNMP for gathering performance statistics (optional)
Configures VPLEX for authentication directory service (LDAP/AD) (optional)
Configures VPLEX for a customized login banner using a .txt file provided by the user
(optional)
From the VPlexcli prompt, type the following command, and follow the
steps in the automated interview:
VPlexcli-1
Note: If you are prompted to enter the Fibre Channel switch password, type Mi@Dim7T.
Task 10: Expose Cluster 1 back-end storage

To zone storage to VPLEX, you need to know the port WWNs of the back-end VPLEX ports
(the ports that connect to the storage arrays).
1. You can determine the WWNs in either of two ways:
Using the VPLEX Port WWN Calculator If you have not already done this,
download the calculator from EMC Online Support (http://one.emc.com/
clearspace/docs/DOC-29929) to your laptop. Then launch the calculator and follow
the instructions.
VPlexcli-1
Using the VPlexcli Type the following command to list all director
port WWNs (identified in the command output as addresses):
where -p enables paging mode, which displays long output one page at a time.
54
Note: The VPlexcli commands ll (two lowercase Ls) and ls support a paging option that
allows you to display long output one page at a time.
- To enable paging, include the option -p at the end of the command.
- To scroll from one page of the command output to the next, press the space bar.
- To exit paging mode while you are viewing paged output, press q.
(The remainder of the output appears in its entirety.)
Note: As the ll command shows, if you want a single command to affect multiple
entities (for example, directors or ports), you sometimes can use an asterisk as a
wildcard (called command globbing). The VPLEX CLI Guide provides more detail.
Implementation and Planning Best Practices for EMC VPLEX Technical Notes.
Task 11: Resume EZ-Setup on Cluster 1

VPlexcli-1
This part of the EZ-Setup finishes by rediscovering the back-end arrays. Wait several
minutes for the rediscovery to complete before you proceed to the next task.
Note: If at any point you need to reset the EZ-Setup steps you have performed, you can
revert the setup as described in Reference: Reverting the setup on page 70.
Task 12: Create a meta-volume on Cluster 1

1.
Type the following command, which lists available storage volumes

that meet the requirements for a meta-volume (78 GB or larger, and unclaimed):
VPlexcli-1
Output example:
Name
---------------------------------------VPD83T3:60000970000192601714533036464234
VPD83T3:60000970000192601714533036464235
VPD83T3:60000970000192601714533036464236
VPD83T3:60000970000192601714533036464238
VPD83T3:60000970000192601714533036464239
VPD83T3:600616037e202200d03f54035c1fe012
VPD83T3:6006016037202200d13e64035c1fe012
Capacity
-------80.1G
80.1G
80.1G
80.1G
80.1G
85G
85G
Vendor
-------EMC
EMC
EMC
EMC
EMC
DGC
DGC
IO Status
--------alive
alive
alive
alive
alive
alive
alive
Type
---------traditional
traditional
traditional
traditional
traditional
traditional
traditional
Array Name
--------------EMC-SYMMETRIX-192501423
2. From the output, identify four volumes to be used for the meta-volume, a mirror of the
meta-volume, and backups for both the meta-volume and the mirror.
Note: Unless only one back-end array is visible, the meta-volume and mirror must be
on separate arrays, and should be in separate failure domains. This requirement also
applies to the mirror volume and its backup volume.
Setup procedure
55
3.
VPlexcli-1
To create the meta-volume and a mirror, type the following command,
where:
The mirror can consist of multiple storage volumes (which will become a RAID 1), in
which case you would include each additional volume, separated by commas. For
example:
storage-volume_1_name,storage-volume_2_name,storage-volume_3_name
Note: You can copy a storage volume name from the configuration show-meta-volumecandidates output and paste it into the following command. To do this, highlight the
volume to select it, and then right-click at the point in the command where you want to
paste the volume.
Command example:
meta-volume create n c1_meta d
VPD83T3:60000970000192501423533036464234,
VPD83T3:6006016037202200d13e64035c1fe012
4.
VPlexcli-1
To display the meta-volume status, type the following command:
5. In the output, verify that the attribute active shows a value of true.
6.
VPlexcli-1
To display the cluster status, type the following command:
cluster status
Output example:
Cluster cluster-1
operational-status:
ok
health-state:
ok
health-indications:
Task 13: Set a backup schedule for Cluster 1

1.
VPlexcli-1
56
Task 14: Register Cluster 1

You must register the cluster with EMC in order to receive service. From the
VPlexcli prompt, type the following command, and follow the instructions:
VPlexcli-1

Task 15: Enable the front-end ports

VPlexcli-1
configuration enable-front-end-ports
Task 16: Connect to Cluster 2

Did you set the public IP address on both management servers in Task 2?
If yes:
1. Establish a PuTTY session to the management server in Cluster 2, and log in with
username service and password Mi@Dim7T.
2.
Shell-2
VPlexcli:
vplexcli

3. Proceed to Task 17.
If no:
1.
Shell-2
VPlexcli-2
Repeat Task 2 for Cluster 2.
2. Proceed to Task 17.
Task 17: Verify the product version for Cluster 2

1.
From the VPlexcli prompt, type the following command to connect to

all local directors:
VPlexcli-2
2.
VPlexcli-2
Setup procedure
57
version

VPLEX Release Notes, follow the steps in .
If the VPLEX cluster contains VS1 engines, proceed to Task 19: Synchronize
the time on the clusters on page 59.
If the VPLEX cluster contains VS2 engines, proceed to Task 18: VS2 hardware
only: Verify the cluster health for Cluster 2 on page 58.
Task 18: VS2 hardware only: Verify the cluster health for Cluster 2
hardware, you should verify that all components in the cluster are functioning correctly.
1.
VPlexcli-2 From the VPlexcli prompt, type the following command:

exit
2.
From the shell prompt, type the following command (where the options
are as described following the command):
Shell-2
You can include one or more of these options

3. In the output, confirm the following values:
58
Category
Values
System Information
Connectivity Check
All OK

Category
Values
Management Server
System Check
Process Check : OK
CPU Check : OK
If the system is a small system, values in this category stays same as
before

each director
All OK
Platform Health Check Found XX errors
Note: XX is a numeric value and would depend on the

configuration of the unit.
4.
Shell-2
VPlexcli:
vplexcli
Task 19: Synchronize the time on the clusters

VPlexcli-2
From the VPlexcli prompt, type the following command, which
synchronizes the time on Cluster 2 with the time on Cluster 1:
configuration sync-time
Note: The synchronization might cause your VPlexcli or shell session to end. If this
happens, log in again and proceed to Task 20.
Task 20: Launch the EZ-Setup Wizard on Cluster 2

VPlexcli-2
From the VPlexcli prompt, type the following command, and follow the
steps in the automated interview:

If you see a message stating that the management server is not reachable, ignore it.
Setup procedure
59
Task 21: Expose Cluster 2 back-end storage

1. Use either the VPLEX Port WWN Calculator or the VPlexcli to determine the VPLEX
back-end ports that you will zone to the storage ports:
Using the Port WWN Calculator If you have not already done this, download the
calculator from EMC Online Support
(http://one.emc.com/clearspace/docs/DOC-29929) to your laptop. Then launch
the calculator and follow the instructions.
Using the VPlexcli Type the following command to list all director
port WWNs (identified in the command output as addresses):
VPlexcli-2
Implementation and Planning Best Practices for EMC VPLEX Technical Notes, which are
available on EMC Online Support.
Task 22: Resume EZ-Setup on Cluster 2

VPlexcli-2
Wait several minutes for array rediscovery to complete before you proceed to the next
task.
Note: If at any point you need to cancel all the EZ-Setup steps you have performed, you
can cancel the setup as described in Reference: Reverting the setup.
Task 23: Restart the web server on Cluster 2 if necessary

If you configured the cluster for LDAP/AD, then type the following
command from the VPlexcli prompt:
VPlexcli-2
webserver restart
Task 24: Create a meta-volume on Cluster 2

1.
Type the following command to list available storage volumes that

meet the requirements for a meta-volume (78 GB or larger, and unclaimed):
VPlexcli-2
2. From the output, identify two volumes to be used for the meta-volume and a mirror of
the meta-volume. Task 12 shows an output example.
Note: Unless only one back-end array is visible, the meta-volume and mirror must be
on separate arrays, and should be in separate failure domains.
60
3.
VPlexcli-2
Type the following command to create the meta-volume and a mirror:

where:
The mirror can consist of multiple storage volumes, in which case you would
include each additional volume, separated by commas.
Command example:
meta-volume create -n c2_meta -d
VPD83T3:60000970000192601714533036464234,VPD83T3:600009700001926017
14533036464235
4.
VPlexcli-2
Type the following command to display the meta-volume status:
In the output, verify that the attribute active shows a value of true.
5.
VPlexcli-2
Type the following command to display the cluster status:
cluster status
Output example:
Cluster cluster-2
operational-status:
ok
health-state:
ok
health-indications:
Task 25: Set a backup schedule for Cluster 2

1.
VPlexcli-2
To schedule regular meta-volume backups, type the following
command:
Select the same time for backups that you selected for Cluster 1.
Setup procedure
61
Task 26: Register Cluster 2

You must register the cluster with EMC in order to receive service.
Type the following command, and follow the instructions:
VPlexcli-2

Task 27: Deploy each cluster on the ESRS if necessary

ESRS must be deployed by EMC personnel. If ESRS will be used in the VPLEX
implementation, EMC personnel should follow the procedure described in the ESRS
documentation on the GTS website, in the Application Download area, under EMC Secure
Remote Support Gateway > Implementation > Install Procedure.

The next two tasks are performed on Cluster 1.
Task 28: Complete the EZ-Setup on Cluster 1

VPlexcli-1
From the VPlexcli prompt on Cluster 1, type the following command:
The EZ-Setup Wizard performs the following steps on the cluster:
Configures VPN for inter-cluster communication
Establishes a secure connection between the clusters
Enables the WAN COM ports
Connects to Cluster 2s directors
Task 29: Restart the web server on Cluster 1 if necessary

VPlexcli-1
If you configured the cluster for authentication directory service
(LDAP/AD), type the following command:
webserver restart
Task 30: Complete the EZ-Setup on Cluster 2

VPlexcli-2
command:
62
From the VPlexcli prompt on management server 2, type the following
The EZ-Setup Wizard performs the following steps on the cluster:
Enables the WAN COM ports
Connects to Cluster 1s directors
Task 31: Configure the WAN interfaces

This task depends on the WAN interface type:
Fibre Channel - Follow the recommendations in the Implementation and Planning Best
Practices for EMC VPLEX Technical Note to zone the WAN COM ports.
IP:
1. Locate and download the VPLEX IP COM Configuration Worksheet on EMC Online
Support:
EMC Online Support > Support by Product > Search Support Vplex > Tools >
IPComConfigWorksheet_v.x.x.zip
2. Follow the instructions in the worksheet, and enter the required input.
3. Click Generate Command Script.
This generates a script file named IPWANSetupCmd.py on the PC from which you
opened the worksheet.
4. Use SCP to copy IPWANSetupCmd.py to the directory /var/log/VPlex/cli on the
management server on which you will perform IP WAN COM configuration.
5.
VPlexcli-2 From the VPlexcli prompt on the management server, type the
following command:
script -i IPWANSetupCmd
6.
VPlexcli-2
After the script has been imported, type the following command:
configuration ip-wan-setup
Task 32: VPLEX Geo only: Verify cluster connectivity

connectivity validate-wan-com
In the output, confirm that all local and remote directors are reachable.
Output example:
Determining expected connectivity...
Determining actual connectivity...
Comparing expected and actual connectivity...
All expected connectivity is present.
Setup procedure
63
Task 33: Join the clusters

From the VPlexcli prompt on management server 2, type the following
command, which verifies connectivity between Cluster 1s directors and Cluster 2s
directors, and joins the directors into a unified configuration.
VPlexcli-2
The specific command depends on the WAN connection type:

Connection type:
Command:
Fibre Channel
configuration join-clusters
IP
cluster add cluster-1 cluster-2
Task 34: Create logging volumes

VPLEX uses logging volumes to track changes during a loss of connectivity or loss of a
volume that is a mirror in a distributed device. You must create a logging volume on each
cluster. Each logging volume must be large enough to contain one bit for every page of
distributed storage space (approximately 10 GB of logging volume space for every 160 TB
of distributed devices).
The logging volumes experience much I/O during and after link outages. The
recommended best practice is to stripe each logging volume across many disks for speed,
and also to have a mirror (on another fast disk), because this is important data.

If a logging volume does not exist, every link failure could cause a full resynchronization
of every distributed device in the system.
Volumes that will be used for logging volumes must be clean (have zeros written) before
they can be used.
An example of how to clean all data from the given disk:

1. Expose disk that will be used for logging volume to the Linux host
2. Write zeros to the while disk using the following command:
For example:
64
To create the logging volumes, you first must claim the storage volumes that will be used,
and create extents from those volumes:
1.
On management server 2, type the following commands to list the

storage volumes:
VPlexcli-2
ll
2.
Type the following command to claim the storage volume(s) that you
will use for the logging volume:
VPlexcli-2
where:
storage_volume_name is a unique name you are assigning to the volume.
VPLEX CLI Guide.
3.
VPlexcli-2
Type the following command to create an extent:
extent create -d storage-volume_name,storage-volume_ name,.....
Repeat this step for each extent you want to create on the cluster.
4.
VPlexcli-2
Type the following commands to create the logging volume:
cd /clusters/cluster-Cluster_ID/system-volumes
logging-volume create -n name -g raid_geometry -e extent_1 , extent_2
[, extent_3 ... extent_n] -d stripe_depth
where:
name is a name for the logging volume.
raid_geometry is the RAID type: raid-0 or raid-1.
extent_ identifies the names of the extents that makes up the logging volume.
-d stripe_depth is required only if geometry is raid-0.
The stripe depth must be:
Greater than zero, but no greater than the number of blocks of the smallest
element of the RAID 0 device being created
A multiple of 4000 bytes
Note: A depth of 32 means that 128 K (32 x 4 K) is written to the first disk, the next
128 K is written to the next disk, and so on.
Note: Concatenated RAID devices are not striped.
Setup procedure
65
Example for Cluster 2:

logging-volume create -n cluster_2_log -g raid-0 -e ext1 , ext2 -d 32
5.
VPlexcli-1
Repeat steps 1 through 4 for Cluster 1.
Task 35: Check the cluster health

1.
VPlexcli-1
Type the following command:
health-check
2. In the output, confirm the following:

Operational Status and Health State are ok.
Operational Status and Health State of the metadata volumes are ok.
There are no unhealthy storage volumes.
Each storage volume is visible from all directors and with at least two paths.
3.
On Cluster 2, repeat the health-check command, and confirm the

output as described in step 2 .
VPlexcli-2
Task 36: Expose storage to hosts

Use a VPlexcli session or the VPLEX Management Console GUI to perform this task.
Recommendations:
If a storage volume is equal to or larger than the desired virtual volume capacity,
create an extent the size of the desired virtual volume.
If a storage volume is smaller than the desired virtual volume capacity, create a single
extent per storage volume, and then use devices to concatenate or stripe these
extents into a larger device.
Create one view for each set of hosts that require access to the same storage.
You can use the VPlexcli or the Management Console GUI to expose storage. The basic
steps are the same for either:
To use the GUI, proceed to If you are using the GUI
To use the VPlexcli, proceed to If you are using the VPlexcli
If you are using the GUI

To use the GUI:
1. Open a browser and type the following, where mgmt_server_address is the IP address
of the management server's public IP port:
https://mgmt_server_address
66
Note: If the security message screen was enabled during system setup, a security
message appears. Read the message, and then click Continue.
3. Click System Status to view the status of the system, clusters, and directors. Confirm
that the health state and operational status are ok.
4. To begin provisioning and exporting storage, click Provision Storage on the main
screen of the Unisphere for VPLEX Online Help screen (shown in Figure 27).
Figure 27 Unisphere for VPLEX Online Help screen: Provision Storage
Note: To display online help and product information, click the question mark at the upper
right corner of the screen. To display documentation and additional resources for the
current VPLEX release, click Support on the navigation bar.
If you are using the VPlexcli

Note: The VPLEX CLI Guide contains details on using VPlexcli commands.
To claim and name a storage volume:
1.
VPlexcli
To display a list of available storage volumes, type the following
commands:
ls
2.
VPlexcli
To claim and name a storage volume, type the following command,
where:
storage_volume_name is a unique name you are assigning to the volume.
VPLEX CLI Guide.
Setup procedure
67
3.
VPlexcli
To create the extent, type the following command:
extent create -d storage_volume_name
In you do not include any arguments, this command creates an extent the size of the
storage volume. However, you can create multiple smaller extents (up to 128 per
storage volume).
Note: Extents are named and claimed automatically.
4.
VPlexcli
To verify that the extent was created, type the following command:
ls /clusters/cluster-Cluster_ID/storage-elements/extents

/clusters/cluster-1/storage-elements/extents:
5.
VPlexcli
To create the RAID device, type the following commands:
cd /clusters/cluster-Cluster_ID/devices
local-device create device_name -g[raid-0|raid-1|raid-c] -e
extent,extent
6.
VPlexcli
To create the virtual volume, type the following commands:
cd /clusters/cluster-Cluster_ID/virtual-volumes
create -r device_name
7.
VPlexcli
To list the initiator ports, type the following command:
ll /clusters/cluster-Cluster_ID/exports/initiator-ports
68

Name
-----------UNREGISTERED-0x10000000c866fff2
port-wwn
-----------------0x10000000c866fff2
node-wwn
type
------------------ ------0x20000000c866fff2 default
UNREGISTERED-0x10000000c866fff3
0x10000000c866fff3
0x20000000c866fff3
default
UNREGISTERED-0x10000000c866ffec
0x10000000c866ffec
0x20000000c866ffec
default
UNREGISTERED-0x10000000c866ffed
0x10000000c866ffed
0x20000000c866ffed
default
8.
VPlexcli
Target Port Names

-------------------------P000000003CA00165-A0-FC00,
P000000003CA00183-A0-FC00,
P000000003CB00165-B0-FC00,
P000000003CB00183-B0-FC00
P000000003CA00165-A0-FC01,
P000000003CA00183-A0-FC01,
P000000003CB00165-B0-FC01
P000000003CA00165-A1-FC00,
P000000003CA00183-A1-FC01,
P000000003CB00165-B1-FC00,
P000000003CB00183-B1-FC01
P000000003CA00165-A0-FC01,
P000000003CA00183-A1-FC00,
P000000003CB00165-B0-FC01,
P000000003CB00183-B0-FC01,
P000000003CB00183-B1-FC00
To register each initiator port, type the following commands, where:
initiator_port is the human readable name of the initiator port. The new initiator
name cannot be the same default name (UNREGISTERED_xxx).
type is the initiator type: hpux, sun-vcs, aix, or default.
cd /clusters/cluster-Cluster_ID/exports/initiator-ports
export initiator-port register -i initiator_port -p portWWN|nodeWWN
-t type
9.
VPlexcli
To create and export the storage view, type the following commands:
storage-view create -c /clusters/cluster-Cluster_ID/ -n
storage_view_name -p VPLEX_target_port,VPLEX_target_port
10. VPlexcli
To add each initiator port to the storage view, type the following
commands:
storage-view addinitiatorport -v storage_view_name -i
initiator_port,initiator_port
11. VPlexcli
To add the virtual volume(s) to the storage view, type the following
commands:
storage-view addvirtualvolume -v storage_view_name -o
virtual-volume_name
12. VPlexcli
To verify the status of the storage view, type the following commands:
cd /clusters/cluster-Cluster_ID/exports/storage-views
export storage-view summary
View health summary(cluster-1):
view name
health-state exported volumes
ports
-----------
-----
------------
----------------
registered
initiators
----------
Setup procedure
69
VMware_view
view1
view2
view3
view4
healthy
healthy
healthy
healthy
healthy
2
1311
10
11
10
4
4
4
4
4
4
480
2
2
2
Total 5 views, 0 unhealthy.
Task 37: Perform a rescan

After provisioning and exporting storage, perform a rescan from the host to verify that the
exported virtual volume is visible.
Task 38: (Optional) Perform Cluster Witness setup

Note: Cluster Witness is the method used to implement the VPLEX Witness feature.
If you plan to deploy the VPLEX Cluster Witness function, follow the steps in the Cluster
Witness deployment procedure, available through the generator, which you can download
from EMC Online Support.
Reference: Reverting the setup

If at any point you need to cancel all the EZ-Setup steps you have performed, you can
revert to the pre-setup state.
Exceptions: This operation works only if no meta-volume exists and no storage is exposed
to hosts.
The operation returns your system to a pre-configured state, including:
Logically disconnecting the directors from the management server
Disabling call-home notification if it is enabled
Disabling the front-end ports
Note that although the reset operation erases all configuration entries you have made,
those entries become the new default values when you next perform the EZ-Setup.
To revert the setup, type the following command:
configuration system-reset
70
APPENDIX A
Note: This procedure applies only to a new installation. If you need to upgrade an existing
VPLEX implementation, then launch the generator and follow the directions for the
upgrade procedure.
Release 5.3 introduces an upgrade of the SLES 11 operating system. If you are upgrading
to Release 5.3 or later from previous releases, you must re-image the management server.
For this reason:
All upgrades from before Release 5.3 to 5.3 or after require an upgrade of the
operating system as part of the management server upgrade. See Upgrade the
Management Server (with OS upgrade)
All upgrades to releases before 5.3 do not require this operating system upgrade.
See Upgrade the Management Server (no OS Upgrade)
All upgrades from Release 5.3 to a later release do not require this operating
system upgrade. See Upgrade the Management Server (no OS Upgrade)
Note: For VPLEX Metro or VPLEX Geo, you must perform this procedure on each clusters
management server. The following steps assume you are upgrading Cluster 1 first.
Before You Begin

Download the following files from the software download area on EMC Support Online to
your laptop:
To upgrade without OS upgrade:

VPlex-version-management-server-package.tar
VPlex-version-director-firmware-package.tar
To upgrade with OS upgrade:

VPlex-5.x.0.00.00.xx-D4_ISO_7-management-server.iso
Upgrade the Management Server (no OS Upgrade)

1. Ensure that all the local directors are connected before proceeding with the upgrade. If
directors are not connected to VPlexcli, follow the steps below to connect them:
1. If you are not logged into VPLEX CLI:
1.
Shell-1 From the shell prompt, type the following command to connect to
the VPlexcli:
vplexcli
71
2. Login in with username service and password Mi@Dim7t.

2.
local directors:
VPlexcli
2. Logout from the VPlexcli prompt on the management server, if you are logged into it.
Type the following command, to do so:
exit
3. Copy the following files from your laptop to the directory /tmp on the management
server in Cluster 1.
4. From the shell prompt, type the following commands:
VPlex-MS-installer /tmp/VPlex-version-management-server-package.tar
The install script will determine if a reboot is necessary. If a reboot is necessary the
script itself will initiate the reboot. You would see the following output before the
reboot:
...
Broadcast message from root (pts/1) (Mon Jun
9 16:56:36 2014):
System packages have been updated.

The system is going DOWN for reboot in 2 minutes!
9 16:57:36 2014):

The system is going DOWN for reboot in 1 minute!
9 16:58:36 2014):

The system is going down for reboot NOW!
5. If the management server did not reboot, proceed to step 6 , else wait for the
management server to come back up, establish an SSH session to the management
server, and log in with username service and password Mi@Dim7T.
6. From the VPlexcli prompt, type the following command:
ndu pre-config-upgrade -u
/tmp/VPlex-version-director-firmware-package.tar
Messages track the status of the upgrade and notify you when it is complete.
version -a
In the output, confirm the following:

The Product Version is what you expect to see.
72
All directors in the cluster are running the same version as each other.
8. VPLEX Metro or VPLEX Geo only - Repeat step 1 through step 7 for Cluster 2 on the
Cluster 2 management server and VPlexcli.
Note: Because this is a new installation, the director addresses are the system
defaults, which match those on Cluster 1. The EZ-Setup procedure resets the
addresses for Cluster 2.
9. Continue with the steps in Post Upgrading Tasks.
Upgrade the Management Server (with OS upgrade)

1. Ensure that all the local directors are connected before proceeding with the upgrade. If
directors are not connected to VPlexcli, follow the steps below to connect them:
1. If you are not logged into VPLEX CLI:
1.
Shell-1 From the shell prompt, type the following command to connect to
the VPlexcli:
vplexcli
2. Login in with username service and password Mi@Dim7t.

2.
local directors:
VPlexcli
2. Logout from the VPlexcli prompt on the management server, if you are logged into it.
Type the following command, to do so:
exit
3. At the management server prompt, type the following command to change the current
directory to /tmp:
service@ManagementServer:~> cd /tmp
service@ManagementServer:/tmp/>
4. Copy the management server package and the imager iso files for the new
GeoSynchrony release:
FROM: the site documented in the Release Notes
TO: the /tmp directory on the management server.

Do not upload the director firmware tar files at this step. Ensure the management
server files are copied to /tmp.
73
For example:
service@ManagementServer:/tmp> scp -p
usert@xxx.xxx.xxx.xxx:/VPLEX_builds/VPLEX-5.x.0.00.00.xx/VPLEX_PACK
AGES/VPlex-5.x.0.00.00.xx-management-server-package.tar /tmp
service@ManagementServer:/tmp> scp -p
usert@xxx.xxx.xxx.xxx:/VPLEX_builds/VPLEX-5.x.0.00.00.xx/VPLEX_PACK
AGES/VPlex-5.x.0.00.00.xx-D4_ISO_7-management-server.iso /tmp
Note: Replace xxx.xxx.xxx.xxx with the IP address

5. At the management server prompt, type the ls tar-file-name and ls iso-file-name to
confirm that the packages are present:
service@ManagementServer:/tmp> ls
VPlex-5.x.0.00.00.xx-management-server-package.tar
VPlex-5.3.00.00.xx-management-server-package.tar
service@ManagementServer:/tmp> ls
6. Retrieve the management server software package MD5 checksum value from the site
documented in Release Notes.
7. Verify that the MD5 checksum on the management server package matches that
retrieved in step 6 .
service@ManagementServer:/tmp> md5sum
If the checksum does not match, remove the corrupted management server package
and return to step 4 .
IMPORTANT
The management server upgrade must be run from the /tmp/VPlexInstallPackages
directory.
8. Change to the VPlexInstallPackages directory.
service@ManagementServer:/tmp> cd VPlexInstallPackages
service@ManagementServer:/tmp/VPlexInstallPackages>

As part of the next step, the configuration will be backed up and you will be
instructed to save the backup and informed that the management server will be
re-imaged on reboot. When you are given the opportunity to save the backup, copy
the backup to a different machine. You will use this file in a later step to restore your
configuration. Ensure that you name the backup files appropriately to be able to
identify as to which cluster it belongs to.
9. Run VPlex-MS-installer to upgrade the management server OS and software. The
configuration will be backed up, and you are instructed to save the backup and
informed that the management server will be re-imaged on reboot.
74
service@ManagementServer:/tmp/VPlexInstallPackages>
VPlex-MS-installer --skip-package-verification --pre-reimage
/tmp/VPlex-5.x.0.00.00.xx-D4_ISO_7-management-server.iso
/tmp/VPlex-5.x.00.00.xx-management-server-package.tar
10. Type the password for the service account.

A series of messages is displayed indicating that the management server will reboot
and re-image itself.
11. When the management server reboot is completed, login to the management server
again.

Do not upload the director package or the backup file now. Because the management
server install process removes all files from the /tmp/VPlexInstallPackages.
directory.
12. Copy the management server package for the new GeoSynchrony release to the newly
imaged management server:
TO: the /tmp/VPlexInstallPackages directory on the management server.
For example:
service@ManagementServer:/tmp/VPlexInstallPackages> scp -p
user@xxx.xxx.xxx.xxx:/VPLEX_builds/VPLEX-5.x.0.00.00.xx/VPLEX_PACKA
GES/VPlex-5.x.0.00.00.xx-management-server-package.tar
/tmp/VPlexInstallPackages
Note: Replace xxx.xxx.xxx.xxx with the ip address
13. At the management server prompt, type the ls tar-file-name to confirm that the
package is present:
service@ManagementServer:/tmp/VPlexInstallPackages> ls
14. Type the following command to run VPlex-MS-installer to restore the backup.

You will be prompted to copy the back up to the newly imaged management server.
Do not place them there ahead of time or they will be removed. Ensure that you are
copying the appropriate files to restore on the same cluster from which they were
taken.
VPlex-MS-installer --skip-package-verification
--omit-manifest-check --post-reimage
/tmp/VPlexInstallPackages/VPlex-5.x.0.00.00.xx-management-server-pa
ckage.tar
A series of messages is displayed.
75
IMPORTANT
Contact EMC Customer Support if this command fails with an error.
Note: The management server will be rebooted automatically by the script after
restoring the backup.
15. When the management server comes back up, establish an SSH session to the
16. Copy VPlex-5.x.0.00.00.xx-director-firmware-package.tar file on the management
server in Cluster 1.
TO: the /tmp/VPlexInstallPackages directory on the management server.
For example:
service@ManagementServer:/tmp/VPlexInstallPackages> scp -p
user@XXX.XXX.XXX.XXX:/VPLEX-5.x.0.00.00.xx/VPLEX_PACKAGES/VPlex-5.x
.0.00.00.xx-director-firmware-package.tar /tmp/VPlexInstallPackages
Note: Replace xxx.xxx.xxx.xxx with the IP address
17. From the shell prompt, type the following command:

vplexcli

Note: If already logged into VPlexcli, then skip step 17 .
18. Verify all the directors are connected by listing the directors in the directors context.
VPlexcli:/> ll engines/*/directors/

ndu pre-config-upgrade -u
/tmp/VPlexInstallPackages/VPlex-version-director-firmware-package.t
ar
Messages track the status of the upgrade and notify you when it is complete.
version -a
In the output, confirm the following:

The Product Version is what you expect to see.
All directors in the cluster are running the same version as each other.
21. VPLEX Metro or VPLEX Geo only - Repeat step 1 through step 20 for Cluster 2 on the
Cluster 2 management server and VPlexcli.
76
Note: Because this is a new installation, the director addresses are the system
defaults, which match those on Cluster 1. The EZ-Setup procedure resets the
addresses for Cluster 2.
Post Upgrading Tasks

After completing the upgrade of the management server, proceed to the applicable task:
VPLEX Local - Task 5: VS2 hardware only: Verify the cluster health.
VPLEX Metro Cluster 1 - Task 7: VS2 hardware only: Verify the cluster health for
Cluster 1.
VPLEX Metro Cluster 2- Task 18: VS2 hardware only: Verify the cluster health for
Cluster 2.
VPLEX Geo Cluster 1 - Task 7: VS2 hardware only: Verify the cluster health for Cluster
1.
VPLEX Geo Cluster 2- Task 18: VS2 hardware only: Verify the cluster health for Cluster
2.
Post Upgrading Tasks
77
78
APPENDIX B
Reference
This appendix contains miscellaneous information you will need during the installation.
The appendix also contains tables to record other information you might need.
VPLEX hardware overview........................................................................................ 79

IP addresses and component IDs ............................................................................ 86
Internal cabling....................................................................................................... 90
Cabinet power connections ................................................................................... 113
VPLEX hardware overview

Three implementations of EMC VPLEX are available in the current release:
VPLEX Local - single cluster
VPLEX Metro - two clusters, separated by synchronous distances
VPLEX Geo - two clusters, separated by asynchronous distances
A cluster is a single cabinet that contains one of the hardware configurations shown in
VS1 hardware configurations or VS2 hardware configurations.
Note that in the current GeoSynchrony release, VS1 and VS2 hardware cannot co-exist in a
VPLEX implementation, with one exception - both versions can co-exist in a VPLEX Local
cluster during a nondisruptive hardware upgrade from VS1 to VS2.
VS1 hardware configurations

Note: The component placement shown for single-engine and dual-engine configurations
allows for nondisruptive upgrades to larger configurations.
Note: Each component labeled SPS in the figures is a standby power supply module.
Reference
79
Reference
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
Engine 1
ON
I
O
OFF
O
OFF
Management server
ON
I
O
OFF
Director 1B
Director 1A
SPS 1
VPLX-000215
Figure 28 VPLEX VS1 hardware example: Single-engine configuration
80
Reference
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
Fibre Channel switch B

UPS B
Fibre Channel switch A
UPS A
O
OFF
O
OFF
ON
I
ON
I
Management server
Engine 2
Director 2B
Director 2A
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
SPS 2
Engine 1
Director 1B
Director 1A
SPS 1
VPLX-000214
Figure 29 VPLEX VS1 hardware example: Dual-engine configuration
81
Reference
Director 4B
Director 4A
Engine 4
ON
I
ON
I
O
OFF
O
OFF
SPS 4
Engine 3
SPS 3
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
Director 3B
Director 3A

UPS B
UPS A
O
OFF
O
OFF
ON
I
ON
I
Management server
Engine 2
Director 2B
Director 2A
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
SPS 2
Engine 1
Director 1B
Director 1A
SPS 1
VPLX-000213
Figure 30 VPLEX VS1 hardware example: Quad-engine configuration
0
F
IOM B0
1
2
F
F
3
F
0
F
IOM B1
1
2
F
F
3
F
0
B
IOM B2
1
2
B B
3
B
0
B
IOM B3
1
2
B B
3
B
Power supply B
Side B
mgmt. module
Director B
Power supply A
0
F
IOM A0
1
2
F
F
0
L
IOM B4
IOM B5
1
2
3
0 1
2
L WF WF WI WI n
3
F
0
F
IOM A1
1
2
F
F
3
F
0
B
IOM A2
1
2
B B
0
L
IOM A4
IOM A5
1
2
3
0 1
2
L WF WF WI WI n
3
B
0
B
IOM A3
1
2
B B
3
B
Director A
Side A mgmt. module
IOM = I/O module

F
= Front-end SAN port
B
= Back-end SAN port
3
n
L
WF
WI
n
3
n
= Local COM port

= WAN COM port for Fibre Channel
= WAN COM port for IP
= not currently used
I/O module carrier
VPLX-000343
Figure 31 VPLEX VS1 Engine components
Note: The WAN COM ports on IOMs A4 and B4 are used if the inter-cluster connections are
over Fibre Channel, and the WAN COM ports on IOMs A5 and B5 are used if the
inter-cluster connections are over IP.
82
Reference
VS2 hardware configurations

Note: The component placement shown for single-engine and dual-engine configurations
allows for nondisruptive upgrades to larger configurations.
Note: Each component labeled SPS in the figures is a standby power supply module.
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
Laptop tray
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
Engine 1, Director B
SPS 1B
Management server
Engine 1, Director A
SPS 1A
VPLX-000226
Figure 32 VPLEX VS2 hardware example: Single-engine cluster
83
Reference
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
Laptop tray

UPS B

UPS A
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
SPS 2B
Management server
SPS 2A
O
OFF
O
OFF
ON
I
ON
I
SPS 1B
SPS 1A
VPLX-000227
Figure 33 VPLEX VS2 hardware example: Dual-engine cluster
84
Reference
ON
I
ON
I
O
OFF
O
OFF
SPS 4B
SPS 4A
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
SPS 3B
SPS 3A
Laptop tray

UPS B

UPS A
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
SPS 2B
Management server
SPS 2A
O
OFF
O
OFF
ON
I
ON
I
SPS 1B
SPS 1A
VPLX-000228
Figure 34 VPLEX VS2 hardware example: Quad-engine cluster
85
Reference
Director B
IOM A4 - reserved
IOM A3 - Local COM
IOM A2 - WAN COM
IOM A1 - Back end
IOM A0 - Front end
Management module A
IOM B4 - reserved
IOM B3 - Local COM
IOM B2 - WAN COM
IOM B1 - Back end
IOM B0 - Front end
Management module B
Figure 35 shows the modules in a VPLEX VS2 engine. Note that IOMs A2 and B2 in the
figure each contain four Fibre Channel ports for VPLEX Metro or VPLEX Geo WAN
connections. VPLEX Metro and VPLEX Geo also support IP WAN connections, in which case
these IOMs each contain two Ethernet ports. In a VPLEX Local configuration, these IOMs
contain no ports.
Director A
Depending on the cluster topology, slots A2 and B2 contain one of the following
I/O modules (IOMs) (both IOMs must be the same type):
8 Gb/s
Fibre Channel
10 Gb/s
Ethernet
Filler module
(VPLEX Local only)
VPLX-000229
Figure 35 VPLEX VS2 engine modules (front view)
IP addresses and component IDs

The IP addresses of the VPLEX hardware components are determined by a set of formulae
that depend on the internal management network (A or B), the Cluster IP Seed, and (for
directors) the Enclosure ID (which matches the engine number).
Figure 38 shows the IP addresses in a cluster with a Cluster IP Seed of 1, and Figure 39
shows the addresses for a Cluster IP Seed of 2. Note that the Cluster IP Seed is the same
as the Cluster ID, which depends on the VPLEX implementation:
86
VPLEX Local - The Cluster ID is always 1.
VPLEX Metro or VPLEX Geo - The Cluster ID for the first cluster that is set up
is 1, and the second cluster is 2.
Reference
VPLEX VS1 hardware

Cluster IP Seed = 1
Enclosure IDs = engine numbers
Management network A addresses
Management network B addresses
Engine 4:
Director 4B
Director 4A
128.221.253.42
128.221.253.41
Engine 4:
Director 4B
Director 4A
128.221.252.42
128.221.252.41
Engine 3:
Director 3B
Director 3A
128.221.253.40
128.221.253.39
Engine 3:
Director 3B
Director 3A
128.221.252.40
128.221.252.39
FC switch B 128.221.253.34
Service port
128.221.252.2
Public Ethernet port

Customer-assigned
FC switch A 128.221.252.34
Mgt B port
128.221.253.33
Mgt A port
128.221.252.33
Management server
Engine 2:
Director 2B
Director 2A
128.221.253.38
128.221.253.37
Engine 2:
Director 2B
Director 2A
128.221.252.38
128.221.252.37
Engine 1:
Director 1B
Director 1A
128.221.253.36
128.221.253.35
Engine 1:
Director 1B
Director 1A
128.221.252.36
128.221.252.35
VPLX-000107
Figure 36 Component IP addresses in Cluster 1
87
Reference
Cluster IP Seed = 2
Management network B addresses
Management network A addresses
Engine 4:
Director 4B
Director 4A
128.221.253.74
128.221.253.73
Engine 4:
Director 4B
Director 4A
128.221.252.74
128.221.252.73
Engine 3:
Director 3B
Director 3A
128.221.253.72
128.221.253.71
Engine 3:
Director 3B
Director 3A
128.221.252.72
128.221.252.71
FC switch B 128.221.253.66
Service port
128.221.252.2

Customer-assigned
FC switch A 128.221.252.66
Mgt B port
128.221.253.65
Mgt A port
128.221.252.65
Management server
Engine 2:
Director 2B
Director 2A
128.221.253.70
128.221.253.69
Engine 2:
Director 2B
Director 2A
128.221.252.70
128.221.252.69
Engine 1:
Director 1B
Director 1A
128.221.253.68
128.221.253.67
Engine 1:
Director 1B
Director 1A
128.221.252.68
128.221.252.67
VPLX-000108
Figure 37 Component IP addresses in VPLEX Metro or VPLEX Geo Cluster 2
88
Reference
VPLEX VS2 hardware

Cluster IP Seed = 1
Engine 4:
Director 4B, A side: 128.221.252.42
Director 4B, B side: 128.221.253.42
Engine 4:
Director 4A, A side: 128.221.252.41
Director 4A, B side: 128.221.253.41
Engine 3:
Engine 3:
FC switch B 128.221.253.34
Service port
128.221.252.2

Customer-assigned
FC switch A 128.221.252.34
Mgt B port
128.221.253.33
Mgt A port
128.221.252.33
Management server
Engine 2:
Engine 2:
Engine 1:
Engine 1:
VPLX-000242
Figure 38 Component IP addresses in Cluster 1
89
Reference
Cluster IP Seed = 2
Engine 4:
Engine 4:
Engine 3:
Engine 3:
FC switch B 128.221.253.66
Service port
128.221.252.2

Customer-assigned
FC switch A 128.221.252.66
Mgt B port
128.221.253.65
Mgt A port
128.221.252.65
Management server
Engine 2:
Engine 2:
Engine 1:
Engine 1:
VPLX-000243
Figure 39 Component IP addresses in VPLEX Metro or VPLEX Geo Cluster 2
Internal cabling
The figures in this section show the various cabling inside a VPLEX cabinet. The figures are
included here for reference only, because all the cables shown in this section except
inter-cluster WAN COM cables (VPLEX Metro and VPLEX Geo only) are installed before the
unit ships from EMC.
VPLEX VS1 cabling
90
This section includes the following figures:

Cluster size
Cable type
Figure
Quad-engine
Ethernet
Figure 40 on page 92
Serial
Fibre Channel
AC power
Reference
Cluster size
Cable type
Figure
Dual-engine
Ethernet
Serial
Fibre Channel
AC power
Ethernet
Serial
Fibre Channel
AC power
Fibre Channel WAN

COM
IP WAN COM
Single-engine
All cluster sizes,

VPLEX Metro or
VPLEX Geo only
Internal cabling
91
Reference
VPLEX VS1 quad-engine configuration
Green, 20 in.
Purple, 71 in.
Green, 48 in.
Purple, 20 in.
Engine 4
Engine 3
Green, 37 in.
Purple, 37 in.
Purple, 20 in.
Green, 37 in.
Green, 20 in.
Purple, 71 in.
Management server
Engine 2
Engine 1
VPLX-000044
Figure 40 Ethernet cabling in a VPLEX VS1 quad-engine configuration
92
Reference
Engine 4
12 in.
12 in.
Engine 3
12 in.
12 in.
UPS B
UPS A
40 in.
40 in.
Engine 2
12 in.
12 in.
Engine1
12 in.
12 in.
VPLX-000065
Figure 41 Serial cabling in a VPLEX VS1 quad-engine configuration
Note: The figure depicts an APC UPS, you may have an Emerson UPS on your setup. Refer
Figure 70 for details.
Internal cabling
93
Reference
Engine 4
Engine 3
79 in.
(all 16 cables)
Engine 2
Engine 1
VPLX-000055
Figure 42 Fibre Channel cabling in a VPLEX VS1 quad-engine configuration
Note: All 16 Fibre Channel cables are light blue. However, the cables connected to Fibre
Channel switch A have blue labels, and the cables connected to switch B have orange
labels.
94
Reference
ON
I
ON
I
O
OFF
O
OFF
Engine 4
SPS 4
ON
I
ON
I
O
OFF
O
OFF
Engine 3
ON
I
ON
I
O
OFF
O
OFF
SPS 3

UPS B

UPS A
Management server
Engine 2
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
SPS 2
O
OFF
O
OFF
ON
I
ON
I
Engine 1
SPS 1
VPLX-000211
Figure 43 AC power cabling in a VPLEX VS1 quad-engine configuration
Internal cabling
95
Reference
VPLEX VS1 dual-engine configuration
Green, 20 in.
Green, 37 in.
Purple, 71 in.
Management server
Purple, 20 in.
Purple, 71 in.
Green, 48 in.
Engine 2
Engine 1
VPLX-000043
Figure 44 Ethernet cabling in a VPLEX VS1 dual-engine configuration
96
Reference
UPS B
UPS A
40 in.
40 in.
Engine 2
12 in.
12 in.
Engine1
12 in.
12 in.
VPLX-000067
Figure 45 Serial cabling in a VPLEX VS1 dual-engine configuration
Internal cabling
97
Reference
79 in. (all 16 cables)

Eight cables for a quad-engine configuration are included for
ease of upgrading, and are tied to the cabinet sidewalls
Engine 2
Engine 1
VPLX-000542
Figure 46 Fibre Channel cabling in a VPLEX VS1 dual-engine configuration
Note: In the drawing, blue lines represent the Side-A connections and orange lines
represent the Side-B connections. All 16 Fibre Channel cables are light blue. However, the
Side-A cables have blue labels and the Side-B cables have orange labels.
98
Reference

UPS B

UPS A
Management server
I
Engine 2
I
O
I
I
O
SPS 2
I
O
I
O
Engine 1
SPS 1
VPLX-000042
Figure 47 AC power cabling in a VPLEX VS1 dual-engine configuration
Internal cabling
99
Reference
VPLEX VS1 single-engine configuration
Green, 37 in.
Purple, 71 in.
Management server
Engine 1
VPLX-000052
Figure 48 Ethernet cabling in a VPLEX VS1 single-engine configuration
Engine 1
12 in.
12 in.
VPLX-000069
Figure 49 Serial cabling in a VPLEX VS1 single-engine configuration
Engine 1
39 in.
(2 cables)
VPLX-000543
Figure 50 Fibre Channel cabling in a VPLEX VS1 single-engine configuration
Note: In the drawing, blue lines represent the Side-A connections and orange lines
represent the Side-B connections. Both Fibre Channel cables are light blue. However, the
Side-A cable has blue labels and the Side-B cable has orange labels.
100
Reference
Management server
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
Engine 1
SPS
VPLX-000041
Figure 51 AC power cabling in a VPLEX VS1 single-engine configuration
WAN COM cabling on VPLEX Metro and VPLEX Geo

Figure 52 and Figure 53 show the WAN COM connection options for VS1 hardware.
Cluster 1 (same connections from each engine in cluster)
B4-FC02
B4-FC03
A4-FC02
B4-FC02
A4-FC03
Intercluster
COM SAN
switch 1A
Intercluster
COM SAN
switch 1B
Cluster 2 (same connections from each engine in cluster)
ISL 1
ISL 2
Intercluster
COM SAN
switch 2A
B4-FC03
A4-FC02
A4-FC03
NOTE: ISL is
inter-switch link
Intercluster
COM SAN
switch 2B
VPLX-000317
Figure 52 Fibre Channel WAN COM connections on VS1 VPLEX hardware
Internal cabling
101
Reference
Cluster 1
(same connections from each engine in cluster)
B5-GE00
B5-GE01
A5-GE00
A5-GE01
Cluster 2
IP
subnet A
B5-GE00
B5-GE01
A5-GE00
A5-GE01
IP
subnet B
VPLX-000368
Figure 53 IP WAN COM connections on VS1 hardware
VPLEX VS2 cabling
This section includes the following figures:

Cluster size
Cable type
Figure
Quad-engine
Ethernet
Serial
Fibre Channel
AC power
Ethernet
Serial
Fibre Channel
AC power
Ethernet
Serial
Fibre Channel
AC power
Fibre Channel WAN

COM
IP WAN COM
Dual-engine
Single-engine
All cluster
sizes, VPLEX
Metro or VPLEX
Geo only
102
Reference
VPLEX VS2 quad-engine configuration
Green, 37 in.
Purple, 37 in.
Engine 4
Green, 64 in.
Purple, 71 in.
Green, 64 in.
Purple, 71 in.
Engine 3
Management server
Purple, 37 in.
Green, 48 in.
Green, 37 in.
Purple, 71 in.
Engine 2
Engine 1
VPLX-000244
Figure 54 Ethernet cabling in a VPLEX VS2 quad-engine configuration
Internal cabling
103
Reference
Engine 4
19 in.
19 in.
Engine 3
19 in.
19 in.
UPS B
40 in.
UPS A
40 in.
Engine 2
19 in.
19 in.
Engine 1
19 in.
19 in.
VPLX-000247
Figure 55 Serial cabling in a VPLEX VS2 quad-engine configuration
104
Reference
Engine 4
79 in.
(all 16 cables)
Engine 3
Engine 2
Engine 1
VPLX-000250
Figure 56 Fibre Channel cabling in a VPLEX VS2 quad-engine configuration
labels.
Internal cabling
105
Reference
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
Engine 4
SPS 4
Engine 3
ON
I
ON
I
O
OFF
O
OFF
SPS 3

UPS B
UPS A
O
OFF
O
OFF
ON
I
ON
I
Management server
Engine 2
O
OFF
O
OFF
ON
I
ON
I
SPS 2
O
OFF
O
OFF
ON
I
ON
I
Engine 1
SPS 1
VPLX-000253
Figure 57 AC power cabling in a VPLEX VS2 quad-engine configuration
106
Reference
VPLEX VS2 dual-engine configuration
Purple, 71 in.
Green, 64 in.
Purple, 71 in.
Management server
Green, 48 in.
Green, 37 in.
Purple, 37 in.
Engine 2
Engine 1
VPLX-000245
Figure 58 Ethernet cabling in a VPLEX VS2 dual-engine configuration
Internal cabling
107
Reference
UPS B
40 in.
UPS A
40 in.
Engine 2
19 in.
19 in.
Engine 1
19 in.
19 in.
VPLX-000248
Figure 59 Serial cabling in a VPLEX VS2 dual-engine configuration
108
Reference
79 in. (all 16 cables)

Eight cables for a quad-engine configuration are included for
ease of upgrading, and are tied to the cabinet sidewalls
Engine 2
Engine 1
VPLX-000251
Figure 60 Fibre Channel cabling in a VPLEX VS2 dual-engine configuration
labels.
Internal cabling
109
Reference
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF

UPS B
UPS A
O
OFF
O
OFF
ON
I
ON
I
Management server
Engine 2
O
OFF
O
OFF
ON
I
ON
I
SPS 2
O
OFF
O
OFF
ON
I
ON
I
Engine 1
SPS 1
VPLX-000254
Figure 61 AC power cabling in a VPLEX VS2 dual-engine configuration
110
Reference
VPLEX VS2 single-engine configuration
Green, 48 in.
Purple, 71 in.
Management server
Engine 1
VPLX-000246
Figure 62 Ethernet cabling in a VPLEX VS2 single-engine configuration
Engine 1
19 in.
19 in.
VPLX-000249
Figure 63 Serial cabling in a VPLEX VS2 single-engine configuration
Engine 1
VPLX-000252
Figure 64 Fibre Channel cabling in a VPLEX VS2 single-engine configuration
Note: Both Fibre Channel cables are light blue. However, the A side cable has a blue label
and the B side cable has an orange label.
Internal cabling
111
Reference
O
OFF
O
OFF
ON
I
ON
I
Management server
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
Engine 1
SPS 1
VPLX-000255
Figure 65 AC power cabling in a VPLEX VS2 single-engine configuration
WAN COM cabling on VPLEX Metro and VPLEX Geo

Figure 66 and Figure 67 show the WAN COM connection options for VS2 hardware.
Cluster 1
Cluster 2
Intercluster
COM SAN
switch 1A
B2-FC01
ISL 1
Intercluster
COM SAN
switch 2A
A2-FC01
B2-FC01
A2-FC01
B2-FC00
A2-FC00
NOTE: ISL is
inter-switch link
B2-FC00
A2-FC00
Intercluster
COM SAN
switch 1B
ISL 2
Intercluster
COM SAN
switch 2B
Figure 66 Fibre Channel WAN COM connections on VS2 VPLEX hardware
112
VPLX-000234
Reference
Cluster 1
Cluster 2
IP
subnet A
B2-XG01
A2-XG01
B2-XG00
A2-XG00
IP
subnet B
B2-XG01
A2-XG01
B2-XG00
A2-XG00
VPLX-000235
Figure 67 IP WAN COM connections on VS2 VPLEX hardware
Cabinet power connections

Notes:
The upper PDUs are not used
in a single-engine configuration.
Outlet group
circuit breaker
OG
ON
I
O
OFF
O
OFF
OG
Power distribution
unit (PDU)
OG
ON
I
OG
ON
I
ON
I
O
OFF
O
OFF
OG
OG
ON
I
ON
I
O
OFF
O
OFF
The upper PDUs are installed

upside-down from the lower PDUs.
Therefore, each circuit breaker in
the upper PDUs controls the outlet
group (OG) directly above it, while
each circuit breaker in the lower
PDUs controls the outlet group
directly below it.
Outlet groups
O
OFF
O
OFF
ON
I
ON
I
OG
OG
OG
OG
OG
OG
O
OFF
Power distribution
panel (PDP)
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
To 30 A, 220 VAC
power source 2
To 30 A, 220 VAC
power source 1
Rear view
VPLX-000080
Figure 68 Power connectors in a VPLEX cabinet
Cabinet power connections
113
Reference
UPS LEDs
Online LED
Overload LED
UPS: Front view
On battery LED
Replace battery LED
Power button
UPS: Rear view
AC input indicators Circuit breakers
VPLX-00121
Figure 69 APC UPS
Overload LED
UPS: Front view
Online LED
On battery
LED
On/off button
Replace battery
LED
UPS: Rear view
AC input indicators
Figure 70 Emerson UPS
114
Circuit breakers
VPLX-000559
INDEX
A
addresses of hardware components 86
C
cabling, internal
VPLEX VS1 dual-engine configuration 96
VPLEX VS1 quad-engine configuration 92
VPLEX VS1 single-engine configuration 100
VPLEX VS2 dual-engine configuration 107
VPLEX VS2 quad-engine configuration 103
VPLEX VS2 single-engine configuration 111
Cluster Witness 70
cluster, defined 79
I
IP addresses 86
L
LEDs
Fibre Channel switch 15
management server 15
UPS 14
P
password, management server service account 24, 47
power connections to PDUs 113
U
username, management server service account 24, 47
V
VPLEX Witness 70
W
web server, restarting 31
115
Index
116

Vplex

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vplex

Uploaded by

Copyright:

Available Formats

EMC VPLEX

EMC VPLEXConfiguration Guide

Cautions and Warnings

Configuring a VPLEX Local implementation

Configuring a VPLEX Metro or VPLEX Geo implementation

Upgrading an Unconfigured System

EMC VPLEXConfiguration Guide

AC power cabling in a VPLEX VS1 single-engine configuration ...................................

EMC VPLEX Configuration Guide

Cautions and Warnings

Additional warnings and cautions

EMC VPLEXConfiguration Guide

Cautions and Warnings

Always use the correct tools for the job.

Always use the correct replacement parts.

Keep all paperwork, including incident reports, up to date, complete, and

Store all printed circuit boards in antistatic bags.

Use a ground strap whenever you handle a printed circuit board.

Unless specifically designed for nondisruptive replacement, never plug or

EMC VPLEXConfiguration Guide

Changes since previous revision

Chapter 3 - Task 27 updated to include path to IP configuration worksheet.

Added directions for upgrading an unconfigured system to Release 5.3.

Changes made to support Release 5.4.

Changes made to support Release 5.4.1 and general defect fixes.

EMC VPLEX Release Notes for GeoSynchrony Releases

EMC VPLEX Product Guide

EMC VPLEX Site Preparation Guide

EMC VPLEX Hardware Installation Guide

EMC VPLEX Configuration Worksheet

EMC VPLEX Configuration Guide

EMC VPLEX Security Configuration Guide

EMC VPLEXConfiguration Guide

EMC VPLEX CLI Reference Guide

EMC VPLEX Administration Guide

VPLEX Management Console Help

EMC VPLEX Element Manager API Guide

EMC VPLEX Open-Source Licenses

EMC VPLEX GPL3 Open-Source Licenses

EMC Regulatory Statement for EMC VPLEX

Procedures provided through the Generator

EMC Host Connectivity Guides

Conventions used in this document

Used in running (nonprocedural) text for:

Used in running (nonprocedural) text for:

EMC VPLEXConfiguration Guide

Used in all text (including procedures) for:

Used in procedures for:

Square brackets enclose optional values

Vertical bar indicates alternate selections - the bar means or

Braces indicate content that you must specify (that is, x or y or z)

Ellipses indicate nonessential information omitted from the example

Where to get help

EMC VPLEXConfiguration Guide

EMC VPLEXConfiguration Guide

On-Battery (if steady amber)

Figure 1 SPS LEDs

Blinking amber during boot-up

Blinking amber during firmware load

Figure 2 VS1 director LEDS during and after power-up

PS power LEDs: Steady green

Figure 3 VS2 engine LEDs after power-up

UPS: Front view