VMAX Cascading

80
VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser) Distributed Storage Management Version: 1.0 (Draft 7) Owner: Gary Wallace Authors: Errick Gibson Blue Color Changes are suggested by Amit Gandage Document: DSM Documentation Date: 6/6/2022 Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management Page 1 of

description

casca

Transcript of VMAX Cascading

Page 1: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Distributed Storage Management

Version: 1.0 (Draft 7)

Owner: Gary Wallace

Authors: Errick Gibson

Blue Color Changes are suggested by Amit Gandage

Green Color Region need to be ignored.

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 1 of 60

Page 2: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Document LocationThe source of the document can be found in the Team Room, located at:

· Database Name: TBD

· Server Name: TBD

· File Name: TBD

Please address any questions to: Revision HistoryDate of this revision 01/11/2011 Date of next revision: TBD

Revision Number

Revision Date

Summary of Changes Changes marked

1/22/2010 Creation of first draft by Errick Gibson Eg

1.1 1/27/2010 Remove the –IG –PG -SG and –MV from the names eg

1.2 6/29/2010 Changed - to _ also added application name to view, and group. This maybe useful if FAST is used in the future.

eg

1.3 8/09/2010 ADDED the _ig ,,-pg , _sg and _mv to the names (Dan Chiem wanted to have this added back.

eg

1.4 8/10/2010 Fix syntax error, syntax error and name format errors . Modiied port group name to allow unique FA configuration for single server and clustered Server setups.

eg

1.5 8/15-16/2010

Correct Typo Errors and inconsistencies. This include Best Practice of connecting HBA to the SAN’s

eg

1.7 9/27/10 Added Auto_Provisoning Naming convention and examples to support VMWARE ESX SERVER LUn sharing across multiple ESX SERVER _Pair/frame. Same VM group is normally used across all Shared ESX SERVER-Pairs. Change VMAX example form 2024 to 7777 per GR team

eg

1.8 1/11/11 Used VM Define cluster names for cluster related MV, IG,SG and PG. Adjusted Names of MV,PG,SG to allow mapping , masking of consistent Lun ids within an ESX cluster configuration where a subset of ESX Servers within a Cluster are connected to one Dual Fabric and another subset is connected to another Dual Fabric

ApprovalsThis document requires following approvals:

Name Title

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 2 of 60

Page 3: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Fred Rosalino

Andre Humphrey

Jaeook Yoon

Dan Chiem

Gary Wallace

Amit Gandage

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 3 of 60

Page 4: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

TABLE OF CONTENT

Executive Summary.............................................................................................................6SAMPLE KAISER VMWARE ESX CLUSTERED SERVER SAN/STORAGE LAYOUT.............................................................................................................................7

FIGURE1:........................................................................................................................7Naming Conventions...........................................................................................................8VMAX Auto-Provisioning Concepts..................................................................................9VMAX Auto-Provisioning Groups and Views Overview...................................................9

Initiator Groups................................................................................................................9Cascade initiator groups..................................................................................................9Port Group(s)...................................................................................................................9Storage Group(s)............................................................................................................10Masking View(s)...........................................................................................................10

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS...........................................................................................................................................11ESX VMAX STORAGE DEPLOYMENT/NAMING GUIDELINES.............................12

Single ESX Server Storage Deployments:....................................................................12Clustered ESX Server Storage Deployments:...............................................................13

Single-VMWARE ESX Server and Clustered ESX Server Initiator Group Naming Standards............................................................................................................................15

Format: Single-VMWARE ESX Server Initiator Group Naming Standards................15Format: VMWARE ESX Clustered-Server Initiator Group Naming Standards (Cascaded).....................................................................................................................16

Example: (Single- ESX Server) Initiator Group Naming Standards........................17Example: (Clustered- ESX Servers) Initiator Group Naming Standards.................20

Port Group Naming Standards...........................................................................................22Format: Single-VMWARE ESX Server Port Group Naming Standards (NOT PART OF CURRENT DESIGN)..............................................................................................22Format A: VMWARE Clustered-Server Port Group Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San...............................24Format B: VMWARE Clustered-Server Port Group Naming Standards where a subset ESX Servers within a Cluster are split across multiple Dual Fabrics............................25

Example: (Single-VMWARE ESX Server Port Group Naming Standards).............26Example: Format A: VMWARE Clustered-Server Port Group Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San......27Example: Format B: VMWARE Clustered-Server Port Group Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San...........................................28

Storage Group Naming Standards.....................................................................................29

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 4 of 60

Page 5: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Single ESX Server Storage Deployments:....................................................................29Format: Single-VMWARE ESX Server Storage Group Naming Standards (NOT PART OF CURRENT DESIGN)..................................................................................29Format A: VMWARE Clustered-Server Storage Group Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San.......................31Format B: VMWARE Clustered-Server Storage Group Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San........................................................32

Example: (Single-VMWARE ESX Server Storage Group Naming Standards).......34Example: Format A: VMWARE Clustered-Server Storage Group Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San......35Example: Format B: VMWARE Clustered-Server Storage Group Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San...........................................36Example for Setting Dynamic lun Address when adding a lun to a Storage Group already associated with a existing MV..........................................................................37

Masking View Naming Standards.....................................................................................38Single ESX Server Storage Deployments:....................................................................38Format: Single-VMWARE ESX Server Masking View Naming Standards (NOT PART OF CURRENT DESIGN)..................................................................................38Format A: VMWARE Clustered-Server Masking View Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San.......................40Format B: VMWARE Clustered-Server Masking View Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San........................................................41

Example: (Single-VMWARE ESX Server Storage GroupNaming Standards)........43Example: Format A: VMWARE Clustered-Server Masking View Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San......44Example: Format B: VMWARE Clustered-Server Masking View Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San...........................................45Example for Setting Dynamic lun Address during Masking View Creation................46

APPENDIX A:..................................................................................................................47TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s).................................................................................47

VMWARE ESX SERVER STORAGE DESIGN POINTS..............................................49RECOMMEDATION/BEST PRACTICES......................................................................52

Single ESX Server Storage Deployments Guidelines:..................................................53Clustered ESX Server Storage Deployments Guidelines:.............................................54

SPECIAL NOTES:............................................................................................................55

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 5 of 60

Page 6: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Executive Summary

With the Symmetrix VMAX, Solutions Enabler 7.x and Enginuity 5874, Auto-Provisioning Groups are now the exclusive mechanism for storage provisioning. A new command, symaccess, provides all the storage provisioning requirements for Symmetrix VMAX arrays running Enginuity 5874.

The purpose of this document is to introduce the concepts behind Auto-Provisioning and to define Standard Naming conventions specific to the VMWARE Storage deployments. This documentation is to be used as a guide when creating the Initiator, Storage and Port Groups and the Masking Views specific to VMWARE Storage deployment within Kaiser.

Note:This document is not intended as a tutorial for performing Auto-Provisioning and the use of the symaccess commands for storage deployment within VMWARE ESX Server environment. It is based on the current Kaiser VMWARE ESX Server Storage Allocation layout.

Formal or informal training is recommended for all storage personnel who are involved in the implementation and ongoing support of the VMAX Auto-provisioning process.

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 6 of 60

Page 7: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

SAMPLE KAISER VMWARE ESX CLUSTERED SERVER SAN/STORAGE LAYOUT

FIGURE1:

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 7 of 60

Page 8: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Naming Conventions

One of the advantages of Auto-provisioning Groups is when well thought out naming conventions are used for all group objects and views. These conventions will help to document the systems and facilitate post-implementation support and troubleshooting.

Our goal is to establish best practices and naming conventions for storage, port and initiator groups, and masking views that will provide for self-documentation and facilitate post-implementation support and troubleshooting.

