<?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>topic Re: Unable to VMotion: the object or item referred to could not be found. vDS dvs port 48 cannot be in VMware vCenter™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938904#M46712</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Hi,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Could you please explain yourself better, your last post is not very clear about your network configuration.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 17 Nov 2022 19:15:10 GMT</pubDate>
    <dc:creator>Kinnison</dc:creator>
    <dc:date>2022-11-17T19:15:10Z</dc:date>
    <item>
      <title>Unable to VMotion: the object or item referred to could not be found. vDS dvs port 48 cannot be foun</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938637#M46701</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;I've got a 2 host cluster at the moment with ESXi 7.0.2.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both are configured with 2 distributed vswitches, and the same vmks', of those 3 are static IP'd including the vMotion VLAN.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm able to move VM's from host A to host B, but not from host B to host A.&lt;/P&gt;&lt;P&gt;Any thoughts or ideas?&amp;nbsp; Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 20:48:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938637#M46701</guid>
      <dc:creator>mark24</dc:creator>
      <dc:date>2022-11-16T20:48:31Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to VMotion: the object or item referred to could not be found. vDS dvs port 48 cannot be</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938645#M46702</link>
      <description>&lt;P&gt;Have you checked the network settings on both hosts? Subnet mask, gw, etc ?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 21:11:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938645#M46702</guid>
      <dc:creator>nordhuus</dc:creator>
      <dc:date>2022-11-16T21:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to VMotion: the object or item referred to could not be found. vDS dvs port 48 cannot be</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938902#M46711</link>
      <description>&lt;P&gt;Yes, both hosts have the same info for subnet mask, gw, and the correct IP's.&lt;/P&gt;&lt;P&gt;However, the vmkernel adapters are marked differently and I'm not sure how this would impact - for example, the original host's mgmt vmk0 is labeled incorrectly but with the correct IP address and on a dvswitch.&amp;nbsp; The second host has a mgmt vmk0 on a switch -&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not sure how (if any) much impact vmk's would have on this quite honestly.&amp;nbsp; Otherwise, I may reach out to VMware tech support.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 19:02:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938902#M46711</guid>
      <dc:creator>mark24</dc:creator>
      <dc:date>2022-11-17T19:02:29Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to VMotion: the object or item referred to could not be found. vDS dvs port 48 cannot be</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938904#M46712</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hi,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Could you please explain yourself better, your last post is not very clear about your network configuration.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 19:15:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2938904#M46712</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2022-11-17T19:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to VMotion: the object or item referred to could not be found. vDS dvs port 48 cannot be</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2939002#M46715</link>
      <description>&lt;P&gt;did you check vmkping ( vmotion IP) host B to A , vice versa&lt;/P&gt;</description>
      <pubDate>Fri, 18 Nov 2022 08:33:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-VMotion-the-object-or-item-referred-to-could-not-be/m-p/2939002#M46715</guid>
      <dc:creator>RajeevVCP4</dc:creator>
      <dc:date>2022-11-18T08:33:30Z</dc:date>
    </item>
  </channel>
</rss>

