<br><br><div class="gmail_quote">On Mon, Jan 30, 2012 at 10:52 AM, Mitchell Gore <span dir="ltr"><<a href="mailto:mitchell.gore@gmail.com">mitchell.gore@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><div class="gmail_quote"><div>Interesting. I just checked my BE (that's running on ESXi 4.1u2) and it has a few dropped packets as well (406) since last being rebooted a couple weeks ago. I'm using an E1000 NIC in ESXi for this box. Maybe I should switch it over...</div>
</div>
<br></div>_______________________________________________<br>
<br></blockquote><div><br>I dont think that the issue was nessearly the NIC install but that VMware tools was messed up. I think I remember reading everytime you upgrade the kernal VMware tools needs to be re-installed. Last time I did an upgrade VMware tools still reproted as OK in the VIC so I never did anything. <br>
<br>As a rule of thumb any time you do a kernal upgrade no matter how small of version jump just re run the installer!</div></div></blockquote><div><br></div><div>Isn't that only if you run the installer from the ESXi Host? I have the vmware tools installed from their repo. </div>
</div>