Interfamily Connectivity

SRDF

Interfamily Connectivity Information

REV 01
May 2017

This document defines the versions of HYPERMAX OS and Enginuity that can make up
valid SRDF replication and SRDF/Metro configurations. In addition, there is information
on the versions that can participate in Non-Disruptive Migration (NDM).
l Introduction............................................................................................................ 2
l SRDF Remote Replication.......................................................................................3
l SRDF/Metro......................................................................................................... 10
l NDM......................................................................................................................13
l Requirements for performing system upgrades..................................................... 14
Interfamily Connectivity

Introduction
The versions of HYPERMAX OS and Enginuity that participate in an SRDF remote
replication configuration, a SRDF/Metro high-availability configuration, or a Non-
Disruptive Migration (NDM) configuration need to be compatible. This document
contains advice on which versions of HYPERMAX OS and Enginuity can participate in
those configurations.

Note

This document covers interfamily connectivity for major releases of HYPERMAX OS

and Enginuity and for their service packs. For the latest connectivity information
including interim releases and information on any hot fixes or ePacks that are required,
refer to Knowledgebase article 303996.

Related documents
The following VMAX All Flash, VMAX3, and VMAX documents contain information on
SRDF.
VMAX All Flash and VMAX3 series:
l EMC VMAX3 Family Product Guide for VMAX 100K, VMAX 200K, VMAX 400K with
HYPERMAX OS
l EMC VMAX All Flash Product Guide for VMAX 250F, 450F, 850F, 950F with
HYPERMAX OS
VMAX series:
l Symmetrix Remote Data Facility (SRDF) Product Guide
All systems:
l FBA environments: EMC Solutions Enabler SRDF Family CLI User Guide
l CKD environments: EMC Mainframe Enablers SRDF Host Component for z/OS
Product Guide

2 SRDF Interfamily Connectivity

 Interfamily Connectivity Information

SRDF Remote Replication

Use this section to determine valid SRDF replication configurations and understand
any limitations associated with those configurations.

Connectivity tables
A SRDF configuration consists of one or more pairs of storage arrays. One array is the
source, and is known as the R1 side. The other array is the target that receives data
from the source array, and is known as the R2 side:

These tables show the valid combinations of HYPERMAX OS or Enginuity that can be
a SRDF pair. Use the table for appropriate the device emulation in use: FBA or CKD.

FBA
Table 1 FBA interfamily connectivity

When R1 runs… R2 can run…

5977.814.786 or later
HYPERMAX OS
5977.1125.1125 5876.309.401 with ePack (if the Service Processor runs Windows 7).
Otherwise 5876.309.196 with ePack .

5977.691.684 or later

5876.309.401 with ePack (if the Service Processor runs Windows 7).
5977.952.892 Otherwise 5876.309.196 with ePack .

5876.288.400 with ePack (if the Service Processor runs Windows 7).
Otherwise, 5876.288.195 with ePack.

5977.691.684 or later
5977.945.890 5876.288.400 with ePack (if the Service Processor runs Windows 7).
Otherwise, 5876.288.195 with ePack.

5977.691.684 or later
5977.814.786 5876.288.400 with ePack (if the Service Processor runs Windows 7).
Otherwise 5876.288.195 with ePack.

5977.691.684 or later
5977.813.785 5876.288.400 with ePack (if the Service Processor runs Windows 7).
Otherwise, 5876.288.195 with ePack.

5977.691.684 or later
5977.811.784
5876.288.195 with ePack

SRDF Remote Replication 3

Interfamily Connectivity

Table 1 FBA interfamily connectivity (continued)

When R1 runs… R2 can run…

5977.691.684 or later
5977.810.784
5876.288.195 with ePack

5977.596.583, with ePack containing fixes to support N-x connectivity,

5977.691.684 or later

5876.286.184.

5977.691.684. In this case, 5977.596.583 requires an ePack containing

