VPLEX 4.0 Installation and Setup Guide

EMC VPLEX
v4.0
Installation and Setup Guide

P/N 300-010-499
REV A03
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright 2010 EMC Corporation. All rights reserved.

Published December, 2010
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.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
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 Document/Whitepaper Library on EMC
Powerlink.
EMC VPLEX v4.0 Installation and Setup Guide
Contents
Preface.................................................................................................................................................... 13
Chapter 1
Introduction
VPLEX overview.....................................................................................................
Major components ............................................................................................
Preparing for a new installation ...........................................................................
Required information.......................................................................................
Required hardware...........................................................................................
Required software ............................................................................................
Required tools ...................................................................................................
Reference: VPLEX requirements ....................................................................
Chapter 2
16
18
20
20
20
21
21
21
Installing the Hardware

Installing a cluster................................................................................................... 24
Task 1: Unpack and set up the cabinet .......................................................... 24
Task 2: Check the components ....................................................................... 24
Task 3: Stabilize the equipment ...................................................................... 25
Task 4: Connect the front-end and back-end cables .................................... 26
Task 5: Connect to the customer network ..................................................... 28
Task 6: Metro-Plex only: Cable the clusters .................................................. 28
Task 7: Power on the components .................................................................. 29
Chapter 3
Setting up VPLEX
Preliminary tasks .................................................................................................... 34
Setting up a VPLEX Local implementation ........................................................ 35
Task 1: Set the management servers public IP address ............................. 35
Task 2: Launch the VPLEX EZ-Setup Wizard .............................................. 42
Task 3: Verify the product version ................................................................. 42
Task 4: Verify the VPLEX directors ................................................................ 42
Task 5: Open a second PuTTY session ........................................................... 43
Task 6: Verify the director count .................................................................... 43
Task 7: Verify the Fibre Channel switches if present .................................. 43
Task 8: Expose back-end storage .................................................................... 43
Task 9: Verify storage volume availability ................................................... 44
Task 10: Create a meta-volume ....................................................................... 44
Task 11: Determine the TLA ........................................................................... 45
Task 12: Configure Call Home ........................................................................ 46
Task 13: Configure SYR ................................................................................... 48

Task 14: Verify back-end connectivity .......................................................... 49
Task 15: Enable the front-end ports ............................................................... 50
Task 16: Set up ESRS if necessary .................................................................. 50
Task 17: Ensure that the I/O ports are zoned .............................................. 51
Task 18: Expose storage to hosts .................................................................... 51
Task 19: Perform a rescan ............................................................................... 54
Setting up a VPLEX Metro implementation....................................................... 55
Task 1: Set the management servers public IP address ............................. 55
Task 2: Launch the EZ-Setup wizard ............................................................ 64
Task 3: Verify the product version ................................................................ 64
Task 4: Verify the VPLEX directors ............................................................... 64
Task 5: Open a second PuTTY session .......................................................... 65
Task 6: Verify the director count .................................................................... 65
Task 7: Verify the Fibre Channel switches if present .................................. 65
Task 8: Expose back-end storage ................................................................... 65
Task 9: Verify storage volume availability ................................................... 66
Task 10: Create a meta-volume ...................................................................... 66
Task 12: Configure Call Home ....................................................................... 68
Task 16: Connect to cluster 2 .......................................................................... 72
Task 17: Launch the EZ-Setup wizard .......................................................... 80
Task 18: Verify the product version .............................................................. 80
Task 19: Verify the VPLEX directors ............................................................. 80
Task 20: Open a second PuTTY session ........................................................ 81
Task 21: Verify the director count .................................................................. 81
Task 22: Verify the Fibre Channel switches if present ................................ 81
Task 23: Expose back-end storage ................................................................. 81
Task 24: Verify storage volume availability ................................................. 81
Task 25: Create a meta-volume ...................................................................... 82
Task 27: Configure Call Home ....................................................................... 83
Task 31: Enable the WAN ports ..................................................................... 87
Task 32: Set up ESRS if necessary .................................................................. 88
Task 33: Open a VPlexcli session on cluster 1 .............................................. 88
Task 34: Verify the date and time on both clusters ..................................... 88
Task 35: Complete the setup on cluster 1 ..................................................... 89
Task 36: Enable the WAN ports on cluster 1 ................................................ 89
Task 37: Zone the WAN ports ........................................................................ 89
Task 38: Connect cluster 1 to the directors in cluster 2 ............................... 89
Task 39: Connect cluster 2 to the directors in cluster 1 ............................... 89
Task 40: Join the clusters ................................................................................. 90
Task 41: Create logging volumes ................................................................... 90
Task 42: Verify that the clusters are fully connected .................................. 92
Task 43: Verify the cluster status ................................................................... 92
Task 44: Verify back-end connectivity on cluster 2 ..................................... 92
Task 45: Verify back-end connectivity on cluster 1 ..................................... 93
Task 46: Expose storage to hosts .................................................................... 93
Task 47: Perform a rescan ............................................................................... 96
Appendix A
Reference
IP addresses and component IDs ......................................................................... 98
Internal cabling ..................................................................................................... 100
Quad-engine cluster ....................................................................................... 101
Dual-engine cluster ........................................................................................ 105
Single-engine cluster ...................................................................................... 109
Cabinet power connections ................................................................................. 111
Index ...................................................................................................................................................... 113
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
Page
VPLEX hardware example: Single-engine cluster............................................................

VPLEX hardware example: Dual-engine cluster ..............................................................
VPLEX hardware example: Quad-engine cluster.............................................................
Engine components...............................................................................................................
I/O port connections to redundant fabrics .......................................................................
Directors and I/O module carrier ......................................................................................
Power cable wire bails ..........................................................................................................
Engine components: Front view .........................................................................................
VPLEX I/O ports...................................................................................................................
Cabling to front-end and back-end I/O ports ..................................................................
Management server connection to customer IP network................................................
Intercluster cabling................................................................................................................
WAN cable routing on cable holders .................................................................................
Cabinet power switches and circuit breakers ...................................................................
SPS power switches ..............................................................................................................
SPS and director LEDs..........................................................................................................
UPS, front view......................................................................................................................
UPS, rear view .......................................................................................................................
Fibre Channel switch, rear (port side) view ......................................................................
Management server power button and LEDs...................................................................
Laptop connection to management server ........................................................................
PuTTY settings for VPLEX_service session.......................................................................
PuTTY configuration: SSH protocol ...................................................................................
PuTTY configuration: Scrollback setting ...........................................................................
PuTTY Configuration: Logging window...........................................................................
Director A-side addresses ....................................................................................................
PuTTY settings for logging in over the customer network.............................................
VPLEX Management Console: Provision Storage button ...............................................
Laptop connection to management server ........................................................................
PuTTY settings for VPLEX_service session.......................................................................
PuTTY configuration: SSH protocol ...................................................................................
Director A-side addresses in cluster 1................................................................................
PuTTY settings for logging in to cluster 1 over the customer network ........................
PuTTY settings for logging in to cluster 2 over the customer network ........................
16
17
18
19
22
24
24
25
26
27
28
28
29
30
30
31
31
31
32
32
35
36
37
37
38
39
40
41
41
51
55
56
57
58
59
60
62
62
63
63
Figures
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
Laptop connection to management server........................................................................ 73

PuTTY settings for VPLEX_service session ...................................................................... 74
PuTTY configuration: SSH protocol .................................................................................. 74
PuTTY configuration: Scrollback setting........................................................................... 75
PuTTY Configuration: Logging window .......................................................................... 76
Director A-side addresses.................................................................................................... 77
PuTTY settings for logging in to cluster 2 over the customer network ........................ 78
PuTTY configuration: Scrollback setting........................................................................... 78
PuTTY Configuration: Logging window .......................................................................... 79
VPLEX Management Console: Provision Storage button............................................... 93
Component IP addresses in cluster 1................................................................................. 98
Component IP addresses in cluster 2................................................................................. 99
Ethernet cabling in a quad-engine cluster....................................................................... 101
Serial cabling in a quad-engine cluster............................................................................ 102
Fibre Channel cabling in a quad-engine cluster............................................................. 103
AC power cabling in a quad-engine cluster ................................................................... 104
Ethernet cabling in a dual-engine cluster........................................................................ 105
Serial cabling in a dual-engine cluster............................................................................. 106
Fibre Channel cabling in a dual-engine cluster.............................................................. 107
AC power cabling in a dual-engine cluster .................................................................... 108
Ethernet cabling in a single-engine cluster ..................................................................... 109
Serial cabling in a single-engine cluster .......................................................................... 109
Fibre Channel cabling in a single-engine cluster ........................................................... 109
AC power cabling in a single-engine cluster.................................................................. 110
Power connectors in a VPLEX cabinet............................................................................. 111
Tables
Title
1
2
Page
Major VPLEX hardware components................................................................................. 18

Data center acclimation times ............................................................................................. 25
Tables
10
Warnings and Cautions
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:
WARNING
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.
11
Warnings and Cautions
WARNING
This product operates at high voltages. To protect against physical harm, power off
the system whenever possible while servicing.
WARNING
In case of fire or other emergency, isolate the system's power involved and alert
appropriate personnel.
CAUTION
Trained personnel are advised to exercise great care at all times when working on
the EMC hardware.
Remember to:
Static precautions
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.
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.
CAUTION
Before handling printed circuit boards or other parts containing LSI and/or VLSI
components, observe the following precautions:
12
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.
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.
Related
documentation
Conventions used in
this document
Related documentation (avaliable on EMC Powerlink) includes:
EMC VPLEX Site Preparation Guide
EMC VPLEX Pre-installation Configuration Worksheet
EMC VPLEX V4.0 Security Configuration Guide
EMC VPLEX V4.0 Getting Started Guide
EMC VPLEX Release 4.0 and Point Releases Release Notes
EMC Best Practices Guide for AC Power Connections in Two-PDP Bays
EMC AC Power Configuration Worksheet
40U-C Unpacking and Setup Guide
EMC VPLEX v4.0 CLI Guide
Implementation and Planning Best Practices for EMC VPLEX Technical Notes
Customer Service Procedure: EMC Secure Remote Support Gateway, available in the
Application Download Area on the Global Services website
VPLEX online help, available on the Management Console GUI
VPLEX procedure generator, available on EMC Powerlink
EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.
13
Preface
CAUTION
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.
WARNING
A warning contains information essential to avoid a hazard that can cause severe
personal injury, death, or substantial property damage if you ignore the warning.
Typographical conventions
EMC uses the following type style conventions in this document:
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
Where to get help
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
<>
Angle brackets enclose parameter or variable values supplied by the user
[]
Square brackets enclose optional values
Vertical bar indicates alternate selections - the bar means or
EMC support, product, and licensing information can be obtained as follows.

Product information For documentation, release notes, software updates, or for
information about EMC products, licensing, and service, go to the EMC Powerlink
website (registration required) at:
http://Powerlink.EMC.com
Technical support For technical support, go to EMC Customer Service on

Powerlink. To open a service request through Powerlink, you must have a valid
support agreement. Please contact your EMC sales representative for details about
obtaining a valid support agreement or to answer any questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and
overall quality of the user publications. Please send your opinion of this document to:
techpubcomments@EMC.com
14
1
Introduction
This chapter provides an overview of the EMC VPLEX hardware components.

