Dell EMC Host Connectivity Guide for IBM i · Dell EMC Host Connectivity Guide for IBM i P/N 300-009-584 REV 07 ... technical escalations for this specific platform. EMC IBM i Global

and Macao.

Dell EMC Host Connectivity Guidefor IBM i

P/N 300-009-584REV 07

This document is not intended for audiences in China, Hong Kong,Taiwan,

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

Published June 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 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 Dell EMC software described in this publication requires an applicable software license.

Dell, EMC2, EMC, and the EMC logo are registered trademarks or trademarks of Dell Inc. or its subsidiaries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulator document for your product line, go to Dell EMC Online Support (https://support.emc.com).

Dell EMC Host Connectivity Guide for IBM i2

CONTENTS

Preface

Chapter 1 Introduction

Introduction to IBM i ................................................................................. 14Platform naming conventions .............................................................. 14IBM i common terminology .................................................................. 15IBM i Knowledge Center ...................................................................... 18

Chapter 2 Dell EMC Storage Configuration for IBM i Environments

Physical drive types .................................................................................. 20Device emulation....................................................................................... 21

D910 emulation .................................................................................... 212107 variable emulations ......................................................................22Emulation interoperability and compatibility with IBM i........................24

Creating devices........................................................................................ 26Ranges ............................................................................................... 26Device type overview...........................................................................27Configuring IBM i devices ................................................................... 29

Setting the Fibre Channel port .................................................................. 43FA director settings .............................................................................43VMAX3 D910 Connect via switch (SAN) .............................................43VMAX3 D910 Direct Connect...............................................................44VMAX D910 Connect via switch (SAN) ...............................................44D910 Direct Connect (with no SAN)....................................................442107/2105 Direct Connect (with no SAN) .......................................... 452107/2105 Connect via switch (SAN)................................................. 45Fibre protocol port flags ..................................................................... 46Setting front end port characteristics ................................................ 46Open systems devices with IBM i D910............................................... 49Open systems gatekeeper devices sharing a FA port with IBM i data devices .............................................................................. 49

SAN connectivity and other options ......................................................... 55Addressing VMAX devices........................................................................ 59

Device mapping .................................................................................. 59IBM i zoning and masking ................................................................... 60

Gatekeepers.............................................................................................. 61Open Systems Gatekeeper .................................................................. 61IBM i Gatekeeper................................................................................. 61

Multipathing on IBM i hosts....................................................................... 63Hardware requirements and planning.................................................. 63Load source and multipath.................................................................. 64Gatekeepers and multipath................................................................. 64Recognizing multipath devices ........................................................... 64Troubleshooting multipath devices ..................................................... 66Determining non-operational paths..................................................... 69Recovering multipath messages ..........................................................74Resetting multipath connections .........................................................75

Dell EMC Host Connectivity Guide for IBM i 3

Contents

Chapter 3 Managing Storage and Disk Paths in IBM i Environments

IBM i Information Center ........................................................................... 78Configuring and viewing disk configurations.............................................. 79Adding devices to a new or existing ASP................................................... 79

Adding devices to a new ASP ..............................................................79Adding devices from two different Symmetrix systems...................... 80Adding or removing devices to/from an existing ASP ......................... 80

Adding devices to a new or existing IASP .................................................. 82Disk management on IBM i ........................................................................ 82

Remove access to a non-configured disk............................................ 82Determine IOA WWN, speed, status, and other useful information...... 82Determine the IOA location and WWN for DD disk resources ............. 84

Chapter 4 IBM i/VMAX Environment Migrations

Migration services..................................................................................... 88Pre-migrations tasks ................................................................................ 89

Performance....................................................................................... 89Current configuration and status ........................................................ 89Full SAVSYS ....................................................................................... 90

Option 1 — Tape backup/reload ................................................................ 91Option 2 — Add/remove disk units ........................................................... 92Option 3 — Host-based journal replication (log shipping) ......................... 93Option 4 — Storage-based migrations (hardware replication).................. 95Option 5 — SAN-based replication .......................................................... 96

Chapter 5 Host Software Options for IBM i

SRDF/TimeFinder Manager .................................................................... 100Standard features.............................................................................. 100Supported array and array features ....................................................101SRDF functionality............................................................................. 103Extended features ............................................................................. 104SRDF/TimeFinder Manager user interface ........................................ 104Installing SRDF/TimeFinder Manager ................................................ 105Configuring SRDF/TimeFinder Manager............................................ 105Related documentation...................................................................... 105

Solutions Enabler .................................................................................... 107SYMCLI usage in IBM i environments ................................................ 107

Dell EMC Unisphere for VMAX GUI ......................................................... 109VMAX and IBM i ................................................................................ 109

Chapter 6 Server Installation

Prerequisites ............................................................................................ 112Installation procedures ............................................................................. 113

Activate the partition.......................................................................... 117Failure recovery scenarios ....................................................................... 120

Chapter 7 Open Storage and Virtual I/O Server (VIOS) for IBM i

Introduction to Virtual I/O Server............................................................ 122Overview ........................................................................................... 122Virtual SCSI ....................................................................................... 122Virtual Fibre Channel ......................................................................... 123

4 Dell EMC Host Connectivity Guide for IBM i

Contents

Configuring VIOS .................................................................................... 125Logical architecture of example VIOS environment ........................... 125Basic configurations .......................................................................... 126

Installing the Virtual I/O Server and Virtual I/O Client ............................. 134Installing the VIOS and configuring the network ................................ 134

Installing Symmetrix definitions to the AIX ODM..................................... 136Configuring Virtual I/O client with Dell EMC-attached storage ............... 137Performing a D-IPL and installing the iClient ........................................... 142TimeFinder in a VIOS and IBM i environment........................................... 143

Performing TimeFinder functions ...................................................... 143Performing an IPL on the virtual client............................................... 145Mapping TimeFinder devices ............................................................. 145

Appendix A Creating an IBM i System Configuration Listing

Generating a system listing ..................................................................... 148

Glossary


Contents


PrefacePREFACE

IBM i is an integrated operating environment. This guide provides information on configuring and installing an IBM i environment.

As part of an effort to improve and enhance the performance and capabilities of its product lines, Dell EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your Dell EMC representative.

Note: IBM i, AS/400, iSeries, and System i are used interchangeably throughout this document. IBM i is the newest terminology for the operating system.

Audience This guide is intended for use by storage administrators, system programmers, or operators who are involved in acquiring, managing, or operating Dell EMC VMAX systems and host devices.

Readers of this guide are expected to be familiar with:

◆ VMAX system operation

◆ IBM operating environment

Relateddocumentation

For the most up-to-date information, always consult the Dell EMC Simple Support Matrix (ESM), available through E-Lab Interoperability Navigator (ELN).

Refer to Dell EMC Online Support (registration required) for the following documentation:


https://elabnavigator.emc.com




https://support.emc.com


Preface

◆ EMC SRDF/TimeFinder Manager for IBM i Release Notes

◆ EMC SRDF/TimeFinder Manager for IBM i Product Guide

◆ EMC VMAX3 Family Product Guide

◆ EMC Solutions Enabler SRDF Family CLI User Guide

◆ EMC Symmetrix VMAX Family with Enginuity Product guide

◆ EMC VMAX3 Family with HYPERMAX OS VMAX 100K, VMAX 200K, VMAX 400K Product Guide

◆ Configuring a Virtual I/O Server and an iClient using Symmetrix server volumes for System i Technical Notes

◆ EMC Host Connectivity Guide for IBM AIX

◆ EMC Symmetrix VMAX Series with Enginuity For IBM I Environments White Paper

◆ Implementing D910 Devices on EMC Symmetrix VMAX 40K and VMAX 20K/VMAX Storage Arrays White Paper

◆ Implementing D910 Devices on EMC VMAX3 Storage Arrays (VMAX 100K, 200K, and 400K Models) White Paper

◆ EMC E-Lab topology TechBooks and support manuals, available through Dell EMC E-Lab Interoperability Navigator.

For a list of useful and up-to-date web links to various IBM websites, refer to EMC knowledgebase solution emc201768. EMC Knowledgebase solutions provide useful information.

For IBM documentation, refer to the IBM Knowledge Center.






https://www.ibm.com/support/knowledgecenter/ssw_ibm_i


Preface

Dell EMC IBM i Global Practice EMC has identified that specialized support is often required when dealing with some products in a presales cycle and/or during the implementation of proposed solutions, migrations, upgrades or other activities. To effectively support such activities for these specific products, Subject Matter Expert teams were formed and these are managed from a corporate level. These teams are called the EMC Global Practices. One of these practices is the IBM i host specific support group for AS/400, iSeries, and System i. EMC IBM i Global Practice is available to support EMC account teams with the aforementioned activities at [email protected].

EMC IBM i Global Practice is not to be confused with the specialized Technical Support Level2 group, that is dealing with break/fix issues, EMC Service requests and technical escalations for this specific platform.

EMC IBM i Global Practice support can be divided into two main categories, each further described in this section.

◆ “Pre-sales support” on page 9

◆ “Implementation support” on page 9

Pre-sales support For presales support, EMC IBM i Global Practice personnel typically work at the Solutions Architect level.

EMC IBM i Global Practice staff can support EMC account teams in the evaluation and design phase of projects that include IBM i systems. EMC IBM i Global Practice strongly recommends you use its Performance Analysis service to analyze the customers current systems in order to effectively size and configure an EMC external storage profile for the involved IBM i servers. The analysis results, together with sizing and configuration recommendations, including best practices, are summarized in a report for the account team and the customer. Every implementation will require some level of services, i.e., connectivity support, migration services, customization, scripting, training, testing, etc. The EMC IBM i Global Practice can provide the technical scope for these services and project/estimate the required LOE (Level Of Effort). The EMC IBM i Global Practice recommendations and LOE then form the basis of the proposed solution and the EMC account team can build their commercials around that framework.

Implementationsupport

For implementation support, EMC IBM i Global Practice personnel typically work at the Implementation Specialist level.

Several services may be included in the delivery phase of a project. Basic connectivity support could be provided in cooperation with the local EMC services department and could include SAN design/connectivity, Zoning/LUN-Masking, storage provisioning and completing the assignment of the new storage profile to the IBM i server(s).

Migration support for the IBM i platform is very specific in nature and also requires specialized resources to support such migrations. Multiple migration options exist for the IBM i platform, varying from full tape restore scenarios to host-based online data migrations and Load Source migrations.

SRDF and TimeFinder implementations are required for local and remote replication of IBM i environments. For IBM i, EMC provides a native i5/OS software suite to configure, monitor, and control these replications. This software is called SRDF/TF


Preface

Manager for IBM i (STM). Software installs, knowledge transfers, customized scripting and training and customer testing windows are common components of TF and SRDF implementations for System i.

Proof-of-concepttesting and

demonstrations

As a special service, requiring both Solutions Architect and Implementation Specialist expertise, the EMC IBM i Global Practice also provides support for customer Proof-Of-Concept testing (POCs) and customer demonstrations in the EMC Solutions Center in Cork, Ireland, or Hopkinton, Massachusetts locations. This is most often requested in the pre-sales phase. POC s can also be performed at the customer site, The local account team has to arrange a loaner, or a "try and buy" program for the required EMC equipment, while the customer provides the host resources (such as the Server, OS, I/O adapters, etc.).

The EMC IBM i Global Practice can be reached through the following email address: [email protected].

Conventions used inthis document

EMC uses the following conventions for special notices.

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

IMPORTANT

An important notice contains information essential to software or hardware operation.

Typographical conventions

EMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements (such as names of

windows, dialog boxes, buttons, fields, and menus)• Names of resources, attributes, pools, Boolean

expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, utilities

• URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications

Bold Used in running (nonprocedural) text for:• Names of commands, daemons, options, programs,

processes, services, applications, utilities, kernels, notifications, system calls, 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


Preface

Where to get help EMC support, product, and licensing information can be obtained on the EMC Online Support site as described next.

Note: To open a service request through the EMC Online Support site, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Product information

For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to EMC Dell EMC Online Support (registration required).

Technical support

EMC offers a variety of support options.

Support by Product — EMC offers consolidated, product-specific information on the Web at Dell EMC Online Support.

The Support by Product web pages offer quick links to Documentation, White Papers, Advisories (such as frequently used Knowledgebase articles), and Downloads, as well as more dynamic content, such as presentations, discussion, relevant Customer Support Forum entries, and a link to EMC Live Chat.

EMC Live Chat — Open a Chat or instant message session with an EMC Support Engineer.

eLicensing support

To activate your entitlements and obtain your Symmetrix license files, visit the Service Center on Dell EMC Online Support, as directed on your License Authorization Code (LAC) letter e-mailed to you.

For help with missing or incorrect entitlements after activation (that is, expected functionality remains unavailable because it is not licensed), contact your EMC Account Representative or Authorized Reseller.

For help with any errors applying license files through Solutions Enabler, contact the EMC Customer Support Center.

Courier bold Used for:• Specific user input (such as commands)

Courier italic Used in procedures for:• Variables on command line• User input variables

< > 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”

{ } Braces indicate content that you must specify (that is, x or y or z)

... Ellipses indicate nonessential information omitted from the example




http://support.EMC.com






Preface

If you are missing a LAC letter, or require further instructions on activating your licenses through the Online Support site, contact EMC's worldwide Licensing team at [email protected] or call:

◆ North America, Latin America, APJK, Australia, New Zealand: SVC4EMC (800-782-4362) and follow the voice prompts.

◆ EMEA: +353 (0) 21 4879862 and follow the voice prompts.

We'd like to hear from you!

Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]

Your feedback on our TechBooks is important to us! We want our books to be as helpful and relevant as possible. Send us your comments, opinions, and thoughts on this or any other TechBook to:

[email protected]


CHAPTER 1

This chapter provides the following general information about IBM i hosts and operating system.

◆ Introduction to IBM i ............................................................................................ 14

Introduction

Introduction 13

Introduction

Introduction to IBM i

Note: IBM i, AS/400, iSeries, and System i are commonly used interchangeably. IBM i is the newest terminology for the operating system.

IBM i is an integrated operating environment. This section contains the following information:

◆ “Platform naming conventions” on page 14

◆ “IBM i common terminology” on page 15

◆ “IBM i Knowledge Center” on page 18

For the most up-to-date information, always consult the Dell EMC Simple Support Matrix (ESM), available through Dell EMC E-Lab Interoperability Navigator.

Platform naming conventions

The term AS/400 may be used to cover this platform; however, AS/400 is a historical name, changed around 2000. Since then, several names have been used for the hardware, including:

◆ AS/400◆ iSeries ◆ eServer iSeries◆ System i◆ Power 5◆ Power System

In addition, operating system names have included:

◆ OS/400◆ i5/OS◆ IBM i

Currently, the correct names are:

◆ For the hardware platform: IBM Power Systems

◆ For the OS:IBM i

However, some still refer to the platform simply as AS/400, iSeries, or System i. Note that Power system now refers to the current converged hardware platform that runs the IBM i, AIX, Linux, and VIOS operating systems.





Introduction

IBM i common terminology

Table 1 lists some of the more common terms, together with definitions more familiar to Open Systems platform users. For a complete glossary of IBM terms, visit the IBM Knowledge Center, select the appropriate version of the operating system, and search for IBM i glossary.

Table 1 IBM i common terminology (page 1 of 3)

Term Description

Add The term used for the process of adding additional disks to an ASP. For a more detailed description and how the ADD process works with Dell EMC external storage, refer to Chapter 3, “Managing Storage and Disk Paths in IBM i Environments.”

APAR Authorised Program Analysis Report. A document released by IBM to describe an issue, procedure, warning, etc. Some APAR may result in one or more PTF.

AS/400AS/400e

Application System 400. Introduced circa 1988, this name may still persist.

ASP Auxiliary Storage Pool. This is a grouping of one or more physical disks on which objects, file systems etc. can be created. Every IBM i has at least one ASP, the system ASP (ASP 1). In addition, up to 31 basic ASP and up to 223 independent ASP (iASP) can be created. The actual maximum configurations depend on the IBM i OS levels. See “IASP” on page 16.

CCIN Customer Card Identification Number. Not to be confused with the feature code, the CCIN is the code by which every piece of hardware (e.g. processor, memory, HBA (IOA) etc.) can be identified on the LPAR. Every CCIN has one or more feature codes associated with it The CCIN (as reported on the LPAR) and the feature code may or may not be the same number. For example, the CCIN 5702 has feature codes 5712 and 5715 associated with it.To match the CCIN to a feature code (or vice versa), please see “feature code” entry below.

CEC Central Electronics Complex. This is the main unit of the server, containing the CPU, memory etc. The model number and serial number are associated with this unit (e.g. model 9406-550, serial number 654A32B).

Cumulative This is the main grouping of fixes (PTF) available for IBM i. Cumulative fixes.

DST Dedicated Service Tools. Normally referred to as DST, this allows the boot (IPL) process to be stopped before the operating system is loaded, allowing such activity as removing disks, checking the status of disks, etc. If the operating system fails to start, it is normal to attempt to boot to DST (from either the LPAR load source or a LIC CD) to further analyze the issue.

Emulation Disks (Dell EMC SymmetrixTM devices) are often referred to as emulations. Emulations take two forms:Internal emulations: - Symmetrix devices that appear to the LPAR as if they are an internal disk.External emulations: - Symmetrix devices that appear to the LPAR as if they are external disks on IBM external storage.Since the LIC only recognizes specific CCIN, and all these CCIN are IBM hardware resources, it is necessary to emulate such CCIN to be recognized by the LIC. Note that all emulations match real IBM CCIN, and are subject to the same pre-requisites (such as LIC and OS levels, PTF levels, IOP/IOA support levels, etc.).

Introduction to IBM i 15





Introduction

Feature Code Not to be confused with the CCIN; the feature code identifies every piece of hardware (e.g. processor, memory, HBA (IOA) etc.) and can be used to order such hardware from IBM, build configurations in the SPT, etc. Every feature code has one or more CCIN associated with it.The CCIN (as reported on the LPAR) and the feature code may or may not be the same number. For example, the feature code 0150 has CCIN 0150 and 25BC associated with it.To match a feature code to the correct CCIN (or vice versa), refer to various IBM feature code cross references, including:IBM System i5, eServer i5 and iSeries System Builder V5R4: http://www.redbooks.ibm.com/abstracts/sg242155.htmlIBM System i Overview: Models 515, 525, 550, 570, 595, and More: http://www.redbooks.ibm.com/abstracts/redp5052.htmlIBM Power 570 and IBM Power 595 (POWER6) System Builder: http://www.redbooks.ibm.com/abstracts/redp4439.html?Open

HMC Hardware Management Console. Linux based PC used to manage the hardware, such as configuring and managing LPAR.

Host One host typically represents one LPAR (not a server, which supports one or more LPAR).

I5/OS and V5Rv

I5/Operating System and V5Rv of the operating system. This name was used for the operating system from circa release V5R3 to V5R4 for the operating system.

IASP Independent Auxiliary Storage Pool. This type of ASP is different from a System ASP or basic user ASP in that: when used on a standalone IBM i partition, they can be made online/offline without having to IPL (boot) the IBM i.They can be switched between different IBM i, without the need for IPL (boot) of any of the IBM i. See “ASP” on page 15.

IBM i The name used for the operating system since circa release V6R1.

IOA Input Output Adapter – this is the actual HBA itself. Some IOAs require a matching IOP to operate while others do not.

IOP Input Output Processor. This is a card paired (for example) with an IOA, and it is used to manage the IOA. More recently, IOP are increasingly becoming unnecessary, depending on the OS level, the server hardware and the IOA (for example) involved

IOPless IOA IOA (HBA) that can be configured without a matching IOP card.

IPL Initial Program Load. This refers to a boot or reboot of the LPAR.

iSeries(eServer)

AS/400 platform renamed to eServer iSeries circa 2000.

LIC Licensed Internal Code. This is the code (below the operating system) that manages many low level functions such as memory addressing, I/O managers, storage management, etc. The boot order is LIC first and then operating system. It is possible to stop the boot after the LIC has loaded and before the operating system has loaded, using DST. This is very useful for activities such as checking the status of the disks before starting the operating system.

Load Source(disk)

The LPAR boot device (boot disk). The LIC is entirely located on the load source, where as the operating system is located on the load source and also other disks. This disk must be visible to the LPAR in order to at least IPL (boot) to DST.

LPAR Logical partition. This is a subset of the overall system resources configured to act as one host. One server may support one or more logical partitions.

MFIOP Multi Function I/O processor. Traditionally, this was the primary SCSI controller in the system that controls the Load Source disk. It may also hold the alternate IPL source, as an internal SCSI tape or CD/DVD drive for install media.


Term Description


http://www.redbooks.ibm.com/abstracts/sg242155.html

http://www.redbooks.ibm.com/abstracts/redp5052.html

http://www.redbooks.ibm.com/abstracts/redp4439.html?Open

Introduction

Mirroring (1) The process of writing the same data to two disk units within the same auxiliary storage pool at the same time. The two disk units become a mirrored pair, allowing the system to continue when one of the mirrored units fails. (2) The process of writing the same data to multiple disks at the same time. The mirroring of data protects it against data loss within the database or within the recovery log.

Non-Configured

When new disks are presented to an LPAR, they enter the list of non-configured disks. The disks can then be added to an ASP or iASP.

OS/400 Operating System/400. This name was used up to circa release V5R3 of the operating system. See also IBM i.

PAL Product Activity Log. This log provides a list of SRC relevant to the LPAR on which it resides. These SRC may represent items that are (for example) statistical, informational, temporary issues or permanent issues.

PTF Program temporary fix – a patch for IBM i related components. Typically an APAR describes the reason for the PTF. The PTF also has a document called a PTF cover Letter that links it to the APAR.

Rack Configuration

The complete hardware configuration printout for the IBM i server. This includes hardware currently associated (or previously associated without being removed) with the LPAR on which the rack configuration is printed. All the hardware in the server can be seen from the HMC.

SAL Service Action Log. This log lists items requiring intervention by service personnel.

SAN BOOT This is IBM terminology for the capability of the LPAR to boot from an external disk via a SAN. FHDA is not considered SAN boot technology, even though it allows boot from the SAN.

Server This comprises of the hardware CEC, expansion racks, expansion towers etc, all covered by one IBM serial number such as 654A32B. One server can support one or more LPAR, each LPAR typically representing one host.

Server Serial number

This is a number such as 654A32B that is used by IBM to identify the server and associated licenses, support contracts etc. See also CEC.

Smart IOA IOA (HBA) that can be configured without a matching IOP card.

SPT IBM system planning tool, also know as the LPAR validation tool. This is a utility that can be downloaded from IBM and used to plan the configuration of LPARs on a server. This tool is very useful for resolving some IBM hardware compatibility and dependencies questions. For information on how to obtain the IBM SPT, please refer to solution

SRC System Reference Codes. These 8 digit hexadecimal codes provide status information for the LPAR and server. SRC starting with “C” indicate IPL progress codes (i.e. the status of the boot process), “D” indicate shutdown progress codes (i.e. the status of the shutdown process), “0000 0000” (all zero SRC) represents a normal statusAll others present a status that may or may not require intervention.

SST IBM i System Service Tools. These tools are available when the full IBM i full OS is loaded. If only the LIC is loaded, or only IPL from CD is possible, then Dedicated Service Tools are available (DST).

STM Dell EMC SRDFTM/TimeFinderTM Manager. This is Dell EMC software based on Dell EMC solutions enabler that allows the IBM i administrator to configure and manage many various features such as Business Continuance Volumes (BCV), Symmetrix Remote Data Facility volumes (SRDF), etc.

System i iSeries renamed circa 2006.


Term Description

Introduction to IBM i 17

Introduction

IBM i Knowledge Center

For technical information about IBM i, refer to IBM i’s welcome page in the IBM Knowledge Center, as shown in Figure 1, at:

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i/welcome

Figure 1 IBM i welcome page


CHAPTER 2

This chapter provides the following information about storage configuration for IBM i environments.

