To work around this issue, you must increase the dvsLargeHeap size.
- Change the host's advanced configuration option:
- Run this esxcli command:
esxcli system settings advanced set -o /Net/DVSLargeHeapMaxSize -i 100
You can verify the value is changed with this command:
esxcli system settings advanced list -o /Net/DVSLargeHeapMaxSize
- On the vCenter Server, browse to Host configuration > Software Panel > Advanced Settings and under Net, change the DVSLargeHeapMaxSize value from 80 to 100.
- On the vSphere 5.1 Web Client browse to Manage host > Settings > Advanced System Settings > Filter, and change the DVSLargeHeapMaxSize value from 80 to 100.
- Save a host profile from the host.
- Associate the profile with the host and update the answer file.
- Reboot the host to confirm that the value is applied.
Note: The maximum value for DVSLargeHeapMaxSize is 128.
Contact VMware Support if you face problems for a large deployment after changing DVSLargeHeapMaxSize to 128 and if logs display either of the the following error messages:
- Unable to Add Port; Status(bad0006)= Limit exceeded
- Failed to get DVS state from vmkernel Status (bad0014)= Out of memory
Note: Advanced configuration parameters management is covered in Configuring advanced options for ESXi/ESX (1038578). Instructions for using the Web Client, the vSphere client, PowerCLI, and the esxcli family of commands are given.