VMware Cloud Community
pkavitha
Contributor
Contributor

Unable to see devices to extend the datastore via vcenter but works for host login

I have observed a couple of issues in our vcenter(6.5) web client when trying to extend the storage for an existing datastore.

In the below screen shot, I am trying to extend the datastore from the vcenter and I cannot see the volume.

pastedImage_1.png

I am trying the same from the ESXi host login and I can see the volume listed here.

pastedImage_2.png

Before contacting vmware support, I wanted to know if anyone had this issue before.

8 Replies
RickVerstegen
Expert
Expert

Hi pkavitha ,

Did you already perform a storage rescan operation within vCenter?

Perform Storage Rescan

Rick

Was I helpful? Give a kudo for appreciation!
Blog: https://rickverstegen84.wordpress.com/
Twitter: https://twitter.com/verstegenrick
Reply
0 Kudos
pkavitha
Contributor
Contributor

Yes, I did a multiple times from the vcenter. Individually for each host from the vcenter and also to entire cluster from the vcenter webclient login.

Reply
0 Kudos
diegodco31
Leadership
Leadership

Did you Try with user administrator@vsphere.local on vcenter?

This could be a user permission issue.

Diego Oliveira
LinkedIn: http://www.linkedin.com/in/dcodiego
Reply
0 Kudos
RickVerstegen
Expert
Expert

Can you check and perform the steps in the KB below:

VMware Knowledge Base

Rick

Was I helpful? Give a kudo for appreciation!
Blog: https://rickverstegen84.wordpress.com/
Twitter: https://twitter.com/verstegenrick
Reply
0 Kudos
pkavitha
Contributor
Contributor

diegodco31

I just did and it's still the same from the vcenter.

Reply
0 Kudos
diegodco31
Leadership
Leadership

Check the following VMware KB article:

VMware Knowledge Base

Diego Oliveira
LinkedIn: http://www.linkedin.com/in/dcodiego
pkavitha
Contributor
Contributor

RickVerstegen

Still the same from vcenter.

Looks like this reason applies here. It used to work before.

Reply
0 Kudos
pkavitha
Contributor
Contributor

Found more accurate reason in this scenario.

The storage volume is mounted to different set of hosts with different LUN Ids.(2) Our new vCenter (6.5) has both host sets added to the cluster and that caused the LUN ID ambiguity for the same volume preventing the vcenter from seeing it.