Note: Review the Documentation section in the current VPLEX release notes for any
corrections to this document. EMC recommends that you mark up a copy of this guide with
any corrections identified in the release notes. This can help minimize errors during
installation.
VPLEX overview ........................................................................................................... 16

Preparing for a new installation.................................................................................. 20
Introduction
15
Introduction
VPLEX overview
Figure 1 through Figure 3 show the main hardware components in the three available
configurations of an EMC VPLEX cluster (a single-cabinet configuration). A
VPLEX implementation can be VPLEX Local (single cluster) or VPLEX Metro
(two clusters, separated by up to 5 ms round trip time, or RTT).
ON
I
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
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
Management server
ON
I
O
OFF
Engine 1
Director 1B
Director 1A
SPS 1
Zep-008
Figure 1
VPLEX hardware example: Single-engine cluster
The component placement in single-engine and dual-engine clusters allows for

nondisruptive upgrades to larger configurations. Note, however, that the current
VPLEX release does not support upgrading to a larger cluster configuration.
16
Introduction
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
Zep-07
Figure 2
VPLEX hardware example: Dual-engine cluster
VPLEX overview
17
Introduction
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
COM switch B
UPS B
COM 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
Zep-06
Figure 3
Major components
Table 1
18
VPLEX hardware example: Quad-engine cluster
Table 1 describes the major hardware components in a VPLEX cluster.
Major VPLEX hardware components
Component
Description
Engine (shown in
Figure 4 on page 19)
Contains the following:

Two directors, each containing four Fibre Channel I/O modules. Two I/O modules are dedicated to
front-end host connections, and two are dedicated to back-end storage connections. Each I/O
module contains four 8 Gb/s Fibre Channel ports.
I/O module carrier, containing two Fibre Channel I/O modules (one for each director) for intersite
and intrasite communication. Each I/O module provides four Fibre Channel ports.
CPU module.
Two 30 GB solid state drives (SSDs), one for each director.
Two management modules
Two redundant power supplies
Four fans
Standby power
supply (SPS)
Provides backup power (through a pair or redundant modules) that allows an engine to ride through
transient (30 seconds or less) power loss.
Introduction
Table 1
Major VPLEX hardware components
Component
Description
Fibre Channel COM

switches
Provide highly available connectivity among the directors in a medium (two-engine) or large
(four-engine) cluster.
Uninterrupted power
supplies (UPS)
Provide backup power to the COM switches and management server in a medium or large cluster,
allowing the connected components to continue operating through a power loss of up to 30 seconds.
Management server
Provides management to the other components in the cluster, and provides an interface for access
from a remote management station.
Management server functions include:
Hosting VPLEX software.
Providing an interface between the customer and the VPLEX cluster.
Generating Call Home events.
Enabling secure management between clusters in a Metro-Plex.
Protecting the internal management network from the customer LAN.
Providing access to VPLEX components for field-replaceable unit (FRU) replacement procedures.
Facilitating nondisruptive upgrades (NDU)
Figure 4
Engine components
VPLEX overview
19
Introduction
Preparing for a new installation

Note: Although most of this guide is intended for use by customers, this section is for use by
EMC personnel.
Before installing a new VPLEX cluster:
Verify that all necessary hardware has been received at the customer site(s), as
documented in the purchase order and shipping list.
Verify that two storage devices of at least 78 GB each have been allocated for use
as a VPLEX meta-volume and a mirrored copy. (The meta-volume will contain
RAID and virtual volume metadata.)
Each storage device should be from a different array.
Note: If the meta-volume is on an EMC CLARiiON array, there must be active paths to
all VPLEX directors from the meta-volume LUN.
You must ensure that these storage devices will provide a maximum average
response time of 10 ms (for random 4K reads). The best practice to ensure this is
to allocate dedicated spindles on the array for any LUN that will be used as part
of the meta-volume mirror.
Verify that you have the following EMC Secure Remote Support (ESRS) gateway
information:
ESRS gateway account.
Model Number VS1
Serial Number Top-level assembly number (TLA) of the cluster, available
on the serial number tag attached to the top rear of the cabinet frame member
(and on the packing slip)
Site ID Provided by ESRS
IP address Address of the public Ethernet port on the VPLEX management
server
Verify that the conditions identified in Reference: VPLEX requirements on

page 21 have been met.
Required
information
Confirm that you have completed the VPLEX Pre-installation Configuration Worksheet,
available with other VPLEX documentation on EMC Powerlink.
Required hardware
You must have a laptop, desktop, PC, or similar device with a keyboard and
graphical interface 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.
Before starting the installation and configuration procedures described in this guide,
confirm that your laptop has the following:
20
USB port.
CD-ROM drive.
Introduction
Required software
Fully charged batteries For mobility between the lab environment and a
quieter location from which you can perform most of the configuration tasks.
Generally, access to power outlets will not be a problem. Just in case, however,
fully charged batteries could be useful.
Laptop power supply or laptop-to-rack power cord For assurance of power.
Confirm that you have the following on your laptop:
Windows OS
PuTTY, version 0.60 or later (download from www.putty.org) or similar SSH

