To harden your ESXi 6.0 hosts, we disable the MOB service so that any attacker can’t get to the web browser and access the MOB of the ESXi host (ex: https://esxi01.lab.com/mob), this setting will disable one of the attack vectors of theESXi hosts in the environment.
to do this, you SSH into the ESXi host where you want to disable the mob service and perform the following commands
esxi01# vim-cmd proxysvc/remove_service "/mob" "httpsWithRedirect"
to verify if the mob service has been removed from the ESXi host, use the following command
esxi01# vim-cmd proxysvc/service_list
the above command will list all the services on the ESXi host, look for the service “/mob”, if you don’t see this service, then it has been removed. if it is still there, then you will have to perform the first command and reboot the ESXi host to disable the mob service from the host.
Recently, I was working on an UCS blade firmware upgrade along with esxi upgrade from esxi 5.5 to 6.0 and came across this error where the esxi host became unresponsive with an error “can’t fork” on its DCUI.
here is a little background on this story, this particular blade was B240 blade which was being used as SAP HANA blade by the customer and the firmware upgrade and esxi upgrade went fine and two days later the host became unresponsive and we couldn’t connect to it using SSH, DCUI, etc, connecting to the kvm console revealed the below screen when we went to its Alt+F1 command interface
we had to bounce the box and we had to reduce the linux vm memory which was hosting SAP HANA on it to be 10% less than the memory of the esxi host.
Conclusion: The HANA VM (linux) on the esxi host should have 10% less memory than the overall memory of the esxi host to avoid this problem.
Recently, I had to install the Cisco vem module onto an esxi 6 host as it was not installed and i couldn’t join the esxi host to the cisco nexus 1000v distributed switch. here is the process on how to first check if the vem module is installed on the esxi host.
SSH into the esxi host and run the following commands to check if the VEM module is installed
host# esxcli software vib list | grep -i vem
the above command will display the cisco vem module installed on the esxi host, if nothing is displayed then you will have to install the vem module by downloading the vem vib from the nexus 1kv in the environment.
i did it by going to https://nexus1kv_hostname in a web browser which will display you the vibs which you can download from nexus 1000v, download the vem vib associated with your environment and run the following command to install the vib onto the esxi host
upload the vem vib file onto a datastore on the host
SSH into the esxi host where you want to install the vem module
host# esxcli software vib install -v /vmfs/volumes/<directory_path>/cross_cisco-vem-version_x.x.x.x.x.vib
NOTE: directory_path in the above command is the place where the cisco vem vib is stored. (name of the datastore/volume)
Once the vib is installed you can check the status of the vem by using the command
host# vem status
The above command will display that the VEM agent (vemdpa) is running