Presenting new Stretched Cluster LUN in VPLEX to a server

//Presenting new Stretched Cluster LUN in VPLEX to a server

VPLEX adds a virtual storage layer between the SAN storage and the Server, normally SAN zoning will be between the SAN and the server. In VPLEX case the zoning is between the VPLEX and the Array from the back-end and the VPLEX and the Server from the front-end.

In details the SAN zoning steps are as following:

Before installing VPLEX the SAN zoning steps are:

  • Zone the SAN directly to the server
  • Create and present the LUNS to the server

After installing VPLEX the SAN zoning steps are:

  • Zone the SAN to VPLEX appliance back-end ports
  • Create and present the LUNs to VPLEX
  • Zone the server to the VPLEX appliance front-end ports
  • From VPLEX, take the LUNs and present them to the server

Stretched cluster is a deployment model where two servers are part of the same logical cluster but are located in two separate geographical area, VPLEX supports two kind of stretched cluster deployment VPLEX metro (synchronous) and VPLEX geo (asynchronous)

VPLEX makes stretched cluster deployment much easier, as it take care of the stretched Cluster LUNs deployment.

In this exercise we will demonstrate how to configure Stretched cluster LUN and present it to the servers, we are assuming the following:

  • Zoning is already done
  • Creating and presenting the LUNS from the SAN to VPLEX is already done.

In summary the steps that will be taken to present a LUN to a server after installing the VPLEX is the following:

  1. Discover the Array
  2. Claim all storage on Supporting Array
  3. Rename the storage volume LUN (Optional)
  4. Create an extent
  5. Create a Device
  6. Create Virtual Volumes
  7. Create Consistency Group
  8. Create Storage Views
  1. Discovery Array

Select the cluster that you present LUNs to and navigate to Physical Storage ==> Storage Array

Press on “Rediscover Array”

VPLEX_LUN01

VPLEX_LUN02

  1. Claim all storage on Supporting Array

Select the cluster that you present LUNs to and navigate to Physical Storage ==> Storage Volumes

VPLEX_LUN03

When inside the Storage Volumes window you will have the device WWN presented not the LUN ID, you can confirm that by going to symmetrix and show the LUN information:

Example: symdev -sid Array# show 36c8

VPLEX_LUN04
VPLEX_LUN05

Select any of the new WWNs and press on “Claim all Storage on Supporting Array”

VPLEX_LUN06

VPLEX_LUN07

VPLEX_LUN08

Select the LUNs that you want to claim

VPLEX_LUN09

VPLEX_LUN10

If you want to re-name the LUNs you can do that now, as now the VPLEX will name the WWN to LUN number

VPLEX_LUN11

  1. Rename the storage volume LUN (Optional)

VPLEX_LUN12

  1. Create an extent

Select the cluster that you present LUNs to and navigate to Virtualized Storage ==> Extents

Press “Create” then select the LUN or LUNs that you want to prepare as an Extent

VPLEX_LUN13

VPLEX_LUN14

VPLEX_LUN15

  1. Create a Device

Select the cluster that you present LUNs to and navigate to Virtualized Storage ==> Devices

Press “Create” then select the Extent that you want to prepare as a Device

  • Select “1 to 1 mapping” if you want to create a “Stretched Cluster”

VPLEX_LUN16
VPLEX_LUN17
VPLEX_LUN18
VPLEX_LUN19
VPLEX_LUN20
VPLEX_LUN21

  1. Create Virtual Volumes (Local Copy only)

Select the cluster that you present LUNs to and navigate to Virtualized Storage ==> Virtual Volumes

Press “Create” then select the Device that you want to add to the Virtual Volume

VPLEX_LUN22

VPLEX_LUN23

Please note: I will explain how to create distributed groups later.

 

  1. Create Consistency Group

Select the cluster that you present LUNs to and navigate to Virtualized Storage ==> Consistency Group

Press “Create”, Type a name for the consistency group, please remember if you created a Distributed Device, you will be able to select “Distributed: All cluster” if you only created a local device, you can only select “Local: Cluster X”

VPLEX_LUN24

If you are adding a local group and you are planning to add the mirror devices later, you should make sure you enable “Global Visibility”

VPLEX_LUN25

Select the fail over policy

VPLEX_LUN26
VPLEX_LUN27
VPLEX_LUN28
VPLEX_LUN29
VPLEX_LUN30
VPLEX_LUN31

 

  1. Create Storage Views

Select the cluster that you present LUNs to and navigate to Hosts ==> Storage View

Press “Create”, Type a name of the storage view, most storage admins use the name of the server to differentiate between storage views.

 

Select the Host Initiators to add to the storage view

VPLEX_LUN32
VPLEX_LUN33

Select the ports to add to the storage view

VPLEX_LUN34

Select the virtual volumes to add to the storage view

VPLEX_LUN35
VPLEX_LUN36
VPLEX_LUN37
VPLEX_LUN38

2017-05-19T00:20:16+00:00 December 3rd, 2014|VPLEX|0 Comments

Leave A Comment

About me

I have more than 15 years hands-on experience in the IT field. The majority of my work is in networking, operating systems and applications and storage. I carry industry certifications in Redhat, Microsoft, EMC, VMWare, VCE and ITIL.

I find it hard to find procedures or documents on how to implement specific technology and this is how the decision to create a place to share my knowledge and ideas for anyone interested in the same subject.

If you have the same vision and you are interested to publish on this website please contact me and I will create an account for you.

Certifications:
RHCSA

Certifications:
MCSE Security
MCSA Massaging

Certifications:
EMCIE- Isilon
EMCTA- Isilon
EMCIE- VNX

Certifications:
VCP-DCV

Certifications:
VCE-CIA

Certifications:
TITL

This site is targeting Solution Architects, Implementation Engineers and Systems Administrators. It is not targeting sales or intending to promote any specific technology or vendor.

The focus is on hands-on work, technical documentations and architecting solutions.

The site reflects my knowledge and opinions, I do recommend that you test what you learn in the lab environment before implementing it in production.

If you have a doubt call technical support, I do not assume any liability for any errors or omissions in those articles, I also make no representations as to the accuracy or completeness of any information on this site or found by following any link on this site

Content published here is tested in my own lab and is not reviewed or approved by any vendor.

If you have any issues with your system I highly recommend you contact the technical support of the vendor.

Disclaimer

Knowledge Ascent (KA) makes information available on its web site to enhance public knowledge and promote a better understanding of the IT environment. KA attempts to provide accurate, complete, and timely information. KA, however, cannot guarantee the quality, content, accuracy, or completeness of the information, text, graphics, links, and other items contained on its web pages because the material comes from a variety of sources, collected and maintained for different purposes. KA also retains the right to change any content on its web site without prior notice.

Information provided on the KA web site should not be used as a substitute for IT or other professional advice. KA assumes no liability for any damages or loss of any kind that might arise from the use of, misuse of, or the inability to use the KA web site and/or the materials contained on the web site. KA also assumes no liability for improper or incorrect use of materials or information contained on its web site. All materials that appear on the KA web site are distributed and transmitted "as is," without warranties of any kind, either express or implied, and subject to the terms and conditions stated in this disclaimer.

Contact Me
FAQ