client
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
Required tools
Reference: VPLEX
requirements
You will need the following tools when unpacking and installing a VPLEX cluster:
Screwdrivers (#2 Phillips and medium flat-head)
Adjustable or 3/4-inch wrench (to remove shipping plates)
7/16-inch socket wrench (to remove shipping plates)
8 mm Allen wrench or cabinet door key (to open and secure the doors)
Knife or wire cutters (to cut strapping)
Use redundant physical Fibre Channel links to connect:
Each host to the VPLEX directors
Each director to the back-end storage
To prevent data unavailability:
Ensure that each host in a storage view has paths to at least two directors in each
cluster.
Ensure that multi-pathing is configured in such a way that the paths are
distributed evenly between directors A and B in each engine.
Use redundant SAN fabrics as shown in Figure 5 on page 22.

As the figure shows, 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 I/O module fails.
Preparing for a new installation
21
Introduction
Figure 5
22
I/O port connections to redundant fabrics
2
Installing the
Hardware
This chapter describes the tasks to install the VPLEX hardware at a customer site.
Note: Although much of this guide is intended for use by customers, this chapter is for use
primarily by EMC personnel.
Installing a cluster ......................................................................................................... 24
23
Installing a cluster
Task 1: Unpack and
set up the cabinet
Follow the steps in the EMC 40U-C Cabinet Unpacking and Setup Guide, which
accompanies each VPLEX cabinet (and is available on Powerlink).
Task 2: Check the

components
Confirm that no components loosened during shipping:

1. From the rear of the cabinet, push each director and the I/O module carrier
(shown in Figure 6) inward, to verify that these components are fully seated.
Director n B
Director n A
I/O module carrier
Figure 6
Zep-041
Directors and I/O module carrier
If any of these components is not fully seated, loosen the orange captive screws,
push the component firmly into the backplane, and retighten the thumbscrews.
2. Confirm that all I/O modules are fully seated.
3. Confirm that all thumbscrews are finger-tight.
4. Confirm that all cables in the cabinet (except AC cables to site power) are securely
connected, and that the wire bail on each SPS power cable, as well as (if present)
each UPS and Fibre Channel switch power cable, is secure.
The bail on each SPS and UPS cable must be clamped onto the plugs plastic
molding, and the bail on each Fibre Channel switch must be clamped onto the
cable itself, as shown in Figure 7.
SPS and UPS:

The wire cable bail is inserted into
the middle of the plugs plastic molding.
Fibre Channel switch:

The wire cable bail is against
the end of the plugs plastic molding.
SYM-002500z
Figure 7
Power cable wire bails
If any cable has become disconnected, reconnect it as identified by the labels on

the cable and cabinet, as well as Internal cabling on page 100 of this guide.
24
5. From the front of the cabinet, remove each engines bezel as shown inFigure 8 ,
and verify that the two power supply modules, four fan modules, and solid state
drive (SSD) enclosure are fully inserted and secure.
Power supply
Fan
SSD enclosure
CL4341c
Engine components: Front view
Figure 8
Task 3: Stabilize the

equipment
Table 2
The equipment requires time to become acclimated to a data center environment.

Table 2 lists the required times.
Data center acclimation times
Transit/storage environment
Condition
Temperature range
Relative humidity
Hours required
before applying
power
Nominal
68o to 72oF (20o to 22oC)
Less than 30%
Cool / Damp Less than 68oF (20oC)
30% or greater
Less than 86oF (30oC)
Cold / Dry
Less than 68oF (20oC)
Less than 20%
Hot / Dry
Less than 30%
Hot / Humid
30% to 45%
45% to 60%
60% to 80%
16
Conditioned air: nominal office

or computer room environment
(< 30% relative humidity)
Note: Temperature and humidity values must be such that condensation does not occur on any
VPLEX component. Altitude and atmospheric pressure specifications are referenced to a
standard day at 58.7F (14.8C). Maximum wet bulb temperature is 82F (28C).
25
Task 4: Connect the

front-end and
back-end cables
Figure 9
Connect customer-supplied Fibre Channel cables from the front-end and back-end
SANs to the appropriate VPLEX I/O ports (identified in Figure 9).
VPLEX I/O ports
Route the cables horizontally to the sides of the cabinet as shown in Figure 10 on
page 27, to prevent blocking other components in the cabinet. Route the cables down
the sides of the cabinet through the plastic cable holders, and secure the cables with
the Velcro straps that are attached to the cabinet frame. Maintain a minimum radius
of two inches for any bend in a Fibre Channel cable.
26
Front-end
cables
Back-end
cables
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
Engine 4
Engine 3
ON
I
ON
I
O
OFF
O
OFF
Engine 2
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
Zep-005_FC
Figure 10
Cabling to front-end and back-end I/O ports
27
Task 5: Connect to
the customer
network
Connect the management server to the customer IP network as shown in Figure 11.
Customer-provided Ethernet cable

1 Gb/s public Ethernet port
Customer
IP network
zep-09a
Figure 11
Task 6: Metro-Plex
only: Cable the
clusters
Management server connection to customer IP network
In a Metro-Plex configuration, connect each director in each cluster (through its WAN
ports on the I/O module carrier) to the intercluster SAN as shown in Figure 12:
1. Label each WAN cable at both ends to identify the connections.
2. Secure the WAN cables in the cable holders below the engines as shown in
Figure 13 on page 29, and route the cables up or down the sides of the cabinet
with the I/O cables.
Cluster 1 (same connections from each engine in cluster)
B4-FC02
B4-FC03
A4-FC02
Intercluster
COM SAN
switch 1B
Figure 12
28
B4-FC02
A4-FC03
Intercluster
COM SAN
switch 1A
Intercluster cabling
Cluster 2 (same connections from each engine in cluster)
ISL 1
ISL 2
Intercluster
COM SAN
switch 2A
Intercluster
COM SAN
switch 2B
B4-FC03
A4-FC02
A4-FC03
Zep-049
Separate wires
around posts
0
Remove cap to route

cables, and then
replace cap
1
2
3
3
Detail
0
1
0
0
1
1
2
2
3
3
0
2
e
ul
od
M
A
0
0
I/O
1
1
Route cables from ports A4-FC02

and B4-FC02 to B side
2
2
3
3
Route cables from ports

A4-FC03 and B4-FC03 to A side
Figure 13
Task 7: Power on the

components
zep-070a
WAN cable routing on cable holders
1. Verify that all PDP switches and PDU circuit breakers (shown in Figure 14 on
page 30) are in the OFF position. As the figure notes, the upper pair of PDUs are
installed upside-down from the lower pair, and the upper PDPs are not used.
2. Complete the EMC AC Power Configuration Worksheet, and place it in a convenient
location foe use in verifying the data center power schemes.
3. Connect the main AC power cables from the lower PDPs into the sites power
sources. To ensure high availability, each cable must connect to a different power
source, as described in the EMC Best Practices Guide for AC Power Connections in
Two-PDP Bays.
29
Notes:
The upper PDPs are installed,
but are not used.
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
The upper PDUs are not used in a

single-engine configuration.
The upper PDUs are installed
upside-down from the lower PDUs.
PDU circuit
breakers
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
O
OFF
O
OFF
ON
I
ON
I
PDP power
switch
To 30 A, 220 VAC
power source 2
Figure 14
PDP power
switch
To 30 A, 220 VAC
power source 1
Zep-013
Cabinet power switches and circuit breakers
4. Switch all SPS power switches (shown in Figure 15) ON.
CL4171
Figure 15
SPS power switches
5. Switch both lower PDPs ON.

6. Switch ON each PDU switch that has components plugged into its power strip.
(Figure 65 on page 111 identifies the circuit breaker associated with each power
strip.)
7. Verify that the LED status on each SPS and director is as shown in Figure 16 on
page 31.
30
Generally, 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, verify that the components are cabled correctly.
Director LEDs
Steady green
Amber during POST, off
during normal operation
SPS LEDs:
On-line Enabled (LED on) or On-line Charging (LED flashing)
On-Battery
Replace Battery
Internal Check
Figure 16
Zep-011a
SPS and director LEDs
8. If the cluster is dual-engine or quad-engine:

a. Verify that the Online LED on each UPS (shown in Figure 17) is illuminated
(green), and that none of the other three LEDs shown in Figure 17 is
illuminated.
If the Online LED on either UPS is not illuminated, push the power button,
and verify that the LED is illuminated before proceeding.
Online LED
Overload LED
On battery LED
Replace battery LED
Power button
Figure 17
sym-001521z
UPS, front view
b. Verify that neither circuit breaker (shown in Figure 18) on either UPS has
triggered. If a circuit breaker has triggered, press it to reseat it.
Circuit breakers
Zep-036a
Figure 18
UPS, rear view
31
c. Verify that the Power and Status LEDs (shown in Figure 19) on both Fibre
Channel switches are steady green.
Status LED
Power LED
Figure 19
Zep-034
Fibre Channel switch, rear (port side) view
9. Remove the bezel from the front of the management server.

10. On the front of the management server (Figure 20), verify that the power LED is
illuminated.
If the LED is not on, press the power button.
Power button
Figure 20
Power LED
Management server power button and LEDs
11. Replace the management server bezel.
32
Zep-015
3
Setting up VPLEX
This chapter describes the tasks to set up a VPLEX Local or VPLEX Metro
implementation. Topics include:
Preliminary tasks........................................................................................................... 34
Setting up a VPLEX Local implementation ............................................................... 35
Setting up a VPLEX Metro implementation.............................................................. 55
Setting up VPLEX
33
Setting up VPLEX
Preliminary tasks
Before you begin the VPLEX setup tasks, perform the following steps:
Note: The values (especially version numbers) in any command output in this document that is
identified as an example might not match what you see on a customer system.
1. Confirm that you know where to find the following documentation on EMC
Powerlink:
Best Practices white papers.
EMC VPLEX Pre-installation Configuration Worksheet. This document is in
Microsoft Word format, to provide a means of typing information (such as IP
addresses) that you will need during the setup procedure.
EMC VPLEX CLI Guide, which provides detailed information on the VPlexcli
commands identified in this installation and setup guide.
VPLEX Procedure Generator, which contains procedures to upgrade to a new
GeoSynchrony (VPLEX operating system) release, and to troubleshoot
installation or configuration issues.
2. If not already done, download the EMC VPLEX Pre-installation Configuration
Worksheet and add the required information.
3. Install and launch the VPLEX Procedure Generator as directed on Powerlink.
Then:
a. Generate a troubleshooting document, for reference if necessary during the
setup procedure. In the procedure generator, follow the link VPLEX >
Troubleshooting > Installation and setup issues.
b. If you are going to upgrade GeoSynchrony to a later release, generate an
upgrade document. In the procedure generator, follow the link VPLEX >
Upgrade Procedures > Upgrade to VPLEX release <number>.
CAUTION
If you want to upgrade to a later GeoSynchrony release, you must perform the
entire 4.0 setup procedure as documented in this guide, and then perform an
upgrade to the desired release.
Note: If any operation described in this document fails, review the troubleshooting
document. If this does not resolve the problem, contact the EMC Support Center.
Next step
34
Proceed to the applicable section:
Setting up a VPLEX Local implementation on page 35
Setting up a VPLEX Metro implementation on page 55
Setting up VPLEX
Setting up a VPLEX Local implementation

!
CAUTION
If you are setting up a VPLEX Metro implementation, follow the tasks in Setting
up a VPLEX Metro implementation on page 55. You cannot set up each cluster
individually and then join them later.
Task 1: Set the

management
servers public IP
address
Before you can log in to the VPLEX management server over the customer network,
you must set the address on the management servers public Ethernet port:
Note: The tasks in this document use PuTTY for logging in to the management server.
However, you can use any similar Telnet/SSH client.
1. Connect your laptop to the management server as shown in Figure 21, using the
red service cable that hangs inside the EMC cabinet.
Laptop
Red service cable in cabinet
Service port
Mgmt-B port
Figure 21
Public Ethernet port
Mgmt-A port
zep-009b
Laptop connection to management server
2. On your laptops toolbar, select Start > Settings > Control Panel > Network
Connections (double-click).
3. If any public network connection is enabled on your laptop, right-click the
network card and select Disable.
4. On the Network Connections window, right-click Local Area Connection and
select Properties.
5. On the Local Area Connection Properties window, double-click Internet
Protocol (TCP/IP) under This connection uses the following items.
6. On the Internet Protocol (TCP/IP) Properties window:
a. If your laptop is configured with specific addresses, make a note of them, to
ensure that you reset the configuration correctly later.
b. Select Use the following IP addresses, and type the following values:
IP address:
128.221.252.3
Subnet mask:
255.255.255.224
Default gateway: 128.221.252.2
7. Click OK on the Internet Protocol (TCP/IP) Properties window, and again on the
Local Area Connection Properties window.
8. Close the Network Connections window.
35
Setting up VPLEX
9. Open a Command Prompt window (Start > Programs > Accessories > Command
Prompt), and type the following command to confirm the settings:
ipconfig
Output example:
Ethernet adapter Local Area Connection:
Connection-specific
IP Address. . . . .
Subnet Mask . . . .
Default Gateway . .
DNS
. .
. .
. .
Suffix
. . . .
. . . .
. . . .
.
.
.
.
:
:
:
:
eng.emc.com
128.221.252.3
255.255.255.224
128.221.252.2
10. Type the following command to verify that you can reach the management
servers service port:
ping 128.221.252.2
11. On your laptop, launch PuTTY.exe.

Note: If you see a PuTTY security alert, read it, and then click yes.
12. 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
13. Select SSH in the Category list, and ensure that Preferred SSH protocol version
is set to 2, as shown in Figure 23.
36
Setting up VPLEX
SSH protocol
version
putty_ssh
Figure 23
PuTTY configuration: SSH protocol
14. For most of the 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 are going to move your connection (as described later), go to step 15.
If you are going to remain connected directly for the entire setup procedure,
read the following information, and then perform any desired steps:
The output from some commands you will type is too long to read in a
standard-size PuTTY session window. One solution is to extend the
scrolling capability. To do this, select Window in the Category list, and set
Lines of scrollback (shown in Figure 24) to 20000.
Set to 20000
scrollback
Figure 24
PuTTY configuration: Scrollback setting
37
Setting up VPLEX
Another solution to long displays is to save the session output to a log file.
Over the course of setting up a dual-engine or quad-engine cluster, the log
file can grow quite large. However, if you want to create a log file anyway:
i. Select Logging in the PuTTY Configuration Category list.
ii. Under Session logging, select All session output.
iii. Type a name in the Log file name field (shown in Figure 25).
Note: Over the course of setting up a dual-engine or quad-engine cluster, the log
file can grow quite large.
Note: The log file saves data from the current PuTTY session. Any time you open a
new session, you must repeat this step if you want to log the output for that session.
All session output

File name
putty_log
Figure 25
PuTTY Configuration: Logging window
15. Select Session in the Category list, and click Save in the PuTTY Configuration
window to save the settings for the session you configured.
16. Click Open to establish a connection to the management server, and log in with
username service and password Mi@Dim7T.
Note the following:
If the connection fails to open, ping 128.221.252.3 (the LAN port on your
laptop) to verify intercomponent communication. If the ping is successful,
ping 128.221.252.2 (the service port on the management server).
The default Linux shell prompt for username service is
service@<current_working_directory>.
17. From the Linux shell prompt, type the following command to verify that the
VPlexcli process started:
sudo /etc/init.d/VPlexElementManager status
38
Setting up VPLEX
18. From the shell prompt, type the following command:

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.
sudo /opt/emc/VPlex/tools/ipconfig/changehostname.py -n <hostname>
where <hostname> is a name for the management server, such as Cluster1. (The
cluster is assigned a Cluster ID of 1 automatically.) This name replaces the default
name (service) in the shell prompt the next time you open an SSH session to the
management server.
19. From the shell prompt, type the following command, to verify connectivy to
director 1-A:
ping 128.221.252.35 -c 5
Note that -c 5 sets the number of pings to 5.

20. Repeat step 19 once for each director in the cluster, substituting the applicable
address shown in Figure 26.
Quad-engine
cluster
Engine 4:
Director 4-B
Director 4-A
128.221.252.42
128.221.252.41
Engine 3:
Director 3-B
Director 3-A
128.221.252.40
128.221.252.39
Engine 2:
Director 2-B
Director 2-A
128.221.252.38
128.221.252.37
Engine 1:
Director 1-B
Director 1-A
128.221.252.36
128.221.252.35
Dual-engine
cluster
Single-engine
cluster
Figure 26
Director A-side addresses
21. Type the following command to connect to the VPlexcli:

telnet localhost 49500
Log in with username service and password Mi@Dim7T.

22. Type the following to configure the IP address of the management servers public
Ethernet port:
management-server set-ip -i <IP_address>:<netmask> -g <gateway> eth3
39
Setting up VPLEX
23. The next step depends on how you want to proceed:

If you want to leave your laptop connected to the management server, go to
Task 2: Launch the VPLEX EZ-Setup Wizard on page 42.
If you want to connect over the network, proceed to step 24.
24. If you want to connect over the customer network to perform the remaining setup
tasks, type the following command at the VPlexcli prompt, and again at the Linux
shell prompt:
exit
25. Disconnect the red service cable from your laptop and the management server,
and return the cable to its location on the inside of the cabinet.
26. Prepare for connection to the customer network:
If you are connecting your laptop to the network, set it to an IP address on the
network.
If you are connecting 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 or other Telnet/SSH client is installed on the device, and
install it if necessary.
c. Set the device to an IP address on the customer network.
27. Launch PuTTY.exe, and configure PuTTY as shown in Figure 27.
Address of public
Ethernet port on
management server
(default)
Session name,
such as: VPLEX
(default)
PuTTY5
Figure 27
PuTTY settings for logging in over the customer network
28. The output from some commands you will type is too long to read in a
standard-size PuTTY session window:
One solution is to extend the scrolling capability. To do this, select Window in
the Category list, and set Lines of scrollback (shown in Figure 28) to 20000.
40
Setting up VPLEX
Set to 20000
scrollback
Figure 28
Another solution to long displays is to save the session output to a log file.
Over the course of setting up a dual-engine or quad-engine cluster, the log file
can grow quite large. If you want to create a log file anyway:
a. Select Logging in the PuTTY Configuration Category list.
b. Under Session logging, select All session output.
c. Type a name in the Log file name field (shown in Figure 29).
All session output

File name
putty_log
Figure 29
41
Setting up VPLEX
30. Click Open, and log in to the management server with username service and
password Mi@Dim7T.
Task 2: Launch the

VPLEX EZ-Setup
Wizard
The EZ-Setup Wizard performs several tasks to set up a VPLEX implementation,

based on a series of prompts for user-entered information. Refer to the EMC VPLEX
Pre-installation Configuration Worksheet as you respond to the prompts.
From the VPlexcli prompt, type the following command, and follow the steps in the
automated interview and configuration procedure:
configuration system-setup
When you see the message Configuration Complete, proceed to Task 3: Verify the
product version.
Task 3: Verify the

product version
From the VPlexcli prompt, type the following command:

version -a
In the output, confirm that the Product Version matches the required version in the
VPLEX release notes.
Task 4: Verify the

VPLEX directors

ll /engines/**/directors
Verify that the output lists all directors in the cluster, and that all directors show the
following:
Commissioned status: true
Operational status: ok
Communication status: ok
Output example in a dual-engine cluster:
42
/engines/engine-1-1/directors:
Name
Director ID
------------- ----------------------------- ----------------director-1-1-A 0x000000003ca00183
director-1-1-B 0x000000003cb00183
Cluster
ID
------1
1
Commissioned
----------------------true
true
Operational
Status
----------ok
ok
Communication
Status
-----------ok
ok
Name
Director ID
------------- ----------------------------- ----------------director-1-2-A 0x000000003ca00165
director-1-2-B 0x000000003cb00165
Cluster
ID
------1
1
Commissioned
----------------------true
true
Operational
Status
----------ok
ok
Communication
Status
-----------ok
ok
Setting up VPLEX
Task 5: Open a
second PuTTY
session
Some setup tasks require executing commands from the VPlexcli prompt, and others
require excuting commands from the Linux shell prompt. You will find it easier to
leave two PuTTY sessions open on the management server, and use the applicable
session for each task.
For ease of identification, tasks that you perform in one of these sessions include one
of the following icons:
.
To open a new Linux shell session, leave the VPlexcli session open, and follow these
steps:
1. Launch PuTTY.exe.
2. Configure PuTTY as shown in Figure 27 on page 40, and then click Save.
password Mi@Dim7T.
Task 6: Verify the

director count
1.
Confirm that the file /etc/vplex/managed-systems/local-system/

manufacturing_manifest.properties exists on the management server.
2. Use vi or a similar editor to open the file, and edit the file if necessary to ensure
that it contains the following contents (with no spaces or newlines):
director_count=<n>
where <n> is the number of directors in the cluster.

3. Save and close the file.
Task 7: Verify the

Fibre Channel
switches if present
Note: If you are configuring a single-engine cluster, skip this task.
In a dual-engine or quad-engine cluster, you should ping the Fibre

Channel COM switches to verify that the IP addresses were set correctly:
1. Ping switch A:
ping <FC_switch_A_address>
where <FC_switch_A_address> is:

128.221.252.34 in Cluster 1
128.221.252.66 in Cluster 2
2. Ping switch B:
ping <FC_switch_B_address>
where <FC_switch_B_address> is:

128.221.253.34 in Cluster 1
128.221.253.66 in Cluster 2
Task 8: Expose
back-end storage
1.
From the VPlexcli prompt, type the following command to list all
director port WWNs (identified in the command output as addresses):
ll /engines/**/ports -p
43
Setting up VPLEX
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 spacebar.
To exit paging mode while you are viewing paged output, type q and press Enter.
(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 port WWNs of the VPLEX back-end ports, following the
recommendations in the Implementation and Planning Best Practices for EMC
VPLEX Technical Notes, which are available on Powerlink.
Task 9: Verify
storage volume
availability
1.
From the VPlexcli prompt, type the following commands to

rediscover the back-end storage:
cd/clusters/cluster-1/storage-elements/storage-arrays
array re-discover <array_name>
2. Type the following command to verify availability of the provisioned storage:

storage-volume summary
Output example:
Storage-VolumeSummary
-----------Health
Task 10: Create a

meta-volume
1.
Vendor
(no tier)
----------------out-of-date
storage-volumes
unhealthy
EMC
0
452
0
452
Use
unclaimed
452
Capacity
total
271G
From the VPlexcli prompt, type the following command to list

available storage volumes:
ll /clusters/cluster-1/storage-elements/storage-volumes -p
Output example (partial):

/clusters/cluster-1/storage-elements/storage-volumes:
Name
VPD83 ID
Capacity Use
Vendor IO
Type
--------------- --------------------------------------- ------- ----- ------ Status-------Clar0068_LUN71 VPD83T3:6006016049e02100281ebe77852cdf11 78G meta-data DGC alive
traditional
Clar0068_LUN74 VPD83T3:6006016049e02100291ebe77852cdf11 78G meta-data DGC alive
traditional
Clar0068_LUN75 VPD83T3:6006016049e02100c064c78a852cdf11 10G unclaimed DGC alive
normal
normal
2. From the ll output, identify the two back-end storage volumes (78 GB minimum)
to be used for the meta-volume and a mirror of the meta-volume.
Note: EMC recommends that the meta-volume and mirror be on separate arrays.
44
Setting up VPLEX
3.
Type the following command to create the meta-volume and a

mirror:
Note: You can copy a storage volume name from the ll 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>
where:
<meta-volume_name> is a name you are assigning to the meta-volume.
<storage-volume_1_name> is the VPD (Virtual Private Database) 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>
4.
Type the following command to display the meta-volume status:

ll /clusters/cluster-1/system-volumes/<meta-volume_name>
In the output, verify that the attribute active shows a value of true.
5.
Type the following command to display the cluster status:

cluster status
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.
Output example:
Cluster cluster-1
operational-status:
ok
transitioning-indications:
transitioning-progress:
health-state:
ok
health-indications:
Task 11: Determine

the TLA
From the VPlexcli prompt, type the following command to list the
attributes of engine 1, and make a note of the top-level-assembly in the output. This
is the TLA (which is the same for each engine in a cluster) that you will need to
specify in a later task:
ll /engines/engine-1-1
45
Setting up VPLEX
Task 12: Configure

Call Home
To configure the Call Home parameters:

1.
From the shell prompt, type the following command from the
directory /opt/emc/connectemc:
Note: The -d and -i arguments are optional.
./connectemcConfig -n <notification_type> -e <server_address>
-s <sender_email_address> -r <recipient_email_address> [-d
<connection_description>] [-i <attach_call_home_data>]
where:
<notification type> is one of the following types:
Type
Use
Primary
Failover
For connections to the EMC Support Center
For notifications to the customer
onSuccess
onFailure
onSuccess/onFailure
onAllFailure
EMC recommends that you configure the following notifications, in the order
listed:
Primary notification
At least one Failover notification (for high availability)
Any necessary customer notifications
<server_address> is the address or hostname of the email server.
If ESRS is being used for the primary notifcation, enter the ESRS gateway
server IP address.
If ESRS is being used for a secondary notifcation, enter a local SMTP IP
address.
If ESRS is not being used, Call Home uses the customer email server.
Note: EMC personnel can find ESRS documentation on the GTS website, in the
Application Download area, under EMC Secure Remote Support Gateway >
Implementation > Install Procedure.
<sender_email_address> should be VPlex_<TLA>@EMC.com (where <TLA> is

the value you determined in Task 11).
<recipient_email_address> is a valid customer site email address.
If you are configuring a Primary or Failover notification type for sending
notifications to EMC, use emailalert@EMC.com for <recipient_email_address>.
Note: All email attachments to Primary and Failover connections are encrypted.
<connection_description> is a description that can be used to identify the

purpose of the connection.
46
Setting up VPLEX
<attach_call_home_data> is valid only if <notification type> is one of the values

used for customer notification, and allows attaching non-encrypted Call
Home XML data to the email. Valid values are Yes or No. (Note that the value
is case-sensitive.)
Command example:
./connectemcConfig -n Primary -e 10.254.3.30 -s
VPlex_FCNBD093014459@EMC.com -r emailalert@EMC.com
Note: If you need to modify or remove a configuration entry, edit /opt/emc/connectemc/
ConnectEMC_config.xml. (Each entry in the file starts with the line <ConnectConfig
Type="<type>"> and ends with the line </ConnectConfig>.)
2.
After you have configured all notifcations, type the following

commands to restart ConnectEMC and verify that it shows a status of running:
sudo /etc/init.d/VPlexConnectemcd restart
sudo /etc/init.d/VPlexConnectemcd status
Output example:
Checking EMC VPlex connectemc status
3.
Running
Type the following commands to restart the VPLEX Management

Console and verify the status:
sudo /etc/init.d/VPlexElementManager restart
Note: This exits the VPlexcli session and leaves you with a second Linux shell session.
Note: In the current VPLEX release, the Management Console is called Element Manager
in some commands and output.
Output example:
Checking VPlex Element Manager status
4.
Running
From either shell prompt, type the following commands to restart

the emaAdaptor process and verify the status:
sudo /etc/init.d/VPlexEmaAdaptor restart
sudo /etc/init.d/VPlexEmaAdaptor status
Output example:
Checking VPlex EmaAdaptor status
5.
Running
From either Linux shell prompt, type the following command to

connect to the VPlexcli:
47
Setting up VPLEX
6.
From the VPlexcli prompt, type the following commands to enable

Call Home and confirm that it is enabled:
cd /notifications/call-home
set enabled true
ls
Output from ls:

Name
------enabled
Value
----true
7.
Type the following commands to test the configuration:

test
The output should be as follows:

call-home test was successful.
8. If Call Home was set up to notify a customer, the email should arrive at the
customers email address. If Call Home was set up to notify EMC, the email
should arrive at the EMC Support Center.
Task 13: Configure

SYR
The VPlexcli includes a set of commands (described in the EMC VPLEX CLI Guide) to
collect system configuration for the EMC System Reporting database (SYR) .
To configure a weekly SYR job, type the commands in the following
steps:
Note: If you are configuring the second cluster in a Metro-Plex, set the same schedule that is set
on the first cluster.
1. Set the schedule:

scheduleSYR add -d <day> -t <hours> -m <minutes>
where:
<day> is 0 for Sunday, 1 for Monday, and so on, through 6 for Saturday.
<hours> is 0 (midnight) 23 (11:00 PM), based on a 24-hour clock.
<minutes> is 0 59.
2. Confirm the schedule:
scheduleSYR list
Output example:
SYR data collection job is currently scheduled at:
Day of Week: 0 (Sunday=0, Monday=1,...Saturday=6)
Hours: 3
Minutes: 0
3. Verify that SYR is working correctly:

syrcollect
48
Setting up VPLEX
This collects system configuration data for SYR, produces a file named
<V-Plex_TLA>_Config_<time_stamp>.zip, and sends the file to the address
specified in the Call Home setup. Ensure that the SYR team verifies this file.
Task 14: Verify

back-end
connectivity
1.
To validate back-end connectivity, type the following command:

connectivity validate-be
As the following output example shows, all storage volumes must have dual
paths, and must be visible from all VPLEX directors:
Summary
Cluster cluster-1
This cluster has 0 storage-volumes which are dead or unreachable
This cluster has 0 storage-volumes which do not have dual paths
This cluster has 0 storage-volumes which are not visible from all
directors
If all storage volumes do not have dual paths, the output might be similar to the
following:
Storage volumes that are dead or unreachable:
Cluster
--------cluster-1
Dead or Unreachable Storage Volumes

---------------------------------------VPD83T3:60000970000192601426533032463334
Storage volumes that are not visible at all directors:

Cluster
--------cluster-1
Director
-------------director-1-1-B
Storage Volumes Director Cannot See

---------------------------------------VPD83T3:60000970000192601426533032463334
Summary
Cluster cluster-1
directors
2.
For each director in the cluster, type the following command, and
verify that the output shows all expected connections:
connectivity director <director_name>
where <director_name> is a predefined value: director-<Cluster_IP_Seed><Enclosure_ID>-A or -B (for example: director-1-1-A).

Note: The Cluster IP Seed matches the Cluster ID that you specified in the setup wizard,
and the Enclosure ID is the engine number, 14, numbered from the bottom up.

Volume
Node WWN
VPD83T3:6006016049e0210097fe419323d6de11 0x500601663ce00f51
0x500601673ce00f51
0x5006016e3ce00f51
0x5006016f3ce00f51
VPD83T3:6006016055b72200a0ec26a913ebde11 0x500601603b20119c
0x500601613b20119c
0x5006016a3b20119c
0x5006016b3b20119c
Port WWN
0x0009000000000000
0x0009000000000000
0x0009000000000000
0x0009000000000000
0x0093000000000000
0x0093000000000000
0x0093000000000000
0x0093000000000000
Port
A2-FC00
A3-FC00
A3-FC00
A2-FC00
A2-FC00
A3-FC00
A3-FC00
A2-FC00
49
Setting up VPLEX
Directors discovered by Dir1-1-A, UUID 0x000000003ca0014d:

Director UUID
Protocol Address
Ports
------------------ -------- ------------------ ------0x000000003cb0014d COMSCSI 0x5000144250014d41 A4-FC01
COMSCSI 0x5000144250014d40 A4-FC00
Task 15: Enable the

front-end ports
1.
Type the following command to enable all front-end ports in the

cluster:
set /engines/*/directors/*/hardware/ports/*[0-1]-FC*::enabled true
Note that the asterisks are wildcards that replace the following entries:
First wildcard All engines in the cluster.
Second wildcard All directors in the cluster.
Third wildcard All A-side ports and all B-side ports. The [0-1] that follows
this wildcard limits the selections to all port numbers that start with A0, A1,
B0, or B1.
Fourth wildcard All ports whose numbers start with A0-FC, A1-FC, B0-FC,
or B1-FC.
2.
Type the following command to verify that all I/O ports are up:

Note: Any front-end port that does not have a host attached shows a Port Status of no-link.
Name
------B0-FC00
B0-FC01
B0-FC02
B0-FC03
B1-FC00
B1-FC01
B1-FC02
B1-FC03
B2-FC00
B2-FC01
B2-FC02
B2-FC03
Address
-----------------0x5000144250014d00
0x5000144250014d01
0x5000144250014d02
0x5000144250014d03
0x5000144250014d10
0x5000144250014d11
0x5000144250014d12
0x5000144250014d13
0x5000144250014d20
0x5000144250014d21
0x5000144250014d22
0x5000144250014d23
Role
--------front-end
front-end
front-end
front-end
front-end
front-end
front-end
front-end
back-end
back-end
back-end
back-end
Port Status
----------no-link
no-link
no-link
no-link
no-link
no-link
no-link
no-link
up
up
up
up
If you are configuring a VPLEX Local implementation, verify that all wan-com
ports (A4-FC02, A4-FC03, B4-FC02, and B4-FC03) in each engine have a Port
Status of down. If one or more wan-com ports have any other status, type the
following command:
set /**/*4-FC0[2-3]::enabled false
Task 16: Set up ESRS

if necessary
50
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.
Setting up VPLEX
Task 17: Ensure that

the I/O ports are
zoned
Task 18: Expose

storage to hosts
Zone the front-end and back-end I/O ports as recommended in the following:
Reference: VPLEX requirements on page 21 of this guide
Implementation and Planning Best Practices for EMC VPLEX Technical Notes,
available on Powerlink
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:
If you are using the

GUI
To use the GUI, proceed to If you are using the GUI.
To use the VPlexcli, proceed to If you are using the VPlexcli on page 52.
To use the GUI:

1. Open a browser and type the following:
https://<mgmt_server_address>
where <mgmt_server_address> is the IP address of the management server's public

IP port.
2. Log in with username service and password Mi@Dim7T.
3. To begin provisioning and exporting storage, click Provision Storage on the main
screen of the VPLEX Management Console GUI (shown in Figure 30).
Figure 30
VPLEX Management Console: Provision Storage button

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 Help on the task bar.
51
Setting up VPLEX

VPlexcli
Note: The VPLEX CLI guide contains details on using VPlexcli commands.
To claim and name a storage volume:

1.
Type the following commands to display a list of available storage

volumes:
cd /clusters/cluster-1/storage-elements/storage-volumes
ls
2. Type the following command to claim and name a storage volume:

storage-volume claim -n <storage_volume_name> -d
<storage_volume_ID>
where:
<storage_volume_name> is an unique name you are assigning to the volume.
<storage_volume_ID> is the ID (for example, Symm2206_2ADF, or
clar2065_LUN537) in the output from step 1.
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. Type the following command to create the extent:

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. Type the following command to verify that the extent was created:
ls /clusters/cluster-1/storage-elements/extents

/clusters/cluster-1/storage-elements/extents:
extent_Symm1707_1000_1 extent_Symm1707_1001_1
extent_Symm1707_100C_1 extent_Symm1707_100D_1
extent_Symm1707_1002_1
extent_Symm1707_100A_1
extent_Symm1707_100E_1
extent_Symm1707_100B_1
extent_Symm1707_100F_1
5. Type the following commands to create the RAID device:

cd /clusters/cluster-1/devices
52
Setting up VPLEX
local-device create <device_name> -g[raid-0|raid-1|raid-c] -e

<extent>,<extent>
6. Type the following commands to create the virtual volume:

cd /clusters/cluster-1/virtual-volumes
create -r <device_name>
7. Type the following command to list the initiator ports:

ll /clusters/cluster-1/exports/initiator-ports

Name
-----------habc4101_pt0
port-wwn
-----------------0x10000000c866fff2
node-wwn
-----------------0x20000000c866fff2
type
------default
habc4101_pt1
0x10000000c866fff3
0x20000000c866fff3
default
habc4102_pt0
0x10000000c866ffec
0x20000000c866ffec
default
habc4102_pt1
0x10000000c866ffed
0x20000000c866ffed
default
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
8. Type the following commands to register each initiator port:

cd /clusters/cluster-1/exports/initiator-ports
export initiator-port register -i <initiator_port> -p
<portWWN|nodeWWN>
9. Type the following commands to create and export the storage view:
cd /clusters/cluster-1/exports
storage-view create -c /clusters/cluster-1/ -n <storage_view_name>
-p <VPLEX_port>,<VPLEX_port>
10. Type the following commands to add each initiator port to the storage view:
storage-view addinitiatorport -v <storage_view_name> -i
<initiator_port>,<initiator_port>
11. Type the following commands to add the virtual volume(s) to the storage view:
storage-view addvirtualvolume -v <storage_view_name> -o
<virtual-volume_name>
Note that for any virtual volumes you add after the first one, you must add -f to
the end of the command. For example:
storage-view addvirtualvolume -f -v <storage_view_name> -i
<virtual-volume_name>,<virtual-volume_name>
53
Setting up VPLEX
Note: Including -f forces the virtual volumes to be added to the view even if the specified
LUNs are in use, the view is live, the virtual volumes are already assigned to another view,
or there are problems determining the view's state.
12. Type the following commands to verify the status of the storage view:
cd /clusters/cluster-1/exports/storage-views
export storage-view summary
Output example:
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: Perform a

rescan
54
After provisioning and exporting storage, perform a rescan from the host to verify
that the exported virtual volume is visible.
Setting up VPLEX
Setting up a VPLEX Metro implementation

Note: You must set up both VPLEX Metro clusters as described in this section. You cannot set
each cluster up individually and then join them later.
Task 1: Set the

management
servers public IP
address
Before you can log in to a VPLEX management server over the customer network,
you must set the address on the management servers public Ethernet port:
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.
Note: The tasks in this document use PuTTY for logging in to the management server.
However, you can use any similar Telnet/SSH client.
1. Remove the red service cable that hangs inside the cabinet of the first VPLEX
cluster you are setting up, and use the cable to connect your laptop to the clusters
management server as shown in Figure 31.
Laptop
Service port
Mgmt-B port
Figure 31
Mgmt-A port
zep-009b
select Properties.
IP address:
128.221.252.3
Subnet mask:
255.255.255.224
55
Setting up VPLEX
ipconfig
Output example:
Ethernet adapter Local Area Connection:
Connection-specific
IP Address. . . . .
Subnet Mask . . . .
Default Gateway . .
DNS
. .
. .
. .
Suffix
. . . .
. . . .
. . . .
.
.
.
.
:
:
:
:
eng.emc.com
128.221.252.3
255.255.255.224
128.221.252.2
ping 128.221.252.2

Type:
128.221.252.2
(default)
Type session name:
VPLEX_service
(default)
PuTTY
Figure 32
56
Setting up VPLEX
SSH protocol
version
putty_ssh
Figure 33
If you are going to remain connected directly for the entire setup procedure on
this management server, follow these steps:
Note: You will perform the same steps on the second management server later.
a. Select Window in the Category list, and set Lines of scrollback (shown in
Figure 34 on page 58) to 20000. (This allows you to read long output in a
standard-size PuTTY session window.)
57
Setting up VPLEX
Set to 20000
scrollback
Figure 34
b. If you want to save the session output to a log file:

i.
Select Logging in the PuTTY Configuration Category list.

iii. Type a name in the Log file name field (shown in Figure 35 on
page 59).
58
Setting up VPLEX
All session output

File name
putty_log
Figure 35
16. 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.
Note the following:
17. From the Linux shell prompt, type the following command, and verify that the
18. Type the following command to change the hostname:

where <hostname> is a name for the management server, such as Cluster1. This
name replaces the default name (service) in the shell prompt the next time you
open a PuTTY session to the management server
director 1-A:
ping 128.221.252.35 -c 5
59
Setting up VPLEX
Quad-engine
cluster
Engine 4:
Director 4-B
Director 4-A
128.221.252.42
128.221.252.41
Engine 3:
Director 3-B
Director 3-A
128.221.252.40
128.221.252.39
Engine 2:
Director 2-B
Director 2-A
128.221.252.38
128.221.252.37
Engine 1:
Director 1-B
Director 1-A
128.221.252.36
128.221.252.35
Dual-engine
cluster
Single-engine
cluster
Zep-056
Figure 36
Director A-side addresses in cluster 1


Ethernet port:

Task 2: Launch the EZ-Setup wizard on page 64.
shell prompt:
exit
25. Disconnect the red service cable from the management server and hang it back in
the cabinet.
26. If the clusters are located at different sites, go to step 35.
If the clusters are at the same location, use the red service cable in the second
clusters cabinet to connect to the service port on the management server, and
then proceed to step 27.
27. Launch PuTTY, and load the VPLEX_Service session you saved earlier in this
task.
28. Click Open, and log in with username service and password Mi@Dim7T.
60
Setting up VPLEX
29. From the Linux shell prompt, type the following command, and verify that the
30. Type the following command:

where <hostname> is a name for the management server, such as Cluster2.

31. Type the following command to connect to the VPlexcli, and log in with username
service and password Mi@Dim7T:
32. From the VPlexcli prompt, type the following command to configure the IP
address of the management servers public Ethernet port:
33. Type the following command at the VPlexcli prompt, and again at the Linux shell
prompt:
exit
the cabinet.
If you are connecting your laptop to the network, set it to an IP address on
the network.
If you are connecting 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 or other Telnet/SSH client is installed on the device,
and install it if necessary.
61
Setting up VPLEX

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 37
PuTTY settings for logging in to cluster 1 over the customer network
37. Select Window in the Category list, and set Lines of scrollback (shown in
Figure 38) to 20000. (This allows you to read long output in a standard-size
PuTTY session window.)
Set to 20000
scrollback
Figure 38
38. If you want to save the session output to a log file:

62
Setting up VPLEX
Note: Over the course of setting up a dual-engine or quad-engine cluster, the log file can
grow quite large.
Note: The log file saves data from the current PuTTY session. Any time you open a new
session, you must repeat this step if you want to log the output for that session.
All session output

File name
putty_log
Figure 39
40. Configure a new PuTTY session as shown in Figure 40.
in the second cluster you
are configuring
(default)
VPLEX service
VPLEX Cluster 1

VPLEX Cluster 2
(default)
PuTTY3
Figure 40
63
Setting up VPLEX
41. Repeat steps 37 through 39.

42. Select the VPLEX Cluster 1 session from the list of saved sessions, and click Load.
password Mi@Dim7T.
Task 2: Launch the

EZ-Setup wizard
The setup wizard performs several tasks to set up a VPLEX implementation, based on
a series of prompts for user-entered information. Refer to the EMC VPLEX
Pre-installation Configuration Worksheet as you respond to the prompts.
product version.
Task 3: Verify the

product version

version -a
Task 4: Verify the

VPLEX directors

following:
64
Name
Director ID
------------- ----------------------------- ----------------director-1-1-A 0x000000003ca00183
director-1-1-B 0x000000003cb00183
Cluster
ID
------1
1
Commissioned
----------------------true
true
Operational
Status
----------ok
ok
Communication
Status
-----------ok
ok
Name
Director ID
------------- ----------------------------- ----------------director-1-2-A 0x000000003ca00165
director-1-2-B 0x000000003cb00165
Cluster
ID
------1
1
Commissioned
----------------------true
true
Operational
Status
----------ok
ok
Communication
Status
-----------ok
ok
Setting up VPLEX
Task 5: Open a
second PuTTY
session
To open a new Linux shell session, leave the VPlexcli session open, and follow these
steps:
1. Launch PuTTY.exe.
2. Configure PuTTY as described in step 37 on page 62 through step 39 on page 63.
password Mi@Dim7T.
For ease of identification, many of the remaining tasks in this section include one of
the following icons to identify the associated session:
.
Task 6: Verify the

director count
1.

director_count=<n>

Task 7: Verify the

Fibre Channel
switches if present

1. Ping switch A:
ping 128.221.252.34
2. Ping switch B:
ping 128.221.253.34
Task 8: Expose
back-end storage
1.
65
Setting up VPLEX
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 spacebar.
To exit paging mode while you are viewing paged output, type q and press Enter.
(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.
Task 9: Verify
storage volume
availability
1.

cd/clusters/cluster-1/storage-elements/storage-arrays/EMC-*

Output example:
-----------Health
Task 10: Create a

meta-volume
1.
Vendor
(no tier)
----------------out-of-date
storage-volumes
unhealthy
EMC
0
452
0
452
Use
unclaimed
452
Capacity
total
271G


Name
VPD83 ID
Capacity Use
Vendor IO
Type
traditional
traditional
normal
normal
From the ll output, identify the two back-end storage volumes (78 GB minimum)
66
Setting up VPLEX
2.

mirror:
where:
meta-volume.
3.

4.

cluster status
Output example:
Cluster cluster-1
operational-status:
ok
health-state:
ok
health-indications:
Task 11: Determine

the TLA
67
Setting up VPLEX
Task 12: Configure

Call Home

1.
where:
Type
Use
Primary
Failover
onSuccess
onFailure
onSuccess/onFailure
onAllFailure
listed:
server IP address.
address.


68
Setting up VPLEX

is case-sensitive.)
Command example:
2.

Output example:
3.
Running

Note: This exits the VPlexcli session and leaves you with two Linux shell sessions.
Output example:
4.
Running

Output example:
5.
Running

69
Setting up VPLEX
6.

set enabled true
ls
Output from ls:

Name
------enabled
Value
----true
7.

test

Task 13: Configure

SYR
steps:
where:
<minutes> is 0 59.
scheduleSYR list
Output example:
Hours: 3
Minutes: 0

syrcollect
70
Setting up VPLEX
Task 14: Verify

back-end
connectivity
1.

Summary
Cluster cluster-1
directors
following:
Cluster
--------cluster-1

---------------------------------------VPD83T3:60000970000192601426533032463334

Cluster
--------cluster-1
Director
-------------director-1-1-B

---------------------------------------VPD83T3:60000970000192601426533032463334
Summary
Cluster cluster-1
directors
2.
where <director_name> is a predefined value: director-1- <Enclosure_ID>-A or -B

(for example: director-1-1-A).
Note: The Cluster IP Seed matches the Cluster ID you specified in the setup wizard, and
the Enclosure ID is the engine number, 14, numbered from the bottom up.

Volume
Node WWN
VPD83T3:6006016049e0210097fe419323d6de11 0x500601663ce00f51
0x500601673ce00f51
0x5006016e3ce00f51
0x5006016f3ce00f51
0x500601613b20119c
0x5006016a3b20119c
0x5006016b3b20119c
Port WWN
0x0009000000000000
0x0009000000000000
0x0009000000000000
0x0009000000000000
0x0093000000000000
0x0093000000000000
0x0093000000000000
0x0093000000000000
Port
A2-FC00
A3-FC00
A3-FC00
A2-FC00
A2-FC00
A3-FC00
A3-FC00
A2-FC00
71
Setting up VPLEX

Director UUID
Protocol Address
Ports
COMSCSI 0x5000144250014d40 A4-FC00
Task 15: Enable the

front-end ports
Type the following command to enable all front-end ports in the cluster:
B0, or B1.
or B1-FC.
Task 16: Connect to

cluster 2
1. Did you set the public IP address on both management servers in Task 1 on
page 55?
Note: As a reminder, the only scenario in which you would have done this is if both
clusters are at the same location and you connected to the cluster over the customer
network after you set the IP address on the management server.
If yes:
a. Type the following command at the VPlexcli prompt, and again at the
Linux shell prompt:
exit
b. Establish a PuTTY session to the management server in cluster 2, and log in

with username service and password Mi@Dim7T.
c. Type the following command to connect to the VPlexcli, and log in with
username service and password Mi@Dim7T:
d. Go to Task 17: Launch the EZ-Setup wizard on page 80.

If no, proceed to step 2.
Note: The procedure described here assumes that a different laptop is being used to set up
cluster 2 than the one that was used for cluster 1.
2. Remove the red service cable that hangs inside cluster 2s cabinet, and use the
cable to connect your laptop to the clusters management server as shown in
Figure 41.
72
Setting up VPLEX
Laptop
Service port
Mgmt-B port
Figure 41
Mgmt-A port
zep-009b
select Properties.
IP address:
128.221.252.3
Subnet mask:
255.255.255.224
ipconfig
ping 128.221.252.2

73
Setting up VPLEX
Type:
128.221.252.2
(default)
Type session name:
VPLEX_service
(default)
PuTTY
Figure 42
SSH protocol
version
putty_ssh
Figure 43
74
Setting up VPLEX
If you are going to remain connected directly for the entire setup procedure,
follow these steps:
a. Select Window in the Category list, and set Lines of scrollback (shown in
Set to 20000
scrollback
Figure 44
b. If you want to save the session output to a log file:

i.
Select Logging in the PuTTY Configuration Category list.

iii. Type a name in the Log file name field (shown in Figure 45).
75
Setting up VPLEX
All session output

File name
putty_log
Figure 45
17. 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.
Note the following:
18. From the Linux shell prompt, type the following command to verify that the
19. Type the following command to change the hostname:

where <hostname> is a name for the management server, such as Cluster2. This
name replaces the default name (service) in the shell prompt the next time you
open a PuTTY session to the management server
director 1-A:
ping 128.221.252.67 -c 5
76
Setting up VPLEX
Quad-engine
cluster
Engine 4:
Director 4-B
Director 4-A
128.221.252.74
128.221.252.73
Engine 3:
Director 3-B
Director 3-A
128.221.252.72
128.221.252.71
Engine 2:
Director 2-B
Director 2-A
128.221.252.70
128.221.252.69
Engine 1:
Director 1-B
Director 1-A
128.221.252.68
128.221.252.67
Dual-engine
cluster
Single-engine
cluster
Zep-056a
Figure 46
Director A-side addresses


Ethernet port:

Task 17: Launch the EZ-Setup wizard on page 80.
shell prompt:
exit
the cabinet.
If you are connecting your laptop to the network, set it to an IP address on the
network.
If you are connecting from a different device:
a. Restore your laptop to the settings it had before you began this procedure
(including re-enabling any network cards).
77
Setting up VPLEX
b. Verify that PuTTY or other Telnet/SSH client is installed on the device, and
install it if necessary.
in the second cluster you
are configuring
(default)
VPLEX service
VPLEX Cluster 1

VPLEX Cluster 2
(default)
PuTTY3
Figure 47
29. Select Window in the Category list, and set Lines of scrollback (shown in
Set to 20000
scrollback
Figure 48
78
Setting up VPLEX
30. If you want to save the session output to a log file:

Note: Over the course of setting up a dual-engine or quad-engine cluster, the log file can
grow quite large.
Note: The log file saves data from the current PuTTY session. Any time you open a new
session, you must repeat this step if you want to log the output for that session.
All session output

File name
putty_log
Figure 49
password Mi@Dim7T.
79
Setting up VPLEX
Task 17: Launch the

EZ-Setup wizard
The setup wizard performs several tasks to set up a VPLEX implementation, based on
a series of prompts for user-entered information. Refer to the EMC VPLEX
Pre-installation Configuration Worksheet as you respond to the prompts
product version.
Task 18: Verify the

product version
Type the following command from the VPlexcli prompt, to display the software
versions:
version -a
Task 19: Verify the

VPLEX directors

following:
80
Name
Director ID
------------- ----------------------------- ----------------director-2-1-A 0x000000003ca00183
director-2-1-B 0x000000003cb00183
Cluster
ID
------1
1
Commissioned
----------------------true
true
Operational
Status
----------ok
ok
Communication
Status
-----------ok
ok
Name
Director ID
------------- ----------------------------- ----------------director-2-2-A 0x000000003ca00165
director-2-2-B 0x000000003cb00165
Cluster
ID
------1
1
Commissioned
----------------------true
true
Operational
Status
----------ok
ok
Communication
Status
-----------ok
ok
Setting up VPLEX
Task 20: Open a

second PuTTY
session
To open a new Linux shell session, leave the VPlexcli session open, and follow step 28
on page 78 through step 32 on page 79.
For ease of identification, many of the remaining tasks include one of the following
icons:
.
Task 21: Verify the

director count
1.

director_count=<n>

Task 22: Verify the

Fibre Channel
switches if present

1. Ping switch A:
ping 128.221.252.66
2. Ping switch B:
ping 128.221.253.66
Task 23: Expose

back-end storage
1.
Task 24: Verify

storage volume
availability
1.

cd/clusters/cluster-2/storage-elements/storage-arrays/EMC-*

81
Setting up VPLEX
Output example:
-----------Health
Task 25: Create a

meta-volume
1.
Vendor
(no tier)
----------------out-of-date
storage-volumes
unhealthy
EMC
0
452
0
452
Use
unclaimed
452
Capacity
total
271G


Name
VPD83 ID
Capacity Use
Vendor IO
Type
traditional
traditional
normal
normal
From the ll output, identify the two back-end storage volumes (78 GB minimum)
2.

mirror:
where:
meta-volume.
3.

82
Setting up VPLEX
4.

cluster status
Output example:
Cluster cluster-2
operational-status:
ok
health-state:
ok
health-indications:
Task 26: Determine

the TLA
Task 27: Configure

Call Home

1.
where:
Type
Use
Primary
Failover
onSuccess
onFailure
onSuccess/onFailure
onAllFailure
listed:
83
Setting up VPLEX

server IP address.
address.


is case-sensitive.)
Command example:
2.

Output example:
3.
Running

Note: This exits the VPlexcli session and leaves you with a second Linux shell session.
84
Setting up VPLEX
Output example:
4.
Running

Output example:
5.
Running


6.

set enabled true
ls
Output from ls:

Name
------enabled
7.
Value
----true

test

Task 28: Configure

SYR
steps. Set the same schedule that is set on cluster 1.
85
Setting up VPLEX
where:
<minutes> is 0 59.
scheduleSYR list
Output example:
Hours: 3
Minutes: 0

syrcollect
Task 29: Verify

back-end
connectivity
1.

Summary
Cluster cluster-2
directors
following:
Cluster
--------- ---------------------------------------cluster-2 VPD83T3:60000970000192601426533032463334
Cluster
Director
--------- -------------- ---------------------------------------cluster-2 director-2-1-B VPD83T3:60000970000192601426533032463334
Summary
Cluster cluster-2
directors
86
Setting up VPLEX
2.
where <director_name> is a predefined value: director-2- <Enclosure_ID>-A or -B

(for example: director-2-1-A).
Note: The Cluster IP Seed matches the Cluster ID that you specified in the setup wizard,
and the Enclosure ID is the engine number, 14, numbered from the bottom up.

Volume
Node WWN
VPD83T3:6006016049e0210097fe419323d6de11 0x500601663ce00f51
0x500601673ce00f51
0x5006016e3ce00f51
0x5006016f3ce00f51
0x500601613b20119c
0x5006016a3b20119c
0x5006016b3b20119c
Port WWN
0x0009000000000000
0x0009000000000000
0x0009000000000000
0x0009000000000000
0x0093000000000000
0x0093000000000000
0x0093000000000000
0x0093000000000000
Port
A2-FC00
A3-FC00
A3-FC00
A2-FC00
A2-FC00
A3-FC00
A3-FC00
A2-FC00

Director UUID
Protocol Address
Ports
COMSCSI 0x5000144250014d40 A4-FC00
Task 30: Enable the

front-end ports
Type the following command to enable all front-end ports in the cluster:
B0, or B1.
or B1-FC.
Task 31: Enable the

WAN ports
1.
Type the following command from the VPlexcli prompt, to enable

all WAN COM ports in the cluster:
set /**/*4-FC0[2-3]::enabled true
2.
Type the following command to display all director ports in the

cluster:
ll /engines/engine-2-*/**/ports
In the output, verify that all ports numbered A4-FC02, A4-FC03, B4-FC02, or
B4-FC03 have a port status of up.
87
Setting up VPLEX
Task 32: Set up 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.
Task 33: Open a

VPlexcli session on
cluster 1
Several of the remaining tasks require moving back and forth between VPlexcli
sessions to both clusters. You will find it easier to leave two sessions open.
Some tasks include one of the following icons to identify the associated PuTTY
session:
Management server 1:
Management server 2:
To open a second session:

Note: It is assumed that you have an open Linux shell session and a VPlexcli session to
management server 2 at this point.
1. Type the following command at the Linux shell prompt:

exit

3. If you already have a VPLEX Cluster 1 session saved, load it.
If no Cluster 1 session exists, configure the PuTTY Configuration window as
shown in Figure 40 on page 63.
4. Click Open to establish a session to management server 1, and log in with
username service and password Mi@Dim7T.
5. From the Linux shell prompt, type the following command to connect to the
VPlexcli:
Task 34: Verify the

date and time on
both clusters
1.
From the VPlexcli prompt on management server 1, type the

following command to display the date and UTC time:
date
Output example:
Tue Feb 16 19:07:58 UTC 2010
2.
3.
Repeat step 1 on management server 2.

or
If the UTC are not synchronized between the
management servers (taking into account the few seconds it took between steps 1
and 2), type the following command on the management server you want to
change:
sudo /bin/date -s "<date_and_time>
88
Setting up VPLEX
where <date_and_time> is in the format shown in the following command

example:
sudo /bin/date -s "29 Jun 2010 17:19:00
Task 35: Complete

the setup on
cluster 1

following command:
configuration system-setup -m
When the automated configuration is complete, the VPlexcli prompt appears.
Task 36: Enable the

WAN ports on
cluster 1
1.

following command to enable all WAN COM ports in the cluster:
set /**/*4-FC0[2-3]::enabled true
2. Type the following command to display all director ports in the cluster, and verify
that all ports numbered A4-FC02, A4-FC03, B4-FC02, or B4-FC03 have a port
status of up:
ll /engines/engine-1-*/**/ports
Task 37: Zone the

WAN ports
Task 38: Connect

cluster 1 to the
directors in cluster 2
Zone the WAN COM ports as recommended in the following:
Reference: VPLEX requirements on page 21 of this guide
Implementation and Planning Best Practices for EMC VPLEX Technical Notes,
available on Powerlink
1.

following command:
configuration connect-remote-directors
When prompted, type the number of engines in cluster 2.

2. Type the following command to verify that cluster 1 is connected to all of the
directors in cluster 2:
ls /engines/engine-2-*/directors
Output example for a dual-engine cluster:

director-2-1-A
director-2-1-B
director-2-2-A
director-2-2-B
Task 39: Connect

cluster 2 to the
directors in cluster 1
1.

following command:
configuration connect-remote-directors
When prompted, type the number of engines in cluster 1.

89
Setting up VPLEX
2. Type the following command to verify that cluster 2 is connected to all of the
directors in cluster 1:
ls /engines/engine-1-*/directors
Output example for a dual-engine cluster:

director-1-1-A
director-1-1-B
director-1-2-A
director-1-2-B
Task 40: Join the

clusters
1.
Type the following commands to assign an Island ID to the

clusters:
cd /clusters
cluster add cluster-1 cluster-2
2.
Type the following command to display a cluster summary:

cluster summary
In the output, verify that both clusters have the same Island ID and an operational
status of ok.
Output example:
Clusters:
Name
Cluster ID Connected Expelled
Operational Status
Health
------------------ --------- ----------------------------------------------------------------------------------------------------------cluster-1
1
true
false
ok
ok
cluster-2
2
true
false
ok
ok
Islands:
Island ID
--------1
Task 41: Create

logging volumes
Clusters
-------------------cluster-1, cluster-2
You must create a logging volume on each VPLEX Metro cluster. The 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 320 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.
CAUTION
If a logging volume does not exist, every link failure could cause a full
resynchronization of every distributed device in the system.
90
Setting up VPLEX
To create the logging volumes, you first must claim the storage volumes that will be
used, and create extents from those volumes:
1.
VPlexcli-2
following commands to list the storage volumes:
cd /clusters/cluster-<Cluster_ID>/storage-elements/storage-volumes
ll
2.
VPlexcli-2
Type the following command to claim the storage volume(s) that
you will use for the logging volume:
<storage_volume_ID>
where:
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 name(s) of the extent(s) that make(s) 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.
Example for cluster 2:

logging-volume create -n cluster_2_log_vol -g raid-0 -e ext1 , ext2
-d 32
91
Setting up VPLEX
Task 42: Verify that

the clusters are fully
connected
5.
From the VPlexcli prompt on management server 1, repeat steps 1

through 4 for cluster 1.
1.

following command, and verify that all directors in cluster 2 appear in the output:
ll /engines/engine-2-*/**/directors

Name
Director ID
------------- ----------------------------- ----------------director-2-1-A 0x000000003ca00183
director-2-1-B 0x000000003cb00183
Cluster
ID
------2
2
Commissioned
----------------------true
true
Operational
Status
----------ok
ok
Communication
Status
-----------ok
ok
Name
Director ID
------------- ----------------------------- ----------------director-2-2-A 0x000000003ca00165
director-2-2-B 0x000000003cb00165
Cluster
ID
------2
2
Commissioned
----------------------true
true
Operational
Status
----------ok
ok
Communication
Status
-----------ok
ok
2.

following command, and verify that all directors in cluster 1 appear in the output:
ll /engines/engine-1-*/**/directors
Task 43: Verify the

cluster status
1.

following command to display the cluster status:
cluster status
In the output, confirm that operational-status is ok and that there are no health
indications.
2.
Type the following command to display a cluster summary:

cluster summary
In the output, verify that both clusters have the same Island ID and an operational
status of ok.
Task 44: Verify

back-end
connectivity on
cluster 2
From the VPlexcli prompt on management server 2, type the following

command:
In the output, confirm that all storage volumes in the cluster have dual paths, and are
visible from all VPLEX directors.
Output example:
Summary
Cluster cluster-2
directors
92
Setting up VPLEX
Task 45: Verify

back-end
connectivity on
cluster 1

following command:
In the output, confirm that all storage volumes in the cluster have dual paths, and are
visible from all VPLEX directors.
Task 46: 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:

GUI
To use the GUI, proceed to If you are using the GUI.
To use the VPlexcli, proceed to If you are using the VPlexcli.
To use the GUI:

1. Open a browser and type the following:
https://<mgmt_server_address>
where <mgmt_server_address> is the IP address of the management server's public

IP port.
2. Log in with username service and password Mi@Dim7T.
Note: If the security message screen was enabled during system setup, a security message
appears. Read the message, and then click Continue.
3. To begin provisioning and exporting storage, click Provision Storage on the main
screen of the VPLEX Management Console GUI (shown in Figure 50).
Figure 50
VPLEX Management Console: Provision Storage button

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 Help on the task bar.
93
Setting up VPLEX

VPlexcli
Note: The VPLEX CLI guide contains details on using VPlexcli commands.
To claim and name a storage volume:

1. Type the following commands to display a list of available storage volumes:
cd /clusters/cluster-<Cluster_ID>/storage-elements/storage-volumes
ls
2. Type the following command to claim and name a storage volume:

<storage_volume_ID>
where:
VPLEX CLI Guide.
3. Type the following command to create the extent:

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 automatically named and claimed.
4. Type the following command to verify that the extent was created:
ls /clusters/cluster-<Cluster_ID>/storage-elements/extents

5. Type the following commands to create the RAID device:

cd /clusters/cluster-<Cluster_ID>/devices
local-device create <device_name> -g[raid-0|raid-1|raid-c] -e
<extent>,<extent>
94
Setting up VPLEX
6. Type the following commands to create the virtual volume:

cd /clusters/cluster-<Cluster_ID>/virtual-volumes
create -r <device_name>
7. Type the following command to list the initiator ports:

ll /clusters/cluster-<Cluster_ID>/exports/initiator-ports

8. Type the following commands to register each initiator port:

cd /clusters/cluster-<Cluster_ID>/exports/initiator-ports
export initiator-port register -i <initiator_port> -p
<portWWN|nodeWWN>
9. Type the following commands to create and export the storage view:
cd /clusters/cluster-<Cluster_ID>/exports
storage-view create -c /clusters/cluster-<Cluster_ID>/ -n
<storage_view_name> -p <VPLEX_port>,<VPLEX_port>
10. Type the following commands to add each initiator port to the storage view:
storage-view addinitiatorport -v <storage_view_name> -i
<initiator_port>,<initiator_port>
11. Type the following commands to add the virtual volume(s) to the storage view:
storage-view addvirtualvolume -v <storage_view_name> -o
<virtual-volume_name>
Note that for any virtual volumes you add after the first one, you must add -f to
the end of the command. For example:
storage-view addvirtualvolume -f -v <storage_view_name> -i
<virtual-volume_name>,<virtual-volume_name>
Note: Including -f forces the virtual volumes to be added to the view even if the specified
LUNs are in use, the view is live, the virtual volumes are already assigned to another view,
or there are problems determining the view's state.
95
Setting up VPLEX
12. Type the following commands to verify the status of the storage view:
cd /clusters/cluster-<Cluster_ID>/exports/storage-views
export storage-view summary
Output example:
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 47: Perform a

rescan
96
After provisioning and exporting storage, perform a rescan from the host to verify
that the exported virtual volume is visible.
A
Reference
This appendix contains miscellaneous information you will need during the
installation. The appendix also contains tables to record other information you might
need.
IP addresses and component IDs................................................................................ 98

Internal cabling ............................................................................................................ 100
Cabinet power connections........................................................................................ 111
Reference
97
Reference
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 51 on page 98 shows the IP addresses in a cluster with a Cluster IP Seed of 1,
and Figure 52 on page 99 shows the addresses for a Cluster IP Seed of 2.
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

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
Zep-028_1
Figure 51
98
Component IP addresses in cluster 1
Reference
Cluster IP Seed = 2
Enclosure IDs = engine numbers
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
Zep-028_2
Figure 52
Component IP addresses in cluster 2
IP addresses and component IDs
99
Reference
Internal cabling
The figures in this section show the various cabling inside a VPLEX cabinet. The
figures are included here for reference only, because the cables are installed before the
unit ships from EMC.
The figures include cable lengths and EMC part numbers, for use in verifying or
replacing a cable.
This section includes the following figures:
Cluster size
Cable type
Figure
Quad-engine
Ethernet
Figure 53 on page 101
Serial
Fibre Channel
AC power
Ethernet
Serial
Fibre Channel
AC power
Ethernet
Serial
Fibre Channel
AC power
Dual-engine
Single-engine
100
Reference
Quad-engine cluster
038-003-676, 71 in.
038-003-887, 48 in.
038-003-679, 20 in.
038-003-678, 20 in.
Engine 4
Engine 3
038-003-678, 20 in.
Management server
038-003-677, 37 in.
038-003-679, 20 in.
038-003-685, 37 in.
038-003-677, 37 in.
038-003-685, 37 in.
Engine 2
Engine 1
Zep-05_el
Figure 53
Ethernet cabling in a quad-engine cluster
Internal cabling
101
Reference
Engine 4
038-003-682
12 in.
038-003-682
12 in.
Engine 3
038-003-682
12 in.
038-003-682
12 in.
UPS B
UPS A
038-003-894
40 in.
038-003-894
40 in.
Engine 2
038-003-682
12 in.
038-003-682
12 in.
Engine1
038-003-682
12 in.
038-003-682
12 in.
Zep-05_sl
Figure 54
102
Serial cabling in a quad-engine cluster
Reference
Engine 4
Engine 3
038-003-738, 79 in.
(all 16 cables)
Engine 2
Engine 1
Zep-05_fl
Figure 55
Fibre Channel cabling in a quad-engine cluster

Note: All 16 Fibre Channel cables are light blue. However, the A side cables have blue labels
and the B side cables have orange labels.
Internal cabling
103
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
Zep-005_acl
Figure 56
104
AC power cabling in a quad-engine cluster
Reference
Dual-engine cluster
038-003-676, 71 in.
Management server
038-003-677, 37 in.
038-003-679, 20 in.
038-003-678, 20 in.
038-003-887, 48 in.
038-003-676, 71 in.
Engine 2
Engine 1
Zep-05_em
Figure 57
Ethernet cabling in a dual-engine cluster
Internal cabling
105
Reference
UPS B
UPS A
038-003-894
40 in.
038-003-894
40 in.
Engine 2
038-003-682
12 in.
038-003-682
12 in.
Engine1
038-003-682
12 in.
038-003-682
12 in.
Zep-05_sm
Figure 58
106
Serial cabling in a dual-engine cluster
Reference
038-003-738, 79 in. (all 16 cables)

(8 cables for large configuration are included for
ease of upgrading, and are tied to cabinet sidewalls
Engine 2
Engine 1
Zep-05_fm
Figure 59
Fibre Channel cabling in a dual-engine cluster

Note: All 16 Fibre Channel cables are light blue. However, the A side cables have blue labels
and the B side cables have orange labels.
Internal cabling
107
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
Zep-005_acm
Figure 60
108
AC power cabling in a dual-engine cluster
Reference
Single-engine cluster
038-003-677, 37 in.
038-003-676, 71 in.
Management server
Engine 1
Zep-005_es
Figure 61
Ethernet cabling in a single-engine cluster
Engine 1
038-003-682
12 in.
038-003-682
12 in.
Zep-005_ss
Figure 62
Serial cabling in a single-engine cluster
Engine 1
038-003-737,
39 in. (2 cables)
Zep-005_fs
Figure 63
Fibre Channel cabling in a single-engine cluster

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
109
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
Zep-005_acs
Figure 64
110
AC power cabling in a single-engine cluster
Reference
Cabinet power connections
Notes:
The upper PDPs are installed, but
are not used in V-Plex configurations.
Outlet group
circuit breaker
OG
ON
I
O
OFF
O
OFF
Unused PDP
OG
Power distribution
unit (PDU)
The upper PDUs are not used

in a small (2-director) configuration.
OG
ON
I
OG
ON
I
ON
I
O
OFF
O
OFF
OG
OG
ON
I
ON
I
O
OFF
O
OFF
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
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.
Rear view
To 30 A, 220 VAC
power source 1
Zep-012
Figure 65
Power connectors in a VPLEX cabinet
Cabinet power connections
111
Reference
112
Index
ls 39
acclimating to environment 25
addresses of hardware components 98
C
cabling, internal
dual-engine cluster 105
quad-engine cluster 101
single-engine cluster 109
Call Home, configuring 46
circuit breakers, PDU 30
cluster, defined 16
command globbing 39
connectivity, back-end, verifying 49
E
Element Manager 47
ESRS, setting up 50
EZ-Setup wizard 42
meta-volume
creating 44
described 20
P
paging mode, VPlexcli, exiting 39
paging through VPlexcli command output 39
password, service account 38
port roles 26
ports, enabling
front-end 50
WAN COM 87
power connections to PDUs 111
power switches, PDP 30
PuTTY, sessions, multiple 43
S
F
Fibre Channel ports 26
G
GbE ports 26
H
hardware required 20
I
I/O ports 26
IP addresses 98
setup wizard 42
software required 21
storage, exporting 51
SYR, configuring 48
T
TLA, determining 45
tools needed 21
U
username, service account 38
W
wizard, EZ-Setup 42
LEDs
management server 32
SPS 31
UPS 31
ll 39
113
Index
114

VPLEX 4.0 Installation and Setup Guide

Uploaded by

Document Information

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 4.0 Installation and Setup Guide

Uploaded by

Copyright:

Available Formats

EMC VPLEX

Installation and Setup Guide

Copyright 2010 EMC Corporation. All rights reserved.

EMC VPLEX v4.0 Installation and Setup Guide

Installing the Hardware

EMC VPLEX v4.0 Installation and Setup Guide

Task 13: Configure SYR ................................................................................... 48

EMC VPLEX v4.0 Installation and Setup Guide

Index ...................................................................................................................................................... 113

EMC VPLEX v4.0 Installation and Setup Guide

EMC VPLEX v4.0 Installation and Setup Guide

VPLEX hardware example: Single-engine cluster............................................................

EMC VPLEX v4.0 Installation and Setup Guide

Laptop connection to management server........................................................................ 73

EMC VPLEX v4.0 Installation and Setup Guide

Major VPLEX hardware components................................................................................. 18

EMC VPLEX v4.0 Installation and Setup Guide

EMC VPLEX v4.0 Installation and Setup Guide

Warnings and Cautions

The following warnings and cautions pertain throughout this guide.

Trained service personnel only.

Resrv au personnel autoris.

EMC VPLEX v4.0 Installation and Setup Guide

Warnings and Cautions

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 VPLEX v4.0 Installation and Setup Guide

Related documentation (avaliable on EMC Powerlink) includes:

EMC VPLEX Site Preparation Guide

EMC VPLEX Pre-installation Configuration Worksheet

EMC VPLEX V4.0 Security Configuration Guide

EMC VPLEX V4.0 Getting Started Guide

EMC VPLEX Release 4.0 and Point Releases Release Notes

EMC Best Practices Guide for AC Power Connections in Two-PDP Bays

EMC AC Power Configuration Worksheet

40U-C Unpacking and Setup Guide

EMC VPLEX v4.0 CLI Guide

VPLEX online help, available on the Management Console GUI

VPLEX procedure generator, available on EMC Powerlink

EMC uses the following conventions for special notices.

EMC VPLEX v4.0 Installation and Setup Guide

Used in running (nonprocedural) text for:

Where to get help

Used in all text (including procedures) for:

Used for specific user input (such as commands)

Used in procedures for variables on command line

Angle brackets enclose parameter or variable values supplied by the user

Square brackets enclose optional values

Vertical bar indicates alternate selections - the bar means or

EMC support, product, and licensing information can be obtained as follows.

Technical support For technical support, go to EMC Customer Service on

EMC VPLEX v4.0 Installation and Setup Guide

This chapter provides an overview of the EMC VPLEX hardware components.

VPLEX overview ........................................................................................................... 16

VPLEX hardware example: Single-engine cluster

The component placement in single-engine and dual-engine clusters allows for

EMC VPLEX v4.0 Installation and Setup Guide

Fibre Channel switch B

VPLEX hardware example: Dual-engine cluster

VPLEX hardware example: Quad-engine cluster