◆ Physical drive types ............................................................................................. 20◆ Device emulation.................................................................................................. 21◆ Creating devices .................................................................................................. 26◆ Setting the Fibre Channel port ............................................................................. 43◆ SAN connectivity and other options..................................................................... 55◆ Addressing VMAX devices.................................................................................... 59◆ Gatekeepers......................................................................................................... 61◆ Multipathing on IBM i hosts ................................................................................. 63

Dell EMC Storage Configuration for IBM i Environments

Dell EMC Storage Configuration for IBM i Environments 19


Physical drive typesThe Dell EMC VMAX3TM, VMAXTM, and Symmetrix family of storage arrays connects to the IBM i host by emulating the devices the operating expects to see from an IBM storage subsystem. Historically, these were internal SCSI emulations and external SCSI emulations. This section discusses only those emulations supported by the Dell EMC VMAX3, VMAX, and Symmetrix storage arrays through Fibre Channel connectivity. For the most up-to-date support information, always consult the Dell EMC Simple Support Matrix.

Dell EMC VMAX3 (400K, 200K, and 100K) arrays use numerous physical drives from a variety of vendors with a number of differing sizes and characteristics, including Enterprise Flash, SAS, and SATA physical drives. All of the physical drives installed in the VMAX3 arrays have the same low level format, since the VMAX3 array only supports the creation and configuration of standard FBA emulation devices for presentation to the host. The only emulation that can be created on the VMAX3, which can be used on the IBM i host, is the D910 (thin) emulation device.

Dell EMC VMAX 40K, VMAX 20K/VMAX, and VMAX 10K (systems with SN xxx987xxxx) arrays use numerous physical drives from a variety of vendors with a number of differing sizes and characteristics.

The VMAX arrays support two different low level formatted physical disks:

◆ Physical disks (520 block low level format), which will support the creation of Mainframe and Open System host device emulation.

◆ Physical disks with 528 block low level format, which support IBM i 2107_Axx emulation device creation.

Note: VMAX 10K xxx987xxxx only supports 520 block low level format.

Dell EMC can supply Fibre Channel, SATA, and EFD (Flash) physical drives in both low-level formats. These disks are available in many sizes and rotational speeds. disk drives and capacities can be found on Dell EMC Online Support under the product name, documentation.

In the earlier DMX range of arrays, the D910 emulation is not supported.

In earlier ranges of arrays, 512 block low-level format physical disks are required for Mainframe and Open System hosts, while 520 block low-level format physical disks are required for native IBM i host connections (using either 2105 or 2107 emulations).

IMPORTANT

It is not possible to swap physical disks between a VMAX and a DMX due to a change in format of the physical disks.

More information on D910 can be found in the following two Dell EMC technical white papers located at Dell EMC Online Support:

◆ Implementing D910 Devices on EMC VMAX3 Storage Arrays (VMAX 100K, 200K, and 400K models)

◆ Implementing D910 Devices on EMC Symmetrix VMAX 40K and VMAX 20K/VMAX Storage Arrays










Device emulationThe following information is included in this section:

◆ “D910 emulation” on page 21

◆ “2107 variable emulations” on page 22

◆ “Emulation interoperability and compatibility with IBM i” on page 24

D910 emulation

D910 emulation is as follows:

◆ D910-099

• 099 indicates the volume is to be treated as "Protected" DPY Parity devices.

All VMAX3 HYPERMAX OS levels support the D910 emulation.

Prerequisites The IBM i host must meet or exceed the following minimum pre-requisites to be able to utilise the D910 devices.

◆ IBM Power 6 (and later) systems

◆ Connection method can either be direct connected or switch connects.

◆ Host Fibre Channel HBAs (Feature Codes 5749, 5774, and 5735).

◆ Further Fibre Channel HBA are available at IBM i 7.1 and above (see support matrix for full listing)

◆ IBM i 6.1 (6.1.1 LIC) and later releases.

◆ Minimum required IBM PTF levels are:

◆ 6.1.1 requires a minimum CUM C2122610 (2122) MAY 14,2012

◆ (NPIV support excluded).

◆ 7.1 requires a minimum of TECH REFRESH 4 (TR4) or CUM

◆ C2115710 (2115) May 17, 2012.

The latest supported IBM i host OS and Fibre Channel HBA are updated and detailed on the Dell EMC Simple Support Matrix, available through Dell EMC E-Lab Interoperability Navigator.

The VMAX 40K and VMAX 20K arrays support the D910 emulations for the IBM i host. They also support the creation of 2107_Axx emulation devices.

The minimum Dell EMC Enginuity level required to create the D910 emulation devices is 5876.82.57.

The host pre-requisites for utilizing are the same as those listed in “Prerequisites” on page 21.

Note: VMAX 10K only supports D910. You cannot create 2107 devices on a VMAX 10K.

Device emulation 21




The VMAX 40K and VMAX 20K arrays retain the capability to create 2107_Axx emulation devices, which as previously described, require 528 block low level format physical disks to be installed in the array to allow the creation of the 2107_Axx devices.

The variable emulation types are only supported when used with an IBM Power 6 (and later) system using the IBM Smart IOA Fibre Channel HBAs (Feature Codes 5749, 5774, and 5735).

2107 variable emulations

Support for new IBM i variable-sized LUN capabilities was introduced in IBM i V6.1.1 LIC refresh.

Dell EMC now recognizes and tolerates volumes of non-fixed capacities according new LIC for 6.1.1. However, Dell EMC still recommends using the default fixed volume types where possible.

Note: This variable LUN size can be used where small areas of disk are available for the use in a DSE pool.

Variable LUN size emulations

LUN size emulations are as follows:

◆ 2107_099

• 099 indicates the volume is to be treated as "Protected" (equivalent to the current "A0x" models) DPY Parity devices.

◆ 2107_050

• 050 indicates the volume is to be treated as "Unprotected" by the OS (allowing it to be mirrored by the OS, equivalent to current "A8x" models).

Supported minimum Enginuity levels are:

◆ 5874.240.191

◆ 5875.135.91

The variable emulation types are only supported when used with an IBM Power 6 (and later) system using the IBM Smart IOA Fibre Channel HBAs (Feature Codes 5749, 5774, and 5735).

2107 devices

2107 devices include:



◆ 2107-Ax emulations are external disk emulations based on the IBM DS8000 storage subsystem, meaning that the IBM i recognizes that these emulations are not located within the IBM i server racks. Instead, they are connected through Fibre Channel disk controllers.

◆ 2107-Ax emulations are external disk emulations based on the IBM DS8000 storage subsystem, meaning that the IBM i recognizes that these emulations are not located within the IBM i server racks. Instead, they are connected through Fibre Channel disk controllers.

◆ 2107-A8x is reported to the host as an unprotected disk. Note that this does not relate to the protection internal to the Symmetrix system, which could have various local (e.g., two-way mirror) and/or remote (e.g., SRDF) protection. Reporting a disk as unprotected allows the disk to be used in host level mirroring.

◆ 2107-A0x is reported to the host as a parity-protected disk. Note that this does not relate to the protection internal to the Symmetrix system, which could have various local (e.g., two-way mirror) and/or remote (e.g., SRDF) protection. Reporting a disk as protected allows the disk to be used in a protected ASP. Disks that are reported as protected cannot be used for host level mirroring.

The emulation CCINs are assigned to the Dell EMC Symmetrix device at the time that the device is created. For example, when creating a 35.1 GB disk for IBM i using the Dell EMC Symmetrix command line interface (SYMCLI) symconfigure command, the “emulation=EmulationType” parameter is used to determine the emulation CCIN. The devices are always FBA, so the Emulation Type can be set, for example, to AS/400_2107_A05.

Table 2 on page 23 lists a variety of variable block host models available along with their internal array data structure.

Note: 2107 devices in Table 2 can only be created on VMAX 20K and VMAX 40K.

Table 2 Variable host devices and their Symmetrix data structures

Host Emulation

Host Size GB

Cylinder count: Structure

Minimum Ucode

Protection presented to Host

D910_099 Variable min cylinder count 3052max cylinder count 2236962

Note: VMAX3 must be a single device but earlier VMAX systems must be a meta construct device

5876.82.xx DPY / PARITY

iOS 6..1 minSmart IOA required

2107_99 Variable min cylinder count 165 max cylinder count 2236963

5774.240.1915875.27.15.1

DPY / PARITY

iOS 6.1.1 minSmart IOA required

2107_50 Variable min cylinder count 165 max cylinder count 2236963

5774.240.1915875.27.15.1

Unprotected

iOS 6.1.1 minSmart IOA required

Device emulation 23


The DMX arrays only support the creation of 2107_Axx and 2105_Axx emulation devices.

The DMX Enginuity code does not support the creation of variable size 2107 devices, and only the fixed size devices listed in Table 3 on page 24 can be created.

Host models Table 3 lists a variety of fixed block host models available along with their internal array data structure. Cylinder sizes based on a 64k track size are shown.

Note: VMAX3 only supports D910 devices.

1. These emulations are not supported in VMAX 40K, VMAX 20K/VMAX, and VMAX 10K xxx987xxxx arrays.

2. VMAX 10K xxx987xxxx only supports D910 devices.

.Note: Engage Dell EMC iSeries Global Practice when considering SRDF between different generations of Symmetrix, as the meta structure can be different for the same host types.

Emulation interoperability and compatibility with IBM i

Not all Enginuity levels support all emulation sizes and types. To determine which emulations are supported in which Enginuity levels, refer to the Dell EMC Simple Support Matrix.

Table 3 Fixed block host devices and their Symmetrix data structures

Host Emulation

Host Size GB

Cylinder count: Structure

Minimum Ucode Protection presented to Host

Server 0.003 3 VMAX 40K VMAX 20K/VMAXVMAX 10K xxx987xxxx All DMX

GateKeeper Vol for ECC / SE

2105_A82 1 17.5 17860: {4x4465} 5568.29.13.A Unprotected

2105_A02 1 17.5 17860: {4x4465} 5568.19.10A DPY / PARITY

2105_A85 1 35.1 35784: {8x4473} 5670.69.62 Unprotected

2105_A05 1 35.1 35784: {8x4473} 5670.69.62 DPY / PARITY

2105_A84 1 70.5 71792: {16x4487} 5670.69.62 Unprotected

2105_A04 1 70.5 71792: {16x4487} 5670.69.62 DPY / PARITY

2107_A82 2 17.5 17860: {4x4465} 5773.79.58 Unprotected

2107_A02 2 17.5 17860: {4x4465} 5773.79.58 DPY / PARITY

2107_A85 2 35.1 35784: {4x8946} 5773.79.58 Unprotected

2107_A05 2 35.1 35784: {4x8946} 5773.79.58 DPY / PARITY

2107_A84 2 70.5 71792: {4x17948} 5773.79.58 Unprotected

2107_A04 2 70.5 71792: {4x17948} 5773.79.58 DPY / PARITY

2107_A86 2 141.1 143576: {8x17947} 5771.95.103 Unprotected

2107_A06 2 141.1 143576: {8x17947} 5771.95.103 DPY / PARITY

2107_A87 2 282.2 287152: {16x17947} 5771.95.103 Unprotected

2107_A07 2 282.2 287152: {16x17947} 5771.95.103 DPY / PARITY






Since the emulations (disks presented from Dell EMC Symmetrix to IBM i) are reporting IBM CCIN to the IBM i, it follows that these emulations are subject to the same prerequisites rules as their real IBM counterparts. Therefore, in addition to checking the Dell EMC interoperability information, it is also essential to check the IBM compatibility sources of information, including:

◆ IBM prerequisites website

◆ IBM System Planning Tool (SPT)

◆ IBM System builder manuals (where appropriate)

A list of useful IBM compatibility sources of information are listed with links in Dell EMC Knowledgebase solution emc201768. IBM Feature Codes are used to determine the prerequisites, so if the item CCIN is known, it must be first cross-referenced to the feature code (FC).

When the product is installed on the server, the Licensed Internal Code (LIC) identifies the hardware by its factory-assigned Customer Card Identification Number (CCIN). This is also a four-digit code. Note that the CCIN may, or may not, be the same as its assigned Feature Code. In fact, a single feature code may represent several CCINs and vice versa. To cross-reference the feature code to the CCIN and vice versa, refer to the following. For more information, refer to the Dell EMC Knowledgebase solution emc11005.

For example, the CCIN 280E cross references to the Feature Code 5760, so use this feature code on the IBM prerequisites website at https://www-912.ibm.com/e_dir/eserverprereq.nsf, to check compatibility with IBM I OS levels, server hardware models, and the IBM system planning tool (SPT) to determine correct rack slot locations, IOP dependencies, and so on.

Device emulation 25


Creating devices This section includes the following information:

◆ “Ranges” on page 26

◆ “Device type overview” on page 27

◆ “Configuring IBM i devices” on page 29

Ranges

VMAX3 Every VMAX3 array will come from the factory with the bin file (configuration) already created. The following best practices for deployment will already be in place:

◆ TDAT sizes

◆ RAID protection

◆ Virtual Provisioning Pools

Therefore, the only devices that require creation are the TDEV (thin devices).

A thin device that can be used in many of the same ways that regular host-accessible fixed block host devices have traditionally been used. Unlike regular fixed block host devices, thin devices do not need to have physical storage completely allocated at the time the devices are created and presented to a host. The physical storage that is used to supply disk space for a thin device comes from virtual provisioning pool (which, as noted above, is already in place when a VMAX3 array arrives from the factory).

The only thin devices that can be presented to the IBM i host is the AS/400-D910-099 CDEV emulation device.

Note the following in regards to the D910 device when used on the VMAX3 array.

◆ D910 is a standard FBA device◆ Meta devices are not supported on VMAX3◆ FAST for the IBM i host is supported through Dell EMC Solution Enabler. (SE 8)◆ Minimal native IBM i host component support is available◆ Variable sized LUN capacity ranging from 3 GB to 2 TB◆ VMAX3 does not support any legacy device emulations

For further details, refer to the Implementing D910 Devices on EMC VMAX3 Storage Arrays (VMAX 100K, 200K, and 400K models) white paper located at Dell EMC Online Support.

VMAX In the previous VMAX range, a thin storage pool has to be created and the devices for that storage pool, a type of internal Symmetrix device called a data device (TDAT), also has to be created. The resulting storage pool is dedicated to the purpose of providing the actual physical storage used by thin devices. When TDEV are first created, the thin devices are not associated with any particular thin pool. An operation referred to as binding must be performed to associate a thin device with a thin pool.

The following device types can be included in the VMAX configuration:







◆ FBA Server TDAT◆ AS/400-D910-099 CDEV◆ Thin_BCV

Striped and concatenated meta volumes are supported on the VMAX range.

VMAX does support any legacy device emulations (2107_Axx emulation devices) when 528 block format physical disks are installed, including variable size 2107 emulation devices.

Note: The 2107_Axx emulation devices cannot be part of any TDAT pool.

DMX All IBM i Fixed block host devices (2107_Axx and 2105_Axx) are constructed with hyper volumes being combined, in either a striped or concatenated configuration, to form a single meta device, which is then presented to the IBM i host.

The hyper devices are transparent to the IBM i host, which addresses the single meta device.

The number of Symmetrix hyper volumes used to create each meta volume is automatically determined by the 2107/2105 model number and size of the device. (See Table 3 on page 24 for the list of fixed block host models available on the DMX range.) Note the following:

◆ The DMX range does not support the AS/400-D910-099 CDEV emulation.

◆ The DMX range does not support variable size 2107 emulation devices.

Device type overview

Table 4 describes the device types of the VMAX3, VMAX, and Symmetrix storage environments.

Table 4 Device types (page 1 of 3)

Device type Description

ACLX devices ACLX devices are front end port devices similar to VCM devices that are used for storage provisioning using Auto-Provisioning Groups on Enginuity 5874 and higher. For more information, refer to the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide.

BCV devices Specialized devices used to create a local copy of data contained in a standard Symmetrix device, which can be used for backup, restore, decision support, and application testing. Symmetrix TimeFinder is a business continuance solution that allows you to use these special Symmetrix devices called BCV devices (Business Continuance Volume). Each BCV device has its own host address, and is configured as a stand-alone Symmetrix device. For more information, refer to the EMC Solutions Enabler SRDF Family CLI User Guide.

DATA devices (datadev or TDAT)

DATA devices are used for Dell EMC Virtual Provisioning™ and are similar to SAVE devices, in that they are not visible to the host and must be contained in a pool before they can be used. o can only contain devices of the same emulation and protection type, however, the DATA devices can be different sizes. Refer to the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide.

Creating devices 27


Device Masking (VCM) devices

Symmetrix devices that have been masked for visibility only to certain hosts. The device masking database (VCMDB) holds device masking records and typically resides on a 24 or 48 cylinder disk device. VCM devices are used for device masking on Enginuity 5773 and earlier. For more information, refer to the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide.

Diskless devices SRDF/Extended Distance Protection (EDP) streamlines a cascaded SRDF linkage out to the remote site with a direct (diskless) connection. In a cascaded SRDF/EDP environment, the cascaded R21 devices are designated as diskless devices, which provides replication between the source site and remote target site without requiring disks at the middle site. Because the diskless R21 device has no local disk space allocated to store the user data, it reduces the cost of having disk storage at the middle site.

DRV devices Dynamic Reallocation Volume. A non-user-addressable Symmetrix device used by the Symmetrix Optimizer to temporarily hold user data while reorganization of the devices is being executed. Typically, it is used by the Optimizer in logical volume swapping operations. For more information, refer to the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide.

Dynamic RDF devices Devices can be configured to be dynamic RDF-capable devices. Dynamic RDF functionality enables you to create, delete, and swap SRDF pairs while the Symmetrix array is in operation. Using dynamic RDF technology, you can establish SRDF device pairs from non-SRDF devices, then synchronize and manage them in the same way as configured SRDF pairs. The Dynamic RDF configuration state of the Symmetrix array must be enabled via the Configuration Manager and the devices must be designated as dynamic RDF-capable devices. For information about dynamic RDF devices, refer to the EMC Solutions Enabler SRDF Family CLI User Guide.

Gatekeeper devices For detailed information on gatekeeper management, refer to the EMC Solutions Enabler Installation Guide. For specific gatekeeper sizing recommendations for all Symmetrix configurations, refer to EMC Knowledgebase solution emc255976, available on Dell EMC Online Support.

Metadevices Allows individual devices to be concatenated to create larger devices. A metadevice consists of a metahead and its member devices. The metahead is the first device in the metadevice sequence and is responsible for receiving all incoming commands. It also identifies the entire metadevice. When an incoming command for the metahead is processed, the Symmetrix determines which metadevice member should execute the command. Metahead devices can be added to a device group while a metamember cannot be added to a device group. This holds true for both standard and BCV devices.

SAVE devices Special devices (not mapped to the host) that provide physical storage space for pre-update images or changed tracks during a virtual copy session of TF/Snap and SRDF/A DSE operations. SAVE devices are a predefined pool of storage devices and must be configured for this purpose. The SAVE device pool acts as a group for storing data in striped form. SAVE devices are assigned a Symmetrix device number and can be unprotected, mirrored, or parity RAID. For more information, refer to the EMC Solutions Enabler SRDF Family CLI User Guide.

Standard devices A Symmetrix device configured for normal Symmetrix operation under a desired protection method (such as RAID 1, RAID 5, and SRDF).

SRDF devices Devices configured as RDF1, RDF2, or RDF21 to support SRDF operations. The Symmetrix Remote Data Facility (SRDF) is a business continuance solution that maintains a device-level mirror of Symmetrix data on remotely attached Symmetrix arrays. These arrays also may be located in physically separate sites. SRDF provides a recovery solution for component or site failures using remotely mirrored devices. SRDF reduces backup and recovery costs and significantly reduces recovery time after a disaster. For more information, refer to the EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide.




https://support.emc.com/



https://support.emc.com/


Configuring IBM i devices

Configuring devices can be done by a number of ways, including:

◆ “Dell EMC configuration request” on page 29

◆ “VMAX3 D910 configuration using symconfigure” on page 29

◆ “VMAX D910 configuration using symconfigure scripts” on page 32

◆ “Creating 2107 devices using symmconfigure script” on page 34

◆ “VMAX D910 configuration using symconfigure scripts” on page 32

◆ “VMAX configuration using Unisphere for VMAX” on page 37

Dell EMCconfiguration request

Requesting Dell EMC Engineer to create the desired device configuration via an Dell EMC Configuration request change. This is then built and vetted via internal Dell EMC Change Control and loaded by the engineer.

VMAX3 D910configuration using

symconfigure

Note: For more information on D910, refer to the Implementing D910 Devices on EMC VMAX3 Storage Arrays (VMAX 100K, 200K, and 400K models) white paper located at Dell EMC Online Support.

Prior to creating the D910 devices, the following key points must be considered.

Thin devices (TDEV) Thin devices for Virtual Provisioning are devices that do not have storage allocated to them when they are created. Thin devices can be created with an inflated capacity, because the actual storage space for the data written to the thin devices is on the DATA devices.To a host operating system, they look like regular devices with their configured capacity. The host treats them as regular devices and writes and reads from these devices like regular devices. For more information, refer to the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide.

Virtual devices A host-accessible device containing track-level location information (pointers), which indicates where the copy session data is located in the physical storage. Device copies use virtual devices to support TF/Snap operations. Virtual devices consume minimal physical disk storage, as they store only the address pointers to the data stored on the source device or a pool of SAVE devices. For more information, refer to the EMC Solutions Enabler SRDF Family CLI User Guide.



Creating devices 29





◆ The D910 device created will report a capacity on the VMAX3; however, due to the 4 KB page sector conversion from 8x 520 bytes sectors to 9x 512 bytes sectors done by IBM i for D910 attachment, the reported usable IBM i capacity is less than the configured D910 LUN capacity.

IBM i LIC Load Source requirements for IBM i 6.1, 7.1 and 7.2

◆ IBM stated that for IBM i 6.1 is the minimum required size for the load source device must be 17.5 GB (usable space)

◆ IBM stated that for IBM i 7.1 is the minimum required size for the load source device must be 35 GB (usable space)

◆ IBM stated that for the initial release of IBM i 7.2 that the load source device must be 70 GB (usable)

◆ With the introduction of IBM i 7.2 TR1, the load source sizes have been amended to 35 GB usable (from the above figure of 70 GB).

The following table shows (for a VMAX 3 with 128K track size) the reported and usable sizes of the devices when created with the cylinder count specified in the left-hand column:

To size the remaining devices and the number of devices required for the IBM i host, a full performance review should be conducted prior to any proposed migration to ensure that sufficient devices of the correct size are created.

Note: The Dell EMC IBM i Global Practice team can assist with the performance review and can be engaged early in the design process to ensure host performance following the migration.

Matching source and replications target devices is required. It is important to understand the source device count/capacities that are required and ensure in a replicated environment that the equal target devices are created.

The following is an example of the Solutions Enabler symconfigure command used to create a device for use on an IBM i system.

Note: With VMAX3 running HYPERMAX OS, there is no support for meta devices.

The first command, shown with the preview option, checks the change proposed in the symconfigure command to create a single D910 device with a size of 20600 cylinders (which would produce a single device for host usage and would present as 36,001 MB capacity on the host).

symconfigure -sid xxx -cmd "create dev count=1, size=20600 cyl,emulation=as/400_D910_099, config=tdev;" -nop preview

VMAX 3 Cylinder Count Array reported Capacity (MB) Host reported Capacity (MB)

20600 38,625 36,001

41200 77,250 72,002

82400 154,500 144,004



The symconfigure command shown with the "commit" option, performs the required change and creates the device. The output from the command will show the device identifier created (see the following example, which shows a single device being created with a size of 20600 cylinders and the TDEV created is "symdev 154".)

