vplex 4.0 installation and setup guide

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® VPLEX™v4.0

Installation and Setup GuideP/N 300-010-499

REV A03

EMC VPLEX v4.0 Installation and Setup Guide2

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 changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION,AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE.

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 EMCPowerlink.

Contents

Preface.................................................................................................................................................... 13

Chapter 1 IntroductionVPLEX overview..................................................................................................... 16

Major components ............................................................................................ 18Preparing for a new installation ........................................................................... 20

Required information....................................................................................... 20Required hardware........................................................................................... 20Required software ............................................................................................ 21Required tools ................................................................................................... 21Reference: VPLEX requirements .................................................................... 21

Chapter 2 Installing the HardwareInstalling a cluster................................................................................................... 24

Task 1: Unpack and set up the cabinet ..........................................................24Task 2: Check the components .......................................................................24Task 3: Stabilize the equipment ......................................................................25Task 4: Connect the front-end and back-end cables ....................................26Task 5: Connect to the customer network .....................................................28Task 6: Metro-Plex only: Cable the clusters ..................................................28Task 7: Power on the components ..................................................................29

Chapter 3 Setting up VPLEXPreliminary tasks .................................................................................................... 34Setting up a VPLEX Local implementation ........................................................ 35

Task 1: Set the management server’s public IP address .............................35Task 2: Launch the VPLEX EZ-Setup Wizard ..............................................42Task 3: Verify the product version .................................................................42Task 4: Verify the VPLEX directors ................................................................42Task 5: Open a second PuTTY session ...........................................................43Task 6: Verify the director count ....................................................................43Task 7: Verify the Fibre Channel switches if present ..................................43Task 8: Expose back-end storage ....................................................................43Task 9: Verify storage volume availability ...................................................44Task 10: Create a meta-volume .......................................................................44Task 11: Determine the TLA ...........................................................................45Task 12: Configure Call Home ........................................................................46

EMC VPLEX v4.0 Installation and Setup Guide 3

Task 13: Configure SYR ................................................................................... 48Task 14: Verify back-end connectivity .......................................................... 49Task 15: Enable the front-end ports ............................................................... 50Task 16: Set up ESRS if necessary .................................................................. 50Task 17: Ensure that the I/O ports are zoned .............................................. 51Task 18: Expose storage to hosts .................................................................... 51Task 19: Perform a rescan ............................................................................... 54

Setting up a VPLEX Metro implementation....................................................... 55Task 1: Set the management server’s public IP address ............................. 55Task 2: Launch the EZ-Setup wizard ............................................................ 64Task 3: Verify the product version ................................................................ 64Task 4: Verify the VPLEX directors ............................................................... 64Task 5: Open a second PuTTY session .......................................................... 65Task 6: Verify the director count .................................................................... 65Task 7: Verify the Fibre Channel switches if present .................................. 65Task 8: Expose back-end storage ................................................................... 65Task 9: Verify storage volume availability ................................................... 66Task 10: Create a meta-volume ...................................................................... 66Task 11: Determine the TLA ........................................................................... 67Task 12: Configure Call Home ....................................................................... 68Task 13: Configure SYR ................................................................................... 70Task 14: Verify back-end connectivity .......................................................... 71Task 15: Enable the front-end ports ............................................................... 72Task 16: Connect to cluster 2 .......................................................................... 72Task 17: Launch the EZ-Setup wizard .......................................................... 80Task 18: Verify the product version .............................................................. 80Task 19: Verify the VPLEX directors ............................................................. 80Task 20: Open a second PuTTY session ........................................................ 81Task 21: Verify the director count .................................................................. 81Task 22: Verify the Fibre Channel switches if present ................................ 81Task 23: Expose back-end storage ................................................................. 81Task 24: Verify storage volume availability ................................................. 81Task 25: Create a meta-volume ...................................................................... 82Task 26: Determine the TLA ........................................................................... 83Task 27: Configure Call Home ....................................................................... 83Task 28: Configure SYR ................................................................................... 85Task 29: Verify back-end connectivity .......................................................... 86Task 30: Enable the front-end ports ............................................................... 87Task 31: Enable the WAN ports ..................................................................... 87Task 32: Set up ESRS if necessary .................................................................. 88Task 33: Open a VPlexcli session on cluster 1 .............................................. 88Task 34: Verify the date and time on both clusters ..................................... 88Task 35: Complete the setup on cluster 1 ..................................................... 89Task 36: Enable the WAN ports on cluster 1 ................................................ 89Task 37: Zone the WAN ports ........................................................................ 89Task 38: Connect cluster 1 to the directors in cluster 2 ............................... 89Task 39: Connect cluster 2 to the directors in cluster 1 ............................... 89Task 40: Join the clusters ................................................................................. 90Task 41: Create logging volumes ................................................................... 90Task 42: Verify that the clusters are fully connected .................................. 92Task 43: Verify the cluster status ................................................................... 92Task 44: Verify back-end connectivity on cluster 2 ..................................... 92Task 45: Verify back-end connectivity on cluster 1 ..................................... 93Task 46: Expose storage to hosts .................................................................... 93Task 47: Perform a rescan ............................................................................... 96


Appendix A ReferenceIP addresses and component IDs ......................................................................... 98Internal cabling ..................................................................................................... 100

Quad-engine cluster ....................................................................................... 101Dual-engine cluster ........................................................................................ 105Single-engine cluster ...................................................................................... 109

Cabinet power connections ................................................................................. 111

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


Title Page

Figures

1 VPLEX hardware example: Single-engine cluster............................................................ 162 VPLEX hardware example: Dual-engine cluster .............................................................. 173 VPLEX hardware example: Quad-engine cluster............................................................. 184 Engine components............................................................................................................... 195 I/O port connections to redundant fabrics ....................................................................... 226 Directors and I/O module carrier ...................................................................................... 247 Power cable wire bails .......................................................................................................... 248 Engine components: Front view ......................................................................................... 259 VPLEX I/O ports................................................................................................................... 2610 Cabling to front-end and back-end I/O ports .................................................................. 2711 Management server connection to customer IP network................................................ 2812 Intercluster cabling................................................................................................................ 2813 WAN cable routing on cable holders ................................................................................. 2914 Cabinet power switches and circuit breakers ................................................................... 3015 SPS power switches .............................................................................................................. 3016 SPS and director LEDs.......................................................................................................... 3117 UPS, front view...................................................................................................................... 3118 UPS, rear view ....................................................................................................................... 3119 Fibre Channel switch, rear (port side) view...................................................................... 3220 Management server power button and LEDs................................................................... 3221 Laptop connection to management server ........................................................................ 3522 PuTTY settings for VPLEX_service session....................................................................... 3623 PuTTY configuration: SSH protocol ................................................................................... 3724 PuTTY configuration: Scrollback setting ........................................................................... 3725 PuTTY Configuration: Logging window........................................................................... 3826 Director A-side addresses .................................................................................................... 3927 PuTTY settings for logging in over the customer network............................................. 4028 PuTTY configuration: Scrollback setting ........................................................................... 4129 PuTTY Configuration: Logging window........................................................................... 4130 VPLEX Management Console: Provision Storage button ............................................... 5131 Laptop connection to management server ........................................................................ 5532 PuTTY settings for VPLEX_service session....................................................................... 5633 PuTTY configuration: SSH protocol ................................................................................... 5734 PuTTY configuration: Scrollback setting ........................................................................... 5835 PuTTY Configuration: Logging window........................................................................... 5936 Director A-side addresses in cluster 1................................................................................ 6037 PuTTY settings for logging in to cluster 1 over the customer network ........................ 6238 PuTTY configuration: Scrollback setting ........................................................................... 6239 PuTTY Configuration: Logging window........................................................................... 6340 PuTTY settings for logging in to cluster 2 over the customer network ........................ 63


Figures

