EMC® VPLEX™
With GeoSynchrony 5.0

Pre-configuration Worksheet
P/N 300-010-518
REV A00-06

This worksheet identifies information that should be collected before configuring a VPLEX
implementation, to help ensure a smooth and efficient procedure.
 Introduction.......................................................................................................................2
 Information for Cluster 1.................................................................................................3
 ..............................................................................................................................................9
 Pre-configuration Information for Cluster Witness...................................................17

1
Introduction

Introduction
This document is a supplement to the EMC VPLEX with GeoSynchrony 5.0 Configuration Guide,
and is provided in Microsoft Word format to provide the ability for anyone with Word to type
the information into the tables. Complete the worksheet prior to starting the VPLEX setup
procedure described in the Configuration Guide.
The information collection includes some or all of the following for each cluster:
 IP (IPv4 only) networking information for:
o VPLEX management interfaces
o EMC secure remote support gateway
 Schedule for metadata backup
 Optional authentication directory service information (LDAP or Active Directory)
 SMTP details to configure event notifications
 SNMP information for performance statistics
 Certificate Authority (CA) and host certificate information
 Product registration information to initiate your EMC support services
 VPLEX Geo only: A worksheet for IP WAN configuration information
 VPLEX Metro or VPLEX Geo only: A worksheet for Cluster Witness (VPLEX Witness)
configuration information

2
 Information for Cluster 1

Information for Cluster 1

Cluster 1 is the only cluster in a VPLEX Local implementation or the first cluster in a VPLEX Metro or
VPLEX Geo implementation. If this cluster will be configured in a VPLEX Geo configuration, fill in
this information and, for the EMC installation team, the tables starting on page Error: Reference
source not found.

Table 1 VPLEX implementation

Implementation type
___ VPLEX Local
___ VPLEX Metro
___ VPLEX Geo

Table 2 IP networking details for Cluster 1

Information Additional description Value

Management server IP Public IP address for the management server on
address the customer IP network.
Gateway IP address of the gateway used by the
management server.
Network mask Subnet mask for the management server IP
network.
Hostname Hostname for the management server. Once
configured, this name replaces the default name
(service) in the shell prompt each time you open
an SSH session to the management server.
EMC secure remote IP address for the ESRS gateway on the IP
support (ESRS) gateway network.

Table 3 Authentication directory service information for Cluster 1 (optional)

The information in Table 3 is needed only if you are configuring the VPLEX cluster for connection to a
Lightweight Directory Access Protocol (LDAP) or Active Directory (AD) server.

If you want to set up the cluster for LDAP/AD, you can do it during the EZ-Setup procedure, or later
through VPlexcli commands (as described in the VPLEX CLI Guide).

Information Additional description Value

Authentication server IP address for the LDAP/Active Directory server
address
Port to be used for (Default port = 389)
Transport Layer Security
(TLS)
Port to be used for (Default port = 636)
Secured Socket Layer
(SSL)
Authentication server
name a
3
Information for Cluster 1
Information
Base distinguished name
Bind distinguished name
Password for bind
distinguished name
Principal to map to the
VPLEX management
server
a. Necessary if the connection between the VPLEX management server and the authentication server is going over SSL
channel.
Table 4 Event notification information for Cluster 1
Information
Do you want VPLEX to
send event notifications?
Note: The remaining information in this table applies only if you specified yes to the previous question.
SMTP IP address of
primary connection
SMTP IP address for
failover connection
(optional)
SMTP IP address for
additional failover
connection (optional)
SMTP IP address for
additional failover
connection (optional)
First/only recipient’s email
address
SMTP IP address for
first/only recipient
Additional description Value
A sequence of relative distinguished names
connected by commas.
Example:
dc=security,dc=orgName,dc=companyName,
dc=com
A sequence of relative distinguished names
connected by commas.
Example:
cn=Administrator, dc=security,dc=orgName,
dc=companyName,dc=com
A sequence of relative distinguished names
connected by commas.
Example: ou=people,dc=security,dc=orgName,
dc=companyName,dc=com
Additional description Value
Sending event notifications allows EMC to act on Yes or no:
any issues quickly.
Address thru which Call Home emails will be
sent. EMC recommends using your ESRS
gateway as the primary connection address.
Failover connections are attempted, in order,
when the primary and any previous failover
attempts have failed. The connection must go to
EMC through a different SMTP server than the
primary connection.
Email address of a person (generally a
customer’s employee) who will receive Call
Home notifications.
SMTP address through which the first/only
recipient’s email notifications will be sent.
4

