[cisco-voip] network adapter not showing "connected" in vSphere after utils system restart

Mike King me at mpking.com
Fri Jun 10 10:09:47 EDT 2011


Have the VMware Tools been upgraded on the CUCM?

On Thu, Jun 9, 2011 at 9:45 PM, Jason Aarons (AM) <
jason.aarons at dimensiondata.com> wrote:

>
>
> 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.
>
>
>
> I recall 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?  Working  to figure out what the fix is and where the
> bug lies. Is this a Platform bug or a ESXi bug?
>
>
>
> ESXi4.1.0
>
> Unity Connection 8.5(1)SU1
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110610/ee09f38c/attachment.html>


More information about the cisco-voip mailing list