Summary: This one has been on the back burner for a little while, but I finally got it put together thanks to resources like virtualghetto . lamw is crazy smartz! Script: Everything seems to work fine, the only one I’m not sure of is the enabling the CIMoemProviderEnabled Advanced setting as to whether that works or not. Let me know if you happen to brave my custom kickstart script made for Dell servers, but can be adjusted for pretty much any setup I think. 1: # Bind vmnic4 to vSwitch0. EDA adds vmnic0 automatically 2: # Active/Passive 3: esxcfg-vswitch -L vmnic4 vSwitch0 4: esxcfg-vswitch -X 1 vSwitch0 5: 6: # Add vSwitch1, VMkernel, and bind vmnic1/3 7: # Active/Passive 8: # The following configures vSwitch1 as the vmKernel vmotion switch 9: esxcfg-vswitch -a vSwitch1 10: esxcfg-vswitch -A VMkernel vSwitch1 11: esxcfg-vswitch -L vmnic1 vSwitch1 12: esxcfg-vswitch -L vmnic3 vSwitch1 13: esxcfg-vswitch -X 1 vSwitch
Showing posts from July, 2011
- Other Apps
Summary: Found this out the hard way, but for anyone who might be banging your head against the wall. Check if your ESX host has Emulex LPe12000-E and running firmware 2.00A3. If so upgrade to 2.00A4. Symptoms: ESX host not mapping/detecting LUN regardless of rescan attempts. VM's suddenly going offline because of disk access problems.
- Other Apps
Summary: Found this out when installing the Emulex VIB on an ESXi 4.1 host w/ the Dell OMSA VIB installed. Apparently something w/ the Emulex VIB causes issues w/ the Dell OMSA install causing it to stop talking to the Dell Management Plugin for vCenter. Solution: Install the Emulex VIB THEN the Dell OMSA VIB OR Uninstall Dell OMSA VIB, reboot, then attempt install based on order above. FYI: To uninstall a VIB from ESXi 4.1, you can use vCLI or TSM (Tech Support Mode). esxupdate query <-- This will return the installed VIB's and their bulletin ID which is need for removal. esxupdate --b Bulletin_ID_of_VIB remove <-- This will remove the VIB