Information
Event notification type for
first recipient
Second recipient’s email
address (optional)
SMTP IP address for
second recipient *
Event notification type for
second recipient
Third recipient’s email
address (optional)
SMTP IP address for third
recipient *
Event notification type for
third recipient
Do you want VPLEX to
send system reports?
Table 5 SNMP information for performance statistics for Cluster 1
Information
Do you want to use
SNMP to collect
performance statistics? *
xxx
* The supported statistics are listed in the VPLEX CLI Guide.
Information for Cluster 1
Additional description Value
One or more people can receive email 1, 2, 3, or 4:
notifications when events occur.
Notification types:
1. On Success or Failure - Sends an email
regardless of whether the email notification to
EMC succeeded.
2. On Failure - Sends an email each time an
attempt to notify EMC has failed.
3. On All Failure - Sends an email only if all
attempts to notify EMC have failed.
On Success - Sends an email each time EMC is
successfully sent an email notification.EMC
recommends distributing connections over
multiple SMTP servers for better availability.
These SMTP v4 IP addresses can be different
from the addresses used for event notifications
sent to EMC.
Email address of a second person who will
receive Call Home notifications.
SMTP address through which the second
recipient’s email notifications will be sent.
See description of event notification type for first 1, 2, 3, or 4:
recipient.
Email address of a third person who will receive
Call Home notifications.
SMTP address through which the third recipient’s
email notifications will be sent.
See description of event notification type for first 1, 2, 3, or 4:
recipient.
Day of week and time to send system reports. (VPLEX specifies a random
Sending weekly system reports allows EMC to day and time as a default)
communicate known configuration risks, as well
as newly discovered information that can
optimize or reduce risks.
Note that the connections for system reports are
the same connections used for event
notifications.
Additional description Value
You can collect statistics such as I/O operations Yes or no:
and latencies, as well as director memory, by
issuing SNMP GET, GET-NEXT, or GET-BULK
requests.
Community string (if you specified yes above). (Default = private)
5
Information for Cluster 1

Table 6 Certificate Authority (CA) and host certificate information for Cluster 1

Information Additional description Value

CA certificate lifetime How many years the cluster's self-signed CA Valid values are 1, 2, 3, 4,
certificate should remain valid before expiring. or 5 (default):
CA certificate key VPLEX uses self-signed certificates for ensuring Must be at least eight
passphrase secure communication between VPLEX Metro characters (including
clusters. This passphrase is used during spaces):
installation to create the CA certificate necessary
for this secure communication.
Host certificate lifetime How many years the cluster's host certificate Valid values are 1 or 2
should remain valid before expiring. (default):

Host certificate key This passphrase is used to create the host Must be at least eight
passphrase certificates necessary for secure communication characters (including
between clusters. spaces):

Table 7 Meta-volume backup schedule

Information Additional description Value

Day and time to back up The day and time that the cluster’s meta-volume
the meta-volume will be backed up to a remote storage volume on
a back-end array (which will be selected during
the cluster setup procedure) .

Table 8 Product registration information for Cluster 1

Information Additional description Value

Company site ID number Customer-provided identifier.
(optional)
Company name
Company contact First and last name of a person to contact.
Contact’s business email
address
Contact’s business phone
number
Contact’s business Street, city, state/province, ZIP/postal code,
address country.
Method used to send Method by which the cluster will send event __ 1. ESRS
event notifications messages to EMC. __ 2. Email
__ 3. None (notifications
are not configured)
Remote support method Method by which the EMC Support Center can __ 1. ESRS
access the cluster. __ 2. WebEx

CAUTION: You must register the VPLEX cluster to initiate EMC support services.

6
 Information for Cluster 1

Pre-installation information for IP WAN COM connections

The information in Table 9 is used by the EMC installation team to configure a VPLEX Geo
implementation that is set up for intercluster communication over IP. The inter-cluster com
traffic should be on a different network than the management traffic and must be on
different subnets than the management network.
Note the following:
 It is not necessary to use VLANs. If they are used, however, all ports in VPLEX port-group
0 must be assigned to the same VLAN, and all ports in VPLEX port-group 1 must be
assigned to the same VLAN. Also, the VLAN used for port-group 0 must be different than
the VLAN used for port-group 1.
 IP WAN connections in VS2 engines are optical 10 Gb/s Ethernet. These connections do not
automatically negotiate down to slower speeds, which means they must be connected to 10
Gb/s equipment (such as switches or routers). The connected equipment can then negotiate
down to slower connection speeds if required.
 The IP WAN ports do not support trunking.
