New week, new lessons learned… You can find part 1 here.
When Jumbo Frames were introduced in ESX 3.5 a lot of people were interested but it wasn’t supported for the VMkernel which is were most people want to use it as it reduces CPU cycles used due to iSCSI/NFS traffic. When vSphere was released it was one of the things I noticed first. Full support for Jumbo Frames… however:
- Jumbo frames are not supported for VMkernel networking interfaces in ESXi. (page 54)
Although obvious in my opinion it wasn’t obvious for one of my customers:
- VMware ESXi does not support web access at this time.
Although I personally usually disable web access as it a security risk this customer had specific operational procedures around vCenter failures which included web access. It’s not a huge problem as the vSphere/vCenter Client can directly connect to an ESXi host, but it is something you will need to keep in mind when implementing ESXi.
Another thing I discovered today is that scripted/unattended installations of ESXi are not currently supported which makes deploying difficult. (Not only unsupported but also not easily set up) I am currently investigating the option to at least install it with default settings and without manual intervention… If I am successful I will post it in the next “lessons learned”.