This error may occur if the service console lacks memory space.
To check if there is a lack of memory in the service console on ESX 4.x:
- Run this command to see if your service console memory is already swapping:
top
- Run this command to see the internal memory consumption of the VEM:
vemcmd show mempool
If there is a lack of memory in the service console:
- Increase the RAM assigned to the ESX service console. For more information, see Increasing the amount of RAM assigned to the ESX Server service console (1003501).
- Right-click on the host and click Enter Maintenance Mode, then reboot the host.
- Run this command to see if the VEM appears in the VSM:
vem restart
show module
- If the VEM does not appear in the VSM and if you cannot start the /etc/init.d/vem-v1xx-vssnet-load and /etc/init.d/vem-v1xx-vssnet-dpa services, you must perform these steps:
- Run this command to get a list of installed RPMs:
rpm -qa | grep vem
- Run this command to uninstall the VEM packages:
rpm -e package_name
- Reboot the ESX host.
- Run this command to reinstall the VEM:
esxupdate --bundle cisco-vem-v1version_number.zip update
- Run this command a few minutes after the VEM services start:
vem status
To remove and re-add a VIB/VEM on ESXi/ESX:
In ESXi/ESX 4.x:
- Run this command to list the installed VIBs:
esxupdate query
Note: This command returns a Bulletin_ID.
- Run this command to remove the VIB:
esxupdate remove -b Bulletin_ID
- Reboot the ESXi/ESX host.
- Run this command to reinstall the VIB:
esxupdate -b /tmp/VIB_FILE update
In ESXi 5.x:
- Run this command to list the installed VIBs:
esxcli software vib list
- Run this command to remove the VIB:
esxcli software vib remove package_name
In ESXi 5.1, you must use the -n switch to remove the VIB. For example:
esxcli software vib remove -n package_name
- Reboot the ESXi host.
- Run this command to reinstall and copy the offline bundles to /tmp:
esxcli software vib install -v /tmp/VIB_FILE