~ # esxcli software vib update -d /vmfs/volumes/vm_storage/ESX6/update-from-esxi I even got an error found in the release notes and used VMware’s workaround: ~ # esxcli system maintenanceMode set -enable true This time, I read the manual and did the update the way that was supposedly correct. I used “install” instead of “update” and when I rebooted, so that probably nuked the server, right? esxcli and vim-cmd commands failed esxcliĬonnect to localhost failed: Connection failure.Īfter spending a few hours poking around to try to fix the issue, I decided it was probably user error.The web client couldn’t connect – error was “503 Service Unavailable (Failed to connect to endpoint: _serverNamespace = / _isRedirect = false _port = 8309)”.What could possibly go wrong on my first actual ESXi upgrade on servers that have been migrated from different IP addresses, some of which may still be lingering on the system and are unreachable?įirst attempt at upgrading a server, all sorts of things were broken. So, I figured, since the lab’s been down for so long anyway, why not upgrade the ESXi servers from 5.1 to 6.0 update 2 while we’re at it? We have 6 ESXi servers that we just moved into a new lab location and are finally ready to be powered back up after a 4-5 month hiatus. ![]() ![]() I work with a few other TMEs in managing a few clustered Data ONTAP clusters, as well as an ESXi server farm. Here at NetApp, we have a variety of labs available to us to tinker with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |