7. VPLEX Local Deployment
7.3 Preliminary Tasks
After the VPLEX has been physically installed into the rack, you will need to verify that your environment is ready for the deployment of the VPLEX. These tasks include the following:
Install the VPLEX Procedure Generator
Review the VPLEX Implementation and Planning Best Practice Guide Review the VPLEX Simple Support Matrix
Review the VPLEX with GeoSynchrony 5.1 Release Notes Review the VPLEX Configuration Guide
Review the ESX Host Connectivity Guide Review the Encapsulate Arrays on ESX Guide
Verify (4) metadata devices are available for VPLEX install
Review the EMC Secure Remote Support Gateway Install Procedure Before moving forward with the configuration of VPLEX, complete all the relevant
worksheets below to ensure all the necessary information to complete the configuration is available. A blank worksheet is provided in Appendix-D – VPLEX Pre-Configuration
Worksheets. Review Chapter 2, Task 1 of the VPLEX GeoSynchrony v5.1 Configuration Guide. The following tables show sample configuration information as an example and should be replaced by actual values from the installation environment.
Table 3: IPv4 Networking Information
Information Additional description Value
Management server IP address
Public IP address for the management server on the customer IP network.
192.168.44.171
Network mask Subnet mask for the management server IP
network.
255.255.255.0
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.
DC1-VPLEX
EMC secure remote support (ESRS) gateway
IP address for the ESRS gateway on the IP network.
192.168.44.254
Table 4: Metadata Backup Information
Information Additional description Value
Day and time to back up the meta-volume
The day and time that the cluster’s 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 5: SMTP details to configure event notifications
Information Additional description Value
Do you want VPLEX to send event notifications?
Sending event notifications allows EMC to act on any issues quickly.
Yes
Note: The remaining information in this table applies only if you specified yes to the previous question.
SMTP IP address of primary connection
SMTP address thru which Call Home emails will be sent. EMC recommends using your ESRS gateway as the primary connection address.
192.168.44.254
First/only recipient’s email address
Email address of a person (generally a customer’s employee) who will receive Call Home notifications.
SMTP IP address for first/only recipient
SMTP address through which the first/only recipient’s email notifications will be sent.
192.168.44.25
Event notification type One or more people can receive email 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.
1
Second recipient’s email address (optional)
Email address of a second person who will receive Call Home notifications.
SMTP IP address for second recipient *
SMTP address through which the second recipient’s email notifications will be sent.
192.168.44.25
Event notification type for second recipient
See description of event notification type for first recipient.
1
Third recipient’s email address (optional)
Email address of a third person who will receive Call Home notifications.
SMTP IP address for third recipient *
SMTP address through which the third recipient’s email notifications will be sent.
192.168.44.25
Event notification type for third recipient
See description of event notification type for first recipient.
Information Additional description Value
Do you want VPLEX to send system reports?
Day or week and time to send system reports. Sending weekly system reports allows EMC to 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.
default
Table 6: SNMP information
Information Additional description Value
Do you want to use SNMP to collect
performance statistics? *
xxx
You can collect statistics such as I/O operations and latencies, as well as director memory, by issuing SNMP GET, GET-NEXT, or GET-BULK requests.
No
Community string (if you specified yes above). private
Table 7: Certificate Authority (CA) and Host Certificate information
Information Additional description Value
CA certificate lifetime How many years the cluster's self-signed CA certificate should remain valid before expiring.
5
CA certificate key passphrase
VPLEX uses self-signed certificates for ensuring secure communication between VPLEX Metro clusters. This passphrase is used during
installation to create the CA certificate necessary for this secure communication.
dc1-vplex
Host certificate lifetime How many years the cluster's host certificate should remain valid before expiring.
2
Host certificate key passphrase
This passphrase is used to create the host certificates necessary for secure communication between clusters.
dc1-vplex
Table 8: Product Registration Information
Information Additional description Value
Company site ID number (optional)
EMC-assigned identifier used when the VPLEX cluster is deployed on the ESRS server. The EMC customer engineer or account executive can provide this ID.
12345678
Company name CompanyName
Company contact First and last name of a person to contact. First Last
Contact’s business email address
Contact’s business phone number
xxx-xxx-xxxx
Contact’s business address
Street, city, state/province, ZIP/postal code, country.
123 Main Street, City, State, 12345-6789
Method used to send event notifications
Method by which the cluster will send event messages to EMC.
_X_ 1. ESRS _X_ 2. Email
Remote support method Method by which the EMC Support Center can access the cluster.
_X_ 1. ESRS _X_ 2. WebEx
Table 9: VPLEX Metro IP WAN Configuration Information
Information Additional description Value
Local director
discovery configuration details (default values work in most
installations)
Class-D network discovery address 224.100.100.100
Discovery port 10000
Listening port for communications between clusters
(Traffic on this port must be allowed through the network)
11000
Attributes for Cluster 1 Port Group 0
Class-C subnet prefix for 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.
192.168.11.0
Subnet mask 255.255.255.0
Cluster address (use Port Group 0 subnet prefix)
192.168.11.251
Gateway for routing configurations (use Port Group 0 subnet prefix)
192.168.11.1
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
Note: jumbo frames are supported.
1500
Port 0 IP address for director 1-1-A 192.168.11.35
Port 0 IP address for director 1-1-B 192.168.11.36
Attributes for Cluster 1 Port Group 1
Class-C subnet prefix for 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.
10.6.11.0
Information Additional description Value
Cluster address (use Port Group 1 subnet prefix)
10.6.11.251
Gateway for routing configurations (use Port Group 1 subnet prefix)
10.6.11.1
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
Note: jumbo frames are supported.
1500
Port 1 IP address for director 1-1-A 10.6.11.35
Port 1 IP address for director 1-1-B 10.6.11.36
VPLEX Metro supports the VPLEX Witness feature, which is implemented through the Cluster Witness function.
If the inter-cluster network is deployed over Fibre Channel, use separate, unique physical links from other management traffic links.
Table 10: Cluster Witness Configuration Information
Information Additional description Value
Account and password for to log into ESX server where Cluster Witness Server VM is deployed
This password allows you to log into the Cluster Witness Server VM.
username password
Host certificate passphrase for the Cluster Witness certificate
dc1-vplex
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
255.255.255.0
IP Address for ESX server where Cluster Witness Server guest VM is deployed
192.168.34.100
Cluster Witness Server Guest VM Class-C subnet mask
255.255.255.0
Cluster Witness Server Guest VM IP Address 192.168.34.200
Public IP address for management server in Cluster 1
192.168.44.171
Public IP address for management server in Cluster 2
192.168.44.172
Cluster Witness functionality requires these protocols to be enabled by the firewalls
Any firewall between the Cluster Witness Server and the management servers need to allow traffic per the following protocols and ports.
IKE UDP port 500
ESP IP protocol number 50 IP protocol number 51
configured on the
management network NAT Traversal in the IKE (IPsec NAT-T) UDP port 4500