Comments on: ESX Host Currently Has No Management Network Redundancy Error http://www.planetmy.com/blog/esx-host-currently-has-no-management-network-redundancy-error/ Fri, 03 Feb 2012 06:25:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Matt http://www.planetmy.com/blog/esx-host-currently-has-no-management-network-redundancy-error/comment-page-1/#comment-17623 Matt Mon, 31 Mar 2008 21:26:46 +0000 http://www.planetmy.com/blog/esx-host-currently-has-no-management-network-redundancy-error/#comment-17623 I noticed the same thing... I had to reconfigure VMWare HA in order to get the message to disappear. I noticed the same thing… I had to reconfigure VMWare HA in order to get the message to disappear.

]]> By: Recent Virtualization Links - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers http://www.planetmy.com/blog/esx-host-currently-has-no-management-network-redundancy-error/comment-page-1/#comment-17093 Recent Virtualization Links - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers Mon, 21 Jan 2008 19:57:14 +0000 http://www.planetmy.com/blog/esx-host-currently-has-no-management-network-redundancy-error/#comment-17093 [...] ESX Host Currently Has No Management Network Redundancy Error:  This is new to ESX Server 3.5; VMware HA reports a warning when it detects that there is no redundancy for the Service Console.  Clearly, this is an attempt to prevent situations where isolation response kicks in, and as the author points out can be mitigated by adding another NIC to the vSwitch where the Service Console port group is located.  I have also found that creating a second Service Console port group on another vSwitch will also remove the warning.  Duncan of Yellow Bricks also goes into more detail on Service Console redundancy on his blog as well. [...] [...] ESX Host Currently Has No Management Network Redundancy Error:  This is new to ESX Server 3.5; VMware HA reports a warning when it detects that there is no redundancy for the Service Console.  Clearly, this is an attempt to prevent situations where isolation response kicks in, and as the author points out can be mitigated by adding another NIC to the vSwitch where the Service Console port group is located.  I have also found that creating a second Service Console port group on another vSwitch will also remove the warning.  Duncan of Yellow Bricks also goes into more detail on Service Console redundancy on his blog as well. [...]

]]>