I’ve just recently run in to a problem trying to access ESXi’s CLI from the console using IMM2 (Integrated Management Module). The KVM seems to be intercepting commands incorrectly. This seems to be the case for a number of KVM tools.
The normal command for accessing the CLI once enabled, is to press ALT+F1. This won’t work. You will need to hold down ALT+Space, release Space and press F1 while keeping ALT held down.
ALT+Space release space ALT+F1
I recently lost a host at one of my sites which have a failover policy set of IP Hash. No problem, connect a new host remotely and add it back to the network. Problem is, I cannot access this host from vCenter because of this policy. After posting on Reddit, someone gave me the following command to enter via CLI
You will need to enable the CLI from the console -> troubleshooting options.
esxcli network vswitch standard portgroup policy failover set -p "Management Network" -l iphash
Once this is set, you should now be able to see your host from vCenter.
This error can occur after the Windows 10 update, either 1511 or 1607.
This issue occurs as part of the upgrade removes the VMWare authorization service. If you click Start->Run and type service.msc you will see the service missing.
Go to Control Panel->Add/Remove Programs and repair your VMWare Workstation installation.
The other option is to update your version. Ensure you have the correct licensing before you do this.
I’ve been working on an issue for the past week with the following hardware/software:
3x Lenovo x3650 M5 Type 5462
6x Fusion-MPT 12GSAS SAS3008 (two each host)
1x IBM v3700 SAN
VMWare 6.0 U2 (Lenovo image)
The HBA’s and SAN were configured in the following manner:
What I didn’t realise early on was that multipathing from the SAN to VMWare was not working. As I was in a rush, I saw the SAS connections were live. The SAN said everything was ok, so I didn’t think twice.
However, on closer inspection on the SAN, I found that only one SAS HBA on each host was active. Hmm, what was going on?
VMWare was also reporting the same issue:
Initially, I thought this was a SAN issue. I contacted support who checked out the SAN and couldn’t find any issue.
I then contacted VMWare who initially said the configuration was not supported (driver wise). Actually, what I found is VMWare were referring to the wrong driver.
After about a week of going back and forward, I noticed the drivers that were shipped with the Lenovo VMWare image were not the latest. I proceed to update the drivers which in turn, enabled multi-pathing in VMWare.
This was quite a simple issue but made a bit more complicated as all the hardware seemed supported and at the right driver level.
The correct driver was the lsi-msgpt3 driver found here. lsi-msgpt3 version lsi-msgpt3 version 13.00.00.00-1OEM. The installed version was lsi-msgpt3 version 12.00.00.00-1OEM.
Sometimes it pays to check the basics.