41 Laptop connection to management server........................................................................ 7342 PuTTY settings for VPLEX_service session ...................................................................... 7443 PuTTY configuration: SSH protocol .................................................................................. 7444 PuTTY configuration: Scrollback setting........................................................................... 7545 PuTTY Configuration: Logging window .......................................................................... 7646 Director A-side addresses.................................................................................................... 7747 PuTTY settings for logging in to cluster 2 over the customer network........................ 7848 PuTTY configuration: Scrollback setting........................................................................... 7849 PuTTY Configuration: Logging window .......................................................................... 7950 VPLEX Management Console: Provision Storage button............................................... 9351 Component IP addresses in cluster 1................................................................................. 9852 Component IP addresses in cluster 2................................................................................. 9953 Ethernet cabling in a quad-engine cluster....................................................................... 10154 Serial cabling in a quad-engine cluster............................................................................ 10255 Fibre Channel cabling in a quad-engine cluster............................................................. 10356 AC power cabling in a quad-engine cluster ................................................................... 10457 Ethernet cabling in a dual-engine cluster........................................................................ 10558 Serial cabling in a dual-engine cluster............................................................................. 10659 Fibre Channel cabling in a dual-engine cluster.............................................................. 10760 AC power cabling in a dual-engine cluster .................................................................... 10861 Ethernet cabling in a single-engine cluster ..................................................................... 10962 Serial cabling in a single-engine cluster .......................................................................... 10963 Fibre Channel cabling in a single-engine cluster ........................................................... 10964 AC power cabling in a single-engine cluster.................................................................. 11065 Power connectors in a VPLEX cabinet............................................................................. 111


Title Page

Tables

1 Major VPLEX hardware components................................................................................. 182 Data center acclimation times ............................................................................................. 25


Tables



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 electricshock, disconnect all power supply cords before servicing.

Ground-circuit continuity is vital for safe operation of the machine. Never operatethe machine with grounding conductors disconnected. Remember to reconnect anygrounding conductors removed for or during any installation procedure.

Attention Resérvé au personnel autorisé.

Cet appareil EMC comporte plus d'un cordon d'alimentation. Afin de prévenir leschocs électriques, débranchez tous les cordons d'alimentation avant de faire ledépannage.

Un circuit de terre continu est essentiel en vue du fonctionnement sécurisé del'appareil. Ne mettez jamais l'appareil en marche lorsque le conducteur de mise à laterre est débranché.

Warnung Nur für Fachpersonal.

Dieses EMC Produkt verfügt über mehrere elektrische Netzanschlüsse. ZurVermeidung eines elektrischen Schlages sind vor Servicearbeiten an derStromversorgung alle Netzanschlüsse zu trennen.

Kontinuierliche Erdung ist notwendig während der gesamten Betriebsdauer desGerätes. Es ist unzulässig das Gerät ohne Erdung zu betreiben. Gerät muss geerdetwerden, bevor es am Stromnetz angeschlossen wird.

Additional warningsand cautions

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

WARNING

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

Warnings and Cautions


Warnings and Cautions

WARNING

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

WARNING

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

CAUTION!Trained personnel are advised to exercise great care at all times when working onthe EMC hardware.Remember to:

◆ Remove rings, watches, or other jewelry and neckties before you begin anyprocedures.

◆ Use caution near any moving part and any part that may start unexpectedlysuch 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, andaccurate.

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

CAUTION!Before handling printed circuit boards or other parts containing LSI and/or VLSIcomponents, observe the following precautions:

◆ Store all printed circuit boards in antistatic bags.

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

◆ Unless specifically designed for nondisruptive replacement, never plug orunplug printed circuit boards with the power on. Severe component damagemay result.

Preface

As part of an effort to improve and enhance the performance and capabilities of its productlines, EMC periodically releases revisions of its hardware and software. Therefore, somefunctions described in this document may not be supported by all versions of the software orhardware currently in use. For the most up-to-date information on product features, refer toyour 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® fieldpersonnel as an aid in setting up a new VPLEX installation.

Persons performing the procedures described in this document should be familiarwith Linux commands and text editors.

Relateddocumentation

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 theApplication Download Area on the Global Services website

◆ VPLEX online help, available on the Management Console GUI

◆ VPLEX procedure generator, available on EMC Powerlink

Conventions used inthis document

EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.


Preface

CAUTION!A caution contains information essential to avoid data loss or damage to the systemor 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 severepersonal injury, death, or substantial property damage if you ignore the warning.

Typographical conventionsEMC uses the following type style conventions in this document:

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or forinformation about EMC products, licensing, and service, go to the EMC Powerlinkwebsite (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service onPowerlink. To open a service request through Powerlink, you must have a validsupport agreement. Please contact your EMC sales representative for details aboutobtaining 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, andoverall quality of the user publications. Please send your opinion of this document to:

[email protected]

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

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”


http://powerlink.emc.com

1

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

Note: Review the “Documentation” section in the current VPLEX release notes for anycorrections to this document. EMC® recommends that you mark up a copy of this guide withany corrections identified in the release notes. This can help minimize errors duringinstallation.

◆ VPLEX overview ........................................................................................................... 16◆ Preparing for a new installation.................................................................................. 20

Introduction

Introduction 15

Introduction

VPLEX overviewFigure 1 through Figure 3 show the main hardware components in the three availableconfigurations of an EMC® VPLEX™ cluster (a single-cabinet configuration). AVPLEX implementation can be VPLEX Local™ (single cluster) or VPLEX Metro™(two clusters, separated by up to 5 ms round trip time, or RTT).

Figure 1 VPLEX hardware example: Single-engine cluster

The component placement in single-engine and dual-engine clusters allows fornondisruptive upgrades to larger configurations. Note, however, that the currentVPLEX release does not support upgrading to a larger cluster configuration.

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

SPS 1

Engine 1

Management server

Director 1ADirector 1B

Zep-008


Introduction

Figure 2 VPLEX hardware example: Dual-engine cluster

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

SPS 1

Engine 1

UPS A

Fibre Channel switch A

Fibre Channel switch B

Management server


SPS 2

Engine 2 Director 2ADirector 2B

UPS B

Zep-07

VPLEX overview 17

Introduction

Figure 3 VPLEX hardware example: Quad-engine cluster

Major components Table 1 describes the major hardware components in a VPLEX cluster.ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

SPS 1

Engine 1

UPS A

COM switch A

COM switch B

Management server


SPS 2

Engine 2

SPS 3

Engine 3

SPS 4

Engine 4




UPS B

Zep-06

Table 1 Major VPLEX hardware components

Component Description

Engine (shown inFigure 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/Omodule contains four 8 Gb/s Fibre Channel ports.

• I/O module carrier, containing two Fibre Channel I/O modules (one for each director) for intersiteand 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 powersupply (SPS)

Provides backup power (through a pair or redundant modules) that allows an engine to ride throughtransient (30 seconds or less) power loss.


Introduction

Figure 4 Engine components

Fibre Channel COMswitches

Provide highly available connectivity among the directors in a medium (two-engine) or large(four-engine) cluster.

Uninterrupted powersupplies (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 accessfrom 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)

Table 1 Major VPLEX hardware components

Component Description

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 byEMC personnel.

Before installing a new VPLEX cluster:

◆ Verify that all necessary hardware has been received at the customer site(s), asdocumented in the purchase order and shipping list.

◆ Verify that two storage devices of at least 78 GB each have been allocated for useas a VPLEX meta-volume and a mirrored copy. (The meta-volume will containRAID 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 toall VPLEX directors from the meta-volume LUN.

You must ensure that these storage devices will provide a maximum averageresponse time of 10 ms (for random 4K reads). The best practice to ensure this isto allocate dedicated spindles on the array for any LUN that will be used as partof the meta-volume mirror.

◆ Verify that you have the following EMC Secure Remote Support (ESRS) gatewayinformation:

• ESRS gateway account.

• Model Number — VS1

• Serial Number — Top-level assembly number (TLA) of the cluster, availableon 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 managementserver

◆ Verify that the conditions identified in “Reference: VPLEX requirements” onpage 21 have been met.

Requiredinformation

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 andgraphical interface for connecting to the VPLEX management server and configuringyour VPLEX cluster(s). For convenience, this guide uses the term laptop to describethe device.

Before starting the installation and configuration procedures described in this guide,confirm that your laptop has the following:

◆ USB port.

◆ CD-ROM drive.


Introduction

◆ Fully charged batteries — For mobility between the lab environment and aquieter 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.

Required software Confirm that you have the following on your laptop:

◆ Windows OS

◆ PuTTY, version 0.60 or later (download from www.putty.org) or similar SSHclient

◆ 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 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)

Reference: VPLEXrequirements

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 eachcluster.

◆ Ensure that multi-pathing is configured in such a way that the paths aredistributed 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 thefront-end and back-end ports. Connecting the ports as shown prevents dataunavailability if a single I/O module fails.

Preparing for a new installation 21

Introduction

Figure 5 I/O port connections to redundant fabrics


2

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 useprimarily by EMC personnel.

◆ Installing a cluster ......................................................................................................... 24

Installing theHardware

Installing the Hardware 23

Installing the Hardware

Installing a cluster

Task 1: Unpack andset up the cabinet

Follow the steps in the EMC 40U-C Cabinet Unpacking and Setup Guide, whichaccompanies each VPLEX cabinet (and is available on Powerlink).

Task 2: Check thecomponents

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.

Figure 6 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 securelyconnected, 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 plug’s plasticmolding, and the bail on each Fibre Channel switch must be clamped onto thecable itself, as shown in Figure 7.

Figure 7 Power cable wire bails

If any cable has become disconnected, reconnect it as identified by the labels onthe cable and cabinet, as well as “Internal cabling” on page 100 of this guide.

Director “n” B

Director “n” A

I/O module carrierZep-041

SYM-002500z

SPS and UPS:The wire cable bail is inserted into

the middle of the plug’s plastic molding.

Fibre Channel switch:The wire cable bail is against

the end of the plug’s plastic molding.



5. From the front of the cabinet, remove each engine’s bezel as shown inFigure 8 ,and verify that the two power supply modules, four fan modules, and solid statedrive (SSD) enclosure are fully inserted and secure.

Figure 8 Engine components: Front view

Task 3: Stabilize theequipment

The equipment requires time to become acclimated to a data center environment.Table 2 lists the required times.

Note: Temperature and humidity values must be such that condensation does not occur on anyVPLEX component. Altitude and atmospheric pressure specifications are referenced to astandard day at 58.7°F (14.8°C). Maximum wet bulb temperature is 82°F (28°C).

CL4341c

!

!

Power supply

Fan

SSD enclosure

Table 2 Data center acclimation times

Transit/storage environment Hours requiredbefore applyingpower

Conditioned air: nominal officeor computer room environment(< 30% relative humidity)Condition Temperature range Relative humidity

Nominal 68o to 72oF (20o to 22oC) Less than 30% 0 68o to 72oF (20o to 22oC)

Cool / Damp Less than 68oF (20oC) 30% or greater 4 Less than 86oF (30oC)

Cold / Dry Less than 68oF (20oC) Less than 20%

Hot / Dry 72o to 90oF (22o to 32oC) Less than 30%

Hot / Humid 72o to 90oF (22o to 32oC) 30% to 45%

45% to 60% 8

60% to 80% 16

Installing a cluster 25


Task 4: Connect thefront-end andback-end cables

Connect customer-supplied Fibre Channel cables from the front-end and back-endSANs to the appropriate VPLEX I/O ports (identified in Figure 9).

Figure 9 VPLEX I/O ports

Route the cables horizontally to the sides of the cabinet as shown in Figure 10 onpage 27, to prevent blocking other components in the cabinet. Route the cables downthe sides of the cabinet through the plastic cable holders, and secure the cables withthe Velcro straps that are attached to the cabinet frame. Maintain a minimum radiusof two inches for any bend in a Fibre Channel cable.



Figure 10 Cabling to front-end and back-end I/O ports

Zep-005_FC

ONONI

OFFOFFO

ONONI

OFFOFFO

ONONI

OFFOFFO

ONONI

OFFOFFO

ONONI

OFFOFFO

ONONI

OFFOFFO

ONONI

OFF OFFO

ONONI

OFF OFFO

ONONI

OFF OFFO

ONONI

OFF OFFO

ONONI

OFF OFFO

ONONI

OFF OFFO

Engine 2

Engine 1

Engine 4

Back-endcables

Front-endcables

Engine 3



Task 5: Connect tothe customernetwork

Connect the management server to the customer IP network as shown in Figure 11.

Figure 11 Management server connection to customer IP network

Task 6: Metro-Plexonly: Cable theclusters

In a Metro-Plex configuration, connect each director in each cluster (through its WANports 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 inFigure 13 on page 29, and route the cables up or down the sides of the cabinetwith the I/O cables.

Figure 12 Intercluster cabling

zep-09a

1 Gb/s public Ethernet port

Customer-provided Ethernet cable

CustomerIP network

Zep-049

Cluster 1 (same connections from each engine in cluster) Cluster 2 (same connections from each engine in cluster)

InterclusterCOM SANswitch 1A

InterclusterCOM SANswitch 2A

ISL 1

InterclusterCOM SANswitch 2B

ISL 2InterclusterCOM SANswitch 1B

A4-FC03B4-FC03A4-FC02

B4-FC02 A4-FC03B4-FC03A4-FC02

B4-FC02



Figure 13 WAN cable routing on cable holders

Task 7: Power on thecomponents

1. Verify that all PDP switches and PDU circuit breakers (shown in Figure 14 onpage 30) are in the OFF position. As the figure notes, the upper pair of PDUs areinstalled 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 convenientlocation foe use in verifying the data center power schemes.

3. Connect the main AC power cables from the lower PDPs into the site’s powersources. To ensure high availability, each cable must connect to a different powersource, as described in the EMC Best Practices Guide for AC Power Connections inTwo-PDP Bays.

zep-070a

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

0

1

2

3

01

23

I/O Module A4

01

23

0

1

2

3

1

2

0

Detail

Separate wiresaround posts

Remove cap to routecables, and then

replace cap3

Route cables from ports A4-FC02and B4-FC02 to B side

Route cables from portsA4-FC03 and B4-FC03 to A side



Figure 14 Cabinet power switches and circuit breakers

4. Switch all SPS power switches (shown in Figure 15) ON.

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 powerstrip.)

7. Verify that the LED status on each SPS and director is as shown in Figure 16 onpage 31.

Zep-013

The upper PDUs are installedupside-down from the lower PDUs.

The upper PDPs are installed,but are not used.

The upper PDUs are not used in asingle-engine configuration.

PDU circuitbreakers

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

PDP powerswitch

PDP powerswitch

Notes:

To 30 A, 220 VAC power source 1


CL4171



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 thebattery). If any amber LED not related to the SPS recharge remains on formore than 10 minutes, verify that the components are cabled correctly.

Figure 16 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 isilluminated.

If the Online LED on either UPS is not illuminated, push the power button,and verify that the LED is illuminated before proceeding.

Figure 17 UPS, front view

b. Verify that neither circuit breaker (shown in Figure 18) on either UPS hastriggered. If a circuit breaker has triggered, press it to reseat it.

Figure 18 UPS, rear view

Zep-011a

Steady green

Amber during POST, offduring normal operation

Director LEDs

On-line Enabled (LED on) or On-line Charging (LED flashing)On-BatteryReplace BatteryInternal Check

SPS LEDs:

sym-001521z

Online LED Overload LED

On battery LED Replace battery LED

Power button

Zep-036a

Circuit breakers



c. Verify that the Power and Status LEDs (shown in Figure 19) on both FibreChannel switches are steady green.

Figure 19 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 isilluminated.

If the LED is not on, press the power button.

Figure 20 Management server power button and LEDs

11. Replace the management server bezel.

Zep-034

Status LED

Power LED

Zep-015Power LEDPower button


3

This chapter describes the tasks to set up a VPLEX Local or VPLEX Metroimplementation. Topics include:

◆ Preliminary tasks........................................................................................................... 34◆ Setting up a VPLEX Local implementation............................................................... 35◆ Setting up a VPLEX Metro implementation.............................................................. 55

Setting up VPLEX

Setting up VPLEX 33

Setting up VPLEX

Preliminary tasksBefore you begin the VPLEX setup tasks, perform the following steps:

Note: The values (especially version numbers) in any command output in this document that isidentified 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 EMCPowerlink:

• Best Practices white papers.

• EMC VPLEX Pre-installation Configuration Worksheet. This document is inMicrosoft Word format, to provide a means of typing information (such as IPaddresses) that you will need during the setup procedure.

• EMC VPLEX CLI Guide, which provides detailed information on the VPlexclicommands identified in this installation and setup guide.

• VPLEX Procedure Generator, which contains procedures to upgrade to a newGeoSynchrony™ (VPLEX operating system) release, and to troubleshootinstallation or configuration issues.

2. If not already done, download the EMC VPLEX Pre-installation ConfigurationWorksheet 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 thesetup 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 anupgrade 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 theentire 4.0 setup procedure as documented in this guide, and then perform anupgrade to the desired release.

Note: If any operation described in this document fails, review the troubleshootingdocument. If this does not resolve the problem, contact the EMC Support Center.

Next step 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 “Settingup a VPLEX Metro implementation” on page 55. You cannot set up each clusterindividually and then join them later.

Task 1: Set themanagementserver’s public IPaddress

Before you can log in to the VPLEX management server over the customer network,you must set the address on the management server’s 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 thered service cable that hangs inside the EMC cabinet.

Figure 21 Laptop connection to management server

2. On your laptop’s toolbar, select Start > Settings > Control Panel > NetworkConnections (double-click).

3. If any public network connection is enabled on your laptop, right-click thenetwork card and select Disable.

4. On the Network Connections window, right-click Local Area Connection andselect Properties.

5. On the Local Area Connection Properties window, double-click InternetProtocol (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, toensure 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 theLocal Area Connection Properties window.

8. Close the Network Connections window.

zep-009b

Red service cable in cabinet Service port

Mgmt-B port Mgmt-A port

LaptopPublic Ethernet port

Setting up a VPLEX Local implementation 35

Setting up VPLEX

9. Open a Command Prompt window (Start > Programs > Accessories > CommandPrompt), and type the following command to confirm the settings:

ipconfig

Output example:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : eng.emc.comIP Address. . . . . . . . . . . . : 128.221.252.3Subnet Mask . . . . . . . . . . . : 255.255.255.224Default Gateway . . . . . . . . . : 128.221.252.2

10. Type the following command to verify that you can reach the managementserver’s 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.

Figure 22 PuTTY settings for VPLEX_service session

13. Select SSH in the Category list, and ensure that Preferred SSH protocol versionis set to 2, as shown in Figure 23.

PuTTY

Type:128.221.252.2

(default)

(default)

Type session name:VPLEX_service


Setting up VPLEX

Figure 23 PuTTY configuration: SSH protocol

14. For most of the setup tasks, you can leave your laptop connected directly to themanagement server, or you can move to a more-comfortable location andreconnect 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 astandard-size PuTTY session window. One solution is to extend thescrolling capability. To do this, select Window in the Category list, and setLines of scrollback (shown in Figure 24) to 20000.

Figure 24 PuTTY configuration: Scrollback setting

SSH protocolversion

putty_ssh

scrollback

Set to 20000


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 logfile can grow quite large. However, if you want to create a log file anyway:

Note: Over the course of setting up a dual-engine or quad-engine cluster, the logfile can grow quite large.

Note: The log file saves data from the current PuTTY session. Any time you open anew session, you must repeat this step if you want to log the output for that session.

Figure 25 PuTTY Configuration: Logging window

15. Select Session in the Category list, and click Save in the PuTTY Configurationwindow to save the settings for the session you configured.

16. Click Open to establish a connection to the management server, and log in withusername service and password Mi@Dim7T.

Note the following:

• If the connection fails to open, ping 128.221.252.3 (the LAN port on yourlaptop) 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 isservice@<current_working_directory>.

17. From the Linux shell prompt, type the following command to verify that theVPlexcli process started:

sudo /etc/init.d/VPlexElementManager status

i.

ii.

iii.

Select Logging in the PuTTY Configuration Category list.

Under Session logging, select All session output.

Type a name in the Log file name field (shown in Figure 25).

putty_log

All session output

File name


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 tabfeature. If you start typing a command, pressing Tab at any time fills in the commandautomatically, 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. (Thecluster is assigned a Cluster ID of 1 automatically.) This name replaces the defaultname (service) in the shell prompt the next time you open an SSH session to themanagement server.

19. From the shell prompt, type the following command, to verify connectivy todirector 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 applicableaddress shown in Figure 26.

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 server’s publicEthernet port:

management-server set-ip -i <IP_address>:<netmask> -g <gateway> eth3

128.221.252.36128.221.252.35

Engine 1:Director 1-BDirector 1-A

128.221.252.38128.221.252.37


128.221.252.40128.221.252.39


128.221.252.42128.221.252.41


Single-enginecluster

Dual-enginecluster

Quad-enginecluster


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 setuptasks, type the following command at the VPlexcli prompt, and again at the Linuxshell 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 thenetwork.

• 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, andinstall 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.

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 astandard-size PuTTY session window:

• One solution is to extend the scrolling capability. To do this, select Window inthe Category list, and set Lines of scrollback (shown in Figure 28) to 20000.

PuTTY5

Address of publicEthernet port on management server

Session name,such as: VPLEX

(default)

(default)


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 filecan 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).



scrollback

Set to 20000

putty_log

All session output

File name


Setting up VPLEX


30. Click Open, and log in to the management server with username service andpassword Mi@Dim7T.




Task 2: Launch theVPLEX EZ-SetupWizard

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 VPLEXPre-installation Configuration Worksheet as you respond to the prompts.

From the VPlexcli prompt, type the following command, and follow the steps in theautomated interview and configuration procedure:

configuration system-setup

When you see the message Configuration Complete, proceed to “Task 3: Verify theproduct version.”

Task 3: Verify theproduct version

From the VPlexcli prompt, type the following command:

version -a

In the output, confirm that the Product Version matches the required version in theVPLEX release notes.

Task 4: Verify theVPLEX directors


ll /engines/**/directors

Verify that the output lists all directors in the cluster, and that all directors show thefollowing:

◆ Commissioned status: true

◆ Operational status: ok

◆ Communication status: ok

Output example in a dual-engine cluster:

/engines/engine-1-1/directors:Name Director ID Cluster Commissioned Operational Communication------------- ----------------- ID ------------ Status Status------------- ----------------- ------- ------------ ----------- ------------director-1-1-A 0x000000003ca00183 1 true ok okdirector-1-1-B 0x000000003cb00183 1 true ok ok



Setting up VPLEX

Task 5: Open asecond PuTTYsession

Some setup tasks require executing commands from the VPlexcli prompt, and othersrequire excuting commands from the Linux shell prompt. You will find it easier toleave two PuTTY sessions open on the management server, and use the applicablesession for each task.

For ease of identification, tasks that you perform in one of these sessions include oneof the following icons: .

To open a new Linux shell session, leave the VPlexcli session open, and follow thesesteps:

1. Launch PuTTY.exe.

2. Configure PuTTY as shown in Figure 27 on page 40, and then click Save.


Task 6: Verify thedirector 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 ensurethat 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 theFibre Channelswitches 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 FibreChannel 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: Exposeback-end storage

1. From the VPlexcli prompt, type the following command to list alldirector port WWNs (identified in the command output as addresses):

ll /engines/**/ports -p


Setting up VPLEX

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 (calledcommand globbing). The VPLEX CLI Guide provides more detail.

2. Zone the storage to the port WWNs of the VPLEX back-end ports, following therecommendations in the Implementation and Planning Best Practices for EMCVPLEX Technical Notes, which are available on Powerlink.

Task 9: Verifystorage volumeavailability

1. From the VPlexcli prompt, type the following commands torediscover 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 (no tier)------------ -----------------Health out-of-date 0

storage-volumes 452unhealthy 0

Vendor EMC 452

Use unclaimed 452

Capacity total 271G

Task 10: Create ameta-volume

1. From the VPlexcli prompt, type the following command to listavailable 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 traditionalClar0068_LUN74 VPD83T3:6006016049e02100291ebe77852cdf11 78G meta-data DGC alive traditionalClar0068_LUN75 VPD83T3:6006016049e02100c064c78a852cdf11 10G unclaimed DGC alive normalClar0068_LUN76 VPD83T3:6006016049e02100c164c78a852cdf11 10G unclaimed DGC alive 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.

Note: The VPlexcli commands ll (two lowercase Ls) and ls support a paging option thatallows 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.)


Setting up VPLEX

3. Type the following command to create the meta-volume and amirror:

Note: You can copy a storage volume name from the ll output and paste it into thefollowing command. To do this, highlight the volume to select it, and then right-click at thepoint 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 themeta-volume.

• <storage-volume_2_name> is the VPD name of the mirror.

The mirror can consist of multiple storage volumes (which will become aRAID 1), in which case you would include each additional volume, separatedby 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 theoutput 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-1operational-status: oktransitioning-indications:transitioning-progress:health-state: okhealth-indications:

Task 11: Determinethe TLA

From the VPlexcli prompt, type the following command to list theattributes of engine 1, and make a note of the top-level-assembly in the output. Thisis the TLA (which is the same for each engine in a cluster) that you will need tospecify in a later task:

ll /engines/engine-1-1


Setting up VPLEX

Task 12: ConfigureCall Home

To configure the Call Home parameters:

1. From the shell prompt, type the following command from thedirectory /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:

EMC recommends that you configure the following notifications, in the orderlisted:

– 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 gatewayserver IP address.

– If ESRS is being used for a secondary notifcation, enter a local SMTP IPaddress.

– 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 theApplication Download area, under EMC Secure Remote Support Gateway >Implementation > Install Procedure.

• <sender_email_address> should be VPlex_<TLA>@EMC.com (where <TLA> isthe 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 sendingnotifications to EMC, use [email protected] 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 thepurpose of the connection.

Type Use

• Primary• Failover

For connections to the EMC Support Center

• onSuccess• onFailure• onSuccess/onFailure• onAllFailure

For notifications to the customer


Setting up VPLEX

• <attach_call_home_data> is valid only if <notification type> is one of the valuesused for customer notification, and allows attaching non-encrypted CallHome XML data to the email. Valid values are Yes or No. (Note that the valueis case-sensitive.)

Command example:

./connectemcConfig -n Primary -e 10.254.3.30 [email protected] -r [email protected]

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 <ConnectConfigType="<type>"> and ends with the line </ConnectConfig>.)

2. After you have configured all notifcations, type the followingcommands 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 Running

3. Type the following commands to restart the VPLEX ManagementConsole 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 Managerin some commands and output.

Output example:

Checking VPlex Element Manager status Running

4. From either shell prompt, type the following commands to restartthe emaAdaptor process and verify the status:

sudo /etc/init.d/VPlexEmaAdaptor restart

sudo /etc/init.d/VPlexEmaAdaptor status

Output example:

Checking VPlex EmaAdaptor status Running

5. From either Linux shell prompt, type the following command toconnect to the VPlexcli:




Setting up VPLEX

6. From the VPlexcli prompt, type the following commands to enableCall Home and confirm that it is enabled:

cd /notifications/call-home

set enabled true

ls

Output from ls:

Name Value------- -----enabled 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 thecustomer’s email address. If Call Home was set up to notify EMC, the emailshould arrive at the EMC Support Center.

Task 13: ConfigureSYR

The VPlexcli includes a set of commands (described in the EMC VPLEX CLI Guide) tocollect system configuration for the EMC System Reporting database (SYR) .

To configure a weekly SYR job, type the commands in the followingsteps:

Note: If you are configuring the second cluster in a Metro-Plex, set the same schedule that is seton 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: 3Minutes: 0

3. Verify that SYR is working correctly:

syrcollect


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 addressspecified in the Call Home setup. Ensure that the SYR team verifies this file.

Task 14: Verifyback-endconnectivity

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

connectivity validate-be

As the following output example shows, all storage volumes must have dualpaths, and must be visible from all VPLEX directors:

SummaryCluster cluster-1

This cluster has 0 storage-volumes which are dead or unreachableThis cluster has 0 storage-volumes which do not have dual pathsThis cluster has 0 storage-volumes which are not visible from alldirectors

If all storage volumes do not have dual paths, the output might be similar to thefollowing:

Storage volumes that are dead or unreachable:

Cluster Dead or Unreachable Storage Volumes--------- ----------------------------------------cluster-1 VPD83T3:60000970000192601426533032463334

Storage volumes that are not visible at all directors:

Cluster Director Storage Volumes Director Cannot See--------- -------------- ----------------------------------------cluster-1 director-1-1-B VPD83T3:60000970000192601426533032463334



2. For each director in the cluster, type the following command, andverify 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, 1–4, numbered from the bottom up.


Volume Node WWN Port WWN PortVPD83T3:6006016049e0210097fe419323d6de11 0x500601663ce00f51 0x0009000000000000 A2-FC00

0x500601673ce00f51 0x0009000000000000 A3-FC000x5006016e3ce00f51 0x0009000000000000 A3-FC000x5006016f3ce00f51 0x0009000000000000 A2-FC00

VPD83T3:6006016055b72200a0ec26a913ebde11 0x500601603b20119c 0x0093000000000000 A2-FC000x500601613b20119c 0x0093000000000000 A3-FC000x5006016a3b20119c 0x0093000000000000 A3-FC000x5006016b3b20119c 0x0093000000000000 A2-FC00


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 thefront-end ports

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

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 followsthis 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 Address Role Port Status------- ------------------ --------- -----------B0-FC00 0x5000144250014d00 front-end no-linkB0-FC01 0x5000144250014d01 front-end no-linkB0-FC02 0x5000144250014d02 front-end no-linkB0-FC03 0x5000144250014d03 front-end no-linkB1-FC00 0x5000144250014d10 front-end no-linkB1-FC01 0x5000144250014d11 front-end no-linkB1-FC02 0x5000144250014d12 front-end no-linkB1-FC03 0x5000144250014d13 front-end no-linkB2-FC00 0x5000144250014d20 back-end upB2-FC01 0x5000144250014d21 back-end upB2-FC02 0x5000144250014d22 back-end upB2-FC03 0x5000144250014d23 back-end up

If you are configuring a VPLEX Local implementation, verify that all wan-comports (A4-FC02, A4-FC03, B4-FC02, and B4-FC03) in each engine have a PortStatus of down. If one or more wan-com ports have any other status, type thefollowing command:

set /**/*4-FC0[2-3]::enabled false

Task 16: Set up ESRSif necessary

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


Setting up VPLEX

Task 17: Ensure thatthe I/O ports arezoned

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

Task 18: Exposestorage 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 asingle extent per storage volume, and then use devices to concatenate or stripethese 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. Thebasic steps are the same for either:

◆ To use the GUI, proceed to “If you are using the GUI.”

◆ To use the VPlexcli, proceed to “If you are using the VPlexcli” on page 52.

If you are using theGUI

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 publicIP port.

2. Log in with username service and password Mi@Dim7T.

3. To begin provisioning and exporting storage, click Provision Storage on the mainscreen 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 upperright corner of the screen. To display documentation and additional resources for the currentVPLEX release, click Help on the task bar.


Setting up VPLEX

If you are using theVPlexcli

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 storagevolumes:

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, orclar2065_LUN537) in the output from step 1.

