Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 231085

Recurring problems after upgrading to vSphere 5.5

$
0
0

I have 2 HP Servers and each had vSphere 5.0

 

To upgrade them I did the following:

1. I installed vCenter Server on a physical machine.

2. Moved all the VMs from first ESX to secoond  ESX

3. Installed vSphere 5.5 on first server

4. Moved all the VMs to first ESX

5. Installed vSphere 5.5 on the second server

6. Put back VMs on second ESX

 

For 2 days all was working well!

 

Then suddenly all the VMs became inaccessible on server 2. vCenter showed a message that there is a problem accessing one of the LUNs and the message next to the VMs that are located on that LUN said inaccessible, but I can't reach any of the VMs on that host.
It does not want to open the console even to those VMs that are supposedly not affected. The only way to solve this is a reboot. After the reboot, the problematic LUN is not listed in the storage view of my host configuration and it takes many tries to

add it back.

 

And then the next day the same thing happened to server 1.

 

After reboot and after I added the missing storage I thought that all is well - end of story.

 

It happened again and again... one day server 1, next day server 2 and so forth (3 times so far)

 

I don't have any vMotion or other advanced configuration applied.

 

I don't even know where to start troubleshooting this issue (Log files, where are they? never used the command prompt on vSphere)... today I can't even add the missing Disk/LUN. I go through all the steps as before, I select the storage the system finds but it does not add it!

 

Any ideas?

 

Deki


Viewing all articles
Browse latest Browse all 231085

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>