VPLEXâ„¢ Networking Best Practices ... H13552 Best Practices VPLEX Networking Best Practices...

download VPLEXâ„¢ Networking Best Practices ... H13552 Best Practices VPLEX Networking Best Practices Implementation

of 14

  • date post

    18-Mar-2020
  • Category

    Documents

  • view

    0
  • download

    0

Embed Size (px)

Transcript of VPLEXâ„¢ Networking Best Practices ... H13552 Best Practices VPLEX Networking Best Practices...

  • H13552

    Best Practices

    VPLEX™ Networking Best Practices Implementation Planning and Best Practices

    Abstract This White Paper provides an overview of VPLEX networking. This document includes topics for internal IP networks, management network, WAN COM for Metro as well as VPN for Metro and Witness.. It provides guidance for VS2 and VS6 hardware platforms.

    April 2019

  • Revisions

    2 VPLEX™ Networking Best Practices | H13552

    Revisions Date Description

    April 2019 Revision 3

    Acknowledgements This paper was produced by the following:

    Author: VPLEX CSE Team

    VPLEX_CSE_TEAM@emc.com

    The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license. Copyright © April 2019 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. [5/16/2019] [Best Practices] [H13552]

    mailto:VPLEX_CSE_TEAM@emc.com

  • Table of contents

    3 VPLEX™ Networking Best Practices | H13552

    Table of contents Revisions............................................................................................................................................................................. 2

    Acknowledgements ............................................................................................................................................................. 2

    Table of contents ................................................................................................................................................................ 3

    Executive summary ............................................................................................................................................................. 4

    Audience ....................................................................................................................................................................... 4

    Document Organization ................................................................................................................................................ 4

    1 Internal Networks.......................................................................................................................................................... 5

    1.1 Description & Requirement ................................................................................................................................. 5

    1.2 Management Network and Internal Management VPN ...................................................................................... 5

    2 VPLEX Metro WAN Cluster Connectivity ..................................................................................................................... 6

    2.1 VPLEX Metro Fibre Channel WAN Cluster Connectivity ................................................................................... 6

    2.1.1 Requirements ..................................................................................................................................................... 6

    2.2 Metro over IP (10Gb/E) .................................................................................................................................... 10

    2.2.1 Requirements ................................................................................................................................................... 10

    2.3 VPLEX Metro IP WAN Cluster Connectivity ..................................................................................................... 11

    3 Rule Sets .................................................................................................................................................................... 13

  • Executive summary

    4 VPLEX™ Networking Best Practices | H13552

    Executive summary This VPLEX™ Networking Best Practices document covers VPLEX network requirements for WAN communications (both Fibre Channel and Ethernet) for cluster to cluster communications over distance in a VPLEX Metro configuration as well as providing an overview for the internal communication layer between directors and management server to directors within the cluster. This document also covers the VPN configuration between management servers and the Cluster Witness Server (CWS).

    Note: The network best practices section does not cover host cluster network considerations as VPLEX does not provide solutions directly for host stretch cluster networks. Host stretch clusters may require layer 2 network connectivity so please refer to host requirements and network vendor products that provide the ability to separate cluster nodes across datacenters. Even though this document does not provide for host cluster network requirements they are still an integral part of the overall solution.

    Audience These technical notes are for Dell-EMC field personnel and partners and customers who will be configuring, installing, and supporting VPLEX. An understanding of these technical notes requires an understanding of the following:

    • SAN technology and network design • Fiber Channel block storage concepts • VPLEX concepts and components

    Document Organization This technical note is one of a set of documents that supersede the monolithic Implementation Planning and Best Practices for Dell-EMC VPLEX Technical Notes document that had previously been available. It is intended to provide more concise, per-topic information that will be easier to maintain and keep up-to-date.

    All documents are available on SolVe Desktop and http://support.emc.com.

    The following list represents the technical note best practice documents:

    • Dell-EMC VPLEX Overview and General Best Practices • Dell-EMC VPLEX SAN Connectivity • Dell-EMC VPLEX Host Multipathing • Dell-EMC VPLEX Networking • Dell-EMC VPLEX and RecoverPoint Interoperability • Dell-EMC VPLEX Data Mobility and Migrations • Dell-EMC VPLEX Upgrades

    http://support.emc.com/

  • Internal Networks

    5 VPLEX™ Networking Best Practices | H13552

    1 Internal Networks

    1.1 Description & Requirement Within the each VPLEX cluster are two sets of private networks. One set is a redundant internal management IP network between cluster components and the cluster management server. The second set is a redundant internal network which provides director to director communications solely within the VPLEX cluster (intra- cluster). This internal Fibre Channel network (VS2) or InfiniBand network (VS6) is commonly referred to as LOCAL COM. A single-engine cluster simply connects corresponding Local COM ports together with FC/IB cables direct connected. For dual and quad engine VPLEX clusters the LOCAL COM includes two internal use FC or IB switches.

    Note: At no time should any of these internal networks be connected to customer networks.

    1.2 Management Network and Internal Management VPN Each VS2 VPLEX cluster has a single management port located on the management server.

    The VS6 has two management ports, one on MMCS-A and the other on MMCS-B. Both of these ports must be configured and connected to the customer network. MMCS-A is the management port that will be accessed for all management and monitoring purposes.

    MMCS-B must be configured so that processes such as ndu or configuration changes like setting cluster ID during installation can be persisted to MMCS-B or those processes will fail.

    This port provides the connectivity to facilitate the management and configuration of the cluster. For VPLEX Metro, the management port is also utilized for a VPN which extends the internal management networks between all of the cluster components in both clusters and, if installed, the VPLEX Witness.

    Refer the Security Guide for port information and the protocols that need to be allowed on the firewall (both in the outbound and inbound filters).

    The VPLEX Security Configuration Guide is located here: https://support.emc.com/products/29384_VPLEX- Series

    https://support.emc.com/products/29384_VPLEX-Series https://support.emc.com/products/29384_VPLEX-Series

  • VPLEX Metro WAN Cluster Connectivity

    6 VPLEX™ Networking Best Practices | H13552

    2 VPLEX Metro WAN Cluster Connectivity VPLEX Metro connectivity is defined as the communication between clusters in a VPLEX Metro. The two key components of VPLEX Metro communication are FC (FCIP, DWDM) or 10 GigE and VPN between management servers. Please refer to the VPLEX Internal Management VPN section for details. FC WAN is the Fibre Channel connectivity and 10 GigE is the Ethernet connectivity options between directors of each cluster. Choose section that applies to your configuration.

    2.1 VPLEX Metro Fibre Channel WAN Cluster Connectivity FC WAN connectivity for inter-cluster director communication

    2.1.1 Requirements • Latency may be up to 10ms rtt, depending on the use case. Many systems require 5ms rtt or less.

    Please consult the latest VPLEX Simple Support Matrix • Each director’s FC WAN