The IP subnets are used by separate port groups (port 0 and port 1) that have static IP
addresses assigned to them. The following chart shows the number of static IP addresses
that must be available for your EMC installation team.
Number of static addresses required
Cluster size Per subnet Per cluster
Single-engine 3 6
Dual-engine 5 10
Quad-engine 9 18

Table 9 VPLEX Geo only: IP WAN networking information for Cluster 1

See “Pre-installation information for IP WAN COM connections,” which follows this table.

Information Additional description Value

Local director Class-D network discovery address (Default = 224.100.100.100)
discovery configuration
details (default values
work in most Discovery port (Default = 10000)
installations)

Listening port for communications between (Default = 11000)

clusters
(Traffic on this port must be allowed through the
network)
Attributes for Cluster 1 Class-C subnet prefix for Port Group 0.
Port Group 0 The IP subnet must be different than the one
used by the management servers and different
from the Port Group 1 subnet in Cluster 1.
Subnet mask

7
Information for Cluster 1

Information Additional description Value

Cluster address (use Port Group 0 subnet
prefix)
Gateway for routing configurations
(use Port Group 0 subnet prefix)
MTU: (Default = 1500)
The size must be set to the same value for Port
Group 0 on both clusters.
Also, the same MTU must be set for Port Group
1 on both clusters
Port 0 IP address for director 1-1-A

Port 0 IP address for director 1-1-B

Port 0 IP address for director 1-2-A (if present)

Port 0 IP address for director 1-2-B (if present)

Port 0 IP address for director 1-3-A (if present)

Port 0 IP address for director 1-3-B (if present)

Port 0 IP address for director 1-4-A (if present)

Port 0 IP address for director 1-4-B (if present)

Attributes for Cluster 1 Class-C subnet prefix for Port Group 1.

Port Group 1 The IP subnet must be different than the one
used by the management servers and different
from the Port Group 1 subnet in Cluster 2.
Subnet mask

Cluster address (use Port Group 1 subnet

prefix)
Gateway for routing configurations
(use Port Group 1 subnet prefix)
MTU: (Default = 1500)
The size must be set to the same value for Port
Group 1 on both clusters.
Also, the same MTU must be set for Port Group
0 on both clusters
Port 1 IP address for director 1-1-A

Port 1 IP address for director 1-1-B

Port 1 IP address for director 1-2-A *

8
 Information for Cluster 1

Information Additional description Value

Port 1 IP address for director 1-2-B *

Port 1 IP address for director 1-3-A *

Port 1 IP address for director 1-3-B *

Port 1 IP address for director 1-4-A *

Port 1 IP address for director 1-4-B *

Proxy addresses Address for Cluster 1

Address for director 1-1-A port A2-XG00

Address for director 1-1-B port B2-XG00

Address for director 1-2-A port A2-XG00 *

Address for director 1-2-B port B2-XG00 *

Address for director 1-3-A port A2-XG00 *

Address for director 1-3-B port B2-XG00 *

Address for director 1-4-A port A2-XG00 *

Address for director 1-4-B port B2-XG00 *

* If present.

9
Information for Cluster 2

Information for Cluster 2

Cluster 2 is the second cluster in a VPLEX Metro or VPLEX Geo configuration.
Note that you can re-use most of the information from Cluster 1 in configuring Cluster 2.
Table 10 IP networking details for Cluster 2

Information Additional description Value

Management server IP Public IP address for the management server on
address the customer IP network.
Gateway IP address of the gateway used for configuring
the management server.
Network mask Subnet mask for the customer IP network.

ESRS Gateway IP address for the gateway on the customer IP

network.
Hostname Hostname for the management server. Once
configured, this name replaces the default name
(service) in the shell prompt each time you open
an SSH session to the management server.

Table 11 Authentication directory service information for Cluster 2 (optional)

VPLEX offers Lightweight Directory Access Protocol (LDAP) or Active Directory for an
authentication directory service. This information is needed only if you are configuring the
VPLEX cluster for connection to an LDAP/AD server.
If you want to set up the cluster for LDAP, you can do it during the EZ-Setup procedure, or later
through VPlexcli commands. The VPLEX CLI Guide provides more information on the LDAP
parameters.
Information Additional description Value
Authentication server IP address for the LDAP/Active Directory server
address
Port to be used for (Default port = 389)
Transport Layer Security
(TLS)
Port to be used for (Default port = 636)
Secured Socket Layer
(SSL)
Authentication server
name a
Base distinguished name A sequence of relative distinguished names
connected by commas.
Example:
dc=security,dc=orgName,dc=companyName,
dc=com

10

