
Search the Knowledge Base: |
Search the Knowledge Base: |
0x100F
0x1011
0x1010
0x1012
0x101D
You can check the PCI device ID of your network adapters by running the following command in the service console:
lspci -nv | grep "Class 0200"
00:02.0 Class 0200: 8086:100e (rev 02)
00:04.0 Class 0200: 8086:1229 (rev 0d)
00:06.0 Class 0200: 8086:1229 (rev 0c)
02:04.0 Class 0200: 8086:1008 (rev 02)The string that follows 8086: is the device ID.The likelihood of this issue occurring increases greatly if you have overridden the default netPktHeapMaxSize VMkernel boot time parameter. If this value is increased and you are experiencing this problem, the following message appears in your log files:Warning: (errata24) already holdind on to 64bad skb buffers
|
Note: If you are unable to apply this patch, work around this problem by decreasing the size of the network buffer heap (only if you have increased it beyond the default by setting the netPktHeapMaxSize VMkernel boot time parameter with the esxcfg-advcfg command). |
# mkdir /var/updates
Note: VMware recommends that you use the updates directory.
# cd /var/updates
# md5sum ESX-2221.tgz
The md5 checksum output should match the following:
c2e37a178776f9fc1c066e70d19363e4 ESX-2221.tgz
# tar -xvzf ESX-2221.tgz
# cd ESX-2221
If you are in the directory you created above, install the update using the following command:
esxupdate update
If you want to run esxupdate from a different directory, you must specify the bundle path in the command:
esxupdate -r file:<directory>/ESX-2221 update
During the update process, logs appear on the terminal. You can specify the verbosity of esxupdate logs by using the -v option as shown below:
esxupdate -v 10 -r file:<directory>/ESX-2221 update
For more information on using esxupdate, please refer to the Patch Management for ESX Server 3 tech note at http://www.vmware.com/pdf/esx3_esxupdate.pdf.