Highlighted
vssankar1
1 Nickel

Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

Hi ,

Is there any requirement on the LUNS where the data stores are on ( Both source and destination) should not be owned by the same SP ,

for storage vMotion to work properly with VAAI enabled ( DataMover.HardwareAcceleratedMove = 1) ?

For example, I have attached some of the test results we have noticed this evening during some tests …

Appreciate any input …..

Thank you    Sankar

Labels (1)
Tags (1)
0 Kudos
13 Replies
8 Krypton

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

what flare version ?

0 Kudos
8 Krypton

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

See emc287223

As a best practice, it is highly recommended to use LUNs of the same owning Storage Processor for such VMware operations (VAAI)

0 Kudos
8 Krypton

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

wow, how impractical ...i want to distribute my workload between SPs not jumble them together on one SP or everytime i need to do svmotion check lun ownership.

0 Kudos
8 Krypton

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

I notice in your test results that you don't have a test case where the LUNs are owned by the same SP and DataMover.HardwareAcceleratedMove=0

How long does it take in that particular instance?

0 Kudos
vssankar1
1 Nickel

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

VNX 7500

Block Software Version : 05.31.000.5.509

File software version: 7.0.40-1 

VNX 5700

Block Software Version : 05.31.000.5.509

File software version: 7.0.40-1  

VMware ESXi 5.0.0 build-469512 

EMC powermt for PowerPath (c) client Version 5.7 (build 173)

EMC PowerPath (c) Version 5.7 (build 173)

0 Kudos
itzikr
6 Indium

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

0 Kudos
8 Krypton

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

The difference is incredibly huge. I have checked White Paper "VAAI for array integration with VNX for SAN" and haven't found requirement to put replication LUNs on different SP, etc. I suspect it's a code bug issue. VAAI fix mentioned by itzikr is recommended to install to see if it can be fixed.

0 Kudos
8 Krypton

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

Please refer to emc305253.

Not the first time that VNX engineering (and/or other storage engineering), PowerPath engineering not talking to each other, or even talking to each withing a very large scale of engineering team. Some times they the talk to VMware NMP team ...

It's time for PPVE engineering & support team to follow up and update emc272442 emc287223...

===

Here is the NEW on for VMware NMP:

"Unexplained trespass with ESX using NMP and Unified OE Block ALUA"

ID:          emc305253

Usage:          2

Date Created:          10/03/2012

Last Modified:          11/06/2012

STATUS:          Approved

Audience:          Customer

Knowledgebase Solution

Question:          Why are unexplained trespasses occurring on an ESX host using VmWare Native Multipathing Plugin (NMP) and Unified OE Block with ALUA?

Environment:          Product: VNX Unified

Environment:          EMC SW: VNX Operating Environment (OE) for Block 05.31

Environment:          OS: VMware ESX 4.1 and later

Environment:          OS: VMware ESXi 4.1 and later

Environment:          Application SW: VMware vStorage API for Array Integration (VAAI)

Environment: This statement does not apply: OS: VMware ESX  5.1

Problem:          Many unknown path trespasses occurred without any path failures reported.

Change:          VMware operation (cloning, deploying VM from template, etc.) from one LUN to another LUN owned by a different storage processor (SP).

Root Cause:          The VAAI feature enables the ESX host to offload specific virtual machine (VM) and storage management operations to the array. In cases where the operation involves two LUNs owned by different SPs, redirection of I/O occurs. When the number of redirections reaches a certain threshold, the redirector will perform an internal trespass to optimize the I/O load. In the event where there are both high application I/Os and VAAI Xcopy I/Os, it is possible that the LUNs will trespass back and forth.

During implicit trespass such as these, Native Multipathing Plugin (NMP) will receive a unit attention informing it of what happened. At this point the host will issue an explicit trespass, moving the LUN to the other SP. When the operation is completed, if the failover policy is set to Round Robin, the LUN will not be auto-restored. If failover policy is set to Fixed, the LUN should auto-restore to the correct SP.

Fix: This issue with the implicit/explicit code returned by the array has been fixed in VNX OE 05.31.000.5.726. It does not fix the trespass issue, that is still by design and attention should be taken to return trespassed LUNs to their Default owner once the operating is complete. In ESX 5.1, auto-restore will be added for Round Robin, so if the policy is set to either Fixed or Round Robin, LUNs should be restored back to the Default owner.

0 Kudos
8 Krypton

Re: Question on VAAI - VNX - STORAGE vMotion - SP LUN OWNERSHIP

PS: What if we're running Inyo code... 05.32

0 Kudos