Note: If you want to claim multiple storage volumes, separate the volume IDs withcommas or use the command storage-volume claimingwizard, as described in theVPLEX 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 ofthe storage volume. However, you can create multiple smaller extents (up to 128per 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_1002_1 extent_Symm1707_1003_1extent_Symm1707_1004_1 extent_Symm1707_1005_1 extent_Symm1707_1006_1 extent_Symm1707_1007_1extent_Symm1707_1008_1 extent_Symm1707_1009_1 extent_Symm1707_100A_1 extent_Symm1707_100B_1extent_Symm1707_100C_1 extent_Symm1707_100D_1 extent_Symm1707_100E_1 extent_Symm1707_100F_1extent_Symm1707_1010_1 extent_Symm1707_1011_1 extent_Symm1707_1012_1 extent_Symm1707_1013_1extent_Symm1707_1014_1 extent_Symm1707_1015_1 extent_Symm1707_1016_1 extent_Symm1707_1017_1extent_Symm1707_1018_1 extent_Symm1707_1019_1 extent_Symm1707_101A_1 extent_Symm1707_101B_1extent_Symm1707_101C_1 extent_Symm1707_101D_1 extent_Symm1707_101E_1 extent_Symm1707_101F_1extent_Symm1707_1020_1 extent_Symm1707_1021_1 extent_Symm1707_1022_1 extent_Symm1707_1023_1extent_Symm1707_1024_1 extent_Symm1707_1025_1 extent_Symm1707_1026_1 extent_Symm1707_1027_1extent_Symm1707_1028_1 extent_Symm1707_1029_1 extent_Symm1707_102A_1 extent_Symm1707_102B_1extent_Symm1707_102C_1 extent_Symm1707_102D_1 extent_Symm1707_102E_1 extent_Symm1707_102F_1extent_Symm1707_1030_1 extent_Symm1707_1031_1 extent_Symm1707_1032_1 extent_Symm1707_1033_1extent_Symm1707_1034_1 extent_Symm1707_1035_1 extent_Symm1707_1036_1 extent_Symm1707_1037_1extent_Symm1707_1038_1 extent_Symm1707_1039_1 extent_Symm1707_103A_1 extent_Symm1707_103B_1

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

cd /clusters/cluster-1/devices


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 port-wwn node-wwn type Target Port Names------------ ------------------ ------------------ ------- --------------------------habc4101_pt0 0x10000000c866fff2 0x20000000c866fff2 default P000000003CA00165-A0-FC00,

P000000003CA00183-A0-FC00,P000000003CB00165-B0-FC00,P000000003CB00183-B0-FC00

habc4101_pt1 0x10000000c866fff3 0x20000000c866fff3 default P000000003CA00165-A0-FC01,P000000003CA00183-A0-FC01,P000000003CB00165-B0-FC01

habc4102_pt0 0x10000000c866ffec 0x20000000c866ffec default P000000003CA00165-A1-FC00,P000000003CA00183-A1-FC01,P000000003CB00165-B1-FC00,P000000003CB00183-B1-FC01

habc4102_pt1 0x10000000c866ffed 0x20000000c866ffed default 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 tothe end of the command. For example:

storage-view addvirtualvolume -f -v <storage_view_name> -i<virtual-volume_name>,<virtual-volume_name>


Setting up VPLEX

Note: Including -f forces the virtual volumes to be added to the view even if the specifiedLUNs 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 registered

initiators----------- ------------ ---------------- ----- ----------VMware_view healthy 2 4 4view1 healthy 1311 4 480view2 healthy 10 4 2view3 healthy 11 4 2view4 healthy 10 4 2

Total 5 views, 0 unhealthy.

Task 19: Perform arescan

After provisioning and exporting storage, perform a rescan from the host to verifythat 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 seteach cluster up individually and then join them later.

Task 1: Set themanagementserver’s public IPaddress

Before you can log in to a VPLEX management server over the customer network,you must set the address on the management server’s public Ethernet port:

Note: The first cluster you set up will be designated cluster 1, and the second cluster will becluster 2. Several tasks in this guide refer to the management servers on cluster 1 and cluster 2as 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 VPLEXcluster you are setting up, and use the cable to connect your laptop to the cluster’smanagement server as shown in Figure 31.










zep-009b




Setting up a VPLEX Metro implementation 55

Setting up VPLEX




ipconfig

Output example:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : eng.emc.comIP Address. . . . . . . . . . . . : 128.221.252.3Subnet Mask . . . . . . . . . . . : 255.255.255.224Default Gateway . . . . . . . . . : 128.221.252.2


ping 128.221.252.2






PuTTY

Type:128.221.252.2

(default)

(default)



Setting up VPLEX




• If you are going to remain connected directly for the entire setup procedure onthis 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 inFigure 34 on page 58) to 20000. (This allows you to read long output in astandard-size PuTTY session window.)

SSH protocolversion

putty_ssh


Setting up VPLEX


b. If you want to save the session output to a log file:



scrollback

Set to 20000

i.

ii.

iii.



Type a name in the Log file name field (shown in Figure 35 onpage 59).


Setting up VPLEX



16. On the PuTTY Configuration window, click Open to establish a connection to themanagement 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 theVPlexcli process started:


18. Type the following command to change the hostname:



where <hostname> is a name for the management server, such as Cluster1. Thisname replaces the default name (service) in the shell prompt the next time youopen a PuTTY session to the management server


ping 128.221.252.35 -c 5


putty_log

All session output

File name


Setting up VPLEX


Figure 36 Director A-side addresses in cluster 1







• If you want to leave your laptop connected to the management server, go to“Task 2: Launch the EZ-Setup wizard” on page 64.



exit

25. Disconnect the red service cable from the management server and hang it back inthe 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 secondcluster’s cabinet to connect to the service port on the management server, andthen proceed to step 27.

27. Launch PuTTY, and load the VPLEX_Service session you saved earlier in thistask.

28. Click Open, and log in with username service and password Mi@Dim7T.

Zep-056

128.221.252.36128.221.252.35


128.221.252.38128.221.252.37


128.221.252.40128.221.252.39


128.221.252.42128.221.252.41



Dual-enginecluster

Quad-enginecluster


Setting up VPLEX

29. From the Linux shell prompt, type the following command, and verify that theVPlexcli process started:


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 usernameservice and password Mi@Dim7T:


32. From the VPlexcli prompt, type the following command to configure the IPaddress of the management server’s public Ethernet port:


33. Type the following command at the VPlexcli prompt, and again at the Linux shellprompt:

exit



– If you are connecting your laptop to the network, set it to an IP address onthe network.

– If you are connecting from a different PC (or similar device):

a. Restore your laptop to the settings it had before you began thisprocedure (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.



Setting up VPLEX


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 inFigure 38) to 20000. (This allows you to read long output in a standard-sizePuTTY session window.)


38. If you want to save the session output to a log file:




PuTTY2

Type the address of thepublic Ethernet port onthe management serverin the first cluster you are configuring

Type a name that identifiesthe cluster, such as:VPLEX Cluster 1

(default)

(default)

VPLEX service

scrollback

Set to 20000


Setting up VPLEX

Note: Over the course of setting up a dual-engine or quad-engine cluster, the log file cangrow quite large.

Note: The log file saves data from the current PuTTY session. Any time you open a newsession, you must repeat this step if you want to log the output for that session.



40. Configure a new PuTTY session as shown in Figure 40.


putty_log

All session output

File name

PuTTY3

Type the address of thepublic Ethernet port onthe management serverin the second cluster you are configuring


(default)

(default)

VPLEX serviceVPLEX Cluster 1


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.





Task 2: Launch theEZ-Setup wizard

The setup wizard performs several tasks to set up a VPLEX implementation, based ona series of prompts for user-entered information. Refer to the EMC VPLEXPre-installation Configuration Worksheet as you respond to the prompts.






version -a













Setting up VPLEX



To open a new Linux shell session, leave the VPlexcli session open, and follow thesesteps:

1. Launch PuTTY.exe.

2. Configure PuTTY as described in step 37 on page 62 through step 39 on page 63.


For ease of identification, many of the remaining tasks in this section include one ofthe following icons to identify the associated session: .




director_count=<n>






1. Ping switch A:

ping 128.221.252.34

2. Ping switch B:

ping 128.221.253.34





Setting up VPLEX

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 (calledcommand globbing). The VPLEX CLI Guide provides more detail.




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




Output example:



Vendor EMC 452

Use unclaimed 452

Capacity total 271G






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: The VPlexcli commands ll (two lowercase Ls) and ls support a paging option thatallows 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.)


Setting up VPLEX




where:









cluster status


Output example:






Setting up VPLEX






where:














Type Use






Setting up VPLEX


Command example:






Output example:





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


Output example:





Output example:






Setting up VPLEX



set enabled true

ls

Output from ls:




test






To configure a weekly SYR job, type the commands in the followingsteps:



where:





scheduleSYR list

Output example:



syrcollect



Setting up VPLEX
















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, andthe Enclosure ID is the engine number, 1–4, numbered from the bottom up.






Setting up VPLEX


COMSCSI 0x5000144250014d40 A4-FC00


Type the following command to enable all front-end ports in the cluster:







Task 16: Connect tocluster 2

1. Did you set the public IP address on both management servers in Task 1 onpage 55?

Note: As a reminder, the only scenario in which you would have done this is if bothclusters are at the same location and you connected to the cluster over the customernetwork after you set the IP address on the management server.

• If yes:

a. Type the following command at the VPlexcli prompt, and again at theLinux shell prompt:

exit

b. Establish a PuTTY session to the management server in cluster 2, and log inwith username service and password Mi@Dim7T.

c. Type the following command to connect to the VPlexcli, and log in withusername 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 upcluster 2 than the one that was used for cluster 1.

2. Remove the red service cable that hangs inside cluster 2’s cabinet, and use thecable to connect your laptop to the cluster’s management server as shown inFigure 41.


Setting up VPLEX













ipconfig


ping 128.221.252.2



zep-009b





Setting up VPLEX





PuTTY

Type:128.221.252.2

(default)

(default)


SSH protocolversion

putty_ssh


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 inFigure 44) to 20000. (This allows you to read long output in a standard-sizePuTTY session window.)


b. If you want to save the session output to a log file:



scrollback

Set to 20000

i.

ii.

iii.



Type a name in the Log file name field (shown in Figure 45).


Setting up VPLEX



17. On the PuTTY Configuration window, click Open to establish a connection to themanagement 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 theVPlexcli process started:


19. Type the following command to change the hostname:



where <hostname> is a name for the management server, such as Cluster2. Thisname replaces the default name (service) in the shell prompt the next time youopen a PuTTY session to the management server


ping 128.221.252.67 -c 5


