<?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>scolombo Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>scolombo Tracker</description>
    <pubDate>Wed, 15 Nov 2023 12:22:34 GMT</pubDate>
    <dc:date>2023-11-15T12:22:34Z</dc:date>
    <item>
      <title>Re: DVS and kernel port issue</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/DVS-and-kernel-port-issue/m-p/2981397#M14735</link>
      <description>&lt;P&gt;The setup is a single dVS with a Single Subnet space.&lt;/P&gt;&lt;P&gt;2 vmk bound to each vmnik&lt;/P&gt;&lt;P&gt;VMKPING to Storage&lt;/P&gt;&lt;P&gt;It works with no problem when both or one specific NIC, the one bound to uplink1, are connected.&lt;/P&gt;&lt;P&gt;When the NIC bound to uplink2 is the only connected the vmkping to storage doesn't work BUT the storage keeps to be accessible by the host. ALSO other vmk ( vmotion ) on different VLAN connected to the same dVS works fine ( even the vmkping )&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems something much related with the ISCSI virtual adapter binding&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Aug 2023 14:50:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/DVS-and-kernel-port-issue/m-p/2981397#M14735</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2023-08-08T14:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: DVS and kernel port issue</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/DVS-and-kernel-port-issue/m-p/2981186#M14732</link>
      <description>&lt;P&gt;Hi there&lt;/P&gt;&lt;P&gt;we run 8.01&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 15:36:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/DVS-and-kernel-port-issue/m-p/2981186#M14732</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2023-08-07T15:36:30Z</dc:date>
    </item>
    <item>
      <title>DVS and kernel port issue</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/DVS-and-kernel-port-issue/m-p/2981135#M14730</link>
      <description>&lt;P&gt;I'm setting up 2 hosts with dvS.&lt;/P&gt;&lt;P&gt;The dVS has 2 Uplinks and we have configured 2 vmKernel ports for ISCSI traffic and bound each to only one uplink, the other set to unused.&lt;/P&gt;&lt;P&gt;The problem is that it seems that only one, on each host, is working properly.&lt;/P&gt;&lt;P&gt;When we tested the configuration by disabling one uplink at time, from the switch, we found that the with the first uplink UP is working, but with only the second Uplink it is not.&lt;/P&gt;&lt;P&gt;From the switch side all the uplink ports for both the hosts are configured the same.&lt;/P&gt;&lt;P&gt;The strange thing is also that even if the affected host cannot ping the Iscsi Portal anymore it doesn't lose access to the storage.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 11:27:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/DVS-and-kernel-port-issue/m-p/2981135#M14730</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2023-08-07T11:27:37Z</dc:date>
    </item>
    <item>
      <title>Re: Domain Join Error</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Domain-Join-Error/m-p/2976953#M48695</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;The problem with the error was a networking issue that we fixed but still we have something strange happening.&lt;/P&gt;&lt;P&gt;Now we're able to join, apparently, the vcenter to the domain:&lt;/P&gt;&lt;P&gt;- we see the&amp;nbsp; Vcenter's computer object created in the AD&lt;/P&gt;&lt;P&gt;- we see the following in the vcenter&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="scolombo_1-1689169271882.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/102552iB84735AE3DED019F/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="scolombo_1-1689169271882.png" alt="scolombo_1-1689169271882.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;however after the required reboot, but even after a browser refresh, the situation gets back as we didn't do the join&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 13:41:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Domain-Join-Error/m-p/2976953#M48695</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2023-07-12T13:41:21Z</dc:date>
    </item>
    <item>
      <title>Domain Join Error</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Domain-Join-Error/m-p/2976924#M48691</link>
      <description>&lt;P&gt;I'm trying to join a Vcenter 8.01 to an AD domain but I get this error&lt;/P&gt;&lt;P&gt;idm client exception: Error trying to join AD, error code [40121],&lt;/P&gt;&lt;P&gt;anyone had found a fix for this ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jul 2023 11:01:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Domain-Join-Error/m-p/2976924#M48691</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2023-07-12T11:01:02Z</dc:date>
    </item>
    <item>
      <title>vsphere replica</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/vsphere-replica/m-p/2973597#M14220</link>
      <description>&lt;P&gt;we're setting up a vsphere replication appliance in a single Vcenter environment with two hosts.&lt;/P&gt;&lt;P&gt;The purpose is to replicate the VMs from the "production" host to the "DR" host.&lt;/P&gt;&lt;P&gt;So we registered the replication appliance into the vcenter and&amp;nbsp; configured the replica of a vritual machine from the internal datastore of production host to the internal datastore of the DR host.&lt;/P&gt;&lt;P&gt;Then we tried to configure the replica of the VM replica itself, to have it available in case of the production host unaavailability, but got the following errors&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="scolombo_0-1687161674724.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/102121i32902958E56D80D4/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="scolombo_0-1687161674724.png" alt="scolombo_0-1687161674724.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2023 08:01:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/vsphere-replica/m-p/2973597#M14220</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2023-06-19T08:01:21Z</dc:date>
    </item>
    <item>
      <title>sphere replication plug-in issue</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/sphere-replication-plug-in-issue/m-p/2972895#M14216</link>
      <description>&lt;P&gt;I'm installing vsphere replication 8.7 with vcenter 8.01.&lt;/P&gt;&lt;P&gt;After successfully configuring the replication appliance with the vcenter I see the Plug-In in vcenter but I got an error message&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="scolombo_0-1686664310746.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/102048i32ABE3C4C9B160B8/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="scolombo_0-1686664310746.png" alt="scolombo_0-1686664310746.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 13:52:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/sphere-replication-plug-in-issue/m-p/2972895#M14216</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2023-06-13T13:52:02Z</dc:date>
    </item>
    <item>
      <title>Re: change vcenter fqdn</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/change-vcenter-fqdn/m-p/2935040#M46572</link>
      <description>&lt;P&gt;That's the error&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="scolombo_0-1666626340898.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/97949i21DAB2247FBA3DF7/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="scolombo_0-1666626340898.png" alt="scolombo_0-1666626340898.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 15:45:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/change-vcenter-fqdn/m-p/2935040#M46572</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2022-10-24T15:45:48Z</dc:date>
    </item>
    <item>
      <title>Re: change vcenter fqdn</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/change-vcenter-fqdn/m-p/2935027#M46568</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;/P&gt;&lt;P&gt;Vcenter is not in HA and we have no solutions registered.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 14:49:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/change-vcenter-fqdn/m-p/2935027#M46568</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2022-10-24T14:49:05Z</dc:date>
    </item>
    <item>
      <title>change vcenter fqdn</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/change-vcenter-fqdn/m-p/2935007#M46566</link>
      <description>&lt;P&gt;We have a vcenter appliance version&lt;/P&gt;&lt;TABLE border="1" cellspacing="0" cellpadding="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;vCenter Appliance 6.7 Update 3p (6.7.0.51000)&lt;/TD&gt;&lt;TD&gt;2021-11-23&lt;/TD&gt;&lt;TD&gt;18831133&lt;/TD&gt;&lt;TD&gt;18831049&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;with hostname AND FQDN set to only "vcenter".&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="scolombo_0-1666617022297.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/97947iDE8A8113D8CE3245/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="scolombo_0-1666617022297.png" alt="scolombo_0-1666617022297.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we'd like to change it to vcenter.company.com and did it from the VAMI, as per KB.&lt;/P&gt;&lt;P&gt;However the process fail with the error&lt;/P&gt;&lt;P&gt;Fail to reset computer account&lt;/P&gt;&lt;P&gt;and we have to revert to the snapshot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone had the same trouble ?&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 13:12:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/change-vcenter-fqdn/m-p/2935007#M46566</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2022-10-24T13:12:48Z</dc:date>
    </item>
    <item>
      <title>Error chunk 2 failed</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Error-chunk-2-failed/m-p/2902663#M45428</link>
      <description>&lt;P&gt;We have updated vcenter appliance from 6.5 to 7.03d and now in the update tab we get the following error.&lt;/P&gt;&lt;P&gt;How can we fix it ?&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="scolombo_0-1649232538194.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/94610i034AFC4E60FCF021/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="scolombo_0-1649232538194.png" alt="scolombo_0-1649232538194.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2022 08:09:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Error-chunk-2-failed/m-p/2902663#M45428</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2022-04-06T08:09:23Z</dc:date>
    </item>
    <item>
      <title>Re: MIssing virtualwire portgroup when no VM on host</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/MIssing-virtualwire-portgroup-when-no-VM-on-host/m-p/2885689#M14196</link>
      <description>&lt;P&gt;hello&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1199689"&gt;@Sreec&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes I'm referring to Stretched VXLAN.&lt;/P&gt;&lt;P&gt;Port groups are shown in the "networks" tabs in vcenter on the dVS, what I'm referring to is the "virtual switch" tab in the host configuration settings.&lt;/P&gt;&lt;P&gt;The host has the dVS in its configuration tab, and a standard virtual switch, but it doesn't show any of the dvpg defined in the dVS.&lt;/P&gt;&lt;P&gt;Only after moving a VM, which is using one dVPG, the corresponding dVPG is shown in the host's configuration.&lt;/P&gt;&lt;P&gt;It happens with all distributed port group, not only with those related to NSX VXLAN&lt;/P&gt;&lt;P&gt;I suppose this would be normal behavior but never noticed that&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Dec 2021 16:28:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/MIssing-virtualwire-portgroup-when-no-VM-on-host/m-p/2885689#M14196</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-12-29T16:28:18Z</dc:date>
    </item>
    <item>
      <title>MIssing virtualwire portgroup when no VM on host</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/MIssing-virtualwire-portgroup-when-no-VM-on-host/m-p/2885539#M14194</link>
      <description>&lt;P&gt;We have a 4-node cluster with NSX 6.4.4 and recently I noticed a strange thing I'd like to have a check with the community.&lt;/P&gt;&lt;P&gt;I noticed on one host, that was brought back from maintenance, that the virtualwire port groups related to the stretched VLANs are not present on dVS of the host&lt;/P&gt;&lt;P&gt;However after moving a VM, attached to one of the stretched VLAN, to that host works fine and the VM is reachable and the portgroup, then, shows up in the dVS on the vcenter.&lt;/P&gt;&lt;P&gt;Is this an expected behavior ?&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;SC&lt;/P&gt;</description>
      <pubDate>Tue, 28 Dec 2021 15:50:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/MIssing-virtualwire-portgroup-when-no-VM-on-host/m-p/2885539#M14194</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-12-28T15:50:29Z</dc:date>
    </item>
    <item>
      <title>Re: Error while updating from 6.5 to 6.7 no space left</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880236#M279122</link>
      <description>&lt;P&gt;I ran the dry-run install command and it reports a lot of VIBS in the "removed" section, I could not say which would be ok to remove actually&lt;/P&gt;</description>
      <pubDate>Sat, 27 Nov 2021 15:46:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880236#M279122</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-11-27T15:46:54Z</dc:date>
    </item>
    <item>
      <title>Re: Error while updating from 6.5 to 6.7 no space left</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880212#M279120</link>
      <description>&lt;P&gt;I ran the "update" not the "install" since on the host there might be vibs not from HPE customized patch bundle&lt;/P&gt;</description>
      <pubDate>Sat, 27 Nov 2021 13:04:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880212#M279120</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-11-27T13:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: Error while updating from 6.5 to 6.7 no space left</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880208#M279118</link>
      <description>&lt;P&gt;The host was running 6.5 and I've been able to install the HPE customized version&amp;nbsp;V&lt;SPAN class=""&gt;&lt;SPAN&gt;Mware ESXi, 6.7.0, 15160138&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;However if I try, even now, to install the HPE Customized version&amp;nbsp;&amp;nbsp;VMware ESXi, 6.7.0,16773714 I got the error "no space left"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;the command I'm running is&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;esxcli software profile update -p HPE-ESXi-6.7.0-Update3-Gen9plus-670.U3.10.6.0.83-customized -d /vmfs/volumes/SG-BU-SVT-DS01/Upgrade/Q8A57-11113_hpe-esxi6.7u3ep16-16773714-670.U3.10.6.0.83-offline-bundle.zip&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 27 Nov 2021 12:27:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880208#M279118</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-11-27T12:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: Error while updating from 6.5 to 6.7 no space left</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880199#M279116</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;/P&gt;&lt;P&gt;I already had a look at it but Inodes are fine&amp;nbsp;&lt;/P&gt;&lt;P&gt;Following is the output of the command&lt;/P&gt;&lt;P&gt;[root@sg-bu-svt-01:/tmp] find / -path "/vmfs" -prune -o -type f -size +50000k -exec ls -lh '{}' \;&lt;BR /&gt;-r--r--r-- 1 root root 174.6M Nov 27 10:33 /tardisks/sb.v00&lt;BR /&gt;-r--r--r-- 1 root root 311.6M Nov 27 10:33 /tardisks/s.v00&lt;BR /&gt;-r--r--r-- 1 root root 114.6M Nov 27 10:33 /tardisks/kdriver.t00&lt;BR /&gt;-rw------- 1 root root 271.8G Nov 27 11:06 /dev/lvm/5fd21f48-be222f02-1f89-b47af13f8ce4&lt;BR /&gt;-rw------- 1 root root 279.4G Nov 27 11:06 /dev/disks/naa.600508b1001c7e3a9f863ed2438265d8&lt;BR /&gt;-rw------- 1 root root 2.5G Nov 27 11:06 /dev/disks/naa.600508b1001c7e3a9f863ed2438265d8:9&lt;BR /&gt;-rw------- 1 root root 286.0M Nov 27 11:06 /dev/disks/naa.600508b1001c7e3a9f863ed2438265d8:8&lt;BR /&gt;-rw------- 1 root root 110.0M Nov 27 11:06 /dev/disks/naa.600508b1001c7e3a9f863ed2438265d8:7&lt;BR /&gt;-rw------- 1 root root 250.0M Nov 27 11:06 /dev/disks/naa.600508b1001c7e3a9f863ed2438265d8:6&lt;BR /&gt;-rw------- 1 root root 250.0M Nov 27 11:06 /dev/disks/naa.600508b1001c7e3a9f863ed2438265d8:5&lt;BR /&gt;-rw------- 1 root root 272.0G Nov 27 11:06 /dev/disks/naa.600508b1001c7e3a9f863ed2438265d8:3&lt;BR /&gt;-rw------- 1 root root 4.0G Nov 27 11:06 /dev/disks/naa.600508b1001c7e3a9f863ed2438265d8:2&lt;/P&gt;</description>
      <pubDate>Sat, 27 Nov 2021 11:10:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880199#M279116</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-11-27T11:10:17Z</dc:date>
    </item>
    <item>
      <title>Error while updating from 6.5 to 6.7 no space left</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880195#M279113</link>
      <description>&lt;P&gt;We're updating from esxi 6.5 to 6.7 with offline update.&lt;/P&gt;&lt;P&gt;The update fails with the error&amp;nbsp;&lt;/P&gt;&lt;P&gt;[InstallationError]&lt;BR /&gt;[Errno 28] No space left on device&lt;BR /&gt;vibs = VMware_bootbank_esx-base_6.7.0-3.120.16773714&lt;BR /&gt;Please refer to the log file for more details.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we already enable the swap on data store and rebooted but still getting the error&lt;/P&gt;&lt;P&gt;Can anyone provide a fix for this ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 27 Nov 2021 10:47:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Error-while-updating-from-6-5-to-6-7-no-space-left/m-p/2880195#M279113</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-11-27T10:47:13Z</dc:date>
    </item>
    <item>
      <title>NSX Edge L2VPN wrong time</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Edge-L2VPN-wrong-time/m-p/2860488#M13704</link>
      <description>&lt;P&gt;We noticed that the uptime of the L2VPN in our edge report a wrong time ( 1970 ) as in the picture attached, where should we look to correct it ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Aug 2021 07:46:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Edge-L2VPN-wrong-time/m-p/2860488#M13704</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-08-03T07:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot create trunk interface</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Cannot-create-trunk-interface/m-p/2860057#M13695</link>
      <description>&lt;P&gt;Found that first must create the interface and then edit it and change to trunk&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jul 2021 12:05:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Cannot-create-trunk-interface/m-p/2860057#M13695</guid>
      <dc:creator>scolombo</dc:creator>
      <dc:date>2021-07-30T12:05:16Z</dc:date>
    </item>
  </channel>
</rss>

