<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Don’t have a clear fix yet, but so far Cisco TAC states the cisco.com download C210 Host Update 1.3.1d.1 from 4/27/11 is shipping with older Broadcom NetXtreme II BCM57091000BaseT (the Quad PCIe Gige Card) and to update the ESXi driver for that card. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>ssh to ESXi Service Console for a command line, then TAC did a vmkload –s enic and ethtools –i vnnic4 to determine the driver version in ESXi 4.1.0, then esxupdate to install the new driver, this requires shutting down the virtual machines for maintenance mode.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>VMware ESX/ESXi 4.1 Driver CD for Broadcom NetXtreme II Ethernet<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="http://downloads.vmware.com/d/details/esx41_broadcom_netxtremeii_dt/ZHcqYnRlaHRiZCVodw">http://downloads.vmware.com/d/details/esx41_broadcom_netxtremeii_dt/ZHcqYnRlaHRiZCVodw</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>vmware-esx-drivers-net-bnx2-400.2.0.15g.8.v41.1-1vmw.0.0.00000.x86_64.vib<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Jason Aarons (AM) <br><b>Sent:</b> Thursday, June 09, 2011 9:45 PM<br><b>To:</b> cisco-voip (cisco-voip@puck.nether.net)<br><b>Subject:</b> network adapter not showing “connected” in vSphere after utils system restart<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Seems if you issue a “utils system restart” (this was via ssh) you might have some network problems afterwards with the network adapter not showing “connected” in vSphere, can’t ping virtual machine. Manually hitting connect in vSphere won’t fix it.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I recall <span style='color:#1F497D'>a co-worker running into this with another customer, waiting to hear back from them on how they resolved it, maybe delete/add the network adapter via vSphere?</span> <span style='color:#1F497D'> W</span>orking to figure out what the fix is and where the bug lies. Is this a Platform bug or a ESXi bug? <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>ESXi4.1.0<o:p></o:p></p><p class=MsoNormal>Unity Connection 8.5(1)SU1<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>