fixes to support N-x connectivity.
5977.596.583
5977.596.583

5876.272.177 with ePack containing N-x fixes, or later

5977.952.892

5876.306.401 5876.288.195

5773.184.130 with Proactive ePack, or later

5977.952.892

5876.309.196 5876.288.195

5773.184.130 with Proactive ePack, or later

5977.810.784

5876.288.400 5876.159.102

5773.184.130 with Proactive ePack, or later

5977.813.785 or later

5876.288.195 5876.159.102

5773.184.130 with Proactive ePack, or later

5977.691.684

5977.596.583
5876.286.198
5876.159.102 or later

5773.184.130 with a Proactive ePack, or later

5977.596.583. In this case, 5876.272.177 requires an ePack.

5876.272.177 5876.159.102 or later

5773.184.130 with a Proactive ePack, or later

5876.154.130 or later
5876.269.175
5773.184.130 with Proactive ePack, or later.

5876.154.130 or later
5876.286.174
5773.184.130 with Proactive ePack, or later

5876.154.130 or later
5876.229.145
5773.184.130 with Proactive ePack, or later

4 SRDF Interfamily Connectivity

 Interfamily Connectivity Information

Table 1 FBA interfamily connectivity (continued)

When R1 runs… R2 can run…

5876.154.130 or later
5876.163.105
5773.184.130 with Proactive ePack, or later

5876.159.102 or later
5876.159.102
5773.184.130 with Proactive ePack or later

5876.82.57 5773.184.130 with Proactive ePack, or later

5876.288.195

5876.286.194

5876.272.177

5773.184.130 5876.269.175

5876.268.174

5876.251.161

5876.229.145

CKD
Table 2 CKD interfamily connectivity

When R1 runs… R2 can run…

5977.814.786 or later

VMAX 40K systems: 5876.309.401 with ePack (if the Service

HYPERMAX OS
Processor runs Windows 7). Otherwise 5876.309.196 with ePack .
5977.1125.1125
All other VMAX systems: 5876.288.400 with ePack (if the Service
Processor runs Windows 7). Otherwise, 5876.288.195 with ePack.

5977.813.684 or later

5876.309.401 with ePack (if the Service Processor runs Windows 7).
5977.952.892 Otherwise 5876.309.196 with ePack .

5876.288.400 with ePack (if the Service Processor runs Windows 7).
Otherwise, 5876.288.195 with ePack.

5977.811.784 or later
5977.945.890 5876.288.400 with ePack (if the Service Processor runs Windows 7).
Otherwise, 5876.288.195 with ePack.

5977.811.784 or later
5977.814.786 5876.288.400 with ePack (if the Service Processor runs Windows 7).
Otherwise, 5876.288.195 with ePack.

5977.811.784 or later
5977.813.785
5876.288.195 with ePack

Connectivity tables 5
Interfamily Connectivity

Table 2 CKD interfamily connectivity (continued)

When R1 runs… R2 can run…

5977.811.784 or later
5977.811.784
5876.288.195 with ePack

5977.952.892

5876.309.401 5876.288.195

5773.184.130 with Proactive ePack, or later

5977.952.892

5876.309.196 5876.288.195

5773.184.130 with Proactive ePack, or later

5977.945.890

5876.288.400 5876.159.102

5773.184.130 with Proactive ePack, or later

5977.813.785 or later

5876.288.195 5876.159.102

5773.184.130 with Proactive ePack, or later

5876.159.102 or later
5876.286.194
5773.184.130 with Proactive ePack, or later

5876.159.102 or later
5876.272.177
5773.184.130 with Proactive ePack, or later

5876.154.120 or later
5876.269.175
5773.184.130 with Proactive ePack, or later

5876.159.102
5876.286.174
5773.184.130 with Proactive ePack, or later

5876.159.102 or later
5876.251.161
5773.184.130 with Proactive ePack, or later

5876.159.102 or later with ePack