symconfigure -sid xxx -cmd "create dev count=1, size=20600 cyl, emulation=as/400_D910_099, config=tdev;" -nop commit

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.Processing symmetrix 000xxxxxxxxxPerforming Access checks..................................Allowed.Checking Device Reservations..............................Allowed.Initiating COMMIT of configuration changes................Queued.COMMIT requesting required resources......................Obtained.Step 004 of 017 steps.....................................Executing.Step 004 of 017 steps.....................................Executing.Step 007 of 017 steps.....................................Executing.Step 011 of 017 steps.....................................Executing.Step 012 of 017 steps.....................................Executing.Step 012 of 017 steps.....................................Executing.Step 015 of 017 steps.....................................Executing.Local: COMMIT............................................Done.

New symdev: 00154 [TDEV]Terminating the configuration change session..............Done.

The following symconfigure command, creates a single device and also adds the newly created device to a previously defined storage group (called sg1 in this example).

Note: If the storage group is part of an active masking view then the device will be presented to the host upon creation.

symconfigure -sid xxx -cmd "create dev count=1, size=20600 cyl,emulation=as/400_D910_099, config=tdev, sg=sg1;" -nop commit

For details on how to create and manage storage groups on the VMAX3 array, refer to the EMC Solutions Enabler Array Management CLI User Guide, available at Dell EMC Online Support.

The symconfigure command will not check whether adding a device to a storage group will cause the host IOA limitation of devices per path to be exceeded (64 devices per port of an IBM Smart IOA) and care must be taken when making configuration changes to ensure that IBM limitations are not exceeded.

To create a D910 gatekeeper device, the following command will create a single D910 device, automatically setting the size to 3 cylinders and with the correct GK flag correctly set.

symconfigure -sid xxx -cmd "create gatekeeper count=1, emulation=as/400_D910_099,;"-nop

commit

At this point, care must be taken when adding the newly created gatekeeper device to a storage group to ensure that the device remains single pathed (the Dell EMC STM product for which the gatekeeper device is required does not support multipathed gatekeepers).

Creating devices 31







There is no requirement to create TDAT devices as these devices and the storage resource pools are pre-configured in the factory. The only requirement following the D910 device creation is to add the newly created D910 devices to a storage group,

the following shows an example of the command to add D910 devices to a storage group. In this example, the D910 devices 84B:88A are added to storage group SG1.

symaccess -sid xxx -name sg1 -type stor add devs 84B:88A

When that storage group is part of an active masking view on the VMAX3 array, then the D910 device will be presented to the IBM i host.

VMAX D910configuration using

symconfigure scripts

Device sizing and capacity planning should be determined before proceeding with the creation steps. Load Source device should be about 70 GB unless you plan to migrate from something larger.

Matching up source and replications targets is required. It is important to know what source device count/capacities are needed.

Note: The following commands require the use of Solutions Enabler v7.4 and later. Refer to the EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide for more information.

Note: More information on D910 can be found in the Implementing D910 Devices on EMC Symmetrix VMAX 40K and VMAX 20K/VMAX Storage Arrays White Paper, located at Dell EMC Online Support.

IMPORTANT

Take note of the device range as you create since they will be referenced again as you proceed. Device count and size values used in this section are for example purposes.

The following is an example of the process and Solutions Enabler commands used to create a set of devices for use on an IBM i System.

1. Create standard thin devices with D910 emulation.

Symconfigure –sid xxx –cmd “create dev count=15, size=90000, emulation=as/400_d910_099,config=tdev;” commit –nop

2. Create pool devices of various protections in preparation for use in the subsequent examples.

IMPORTANT

Considerations need to be made when choosing COUNT and SIZE so that the replication pools match with the source pool and their corresponding THIN devices (created in the above example).

Symconfigure -sid xx -cmd "create dev count=15, config=2-Way-Mir, attribute=datadev,emulation=FBA, size=90000, disk_group=x;" commit –nop

Note: This device creation would be used for a two-way mirrored configuration. See the following examples of RAID 5 and RAID 6 configurations.





Symconfigure -sid xx -cmd "create dev count=15, config=RAID-5, data_member_count=3,attribute=datadev, emulation=FBA, size=90000, disk_group=x;" commit –nop

Symconfigure -sid xx -cmd "create dev count=15, config=RAID-6, data_member_count=6,attribute=datadev, emulation=FBA, size=90000, disk_group=x;" commit –nop

An example SYMCLI device creation output is shown below:

A Configuration Change operation is in progress. Please wait...Establishing a configuration change session...............Established.Performing Access checks..................................Allowed.Checking Device Reservations..............................Allowed.Submitting configuration changes..........................SubmittedValidating configuration changes..........................Validated.

New symdevs: XXX:YYYYInitiating PREPARE of configuration changes...............Prepared.Initiating COMMIT of configuration changes................Queued.COMMIT requesting required resources......................Obtained.Step 004 of 078 steps.....................................Executing.Step 015 of 078 steps.....................................Executing.Step 020 of 078 steps.....................................Executing.Step 125 of 173 steps.....................................Executing.Step 125 of 173 steps.....................................Executing.Step 130 of 173 steps.....................................Executing.Local: COMMIT............................................Done.Terminating the configuration change session..............Done.

The configuration change session has successfully completed.

3. Create Virtual Pools for the data devices.

Symconfigure -sid xxx -cmd "create pool FC_R1_VP type=thin;" commit -nop

4. Display the data devices.

The following is an example of the SYMCLI list datadev command used to view the device just created.

Symdev list -sid xxx -datadev

Symmetrix ID: 000190103334Device Name Directors Device Cap Sym PhysicalSA :P DA :IT Config Attribute Sts (MB)--------------------------- ------------- -------------------------------------10E4 Not Visible ???:? 01A:C4 2-Way Mir N/A (DT) RW 431410E5 Not Visible ???:? 16C:D4 2-Way Mir N/A (DT) RW 431410E6 Not Visible ???:? 15B:D4 2-Way Mir N/A (DT) RW 431410E7 Not Visible ???:? 02D:C4 2-Way Mir N/A (DT) RW 431410E8 Not Visible ???:? 16A:D4 2-Way Mir N/A (DT) RW 4314

5. Add TDAT devices to the Virtual Pools.

The following command adds storage (TDAT devices) to the pool entities. The correct devices in your environment must be identified and referenced in the commands below:

Symconfigure -sid xxx -cmd "add dev xxx:xxx to pool FC_R1_VP type=thin,member_state=ENABLE;" commit -nop

6. Bind D910 TDEVs to the Virtual Pools.

Symconfigure -sid xxx -cmd "bind tdev xxx:xxx to pool FC_R1_VP;" commit -nop

Note: Choose the second set of 5 devices created in step 1.

7. Create AS400 D910 GK devices for SRDF TimeFinder Manager (STM) use.

Creating devices 33


Symconfigure –sid xxx –cmd “create gatekeeper count=3, emulation=as/400_d910_099;” commit -nop

8. Create D910 devices for clone use.

The following are examples of similar commands needed to create clone and BCV devices.

Symconfigure –sid xxx –cmd “create dev count=15, size=90000, emulation=as/400_d910_099config=tdev;” commit –nop

Symconfigure -sid xx -cmd "create dev count=15, config=2-Way-Mir, attribute=datadev,emulation=FBA, size=90000, disk_group=x

Creating 2107 devicesusing symmconfigure

script

This section will briefly describe how to create devices using the Symconfigure script.

Beginning at Dell EMC Enginuity v5773 with a minimum Solutions Enabler v6.5.1, it is possible to create meta devices using the auto_meta feature, which allows the user to create a meta device in a single configuration change session without first having to create single devices and then combining these devices to form a meta device. There are a number of array wide settings that need to be implemented on the array, as documented in the EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide, available on Dell EMC Online Support.

The process of creating IBM i server metadevices has been simplified. All IBM i server devices are of a fixed size depending on the emulation type selected. Therefore, with Solutions Enabler v6.5.1, running Enginuity v5773, the size field is optional since Solutions Enabler determines the size automatically from the emulation type.

When auto_meta is enabled, Solutions Enabler attempts to create an IBM i server metadevice with or without a size value entered.

When auto_meta is disabled, Solutions Enabler attempts to create an IBM i server non-metadevice, but will reject a request to create an IBM i server metadevice.

Example

The symconfigure -sid 560 -f create.txt -v commit command creates an IBM i server metadevice on a Symmetrix DMX array with emulation AS/400_M2107_A05, where the create.txt file contains the following:

create dev count=1, emulation= AS/400_M2107_A05, config=2-Way-Mir





This creates a four-member metadevice with a total cylinder size of 35784 (4*8946), as shown in the following screen:

VMAX3 configurationusing Unisphere

This section will briefly describe how to create a D910 emulation device using the Unisphere appliance.

The following shows the parameters required during the "create volume" process to create a single D910 device.

In the first example a single D910 device of 50,000 cylinders will be create.

Creating devices 35


Once the device is created, the new device (TDEV 301) can be viewed within Unisphere and then added to the required storage group, as shown in the following example.

Alternatively, you can specify the required storage group during device creation as the following example shows, which will create a single D910 device and add it to a storage group, called "NewGroup" in this example.

To present the newly created devices to the IBM i host, dependent on the proposed configuration, there are a few options:



◆ In a direct connect environment where ACLX is not to be used, the newly created devices will require addressing on the FA ports to which the host is to connect.

◆ In all other cases, either direct connection or a switched connection, where ACLX is to be used, there is no requirement to address the D910 device on the FA port to which the host connects.

With VMAX3 and HYPERMAX OS, the use of symaccess automatically addresses the devices on the FA ports when a symaccess masking view is created.

Both of the above actions are completed using the Dell EMC Solutions Enabler product. Full details of the commands and syntax can be found in the EMC Solutions Enabler Array Management CLI User Guide, located at Dell EMC Online Support.

VMAX configurationusing Unisphere for

VMAX

This section will briefly describe configuring through Unisphere for VMAX and viewing the created devices using CLI. For a complete reference to using Unisphere for VMAX, SMC, and Solutions Enabler/symmconfigure, refer to the technical documentation on Dell EMC Online Support.

To configure IBM i devices using Unisphere, complete the following steps.

1. Log in to Unisphere for VMAX, as shown in Figure 2. This will run a discover.

This step ensures that the local SYMAPI database is in synch with that of the array.

Figure 2 EMC Unisphere for VMAX

Creating devices 37






2. On the Home page, select your Symmetrix system, as shown in Figure 3.

Figure 3 Unisphere for VMAX Home Page

3. Select the Storage tab and then select Create volumes in the Common Tasks pane on the right, as shown in Figure 4.

Figure 4 Storage tab



The Create Volumes dialog box displays, as shown in Figure 5.

Figure 5 Create Volumes dialog box

4. In the Create Volumes dialog box, select the disk technology, a host emulation type, the data protection, the number of volumes, and the capacity of the volumes you want to create. You can create these volumes immediately by clicking Run Now, or schedule them to be created later by clicking Add to Job List.

Refer to Table 3 on page 24 for more information on host devices and their Symmetrix data structure.

Using Unisphere to create 2105 or 2107 devices will automatically use Solution Enabler's Auto Meta feature. Refer to “Enabling Auto Meta” on page 39 for more information.

Note: VMAX 10K xxx987xxxx only supports D910 devices.

Refer to the Unisphere online help for more information on restrictions and limitations.

5. If you selected Add to Job List, you can click Job List in the bottom part of the Common Tasks pane to manage scheduled configuration changes.

Enabling Auto Meta

Another way to create volumes in Unisphere is to enable Auto Meta first, then simply ask for one 2107-A05. Auto Meta correctly sets it up and give you four members of the correct size and meta in one action.

To enable Auto Meta and set the system attributes, complete the following steps.

1. Select the Symmetrix system.

Creating devices 39


2. Select System > Settings > Symmetrix Attributes to open the Symmetrix Attributes dialog box.

3. Set or modify the default values for any number of the following system attributes:

• Hot Swap Policy. Specify whether to use global sparing. Select one of the following values:– Permanent - Use global sparing.– Temporary - Do not use global sparing.

• VCMDB Access Restricted. Specify whether the VCM database can be accessed on this Symmetrix system.

4. Specify whether or not to use the Auto Meta feature.

Select to enable or clear to disable.

If Auto Meta is enabled, set the following properties:

• Minimum Meta Capacity - Enter the minimum volume size that will trigger the creation of a meta volume.

• Member Capacity - Enter the size of the meta members to use when creating meta volumes.

• For Enginuity 5874, this value must be less than or equal to 525336 cylinders, if running in 32K compatibility mode; or 262668 cylinders, if running in native mode.

• Configuration - Enter the meta configuration as either Concatenated or Striped when creating meta volumes.

• When enabled and attempting to create a volume larger than the value specified in the Minimum Meta Capacity field or larger than 59 GB, will automatically trigger the creation of a meta volume according to the values specified in the Member Capacity and Configuration fields.

• PAV - Specify the maximum number of aliases that can be assigned to a volume.

• This panel only displays only for Symmetrix systems with either ESCON or FICON directors.

For z/OS only, set the following parameters:

• Alias Limit. Enter the maximum number of aliases that can be assigned to a volume.

• Mode. Select the one of the following PAV types:

– NoPAV. PAV not configured for the Symmetrix system. – Standard PAV. Volumes with static aliasing. – Dynamic Standard PAV. Standard PAV volumes with dynamic aliasing.

• SRDF. Specify the following SRDF parameters:

– Maximum Cache Usage (Percent) - Type the maximum percentage of system write-pending cache slots for all RDF/A sessions. Valid values are 0 to 100.

– Maximum Host Throttle (Secs) - Type the maximum percentage of system write-pending cache slots for all RDF/A sessions. Valid values are 0 to 65535.

5. Click Apply.



The Create Volume dialog box shown in Figure 6 on page 41 shows the volume request with Auto Meta enabled, requesting one A05.

Figure 6 Volume request with Auto Meta enabled, requesting one A05

Creating devices 41


Viewing devices fromSYMCLI

Like all volumes, when viewed through Dell EMC software, the information is displayed in a different format. The following example is from SYMCLI showing the devices just created (8 x 2107_A05 devices created, two of which are shown here):

uklonrdcsun2# symdev list -sid 114 |more

Symmetrix ID: 000290101114

Device Name Directors Device--------------------------- ------------- -------------------------------------

CapSym Physical SA :P DA :IT Config Attribute Sts (MB)--------------------------- ------------- -------------------------------------03E0 Not Visible ???:? 02A:D6 BCV+R-5 N/Asst'd (M) RW 3407203E1 Not Visible ???:? 01B:D6 BCV+R-5 N/Asst'd (m) RW -03E2 Not Visible ???:? 01A:C6 BCV+R-5 N/Asst'd (m) RW -03E3 Not Visible ???:? 02B:C6 BCV+R-5 N/Asst'd (m) RW -03E4 Not Visible ???:? 02A:D6 BCV+R-5 N/Asst'd (M) RW 3407203E5 Not Visible ???:? 01B:D6 BCV+R-5 N/Asst'd (m) RW -03E6 Not Visible ???:? 01A:C6 BCV+R-5 N/Asst'd (m) RW -03E7 Not Visible ???:? 02B:C6 BCV+R-5 N/Asst'd (m) RW



Setting the Fibre Channel portUsing Solutions Enabler, you can configure the Fibre Channel port for use in an IBM i environment for either a direct connection of the IOA to FA port, or through a SAN connection. This section discusses the necessary director bit setting required to connect to the IBM i Host using these two methods.

For the most up-to-date information on configuring the director settings, refer to the Dell EMC Simple Support Matrix and to the EMC Knowledge Base article emc193938.

This section includes the following information:

◆ “FA director settings” on page 43

◆ “VMAX3 D910 Connect via switch (SAN)” on page 43

◆ “VMAX3 D910 Direct Connect” on page 44

◆ “VMAX D910 Connect via switch (SAN)” on page 44

◆ “D910 Direct Connect (with no SAN)” on page 44

◆ “2107/2105 Direct Connect (with no SAN)” on page 45

◆ “2107/2105 Connect via switch (SAN)” on page 45

◆ “Fibre protocol port flags” on page 46

◆ “Setting front end port characteristics” on page 46

◆ “Open systems gatekeeper devices sharing a FA port with IBM i data devices” on page 49

FA director settings

The following shows required and optional FA director settings for each device emulation type.

VMAX3 D910 Connect via switch (SAN)

In order to set up the FA port for use in an environment with switch connectivity, the FA port settings should be configured with the following parameters.

Setting the Fibre Channel port 43




◆ Point to Point (PP) = Yes

◆ Access_Logix (ACLX) = Optional

No other port flags are required —Link Speed by default is set to auto.

VMAX3 D910 Direct Connect

In order to set up the FA port for use in an environment with no switch connectivity, the FA port settings should be configured with the following parameters:

◆ Access_Logix (ACLX) = Optional

No other port flags are required — Link Speed by default is set to auto.

VMAX D910 Connect via switch (SAN)

In order to set up the FA port for use in an environment with switch connectivity, the FA port settings should be configured with the following parameters.

◆ Loop ID = Default

◆ Common SN (C) = Yes

◆ Unique Worldwide (UWN) = Yes

◆ Point To Point (PP) = Yes

◆ Access Logix (ACLX) = Optional

This setting is used as a best practice in managing new LUNs or when the same initiator (IOA) and LPAR is used for addressing different images in various scenarios (such as TimeFinder Volumes for daily use or a DR image for disaster recovery).

◆ Auto-negotiate (EAN) = Yes

Note: AS4 flag is set to "no"

D910 Direct Connect (with no SAN)


◆ Loop ID = Default (although 7D has traditionally been used)

◆ Common SN = Yes

◆ Unique Worldwide (UWN) = Yes

◆ Access Logix (ACLX) = Optional


◆ Enable Auto Negotiation (EAN) = Yes

Note: AS4 flag is set to "no"



2107/2105 Direct Connect (with no SAN)


◆ Loop ID = Default (although 7D has traditionally been used)

◆ Enable Volume = Yes (V)

◆ Unique Worldwide = Yes (UWN)

◆ FA IBM i server = Yes (AS4)

◆ ACLX or VCM

This setting is optional and is used as a best practice in managing new LUNs or when the same initiator (IOA) and LPAR is used for addressing different images in various scenarios (such as TimeFinder Volumes for daily use or a DR image for disaster recovery).

◆ FA link speed should be specified to the IOA speed setting: 4 or 8 GB, as follows:

• 4 GB with the #5760 [V5R3] and [#5749, #5774 with V6R1]

• 8 GB with the #5735 [VxRx] and [IBM i 6.1.1 with VxRx]

2107/2105 Connect via switch (SAN)

In order to set up the FA port for use in an environment with switch connectivity, the FA port settings should be configured with the following parameters:

◆ Loop ID = Default

◆ Enable Volume Set Addressing = Yes (V)

◆ Unique Worldwide = Yes (UWN)

◆ Point To Point = Yes (PP)

◆ FA IBM i server = Yes (AS4)

◆ VCM (Optional)


◆ EAN (Optional)

This setting is optional or set to required speed setting.



Fibre protocol port flags

Table 5 lists the Fibre protocol flags and their descriptions.

Setting front end port characteristics

Unisphere for VMAX or the symconfigure command can be used to set the front end port characteristics. In this section, the use of the symconfigure command will be demonstrated. This section will demonstrate the changes on a VAMX3 array using SE8.

It is recommended that you check the current FA port settings by running the following command:

Symfg -sid xxx -dir 1E -p 8 list -v

Table 5 Fibre protocol port flags

Fibre protocol flags Description

ACLX When enabled, allows storage provisioning using Auto-provisioning Groups. This flag is applicable for Enginuity 5874 and higher.

AS/400 This flag should be enabled for any AS/400 (iSeries) hosts connecting to the port.

Auto_Negotiate When enabled, allows two fibre ports to handshake and settle on an optimal speed for data transfer.

Class_2_Service a,b This flag should be enabled for a Class 2 fibre protocol connection that requires an acknowledgement for each frame transmitted. (You cannot change this flag.)

Disk_Array a When enabled (default), the port is represented as a disk array. This port information appears in the Inquiry data.

Generic_VSA ab When enabled, the generic volume set addressing mode is selected. GVSA mode allows hexadecimal addressing. (You cannot change this flag.)

Global__3rdParty_Logout a

When enabled (default), an extension is provided to the existing third-party logout required by the standard. In addition to logging out the hosts who are logged in to the port receiving the third-party logout, the logout propagates to other Symmetrix fibre ports that share volumes with the port that had received the logout.

Hard_Addressing a When enabled (default), the FA director attempts to get the loop_id specified when it initializes on the loop (hard-assigned addressing). When disabled, soft addressing is being used.

Init_Point_to_Point c When enabled, specifies a point-to-point (direct or switched) topology in the initialization sequence. When disabled (default), it is initialized as an arbitrated loop.

Non_Participating c When enabled along with the Hard_Addressing flag, the Fibre Channel director only uses hard-assigned addressing when it initializes on the loop. Otherwise, soft-assigned addressing is used during loop initialization (the default).

OpenVMS Enabled for an OpenVMS fibre connection.

Unique_WWN c When enabled (default) for all environment configuration changes and new environments to ensure unique World Wide Names (WWN) within the fibre environment (uses Symmetrix serial numbers and port numbers). When disabled, you don’t have to change WWNs.

VCM_State d Enabled for device masking or the Volume Logix software, which provides volume configuration management controls to handle access to Symmetrix devices. (Disabled is the default.) This flag is only applicable for Enginuity 5773 and earlier.

Volume_Set_Addressing When enabled along with the Disk_Array flag for HP-UX hosts, the volume set addressing mode is selected. VSA mode allows octal addressing.

a.Obsolete in Enginuity version 68 and higher.b.Not available for host-based configuration changes.c.Not available for Gig-E ports.d.Obsolete in Enginuity 5874 and higher.



The trunkated output from this command is shown below:

In this example, it can be seen that the SC3 and OS2007 director flags are set incorrectly for an IBM i host with D910 emulation devices being presented to this FA port. Therefore, these port flags have to be disabled.

In order to make the certain changes to the FA port flags, the port must be offline.

Assuming it is safe to proceed, take the port offline as follows.

The following command will take the port FA 1E:11 offline:

Symcg -sid xxx -fa 1e -p 11 offline

With the FA port offline, the following symconfigure command can be run to disable the two port flags that are not required (SC3 and OS2007):

Symconfigure -sid xxx -cmd "set port 1E:11 SPC2_Protocol_Version=disable, SCSI_3=disable;" commit -v -nop



The following output is truncated.

Once the command completes successfully, the port flags can be validated to confirm that they are now correct. The following output from the port shows that the command has successfully amended the port flags and that the flags are now correct.

Note: The Common_Serial_Number (C) is permanently enabled and cannot be disabled.

Remember to bring the port back on line when all the changes have been completed by issuing the following command:

Symcg -sid xxx -fa 1e -p 11 online -nop

If you want to copy all the settings from one FA port (which is correctly set) to another FA port, issue the following command once both of the ports are offline.



Note: The source FA port must be offline. If you are changing certain FA flags (such as the EAN flag), then the target FA must also be offline.

Symconfigure -sid xxx -cmd "set port 1E:9 copying port 1E:8;" -v commit -noprompt

Finally, set both ports back online.

Open systems devices with IBM i D910

◆ Open systems data devices are only allowed to be mixed on the same port or on the same processor as IBM i D910 devices. However, the use of ACLX is required.

◆ When sharing an FA port between an IBM i host and an Open Systems host that have different FA port flag settings, use of the initiator overrides will be required.

Details on this process can be found in the EMC Solutions Enabler Array Management CLI User Guide, available at Dell EMC Online Support.

◆ The initiator override options are detailed in “Overriding the HBA flags” on page 51, for the specific case of sharing an Open Systems gatekeeper device with IBM i data devices. The same process can be followed when sharing D910 and Open System host devices on the same FA port, though the port settings required must be confirmed at Dell EMC E-Lab Interoperability Navigator.

◆ On a multi-port host adapter (IOA only), one port can address 2107 emulations and the other port can address D910 emulations.

Open systems gatekeeper devices sharing a FA port with IBM i data devices

Pre-requisites VMAX arrays running a minimum Enginuity code of 5874.248.194 with a special build (available on request; for details see Dell EMC Knowledgebase solution emc253605).