Information
Bind distinguished name
Password for bind
distinguished name
Principal to map to the
VPLEX management
server
a. Necessary if the connection between the VPLEX management server and the authentication server is going over SSL
channel.
Table 12 Event notification information for Cluster 2
Information
Do you want VPLEX to
send event notifications?
Note: The remaining information in this table applies only if you specified yes to the previous question.
SMTP IP address of
primary connection
SMTP IP address for
failover connection
(optional)
SMTP IP address for
additional failover
connection (optional)
SMTP IP address for
additional failover
connection (optional)
First/only recipient’s email
address
SMTP IP address for
first/only recipient
Information for Cluster 2
Additional description Value
A sequence of relative distinguished names
connected by commas.
Example:
cn=Administrator, dc=security,dc=orgName,
dc=companyName,dc=com
A sequence of relative distinguished names
connected by commas.
Example: ou=people,dc=security,dc=orgName,
dc=companyName,dc=com
Additional description Value
Sending event notifications allows EMC to act on Yes or no:
any issues quickly.
SMTP address thru which Call Home emails will
be sent. EMC recommends using your ESRS
gateway as the primary connection address.
Failover connections are attempted, in order,
when the primary and any previous failover
attempts have failed. This connection must go to
EMC through a different SMTP server than the
primary connection.
Email address of a person (generally a
customer’s employee) who will receive Call
Home notifications.
SMTP address through which the first/only
recipient’s email notifications will be sent.
11
Information for Cluster 2
Information
Event notification type
Second recipient’s email
address (optional)
SMTP IP address for
second recipient *
Event notification type for
second recipient
Third recipient’s email
address (optional)
SMTP IP address for third
recipient *
Event notification type for
third recipient
Do you want VPLEX to
send system reports?
Table 13 SNMP information for performance statistics for Cluster 2
Information
Do you want to use
SNMP to collect
performance statistics? *
xxx
* The supported statistics are listed in the VPLEX CLI Guide.
Additional description Value
One or more people can receive email 1, 2, 3, or 4:
notifications when events occur.
Notification types:
1. On Success or Failure - Sends an email
regardless of whether the email notification to
EMC succeeded.
2. On Failure - Sends an email each time an
attempt to notify EMC has failed.
3. On All Failure - Sends an email only if all
attempts to notify EMC have failed.
On Success - Sends an email each time EMC is
successfully sent an email notification.EMC
recommends distributing connections over
multiple SMTP servers for better availability.
These SMTP v4 IP addresses can be different
from the addresses used for event notifications
sent to EMC.
Email address of a second person who will
receive Call Home notifications.
SMTP address through which the second
recipient’s email notifications will be sent.
See description of event notification type for first 1, 2, 3, or 4:
recipient.
Email address of a third person who will receive
Call Home notifications.
SMTP address through which the third recipient’s
email notifications will be sent.
See description of event notification type for first 1, 2, 3, or 4:
recipient.
Day or week and time to send system reports. (VPLEX specifies a random
Sending weekly system reports allows EMC to day and time as a default)
communicate known configuration risks, as well
as newly discovered information that can
optimize or reduce risks.
Note that the connections for system reports are
the same connections used for event
notifications.
Additional description Value
You can collect statistics such as I/O operations Yes or no:
and latencies, as well as director memory, by
issuing SNMP GET, GET-NEXT, or GET-BULK
requests.
Community string (if you specified yes above). (Default = private)
12
 Information for Cluster 2

Table 14 Certificate Authority (CA) and host certificate information for Cluster 2

Information Additional description Value

CA certificate lifetime How many years the cluster's self-signed CA Valid values are 1, 2, 3, 4,
(Certificate Authority) certificate should remain or 5 (default):
valid before expiring.
CA certificate key VPLEX uses self-signed certificates for ensuring (Must be the same
passphrase secure communication between VPLEX Metro passphrase that was set on
clusters. This passphrase is used during Cluster 1)
installation to create the CA certificate necessary
for this secure communication.
Host certificate lifetime How many years the cluster's host certificate Valid values are 1 or 2
should remain valid before expiring. (default):

Host certificate key This passphrase is used to create the host Must be at least eight
passphrase certificates necessary for secure communication characters (including
between clusters. spaces):

Table 15 Meta-volume backup schedule

Information Additional description Value

Day and time to back up The day and time that the cluster’s meta-volume (Should be the same time
the meta-volume will be backed up to a remote storage volume on as set for Cluster 1)
a back-end array (which will be selected during
the cluster setup procedure) .

Table 16 Product registration information for Cluster 2

Information Additional description Value