putty_log

All session output

File name


Setting up VPLEX


Figure 46 Director A-side addresses







• If you want to leave your laptop connected to the management server, go to“Task 17: Launch the EZ-Setup wizard” on page 80.



exit



• If you are connecting your laptop to the network, set it to an IP address on thenetwork.

• 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).

Zep-056a

128.221.252.68128.221.252.67


128.221.252.70128.221.252.69


128.221.252.72128.221.252.71


128.221.252.74128.221.252.73



Dual-enginecluster

Quad-enginecluster


Setting up VPLEX

b. Verify that PuTTY or other Telnet/SSH client is installed on the device, andinstall it if necessary.




29. Select Window in the Category list, and set Lines of scrollback (shown inFigure 48) to 20000. (This allows you to read long output in a standard-sizePuTTY session window.)


PuTTY3

Type the address of thepublic Ethernet port onthe management serverin the second cluster you are configuring


(default)

(default)

VPLEX serviceVPLEX Cluster 1

scrollback

Set to 20000


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 cangrow quite large.

Note: The log file saves data from the current PuTTY session. Any time you open a newsession, you must repeat this step if you want to log the output for that session.







putty_log

All session output

File name


Setting up VPLEX

Task 17: Launch theEZ-Setup wizard

The setup wizard performs several tasks to set up a VPLEX implementation, based ona series of prompts for user-entered information. Refer to the EMC VPLEXPre-installation Configuration Worksheet as you respond to the prompts





Type the following command from the VPlexcli prompt, to display the softwareversions:

version -a













Setting up VPLEX



To open a new Linux shell session, leave the VPlexcli session open, and follow step 28on page 78 through step 32 on page 79.

For ease of identification, many of the remaining tasks include one of the followingicons: .




director_count=<n>






1. Ping switch A:

ping 128.221.252.66

2. Ping switch B:

ping 128.221.253.66







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





Setting up VPLEX

Output example:



Vendor EMC 452

Use unclaimed 452

Capacity total 271G






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.





where:









Setting up VPLEX


cluster status


Output example:










where:




Type Use






Setting up VPLEX












Command example:






Output example:





Note: This exits the VPlexcli session and leaves you with a second Linux shell session.


Setting up VPLEX


Output example:





Output example:







set enabled true

ls

Output from ls:




test






To configure a weekly SYR job, type the commands in the followingsteps. Set the same schedule that is set on cluster 1.




Setting up VPLEX

where:





scheduleSYR list

Output example:



syrcollect
















Setting up VPLEX



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, 1–4, numbered from the bottom up.






COMSCSI 0x5000144250014d40 A4-FC00


Type the following command to enable all front-end ports in the cluster:







Task 31: Enable theWAN ports

1. Type the following command from the VPlexcli prompt, to enableall WAN COM ports in the cluster:

set /**/*4-FC0[2-3]::enabled true

2. Type the following command to display all director ports in thecluster:

ll /engines/engine-2-*/**/ports

In the output, verify that all ports numbered A4-FC02, A4-FC03, B4-FC02, orB4-FC03 have a port status of up.


Setting up VPLEX

Task 32: Set up ESRSif necessary

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

Task 33: Open aVPlexcli session oncluster 1

Several of the remaining tasks require moving back and forth between VPlexclisessions 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 PuTTYsession:

◆ 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 tomanagement 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 asshown in Figure 40 on page 63.

4. Click Open to establish a session to management server 1, and log in withusername service and password Mi@Dim7T.

5. From the Linux shell prompt, type the following command to connect to theVPlexcli:



Task 34: Verify thedate and time onboth clusters

1. From the VPlexcli prompt on management server 1, type thefollowing command to display the date and UTC time:

date

Output example:

Tue Feb 16 19:07:58 UTC 2010

2. Repeat step 1 on management server 2.

3. or If the UTC are not synchronized between themanagement servers (taking into account the few seconds it took between steps 1and 2), type the following command on the management server you want tochange:

sudo /bin/date -s "<date_and_time>”


Setting up VPLEX

where <date_and_time> is in the format shown in the following commandexample:

sudo /bin/date -s "29 Jun 2010 17:19:00”

Task 35: Completethe setup oncluster 1

From the VPlexcli prompt on management server 1, type thefollowing command:

configuration system-setup -m

When the automated configuration is complete, the VPlexcli prompt appears.

Task 36: Enable theWAN ports oncluster 1

1. From the VPlexcli prompt on management server 1, type thefollowing 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 verifythat all ports numbered A4-FC02, A4-FC03, B4-FC02, or B4-FC03 have a portstatus of up:

ll /engines/engine-1-*/**/ports

Task 37: Zone theWAN ports

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

Task 38: Connectcluster 1 to thedirectors in cluster 2

1. From the VPlexcli prompt on management server 1, type thefollowing 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 thedirectors in cluster 2:

ls /engines/engine-2-*/directors

Output example for a dual-engine cluster:

/engines/engine-2-1/directors:director-2-1-A director-2-1-B


Task 39: Connectcluster 2 to thedirectors in cluster 1

1. From the VPlexcli prompt on management server 2, type thefollowing command:

configuration connect-remote-directors

When prompted, type the number of engines in cluster 1.


Setting up VPLEX

2. Type the following command to verify that cluster 2 is connected to all of thedirectors in cluster 1:

ls /engines/engine-1-*/directors

Output example for a dual-engine cluster:



Task 40: Join theclusters

1. Type the following commands to assign an Island ID to theclusters:

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 operationalstatus of ok.

Output example:

Clusters:Name Cluster ID Connected Expelled Operational Status Health--------- ---------- --------- -------- -----------------------------------------------------------------------------------------------------cluster-1 1 true false ok okcluster-2 2 true false ok ok

Islands:Island ID Clusters--------- --------------------1 cluster-1, cluster-2

Task 41: Createlogging volumes

You must create a logging volume on each VPLEX Metro cluster. The volume must belarge enough to contain one bit for every page of distributed storage space(approximately 10 GB of logging volume space for every 320 TB of distributeddevices).

The logging volumes experience much I/O during and after link outages. Therecommended best practice is to stripe each logging volume across many disks forspeed, 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 fullresynchronization of every distributed device in the system.


Setting up VPLEX

To create the logging volumes, you first must claim the storage volumes that will beused, and create extents from those volumes:

1. From the VPlexcli prompt on management server 2, type thefollowing commands to list the storage volumes:

cd /clusters/cluster-<Cluster_ID>/storage-elements/storage-volumes

ll

2. Type the following command to claim the storage volume(s) thatyou will use for the logging volume:


where:




3. 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. 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 loggingvolume.

• -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 smallestelement 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 next128 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

VPlexcli-2

VPlexcli-2

VPlexcli-2

VPlexcli-2


Setting up VPLEX

5. From the VPlexcli prompt on management server 1, repeat steps 1through 4 for cluster 1.

Task 42: Verify thatthe clusters are fullyconnected

1. From the VPlexcli prompt on management server 1, type thefollowing command, and verify that all directors in cluster 2 appear in the output:

ll /engines/engine-2-*/**/directors




2. From the VPlexcli prompt on management server 2, type thefollowing command, and verify that all directors in cluster 1 appear in the output:

ll /engines/engine-1-*/**/directors

Task 43: Verify thecluster status

1. From the VPlexcli prompt on management server 1, type thefollowing command to display the cluster status:

cluster status

In the output, confirm that operational-status is ok and that there are no healthindications.

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 operationalstatus of ok.

Task 44: Verifyback-endconnectivity oncluster 2

From the VPlexcli prompt on management server 2, type the followingcommand:


In the output, confirm that all storage volumes in the cluster have dual paths, and arevisible from all VPLEX directors.

Output example:


This cluster has 0 storage-volumes which are dead or unreachableThis cluster has 0 storage-volumes which do not have dual paths

This cluster has 0 storage-volumes which are not visible from alldirectors


Setting up VPLEX

Task 45: Verifyback-endconnectivity oncluster 1

From the VPlexcli prompt on management server 1, type thefollowing command:


In the output, confirm that all storage volumes in the cluster have dual paths, and arevisible from all VPLEX directors.

Task 46: Exposestorage 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 asingle extent per storage volume, and then use devices to concatenate or stripethese 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. Thebasic steps are the same for either:

◆ To use the GUI, proceed to “If you are using the GUI.”

◆ To use the VPlexcli, proceed to “If you are using the VPlexcli.”