The fix is included in Enginuity versions 5874.259.201 and 5875.198.148.

VMAX3 arrays running HYPERMAX code. Dell EMC recommends using the latest target code.

Host OS

No prerequisites other than the VMAX 40K, VMAX 20K/VMAX, and VMAX 10K xxx987xxxx requirements for each host as detailed in the Dell EMC Simple Support Matrix (ESM).

Configurationrequirements

Consider the following requirements:











◆ Open systems data devices are not allowed to be mixed on the same port or on the same processor as mapped IBM i devices.

◆ IBM i device (2107-Axx) mapped to a VMAX host adapter can be mixed on the port or on the processor with open systems gatekeeper devices.

◆ The preferred configuration method would be to use the port flag ACLX with required device masking as there is an additional check to make sure only open systems gatekeeper type devices are being mixed in.

◆ The AS4 flag must be enabled on both FA ports on the processor.

◆ Prior to the Enginuity v5874, mixing IBM i devices with open systems devices on a port is not allowed. Open systems data devices are also not allowed to be mixed on the same processor as mapped IBM i devices. An RPQ is required for open systems gatekeeper devices to be mixed on the same processor with IBM i devices.

The following extract shows the output from the SYMCLI command:

Symcfg -sid xxx -dir nnx -p x list -v

This shows the bit settings for the FA port. (The EAN bit setting is optional.)

Fibre Specific Flags{

Volume_Set Addressing (V): EnabledNon_Participating (NP) : DisabledInit_Point_to_Point(PP) : EnabledUnique_WWN (UWN) : EnabledAccess_Logix (ACLX) : EnabledOpenVMX (OVMS) : DisabledAS400 (AS4) : EnabledAuto_Negotiate (EAN) : Enabled

Note: the AS4 flag must be enabled on both ports of the FA, however it is not necessary to enable the ACLX bit setting on both ports, it is only required on the port where device sharing between Open Systems GKs and the IBM i data devices will occur.

The only other configuration requirement is that the ACLX volume is not addressed on the shared port path. Presenting the ACLX volume on the IBM i host FA path will cause hardware errors on the IBM i host (even though the device is not part of the IBM i storage group).

symaccess The use of the ACLX bit on the FA allows for the use of symaccess (which is only available on VMAX 400K, VMAX 200K, VMAX 100K, VMAX 40K, VMAX 20K/VMAX, and VMAX 10K xxx987xxxx arrays).

The initial symaccess requirement will be to create two views:

◆ One contains the IBM i devices

◆ One contains the Windows gatekeeper devices

Each view shares the same port group (which is the FA port where the ACLX bit is set); however each view has different storage and initiator groups. It is the initiator groups that provide the key to this process of sharing the single FA port.



The IBM i initiator group requires no additional configuration and should operate without issue. The Windows initiator group does require additional configuration to allow the Windows host to "discover" the array.

Overriding the HBAflags

You can override the HBA flags for the Windows Initiator group, which contains the gatekeeper devices, using Unisphere for VMAX, or the symconfigure commands, each explained further in this section:

◆ “Using Unisphere for VMAX” on page 51

◆ “Using SYMCLI” on page 52

Using Unisphere for VMAX

1. Log in to Unisphere for VMAX and select the array.

2. Select Initiator Groups in the Hosts section.

3. Select the Initiator Group that requires amending (in this case App4) and click Set Flags, as shown next.



The Set Initiator Group Flags window displays, as shown next.

4. Select the Port flags that you need to override and ensure that the Enable box is not checked.

5. To enable the required Open Systems HBA flags, check the Override check box next to the flag and click the Enable check box on the required HBA flag.

Note: This screen shows only an example of the settings. The exact settings that will be required for the Open Systems host can extracted from the Dell EMC Simple Support Matrix, available through Dell EMC E-Lab Interoperability Navigator.

6. Click OK to confirm the settings.

Using SYMCLI

To set a flag for an initiator group, using SYMCLI, use the following syntax:

symaccess -sid xxx -name ig_name -type initiator set ig_flags <on <flag> <-enable |-disable>| off [flag]>

For example:

To set the OS2009 [OS2009] for the initiator group my_ig on Symmetrix 266:

symaccess -sid 266 -type init -name my_ig set ig_flags on OS2009 -enable

For further details see the EMC Solutions Enabler Symmetrix Array Controls CLI Version 8 Product Guide, located on message URL Dell EMC Online Support.

Note: The combined settings of the FA bit settings in the current bin file and the settings that are applied with the override options that are valid for the initiator group. In effect, this change removes the AS4 and the V bit from the FA port and adds in the Windows bit settings that are required.







To check the settings for the initiator group issue the following SYMCLI command:

symaccess -sid xxx show "init_group" -type init -detail > yourfile.txt

The output for this command is as follows:

This shows for the gatekeeper initiator group that the HBA port flag overrides are active, the AS4 and V bit settings have been disabled, and the four required settings for the Windows server have been enabled.

The effect of this process has been to create a specific set of bit settings for this initiator group on this FA port that override the bit settings that are active. However, the settings only apply to this group. The other initiator group for the IBM i devices will still use the FA port settings as defined in the bin file as there are no port flag overrides active for this group.

Once the process has been completed, it may be necessary to reboot the Windows host for the changes to be effective.

Note: Refer to “Gatekeepers” on page 61 for details on where the adverse impact of Open systems Gatekeepers on the same front end adaptor as the IBM i host is detailed.

IMPORTANT

The agents from EMC Unisphere can have a dramatic effect on performance if monitoring is aggressive.

The previous statements in this section all apply to the mixing of IBM i and Open Systems on a FA processor/port. These restrictions do not apply to the sharing of a FA processor or port by multiple IBM i partitions.



Using device masking, it is possible to assign to assign specific volumes mapped to a storage port to a specific host initiator. For further details, refer to “IBM i zoning and masking” on page 60. Therefore, multiple IBM i initiators can be zoned to a single FA port, known as "fan in."

IBM recommendations state that a single IBM i partition can present more than one IOA to the same FA port; however, Dell EMC has implemented multiple partitions using the same FA port with little performance degradation. It is still considered a best practice to follow the IBM recommendations, however, and where "fan in" is being utilized, present initiators from a single IBM i partition to an FA port rather than mix initiators from separate partitions on the same port.

Where physical constraints dictate, for example where the number of required connections exceeds the number of physical ports, "fan in" can be used, ensuring where possible that the above recommendation of not presenting initiators from multiple IBM i partitions to a single FA port is followed.

Due to variables, such as the number and size of the LUNs or the disk technology supporting them, it is not possible within this guide for Dell EMC to recommend the amount of "fan ins" that should be implemented.

In such a scenario, Dell EMC recommends that you engage the Dell EMC IBM i Global Practice group (refer to “Dell EMC IBM i Global Practice” on page 9) to conduct a detailed performance analysis of the host to determine the I/O workload and, based on the utilisation rates of the FA ports, make recommendations on the level of "fan in" to be applied.



SAN connectivity and other optionsThis section information when booting from SAN.

Note: For EMC customers only: Dell EMC E-Lab Interoperability Navigator contains the latest matrix listing supported IBM i models, operating environments, and hardware qualified for use with Dell EMC SRDF/TimeFinder Manager for i5/OS.

With V5R2, IBM fully supported the use of SAN-connected storage, though in the first releases SAN boot was not supported. However, in V5R3M5, this restriction was lifted and now all the storage can be SAN connected.

Dell EMC supported SAN-connected storage since the Symmetrix 8000 model. All the current Dell EMC VMAX3, VMAX and DMX models fully support SAN boot and SAN storage.

In the intervening period between the initial release of SAN storage and the release of the SAN boot capability by IBM, the load source device could be maintained internally as an IBM device; however, to take advantage of Dell EMC's remote data facility (RDF) an internal load source emulator was introduced that allowed the load source data to reside in the Symmetrix DMX, and therefore be part of the replicated data. The load source emulator had specific configuration requirements in terms of director bit settings. There was also a requirement to remove the cache card from the IBM IOA that controlled the load source emulator.

The load source emulator is now "end of life" and therefore is no longer supported in new configurations (without an RPQ). Therefore, the required configuration settings for this device are not included in this guide.

Since the introduction of SAN boot capability on V5R3M5, the load source device can be presented on the SAN. However, there are specific IBM hardware requirements to utilise this functionality, which are detailed below for the various OS and hardware releases.

From the Symmetrix VMAX3, VMAX and DMX perspective, the FA port settings for SAN storage can be found in “Setting the Fibre Channel port” on page 43.

Note: The use of a suitable switch as listed in the Dell EMC Simple Support Matrix is required.

The customer must check the IBM hardware prerequisite site at https://www-912.ibm.com/e_dir/eServerPrereq.nsf, to confirm that the feature cards that they are planning to use are fully supported at their OS/ptf levels.

IBM i HBAs are identified by both the feature code and the Customer Card Identification Number (CCIN). The feature code is a four-digit code used when ordering hardware, and is also used by the Hardware Management Console and Integrated Virtualization Manager while assigning hardware resources. The CCIN is also a four-digit code and it is the Licensed Internal Codes representation of the

SAN connectivity and other options 55







hardware feature. Different feature cards can have the same CCIN; for example, the 5273 and 5735 both have a CCIN of 5735. Different CCINs can exist for the same feature card. Refer to the Table 6.

V5R4M5 - Power 5 andPower 5+

2847 IOP is required to control the IBM IOA which is connected to the VMAX3, VMAX, and Symmetrix DMX FA port on which the load source device is presented.

IMPORTANT

The load source cannot be multipathed at this level of OS. To fully protect the load source, Dell EMC recommends that you utilise the IBM remote load source mirroring option within the OS. However, for full resilience and recovery, it is recommended that

Table 6 HBA card type and IBM i versions

System HBA Card Type IBM i Versions

POWER8 Systems Feature Code/CCIN

5276/5774 4-Gb PCIe Smart IOA IBM i 7.1, IBM i 7.2

5273/577D 8-Gb PCIe Smart IOA IBM i 7.1 IBM i 7.2

5735/577D 8-Gb PCIe Smart IOA IBM i 7.1, IBM i 7.2

EN0A/577F 16-Gb PCIe Smart IOA IBM i 7.1, IBM i 7.2

EN0B/577F 16-Gb PCIe Smart IOA IBM i7.1, IBM i 7.2


5276/5774 4-Gb PCIe Smart IOA IBM i 6.1.1, IBM i 7.1, IBM i 7.2

5774/5774 4-Gb PCIe Smart IOA IBM i 6.1.1, IBM i 7.1, IBM i 7.2

5749/576B 4-Gb PCI Smart IOA IBM i6.1.1, IBM i7.1, IBM i7.2

5735/577D 8-Gb PCIe Smart IOA IBM i6.1.1, IBM i7.1, IBM i7.2

5273/577D 8-Gb PCIe Smart IOA IBM i 6.1, IBM i 7.1 IBM i 7.2

ENOA/577F 16-Gb PCIe Smart IOA IBM i7.1, IBM i7.2

ENOB/577F 16-Gb PCIe Smart IOA IBM i7.1, IBM i7.2


5774/5774 4-Gb PCIe Smart IOA IBM I 6.1.1, IBM I 7.1, IBM I 7.2

5760/280E 4-Gb PCI-X HBA v5.4.5, IBM i6.1,IBM I 6.1.1,IBM i7.1.

5749/576B 4-Gb PCI-X Smart IOA IBM I 6.1.1, IBM I 7.1, IBM I 7.2

5735/577D 8-Gb PCIe Smart IOA IBM I 6.1.1, IBM I 7.1.0, IBM I 7.2.0

2787/2787 2-Gb PCI-X HBA v5.4.5, IBM i6.1,IBM I 6.1.1,IBM I 7.1


5760/280E 4-Gb PCI-X HBA v5.4.5, IBM I 6.1,IBM I 6.1.1,IBM I 7.1

2887/2787 2-Gb PCI-X HBA v5.4.5, IBM I 6.1IBM I 6.1.1,IBM I 7.1



the load source mirror device is presented on a separate path, which is again controlled by a 2847 IOP. Therefore, a 2107_A8n device must be presented as the load source (A8n represents an unprotected device). The 2847 IOP can support an additional 31 devices in addition to the load source device.

Data volumes do not require the use of a 2847 IOP. A 2844 IOP can be used to control the IBM IOA, which is connected to the VMAX3, VMAX, and Symmetrix DMX FA port on which the data volumes device are presented. The maximum number of devices that can be presented is 32.

For performance reasons, the recommended IOA is the 4 Gb Single-Port Fibre Channel PCI-X 2.0 DDR adapter (FC 1905, 5758, 5760, 5761; CCIN 1910, 280D, 280E).

Protected devices can be presented as data storage devices (2107_A0n).

Multipathing of data volumes is supported at this version of the OS and when completed all devices show as DMP (not DD as a single path would show).

I6.1/i6.1.1 on Power 5 With IBM i6, Smart IOAs (also known as IOP-less IOAs) was introduced. These IOAs can be used in a SAN-connected environment. Careful consideration must be given to the positioning of these feature cards within the racks and configuration.

IBM card placement guidelines must be followed, as noted in the IBM Prerequisite page at https://www-912.ibm.com/e_dir/eServerPrereq.nsf. There are also specific code requirements associated with the use of these feature cards.

At this hardware level the IOP-less IOA cannot support the load source device and a 2847 IOP and associated IOA must still be used to present the load source to the host.

The IBM 4 Gb Dual-Port Fibre Channel PCI-X 2.0 DDR Adapter (FC 5749; CCIN 576B) has the capability to operate on Power 5 or Power 5+ hardware. However, minimum OS and ptf levels must be checked using the IBM Prerequisite page at https://www-912.ibm.com/e_dir/eServerPrereq.nsf. The 5749 adaptor can support up to 64 devices on each port (two ports per adaptor) giving a maximum supported device count of 128 devices per adaptor. Significant consideration must be given to required performance before that quantity of devices is presented.

I6.1/i6.1.1 on Power 6 With the release of the Power 6 hardware, the requirement to use the 2847 IOP was lifted as the Smart IOA feature cards can (at this hardware level) support the load source device.

One implication of this is that there is no requirement to present an unprotected device as the load source (2107_A8n) and all the devices can be presented as protected devices (2107_A0n).

Note: VMAX 10K xxx987xxxx only supports D910 devices.

Another implication is that multipathing of the load source is now possible and that there is no requirement for a remote load source mirror.

All of the above have specific OS requirements and these must be checked using the IBM Prerequisite page at https://www-912.ibm.com/e_dir/eServerPrereq.nsf.

SAN connectivity and other options 57


The 2847 IOP will continue to work on Power 6 hardware. However, as multipath is now supported, it is good practise to end the load source mirroring and multipath the 2107_A8n device (the remote load source mirror device can then be converted to a 2107_A0n device and added to the ASP).

i7 on Power 6 IBM OS i7 can run effectively on Power 6 hardware and there are no changes to the guidelines listed above for running i6 on Power 6.

i7 on Power 7 With the introduction of the IBM Power 7, many of the IOP and IOA feature cards are no longer supported. Refer to the list located on http://www-03.ibm.com/systems/power/hardware/sod2_nosupport.html.

This list includes the 2847 and 2844 IOP plus the 5760 (280E) IOA; therefore, only the three Smart IOAs listed in “I6.1/i6.1.1 on Power 6” on page 57 can be used for SAN connectivity on a Power 7.

The VMAX3, VMAX, and Symmetrix DMX FA port settings are detailed in “Setting the Fibre Channel port” on page 43. The specific settings are dependent on the device emulation (D910 or 2107/2105) in use.

i7 on Power 8 IBM introduced a new PCI-Express Gen3 I/O Drawer, which allows for the installation of PCIe3 FC. However, at the time of writing there are no available PCIe3 Fibre Channel disk controllers for the IBM i host.



Addressing VMAX devices This section contains information on addressing VMAX devices, including:

◆ “Device mapping” on page 59

◆ “IBM i zoning and masking” on page 60

Device mapping

Mapping of IBM i devices is performed on the fibre port of the array. The traditional 2107 LUNs require the FA-port to have the VSA flag enabled (V) in order to use a LUN address scheme called Volume Set Addressing, which conforms to the volume set address VSA rules. This means that the LUN address ranges only use the lower octet of the channel addressing. For example:

00→07, 10→17, 20→ etc.

The FA port limit of how many devices can be addressed is far greater than the capabilities of the hosts IOAs even when you fan-out to multiple IOAs from the same port. Fan-out rules can be located on Dell EMC E-Lab Navigator.

The D910 emulation devices use standard open systems LUN addressing, hence the V port flag is disabled for D910 connections as detailed in “Fibre protocol port flags” on page 46.

The IBM i uses input/output adaptors (IOAs) to address the fibre-attached volumes. Older hardware versions require input output processors (IOPs) in conjunction with IOAs.

IOAs requiring an IOP can physically address up to 32 volumes.

Later IOP-less IOAs or Smart IOAs (those that do not require IOPs) can address up to 64 volumes per port. However, when considering host performance, you should only address a maximum of 70% of the performance capabilities for the IOA.

VMAX3 devicemapping

When configuring the IBM i devices on a DMX or VMAX array, it was possible (and often recommended) to map the IBM i devices to the FA ports on the array - in the case of the DMX adhering to the volume set addressing octet restrictions, and on the VMAX array adhering to the standard lun addressing scheme.

On the VMAX3, the device mapping is automated when ACLX is enabled on the FA port, therefore when a storage group containing D910 emulation devices is associated with a masking view on the VMAX3, the device mapping is automatically assigned.

If ACLX is not used on the VMAX3, potentially in a direct connect configuration, then device mapping is still required, using the standard LUN addressing scheme.Details of masking devices with auto provisioning groups can be found in the EMC Solutions Enabler Array Management CLI User Guide, available at Dell EMC Online Support.

Addressing VMAX devices 59





IBM i zoning and masking

Zoning Zoning is the process used to map host adapter ports (initiators) to the storage arrays FA ports (targets) in the Storage Area Network (SAN switches). This is typically done with softzoning, based on the unique 16-digit adapter world wide names (wwn).

IMPORTANT

For IBM i, only single-initiator to single-target zones are supported. No IBM i host initiator-wwn should ever be zoned to more than one target wwn on the same array.

When using DMP for redundant multipathing for the storage connections, redundant legs/pairs should be routed through separate fabrics/switches.

VIOS configurations Limitations and restrictions for IBM i client logical partitions are detailed in the IBM Knowledge Center.

In particular, note that when using virtual Fibre Channel, the following restriction applies:

Each virtual Fibre Channel adapter in an IBM i client partition must connect to a different physical Fibre Channel port. Connecting more than one virtual Fibre Channel adapter in the same client logical partition to a single physical Fibre Channel adapter port in the Virtual I/O Server is not supported.

Masking Masking is the process used to assign specific volumes mapped to a target storage port to a specific host initiator and follows the same rules as other open systems host types. For example:

Host LPAR - A has two IOP/IOAs:

Use the method of symmacess documented in the EMC Solutions Enabler Array Management CLI User Guide, available on Dell EMC Online Support.

Creating the required groups (IG/PG/SG) and combining these into a new MV results in the provisioning of the LUNs in the SG to the respective FA-port(s) and host initiator(s).

Note: Although there may be situations where multiple ports are used in a PG and/or multiple initiators are used in an IG, if the zoning is done correctly on the SAN level, then there will still only be "single-initiator- to-single-target" logins through the fabric into the FA-ports on the VMAX.

Initiator World Wide Name

i3 10000000c9616488

i4 10000000c9616489









The following is an example of the first masking view.

SG 1symaccess create -sid 3456 -name SG_1 -type storage devs 100:15F

PG_1symaccess create -sid 3456 -name PG_1 -type port -dirport 8E:0,9E:1

IG_1symaccess create -sid 3456 -name IG_1 -type initiator -wwn 10000000c9616488

symaccess -sid 3456 create view -name MV_1 -sg SG_1 -pg PG_1 -ig IG_1

GatekeepersGatekeepers (GK) are small VMAX devices that Dell EMC software uses to communicate with each VMAX array. Gatekeepers are configured by using either EMC UniSphere or SYMCLI products.

To provide protection against disk and FC path failure, usually two RAID 1-mirrored gatekeeper devices are configured on an IBM i LPAR.

Open Systems Gatekeeper

These small control devices (3 cylinders) should not be multipathed, but should have three GKs per port for each type of software or monitoring to be used. This can add up to 32 or more GK per Open Host initiator if SE, Unisphere, and the associated monitoring software, is utilized.

Refer to Dell EMC Knowledgebase solution emc74113, available on Dell EMC Online Support.

IBM i Gatekeeper

The IBM i Gatekeepers (GK) are used when SRDF/TF Manager or SYMCLI is to be used on the IBM i host for managing LPAR replication.

Note: Solution Enabler 7.4 or later must be used to create a Gatekeeper.

The following is an example for creating three D910 GK devices for use by SRDF TimeFinder Manager (STM).

Symconfigure –sid xxx –cmd “create gatekeeper count=3, emulation=as/400_d910_099;” commit -nop

The Gatekeeper device is never added to the host storage, but when addressed and assigned correctly, should appear in the 'Non-Configured Units list. Attempts to add a Gatekeeper to an ASP results in disk errors. For IASP replication in an IBM i clustered environment, additional Gatekeeper devices must be configured on all target nodes. A minimum of two Gatekeepers per LPAR (on separate paths) are recommended.

IMPORTANT

Never multipath Gatekeeper volumes.

Gatekeepers 61






Historically, an address of 32 was assigned to the Gatekeeper device. This 'rule' is more of an identifier, rather than for any technical reason.

IMPORTANT

A separate Gatekeeper device is required on each path or FA port used for full redundancy. The Gatekeeper that the Dell EMC software uses is nonconfigured to the host IOA and counts toward the IBM device limit of 32 or 64 devices. A maximum of two Gatekeepers are required per LPAR.

Assigning Gatekeeper devices to an IOA that is in use by an IASP can result in unwanted side effects.

Note: Thin D910 Gatekeeper devices are supported to use with the SRDF TF Manager.

Note: On VMAX 40K, VMAX 20K, and VMAX 10K xxx987xxxx, devices must be bound to a pool.

Note: With VMAX3 Family (VMAX 400K/200K/100K) and VMAX 10K xxx987xxxx, all devices are D910 thin devices, including Gatekeeper devices. VMAX3 Family and VMAX 10K xxx987xxxx do not support thick devices.



Multipathing on IBM i hostsTo reduce bottlenecks and increase data availability, IBM announced the support for multipath in V5R3 of the operating system.

To understand this benefit, consider the following:

If a host adaptor fails, then all the devices presented on that path become unavailable. However, with multiple paths to a single device, if a failure occurs then the I/O is rerouted on another path. The rerouting also ensures greater load balancing in normal operations and, consequently, removes potential bottlenecks.

The following information is provided in this section:

◆ “Hardware requirements and planning” on page 63

◆ “Load source and multipath” on page 64

◆ “Gatekeepers and multipath” on page 64

◆ “Recognizing multipath devices” on page 64

◆ “Troubleshooting multipath devices” on page 66

◆ “Determining non-operational paths” on page 69

◆ “Recovering multipath messages” on page 74

◆ “Resetting multipath connections” on page 75

For the most up-to-date information, always consult the Dell EMC Simple Support Matrix.

For technical information about IBM i, refer to IBM i’s welcome page in the IBM Knowledge Center.

Hardware requirements and planning

All IBM operating systems from V5R3 fully support multipath of data devices. Refer to “Load source and multipath” on page 64 for specific software requirements for multipathing load source devices.

In terms of hardware, to present a single device to two separate paths doubles the IBM IOP/IOA requirement for the host. IBM supports up to eight paths to one device.

Dell EMC recommends configuring a minimum of two paths for IBM i hosts with critical high workload and performance requirements; however, four paths may be advisable. In a VIOS/VFC(NPIV) set-up, a minimum of four paths is preferred, two virtual adapters via two separate IOA-ports on each VIOS LPAR.

To maintain a fully-resilient host, careful planning is required to ensure that each path is fully independent of each other. Points to consider on the host include positioning the IOP/IOAs in separate frames and on separate HSL/12x loops and power supplies.

In terms of connectivity, if the paths are presented through switches then consideration should be given to putting each path in separate fabrics.

On the VMAX, the devices will require presenting the paths to two separate front end adaptors. For performance and availability reasons, consideration should be given to ensure that the front end adaptors chosen are on separate directors.

Multipathing on IBM i hosts 63









Load source and multipath

When multipath was initially released at V5R3, there was no support for multipath of the load source. At that time, if protection against path failure was required, the recommendation was to configure and use remote load mirroring. Support for load source multipathing was not included until IBM released version i6.1.

For hosts running i6.1 on a Power 5 or Power 5+ hardware, the load source device is still required to be controlled by an IBM 2847 IOP and an associated IOA. However it is no longer necessary to provision 2107_A8n (unprotected) devices as the load source. In IBM OS i6.1 and later, a protected device (2107_A0n) can be presented as the load source and can be multipathed.

Customers using Power 6 and above hardware have the option of using Smart IOAs (5749/5774/5735 IOA) to control a multipathed load source. Customers should confirm they have met the prerequisites for using these IOAs. Prerequisites can be checked at the following site:

https://www-912.ibm.com/e_dir/eServerPrereq.nsf

Note: VMAX3 Family and VMAX 10K xxx987xxxx only support D910 devices.

Gatekeepers and multipath

The multipathing of Dell EMC Gatekeeper devices is not supported.

Recognizing multipath devices

When a disk resource is presented to a host on a single path, then it is displayed in the disk hardware status screen (available through the IBM i server SST menus) with a resource name of DDxxx.

External disk Units were traditionally viewed when the IOA was expanded within the system unit and bus the IOA is attached to. With V5R3 and above, these now display as a Disk Unit System, as shown in the next screen. The highlighted devices shown in the following screen represent the same logical device, physically presented across two separate IOAs.



The following example shows the same logical device, physically presented across 2 separate IOAs. The breakdown is as follows:

2 / 7 0 9 / 0 / 0 - 2 / / 1 / 1 / 4 0

where:

2 = PCI bus/709 = system bus/0 = system board/0 = system card/- 2 = storage unit/= I/O adapter/1= I/O bus/1= Controller/40= Device

The device changes from a DD resource name to a DMP resource name when a second path is presented to the device, as shown in the next screen.

Resource name DMPxxx breaks down to Device Multipath Protection.



xxx = resource number assigned by the system

In the following example, in an abbreviated system configuration list from a V5R4M5 host you can see that the load source device (DD001) is single-pathed (and will be protected with a load source mirror) and that all the other devices in this configuration show as DMP (multipathed).

In the next example from a i6.1 host, note that all the devices, including the load source device, are showing as DMP.

Troubleshooting multipath devices

IBM OS V5 has no tools within the service tools to check the status of the paths. However, with IBM OS i6 and later, there is an option to check the status of the paths using System Service Tools. Choose Display Disk Configuration > Display Disk Path Status.



The following example shows that one path has failed and that the three other paths are active. Careful investigation is required to determine which physical path is affected, discussed further in “Determining non-operational paths” on page 69.

Further information about a non-active path can also be found in the qsysopr message queue. The following screen shows the warnings that can display.



To check the status of the failed resource, (in this case DMP020), access the SST menu and HSM (Hardware Service Manager), and select option 3 - Locate resource by resource name and enter DMP020. The resulting display shows that the resource in this example is not connected, This should be investigated to confirm whether the connection issue is located on the host or on the Dell EMC storage array.

Interrogating the individual message in the qsysopr message queue (press F1 when the cursor is over the individual message) shows further information about the IOA resource name, where the failing device is presented, in this case DC05 and device DMP020.

The Product Activity Log (PAL) records the information within the log for that period with the following System Reference Code D9103002. The following example shows that the addressed device is not responding. Unfortunately, the PAL does not give you the resource name of the IOA that is affected. However, by creating a system



configuration list from Service tools hardware service manager, it is possible to cross reference the device serial number with the IOA using the method described in “Determining non-operational paths” on page 69.

Determining non-operational paths

When a multipath connection fails, it is imperative to resolve this issue correctly so the path is made operational again and that the remaining operational path is not affected in error. This section will highlight the methods using System Service tools and the system configuration list to determine which path is not operational, and how to check the WWNs of the HBAs to confirm which path on the VMAX 40K, VMAX 20K/VMAX, VMAX 10K xxx987xxxx, or DMX array is affected.

◆ “Using System Service tools” on page 69

◆ “Using system hardware resoruce list” on page 73

Using System Servicetools

When a path to a multipath device fails, this incident is recorded in the qsysopr message queue. Interrogation of the message using the F1 key reveals the resource name of the affected IOA. Using this resource name, it is possible to determine the physical location of the IOA and the WWN of the IOA.

1. In the System Service tools menu in the IBM OS, choose option 1 to start a service tool.

2. In the resulting menu, choose option 7 (hardware service manager).

3. It the resulting menu, choose option 3 to locate by resource name.

4. Enter the resource name that you obtained from the qsysopr messages.



In the following example, DC07 is the resource name. From the screen below we can see that the IOA is a 280e (5760) and is operational. Should this show any other status, then the cause of the issue has been located.

Continuing with this example, placing a 5 next to the IOA allows the detail of the device to be examined, the WWN of the two ports on the IOA to be obtained.

The above screen shows that the WWN is 10000000C9C5427E for port 0 and C9C5427F for port 1. Using the F11 key you can also check the connectivity for each port. In the following example, the port status is “not active” for port 0 and “active” for port 1.



To determine the physical location of the IOA in the rack, return to the logical hardware resources screen (press F12 twice) and then choose option 8 to show the associated packaging resources.

From the resulting screen, it is possible to determine the exact location within the rack by choosing option 5 from the below screen to display detail.

Display the details (option 5) shows the location of the physical IOA on the host.

These investigations allow the IOA physical location and its operational status to be determined, which may resolve the issue. However, if the issue is not resolved, then the array connections can be checked to ensure that the WWN of the IOA is logging in correctly. (In a switched environment, the switch hardware status must be checked along with the zoning.)

To ensure that the array connectivity is operational, from SYMCLI issue the following command:

symcfg -fa all list -port -sid xxx



The resulting screen shows the director and port status.

To then determine which host IOAs are logged into the array, issue the following command:

- symaccess -sid xxx list logins -dirport 1e:8

This then shows that the IOA with the WWN of 10000000C9C5427E (which was found on the host IOA) is on the fabric abut is not logged into the FA port.

In the scenario, the procedure has shown the physical connectivity from the IOA on the host to the array is fully operational but that the FA port is offline, which is the root cause of the issue affecting the multipath presentation of the devices on the host in this example.



Using systemhardware resoruce list

In this case, the host has a reported issue with DC05 but service tools are not available to investigate the issue. Therefore, to correlate that resource with the FA port, fun the following command on the IBM i host:

DSPHDWRSC *STG *PRINT

This produces a single spool file. Using System i Navigator, locate the spool file, then drag and drop the file to your PC, which converts the file to a readable text format. Open the hardware resource listing created and using the Find option, search for DC05.

Continue to click the Find next button in the Find dialogue until you reach the final entry in the file, which for a Smart IOA will show the resource name (DC05); the IOA type (577D); the port (0); and status (active); plus the port speed, protocol, and the wwn of the port (10000000C9C5427E).

On the Dell EMC array, generate the list of port login information with the following command:

Symaccess -sid xxx list logins

The output from this command can be piped to a text file for interogation. Open the list login file and use the find option to find the host port wwn:

10000000C9C5427E



This shows that the host wwn listed is not logged into the FA port (1E-8) and further investigation will be required to determine why the host initiator is not logged in to the array FA port.

In this example, we know that the FA port was "offline" which prevented the host initiator from logging in. However, there are many causes that could prevent the host initiator from logging in, including switch connectivity issues, which would have to be investigated to resolve the missing multipath connection issue.

Recovering multipath messages

Following recovery of a previously failed multipath connection, the qsysopr message queue will show the following informational messages, as shown in the following example:



Each individual message can be checked and details are shown in the following screen:

The product activity log (PAL) will also record the information for the period and the SRC B6008003. The external storage subsystem disk unit connection was restored.

Resetting multipath connections

Following reconfiguration, or for the removal of dead paths (once the reason for the dead path has been confirmed), IBM software contains commands to reset the number of multipath connections to those that are currently active.

This process was amended at IBM i6.1, although the earlier version will still operate successfully at i6.

At all OS versions of V5, the multipath reset command can be located and run as follows (for IBMI i6.1 and later, an optional procedure follows this one):

1. Access the system service tools main menu.

2. Select option 1 from System services >Start a service tool.

3. Select option 4 from Start a service tool > display/alter/dump.

4. Select option 1 from display/alter/dump output device > display/alter storage.

5. Select option 2, licensed internal code (LIC) data, from the Select data menu.



6. Select option 14, advanced analysis, from the Select LIC data menu.

7. On the Select advanced analysis command screen, place a 1 in front of the MULIPATHRESETTER command, and press Enter.

8. On the option line for the MULIPATHRESETTER command, type -resetmp -all, and press Enter.

9. On the option line for the MULIPATHRESETTER command, type -confirm -all, and press Enter.

At IBM i6.1 and later, the multipath reset procedure can also be run as follows (V6R1 and above):

1. Access the system service tools main menu.

2. Select option 1 from Systems services > Start a service tool.

3. Select option 7, Hardware service manager.

4. Select option 1, Packaging hardware resources.

5. Select option 9 against the required Disk Unit System.

6. Select option 7, Paths to multiple path disk, to check the status of the paths.

7. Press F14 to reset all the paths. When prompted for confirmation, verify the information and press F10 to reset the paths.

When the reset is completed, a confirmation message is displayed at the end of the screen.


CHAPTER 3

This chapter provides information on how to manage storage and disk paths in IBM i environments.

◆ IBM i Information Center...................................................................................... 78◆ Configuring and viewing disk configurations ........................................................ 79◆ Adding devices to a new or existing ASP.............................................................. 79◆ Disk management on IBM i................................................................................... 82

Managing Storage and Disk Paths in IBM i Environments

Managing Storage and Disk Paths in IBM i Environments 77


IBM i Information Center For technical information about IBM i, refer to IBM i’s welcome page in the IBM Knowledge Center, as shown in Figure 7, at:

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i/welcome

Figure 7 IBM i information center, System management content

Type in your search criteria, such as backup and recover procedures, auxiliary storage pools procedures, disk management, disk pool procedures, disk management checklist procedures, and so on.



Configuring and viewing disk configurationsASP configurations can be viewed and changed through either DST (dedicated services tools) or SST (system services tools) on the IBM i host.

DST allows more flexibility than SST since the host is not fully up in the DST state. DST allows you to display configurations as well as to add, remove, and move devices between ASPs.

DST also allows the use of “copy disk unit data.” This options allows the user to copy the internal IBM LS to a Symmetrix volume.

SST restricts the user to add and configuration displays only. Moves and removal of configured volumes must be done at DST. SST has more restrictions than DST.

See IBM documentation for more details on these tools.

Adding devices to a new or existing ASPThis section contains the following information to add devices to a new or existing auxiliary storage pool (ASP):

◆ “Adding devices to a new ASP” on page 79

◆ “Adding devices from two different Symmetrix systems” on page 80

◆ “Adding or removing devices to/from an existing ASP” on page 80

Adding devices to a new ASP

Devices can be added to a new ASP using either DST or SST, as further described in this section.

Using SST To add a device to a new ASP using SST, complete the following steps:

1. Log in to SST.

2. Select Option 3) Work with disk units.

