Newly upgraded ESX 6.7 host can no longer see shared storage
ok, we have two Dell R730 servers with LSI HBA cards. Those two servers are connected to a Dell MD1200 enclosure with 36TB of storage.
Server 1 was running ESX 6.0
Server 2 is running 6.7
I vMotioned the live VMs off of Server 1 over to Server 2 and upgraded Server 1 to 6.7
Both server are now running ESX 6.7
The problem is, Server 2 came up and while it is connected to the MD1200, the existing datastore does not show up in the list of Server 2 datastores. The internal storage is there, and the IBM v3700 is there, but the Dell MD1200 didn't come back.
Now, Server 2 is connected to the MD1200 and all VMs live there. I simple want Server 1 to reconnect and share that datastore, but I'm not sure what is going on.
Can someone point me in the direction of making that MD1200 come back to Server 1 now that it's ESX is up to 6.7??
Thanks
Cliff
PS: Reminder, Server 2 is connected to the Dell MD1200 and all live VMs live there and are on that host. I just need my newly upgraded Server 1 to reconnect and share the storage.
Server 1 was running ESX 6.0
Server 2 is running 6.7
I vMotioned the live VMs off of Server 1 over to Server 2 and upgraded Server 1 to 6.7
Both server are now running ESX 6.7
The problem is, Server 2 came up and while it is connected to the MD1200, the existing datastore does not show up in the list of Server 2 datastores. The internal storage is there, and the IBM v3700 is there, but the Dell MD1200 didn't come back.
Now, Server 2 is connected to the MD1200 and all VMs live there. I simple want Server 1 to reconnect and share that datastore, but I'm not sure what is going on.
Can someone point me in the direction of making that MD1200 come back to Server 1 now that it's ESX is up to 6.7??
Thanks
Cliff
PS: Reminder, Server 2 is connected to the Dell MD1200 and all live VMs live there and are on that host. I just need my newly upgraded Server 1 to reconnect and share the storage.
ASKER
correct. I see the Dell MD1200 attached under storage devices, but the datastore that's on there is not showing in the datastores list like it did when it had 6.0 on there.
Can you access the ESXi server shell prompt to type some commands?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
All that said I am trying to google for this issue with our San and finding nada.
I will reach out to that engineer who encountered it and confirm with him if he can find the bug report but he is out of that country for two weeks so it will be some time.
It's also possible the issue is slightly different than stated as I didn;t work ion this directly, but I definitely recall the discussion we had as he preferred to "Have just one 6.7 host, and it will see the datastores okay so long as we don't upgrade others" which I saw as being a non-starter in my opinion, and recommending to revert all of them instead to keep our environments in lock-step code-wise.
I will reach out to that engineer who encountered it and confirm with him if he can find the bug report but he is out of that country for two weeks so it will be some time.
It's also possible the issue is slightly different than stated as I didn;t work ion this directly, but I definitely recall the discussion we had as he preferred to "Have just one 6.7 host, and it will see the datastores okay so long as we don't upgrade others" which I saw as being a non-starter in my opinion, and recommending to revert all of them instead to keep our environments in lock-step code-wise.
ASKER
This gets stranger and stranger. The on-site tech decided to RE OS the host and now, it "sees" the shared datastore, but it's named Datastore(1) and the original datastore is named Datastore. The data is identical, but obviously, it's still not seeing the datastore correctly.
Can you rename the datastore(1) - datastore.
or, the Host already has datastore mapped.
or, the Host already has datastore mapped.
ASKER
See screen caps. Each host sees the same datastore, it's just they see them independently.
Screen-Shot-2019-04-23-at-4.56.08-PM.png
Screen-Shot-2019-04-23-at-4.55.53-PM.png
Screen-Shot-2019-04-23-at-4.56.08-PM.png
Screen-Shot-2019-04-23-at-4.55.53-PM.png
ASKER
Andrew, check this out:
I logged into each host, and despite the enclosure and the datastore being the same, each hosts "sees" it differently.
Screen-Shot-2019-04-23-at-5.10.11-PM.png
Screen-Shot-2019-04-23-at-5.10.21-PM.png
I logged into each host, and despite the enclosure and the datastore being the same, each hosts "sees" it differently.
Screen-Shot-2019-04-23-at-5.10.11-PM.png
Screen-Shot-2019-04-23-at-5.10.21-PM.png
($0.02) The one in the brackets either can't be seen or there's a comms problem - I had the same with an HP3Par last week!
Look at the drive sizes and VMFS versions they are Zero
</P>
Look at the drive sizes and VMFS versions they are Zero
</P>
ASKER
Still poking this. What I have learned is that the connection for multi path is Round Robin for the datastore that is working as expected and for the one that is showing up as separate storage on each host, the multi path is set to VMware (Fixed). I'm thinking that after peeps leave work, I'll edit that and see. Does anyone think editing multi path will break the host connectivity with the datastore?
it's time to look at the logs. and log in to the shell.
ASKER
Ben, you pegged it. Once we got 6.7 on the host and rebooted, it was fine.
Glad to help! :)
e.g. all luns visible...
and it's just a datastore which is missing ?