If you are using theGUI

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 publicIP port.

2. Log in with username service and password Mi@Dim7T.

Note: If the security message screen was enabled during system setup, a security messageappears. Read the message, and then click Continue.

3. To begin provisioning and exporting storage, click Provision Storage on the mainscreen 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 upperright corner of the screen. To display documentation and additional resources for the currentVPLEX release, click Help on the task bar.


Setting up VPLEX

If you are using theVPlexcli

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:


where:




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 ofthe storage volume. However, you can create multiple smaller extents (up to 128per 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>


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 tothe 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 specifiedLUNs 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.


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 registered

initiators----------- ------------ ---------------- ----- ----------VMware_view healthy 2 4 4view1 healthy 1311 4 480view2 healthy 10 4 2view3 healthy 11 4 2view4 healthy 10 4 2

Total 5 views, 0 unhealthy.

Task 47: Perform arescan

After provisioning and exporting storage, perform a rescan from the host to verifythat the exported virtual volume is visible.


A

This appendix contains miscellaneous information you will need during theinstallation. The appendix also contains tables to record other information you mightneed.

◆ IP addresses and component IDs................................................................................ 98◆ Internal cabling............................................................................................................ 100◆ Cabinet power connections........................................................................................ 111

Reference

Reference 97

Reference

IP addresses and component IDsThe IP addresses of the VPLEX hardware components are determined by a set offormulae that depend on the internal management network (A or B), the Cluster IPSeed, 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.

Figure 51 Component IP addresses in cluster 1

Management network A addresses

Zep-028_1

FC switch A

128.221.252.42128.221.252.41

128.221.252.40128.221.252.39

128.221.252.38128.221.252.37

128.221.252.36128.221.252.35

128.221.253.42128.221.253.41

128.221.253.40128.221.253.39

128.221.252.34

FC switch B 128.221.253.34

128.221.253.38128.221.253.37

128.221.253.36128.221.253.35

Management network B addresses

Cluster IP Seed = 1Enclosure IDs = engine numbers

Engine 4:Director 4BDirector 4A








Management server

Public Ethernet portCustomer-assigned

Service port128.221.252.2

Mgt B port128.221.253.33

Mgt A port128.221.252.33


Reference

Figure 52 Component IP addresses in cluster 2

Zep-028_2

FC switch A

128.221.252.74128.221.252.73

128.221.252.72128.221.252.71

128.221.252.70128.221.252.69

128.221.252.68128.221.252.67

128.221.253.74128.221.253.73

128.221.253.72128.221.253.71

128.221.252.66

FC switch B 128.221.253.66

128.221.253.70128.221.253.69

128.221.253.68128.221.253.67

Cluster IP Seed = 2Enclosure IDs = engine numbers









Management server

Public Ethernet portCustomer-assigned

Service port128.221.252.2

Mgt B port128.221.253.65

Mgt A port128.221.252.65

Management network A addressesManagement network B addresses

IP addresses and component IDs 99

Reference

Internal cablingThe figures in this section show the various cabling inside a VPLEX cabinet. Thefigures are included here for reference only, because the cables are installed before theunit ships from EMC.

The figures include cable lengths and EMC part numbers, for use in verifying orreplacing a cable.

This section includes the following figures:

Cluster size Cable type Figure

Quad-engine Ethernet Figure 53 on page 101

Serial Figure 54 on page 102

Fibre Channel Figure 55 on page 103

AC power Figure 56 on page 104

Dual-engine Ethernet Figure 57 on page 105




Single-engine Ethernet Figure 61 on page 109





Reference

Quad-engine cluster

Figure 53 Ethernet cabling in a quad-engine cluster

Zep-05_el

Engine 1



Management server

Engine 2

Engine 3

Engine 4

038-

003-

676,

71

in.

038-

003-

685,

37

in.

038-

003-

678,

20

in.

038-

003-

685,

37

in.

038-

003-

678,

20

in.

038-003-679, 20 in.038-003-679, 20 in.

038-003-887, 48 in.038-003-677, 37 in.

038-003-677, 37 in.

Internal cabling 101

Reference

Figure 54 Serial cabling in a quad-engine cluster

Zep-05_sl

Engine1

UPS A

UPS B

Engine 2

Engine 3

Engine 4

038-003-68212 in.

038-003-68212 in.

038-003-68212 in.

038-003-68212 in.

038-003-89440 in.

038-003-89440 in.

038-003-68212 in.

038-003-68212 in.

038-003-68212 in.

038-003-68212 in.


Reference

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 labelsand the “B” side cables have orange labels.

Zep-05_fl

Engine 1



Engine 2

Engine 3

Engine 4

038-003-738, 79 in.(all 16 cables)


Reference

Figure 56 AC power cabling in a quad-engine cluster

Zep-005_acl

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

SPS 1

Engine 2

Engine 1

Engine 4

Engine 3

UPS A

Management server

SPS 2

SPS 3

SPS 4

UPS B




Reference

Dual-engine cluster

Figure 57 Ethernet cabling in a dual-engine cluster

Zep-05_em

Engine 1



Management server

Engine 2

038-

003-

676,

71

in.

038-

003-

676,

71

in.

038-

003-

678,

20

in.

038-003-679, 20 in.038-003-887, 48 in.

038-003-677, 37 in.


Reference

Figure 58 Serial cabling in a dual-engine cluster

Zep-05_sm

Engine1

UPS A

UPS B

Engine 2

038-003-89440 in.

038-003-89440 in.

038-003-68212 in.

038-003-68212 in.

038-003-68212 in.

038-003-68212 in.


Reference

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 labelsand the “B” side cables have orange labels.

Zep-05_fm

Engine 1



Engine 2

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


Reference

Figure 60 AC power cabling in a dual-engine cluster

Zep-005_acm

I

IO

IO

I

IO

IO

SPS 1

Engine 1

Engine 2

UPS A



Management server

SPS 2

UPS B

I


Reference

Single-engine cluster

Figure 61 Ethernet cabling in a single-engine cluster

Figure 62 Serial cabling in a single-engine cluster

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 labeland the “B” side cable has an orange label.

Zep-005_es

Engine 1

Management server

038-

003-

676,

71

in.

038-003-677, 37 in.

Zep-005_ss

Engine 1

038-003-68212 in.

038-003-68212 in.

Zep-005_fs

Engine 1

038-003-737,39 in. (2 cables)


Reference

Figure 64 AC power cabling in a single-engine cluster

Zep-005_acs

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

SPS

Engine 1

Management server


Reference

Cabinet power connections

Figure 65 Power connectors in a VPLEX cabinet

Zep-012

Unused PDP

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

ONI

OFFO

Rear view

OG

OG

OG

OG

OG

OG

OG

OG

OG

OG

OG

OG

Outlet groups

Power distributionpanel (PDP)

Power distributionunit (PDU)

Outlet groupcircuit breaker



The upper PDUs are installedupside-down from the lower PDUs.Therefore, each circuit breaker inthe upper PDUs controls the outletgroup (OG) directly above it, whileeach circuit breaker in the lowerPDUs controls the outlet group directly below it.

The upper PDPs are installed, butare not used in V-Plex configurations.

The upper PDUs are not used in a small (2-director) configuration.

Notes:

Cabinet power connections 111

Reference


Index

Aacclimating to environment 25addresses of hardware components 98

Ccabling, internal

dual-engine cluster 105quad-engine cluster 101single-engine cluster 109

Call Home, configuring 46circuit breakers, PDU 30cluster, defined 16command globbing 39connectivity, back-end, verifying 49

EElement Manager 47ESRS, setting up 50EZ-Setup wizard 42

FFibre Channel ports 26

GGbE ports 26

Hhardware required 20

II/O ports 26IP addresses 98

LLEDs

management server 32SPS 31UPS 31

ll 39

ls 39

Mmeta-volume

creating 44described 20

Ppaging mode, VPlexcli, exiting 39paging through VPlexcli command output 39password, service account 38port roles 26ports, enabling

front-end 50WAN COM 87

power connections to PDUs 111power switches, PDP 30PuTTY, sessions, multiple 43

Ssetup wizard 42software required 21storage, exporting 51SYR, configuring 48

TTLA, determining 45tools needed 21

Uusername, service account 38

Wwizard, EZ-Setup 42


Index


vplex 4.0 installation and setup guide

Documents

emc software

required information

emc corporation trademarks

required software

publication date

new installation

required hardware

required tools