3. Select Option 2) Work with disk unit configuration.

4. Select Option 2) Add units to ASP.

You have three options. Select one of the following:

• Option 1) Create unencrypted ASP.

• Option 2) Create encrypted ASP.

• Option 3) Add units to existing ASP.

Using DST To add a device to a new ASP using DST, complete the following steps:

1. Log in to DST.


3. Select Option 2) Work with disk configuration.

4. Select Option 3) Work with ASP configuration.

Configuring and viewing disk configurations 79


At this point there are several options to choose from including:

• Delete user ASP.• Add units to ASPs.• Delete ASP data.• Move units from one ASP to another.• Remove units from configuration.

Adding devices from two different Symmetrix systems

Devices from multiple Symmetrix systems may be presented to the same host. The last three digits of the device Serial ID ( = last 3 digits of the Symmetrix) denotes to which Symmetrix the device is connected.

Add/remove is one method for migrating from one Symmetrix system to another. This is accomplished by adding devices from the new Symmetrix system to an existing ASP, then removing the devices of the old Symmetrix system from the ASP.

Adding or removing devices to/from an existing ASP

This section provides procedures for adding or removing disks to an existing ASP.

Once you are at the DST, complete the following steps:

Adding devices To add a disk to a new ASP using DST, complete the following steps:

1. Log in to the DST.




At this point there are several options to choose from including:

• Delete user ASP• Add units to ASPs• Delete ASP data• Move units from one ASP to another• Remove units from configuration

Removing devices The removal of devices from a standard ASP must be done at DST. To remove devices, complete the following steps:




4. Select Option 7) Remove units from configuration.

If disk access is removed from the host (that is, masking or mapping) you will need to perform another IPL to remove the resulting (missing) non-configured disks.

When non-configured units are physically removed from the host, a clean-up of missing and non-reporting devices should be performed.

From the DST or SST, select one of the following:



◆ Option 1) Start a service tool.

◆ Option 7) Hardware service manager.

◆ Option 4) Failed and non-reporting hardware resources.

Use option 4 to cleanup failed and non-reporting resources.

Adding devices to a new or existing ASP 81


Adding devices to a new or existing IASPThe IBM i 6.1 Independent ASPs: A Guide to Quick Implementation of Independent ASPs Redbook explains how to build an independent auxiliary storage pool (IASP) using the IBM Systems Director Navigator for i5/OS. Chapter 2, “Creating an IASP,” details how to add disk to an iASP. This Redbook can be found at http://www.redbooks.ibm.com/redbooks/pdfs/sg247811.pdf.

Disk management on IBM iA configured disk unit is used by the system and is added to an ASP.

A non-configured disk unit is a unit that has been presented to the system but must be added to an ASP before use.

Remove access to a non-configured disk

If a non-configured disk disappears (for example, using symmask to remove access to it), then the disk still stays in the non-configured disks list. Immediately following the symmask refresh command, the hardware status of the non-configured disks changes to not operational.

Visit the IBM Knowledge Center for more information.

Determine IOA WWN, speed, status, and other useful information

This section describes how to find the WWN for a specific IOA configured on an i5 host. It is, possible to use other techniques, such as:

◆ Using your available SAN management tools, check the switch port to determine the IOA WWN (can be used prior to zoning).

◆ Dell EMC Customer Service Engineers have access to Symmetrix tools to find exact IOA WWNs.

Only the physical IOA rack and slot is knownIf only the physical IOA location is known (for example, the cable is going into a specific IOA port), then to determine the WWN from the host perspective (if it is not written or visible on the physical IOA, or if it needs to be verified):





◆ In the rack where the IOA is located, there is normally a panel at the front or back which contains a model number, for example 0588. Take note of this rack model number. If this cannot be easily found, it is not essential.

◆ In the rack where the IOA is located, there is normally a LED or LCD display. This typically shows the i5 server serial number to which the rack is connected. Take note of this serial number.

◆ In the rack where the IOA is located, there is normally a rack serial number displayed (on a sticker or similar, usually in large figures to distinguish from individual rack component serial numbers). Take note of this serial number.

◆ Above or below the slot where the IOA is physically located, there is typically a sticker or printed text showing the slot number (for example C02). Take note of this slot number.

The above information can be used to determine the device location code for the IOA on the i5 server. The most important information is the rack serial number and slot number. It is also possible to check the information by completing the following steps:

1. Log in to the HMC console.

2. Select server and partition.

3. Select Server management.

4. Select the server matching the i5 serial number.

5. Select the partition and partition profile to which the IOA is configured.

If the partition name is unknown, it is possible to use the HMC to create a system plan for the server.

a. Right-click on the server serial number, then select create system plan.

b. Search for the rack serial number.

c. Search for the slot number, which will indicate the partition to which the IOA is configured (used by partition/profile). The device location code is also provided under “location code”. If the IOA is not configured to any partition, it will not be possible to query the WWN as it will remain powered off until it is assigned to a partition profile and that profile is activated.

6. On the partition, right-click Properties, then select the Physical I/O tab.

7. In the profile I/O devices, expand the appropriate rack serial number and slot number.

8. Click Properties. The device location code is displayed in the Properties window.

Refer to the IBM i information center on the IBM website for more information on how to verify the device location code for the IOA.

It is also possible to print the server configuration to a spool file and search for the rack serial number and slot number for the IOA. This can also provide the WWN.

Only the WWN of the IOA is knownFollow the steps in this section when a WWN is reported as faulty from Dell EMC Control Center, Dell EMC Customer Support (connected to Symmetrix), or from switch logs, and it is not certain which IOA owns the WWN.

Disk management on IBM i 83


Note: If a WWN is reported missing, then it is possible that the IOA will not be in a state (may not respond) to query the WWN from the OS.

To find a WWN on an IBM i server, print the server configuration to a spool file and edit the spool file by completing the following steps:

STRSST1. Start a service tool7. Hardware Service Manager6. Print configuration

1. Select Format 1 (132 columns).

2. Select Information printed 1 (Packaging resources sorted by location).

The message "Print request successfully submitted to service printer" displays.

3. View the generated spool file, for example:

a. Press PF12 to return to the SST screen.

b. Press PF10 for command entry:

WRKSPLF

c. Press PF10 to change view showing date (to assist selection of file).

d. Press PF18 to go to the bottom of the list.

e. Find the generated spool file (it most likely has a name similar to QPCSMPRT).

f. Choose option 5 to display the spool file.

g. Press PF14 to enter find options.

h. In the "character string to find" field, enter the WWN, such as C9442020.

i. Ensure the search is from position 1 to 132.

j. Press PF16 to find the WWN.

Information such as the IOA location can now be found. By pressing F16 repeatedly, each disk resource name and serial number can be found for that IOA/WWN.

Use PF19 and PF20 to scroll left and right. Press PF1 for more window control information.

It is also possible to send the spool file to a PC printer emulator and create an ASCII text file, providing more options for searching (for example, import to Microsoft Excel) and sending the information to Dell EMC or other interested parties.

Determine the IOA location and WWN for DD disk resources

A disk resource name that begins with "DD" usually indicates a single path disk. It is possible for an administrator to rename a multipath (DMP) disk resource to "DD," but this is unusual.

Get the resources names for each of the disks. For each disk resource name that starts with DD, complete the following steps:

1. Go to Strsst > Start service tool >Hardware service manager > locate resource by resource name.



2. Enter the disk resource name, such as DD004.

3. When displayed, check the status of the disk. Does it show as operational or not operational? Does it match the status found in the previous "check disk hardware status" above?

4. Choose option 8 associated packaging resources.

5. Choose option 5 display detail.

This will give the logical path to the IOA hardware (HBA) and its WWN.

6. Repeat for each DD resource name.

Disk management on IBM i 85



CHAPTER 4

This chapter provides information specific to IBM i hosts connecting to VMAX systems.

◆ Migration services.............................................................................. 88◆ Pre-migrations tasks .......................................................................... 89◆ Option 1 — Tape backup/reload..................................................... 91◆ Option 2 — Add/remove disk units............................................... 92◆ Option 3 — Host-based journal replication (log shipping) ......... 93◆ Option 4 — Storage-based migrations (hardware replication) ... 95◆ Option 5 — SAN-based replication................................................. 96

IBM i/VMAX Environment Migrations

IBM i/VMAX Environment Migrations 87


Migration servicesDell EMC has assisted in data migrations to the VMAX and Symmetrix enterprise storage platform for numerous supported server platforms, including iSeries, System i, and IBM i data and load source migrations. There are several options available to migrate IBM i data to an Dell EMC external SAN-based storage profile.

Following “Pre-migrations tasks” on page 89, five basic migration options are discussed:

◆ “Option 1 — Tape backup/reload” on page 91

◆ “Option 2 — Add/remove disk units” on page 92

◆ “Option 3 — Host-based journal replication (log shipping)” on page 93

◆ “Option 4 — Storage-based migrations (hardware replication)” on page 95

◆ “Option 5 — SAN-based replication” on page 96



Pre-migrations tasks Consider the following tasks before migrating:

◆ “Performance” on page 89

◆ “Current configuration and status” on page 89

◆ “Full SAVSYS” on page 90

Performance

Disk performance is important for production systems. When migrating from IBM storage, either internal or external, typically the Dell EMC IBM i Global Practice has been involved to analyze and review the current (pre-migration) performance and provide recommendations for the sizing and configuration of the new Dell EMC external storage profile. This data is very beneficial when there is a need to evaluate the disk performance of the new Dell EMC (post-migration) profile. The Dell EMC IBM i Global Practice can provide the proper procedure and forms to request this performance analysis as part of the pre-sales engagement (refer to “Dell EMC IBM i Global Practice” on page 9). Dell EMC IBM i Global Practice staff can provide this service as part of a presales service for correctly sizing the external storage profile or as part of a PS delivery task, depending on the cycle/status of the project.

When migrating from a current Dell EMC VMAX or Symmetrix profile to a new family of VMAX systems, the same IBM i host based analysis can be done to verify that the performance is still at an acceptable level and to determine how the new VMAX profile should be sized and configured. An additional VMAX or Symmetrix performance analysis (from STP/WLA-data) of the current IBM i storage configuration is strongly advised. A local or regional Dell EMC "SPEED guru" or Performance RTS staff should be involved to analyze the performance and utilization of the current profile and to project the current workload to the new VMAX profile. Based on this analysis/projection, recommendations for the new VMAX system can be given.

Current configuration and status

Prior to the migration, detailed configuration information on the current profile should be available. In case any problems are experienced during the migration and a fall-back to the original profile is required, it is important to know what the original configuration looked like. The IBM i LPAR's detailed rack configuration should be printed by the customer as per the Dell EMC Knowledgebase solution emc155136. This provides an overview of the current disk configuration with all disks listed with their serial numbers, the disk IOPs, and IOA s that are in use for the disks and their respective slot positions in the I/O racks/buses.

From the LPAR's SST menu (concurrent System Service Tools), the status of all hardware components should be checked, especially for the disk and I/O path's configuration, its hardware status, and the protection status (Mirroring/RAID 5). In the SST menu, to identify "Failed and Non-Reporting Hardware" of a IBM i LPAR, all hardware resources are listed that have either failed or that have not reported in after having been detected before.

Pre-migrations tasks 89


Having resources in this list is not necessarily indicative of any real hardware problems, since old or stale resources can also be listed, as well as dynamic LPAR resources that might have been (temporarily) assigned to another LPAR within the IBM Power systems complex. This repository should be cleaned up prior to the migration, whenever possible. After this list has been cleaned up (removing all undesired entries), a "full normal" IPL should be performed. After signing on again, the list should be inspected to see if any disk-related resources have real problems. Correct any relevant problems prior to the migration.

Full SAVSYS

It is the customers' responsibility to create a full system save of the entire LPAR that is going to be migrated. The "Single Level Storage" concept used in the IBM i storage architecture is very unforgiving when any disk within an ASP fails without a redundant component being available.

Some processes for a IBM i data-migration, such as a Load Source migration procedure, might have to temporarily suspend mirroring operations during the actual data-migration process for the LS. At that time, such a component in the LPAR's ASP is considered a SPOF (Single Point Of Failure) and presents a possible risk. Whenever you deal with a IBM i data migration, the customer should be educated about any risks and that a full backup is highly-recommended. If the current disk profile is already running on the VMAX system, then alternatively, Dell EMC can assist by using any existing TimeFinder or SRDF replication to create a consistent "Golden Copy" of the current storage profile. These replicas should be split when the LPAR is in a power-down status, in order to enable a normal IPL after this golden copy is restored, in case of a fall-back procedure.



