<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>aaal Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>aaal Tracker</description>
    <pubDate>Wed, 15 Nov 2023 11:30:13 GMT</pubDate>
    <dc:date>2023-11-15T11:30:13Z</dc:date>
    <item>
      <title>Re: Host xxx currently has no management network redundancy</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Host-xxx-currently-has-no-management-network-redundancy/m-p/1552430#M21732</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just to add on something even if you find that you already have 2 or more nics set for redundancy network (and probably you have done the rest which the other posters mentioned) but the warning still persists, then you may have look at your port group settings again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have vmotion enabled, re-check that your switch properties that you have the Vmotion and Management Traffic enabled (most likely its just the vmotion issue). I made this silly mistake once by not enabling it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Jan 2015 08:44:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/Host-xxx-currently-has-no-management-network-redundancy/m-p/1552430#M21732</guid>
      <dc:creator>aaal</dc:creator>
      <dc:date>2015-01-19T08:44:36Z</dc:date>
    </item>
  </channel>
</rss>

