How can I create an iSCSI LUN that doesn't automatically create a named datastore in vCenter?


I have a VNXe 3150 connected to vCenter / ESXi hosts (all 5.5) over iSCSI. Max LUN size is 2 TB on the SAN. I have two 2 TB datastores on SAN / vCenter and have 2 TB free on the SAN. Max LUN size on this device is 2 TB. I want to add an extent to one of the datastores using the 2 TB I have free.

The issue is when I create a LUN on the SAN with the free 2 TB, after rescanning the iSCSI adapter on vCenter, the LUN is presented but also shows up as a named datastore. This prevents me from using it as an extent (it doesn't show up as available storage when increasing the datastore).

How can I present the storage from the SAN so it shows up under Storage in vCenter but doesn't get automatically added as a datastore under Datastores in vCenter? I see other iSCSI LUNs under Storage that are not automatically creating datastores.

Thanks for the help.
king daddyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

king daddyAuthor Commented:
For example, in the snip I attached, when I go to increase Datastore01, I see three LUNs. Those are presented to VMware over iSCSI from an EMC SAN but they did not get an automatically created datastore. The storage I provisioned on the SAN, Datastore01_Extent, does not show up as a LUN I can use to increase Datastore01 and that storage was used to automatically create a LUN (named Datastore01_Extent) which you can see in the image just below Datastore01 in the Datastore view.

Anyway, I am just not sure why the Datastore was automatically created for the one I need to not be automatically created as other wise that is cool.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is this something weird with your EMC plugin

If we create LUNs on our SANs they do not become datastore unless we add them as datastore to ESXi

What if you connect direct to ESXi not vCenter
king daddyAuthor Commented:
Yeah weird. This is the only EMC I have seen this on and it doesn't happen to each LUN presented. We got a call from a new client so started working on this earlier this week. Lots of issues and limited available times that they allow us to work on the system. I am hoping to get on it this weekend and see what is going on.

I will try to connect to one of the hosts and try it again.

Thanks and have a good one.
king daddyAuthor Commented:
same thing happens when connecting to any of the hosts. Ended up reconfiguring the SAN and added it to an existing LUN.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
king daddyAuthor Commented:
Ended up reconfiguring SAN as I was unable to add this 2.5 TB LUN. Not sure what caused it. Oh well.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.