Option 1 — Tape backup/reload Tape backup/reload is considered an old-style migration scenario and will impact the customer’s operations due to the elongated outage associated with this method. However, if this downtime is acceptable, this is still considered a valid and proven migration option. This method can be used for local migrations, or when tapes are sent with couriers, also for long-distance migrations.

A tape reload requires that an offline full system save is being made. This is also called a full SAVSYS or “option-21 save” in IBM i terminology. A full SAVSYS delivers a bootable media image with a backup of all LIC, OS, system, and user data. User data is often referred to as *NONSYS data.

As a precaution, after the full save procedure, the backup media is often duplicated by the host to create an extra set of tapes in case of media failures (DUPTAP operation). When these tapes are used to reload to a new system, a manual D-type IPL enables a boot from this media. At this point, it becomes a scratch new install for this LPAR, with the whole LIC installed to the NEW LS. After the additional data disk units have been added, the system can then restore the OS and user data to the new profile.

For a detailed description of backup and restore procedures, refer to IBM’s Power systems Redbooks at the IBM web page at http://www.redbooks.ibm.com/Redbooks.nsf/portals/Power?Open.

Option 1 — Tape backup/reload 91


Option 2 — Add/remove disk unitsWith this method, the new target disk units get added to the existing ASP(s). This is an online process, completed using the System Service Tools (SST) menus. For provisioning and adding disks to the IBM i LPAR, refer to Chapter 3, “Managing Storage and Disk Paths in IBM i Environments.”

Once the new units have been added, the IBM i LPAR is able to use the new capacity. The next step is to then remove the old disk units from the ASP. The Remove units from ASP is typically an offline process completed using the Dedicated Service Tools (DST) menus. However, starting with version i7.1 of the OS, there is now also an option to remove disk units from the ASP configuration with a new option in the concurrent SST service tools menu while the system is online. With this new option, the actual remove process may take a longer time, but it does not require any downtime for the customers applications. Refer to the IBM i7.1 manuals for further details.

When the units for removal have been selected and confirmed, the system copies all remaining data from these units to the new units that remain in the ASP. Depending on the size of the ASP and the number of disk units, this process can take a considerable amount of time.

Optionally, between the adding of new units and removing the old units, the IBM i STRASPBAL procedure can be used to migrate the bulk of the data in the background, while the system remains operational for the applications and users. After adding the new units, this command can do an *ENDALLOCATE for the old units and then perform a *MOVDTA process to move the data from the old units to the new units. By using this process, all old data disks can be drained almost entirely. Typically, less than 1% of the data remains on these disk units. At that time, an offline window has to be planned to actually remove the old units from the ASP by using the DST menu.

This migration method can only be used for local migrations within SAN distance, as the IBM i LPAR needs to have access to both the old and the new storage. This also temporarily requires extra connectivity resources on the existing LPAR to be able to connect the "new" storage while the "old" storage is still active.

The systems LS cannot be migrated with add and remove; it requires a special offline procedure completed using the DST. At this stage, the IBM is in a restricted state and not available for applications and users; only operations from the systems console are available. This procedure, known as Copy Disk Unit Data, is available in the DST menus. To find these procedures, refer to the IBM Redbooks page.


http://www.redbooks.ibm.com/




Option 3 — Host-based journal replication (log shipping) There are several vendors that have host-based software tools available for the IBM i for sending and applying journal log updates to a remote system. Vision OMS, MiMiX, iTera, QuickEDD, Datamirror are a few of these products. These products are typically set up in asynchronous replication mode. IBM acquired a few of these companies. Together, VISION and IBM have the largest market share for these products. This technique is also called remote journaling or log shipping.

This method can be used for local or long distance migration. It requires two active LPARs, where the source LPAR replicates its updates to the target LPAR over a TCP/IP link. Typically, these software products are in use for host-based disaster recovery (based on logical replication), but can also be used to run a data migration.

This process is typically started by performing a FULL system save on the source system. This backup then gets reloaded to the target system. At this time, the software replication product is set up and activated to start synchronizing the updates to the (remote) target LPAR. An example of the schematics for this set up is shown in Figure 8.

Figure 8 Host-based replication setup

The disadvantages for host-based migrations are the same as for the disaster recovery setups with these products:

◆ It requires detailed setup and monitoring from a specialized staff.

◆ Sometimes not all objects are in sync (out-of-sync objects can be a common problem).

◆ It is susceptible to human error. For instance, the operator or administrator may forget to replicate certain objects. This may not be discovered immediately. At a later time, if a certain object which was not replicated is required for application

Option 3 — Host-based journal replication (log shipping) 93


processing or batch jobs, (such as, End-Of_Year processing, Prolongations, etc.) the migration would be severely impacted, possibly resulting in data loss or data unavailability for the application users.

◆ Many customers are not comfortable with software replication in large environments with multiple LPARs.

The overhead in terms of setup, continued monitoring, and maintenance, together with the chance of having an incomplete image on the target LPAR, are the main reasons why many customers are moving to a hardware-based replication scenario, like Dell EMC SRDF (or IBM Metro/Global-Mirror).

IMPORTANT

Dell EMC cannot perform such host-based migrations. This is a task for either the customer or a third-party consultation effort.



Option 4 — Storage-based migrations (hardware replication)

When the IBM i LPAR has a complete external Dell EMC storage profile with the data disks and the load source residing on an Dell EMC VMAX system, then Dell EMC’s SRDF hardware-based replication can be used to replicate the entire image to another frame.

Once the replication is set up between all volumes and the first time full synchronization has completed, then it is very easy to run a migration rehearsal on the remote target system. This is done by splitting the links between the source and target volumes and then IPL-ing the new host from the split image. The production host remains active during this time. In the actual cut-over window, the production host is shut down, the last updates are replicated to the remote storage system. Link split again and the new target production host can be restarted with the up-to-date production data. The basic SRDF migrations scenario is the same as for SRDF migrations for open systems.

If the existing LPAR is going to be reused, and it is just the data that is moving to a new VMAX system, then in a local migration scenario, after the host is shutdown, the FC connections must be rerouted to the new frame, (LUN assignments, cabling, zoning, and masking can be prepared in advance), and the old system can just IPL of off the new VMAX image.

In the case of remote migrations, you have the option to ship the existing LPAR to the new location, but this is not often done due to the high risks and elongated outage required for this method.

SRDF migrations are available for local and long distance migrations. Obviously, replication speed is dependent of available bandwidth, but in most cases, existing TCP/IP connectivity could be used to facilitate such migrations. Dell EMC SRDF is the only replication solution that supports native IP connectivity directly from the VMAX GIGe (TCP/IP) director boards. Other vendors (for IBM i, just IBM in this case) will need to bring in expensive FC-IP routing equipment on local and remote sites to enable hardware replication over TCP/IP.

Option 4 — Storage-based migrations (hardware replication) 95


Option 5 — SAN-based replicationDell EMC Open Replicator for Symmetrix (ORS), is a unique migration option using the existing SAN connectivity to migrate from an existing external SAN storage profile to a new VMAX storage profile. This is typically used to migrate from an older family of Symmetrix systems to a new system, but depending on the setup, migrations from SAN-attached IBM DS8000 might be possible.

For VMAX ORS migration, complete the following steps:

IMPORTANT

ORS migration is not supported for 2107 to D910.

1. Reroute host connections to the new VMAX system.

2. Use existing SAN insfrastructure to migrate data.

To better understand the setup and operations, refer to Figure 9.

Figure 9 ORS migration example

In the SAN setup shown in Figure 9, the VMAX FA-ports (WWNs) are granted access to the old Symmetrix DMX-4 FA ports and their assigned IBM i LUNs (zoning and masking). All available ports should be included in the migration process. At that time, a short offline window needs to be planned to shut down the production host, change its connections to the new VMAX ports (zoning and masking) and from the SYMCLI server, the ORS replication session will be started. The production system can now be restarted.

In the background, the ORS replication session moves the data from the DMX-4 to the VMAX through the SAN connections. The ORS replication session fetches the data requested by the LPAR with priority. For IBM i, both hot pull and cold pull to the VMAX are supported.



◆ With a hot pull, the production host is active while the replication is in progress.

• When using a hot pull, it is highly recommended to also use the donor-update feature. This feature will also update the old image with any new production data updates. In case of a failure during the replication, it ensures that there is always an up-to-date fall-back image on the original DMX-4 frame.

• When using the donor-update, there is no "instant fall-back image" anymore. The original pre-migration image is NOT preserved.

• A hot-pull can have significant performance impact on the active IBM i production LPAR.

◆ With a cold pull, the production LPAR is shut down until the replication of all data to the VMAX is completed.

Refer to the general ORS documentation and command reference manuals for the set up and execution of this migration method, as this is generic and also valid for the IBM i ORS migration. The setup and commands are run from an external SYMCLI server that has access to the VMAX system.

Option 5 — SAN-based replication 97



CHAPTER 5

This chapter provides an overview of the following software options for IBM i:

◆ SRDF/TimeFinder Manager ............................................................................... 100◆ Solutions Enabler ................................................................................................ 107◆ Dell EMC Unisphere for VMAX GUI.................................................................... 109

Host Software Options for IBM i

Host Software Options for IBM i 99


SRDF/TimeFinder ManagerDell EMC SRDFTM/TimeFinderTM Manager (STM) for IBM i is a set of host-based utilities that provide an IBM i interface to Dell EMC Remote Data Facility (SRDF) and Dell EMC TimeFinder.

For more details on supported SRDF/TimeFinder features, functionality, and extended features, refer to the most recent EMC SRDF/TimeFinder Manager for IBM i Product Guide, available on Dell EMC Online Support.

Note: Installation and extended features are included starting with Version 8.0.

SRDF/TimeFinder Manager for IBM i is available as a zipped file on Dell EMC Online Support.

The following information is included in this section:

◆ “Standard features” on page 100

◆ “Supported array and array features” on page 101

◆ “TimeFinder technologies supported for Enginuity 5876 or lower” on page 102

◆ “SRDF functionality” on page 103

◆ “Extended features” on page 104

◆ “SRDF/TimeFinder Manager user interface” on page 104

◆ “Installing SRDF/TimeFinder Manager” on page 105

◆ “Configuring SRDF/TimeFinder Manager” on page 105

◆ “Related documentation” on page 105

Standard features

The SRDF/TimeFinder interface enables you to configure and control SRDF or TimeFinder operations on VMAX3 Family, VMAX Family, and Symmetrix DMX arrays attached to IBM i hosts. The operations are as follows:

◆ Execute TimeFinder commands to establish and split TimeFinder BCV devices where BCVs are used for local mirroring, or are used as the source device in multi-hop replication solutions.

◆ Create point-in-time copies of full volumes or individual data sets using TimeFinder/Clone copy sessions.

◆ Create logical point-in-time snapshots of images for:

• Arrays running HYPERMAX OS 5977 (VMAX 100K, 200K, and 400K arrays) using TimeFinder SnapVX.

Note: TimeFinder SnapVX is supported only on arrays running HYPERMAX OS 5977.


http://powerlink.emc.com/products/connectrix











• Arrays running Enginuity 5876, using TimeFinder/VP Snap.

• Arrays, running Enginuity 5876 or lower, using TimeFinder/Snap.

Note: TimeFinder/Snap is not supported for VMAX 10K arrays or for arrays running HYPERMAX OS 5977.

◆ Execute SRDF commands to perform establish and split operations for local replication solutions, or for extended-distance replication solutions, such as SRDF/Asynchronous (SRDF/A).

◆ SRDF/TimeFinder Manager provides support for the IBM i host environment, such as multipath, boot from SAN, and independent ASP (IASP) functionality.

Supported array and array features

SRDF/TimeFinder Manager is used in environments that are configured with DMX and VMAX Family arrays.

The following rules and requirements apply to VMAX 10K arrays or arrays running HYPERMAX OS 5977:

◆ D910 device emulation only. Emulation for 2107 devices is not supported.

◆ Thin devices only. Thick devices are not supported.

◆ Thin (bound) gatekeeper devices only.

Note: Meta devices are supported on VMAX 10K arrays but not on arrays running HYPERMAX OS 5977.

Enginuityrequirements

Note the following requirements:

◆ HYPERMAX OS 5977 is supported on VMAX 100K, 200K, 400K arrays

◆ Enginuity 5874 through 5876 is supported on VMAX 10K, 20K, 40K arrays

◆ EMC Enginuity 5773 or lower is supported on DMX arrays

HYPERMAX 5977

For SRDF/TimeFinder manager and IBM i operating system version 6.1.1 or higher with device type D910-099, automated FAST control is supported on VMAX 100K, 200K, and 400K arrays. The automated FAST handles all thin device binding and allocation and manages the movement of application data across all of the storage a capacity defined in a Storage Resource pool (SRP). Data movement is based on gathered performance data and a performance Service Level Priority (SLP) defined for the application.

Enginuity 5876

The following VMAX 10K, 20K, and 40K features are supported with SRDF/TimeFinder Manager and IBM i operating system version 6.1.1 or higher with device type D910-099:

SRDF/TimeFinder Manager 101


◆ FAST VP

◆ VLUN VP Migration

◆ Virtual Provisioning

For detailed information on the above features, refer to “Supported features for arrays running Enginuity 5876” in the EMC SRDF/TimeFinder Manager for IBM i Product Guide, available on Dell EMC Online Support.

TimeFinderfunctionality

The TimeFinder family of local replication software allows users to non-disruptively create and manage point-in-time copies of data to allow operational processes, such as backup, reporting, and application testing to be performed independent of the source application, and to maximize service levels without impacting performance or availability.

TimeFinder technologies supported for HYPERMAX OS 5977

TimeFinder SnapVX is the TimeFinder technology supported on arrays running HYPERMAX OS 5977. TimeFinder Mirror and Clone commands can be run on HYPERMAX OS 5977, but emulations are invoked that use SnapVX as the underlying technology. When running emulation sessions, devices cannot be a SnapVX source or a link target. When devices are SnapVX sources or link targets, they cannot be used for emulation sessions.

TimeFinder Snap sessions are not supported; therefore, there is no emulation for this local replication type.

TimeFinder SnapVX

SnapVX creates point-in-time copies directly in the Storage Resource Pool (SRP) of the source device, eliminating the concepts of target devices and source/target pairing. If point-in-time data is needed, then linked targets are created. The maximum number of SnapVX snapshots per source device is 256.

TimeFinder technologies supported for Enginuity 5876 or lower

TimeFinder/Clone, TimeFinder/Snap, and TimeFinder/Mirror are supported on arrays running Enginuity 5876 or lower. Except where noted these technologies are referred to as “TimeFinder” in this document.

TimeFinder base products include:

◆ TimeFinder/Clone — Provides clone copy sessions that create point-in-time copies of full volumes or individual data sets. TimeFinder/Clone enables users to make copies of data simultaneously on multiple target devices from a single source device. The data is available to the target host immediately upon activation, even if





the copy process has not completed. Data may be copied from a single source device to as many as 16 target devices. Both source and target devices can be either a standard device or a BCV device.

◆ TimeFinder/Snap — Provides snap copy sessions that create economical, pointer-based replicas simultaneously on multiple target devices from a single source device where only the pre-images of changed data are written. TimeFinder/Snap enables users to configure special devices called virtual devices (VDEVs) and save area devices (SAVE devices).

Note: TimeFinder/Snap is not supported on VMAX 10K arrays.

◆ TimeFinder/Mirror — Provides full physical copies of data from a standard device, which are online for regular I/O operations from the host. Data is copied to BCV devices as a mirror of the primary data. Data is available to the target host after devices are split.

Note: For Enginuity version 5876, TimeFinder/Mirror native operations are no longer supported. However, TimeFinder/Mirror commands are still supported using the TimeFinder/Clone Emulation feature. TimeFinder/Clone Emulation enables TimeFinder/Mirror scripts that were developed and deployed on previous generation DMX arrays to run on the VMAX Family arrays. Clone Emulation is the default for RAID 5/RAID 6-protected BCVs. TimeFinder/Mirror operations will work in DMX array environments running Enginuity version 5773 or lower.

SRDF functionality

Within the SRDF family of software, SRDF/TimeFinder Manager supports:

◆ SRDF Cascaded replication

◆ SRDF Extended Distance Protection (SRDF/EDP)

◆ SRDF Reserve Capacity with Transmit Idle

◆ SRSF/A Delta Set Extension (DSE)

◆ SRDF/Synchronous (SRDF/S)

◆ SRDF/Asynchronous (SRDF/A)

◆ Concurrent SRDF/S

◆ Concurrent SRDF/A

◆ SRDF/A Multi-Cycle

Two modes of operation are:



◆ SRDF/Synchronous (SRDF/S)

◆ SRDF/Asynchronous (SRDF/A)

Extended features

Dell EMC SRDF /TimeFinder Manager for IBM i Extended Features provides support for the IBM independent ASP (IASP) functionality. An IASP is a set of switchable or private auxiliary disk pools (up to 223) that can be brought online or offline on an IBM i host without affecting the rest of the system.

This support, when combined with SRDF/TimeFinder Manager for IBM i, enables you to control SRDF or TimeFinder operations on DMX and VMAX Family arrays attached to IBM i hosts as described in “Standard features” on page 100. In addition, the extended features can use IASPs to present one or more target devices containing an IASP image to another host for business continuance (BC) processes.

Extended features control operations can be performed two ways:

◆ From the SRDF/TimeFinder Manager menu-driven interface.

◆ From the command line using SRDF/TimeFinder Manager commands and associated IBM i commands.

For more details on extended features for SRDF/TimeFinder Manager, refer to the latest SRDF/TimeFinder Manager for IBM i Product Guide Version located on Dell EMC Online Support.


SRDF/TimeFinder Manager user interface

SRDF/TimeFinder Manager is designed to activate and provide access to the Symmetrix array’s preconfigured BCV devices or Snap devices and control SRDF links. These operations are controlled in two ways:

◆ IBM i menu-driven interface

• Main menu

The Dell EMC SRDF/TimeFinder Manager for IBM i main menu is used as an IBM i interface to Symmetrix functionality. For more information about this menu and instructions on how to access and exit this interface, refer to the EMC SRDF/TimeFinder Manager for IBM i Product Guide, available on Dell EMC Online Support.

• Control menu

The Dell EMC SRDF/TimeFinder Manager for IBM i Control menu executes commands that perform control actions for all supported SRDF and TimeFinder operations and other system-control operations from an IBM i host using screens instead of a command line. For more information on this menu, refer to the latest EMC SRDF/TimeFinder Manager for IBM i Product Guide, available on Dell EMC Online Support.















◆ IBM i commands

SRDF/TimeFinder Manager uses the concept of an image as the high-level controlling object and paths and steps for representing how data on the source device gets to data on one or more target devices.

For more details on the user interface, refer to the latest EMC SRDF/TimeFinder Manager for IBM i Product Guide, available on Dell EMC Online Support.

Installing SRDF/TimeFinder Manager

EMC SRDF /TimeFinder Manager for IBM i Product Guide version 8.0 and higher, located on Dell EMC Online Support, describes how to prepare for installing SRDF/TimeFinder Manager in both a standard and IASP environment and provides information on how to perform new installations of SRDF/TimeFinder Manager and to upgrade from previous versions. This guide also provides information on features, such as eLicenses.

SRDF/TimeFinder Manager is installed on the source IBM i host. Systems with multiple logical partitions (LPARs) must have SRDF/TimeFinder Manager installed on each LPAR that controls TimeFinder BCV or SRDF devices.

In a multinode configuration with IASP support, the SRDF/TimeFinder Manager client is installed on the additional nodes.

Before you install SRDF/TimeFinder Manager, all systems participating in the replication solution must meet the minimum SRDF/TimeFinder Manager base (hardware and software) requirements, outlined in the “Environment and system requirements” section of the most current EMC SRDF/TimeFinder Manager for IBM i Release Notes, available on Dell EMC Online Support.

Configuring SRDF/TimeFinder Manager

Before using SRDF/TimeFinder Manager to control SRDF and BCV devices and monitor their status, several configuration tasks must be performed. To configure SRDF/TimeFinder Manager to control SRDF and TimeFinder replication environments used with IBM i hosts, or to configure the SRDF/TimeFinder Manger environment, refer to the EMC SRDF/TimeFinder Manager for IBM i Product Guide, available on Dell EMC Online Support. A configuration task checklist is also provided in this document.

Related documentation

Related documents include:

◆ EMC SRDF/TimeFinder Manager for IBM i Version 8.0 Product Guide


















◆ EMC SRDF/TimeFinder Manager for IBM i Release Notes


◆ EMC VMAX3 Family Product Guide

◆ EMC Solutions Enabler SRDF Family CLI User Guide

◆ EMC Symmetrix VMAX Family with Enginuity Product guide

◆ EMC VMAX3 Family with HYPERMAX OS VMAX 100K, VMAX 200K, VMAX 400K Product Guide

For a complete list of IBM reference material, refer to the IBM Redbooks page and theIBM Knowledge Center.

Note: IBM i is an integrated operating environment formerly referred to as IBM i5/OS. Documentation might refer to IBM i as i5/OS.








Solutions EnablerDell EMC Solutions Enabler (SE) runs on a wide variety of operating systems. For detailed interoperability and support information, always refer to the support matrices located at Dell EMC E-Lab Interoperability Navigator.

SE provides the host with SYMAPI, CLARAPI, and STORAPI shared libraries for use by Solutions Enabler applications, and the Symmetrix Command Line Interface (SYMCLI) for use by Storage Administrators and Systems Engineers. SYMCLI is a specialized library of commands that are available on a UNIX or Windows CLI. It supports single command line entries and scripts to map and perform control operations on devices and data objects. It can also be used to monitor device configuration and status of devices that make up the storage environment.

Note: SRDF/TimeFinder Manager for IBM i uses SYMAPI for VMAX functionality. SYMCLI support is limited on IBM i. Refer to the “Supported Solutions Enabler CLI commands” in the EMC SRDF /TimeFinder Manager Product Guide for IBM i for the latest information.

SYMCLI usage in IBM i environments

As previously explained, Dell EMC STM for IBM i runs natively on the IBM i host and is primarily used to configure, control, and monitor the local and/or remote replication of the IBM i host's volumes. STM is only capable of controlling the volumes that are owned by this host.

SE or SYMCLI provides an additional method for IBM i or storage administrators to view and control the entire VMAX environment. It is important to understand that some operations can simply NOT be done from the connected host itself, regardless of whether it is an IBM i, Windows UNIX, or Mainframe host. To illustrate this, consider the following two example scenarios.

Scenario 1

One of the safety precautions with SRDF is to allow no updates (writes) to the replicated volume. If you are replicating a local production volume to the remote site for DR purposes, you do not want anyone to be able to touch that volume as it is your "golden DR copy" of the production data. Therefore, these target volumes are Write_Disabled. Should you need to failover to the remote site for any reason, operations can be stopped on the local site and resumed on the remote volumes. Likewise, as a safety precaution, the original local volumes then become Write_Disabled. While a running host can obviously not Write_Disable its own volumes, such failover operations have to be run from an external server. This is where the SYMCLI software is useful.

Scenario 2

You need to recover if you experience a full failure of the production host or even the entire site. In this case, your primary host and its instance of STM is unavailable so an alternative interface to the Symmetrix is required. SYMCLI can be used to control the failover, etc.

Solutions Enabler 107




Note: These two scenarios for DR failover are specific to regular ASP environments. For iASP environments, the remote IBM i cluster node is available to run the required commands. In that case, for DR operations, SYMCLI is not required.

SYMCLI also provides advanced configuration options for the entire VMAX environment, such as the creation of new devices, mapping devices to front-end FC ports, granting host initiator ports access to devices, setting up TF and SRDF replication, and so on.

For further details, refer to the appropriate Solutions Enabler documentation available on Dell EMC Online Support.







