• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 33
  • Last Modified:

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

Greetings,

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.
0
king daddy
Asked:
king daddy
  • 4
2 Solutions
 
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.

Thanks
datastores-increase.JPG
0
 
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
0
 
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.
0
 
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.

Thanks
0
 
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

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