Company site ID number Customer-provided identifier.
(optional)
Company name
Company contact First and last name of a person to contact.
Contact’s business email
address
Contact’s business phone
number
Contact’s business Street, city, state/province, ZIP/postal code,
address country.
Method used to send Method by which the cluster will send event __ 1. ESRS
event notifications messages to EMC. __ 2. Email
__ 3. None (notifications
are not configured)
Remote support method Method by which the EMC Support Center can __ 1. ESRS
access the cluster. __ 2. WebEx

CAUTION: You must register the VPLEX cluster in order to receive support from EMC.

13
Information for Cluster 2

Table 17 VPLEX Geo only: IP WAN networking information for Cluster 2

See “Pre-installation information for IP WAN COM connections” on page 7.

Information Additional description Value

Local director Class-D network discovery address (Default = 224.100.100.100)
discovery configuration
details (default values
work in most Discovery port (Default = 10000)
installations)

Listening port for communications between (Default = 11000)

clusters
(Traffic on this port must be allowed through the
network)
Attributes for Cluster 2 Class-C subnet prefix for Port Group 0.
Port Group 0 The IP subnet must be different than the one
used by the management servers and different
from the Port Group 1 subnet in Cluster 2.
Subnet mask

Cluster address (use Port Group 0 subnet

prefix)
Gateway for routing configurations
(use Port Group 0 subnet prefix)
MTU:
The size must be set to the same value for Port
Group 0 on both clusters.
Also, the same MTU must be set for Port Group
1 on both clusters
Port 0 IP address for director 2-1-A

Port 0 IP address for director 2-1-B

Port 0 IP address for director 2-2-A (if present)

Port 0 IP address for director 2-2-B (if present)

Port 0 IP address for director 2-3-A (if present)

Port 0 IP address for director 2-3-B (if present)

Port 0 IP address for director 2-4-A (if present)

Port 0 IP address for director 2-4-B (if present)

14
 Information for Cluster 2

Information Additional description Value

Attributes for Cluster 2 Class-C subnet prefix for Port Group 1.
Port Group 1 The IP subnet must be different than the one
used by the management servers and different
from the Port Group 1 subnet in Cluster 1.
Subnet mask

Cluster address (use Port Group 1 subnet

prefix)
Gateway for routing configurations
(use Port Group 1 subnet prefix)
MTU:
The size must be set to the same value for Port
Group 1 on both clusters.
Also, the same MTU must be set for Port Group
0 on both clusters
Port 1 IP address for director 2-1-A

Port 1 IP address for director 2-1-B

Port 1 IP address for director 2-2-A *

Port 1 IP address for director 2-2-B *

Port 1 IP address for director 2-3-A *

Port 1 IP address for director 2-3-B *

Port 1 IP address for director 2-4-A *

Port 1 IP address for director 2-4-B *

Proxy addresses Address for Cluster 2

Address for director 2-1-A port A2-XG00

Address for director 2-1-B port B2-XG00

Address for director 2-2-A port A2-XG00 *

Address for director 2-2-B port B2-XG00 *

Address for director 2-3-A port A2-XG00 *

Address for director 2-3-B port B2-XG00 *

15
Information for Cluster 2

Information Additional description Value

Address for director 2-4-A port A2-XG00 *

Address for director 2-4-B port B2-XG00 *

* If present.

16
Pre-configuration Information for Cluster Witness
VPLEX Metro and VPLEX Geo support the VPLEX Witness feature, which is implemented
through the Cluster Witness function.
If the intercluster network is deployed over Fibre Channel, use separate, unique physical links
from other management traffic links.
Table 18 Cluster Witness Configuration Information

Information Additional description Value

Account and password for This password allows you to log into the Cluster
to log into ESX server Witness Server VM.
where Cluster Witness
Server VM is deployed
Host certificate Must be at least eight
passphrase for the characters (including spaces):
Cluster Witness certificate

Cluster Witness requires
management IP network
to be separate from inter-
cluster network
Class-C subnet mask for the ESX server where
Cluster Witness Server guest VM is deployed
IP Address for ESX server where Cluster
Witness Server guest VM is deployed
Cluster Witness Server Guest VM Class-C
subnet mask
Cluster Witness Server Guest VM IP Address

Public IP address for management server in

Cluster Witness
functionality requires
these protocols to be
enabled by the firewalls
configured on the
management network
Cluster 1
Public IP address for management server in
Cluster 2
Any firewall between the Cluster Witness Server IKE UDP port 500
and the management servers need to allow
traffic per the following protocols and ports. ESP IP protocol number 50
IP protocol number 51
NAT Traversal in the IKE
(IPsec NAT-T) UDP port
4500

17