Dell EMC Unisphere for VMAX GUIDell EMC Unisphere for VMAX is a browser-based product that provides a single pane of glass for essential storage management and performance reporting activities on VMAX arrays. It offers big-button navigation and streamlined operations to simplify and reduce the time required to manage your Symmetrix environment. Unisphere for VMAX reflects Dell EMC's shift to simpler and more intuitive management for operations including storage volume configuration, data protection, FAST VP configuration, and performance reporting and analysis. Management of D910 devices connected to IBM i hosts is supported.

Unisphere for VMAX provides a GUI to the VMAX array for the same monitoring and control operations where SYMCLI can be used. Storage provisioning for hosts connected to the VMAX can be done with Unisphere for VMAX or SYMCLI. Users can manage operations from device creation to virtual provisioning to replication configuration and monitoring.

Note: Unisphere for VMAX can run on Windows, UNIX, or Linux. It is also available as Virtual Appliances.

VMAX and IBM i

VMAX introduced the concept of Auto-provisioning Groups. Unisphere for VMAX can now easily provision storage to new and existing host systems, including IBM i LPARs. Auto-provisioning Groups allow the user to predefine groups of resources, such as host FC IOA-initiator groups, VMAX storage devices groups, and VMAX FA-port groups. These individual groups can then be combined into a relationship, called a masking view, to grant host access to VMAX devices over the predefined storage ports and host initiators. Once these groups and masking views have initially been created, new storage devices (i.e., new IBM i disk units) can easily be assigned by just adding them to an existing storage group. All required operations will be processed in the background (channel assignment, LUN address, and masking).

This provisioning task just takes a few mouse clicks on the management console window; then the provisioning task is executed in a few seconds, after which the devices are instantly available on the "Display Non-Configured Units" screen. From there, the new disks can be simply added to the desired ASP by the IBM i administrator.

This is just one example of how the functionality in Unisphere for VMAX provides great value for storage and IBM i administrators. For further details, refer to the appropriate Unisphere for VMAX documentation available on Dell EMC Online Support.

Dell EMC Unisphere for VMAX GUI 109





CHAPTER 6

This chapter provides information on how to install the IBM i server.

◆ Prerequisites ....................................................................................................... 112◆ Installation procedures ........................................................................................ 113◆ Failure recovery scenarios.................................................................................. 120

Server Installation

Server Installation 111

Server Installation

PrerequisitesBefore installing the IBM i server, refer to the following:

◆ For the most up-to-date information, always consult the Dell EMC Simple Support Matrix, available through Dell EMC E-Lab Interoperability Navigator.

◆ Refer to the Documentation Library on Dell EMC Online Support for the following documentation:

• EMC SRDF/TimeFinder Manager (STM) Product Manual

• EMC SRDF/TimeFinder Manager for IBM i Product Guide

• EMC SRDF/TimeFinder Manager for IBM i Release Notes









Server Installation

Installation procedures Before adding a disk to a IBM i partition, you must first set up to boot from SAN at the Hardware Management Console (HMC).

Tag the boot-capable IOA to which the load source drive will be attached. This allows the system to find the load source unit during the D-mode IPL. Refer to IBM's Redbook, IBM i and IBM system storage guide to implementing External disks on IBM i, for more information.

On the HMC, perform the following steps:

1. Select the partition name with which you are working and then select Tasks > Configuration > Manage Profiles.

The Manage Profiles dialog box displays, as shown in Figure 10.

Figure 10 Manage Profiles dialog box

2. Select Actions > Edit.

The Logical Partition Profile Properties window displays, as shown in Figure 10.

Figure 11 Logical Partition Profile Properties window

Installation procedures 113

Server Installation

3. In the Logical Partition Profile Properties window select the Tagged I/O tab, shown in Figure 12.

Figure 12 Tagged I/O tab

a. In the Load source pull-down menu, select the IOA that you want to correspond to the load source.

b. In the Alternate restart device pull-down menu, select the disk controller where the CD/DVD ROM is located.

c. In the Console pull-down menu, select the console. In this case, it is the Hardware Management Console.

d. Click OK to save your settings for the LPAR profile.


Server Installation

The Managed Profiles dialog box displays, as shown in Figure 13.

Figure 13 Managed Profiles dialog box

4. Click Close.

5. Change the IPL attributes to perform a manual D-Mode IPL.

Change the partition to perform a manual IPL as follows:

a. From the HMC, select Tasks >Properties.

The Partition Properties window displays.


Server Installation

b. In the Partition Properties window, select the Settings tab and choose the IPL Source, D.


Server Installation

c. In the Settings tab, Keylock position, select Manual.

d. Click OK when done.

Activate the partition

To activate the partition, complete the following steps:

1. Insert the LIC CD into the alternate IPL DVD-ROM device and perform a D-mode IPL by selecting the partition and choosing Tasks > Operations > Activate.

IMPORTANT

Prior to activating the system, make sure the load source drive on the Symmetrix system is the only drive assigned or masked to that IOA. Alternately, make sure to select the volume you want to be the load source from the list of devices presented on the screen.


Server Installation

The Activate Logical Partition window displays, as shown in Figure 14.

Figure 14 Activate Logical Partition window

2. In the Activate Logical Partition window, select the partition profile to be used and click OK.

This window closes and a terminal window/console session displays.

When at the DST, you will be required to first choose a language. 2924 is the default (English) language to install.

3. On the Confirm Language Group dialog box, press Enter to confirm the language code.

4. On the Install Licensed Internal Code screen select:

1. Install Licensed Internal Code.


Server Installation

The next panel shows the volume that is selected as the external load source unit (Confirm Serial Number and Emulation SN = xxxxyyyy x=Symmetrix device number y = Symmetrix serial number), there is also e a list of options for installing the Licensed Internal Code. Select 2.

2. Install Licensed Internal Code and Initialize System.

The Confirmation panel displays. Read the warning message and press F10 to continue the installation

This will initialize the load source disk and install license internal code to the disk. Once this is complete, the system will perform an IPL and return to DST. You will then need to log back into DST. You will need to create a new or temporary DST password.

The default new login is QSECOFR and the password is QSECOFR (case sensitive).

Continue to load the operating system and install licenced programs as you normally would. See the IBM manuals located at http://www.ibm.com for software installation on System i.


Server Installation

Failure recovery scenarios Refer to the following documentation located on Dell EMC Online Support for failure recovery scenarios:

◆ EMC SRDF/TimeFinder Manager (STM) Product Manual






CHAPTER 7

This chapter introduces the concepts and architecture of Virtual I/O Server (VIOS) and then explains how to configure a VIOS and an iClient using Symmetrix volumes with Dell EMC Enginuity operating environment for Symmetrix release level 5875, using Dell EMC TimeFinder volumes in an IBM i environment.

◆ Introduction to Virtual I/O Server....................................................................... 122◆ Configuring VIOS ............................................................................................... 125◆ Installing the Virtual I/O Server and Virtual I/O Client........................................ 134◆ Installing Symmetrix definitions to the AIX ODM................................................ 136◆ Configuring Virtual I/O client with Dell EMC-attached storage ........................... 137◆ Performing a D-IPL and installing the iClient ...................................................... 142◆ TimeFinder in a VIOS and IBM i environment ..................................................... 143

Open Storage and Virtual I/O Server (VIOS) for IBM i

Open Storage and Virtual I/O Server (VIOS) for IBM i 121


Introduction to Virtual I/O ServerThis section contains the following introductory information for Virtual I/O Server (VIOS):

◆ “Overview” on page 122

VIOS supports two different ways to share storage, also introduced in this section:

◆ “Virtual SCSI” on page 122

◆ “Virtual Fibre Channel” on page 123

Overview

Virtual I/O Server (VIOS) provides virtual SCSI target, virtual Fibre Channel, Shared Ethernet Adapter, and PowerVM™ Active Memory Sharing capability to client logical partitions within the POWER system. VIOS allows a physical adapter with attached disks on the VIOS partition to be shared by one or more Virtual I/O Client (VIOC) partitions, enabling clients to consolidate and minimize the number of physical adapters. Virtual I/O Server supports client logical partitions (LPARs) that run IBM AIX 5.3 or later, IBM i 6.1 or later, and several specific Linux on IBM System p releases.

The VIOS partition is not intended to run applications or to accept general user logins. It is used for specific commands, such as oem_setup_env, allowing the installation of software products. These products include Dell EMC ODM support software and Dell EMC PowerPathTM multipathing software.

Figure 15 on page 122 shows the architecture of a VIOS serving Virtual I/Os to multiple client logical partitions.

Figure 15 VIOS architecture serving multiple client LPARs

Virtual SCSI

Virtual SCSI (VSCSI) is based on a client-server relationship. The Virtual I/O Server owns the physical resources and the virtual SCSI server adapters. It acts as a server, or SCSI target device. The client logical partitions are configured with the virtual SCSI client adapter as the SCSI initiator and access the virtual SCSI targets as standard SCSI LUNs. Physical storage owned by the Virtual I/O Server can be exported and

POWER Hypervisor

Virtual I/OServer

Partition

ICO-IMG-000894

Virtual I/Opaths

ClientLPAR1

IBM i

ClientLPAR2

AIX

ClientLPAR3

LinuxEthernetsharing

Storagesharing

Network



assigned to a virtual SCSI server adapter. Then, that storage can be accessed by the client logical partition through a virtual SCSI client adapter. The virtual SCSI client adapter recognizes standard SCSI devices and LUNs through this virtual adapter.

Figure 16 shows a standard virtual SCSI configuration.

Figure 16 Virtual SCSI configuration example

Virtual Fibre Channel

N_Port ID Virtualization (NPIV) is a standard technology for Fibre Channel networks. With NPIV, multiple logical partitions can access independent physical storage through the same physical Fibre Channel adapter. In a VIOS environment which is assigned with the physical Fibre Channel adapters that support NPIV, virtual Fibre Channel adapters can be configured to provide client logical partitions with Fibre Channel connections to a storage area network through the VIOS.

Note: In a VIOS configuration, the use of D910 with NPIV requires a minimum OS of 7.1. Refer to the Implementing D910 Devices on EMC VMAX3 Storage Arrays (VMAX 100K, 200K, and 400K Models) White Paper and Implementing D910 Devices on EMC Symmetrix VMAX 40K and VMAX 20K/ VMAX Storage Arrays White Paper, located on Dell EMC Online Support, for more information about D910.

There are two different virtual Fibre Channel adapters:

◆ Virtual Fibre Channel adapters on the client logical partitions

• Referred to as client virtual Fibre Channel adapters

◆ Virtual Fibre Channel adapters on the VIOS partition

• Referred to as server virtual Fibre Channel adapters

Client virtual Fibre Channel adapters need to be paired with server virtual Fibre Channel adapters to provide connections between client logical partitions and the VIOS partition. The VIOS partition provides the connection between the server virtual Fibre Channel adapters and the physical Fibre Channel adapters.

POWER Hypervisor

Virtual I/OServer

Partition

ICO-IMG-000895

Physical HBAs

VSCSI serveradapters

VSCSI clientadapters

ClientLPAR1

IBM i

ClientLPAR2

AIX

ClientLPAR3

Linux

Virtual I/Opaths

Introduction to Virtual I/O Server 123





Figure 17 shows a managed system configured to use NPIV.

Figure 17 Virtual Fibre Channel architecture example

The VIOS partition is created using the Hardware Management Console (HMC). The VIOS installation media ships with the POWER system that is configured with the PowerVM feature and can be installed by any of the following methods:

◆ Media (assigning the DVD-ROM drive to the partition and booting from the media)

◆ The HMC (inserting the media in the DVD-ROM drive on the HMC and using the installios command)

◆ Using Network Installation Management (NIM)

For more information on Virtual I/O Server in an IBM i environment, refer to related documentation on the IBM Information Center web location:

http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp

POWER Hypervisor

Virtual I/OServer

Partition

ICO-IMG-000896

ClientLPAR1

IBM i

ClientLPAR2

AIX

ClientLPAR3

Linux

Virtual I/Opaths

SAN

Physicalstorage 1

Physicalstorage 2

Physicalstorage 3

Physical storage

Physical FC adapter

Server virtual FC adapter

Client virtual FC adapter



Configuring VIOSAs described in “Overview” on page 122, VIOS can provide storage sharing for client logical partitions with IBM i installed. This section explains how to configure a VIOS to provide virtual SCSI storage sharing for IBM i client LPARs. This section contains the following information:

◆ “Logical architecture of example VIOS environment” on page 125

◆ “Basic configurations” on page 126

Logical architecture of example VIOS environment

The logical architecture of this example’s VIOS environment is illustrated in Figure 18.

Figure 18 Logical architecture of the example VIOS environment

In this example’s environment, an IBM Power system is partitioned into three logical partitions:

◆ VIOS (VIO)◆ iClient source (iClient_Served_By_VIO) ◆ iClient target (iClient_Target)

The physical FC HBA card of VIOS is attached directly to SAN and can access LUNs on Dell EMC Symmetrix VMAX 40K or VMAX 20K/VMAX. LUNs on VMAX 40K or VMAX 20K/VMAX are mapped to VIOS and then shared by iClients through virtual SCSI adapters.

EMC Symmetrix VMAXICO-IMG-000897

LAN

VIOC (iClient_Served_By_VIO)

VIOS (VIO)

Loadsource

Loadsource

vSCSiadaptervscsi0

vSCSiadaptervhost0

vSCSiadaptervhost3

vSCSiadaptervscsi0

EthernetAdapter

EthernetAdapter

EthernetAdapter

VIOC (iClient_Target)

hdisk1 hdisk11

FC HBA Card

LUNSTV

LUNBCV

TimeFinder/Mirror

SAN Fabric

Configuring VIOS 125


