Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 357
  • Last Modified:

Vmware seeing existing LUNs on a SAN via iSCSI

Here is the situation.  I have a client that has a Dell NAS with 2 LUNS created on the NAS.  Physical Disk 'A' can see LUN 1 and Physical Disk 'B' can see LUN 2.  Both Physical servers are connected to the NAS via iSCSI.

They have recently implemented a VMWare server and we are trying to connect the VMWare server to the NAS via iSCSI.  It sees the NAS, but keeps saying "no devices".  I have attached a screenshot of the VMware configuration.

What step am I missing?
Vmware-connection-to-existing-SAN-LUNs.J
0
KPI1
Asked:
KPI1
  • 3
  • 2
4 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Both Physical servers are connected to the NAS via iSCSI.

What are these servers ? ESXi Hosts ?

Have you added the iSCSI Software IQN to the permissions or ACLs of the LUNs, but before you do this....

are all these servers ESXi hosts?

You cannot have Windows and ESXi hosts access the same LUN
0
 
KPI1Author Commented:
The current "physical" servers I refer to are a Standalone Windows 2003 server (Server A) and a Standalone Windows 2008 server (Server B).  These are Dell servers and so is the SAN.

I didn't think Windows servers and ESXi servers could see the same LUN, but my Dell server person said it's possible.  The idea is not to have the Windows server share the LUN with ESXi.  ESXi would only access it if the Windows server failed.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
So you have two servers (2003) and (2008). access the same LUNs ? - if so this will cause file system corruption.

I didn't think Windows servers and ESXi servers could see the same LUN, but my Dell server person said it's possible.

Dell server person is talking rubbish! - Not possible, and will cause corruption, Windows cannot read VMware VMFS, and VMware ESXi cannot read NTFS!

ESXi would only access it if the Windows server failed.

Sorry, not going to work.

You would need to have a Windows VM.
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
andyalderSaggar makers bottom knockerCommented:
>Physical Disk 'A' can see LUN 1 and Physical Disk 'B' can see LUN 2.

Do you mean Physical Windows Server 'A' etc.? IF so them each server sees a different LUN which is fine. It's also possible for a VM to have one of these LUNs presented to it by configuring the SAN so that the VMware server has access to it and configuring VMware to pass the LUN to the OS using RDM. Just make sure the physical windows server and VM do not have access at the same time by only having one of them running.
0
 
KPI1Author Commented:
Yes, I mean Physical server 'A' (Windows 2003 server) can access LUN 1 on the SAN.  It can not see LUN2 on the SAN.  Physical server 'B' (Windows 2008 server) can access LUN2 but can't see LUN 1 on the SAN.

When you say,
 "It's also possible for a VM to have one of these LUNs presented to it by configuring the SAN so that the VMware server has access to it and configuring VMware to pass the LUN to the OS using RDM. Just make sure the physical windows server and VM do not have access at the same time by only having one of them running.".

That's exactly what I am trying to do.  Can you point me to more documentation on configuring VMWare to pass the LUN to the OS using RDM?

Thank you.



Can you point
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you want to do RDM, then see here:-

https://www.vmadmin.co.uk/resources/35-esxserver/58-rdmvm
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now