<?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>rcporto Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>rcporto Tracker</description>
    <pubDate>Wed, 15 Nov 2023 10:55:21 GMT</pubDate>
    <dc:date>2023-11-15T10:55:21Z</dc:date>
    <item>
      <title>Re: content library iso file in vsphere 6.0</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/content-library-iso-file-in-vsphere-6-0/m-p/2248111#M26840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure if I understand your question, but to mount a ISO from content library to a VM you need vSphere 6.5.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Oct 2019 10:59:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/content-library-iso-file-in-vsphere-6-0/m-p/2248111#M26840</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-10-10T10:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: vcenter role</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/vcenter-role/m-p/2246957#M1944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Read only should be enough and you can check additional information in the following link: &lt;A href="https://docs.vmware.com/en/vRealize-Log-Insight/4.8/com.vmware.log-insight.getting-started.doc/GUID-4E3853AA-EFBF-4004-B182-DF5F6DC3826F.html" title="https://docs.vmware.com/en/vRealize-Log-Insight/4.8/com.vmware.log-insight.getting-started.doc/GUID-4E3853AA-EFBF-4004-B182-DF5F6DC3826F.html"&gt;Minimum Requirements&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN style="color: #565656; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; font-size: 13px;"&gt;To pull events, tasks, and alarms data from a vCenter Server, you must provide a set of user credentials for that vCenter Server. The minimum role required to register and unregister vRealize Log Insight with a vCenter Server is &lt;/SPAN&gt;&lt;SPAN class="ph uicontrol" style="font-weight: bold; color: #565656; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; font-size: 13px;"&gt;Read-only&lt;/SPAN&gt;&lt;SPAN style="color: #565656; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; font-size: 13px;"&gt;. The role must be set at the vCenter Server level and propagated to child objects. To configure ESXi hosts that a vCenter Server manages, &lt;/SPAN&gt;&lt;SPAN class="ph productname" style="color: #565656; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; font-size: 13px;"&gt;vRealize Log Insight&lt;/SPAN&gt;&lt;SPAN style="color: #565656; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; font-size: 13px;"&gt; requires additional privileges.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jul 2019 00:06:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/vcenter-role/m-p/2246957#M1944</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-07-10T00:06:27Z</dc:date>
    </item>
    <item>
      <title>Re: VMHBA "Unknown"</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VMHBA-quot-Unknown-quot/m-p/484289#M5099</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you tried to swap the cable between the vmhba1 and vmhba2 to see if the problem still happen on vmhba1 or if it moves to vmhba2? Also, the FC port type on physical switch are configured with the same settings? Are you using Brocade switches?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Jul 2019 00:01:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VMHBA-quot-Unknown-quot/m-p/484289#M5099</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-07-10T00:01:28Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot access esxi host</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cannot-access-esxi-host/m-p/483488#M4992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you double check if the IP address assigned to the ESXi is not duplicated? Also, please login to ESXI through the SSH and run the following command to check if Host Client vib is correctly installed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#&amp;nbsp;&amp;nbsp; esxcli software vib list | grep esx-ui&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Jul 2019 23:40:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cannot-access-esxi-host/m-p/483488#M4992</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-07-09T23:40:59Z</dc:date>
    </item>
    <item>
      <title>Re: Max Latency between 6.7 vCenter and remote hosts</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Max-Latency-between-6-7-vCenter-and-remote-hosts/m-p/484577#M6364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure about max latency, but ESXi send a heartbeat every 10 seconds and vCenter has a window of 60 seconds to receive the heartbeat. If your hosts are intermittently disconnecting from vCenter, you may can increase the timeout limit like described in the following KB: &lt;A href="https://kb.vmware.com/s/article/1005757"&gt;https://kb.vmware.com/s/article/1005757&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Jul 2019 23:25:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Max-Latency-between-6-7-vCenter-and-remote-hosts/m-p/484577#M6364</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-07-09T23:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: P2V stock at 1% - cannot connect to helper</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/P2V-stock-at-1-cannot-connect-to-helper/m-p/481270#M7034</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you check the helper VM received correct IP address settings? Also, check if the following KB helps: &lt;A href="https://kb.vmware.com/s/article/2037687" title="https://kb.vmware.com/s/article/2037687"&gt;VMware Knowledge Base&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jul 2019 02:03:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/P2V-stock-at-1-cannot-connect-to-helper/m-p/481270#M7034</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-07-08T02:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: VMs only Power on, direct on ESXi host</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VMs-only-Power-on-direct-on-ESXi-host/m-p/459813#M1963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You mean that you cannot power on VMs from vCenter, but if you login directly to the ESXi host you are able to power on the VMs? If my understand is correct, can you share the message that you get when trying to power on the VM from vCenter? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I experienced that problem before and it was due to some services stopped on vCSA due to low free space. Also, you may can check if the following help: &lt;A href="http://virtualization24x7.blogspot.com/2016/01/unable-to-power-on-vm-in-vcenter-6.html" title="http://virtualization24x7.blogspot.com/2016/01/unable-to-power-on-vm-in-vcenter-6.html"&gt;Virtualization The Future: Unable to Power on VM in vCenter 6 - A general system error occurred: Connection refused&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jun 2019 17:38:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VMs-only-Power-on-direct-on-ESXi-host/m-p/459813#M1963</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-11T17:38:27Z</dc:date>
    </item>
    <item>
      <title>Re: Weird EVC mode - EVC (sandy) enabled yet VMs will not migrate across cluster (both sandy)</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Weird-EVC-mode-EVC-sandy-enabled-yet-VMs-will-not-migrate-across/m-p/457596#M1712</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have seen this before, but problem was related to Spectre/Meltdown patch not present in some hosts which was running different build numbers, but in your case build numbers are the same. In that case, I would check the BIOS settings and firmware version if are the same across all three hosts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jun 2019 22:55:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Weird-EVC-mode-EVC-sandy-enabled-yet-VMs-will-not-migrate-across/m-p/457596#M1712</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-10T22:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: Weird EVC mode - EVC (sandy) enabled yet VMs will not migrate across cluster (both sandy)</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Weird-EVC-mode-EVC-sandy-enabled-yet-VMs-will-not-migrate-across/m-p/457594#M1710</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you please let us know the exact build number of each ESXi host and also the exact message that you get regarding the CPU compatibility?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jun 2019 18:38:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Weird-EVC-mode-EVC-sandy-enabled-yet-VMs-will-not-migrate-across/m-p/457594#M1710</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-10T18:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN uplinks - add vMotion traffic</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-uplinks-add-vMotion-traffic/m-p/456624#M637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;B&gt;andvm&lt;/B&gt;​&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If implemented correctly it should not be a problem, I have seen many clusters sharing the 10GbE uplinks not between vSAN and vMotion but also for VM traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following documentation shows how to designing a vSAN network and talks about implement NIOC to configure shares and reservation for the traffic that is sharing the uplinks: &lt;A href="https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vsan-planning.doc/GUID-031F9637-EE29-4684-8644-7A93B9FD8D7B.html" title="https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vsan-planning.doc/GUID-031F9637-EE29-4684-8644-7A93B9FD8D7B.html"&gt;Designing the vSAN Network&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Jun 2019 21:53:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-uplinks-add-vMotion-traffic/m-p/456624#M637</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-08T21:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: vSwitch  information about vmnicX connectoin to physical switch</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSwitch-information-about-vmnicX-connectoin-to-physical-switch/m-p/451097#M867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The CDP (Cisco DIscovery Protocol) is also available if you connect directly to the vSphere Host Client, but you need to make sure it is enabled on physical switch. Here is how it shows on vSphere Host Client:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/11095iC48CD0F3BFCB1025/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2019 14:27:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSwitch-information-about-vmnicX-connectoin-to-physical-switch/m-p/451097#M867</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-07T14:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Restore files delta.vmdk without flat and data loss (vmdk)</title>
      <link>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Restore-files-delta-vmdk-without-flat-and-data-loss-vmdk/m-p/451415#M2372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, I misunderstood... I thought he have the flat vmdk and only the description vmdk was missing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2019 11:44:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Restore-files-delta-vmdk-without-flat-and-data-loss-vmdk/m-p/451415#M2372</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-06T11:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: Restore files delta.vmdk without flat and data loss (vmdk)</title>
      <link>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Restore-files-delta-vmdk-without-flat-and-data-loss-vmdk/m-p/451412#M2369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sergio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following VMware KB article shows how to recreate a missing virtual machine disk descriptor file : &lt;A href="https://kb.vmware.com/s/article/1002511" title="https://kb.vmware.com/s/article/1002511"&gt;VMware Knowledge Base&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2019 10:51:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Restore-files-delta-vmdk-without-flat-and-data-loss-vmdk/m-p/451412#M2369</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-06T10:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: vcenter 6.7 U1 appliance version cannot login FLEX.</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vcenter-6-7-U1-appliance-version-cannot-login-FLEX/m-p/449080#M640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please, check if Flash is allowed on that site. The vSphere Web Client (FLEX) is still available on vCenter 6.7 U1, but need to make sure Flash is allowed and after allow, try reload/refresh the page.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2019 09:33:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vcenter-6-7-U1-appliance-version-cannot-login-FLEX/m-p/449080#M640</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-06T09:33:46Z</dc:date>
    </item>
    <item>
      <title>Re: vSwitch  information about vmnicX connectoin to physical switch</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSwitch-information-about-vmnicX-connectoin-to-physical-switch/m-p/451095#M865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On vSphere Web Client HTML5 version, just go to Configure -&amp;gt; Networking -&amp;gt; Physical Adapters then select the vmnicX and you will have the option to check the CDP or LLDP information like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/11036iAA088BCA527381DE/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2019 09:28:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSwitch-information-about-vmnicX-connectoin-to-physical-switch/m-p/451095#M865</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-06T09:28:03Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to add vCenter Server in Skyline Collector</title>
      <link>https://communities.vmware.com/t5/Skyline-Community-Discussions/Unable-to-add-vCenter-Server-in-Skyline-Collector/m-p/448544#M30</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you using a SSO domain different than vsphere.local ? If yes you need to select the option to use Custom SSO Configuration, see: &lt;A href="https://docs.vmware.com/en/VMware-Skyline/1.4/user-guide/GUID-1FCCB902-2710-4B6A-9824-FAFDAA36E72F.html" title="https://docs.vmware.com/en/VMware-Skyline/1.4/user-guide/GUID-1FCCB902-2710-4B6A-9824-FAFDAA36E72F.html"&gt;Add a vCenter Server&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jun 2019 18:16:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Skyline-Community-Discussions/Unable-to-add-vCenter-Server-in-Skyline-Collector/m-p/448544#M30</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-05T18:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: Different ESXi Host Versions on the Protected and Recovery Sites</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/Different-ESXi-Host-Versions-on-the-Protected-and-Recovery-Sites/m-p/446608#M1934</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are correct, you just need to make sure that VMs at protected site running vSphere ESXi 6.7 do not run on virtual hardware version higher than 13, otherwise the VMs will not be able to boot at protected site running vSphere ESXi 6.5, since the it supports only virtual hardware version 13 and lower: &lt;A href="https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-64D4B1C9-CD5D-4C68-8B50-585F6A87EBA0.html" title="https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-64D4B1C9-CD5D-4C68-8B50-585F6A87EBA0.html"&gt;Virtual Machine Compatibility&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jun 2019 18:04:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/Different-ESXi-Host-Versions-on-the-Protected-and-Recovery-Sites/m-p/446608#M1934</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-05T18:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: isolated mode conditions</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/isolated-mode-conditions/m-p/444192#M3133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Host is isolated if it cannot ping the isolation address (usually the default gateway) and the vSphere HA agent cannot communicate with any other host in the cluster. Read more about that in the following documentation link: &lt;A href="https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-2CE4E436-0B0A-48E9-ABE6-5CA3996F6877.html" title="https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-2CE4E436-0B0A-48E9-ABE6-5CA3996F6877.html"&gt;vSphere HA Agent is in the Network Isolated State&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Jun 2019 00:22:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/isolated-mode-conditions/m-p/444192#M3133</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-04T00:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: NFS best practice</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/NFS-best-practice/m-p/444546#M80</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To isolate storage traffic from other network traffic, a best practices is to use either dedicated switches and physical NICs for your NFS, but if you don't have enough physical network resources to dedicated to NFS, you may can share the same physical network, including physical NICs, but make sure you at least isolate NFS traffic using VLANs and since you are using distributed switches you may also can consider enable Network I/O Control (NIOC).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check some additional best practices in the following link: &lt;A href="https://storagehub.vmware.com/export_to_pdf/best-practices-for-running-vmware-vsphere-on-network-attached-storage" title="https://storagehub.vmware.com/export_to_pdf/best-practices-for-running-vmware-vsphere-on-network-attached-storage"&gt;https://storagehub.vmware.com/export_to_pdf/best-practices-for-running-vmware-vsphere-on-network-attached-storage&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Jun 2019 22:58:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/NFS-best-practice/m-p/444546#M80</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-06-03T22:58:19Z</dc:date>
    </item>
    <item>
      <title>Re: TIME : difference between VSPHERE 6.0 U3 , installed client   vs  HTML/JAVA client</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/TIME-difference-between-VSPHERE-6-0-U3-installed-client-vs-HTML/m-p/1841996#M20330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The ESXi uses UTC time and do not support time zone change. The time that you see in the vSphere Client is the date and time of host translated to the local time where you are running the vSphere Client. I just checked one of my ESXi 6.5 hosts and if you use the embedded host client (HTML5) looks like it shows the UTC time instead of translate the time to the local time zone as the vSphere Client does. That said, you should not worry about that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For additional info, please check the following VMware KB article: &lt;A href="https://kb.vmware.com/s/article/1436" title="https://kb.vmware.com/s/article/1436"&gt;VMware Knowledge Base&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Mar 2019 14:17:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/TIME-difference-between-VSPHERE-6-0-U3-installed-client-vs-HTML/m-p/1841996#M20330</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2019-03-25T14:17:15Z</dc:date>
    </item>
  </channel>
</rss>