Dell EMC TimeFinder/Mirror (actually emulated by TimeFinder/Clone on VMAX 40K or VMAX 20K/VMAX is used to get a BCV copy of the load source of iClient source, which is stored on VMAX 40K or VMAX 20K/VMAX. After synchronization, this BCV can be used as the load source of iClient target.

Assumptions Before starting detailed configurations, preliminary works such as hardware deployment, cable connections, and setting up the HMC are assumed to have been finished.

In addition, HBAs of the power system need to be connected to the SAN, and SAN zoning must be done to ensure that Dell EMC storage volumes can be accessed from those HBAs.

Basic configurations

For such a VIOS environment setup, basic configurations consists of the following, discussed further in this section:

◆ “Configuring Symmetrix array devices” on page 126

◆ “Configuring logical partitions on HMC” on page 128

◆ “Configuring virtual SCSI (VSCSI) adapters for VIOS and iClient” on page 130

◆ “Configuring a virtual SCSI (VSCSI) adapter on the HMC: iClient partition” on page 131

Configuring Symmetrix array devicesFor the VIOS to host an iClient, the Symmetrix array must be low-level formatted and configured with Server emulation, instead of the usual 2105 or 2107 emulation device types for IBM i. To configure devices in the Symmetrix array, you can use Solutions Enabler commands.

Creating devices

To create devices, use the symconfigure command.

When creating devices, "emulation type" cannot be specified as "AS/400_M2107_Ann" or "AS/400_M2105_Ann" (nn refers to 85 or 05, etc.) which are used when Dell EMC Symmetrix arrays are directly connected with an IBM i host. Instead, it must be specified as "FBA".

Moreover, unlike IBM i devices whose sizes must be set to specific numbers, "device size" for VIOS can be set freely.



Figure 19 shows those attributes. In addition, you can see that the "Device Block Size" is 512 bytes, not 520 bytes for IBM i.

Figure 19 Symmetrix device attributes for VIOS

Auto provisioning

Auto provisioning can be performed by using the symaccess SYMCLI command. After issuing that command, device mapping and masking is finished automatically.

Symmetrix port flags for VIOS

Figure 20 shows some flags of Symmetrix directors configured for VIOS. The flags are the same as IBM AIX host settings. The flags that are currently set are: C, SC3, SPC2, PP, UWN, ACLX, and EAN. Note that AS4 and V are not set.

Figure 20 Port flags of Symmetrix directors configured for VIOS



Configuring logical partitions on HMCFigure 21 shows the HMC with three partitions configured on an M25-managed system. VIOS will host the storage for the iClient source, and iClient target.

Figure 21 HMC with three partitions configured

Figure 22 on page 129 shows the VIOS LPAR configuration. The I/O for all VIOS served partitions must be allocated to the VIOS partition and then presented to the clients. For this configuration, a dedicated processor and 1 GB of memory was allocated just for VIOS use. The processors and memory for the iClient partitions (not shown) are allocated to each partition, just as before.



Figure 22 VIOS configuration, physical I/O allocated to VIOS partition



Configuring virtual SCSI (VSCSI) adapters for VIOS and iClient Access the Virtual Adapters tab, as shown in Figure 23, to create the Server SCSI virtual client adapters that will serve the iClient. Use the Action drop-down menu at the top left corner of this tab to create VSCSI server adapters that will serve the iClients.

Figure 23 Virtual Adapter tab

Figure 24 shows the VSCSI adapter on the VIOS partition that was created to attach to the iClient.

Figure 24 VSCSI adapter

To create the connection, select Create/SCSI Adapter from the Action drop-down menu in the Virtual Adapter tab, shown in Figure 23 on page 130.



Figure 25 shows a virtual SCSI server ID 12 that was created to serve and connect to the iClient with client adapter ID set to 4.

Figure 25 VSCSI server

Configuring a virtual SCSI (VSCSI) adapter on the HMC: iClient partitionAfter configuring the iClient Source and iClient target LPARs with regard to allocating memory and processing, access the Virtual Adapters tab to configure the client adapter to point to the VIOS host adapter.

Figure 26 shows the iClient HMC configuration, Virtual Adapter tab. Note that this is the inverse of what was created on the VIOS host. In this example, VSCSI adapter ID4 was created to connect to 12 on the VIOS.

Figure 26 iClient HMC configuration, Virtual Adapter tab



Figure 27 shows the client adapter 4 details.

Figure 27 VSCSI adapter properties set to 4

Figure 28 shows a tagged I/O profile for the iClient. Note that the load source will be from the VIOS controlling host. This is the VSCSI adapter 4 created that points to ID12 on the VIOS host. The alternate restart device is a virtual SCSI device that is configured to the CD-ROM and disk controller on the VIOS as well.

Figure 28 Tagged I/O profile for the iClient



Figure 29 shows there is no dedicated I/O on the virtual iClient other than a dedicated Ethernet connection. In this example, Ethernet is used outside of virtualization. This allows a virtual iClient to have dedicated hardware.

Figure 29 No dedicated I/O on the virtual iClient (except for Ethernet NIC)

Do the same for the iClient target on both the VIOS host and the client and create VSCSI adapters that point to each other.



Installing the Virtual I/O Server and Virtual I/O Client The Virtual I/O Server and Virtual I/O Clients must be installed in a specific order.

After VIOS is installed, some configuration needs to be performed before installing the iClient. This section explains the installation and configuration step by step.

Installing the VIOS and configuring the network

Once the Virtual I/O Server partition is successfully created, install the VIOS.

To install the VIOS, complete the following steps.

1. Activate the partition and enter the System Management Services (SMS) mode.

2. Insert the Virtual I/O Server installation DVD into the DVD-ROM drive and select the boot option to use the CD/DVD-ROM.

3. Restart the Virtual I/O Server by exiting the SMS mode and selecting to reboot in normal mode.

4. When the Virtual I/O Server is rebooting from the DVD, it should be able to be installed onto the SAN disk that was created.

Note: For detailed instructions for the VIOS load, refer to the PowerVM Virtualization on IBM System p: Introduction and Configuration Redbook at http://www.redbooks.ibm.com. This Redbook takes you through the installation command and selection of a disk for the rootvg to store the VIOS operating system.

The latest releases of the VIOS require a minimum of 30 GB of disk space to store the contents of the installation media.

When the installation procedure has finished, use the padmin user name to log in. Upon initial login, supply the password. There is no default password.

Note: After a successful login, you will be redirected to the Virtual I/O Server command line interface (CLI).

To accept the Software Maintenance Agreement terms, type a and press Enter.

To accept the license, enter the following command:

$ license -accept



Configure the network interface using the cfgassist command, which displays the Config Assist for VIOS screen, as shown in Figure 30.

Figure 30 Config Assist for VIOS screen

After the VIOS partition is created and is ready to serve the iClient, bring the Symmetrix FAs online to the VIOS host for the storage you want to use on the client.

Note: The Redpiece PowerVM Virtualization on IBM System p: Managing and Monitoring Redbook, located on http://www.redbooks.ibm.com, will help with the VIOS disk configuration portion of the next step and also contains a VIOS command reference.

Installing the Virtual I/O Server and Virtual I/O Client 135


Installing Symmetrix definitions to the AIX ODMThe following procedure downloads and installs the AIX ODM definitions for Symmetrix and CLARiiON release 13 or higher:

1. From the FTP server, ftp.EMC.com, download the most recent ODM fileset. Log in using ftp and your email address as password. Navigate to the following location:

/pub/elab/aix/ODM_DEFINITIONS

2. In the /tmp directory, uncompress the fileset. Substitute the appropriate filename revision for the command to work properly:

uncompress EMC.AIX.X.X.X.tar.Z

After uncompressing the fileset, the .tar extension remains.

3. Untar the resulting file. Substitute the appropriate filename revision for the command to work properly:

tar -xvf EMC.AIX.X.X.X.tar

4. Start the installation by typing the following:

oem_setup_envsmit installp

5. Select Install Software.

6. Place a dot [.] in the [entry field] and press Enter.

7. Use the List function (Esc+4) to see the software to install.

Install Dell EMC Symmetrix AIX Support Software and one other, depending on the configuration.

• If using VIOS with single path or Dell EMC PowerPath, also select Dell EMC Symmetrix FCP Support Software.

• If you do not install PowerPath and are going to do MPIO to the VIOS host, load Dell EMC Symmetrix FCP MPIO Support Software instead.

8. Press Enter after making all desired selections. You can take the default options.

9. Scroll down to the bottom of the window to see the Installation Summary and verify that the “SUCCESS” message appears.

10. Reboot the host for all changes to take effect.



Configuring Virtual I/O client with Dell EMC-attached storage

Complete the following steps to configure virtual SCSI devices.

Note: Dell EMC recommends creating a PVID on each disk.

1. Before mapping the Virtual SCSI with the physical hdisk, create PVIDs on the hdisk or hdiskpower devices. This will assist in understanding the device relationships between the VIOS and the Virtual I/O client (VIOC).

2. Type the following command (where <x> is the device instance) on the VIOS for all the configured hdisk or hdiskpower devices:

> chdev -l hdisk<x> -a pv=yes

3. Type the lspv command to display configured devices:

> lspv

The follow ii ng output displays:

hdisk0 00cfa11d15552dd5 rootvg activehdisk1 00cfa11d72d77343 Nonehdisk2 00cfa11d72dde22c Nonehdisk3 00cfa11d72d53f81 Nonehdisk4 00cfa11d72dba7e8 Nonehdisk5 00cfa11d72dea14a Nonehdisk6 00cfa11d72dd8fdd Nonehdisk7 00cfa11d72d6eda6 None

4. Type the exit command to exit the shell.

5. Map Symmetrix LUNs to the host on a one-for-one basis. For each Symmetrix LUN number presented to the VIOS as an hdisk, create one VTSCSI LUN and associate it to the appropriate VSCSI adapter using VIOS commands.

Note: The following pertains to the number of physical LUNs per port and the number of VTSCSI LUNs per VSCSI adapter. For optimal performance, keep the number of physical LUNs per port on the Symmetrix FA assigned to the physical IOA the same as the number of LUNs on the virtual SCSI adapter (for both ease of use and reduced complexity).

The IBM i Virtualization and Open Storage Read-me First claims up to 16 LUNs can be virtualized to IBM i through a single virtual SCSI connection. If more than 16 LUNs are required in an IBM i client partition, you must create an additional pair of virtual SCSI server (VIOS) and client (IBM i) adapters in the HMC. You can link additional LUNs available in VIOS to the new vhostX device through vtscsiX devices, making them available to IBM i.

Configuring Virtual I/O client with Dell EMC-attached storage 137


6. Use the lsdev command on the VIOS console to view the hdisks from the Symmetrix array on the VIOS server, as shown in Figure 31.

Figure 31 View hdisks with lsdev command in multipath environment

Figure 31 shows an example in a multipath environment.

Figure 32 shows an example in a non-multipath environment.

Figure 32 View hdisks with lsdev command in non-multipath environment



Figure 33 shows deeper look at the hdisk1 with the lsdev -dev hdisk1 -vpd; the Symmetrix device CA is on cab 53. The example also shows the Symmetrix cab number and the device number in hex on the line entitled Serial Number.

Figure 33 hdisk1 with the lsdev -dev hdisk1 -vpd

7. Repeat the identification process for all hdisks to ensure that what you are mapping in the next step is correct.

8. Find the vhost to VSCSIxx relationship:

lsmap -all

9. Figure 34 shows a vhost0 associated with C12. The C12 indicate VSCSI adapter ID12 that we created on the VIOS partition.

Figure 34 vhost to VSCSIxx relationship

10. Create the virtual devices from the hdisks and map them to the appropriate adapter with the following VIOS commands from step 11 through step 17.

11. Type the lsdev -virtual command to confirm that the virtual SCSI adapter is available

$ lsdev -virtual



The following output displays:

name status descriptionent2 Available Virtual I/O Ethernet Adapter (l-lan)vhost0 Available Virtual SCSI Server Adaptervhost1 Available Virtual SCSI Server Adapter

12. Create a virtual target device, which maps the Virtual SCSI Server adapter vhost0 to the hdisk01 device.

13. Type the mkvdev command for each device instance:

$ mkvdev -vdev hdisk01 -vadapter vhost0


vtscsi0 Available

14. Type the lsdev command to show the newly created Virtual target devices:

$ lsdev -virtual


name status descriptionent2 Available Virtual I/O Ethernet Adapter (l-lan)vhost0 Available Virtual SCSI Server Adaptervtscsi1 Available Virtual Target Device - Diskvtscsi2 Available Virtual Target Device - Diskvtscsi3 Available Virtual Target Device - Diskvtscsi4 Available Virtual Target Device - Diskvtscsi5 Available Virtual Target Device - Diskvtscsi6 Available Virtual Target Device - Diskvtscsi7 Available Virtual Target Device - Disk

15. Type the lsmap command to show the logical connections between the newly created devices:

$ lsmap -all? mm


$ lsmap -allSVSA ID Physloc Client Partition----------------------------------------------------------------------------vhost 0U9408.M25.102C492-V2-C12 0x00000001

Status AvailableLUN 0x8100000000000000Backing device hdisk0Physloc U789C.001.DQD3602-P1-C3-T1-W500009720800D59C-L0

VTD vtscsi1LUN 0x8200000000000000Backing device hdisk1Physloc U789C.001.DQD3602-P1-C3-T1-W500009720800D59C-L100000000000


VTD vtscsi3LUN 0x8400000000000000



Backing device hdisk3Physloc U789C.001.DQD3602-P1-C3-T1-W500009720800D59C-L3000000000000


VTD vtscsi5LUN 0x8600000000000000Backing device hdisk5

etc...16. If planning to use the managed system to do the D-IPL, create a Virtual Optical

device by associating the physical CD0 with a virtual adapter, in this case vhost1.

17. Type the following command:

$ mkvdev -vdev cd0 -vadapter vhost1


vtopt0 Available

18. Once the Virtual I/O Client devices are exported, proceed in activating the Client Partition and install the operating system on the virtual Client.



Performing a D-IPL and installing the iClientOnce the steps are completed for configuring virtual SCSI devices, you can now perform a D-IPL and install the iClient.

To perform a D-IPL and install the iClient, complete these steps:

1. D-IPL iClient partition 1 and load the operating system. The system is set to D-IPL on the virtual SCSI adapter.

2. Place the O/S Base CD in the managed system and do the O/S load.

Figure 35 shows how a virtualized disk appears to the IBM i host.

Figure 35 Virtualized disk on an IBM i host



TimeFinder in a VIOS and IBM i environmentDell EMC TimeFinder is a family of local replication products that operate in a single VMAX array and can non-disruptively create and manage point-in-time copies of data volumes.

◆ TimeFinder/Clone provides full copies of source volumes.

◆ TimeFinder/Snap provide space-saving pointer-based copies of source volumes.

◆ TimeFinder SnapVX is the new and only option available for local replication in a VMAX3 array. In order to be backward compatible with existing scripts or configurations, it uses clone and snap emulation.

Note: VMAX 10K xxx987xxxx does not support TimeFinder/Snap.

Although Dell EMC's native STM IBMi software cannot be used on the IBM i client LPAR (VIOC) in the VIOS/VSCSI environment, the next section shows that TimeFinder can still provide a business continuity solution for IBM i environments, by controlling the replication from an external server.

The major steps, explained further in this section, consist of:

◆ “Performing TimeFinder functions” on page 143

◆ “Performing an IPL on the virtual client” on page 145

◆ “Mapping TimeFinder devices” on page 145

Performing TimeFinder functions

Once the IBM i host is installed, go to the external host that has Unisphere or SYMCLI installed and create the replication pairs. In the following example, on the VMAX array, the standard devices are CA to D4 and the BCVs are E4 to EE. This example uses a Windows server with Unisphere and SYMCLI to control an environment with symmir (BCV) commands. A similar approach is used when creating and activating Clone or Snap copies with their respective commands (symclone, symsnap, symsnapvx).

1. Create a device group and associate the standard and BCV devices. Figure 36 on page 144 shows how the device group displays in Unisphere for VMAX, showing the group "vios" and the association (for two targets).

TimeFinder in a VIOS and IBM i environment 143


Figure 36 Unisphere for VMAX device group display

2. In Solutions Enabler, start a TimeFinder/Mirror session and monitor the progress of the session, as shown in Figure 37.

Figure 37 Initiating a TimeFinder/Mirror session

3. Monitor the progress of the session by entering the following command:

symmir -g vios query



Figure 38 shows the output of the symmir -g vios query command.

Figure 38 Output of the symmir -g vios query command

Performing an IPL on the virtual client

Wait for synchronized status and then split the BCV relationship after powering off the Source iClient.

1. Perform the Split operation and power up the iClient source, as shown in Figure 39.

Figure 39 Perform a Split operation and power up the iClient source

2. After the split operation, present the BCVs to the VIOS partition and associate the hdisks to VTSCSI and virtual adapters in the same way as was performed in step 10 on page 139 through step 17 on page page 141.

Mapping TimeFinder devices

1. Create the virtual devices from the hdisks and map them to the appropriate adapter with the following VIOS command:

mkdev -vdev hdisk11 -vadapter vhost3

2. Repeat the process for each Symmetrix BCV LUNs you need to present to the virtual target client on vhost3 (C15) Client partition3.

3. IPL the iClient target and run testing against the image of the source.

TimeFinder in a VIOS and IBM i environment 145


If you want to run a tape backup of the virtual client, you will have to follow the tape backup rules as set forth in IBM documentation for VIOS (back up, then FTP).

Once the steps are complete, you can perform an Establish and Split operation and then present the BCV image without the mapping step, unless the configuration changes.


APPENDIX A

This appendix provides information for creating an IBM i system configuration listing:

◆ Generating a system listing ................................................................................ 148

Creating an IBM i System Configuration Listing

Creating an IBM i System Configuration Listing 147


Generating a system listingThe IBM iSeries System configuration listing, often referred to as a rack config, is a physical road map of the system.

The listing details the system units, system buses, adaptors, disk drives plus all the other components of the system.

To generate a system listing, complete the following steps:

1. Issue the STRSST command (start system tools) and sign in using a user and password that has the privileges to use SST's hardware service manager.

2. Once logged in, choose option 1, Start a Service Tool, from the initial menu.

3. From the next menu, choose option 7, Hardware service manager.

4. From this resulting screen, use the F6 function key to generate the system configuration listing. The following menu displays:

Figure 40 Print Format Options menu

5. Keep the default format (1) and then choose the option to print all the resources sorted by location.

6. Repeat the F6 option.

7. Choose option 2.

8. Repeat the process and choose option 3, to generate three listings.

The simplest way to convert the files is to open the System i Navigator software that is installed by default when Client Access is installed on a PC/Server.

Once the System i Navigator software has been opened, navigate to the “basic operations” section. Within that section, select the printer output.



When the files have been located in this section (the files are typically called qpcsmprt), right-click on the files and choose Export from the drop-down menu.

Figure 41 Export

At this point, a prompt for a Window directory in which the files are to be saved will appear. Choose the preferred location and click Save. The files are saved in a txt format for easy searching, manipulating, and emailing.

You can also choose to simply drag the files from the location in the printer output to your desktop. The files will be converted to text files and placed on your desktop.

If Client Access is not used, then the spool file can be converted to a database file and then transferred to a network drive to download the file to a PC. Refer to the IBM Knowledge Center for details.

Generating a system listing 149







GLOSSARYGloossary contains terms related tobusiness continuance operations and disk storagesubsyste. Many of these terms are used in this guide.

AAdapter Card that provides the physical interface between the director and disk devices,

director and serial channels (Serial adapter).

ASPs Auxiliary Storage Pools (ASPs) are individual disks (storage units) or sets of disks reserved for particular objects (such as libraries). ASPs help organize data to limit the impact of storage-device failures and reduce recovery time. ASPs can be used to isolate those objects to facilitate backup and recovery.

BBackup node The partition or host that is the secondary owner for a particular IASP. The backup

node has target devices connected to it.

BCV devices Standard Symmetrix devices with special attributes that allow the devices to independently support applications and processes. BCVs are active production images that are logically or physically separate from the production volumes with no reliance on the production host, thus providing protection from physical or logical corruption. Once the BCV task is complete, the volume can be resynchronized with the production volume, reassigned to another production volume, or maintained “as is” for another task. See also ”Standard devices.”

BCV mirror A standard device mirror (one of M2, M3, or M4) assigned to the BCV device upon establishing or re-establishing a BCV pair. See also ”Establish,” “Re-establish” and “BCV pair.”

BCV pair Consists of a standard device and a BCV device attached together.

Business Continuance(BC) Processes

Processes that allow customers to access and manage instant copies of Symmetrix standard devices. See also ”Establish,” “Re-establish” and “Split.”

Business ContinuanceVolume (BCV)

See ”BCV devices.”

CCache Random access electronic storage used to retain frequently used data from disk for

faster access by the channel.

Cache slot Unit of cache equivalent to one track.

GlossaryGloossary contains terms related to business continuance operations and disk storage subsyste. Many of these terms

GlossaryGloossary contains terms related to business continuance operations and disk storage subsyste. Many of these terms are used in this

Channel director The component in the Symmetrix subsystem that interfaces between the host channels and data storage. It transfers data between the channel and cache.

Concurrentestablished BCV pair

The relationship that establishes two BCV devices as concurrent mirrors of a single standard device that allows two synchronized copies of the standard data to be created simultaneously.

Consistency group A composite group is a user-defined group of devices that can span multiple Symmetrix arrays and, if needed, provide consistency protection. When an SRDF composite group is enabled for consistency protection, it is known as an SRDF consistency group. Consistency means that the devices within the group act in unison to preserve dependent-write consistency of a database that may be distributed across multiple Symmetrix arrays or multiple SRDF groups within a single Symmetrix. (A device group can be used for consistency protection if the group of devices is within a single SRDF group in a single Symmetrix array.)

CRG Cluster Resource Group.

DDA Disk Adapter. See ”Disk director.”

Data availability Access to any and all user data by the application.

DEFAULT_POOL A special Snap pool exists by default. This pool contains SAVE devices that have not been assigned to any named pools but are available for Snap operations. SAVE devices in the DEFAULT_POOL are either enabled or disabled but have used tracks. See also ”Save pool” and “Snap pool.”

Define BCV pair The process of identifying a BCV device and a standard device to be established.

Delayed Fast Write No existence of room in cache for the data presented by the write operation.

Dependent-write I/O A dependent-write I/O is one that cannot be issued until a related predecessor I/O has completed. Most application have imbedded dependent-write logic to ensure data integrity in the event of a failure in the host or server processor, software, storage subsystem, or if an environmental power failure occurs.

Dependent-writeconsistency

Dependent-write consistency is a data state where data integrity is guaranteed by dependent-write I/Os embedded in application logic. Database management systems are good examples of applications that utilize the dependent-write consistency strategy.

Destage The asynchronous write of new or updated data from cache to disk device.

Device A uniquely addressable part of the Symmetrix subsystem that consists of a set of access arms, the associated disk surfaces, and the electronic circuitry required to locate, read, and write data.

Device address The hexadecimal value that uniquely defines a physical I/O device on a channel path. A SCSI address consists of a Target ID and a Logical Unit Number (LUN).

Device number The value that logically identifies a disk device in a string.



Direct Access StorageDevice (DASD)

Most commonly known as a magnetic disk device.

Director The component in the Symmetrix subsystem that allows Symmetrix to transfer data between the host channels and disk devices. See also ”Channel director” and “Disk director.”

Disaster recovery The process of restoring a previous copy of the data and applying logs or other necessary processes to that copy to bring it to a known point of consistency.

Disaster recovery (DR)node

The node that takes over when the primary node fails, if part of a three-node solution.

Disk director The component in the Symmetrix subsystem that interfaces between cache and the disk devices.

Disk pool An auxiliary storage pool (ASP) of disks only. See also ”ASPs.”

DR node See ”Disaster recovery (DR) node.”

DSE pools SRDF uses SRDF/A DSE pools to extend the cache space available for SRDF/A cycles by offloading some or all of the cycle data from cache to pre-configured disk storage pool. Using SRDF/A DSE pools provides a safety net for running SRDF/A sessions; however, SRDF/A will continue to operate normally with this feature disabled. See also ”Snap pool.”

DSS Decision Support Systems. Database software used to support management decision making. Database data is extracted and analyzed, but not modified.

Dual-Initiator A Symmetrix feature that automatically creates a backup data path to the disk devices serviced directly by a disk director, if that disk director or the disk management hardware for those devices fails.

Dynamic Sparing A Symmetrix feature that automatically transfers data from a failing disk device to an available spare disk device without affecting data availability. This feature supports all nonmirrored devices in the Symmetrix subsystem.

EEA ESCON Adapter.

Establish A Business Continuance process which assigns a BCV device as the next available mirror of a standard device.

Established The BCV pair condition where the BCV device and standard device are synchronized and functioning as a Symmetrix mirror. A BCV pair is established by the BCV commands establish and re-establish.

FFC Fibre Channel. See ”Fibre Channel Director.”

153


Fibre Channel Director The component in the Symmetrix subsystem that interfaces between the host Fibre Channel interface and data storage. A Fibre Channel Director transfers data between the channel and cache.

GGatekeeper A small logical volume on a Symmetrix device used to pass SCSI commands from a

host to the Symmetrix. Gatekeeper devices are configured on standard Symmetrix disks using six cylinders (3 MB).

HHead and Disk

Assembly (HDA)A field replaceable unit in the Symmetrix subsystem containing the disk and actuator.

Hyper-VolumeExtension

The ability to define more than one logical volume on a single physical disk device making use of its full formatted capacity. These logical volumes are user-selectable in size. The minimum volume size is one cylinder and the maximum size depends on the disk device capacity and the emulation mode selected.

IIASP An independent disk pool, or independent auxiliary storage pool (ASP). An IASP is a

collection of disks that can be brought online or taken offline independently from the remainder of the system’s storage, which includes the system ASP, user ASPs, and other independent disk pools. An IASP can be either:

◆ Switchable among multiple systems in a clustered environment. ◆ Privately connected to a single server.

Identifier (ID) A sequence of bits or characters that identifies a program, device, controller, or system.

IFS Integrated File System.

Image The ASP set that can be operated on simultaneously.

Image types There are several image types (UDFS IASP or an image containing primary and all secondary IASPs that belong to the same ASP group). See also ”System image” and “UDFS.”

IML Initial microcode program loading.

Incremental Establish A time-saving operation similar to an Establish. The source (R1) device copies to the target (R2) device only the new data that was updated on the source R1 device while the SRDF pair was split. Any changed tracks on the target (R2) device are also refreshed from the corresponding tracks on the source (R1) device. The R2 device is write disabled to the target host.

Independent AuxiliaryStorage Pool

See ”IASP.”



Instant Split A method of splitting a BCV that improves the performance of a typical split operation by performing a quick foreground BCV split, which reduces the time the application needs to be frozen and is shorter than using a regular Split.

I/O device An addressable input/output unit, such as a disk device.

KKilobyte (K) 1024 bytes.

LLeast Recently Used

Algorithm (LRU)The algorithm used to identify and make cache space available by removing the least recently used data.

Logical partition A subset of a single IBM i host that contains resources (processors, memory, and input/output devices). A logical partition operates as an independent system. When hardware requirements are met, multiple logical partitions can exist within a system.

Logical volume A user-addressable unit of storage. In the Symmetrix subsystem, the user can define multiple logical volumes on a single physical disk device. Logical volumes can reside on an SRDF-enabled Symmetrix array, but do not participate in SRDF activity. Local volumes are typically protected either by local mirroring, RAID-S, or a dynamic spare.

LPAR A function of the OS/400 licensed program that enables the creation of logical partitions.

MMedia The disk surface on which data is stored.

Meta device A logical device that spans multiple physical devices, which are concatenated to create larger devices. A meta device consists of a meta head and its member devices. The meta head is the first device in the meta device sequence and is responsible for receiving all incoming commands. It also identifies the entire meta device. When an incoming command for the metahead is processed, the Symmetrix array determines which meta device member should execute the command. Meta-head devices can be added to a device group while a meta member cannot be added to a device group. This holds true for both standard and BCV devices. In an SRDF configuration, you can create meta devices for both primary and secondary volumes.

MII Machine Initiated Interrupt.

Mirroring The Symmetrix maintains identical copies of a designated volume on separate disks. Each volume automatically updates during a write operation. If one disk device fails, Symmetrix automatically uses the other disk device(s).

Mirrored pair A logical volume comprised of two or more physical devices with all data recorded on each device.

155


PPoint of consistency A point in time to which data can be restored and recovered or restarted and maintain

integrity for all data and applications.

Primary node The partition or host that is the primary owner for a particular IASP.

Private ASP A private independent ASP that is owned by a single system or a single LPAR. See also ”ASPs.”

Promotion The process of moving data from a track on the disk device to cache. See also ”Stage.”

Protected BCVEstablish

The process of moving all mirrors of locally-mirrored BCV devices to join the mirrors of a standard device.

QQuery A command that reports the state of all BCV devices in the system.

RR1 See ”Source volume (R1).”

R2 See ”Target volume (R2).”

RA RLD Adapter. See ”SRDF Remote Link Director.”

RAID Redundant Array of Independent Disks.

Rdfa DSE pool A collection of SAVE devices used for SRDF/A DSE. Also called Rdfa DSE Save Pool or Rdfa DSE Save Device Pool.

Read Hit Data requested by the read operation is in cache.

Read Miss Data requested by the read operation is not in cache.

Re-establish A BC process which reassigns a BCV device as the next available mirror of the standard device with which it was previously paired. The BCV mirror is updated with the data that was written to the standard device during the period that the BCV pair was split. The data that was written to the BCV device during the split is overwritten by data from the standard device.

Recreate A snap session that is recreated on an existing virtual device (VDEV) to prepare to activate a new point-in-time image. The Recreate action is only valid when issued against sessions which have been previously activated. This feature is available with Enginuity 5874 and later.

Restore Restore is the process that reinstates a prior copy of the data.

Rolling disaster A rolling disaster is a series of events that lead up to a complete disaster. For example, the loss of a communication link occurs prior to a site failure. Most disasters are rolling disasters; their duration may be only milliseconds or up to hours.



SSA SCSI Adapter.

SAVE device A device configured for use in TimeFinder/Snap operations and SRDF/A DSE. These devices not mapped to the host that provide polled physical storage space for storing pre-update images of the source device change tracks and new writes during a TimeFinder/Snap virtual copy session.

Save pool A collection of SAVE devices. Also called Save Device Pool.

Scrubbing The background process of reading, checking the error correction bits, and writing corrected data back to the source.

Snap device See ”Virtual device” and “SAVE device.”

Snap pool A collection of SAVE devices used for Snap operation. Also called Snap Save Pool or Snap Save Device Pool (formerly known as SaveDev Pool).

Source Image of anIASP

The set of the standard/R1 devices in a particular IASP.

Source volume (R1) A Symmetrix logical volume that is participating in SRDF operations. It resides in the local Symmetrix array. All CPUs attached to the Symmetrix may access a source volume for read/write operations. All writes to this primary source volume are mirrored (copied to a secondary target volume) in another Symmetrix array, which can be remote. A source volume is not available for local mirroring or dynamic sparing operations.

Split A Business Continuance process that removes the BCV mirror from the existing BCV pair and assigns the BCV mirror back to its original device address. The BCV device then holds an instant copy of the data from the standard device.

Source image of IASP A set of standard/R1 devices in a particular IASP. See also ”ASPs.”

SRDF Symmetrix Remote Data Facility. SRDF consists of the microcode and hardware required to support Symmetrix remote mirroring.

SRDF/Asynchronousmode

A combination of hardware and software that extends the capability of SRDF to support Asynchronous Ordered Writes that ensures a consistent copy of data for remote replication over unlimited distances, for a variety of uses. SRDF/A inherits all the advantages of SRDF/Synchronous (SRDF/S).

SRDF/A DSE SRDF/A Delta Set Extension

SRDF Remote LinkDirector

The Remote Link Director (RLD) is a 2-port, serial-channel director microcode configured as the link between the two Symmetrix arrays in a Symmetrix Remote Data Facility (SRDF) configuration.

Stage The process of writing data from a disk device to cache. See ”Promotion” and “Destage.”

Standard devices Symmetrix devices configured for normal Symmetrix operation under a desired protection method (such as RAID 1, RAID 5, RAID 6, RAID-S, SRDF).

157


Switchable IASP An independent ASP that can switch between two separate IBM i hosts or separate LPARs. See also ”ASPs.”

System ASP An auxiliary storage pool consisting of system programs and system data. See also ”ASPs.”

System image A combination of the system ASP and all user ASPs. SRDF/TimeFinder Manager references a System image as SYSTEM on its screens.

TTarget image of an

IASPA set of BCV/R2 or Snap devices comprising a mirror copy of an IASP. See also ”ASPs.”

Target volume (R2) A Symmetrix logical volume that is participating in SRDF operations. It resides in the remote Symmetrix array. This secondary target volume is paired with a primary source volume in the local Symmetrix array and receives all write data from its mirrored pair. This volume is not accessed by user applications during normal I/O operations. A target volume is not available for local mirroring or dynamic sparing operations.

TimeFinder A business continuance solution that allows customers to use special devices (BCVs, Clones, and VDEVs) that contain copies of Symmetrix devices while the standard devices are on-line for regular Symmetrix operation.

UUDFS See ”User Defined File System (UDFS).”

User Defined FileSystem (UDFS)

The user-defined file system that you create and manage. This file system resides on the auxiliary storage pool (ASP) or independent auxiliary storage pool (IASP) of your choice.

VValidate The action that makes all tracks for a source volume valid on a target volume.

Vary off The process of making an IASP image unavailable for its intended (normal) use. All primary and secondary disk pools in the IASP vary off together.

Vary on The process of making an IASP image available for its intended (normal) use. All primary and secondary disk pools in the IASP vary on together.

Virtual device A host-accessible device containing track-level location information (pointers), which indicate where the copy session data is located in the physical storage. Virtual devices consume minimal physical disk storage, as they store only the address pointers to the data stored on the source device or a pool of SAVE devices. Using virtual devices, TimeFinder/Snap operations provide instant snapshot copies.

Volume A general term referring to a storage device. In the Symmetrix subsystem, a volume corresponds to single disk device.


Documents

Dell EMC Host Connectivity Guide for IBM i · Dell EMC Host Connectivity Guide for IBM i P/N 300-009-584 REV 07 ... technical escalations for this specific platform. EMC IBM i Global