5876.159.102
5773.184.130 with Proactive ePack, or later

6 SRDF Interfamily Connectivity

 Interfamily Connectivity Information

How to determine valid SRDF configurations

These procedures show how to use Table 1 on page 3 and Table 2 on page 5 to
determine valid configurations for 2-site and 3-site SRDF. Follow the appropriate
procedure.

2 site

Procedure
1. Locate the version of HYPERMAX OS or Enginuity that the R1 side runs in the
When the R1 runs column.
2. The corresponding entries in the R2 can run column show the versions of
HYPERMAX OS and Enginuity that can be on the R2 side. Choose one of those
versions.

For example, the R1 side in FBA configuration runs HYPERMAX OS 5977.952.892.

From Table 1 on page 3 the R2 side can run HYPERMAX OS 5977.691.684 or later,
Enginuity 5876.309.401 with an ePack, or Enginuity 5876.309.196 with an ePack. The
R2 side can also run 5876.288.400 with an ePack or 5876.288.195 with an ePack.

3-site concurrent

Procedure
1. Locate the version of HYPERMAX OS or Enginuity that the R11 site runs in the
When R1 runs column.
2. The corresponding entries in the R2 can run column show the versions of
HYPERMAX OS and Enginuity that can be on the R2 sites. Choose one of those
versions for each R2 side.
The two R2 sides can run different versions of HYPERMAX OS and Enginuity.

For example, the R11 side in a FBA configuration runs HYPERMAX OS 5977.810.784.
From Table 1 on page 3 each R2 side can run HYPERMAX OS 5977.691.684 or later,
or Enginuity 5876.288.195 with an ePack.

How to determine valid SRDF configurations 7

Interfamily Connectivity

3-site cascaded

Procedure
1. Locate the version of HYPERMAX OS or Enginuity that the R1 side runs in the
When R1 runs column.
2. The corresponding entries in the R2 can run column show the versions of
HYPERMAX OS and Enginuty that can run on the R21 side. Choose one of
those versions.
3. Locate the chosen R21 version of HYPERMAX OS or Enginuity in the When R1
runs column.
4. The corresponding entries in the R2 can run column show the versions of
HYPERMAX OS and Enginuity that can be on the R2 side. Choose one of those
versions.

For example, the R1 side in a CKD environment runs HYPERMAX OS 5977.813.785.

Table 2 on page 5 shows that the R21 side can run HYPERMAX OS 5977.811.784 or
later, or Enginuity 5876.288.195 with an ePack.

Assume that the R21 side runs HYPERMAX OS 5977.811.784. Locating the row with
that version in the When R1 runs column of Table 2 on page 5 shows that the R2 side
can run HYPERMAX OS 5977.811.784 or later, or Enginuity 5876.288.195 with an
ePack.

8 SRDF Interfamily Connectivity

 Interfamily Connectivity Information

Limitations
There are some limitations to SRDF communications in these environments:
l 2-site
l Cascaded
l Concurrent
2-site
l R1 and RecoverPoint CDP co-existence is not supported on an array running
Enginuity 5876 when the R2 device is on an array running HYPERMAX OS 5977.
If the SRDF R1 device is tagged as a RecoverPoint CDP source device, disable
RecoverPoint consistency before performing any SRDF operations that may cause
data to flow from the R2 device to the R1 device.
l There is no support for FAST coordination propagation between a VMAX3 array
running HYPERMAX OS 5977 and Enginuity 5876.
l An update operation on the source (R1) side after a failover where the target (R2)
side is still operational to the hosts is not supported when the R1 side is a VMAX
10K, 20K, or 40K array running Enginuity 5876.
l Remote Pair Flashcopy for CKD devices is not supported between a VMAX3 array
running HYPERMAX OS 5977 and an array running Enginuity 5876.
l Thick-to-thin connectivity requires at least Enginuity 5876.159.102 on VMAX
arrays.
l In thin-to-thick and thick-to-thin configurations of arrays running Enginuity 5876
and Enginuity 5773, the thick devices reside on the array running Enginuity 5773.
In configurations running Enginuity 5876 and HYPERMAX OS 5977, the thick
devices reside on the array running Enginuity 5876.
Concurrent
l In SRDF/A mode, you cannot move dynamic SRDF devices between groups.
l Arrays running Enginuity 5876 with CKD zBoost require additional fixes to be able
to connect to HYPERMAX OS 5977.811.784 and 5977.813.785. Contact your Dell
EMC representative for more information.
Cascaded
l When a VMAX 10K is part of a configuration, it must run Enginuity 5876.159.102 to
connect to thick FBA devices on:
n DMX array running Enginuity 5773
n VMAX 40K, VMAX 20K, or VMAX arrays running 5876.159.102 or later
l When the R21 site is a VMAX 10K it must run Enginuity 5876.159.102 or later.