A name can be up to 64 alphanumeric characters in length and may include the hyphen ("-") and underscore ("_") special characters. While the maximum name length is 64 characters, some SE CLI commands will truncate names longer than 20 characters

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 8 of 60

Page 9: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

VMAX Auto-Provisioning Concepts

Auto-provisioning Groups allow for the creation of groups of host initiators, front-end ports, and logical devices. These groups are then associated to form a masking view, from which all controls are managed.

The fundamental concept of Auto-provisioning Groups is the logical grouping of related objects and the creation of a view that associates the related groups together.

VMAX Auto-Provisioning Groups and Views Overview

Initiator GroupsAn Initiator group is a logical grouping of up to 32 Fibre Channel initiators or 8 iSCSI names or a combination of both. An initiator group may also contain the name of another initiator group to allow the groups to be cascaded to a depth of one. These are known as Cascade initiator groups.

Cascade initiator groupsAn HBA can only belong to a single initiator group. Cascade initiator groups can be configured to allow an initiator group to be a member of another initiator group.

Port Group(s)A port group is a logical grouping of Fibre Channel and/or iSCSI front-end director ports. The only limit on the number of ports in a port group is the number of ports in Symmetrix V-max. It is likely that a port group will contain a subset of the available portsDocument: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 9 of 60

Page 10: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 10 of 60

Page 11: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Storage Group(s)A storage group is a logical grouping of up to 4096 Symmetrix devices. LUN addresses are assigned to the devices in the storage group when the masking view is created using the dynamic LUN addressing feature.

Masking View(s)A masking view defines an association between one initiator group, one port group, and one storage group. When a masking view is created, the devices in the storage group are mapped to the ports in the port group and masked to the initiators in the initiator group. Depending on the server and application requirements, each server or group of servers may have one or more masking views that associate a set of Symmetrix devices to an application, server, or cluster of servers. When a masking view is created, the devices are automatically masked and mapped. After the masking view is created, any objects (devices, ports, initiators) added to a group automatically become part of the masking view.

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 11 of 60

Page 12: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

CLUSTER NAME

ESX SERVER

ESX FRAME #

HYPERVISOR

FABRIC VMAX SID FA-PAIRS ZONED

cdc_prod_lab cscrdesxp001 11111 ESX CDC_PROD_FABRIC 7777 8E0_9E0 8F0_9F0 8G0_9G0 8H0_9H0

cdc_prod_lab cscrdesxp002 22222 ESX CDC_PROD_FABRIC 7777 8E0_9E0 8F0_9F0 8G0_9G0 8H0_9H0

cdc_prod_lab cscrdesxp003 33333 ESX CDC_PROD_FABRIC 7777 8E0_9E0 8F0_9F0 8G0_9G0 8H0_9H0

cdc_prod_lab cscrdesxp004 44444 ESX CDC_PROD_FABRIC 7777 8E0_9E0 8F0_9F0 8G0_9G0 8H0_9H0

cdc_prod_lab cscrdesxp005 55555 ESX CDC_VI_FABRIC 7777 10E0_7E0 10F0_7F0 10G0_7G0 10H0_7H0

CLUSTER NAME

ESX SERVER ESX FRAME #

HYPERVISOR

FABRIC vmhba1 vmhba4

cdc_prod_lab cscrdesxp001 11111 ESX CDC_PROD_FABRIC 10000000C988AF02 10000000C988BD69

cdc_prod_lab cscrdesxp002 22222 ESX CDC_PROD_FABRIC 10000000C988B299 10000000C988BD47

cdc_prod_lab cscrdesxp003 33333 ESX CDC_PROD_FABRIC 10000000C988B15E 10000000C988BD1F

cdc_prod_lab cscrdesxp004 44444 ESX CDC_PROD_FABRIC 10000000C799B14A 10000000C7554931

cdc_prod_lab cscrdesxp005 55555 ESX CDC_VI_FABRIC 100000004B58497A 100000005B364A44

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 12 of 60

Page 13: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

ESX VMAX STORAGE DEPLOYMENT/NAMING GUIDELINES

Single ESX Server Storage Deployments: NOTE: LUNS ALLOCATION TO A SINGLE ESX SERVER IS NOT PART OF THE CURRENT DESIGN BUT IS INCLUDED IN THIS DOCUMENT TO COVER POSSIBLE FUTURE USAGE

A. As a best practice, Single Server IG’s for each Server in a Cluster should always be created and used to build a Cascaded IG for the Cluster.

B. A Single Server IG , PG, SG and MV can be used dedicate a particular lun to a single ESX Server.

C. IG’s are created with the consistent-lun option to enforce a common host lun id for each unique Symm-device masked via the unique masking view.

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 13 of 60

Page 14: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Clustered ESX Server Storage Deployments:

A. In a configuration where all ESX Servers in the Cluster are connected to the same Dual Fabric San

As a best practice, all servers in the Cluster see the same set of Array FA pair’s

By definition , all HBA’s and Array FA’s associated with the Cluster are physically connected to the same Dual Fabric San

As a best practice , each unique LUN shared by the Clustered Servers, will be mapped to one and only one of the FA pairs seen by the Cluster. All in the same Dual Fabric San

As a best practice, LUNs will be mapped uniquely and in round-robin fashion , across the set FA pair’s seen by the Cluster

B. In a configuration where a Subset of ESX Servers within a Cluster are connected to one Dual Fabric San and another subset is connected to a different Dual Fabric San;

!! Not Recommended, but may be required for some existing configurations.

As a best practice, a unique set of FA pair’s will need to be physically connected to each Dual Fabric San. Allowing backend storage assess by each subset of ESX Servers within the Cluster.

By definition , all HBA’s and Array FA’s associated with the subset of Clustered Servers within a particular Dual Fabric San should be physically connected to that Dual Fabric

As a best practice , each unique LUN shared by the Clustered Servers, will be mapped to one and only one of the FA pairs on each of the Dual Fabric San’s

A unique set of MVs, SG’s and PGs will be created to include an the FA pairs attached to each of the DUAL Fabric SANs

As a best practice, LUNs will be mapped uniquely and in round-robin fashion , across the set FA pair’s seen by the Cluster

For availability and performance, devices should be mapped to two or more front-en director ports. These ports should be on different directors and if possible, different engines. With the exception of a single engine systems, the "Rule of 17 " can still followed

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 14 of 60

Page 15: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 15 of 60

Page 16: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Single-VMWARE ESX Server and Clustered ESX Server Initiator Group Naming Standards

Reference to Single and Clustered ESX Server VMAX Allocation Guidelines ESX VMAX STORAGE DEPLOYMENT/NAMING GUIDELINES

Format: Single-VMWARE ESX Server Initiator Group Naming Standards

<ESX SERVER_server>_<frame#>_ig

