Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
Operating System - VMware
Showing results for 
Search instead for 
Did you mean: 

2 EVA Arrays -- Imperative to have diferent LUN Numbers?

Go to solution
Honored Contributor

2 EVA Arrays -- Imperative to have diferent LUN Numbers?

Our Vmware Admin is saying LUN #s from differnt EVAs should be different. That if I already have a VDISK from EVA1 presented as LUN 1 - that I should NOT have a VDISK from EVA2 as still LUN1.

Is this true?
Hakuna Matata.
Uwe Zessin
Honored Contributor

Re: 2 EVA Arrays -- Imperative to have diferent LUN Numbers?

Technically, it is not necessary. Those LUNs are visible on different bus/targets addresses and they have different LUN WWNs, so they can be identified clearly.

But: if you even want to use Continuous Access on those virtual disks, I agree that it is a good idea to use unique LUN addresses (not sure if they had that in mind, though ;-)
Steven Clementi
Honored Contributor

Re: 2 EVA Arrays -- Imperative to have diferent LUN Numbers?

One of the things that I have started doing is setting a range of lun numbers to use per site. It is not necessary to have different lun numbers as mentioned, but for a quicker indentification of a lun... it might be worth doing.


Site 1 EVA uses 1 through 100
Site 2 EVA uses 101 through 200

If I am doing CA with a vdisk, I make sure that I match the LUN numbers... site 1: LUN 22 (assuning this is the replicated vdisk), in Site 2 I'll use LUN 122 for the replicated copy of that vdisk.

This works well in a 2 site 2 EVA environment, but if you hame multiple arrays per site... you may end up having to use the same LUN numbers anyway.

I also have environments that use the same LUN numbers from multipe EVA's... so it is not "imperative" to use different numbers.

Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
NPP3 (Nutanix Platform Professional)