Limitations 9
Interfamily Connectivity

SRDF/Metro
Use this section to determine valid SRDF/Metro configurations.
Multi-Path Cluster

Read/Write Read/Write
Read/Write Read/Write

R1 SRDF links R2 R1 SRDF links R2

Site A Site B Site A Site B

Connectivity
This table shows the valid configurations for SRDF/Metro.

Table 3 SRDF/Metro connectivity

When one side runs… The other side runs…

HYPERMAX OS 5977.814.786 or later
5977.1125.1125

5977.952.892 5977.813.785 or later

5977.945.890 5977.813.785 or later

5977.814.786 5977.811.784 or later

5977.813.785 5977.811.784 or later

5977.811.784 5977.811.784

5977.691.684 5977.691.684

Limitations
l SRDF/Metro does not support:
n CKD device pairs
n ProtectPoint
n CloudArray
n Mobility Safe ID with ALUA
n Microsoft ODX
n Microsoft Cluster with non-uniform connection (without cross-connects)
n SRDF with Consistency with ODX
n FCoE front-end capabilities

10 SRDF Interfamily Connectivity

 Interfamily Connectivity Information

l Active is the only valid SRDF mode. You cannot change this mode once the device
pairs are in an SRDF/Metro configuration.
l You cannot change the SRDF Consistency state once it is enabled for all SRDF
devices.
l Consistency Group (CG) SRDF control and set operations are allowed on one
SRDF group at a time.
l VAAI commands are available with HYPERMAX OS 5977.811.784 and later except
for xCopy/ODX.
l SCSI 2 and 3 reservations are available on HYPERMAX OS 5977.811.784 and later
only.

Array witness
If one or more device pairs become Not Ready or connectivity is lost between the
arrays, SRDF/Metro must decide which side of the pair remains accessible to the
hosts. One of the available methods is the Array Witness which uses a third array to
choose the side that remains available.
SRDF/Metro Witness array:
SR
p
ou

DF
gr

W
s

i tn
es
i tn

es
sg
W
DF

ro
up
SR

SRDF links
R1 R2

R1 array R2 array

The version of HYPERMAX OS or Enginuity that runs on the witness array must be
compatible with that running on each SRDF/Metro array. Use Table 1 on page 3 to
determine the compatibility for the systems that make up your SRDF/Metro pair.

For example, the R1 and R2 sides both run HYPERMAX OS 5977.811.784. Table 1 on
page 3 shows that the Array Witness can run HYPERMAX OS 691.684 or later, or
Enginuity 5876.288.195, with an ePack.

Array witness 11
Interfamily Connectivity

Disaster recovery
In HYPERMAX OS 5977.945.890 or later, you can attach disaster recovery arrays to a
SRDF/Metro configuration. Either or both sides of the configuration can replicate to
another array:
Single-sided replication

SRDF/Metro SRDF/Metro

R11 R2 R1 R21

Site A Site B Site A Site B