Where:<ESX SERVER_server>= ESX Server Name ((Provided by VMWare Eng)

<frame#> = Frame # (Provided by VMWare Eng)ig =(indicates that this is an inititator group)

Note: A Single-VMWARE ESX Server Initiator group is created for each ESX SERVER within the ESX CLUSTER. These are used to create a Cascade IG representing the ESX SERVER Server pair.

example: cscrdesxp001_11111_ig

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 16 of 60

Page 17: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Format: VMWARE ESX Clustered-Server Initiator Group Naming Standards (Cascaded)Reference to Single and Clustered ESX Server VMAX Allocation Guidelines ESX VMAX STORAGE DEPLOYMENT/NAMING GUIDELINES

<ESX CLUSTER_Name>_vm_clstr_ig

Where:< ESX CLUSTER_Name >= ESX_Cluster_Name ((Provided by VMWare Eng with a list of all ESX Server in the cluster)vm = (vmware)clstr = (clustered)ig =(indicates that this is an initiator group)

example: cdc_prod_lab_vm_clstr_ig

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 17 of 60

Page 18: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: (Single- ESX Server) Initiator Group Naming StandardsCLUSTER NAME

ESX SERVER ESX FRAME #

HYPERVISOR

FABRIC vmhba1 vmhba4

cdc_prod_lab cscrdesxp001 11111 ESX CDC_PROD_FABRIC 10000000C988AF02 10000000C988BD69

cdc_prod_lab cscrdesxp002 22222 ESX CDC_PROD_FABRIC 10000000C988B299 10000000C988BD47

cdc_prod_lab cscrdesxp003 33333 ESX CDC_PROD_FABRIC 10000000C988B15E 10000000C988BD1F

cdc_prod_lab cscrdesxp004 44444 ESX CDC_PROD_FABRIC 10000000C799B14A 10000000C7554931

cdc_prod_lab cscrdesxp005 55555 ESX CDC_VI_FABRIC 100000004B58497A 100000005B364A44

The user generated name should be set with the “symaccess –rename “ command to associated a wwn with particular server/(hba adapter). Facilitating troubleshooting. All wwns should have this value set.

Single Server Initiator groups will be used as the building block for “VMWARE ESX SERVER CLUSTER “ Initiator Groups

IG’s created with the consistent-lun option to enforce a common host lun id for each unique Symm-device masked via the unique masking view.

1. Create Initiator Groups (One IG per server containing all hbas for that server)Dedicate (per adapter)

Sample SYMCLI commands Single VMWARE ESX Server Initiator Groups:

cscrdesxp001:symaccess -sid 7777 -type initiator –file /home/storman1/data/ cscrdesxp001_11111_wwns.txt -name cscrdesxp001_11111_ig create -consistent_lun

File cscrdesxp001_11111_wwns.txt :WWN:10000000C988AF02 WWN:10000000C988BD69

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 18 of 60

Page 19: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

SET WWN ALIASsymaccess –sid 7777 rename -wwn=10000000C988AF02 –alias s cscrdesxp001/vmhaba1symaccess –sid 7777 rename -wwn=10000000C988BD69 –alias cscrdesxp001/vmhaba4

cscrdesxp002:symaccess -sid 7777 -type initiator –file /home/storman1/data/ cscrdesxp002_22222_wwns.txt -name cscrdesxp002_22222_ig create -consistent_lun

File: cscrdesxp002_22222_wwns.txt :WWN: 10000000C988B299 WWN: 10000000C988BD47

SET WWN ALIASsymaccess –sid 7777 rename -wwn=10000000C988B299 –alias cscrdesxp002/vmhba1symaccess –sid 7777 rename -wwn=10000000C988BD47 –alias cscrdesxp002/vmhba4

cscrdesxp003:symaccess -sid 7777 -type initiator –file /home/storman1/data/ cscrdesxp003_33333_wwns.txt -name cscrdesxp003_33333_ig create -consistent_lun

File: cscrdesxp003_33333_wwns.txt :WWN: 10000000C988B15E WWN: 10000000C988BD1F

SET WWN ALIASsymaccess –sid 7777 rename -wwn=10000000C988B15E –alias cscrdesxp003/vmhba1symaccess –sid 7777 rename -wwn=10000000C988BD1F –alias cscrdesxp003/vmhba4

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 19 of 60

Page 20: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

cscrdesxp004:symaccess -sid 7777 -type initiator –file /home/storman1/data/ cscrdesxp004_44444_wwns.txt -name cscrdesxp004_44444_ig create -consistent_lun

File: cscrdesxp004_44444_wwns.txt :WWN: 10000000C799B14A WWN: 10000000C7554931

SET WWN ALIASsymaccess –sid 7777 rename -wwn=10000000C799B14A –alias cscrdesxp004/vmhba1symaccess –sid 7777 rename -wwn=10000000C7554931 –alias cscrdesxp004/vmhba4

cscrdesxp005:symaccess -sid 7777 -type initiator –file /home/storman1/data/ cscrdesxp005_55555_wwns.txt -name cscrdesxp005_55555_ig create -consistent_lun

File: cscrdesxp005_55555_wwns.txt :WWN: 100000004B58497A WWN: 100000005B364A44

SET WWN ALIASsymaccess –sid 7777 rename -wwn=100000004B58497A –alias cscrdesxp005/vmhba1symaccess –sid 7777 rename -wwn=100000005B364A44 –alias cscrdesxp005/vmhba4

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 20 of 60

Page 21: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: (Clustered- ESX Servers) Initiator Group Naming Standards

Single Server Initiator groups will be used as the building block for “VMWARE ESX SERVER CLUSTER “ Initiator Groups

IG’s created with the consistent-lun option to enforce a common host lun id for each unique Symm-device masked via the unique masking view.

All luns shared across the ESX cluster must have the same host lun id

CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

ESX VMAX STORAGE DEPLOYMENT/NAMING GUIDELINES

2. Create VMWARE ESX Clustered ESX Server’s Initiator Group

ESX CLUSTERED ESX SERVER IG => cdc_prod_lab_vm_clstr_ig

ig => cscrdesxp001_11111_ig (all wwns for cscrdesxp001) ig => cscrdesxp002_22222_ig (all wwns for cscrdesxp002) ig => cscrdesxp003_33333_ig (all wwns for cscrdesxp003) ig => cscrdesxp004_44444_ig (all wwns for cscrdesxp005) ig => cscrdesxp005_55555_ig (all wwns for cscrdesxp005)

Sample SYMCLI commands for a VMWARE ESX CLUSTER Initiator Group:

symaccess -sid 7777 create -name cdc_prod_lab_vm_clstr_ig -type initiator -file cdc_prod_lab_vm_clstr_igs.txt -consistent_lun

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 21 of 60

Page 22: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

CASCADE GROUP IG TEXT FILE:

IGFILE= cdc_prod_lab_vm_clstr_igs.txtIG: cscrdesxp001_11111_igIG: cscrdesxp002_22222_igIG: cscrdesxp003_33333_igIG: cscrdesxp004_44444_igIG: cscrdesxp005_55555_ig

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 22 of 60

Page 23: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Port Group Naming Standards

Reference to Single and Clustered ESX Server VMAX Allocation Guidelines ESX VMAX STORAGE DEPLOYMENT/NAMING GUIDELINES

CONFIGURATION REFERENCE:VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

Format: Single-VMWARE ESX Server Port Group Naming Standards (NOT PART OF CURRENT DESIGN)

NOTE: LUNS ALLOCATION TO A SINGLE ESX SERVER IS NOT PART OF THE DESIGN BUT IS INCLUDED IN THIS DOCUMENT TO COVER POSSIBLE FUTURE USAGE

A. As a best practice, Single Server IG’s for each Server in a Cluster should always be created and used to build a Cascaded IG for the Cluster.

B. A Single Server IG , PG, SG and MV can be used dedicate a particular lun to a single ESX Server.

C. In a configuration where all ESX Servers in the Cluster are connected to the same Dual Fabric San the Cluster_Server IG could be used but for complete autonomy a unique PG for single ESX Server storage allocation is the preferred best practice,

<ESX SERVER>_ <sid>_[FA#[proc][port]_ {FA#[proc][port})]_pg

Where:<ESX SERVER>= ESX Server Name ((Provided by VMWare Eng) <sid> = last 4 digits of vmax sid

(repeat for all FA’s / ports within the unique FA-pair)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 23 of 60

Page 24: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

FA# = Vmax FA # (7,8,9,10 etc) (ALL Processor and Ports in the Particular FA Pair should be included)

[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1) pg = (indicates this is a port group)

example: cscrdesxp001_7777_8E0_9E0_pg

(ESX Server: cscrdesxp001 , SID =7777, ESX SERVER FA PAIR :{8E:0,9E:0)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 24 of 60

Page 25: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Format A: VMWARE Clustered-Server Port Group Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San

< ESX CLUSTER_Name >_<sid>_[FA#[proc][port]_ {FA#[proc][port})]_Fabric Name_clstr_pg

Where:< ESX CLUSTER_Name >= _ ESX_Cluster_Name ((Provided by VMWare Eng)

<sid> = last 4 digits of vmax sid

(repeat for all FA’s / ports within the unique FA-pair)

FA# = Vmax FA # (7,8,9,10 etc) (ALL Processor and Ports in the Particular FA Pair should be included)

[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1) Fabric Name = Provided by Vmware Eng

clstr = (clustered)pg = (indicates that this is a port group)

example:cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_pg

or

cdc_prod_lab_7777_8E0_9E0_vi_vm_clstr_pg

(All ESX servers are connected to the same Dual Fabric and the FA pair 8E0/9E0 will be used to map and mask luns)

REFERENCESClustered ESX Server Storage Deployments:

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 25 of 60

Page 26: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 26 of 60

Page 27: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Format B: VMWARE Clustered-Server Port Group Naming Standards where a subset ESX Servers within a Cluster are split across multiple Dual Fabrics

< ESX Cluster_Name >_<sid>_[Dual_Fabric_1_FA_Pair FA#[proc][port]_{ FA#[proc][port})]_>_[Dual_Fabric_2_FA_Pair FA#[proc][port]_{ FA#[proc][port})]_vm_clstr_pg

Where:< ESX Cluster_Name > => ESX_Cluster_Name ((Provided by VMWare Eng)<sid> = last 4 digits of vmax sid

[Dual_Fabric_1_FA_Pair FA#[proc][port]_{ FA#[proc][port})] => selected FA Pairs mapped to the first Dual Fabric San

[Dual_Fabric_2_FA_Pair FA#[proc][port]_{ FA#[proc][port})] => selected FA Pairs mapped to the second Dual Fabric San

(repeat for all FA’s / ports within each unique FA-pair)

{INDIVIDUAL FA PORT LAYOUT WITH 2 FA’s PER PAIR (rule of 17 if possible) } FA# = Vmax FA # (7,8,9,10 etc)[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1)

vm = (vmware)clstr = (clustered)pg =(indicates that this is port group)

example:a Subset of ESX Servers within a Cluster are connected to one Dual Fabric San and another subset is connected to a different Dual Fabric San. FA pair’s 8E0/9E0 in cdc_prod_fabric. FA pairs 10E0/7E0 in cdc_vm_fabric

sample pg name: cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_pg

REFERENCESClustered ESX Server Storage Deployments:

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 27 of 60

Page 28: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 28 of 60

Page 29: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: (Single-VMWARE ESX Server Port Group Naming Standards)

NOTE: LUNS ALLOCATION TO A SINGLE ESX SERVER IS NOT PART OF THE DESIGN BUT IS INCLUDED IN THIS DOCUMENT TO COVER POSSIBLE FUTURE USAGE

1. Create VMWARE ESX SERVER Server Port Group used to map luns to a single server. (Vmax Front-End Ports)

Sample SYMCLI commands:

PG=> cscrdesxp001_7777_8E0_9E0_pg ESX SERVER: cscrdesxp001 sid => 7777: adapters: 8e:0; 9e:0

symaccess -sid 7777 -type port -name cscrdesxp001_7777_8E0_9E0_pg –dirport 8E:0,9E:0 create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 29 of 60

Page 30: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: Format A: VMWARE Clustered-Server Port Group Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San

1. Create VMWARE ESX CLUSTERED SERVER Port Group (Vmax Front-End Ports. All ESX Servers in the cluster are connected to cdc_prod_fabric

Allows a unique set of luns to me mapped to a unique FA pairs across all ESX Servers in the cluster

CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

PG=> cdc_prod_lab_7777_8E0_9E0_vm_clstr_pg sid => 7777: adapters: 8e:0; 9e:0 (cdc_prod_fabric)

Sample SYMCLI commands:

symaccess -sid 7777 -type port -name cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_pg –dirport 8E:0,9E:0 create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 30 of 60

Page 31: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: Format B: VMWARE Clustered-Server Port Group Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San

1. Create VMWARE ESX CLUSTERED SERVER Port Group (Vmax Front-End Ports. A subset of ESX Servers are connected to cdc_prod_fabric. Another subset is connected to cdc_vm_fabric

As a best practice , each unique LUN shared by the Clustered Servers,

will be mapped to one and only one of the FA pairs on each of the Dual Fabric San’s

.

CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

PG=> cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_pg sid => 7777: adapters: 8e:0; 9e:0 (cdc_prod_fabric_ sid => 7777: adapters: 10e:0; 7e:0 (cdc_vi_fabric)

Sample SYMCLI commands:

symaccess -sid 7777 -type port -name cdc_prod_lab_7777_8E0_9E0_ 10E0_7E0_prod_vm_clstr_pg –dirport 8E:0,9E:0 create

symaccess -sid 7777 -type port -name cdc_prod_lab_7777_10E0_7E0_vi_vm_clstr_pg –dirport 10E:0,7E:0 create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 31 of 60

Page 32: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Storage Group Naming Standards

Single ESX Server Storage Deployments:

Reference to Single and Clustered ESX Server VMAX Allocation Guidelines ESX VMAX STORAGE DEPLOYMENT/NAMING GUIDELINES

CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

Format: Single-VMWARE ESX Server Storage Group Naming Standards (NOT PART OF CURRENT DESIGN)

NOTE: LUNS ALLOCATION TO A SINGLE ESX SERVER IS NOT PART OF THE DESIGN BUT IS INCLUDED IN THIS DOCUMENT TO COVER POSSIBLE FUTURE USAGE

D. As a best practice, Single Server IG’s for each Server in a Cluster should always be created and used to build a Cascaded IG for the Cluster.

E. A Single Server IG , PG, SG and MV can be used dedicate a particular lun to a single ESX Server.

F. In a configuration where all ESX Servers in the Cluster are connected to the same Dual Fabric San the Cluster_Server IG could be used but for complete autonomy a unique PG for single ESX Server storage allocation is the preferred best practice,

<ESX SERVER>_ <sid>_[FA#[proc][port]_ {FA#[proc][port})]_sg

Where:<ESX SERVER>= ESX Server Name ((Provided by VMWare Eng) <sid> = last 4 digits of vmax sid

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 32 of 60

Page 33: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

(repeat for all FA’s / ports within the unique FA-pair)

FA# = Vmax FA # (7,8,9,10 etc) (ALL Processor and Ports in the Particular FA Pair should be included)

[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1) sg = (indicates this is a storage group)

example: cscrdesxp001_7777_8E0_9E0_sg

(ESX Server: cscrdesxp001 , SID =7777, ESX SERVER FA PAIR :{8E:0,9E:0)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 33 of 60

Page 34: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Format A: VMWARE Clustered-Server Storage Group Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San

< ESX CLUSTER_Name >_<sid>_[FA#[proc][port]_ {FA#[proc][port})]_clstr_sg

Where:< ESX CLUSTER_Name >= _ ESX_Cluster_Name ((Provided by VMWare Eng)

<sid> = last 4 digits of vmax sid

(repeat for all FA’s / ports within the unique FA-pair)

FA# = Vmax FA # (7,8,9,10 etc) (ALL Processor and Ports in the Particular FA Pair should be included)

[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1) Fabric Name = Provided by Vmware Eng

clstr = (clustered)sg = (indicates that this is a storage group)

example:cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_sg

or

cdc_prod_lab_7777_8E0_9E0_vi_vm_clstr_sg

(All ESX servers are connected to the same Dual Fabric and the FA pair 8E0/9E0 will be used to map and mask luns)

REFERENCESClustered ESX Server Storage Deployments:

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 34 of 60

Page 35: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Format B: VMWARE Clustered-Server Storage Group Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San

< ESX Cluster_Name >_<sid>_[Dual_Fabric_1_FA_Pair FA#[proc][port]_{ FA#[proc][port})]_>_[Dual_Fabric_2_FA_Pair FA#[proc][port]_{ FA#[proc][port})]_vm_clstr_sg

Where:< ESX Cluster_Name > => ESX_Cluster_Name ((Provided by VMWare Eng)<sid> = last 4 digits of vmax sid

[Dual_Fabric_1_FA_Pair FA#[proc][port]_{ FA#[proc][port})] => selected FA Pairs mapped to the first Dual Fabric San

[Dual_Fabric_2_FA_Pair FA#[proc][port]_{ FA#[proc][port})] => selected FA Pairs mapped to the second Dual Fabric San

(repeat for all FA’s / ports within each unique FA-pair)

{INDIVIDUAL FA PORT LAYOUT WITH 2 FA’s PER PAIR (rule of 17 if possible) } FA# = Vmax FA # (7,8,9,10 etc)[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1)

vm = (vmware)clstr = (clustered)sg =(indicates that this is storage group)

example:a Subset of ESX Servers within a Cluster are connected to one Dual Fabric San and another subset is connected to a different Dual Fabric San. FA pair’s 8E0/9E0 in cdc_prod_fabric. FA pairs 10E0/7E0 in cdc_vm_fabric

sample name: cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_sg

REFERENCES

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 35 of 60

Page 36: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Clustered ESX Server Storage Deployments:

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 36 of 60

Page 37: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: (Single-VMWARE ESX Server Storage Group Naming Standards)

NOTE: LUNS ALLOCATION TO A SINGLE ESX SERVER IS NOT PART OF THE DESIGN BUT IS INCLUDED IN THIS DOCUMENT TO COVER POSSIBLE FUTURE USAGE

1. Create VMWARE ESX SERVER Server Storage Group used to map luns to a single server. (Vmax Front-End Ports)

Sample SYMCLI commands:

SG=> cscrdesxp001_7777_8E0_9E0_sg ESX SERVER: cscrdesxp001 sid => 7777: FA PAIR: 8e:0; 9e:0 (VMAX7777: Dev: 100)

Sample SYMCLI commands:

symaccess -sid 7777 -type storage -name cscrdesxp001_7777_8E0_9E0_sg –devs 100 create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 37 of 60

Page 38: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: Format A: VMWARE Clustered-Server Storage Group Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San

1. Create VMWARE ESX CLUSTERED SERVER Storage Group(Vmax Front-End Ports. All ESX Servers in the cluster are connected to cdc_prod_fabric

As a best practice, LUNs will be mapped uniquely and in round-

robin fashion , across the set FA pair’s seen by the Cluster

CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

SG=> cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_sg sid => 7777: FA PAIR: 8e:0; 9e:0 (cdc_prod_fabric) sid => 7777: dev: 201

Sample SYMCLI commands:symaccess -sid 7777 -type storage -name cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_sg –devs 201 create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 38 of 60

Page 39: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: Format B: VMWARE Clustered-Server Storage Group Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San

1. Create VMWARE ESX CLUSTERED SERVER Storage Group(Vmax Front-End Ports. A subset of ESX Servers are connected to cdc_prod_fabric. Another subset is connected to cdc_vm_fabric

As a best practice , each unique LUN shared by the Clustered Servers,

will be mapped to one and only one of the FA pairs on each of the Dual Fabric San’s

.

CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

SG=> cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_sg sid => 7777: adapters: 8e:0; 9e:0 (cdc_prod_fabric) sid => 7777: adapters: 10e:0; 7e:0 (cdc_vm_fabric) sid => 7777: dev: 201 (mapped across a single Fa pair in each Dual

Fabric)Note :- We are putting the same SYMM device (201) into multiple SG group.

Sample SYMCLI commands:symaccess -sid 7777 -type storage -name cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_sg –devs 201 create

&

symaccess -sid 7777 -type storage -name cdc_prod_lab_7777_10E0_7E0_vi_vm_clstr_sg –devs 201 create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 39 of 60

Page 40: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example for Setting Dynamic lun Address when adding a lun to a Storage Group already associated with a existing MV

· When IG’s are created with the consistent_lun option Vmax will enforce consistent host luns id across the hosts define in the IG associate with the Masking view.

· Lun Id can also be set specifically by using the –lun argument on the masking view create or adding lun to storage group already associated with a mv

SG=> cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_sg sid => 7777: adapters: 8e:0; 9e:0 (cdc_prod_fabric) sid => 7777: adapters: 10e:0; 7e:0 (cdc_vm_fabric) sid => 7777: dev: 201 (mapped across a single Fa pair in each Dual

Fabric) IG: cdc_prod_lab_vm_clstr_ig (Cascated IG for servers in the cluster) PG: cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_pg (FA PAIR

{8e:0,9e:0 in cdc_prod_fabric/10e:0,7e:0 in cdc_vm_fabric } SG: cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_sg (Luns

mapped to FA PAIR {8e:0,9e:0 in cdc_prod_fabric/10e:0,7e:0 in cdc_vm_fabric }

Sample SYMCLI commands:symaccess -sid 7777 -type storage -name cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_sg –devs 201 add –lun 001

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 40 of 60

Page 41: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Masking View Naming Standards

Single ESX Server Storage Deployments:

Reference to Single and Clustered ESX Server VMAX Allocation Guidelines ESX VMAX STORAGE DEPLOYMENT/NAMING GUIDELINES

CONFIGURATION REFERENCE:VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

Format: Single-VMWARE ESX Server Masking View Naming Standards (NOT PART OF CURRENT DESIGN)

NOTE: LUNS ALLOCATION TO A SINGLE ESX SERVER IS NOT PART OF THE DESIGN BUT IS INCLUDED IN THIS DOCUMENT TO COVER POSSIBLE FUTURE USAGE

A. As a best practice, Single Server IG’s for each Server in a Cluster should always be created and used to build a Cascaded IG for the Cluster.

B. A Single Server IG , PG, SG and MV can be used dedicate a particular lun to a single ESX Server.

C. In a configuration where all ESX Servers in the Cluster are connected to the same Dual Fabric San the Cluster_Server IG could be used but for complete autonomy a unique PG for single ESX Server storage allocation is the preferred best practice,

<ESX SERVER>_ <sid>_[FA#[proc][port]_ {FA#[proc][port})]_mv

Where:<ESX SERVER>= ESX Server Name ((Provided by VMWare Eng) <sid> = last 4 digits of vmax sid

(repeat for all FA’s / ports within the unique FA-pair)Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 41 of 60

Page 42: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

FA# = Vmax FA # (7,8,9,10 etc) (ALL Processor and Ports in the Particular FA Pair should be included)

[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1) sg = (indicates this is a storage group)

example: cscrdesxp001_7777_8E0_9E0_mv

(ESX Server: cscrdesxp001 , SID =7777, ESX SERVER FA PAIR :{8E:0,9E:0)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 42 of 60

Page 43: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Format A: VMWARE Clustered-Server Masking View Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San

< ESX CLUSTER_Name >_<sid>_[FA#[proc][port]_ {FA#[proc][port})]_clstr_mv

Where:< ESX CLUSTER_Name >= _ ESX_Cluster_Name ((Provided by VMWare Eng)

<sid> = last 4 digits of vmax sid

(repeat for all FA’s / ports within the unique FA-pair)

FA# = Vmax FA # (7,8,9,10 etc) (ALL Processor and Ports in the Particular FA Pair should be included)

[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1) Fabric Name = Provided by Vmware ENG. clstr = (clustered)mv = (indicates that this is a masking view)

example:cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_mv

or

cdc_prod_lab_7777_8E0_9E0_vi_vm_clstr_mv

(All ESX servers are connected to the same Dual Fabric and the FA pair 8E0/9E0 will be used to map and mask luns)

REFERENCESClustered ESX Server Storage Deployments:

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 43 of 60

Page 44: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 44 of 60

Page 45: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Format B: VMWARE Clustered-Server Masking View Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San

< ESX Cluster_Name >_<sid>_[Dual_Fabric_1_FA_Pair FA#[proc][port]_{ FA#[proc][port})]_>_[Dual_Fabric_2_FA_Pair FA#[proc][port]_{ FA#[proc][port})]_vm_clstr_mv

Where:< ESX Cluster_Name > => ESX_Cluster_Name ((Provided by VMWare Eng)<sid> = last 4 digits of vmax sid

[Dual_Fabric_1_FA_Pair FA#[proc][port]_{ FA#[proc][port})] => selected FA Pairs mapped to the first Dual Fabric San

[Dual_Fabric_2_FA_Pair FA#[proc][port]_{ FA#[proc][port})] => selected FA Pairs mapped to the second Dual Fabric San

(repeat for all FA’s / ports within each unique FA-pair)

{INDIVIDUAL FA PORT LAYOUT WITH 2 FA’s PER PAIR (rule of 17 if possible) } FA# = Vmax FA # (7,8,9,10 etc)[proc]= Processor # (E, F, G,H)[port] = Port # (0 = port 0, 1 = port 1)

vm = (vmware)clstr = (clustered)mv =(indicates that this is masking view)

example:a Subset of ESX Servers within a Cluster are connected to one Dual Fabric San and another subset is connected to a different Dual Fabric San. FA pair’s 8E0/9E0 in cdc_prod_fabric. FA pairs 10E0/7E0 in cdc_vm_fabric

sample name: cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_mv

REFERENCES

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 45 of 60

Page 46: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Clustered ESX Server Storage Deployments:

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 46 of 60

Page 47: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: (Single-VMWARE ESX Server Storage GroupNaming Standards)

NOTE: LUNS ALLOCATION TO A SINGLE ESX SERVER IS NOT PART OF THE DESIGN BUT IS INCLUDED IN THIS DOCUMENT TO COVER POSSIBLE FUTURE USAGE

1. Create VMWARE ESX SERVER Server Masking View used to map luns to a single server. (Vmax Front-End Ports)

MV=> cscrdesxp001_7777_8E0_9E0_mv ESX SERVER: cscrdesxp001 sid => 7777: FA PAIR: 8e:0; 9e:0 (VMAX7777: Dev: 100) IG: cscrdesxp001_11111_ig (wwn for all ESX Server HBA’s_ PG: cscrdesxp001_7777_8E0_9E0_pg (FA PAIR {8e:0,9e:0

/cdc_prod_fabric} SG: cscrdesxp001_7777_8E0_9E0_sg {Luns mapped to ESX Server FA

PAIR {8e:0,9e:0} VMAX7777: Dev: 100

Sample SYMCLI commands:

symaccess -sid 7777 view -name cscrdesxp001_7777_8E0_9E0_mv –ig cscrdesxp001_11111_ig –pg cscrdesxp001_7777_8E0_9E0_pg–sg cscrdesxp001_7777_8E0_9E0_sg create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 47 of 60

Page 48: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: Format A: VMWARE Clustered-Server Masking View Naming Standards where All ESX Servers in the Cluster are connected to the same Dual Fabric San

1. Create VMWARE ESX CLUSTERED SERVER Masking View (Vmax Front-End Ports. All ESX Servers in the cluster are connected to cdc_prod_fabric

As a best practice, LUNs will be mapped uniquely and in round-

robin fashion , across the set FA pair’s seen by the Cluster

CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

MV=> cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_mv ESX SERVER Cluster: cscrdesxp001, cscrdesxp002, cscrdesxp003,

cscrdesxp004, cscrdesxp005 sid => 7777: FA PAIR: 8e:0; 9e:0 (cdc_prod_fabric) sid => 7777: dev: 201 (mapped to one FA pair seen by cluster) IG: cdc_prod_lab_vm_clstr_ig (Cascated IG for servers in the cluster) PG: cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_pg (FA PAIR

{8e:0,9e:0 all in cdc_prod_fabric} SG: cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_sg (Luns mapped to

FA PAIR {8e:0,9e:0} VMAX7777: Dev: 201 across all ESX Servers in the Cluster

ALL ESX SERVER ARE IN THE SAME DUAL FABRIC SAN

Sample SYMCLI commands:symaccess -sid 7777 view -name cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_mv –ig cdc_prod_lab_vm_clstr_ig –pg cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_pg–sg cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_sg create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 48 of 60

Page 49: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Example: Format B: VMWARE Clustered-Server Masking View Naming Standards where a subset ESX Servers in the Cluster are connected one Dual Fabric San and another subset is connected to a different Dual Fabric San

1. Create VMWARE ESX CLUSTERED SERVER Masking View (Vmax Front-End Ports. A subset of ESX Servers are connected to cdc_prod_fabric. Another subset is connected to cdc_vm_fabric

As a best practice , each unique LUN shared by the Clustered Servers, will be mapped to one and only one of the FA pairs on each of the Dual Fabric San’s

.CONFIGURATION REFERENCE:

VMWARE ESX SERVER/CLUSTER STORAGE DEPLOYMENT LAYOUT

SAMPLE VMWARE ESX SERVER/CLUSTER CONFIGURATION COMPONENTS

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

MV=> cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_mv ESX SERVER Cluster: cscrdesxp001, cscrdesxp002, cscrdesxp003,

cscrdesxp004, cscrdesxp005 sid => 7777: adapters: 8e:0; 9e:0 (cdc_prod_fabric) sid => 7777: adapters: 10e:0; 7e:0 (cdc_vm_fabric) sid => 7777: dev: 201 (mapped across a single Fa pair in each Dual

Fabric) IG: cdc_prod_lab_vm_clstr_ig (Cascated IG for servers in the cluster) PG: cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_pg (FA PAIR

{8e:0,9e:0 in cdc_prod_fabric } PG: cdc_prod_lab_7777_10E0_7E0_vi_vm_clstr_pg (FA PAIR

{10e:0,7e:0 in cdc_vm_fabric } SG: cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_sg (Luns mapped to

FA PAIR {8e:0,9e:0 in cdc_prod_fabric } SG: cdc_prod_lab_7777_10E0_7E0_vi_vm_clstr_sg (Luns mapped to FA

PAIR {10e:0,7e:0 in cdc_vm_fabric }

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 49 of 60

Page 50: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

· Allows for consistent lun id’s across both FA pair’s on each Dual Fabric SAN seen by the ESX Cluster

· Lun Id can also be set specifically by using the –lun argument on the masking view create or adding lun to storage group already associated with a mv.

Sample SYMCLI commands: (lun id create by VMAX) symaccess -sid 7777 view -name cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_mv –ig cdc_prod_lab_vm_clstr_ig –pg cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_pg–sg cdc_prod_lab_7777_8E0_9E0_prod_vm_clstr_sg create

symaccess -sid 7777 view -name cdc_prod_lab_7777_10E0_7E0_vi-_vm_clstr_mv –ig cdc_prod_lab_vm_clstr_ig –pg cdc_prod_lab_7777_10E0_7E0_vi_vm_clstr_pg–sg cdc_prod_lab_7777_10E0_7E0_vi_vm_clstr_sg create

Example for Setting Dynamic lun Address during Masking View Creation

· When IG’s are created with the consistent_lun option Vmax will enforce consistent host luns id across the hosts define in the IG associate with the Masking view.

· Lun Id can also be set specifically by using the –lun argument on the masking view create or adding lun to storage group already associated with a mv

Sample SYMCLI commands: (lun id assigned as part of the command)

symaccess -sid 7777 view -name cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_mv –ig cdc_prod_lab_vm_clstr_ig –pg cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_pg–sg cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_sg –lun 001 create

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 50 of 60

Page 51: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

APPENDIX A:

Note :- We will concentrate on changing the below mentioned Paramenter once we finalize on the naming convention standards.

TABLE OF SAMPLE ESX CLUSTERED SERVER VMAX AUTO-PROVISIONING OBJECTS (MVs, SGs, PGs. IG;s)

ESX configuration where a subset of ESX Servers within a Cluster are connected to one Dual Fabric and another subset is connected to another Dual Fabric

SAMPLE CLUSTER OBJECTSCDC_PROD_FABRIC/ CDC_VM_FABRICCLUSTER: CDC_PROD_LABVMAX OBJECTS FOR LUNS MAPPED TO FA PAIR 8E0_9E0 & 10E0_7E0

LUNS MAPPED ACROSS FA PAIRS FOR EACH DUAL FABRIC

COMMENTS

cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_mvcdc_prod_lab_vm_clstr_ig IGs: cscrdesxp001_11111_ig,

cscrdesxp002_22222_ig cscrdesxp003_33333_ig, cscrdesxp004_44444_ig , cscrdesxp005_55555_ig

Single server Igs are used to build Clustered /Cascaded IG's . Consistent_LUN is set for all IG's

cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_pg

8E:0 :9E:0 ,10E:0 :7E:0

cdc_prod_lab_7777_8E0_9E0_10E0_7E0_vm_clstr_sg

sample: sym dev# 201 / host lun= 001

VMAX OBJECTS FOR LUNS MAPPED FA PAIR 8F0_9F0 & 10F0_7F0

LUNS MAPPED ACROSS FA PAIRS FOR EACH DUAL FABRIC

COMMENTS

cdc_prod_lab_7777_8F0_9F0_10F0_7F0_vm_clstr_mvcdc_prod_lab_vm_clstr_ig IGs: cscrdesxp001_11111_ig,

cscrdesxp002_22222_ig cscrdesxp003_33333_ig, cscrdesxp004_44444_ig , cscrdesxp005_55555_ig

Single server Igs are used to build Clustered /Cascaded IG's . Consistent_LUN is set for all IG's

cdc_prod_lab_7777_8F0_9F0_10F0_7F0_vm_clstr_pg

8F:0 :9F:0 ,10F:0 :7F:0

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 51 of 60

Page 52: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

cdc_prod_lab_7777_8F0_9F0_10F0_7F0_vm_clstr_sg

sample: sym dev# 202 / host lun= 002

VMAX OBJECTS FORLUNS MAPPED FA PAIR 8G0_9G0 & 10G0_7G0

LUNS MAPPED ACROSS FA PAIRS FOR EACH DUAL FABRIC

COMMENTS

cdc_prod_lab_7777_8G0_9G0_10G0_7G0_vm_clstr_mvcdc_prod_lab_vm_clstr_ig IGS: cscrdesxp001_11111_ig,

cscrdesxp002_22222_ig cscrdesxp003_33333_ig, cscrdesxp004_44444_ig , cscrdesxp005_55555_ig

Single server Igs are used to build Clustered /Cascaded IG's . Consistent_LUN is set for all IG's

cdc_prod_lab_7777_8G0_9G0_10G0_7G0_vm_clstr_pg

8G:0 :9G:0 ,10G:0 :7G:0

cdc_prod_lab_7777_8G0_9G0_10G0_7G0_vm_clstr_sg

sample: sym dev# 203 / host lun= 003

VMAX OBJECTS FORLUNS MAPPED FA PAIR 8H0_9H0 & 10H0_7H0

LUNS MAPPED ACROSS FA PAIRS FOR EACH DUAL FABRIC

COMMENTS

cdc_prod_lab_7777_8H0_9H0_10H0_7H0_vm_clstr_mvcdc_prod_lab_vm_clstr_ig IGS: cscrdesxp001_11111_ig,

cscrdesxp002_22222_ig cscrdesxp003_33333_ig, cscrdesxp004_44444_ig , cscrdesxp005_55555_ig

Single server Igs are used to build Clustered /Cascaded IG's . Consistent_LUN is set for all IG's

cdc_prod_lab_7777_8H0_9H0_10H0_7H0_vm_clstr_pg

8H:0 :9H:0 ,10H:0 :7H:0

cdc_prod_lab_7777_8H0_9H0_10H0_7H0_vm_clstr_sg

sample: sym dev# 204 / host lun= 004

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 52 of 60

Page 53: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

VMWARE ESX SERVER STORAGE DESIGN POINTS

VM SUPPORT FEATURES KAISER USAGE(TO DATE) VM SMEvMotion YES Stephen

SaenzStorage vMotion YES Stephen

SaenzVMware HA YES Stephen

SaenzDRS YES Stephen

SaenzVCB VCB is no longer supported by VMware

and has been replaced with VDP (VMware Data Protection). VDP is not currently used, but is tentatively planned for design & implementation in 2011.

Stephen Saenz

Fault Tolerance Not planned. Stephen Saenz

Thin provisioned Currently not used, but planned for 2011. Stephen Saenz

VMware NMP YES Stephen Saenz

TF Clones/Snaps We have Symclones defined in NDC only, but cloning is not taking place. KP VI Tower owners still desire this functionality.

Stephen Saenz

NPIV Support Not planned, but may be a future requirement.

Stephen Saenz

RDM Requirements Not planned, but may be a future requirement.

Stephen Saenz

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 53 of 60

Page 54: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

VM ESX SERVER/CLUSTER DESIGN STANDARDS GUIDELINES (VMAX CENTRIC)

VM SME

DESIGN ITEMS# of ESX Servers Per Clusters Min = 2 Stephen Saenz

Max = 64 Stephen Saenz# of VMAX FA's pairs mapped to each ESX Cluster

4 - 8 FA Pairs per cluster ?? Stephen Saenz

# of FA pairs over which each Datastore/luns will be shared per ESX Cluster

1 out the 8 FA Pairs Stephen Saenz

# of HBAs per ESX Server 2 HBA ports Per ESX HOST (note : 2 port HBA with on one port used per HBA)

Stephen Saenz

Note: Newest servers (x3850X5) have 2x single-port HBAs.

Stephen Saenz

HBA Speed All servers, except newest, have LPe11002, which are 4Gbps.

Stephen Saenz

Newest servers (x3850X5) have LPe12000, which are 8Gbps.

Stephen Saenz

# of HBA to FA pairs per ESX Server

Each HBA see all FA's designated for that ESX Server/Cluster

Stephen Saenz

Will the relative HBA to FA mapping be the same across all ESX Servers in the ESX Cluster?

yes Stephen Saenz

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 54 of 60

Page 55: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

VM ESX SERVER/CLUSTER DESIGN STANDARDS GUIDELINES (VMAX CENTRIC)

VM SME

DESIGN ITEMSWill Luns/datastores be shared across multiple ESX Clusters

Normally, no. But, there may be occasions where we will need to temporarily present a common set of LUNs to multiple clusters.

Stephen Saenz

The LUN-ID assigned to a specific backend Symm Dev must be the same across all ESX Servers in the Cluster. Regardless of what FA's it maybe mapped to on the Array.

Note: When mapping luns to ESX Clustered Servers particular attention should be paid to ensure that this criteria is always enforced

Use the -consistent_lun option if the devices of a storage group (in a view) need tobe seen on the same LUN on all ports of the port group). If the -consistent_lun optionis set on the initiator group, Solutions Enabler will make sure that the LUN numberassigned to devices is the same for the ports. If this is not set, then the first availableLUN on each individual port will be chosen.

When devices are added at the storage group creation time, do not specify a LUN address. The LUN address is determined when the masking view is created LUN addresses should only be supplied if the storage group is already contained within a view. In this case, a single LUN can be given, or one for each device range. If the LUN address is not specified, the Symmetrix array will assign the LUN address

Stephen Saenz

Will there be luns that will be mapped to a specific ESX Server and not shared at the cluster level?

No Stephen Saenz

Standard Meta-size for Backend LUN

44 way meta x 11 GB for FC drives 10 way metas for SATA Drives

Stephen Saenz

Raid Protection Type raid 5(FC drives) / Raid 6 (Sata drives) Stephen SaenzESX Server Naming convention Defined by VI support and provided for all

new ServerStephen Saenz

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 55 of 60

Page 56: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

ESX Cluster_Naming convention

Defined by VI support and provided for all new ESX Server/Cluster)

Stephen Saenz

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 56 of 60

Page 57: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

RECOMMEDATION/BEST PRACTICES

NOTE Single Server Initiator groups will be used as the building block for

“VMWARE ESX SERVER CLUSTER “ Initiator Groups Each unique Sym Devices(meta-luns/LUNs) , presented to Clustered

ESX Servers should be configured with the same LUN-ID on all FA’s to which it is mapped.

No 2 unique Symm Devices( (Meta-lun/LUNs) presented to either a single ESX Server or Clustered Set of servers should have the same LUN_ID

A particular Storage Group Port Group and Masking View association allows a lun to be masked at the FA pair level for a Single ESX Server or Clustered set of ESX Servers

1. All IG’s are created with the consistent_lun option Vmax will enforce consistent host luns id across the hosts define in the IG associate with the Masking view.

2. Lun Id can also be set specifically by using the –lun argument on the masking view create or adding lun to storage group already associated with a mv

3. All new ESX Servers and array FA pairs within a Cluster should be connected to the same Dual Fabric San

4. In a configuration where a Subset of ESX Servers within a Cluster are connected to one Dual Fabric San and another subset is connected to a different Dual Fabric San

a. This document has been expanded to account for this configuraton b. Consider migrating these server to a single Dual Fabricc. As a best practice , each unique LUN shared by the Clustered

Servers, will be mapped to one and only one of the FA pairs on each of the Dual Fabric San’s

5. Fabric zoning is independent of the mapping and masking that are performed using Auto-porvisioning Groups. The best practice of only mapping and masking devices to initiators and ports that are zoned no longer applies with Auto-provisioning Groups

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 57 of 60

Page 58: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

6. Multi-pathing GK devices is an accepted practice and GK can be part of the same masking view as a production data device. It is a best practice not to share gatekeepers devices between servers

7. For availability and performance, devices should be mapped to two or more front-en director ports. These ports should be on different directors and if possible, different engines. With the exception of single engine systems, the "Rule of 17” can still followed.

8. The user generated name should be set with the symaccess –rename command to associated wwns with particular server/(hba adapter). Facilitating troubleshooting. All wwns should have this value set.

9. Vmax Even FA Ports should be mapped to SAN A switches. 10. Vmax Odd FA Ports should be mapped to SAN B switches.11. Even Server HBA Adapters should be mapped to SAN A switches(ex:fcs0,fcs2)12. Odd Server HBA Adapters should be mapped to SAN B switches(ex:fscs1,fcs3)

.

Single ESX Server Storage Deployments Guidelines: NOTE: LUNS ALLOCATION TO A SINGLE ESX SERVER IS NOT PART OF THE CURRENT DESIGN BUT IS INCLUDED IN THIS DOCUMENT TO COVER POSSIBLE FUTURE USAGE

A. As a best practice, Single Server IG’s for each Server in a Cluster should always be created and used to build a Cascaded IG for the Cluster.

B. A Single Server IG , PG, SG and MV can be used dedicate a particular lun to a single ESX Server.

C. IG’s are created with the consistent-lun option to enforce a common host lun id for each unique Symm-device masked via the unique masking view.

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 58 of 60

Page 59: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

Clustered ESX Server Storage Deployments Guidelines:

C. In a configuration where all ESX Servers in the Cluster are connected to the same Dual Fabric San

As a best practice, all servers in the Cluster see the same set of Array FA pair’s

By definition , all HBA’s and Array FA’s associated with the Cluster are physically connected to the same Dual Fabric San

As a best practice , each unique LUN shared by the Clustered Servers, will be mapped to one and only one of the FA pairs seen by the Cluster. All in the same Dual Fabric San

As a best practice, LUNs will be mapped uniquely and in round-robin fashion , across the set FA pair’s seen by the Cluster

D. In a configuration where a Subset of ESX Servers within a Cluster are connected to one Dual Fabric San and another subset is connected to a different Dual Fabric San;

!! Not Recommended, but may be required for some existing configurations.

As a best practice, a unique set of FA pair’s will need to be physically connected to each Dual Fabric San. Allowing backend storage assess by each subset of ESX Servers within the Cluster.

By definition , all HBA’s and Array FA’s associated with the subset of Clustered Servers within a particular Dual Fabric San should be physically connected to that Dual Fabric

As a best practice , each unique LUN shared by the Clustered Servers, will be mapped to one and only one of the FA pairs on each of the Dual Fabric San’s

A unique set of MVs, SG’s and PGs will be created to include an the FA pairs attached to each of the DUAL Fabric SANs

As a best practice, LUNs will be mapped uniquely and in round-robin fashion , across the set FA pair’s seen by the Cluster

For availability and performance, devices should be mapped to two or more front-en director ports. These ports should be on different directors and if possible, different engines. With the exception of a single engine systems, the "Rule of 17 " can still followed

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 59 of 60

Page 60: VMAX Cascading

VMAX Auto-Provisioning Concepts/Naming Standards/Best Practices for VMWARE Storage Deployments (Acct:Kaiser)

SPECIAL NOTES:

Auto-provisioning Groups are not supported on Symmetrix DMX arrays running Enginuity 5773 and earlier. Storage administrators should continue to use the

symmask and symmaskdb commands to mask devices in Symmetrix DMX arrays A new command, symaccess, provides all the storage provisioning requirements

for Symmetrix VMAX arrays running Enginuity 5874. Ports must have the ACLX flag enabled to be added to a port group With symaccess, the following device masking functions are no longer supported:

There is no device masking database. There is no initialization, backup, or restore.

With the symaccess command, all groups and views are backed up to a file, and can be restored from a backup file.

Volume visibility and the LUN offset on an initiator are no longer supported.

Heterogeneous host types are no longer supported. The HBA flags option is supported.

Document: DSM Documentation Date: 4/8/2023Title: VMAX Auto-Provisioning Concepts/Naming Conventions for the Kaiser Acct Version: 1.0 Owner: Distributed Storage Management

Page 60 of 60