SRDF/A SRDF/A
or Adaptive Copy or Adaptive Copy
Disk Disk

R2 R2

Site C Site C

Double-sided replication

SRDF/Metro SRDF/Metro

R11 R21 R11 R21

SRDF/A SRDF/A SRDF/A

Site A or Adaptive Copy Site B or Adaptive Copy Site A or Adaptive Copy Site B
Disk Disk Disk
SRDF/A
or Adaptive Copy
Disk

R2

R2 R2

R2

Site C Site D Site C

The version of HYPERMAX OS or Enginuity that runs on the disaster recovery array or
arrays must be compatible with that running on the SRDF/Metro array it is connected
to. Use the Table 1 on page 3 to determine the compatibility for the systems that
make up your SRDF/Metro configuration.

For example, a double-sided configuration replicates the R11 and R21 sides to a shared,
third array. Also, both the R11 and R21 SRDF/Metro partners run HYPERMAX OS
5977.952.892. Table 1 on page 3 shows that the disaster recovery array can run
HYPERMAX OS 5977.691.684 or later, Enginuity 5876.309.401 with an ePack, or
Enginuity 5876.309.196 with an ePack.

12 SRDF Interfamily Connectivity

 Interfamily Connectivity Information

NDM
NDM uses SRDF to migrate data from an array that runs Enginuity 5876 to another
that runs HYPERMAX OS 5977.945.890 or later. NDM does not affect the operation
of the application host, allowing applications to continue to run while the migration
takes place. Once the migration is complete, the application host switches to using the
array that runs HYPERMAX OS. A typical use of NDM is when a data center replaces
an existing array with a new one.
This table shows the versions of HYPERMAX OS 5977 and Enginuity 5876 that are
compatible for use in NDM operations.

Table 4 NDM compatibility

HYPERMAX OS version Enginuity version

5876.309.401 with ePack (if the Service Processor runs
HYPERMAX OS 5977.1125.1125
Windows 7). Otherwise 5876.309.196 with ePack.

5876.309.401 with ePack (if the Service Processor runs

Windows 7). Otherwise 5876.309.196 with ePack.
5977.952.892
5876.288.400 with ePack (if the Service Processor runs
Windows 7). Otherwise 5876.288.195 with ePack.

5977.945.890 with ePack 5876.288.400 with ePack (if the Service Processor runs
Windows 7). Otherwise 5876.288.195 with ePack.

Refer to the host support matrix for information on the hosts that are supported for
these combinations of operating environment.
For disaster recovery (DR) purposes, either or both arrays in an NDM configuration
can be connected to additional arrays using SRDF. The rules for SRDF connectivity
between a NDM array and a DR array are the same as a regular 2-site SRDF
replication configuration. When both sides of the NDM configuration are connected to
other arrays, treat each side as a separate, 2-site configuration.

NDM 13
Interfamily Connectivity

Requirements for performing system upgrades

When upgrading HYPERMAX OS in any SRDF configuration, ensure that the arrays
remain in a supported scenario throughout the upgrade process. For example, in a 2-
site configuration upgrading Site A to 5977.811.784 or later leaving Site B running
5977.596.583 is not supported.
To avoid unsupported configurations, use an upgrade path similar to the following
example of a 3-site SRDF configuration. Initially, all sites are running 5977.596.583
and the aim is to upgrade to 5977.814.786.
1. Upgrade Site A to 5977.691.684.
2. Upgrade Site B to 5977.691.684.
3. Upgrade Site C to 5977.691.684.
4. Upgrade Site A to 5977.814.786.
5. Upgrade Site B to 5977.814.786.
6. Upgrade Site C to 5977.814.786.

14 SRDF Interfamily Connectivity

 Interfamily Connectivity Information

Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved.

Published May 2017

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL 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 DELL SOFTWARE DESCRIBED IN THIS PUBLICATION
REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.

Requirements for performing system upgrades 15