<?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>A13x Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>A13x Tracker</description>
    <pubDate>Sat, 25 Nov 2023 07:13:06 GMT</pubDate>
    <dc:date>2023-11-25T07:13:06Z</dc:date>
    <item>
      <title>Re: vSphere 7 vSAN Skyline error for Update Manager</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSphere-7-vSAN-Skyline-error-for-Update-Manager/m-p/2909940#M14269</link>
      <description>&lt;P&gt;I updated vCenter versions and it resolved it for me:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3e-release-notes.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3e-release-notes.html&lt;/A&gt;&lt;/P&gt;&lt;H2&gt;Resolved Issues&lt;/H2&gt;&lt;P&gt;The resolved issues are grouped as follows.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3e-release-notes.html#miscellaneous-issues-resolved" target="_blank" rel="noopener"&gt;Miscellaneous Issues&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Miscellaneous Issues&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;VMware Skyline Health screen shows an error instead of system health info&lt;/STRONG&gt;&lt;P&gt;In the vSphere Client, when you navigate to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Monitor&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Skyline Health&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;under a vSAN or vSphere cluster, you see an error such as&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Unable to query vSphere health information. Check vSphere Client logs for details.. The issue occurs because in certain environments Skyline Health cannot discover the APIs it needs to collect data from the vCenter Server system and ESXi hosts.&lt;BR /&gt;In the analytics service logs, you see errors such as:&lt;BR /&gt;Error while getting the data providers list from: com.vmware.ph.phservice.provider.appliance.ApplianceDataProvidersConnection java.lang.IllegalStateException: Unable to locate VAPI URI.&lt;/P&gt;&lt;P&gt;This issue is resolved in this release.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 07:43:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSphere-7-vSAN-Skyline-error-for-Update-Manager/m-p/2909940#M14269</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2022-05-19T07:43:43Z</dc:date>
    </item>
    <item>
      <title>Random Freezes after updating DELL BIOS to 2.14 + ESXi 7 U3d</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Random-Freezes-after-updating-DELL-BIOS-to-2-14-ESXi-7-U3d/m-p/2908671#M281546</link>
      <description>&lt;P&gt;I seem to have a strange one, hosts are randomly freezing / locking up (not crashing or PSOD) after updating the DELL BIOS to 2.14 with either the VMware or DELL 7 U3d image (&lt;SPAN class=""&gt;&lt;SPAN&gt;VMware ESXi, 7.0.3, 19482537)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Is anyone experiencing any strangeness?&lt;/P&gt;&lt;P&gt;Downgrading the host back to 2.13 seems to have brought most of the stability back but unsure how a BIOS update could cause this. Nothing in the logs to provide any hints as to why this is occurring and it seems to be more frequent on some hosts than others (all running same hardware).&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 10:35:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Random-Freezes-after-updating-DELL-BIOS-to-2-14-ESXi-7-U3d/m-p/2908671#M281546</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2022-05-12T10:35:42Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2867282#M278033</link>
      <description>&lt;P&gt;It sounds like your NSX appliance might need a db cleanup. Our T and V appliances always clog up after sometime and we clear the db down before any upgrade&lt;/P&gt;</description>
      <pubDate>Fri, 17 Sep 2021 07:37:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2867282#M278033</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-09-17T07:37:49Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2865004#M277814</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/221674"&gt;@einstein-a-go-g&lt;/a&gt;&amp;nbsp;i really do not see what the issue is, times have changed and so have recommendations. It also baffles me why anyone would upgrade to major releases and not do a complete full rebuild of a host. On the next host refresh just spec in some disks rather than SD cards.&amp;nbsp;&lt;/P&gt;&lt;P&gt;the errors and log spew would have been detected after upgrading to make you stop the roll out.&lt;/P&gt;&lt;P&gt;if you can afford to run VMware i am sure a few disks are next to nothing. ESXi rebuilds can be done in minutes.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Sep 2021 16:03:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2865004#M277814</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-09-02T16:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2864693#M277769</link>
      <description>&lt;P&gt;Lcm has the Dell add-on images,the same ones that are built into the Dell iso. You just create a baseline and patch.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Aug 2021 22:36:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2864693#M277769</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-08-31T22:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2864397#M277731</link>
      <description>&lt;P&gt;Skyline detects for potential issues with the new VMFS-L on low endurance SD cards&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Aug 2021 14:42:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2864397#M277731</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-08-30T14:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2863953#M277676</link>
      <description>&lt;P&gt;All seems fine for majority of customers however I do have a few which skyline detects possible sd card issues.&lt;/P&gt;&lt;P&gt;Only time will tell but so far so good&lt;/P&gt;</description>
      <pubDate>Thu, 26 Aug 2021 17:27:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2863953#M277676</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-08-26T17:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2863597#M277610</link>
      <description>&lt;P&gt;Test Environment patched, will see how it goes before moving onto prod. I hope VMware are not going through a bad patch with the updates/ patches again like they did years ago. Patch one thing and introduce another bug just as bad...&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 21:55:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2863597#M277610</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-08-24T21:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.0.2 becomes uncontrollable</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2862739#M6722</link>
      <description>&lt;P&gt;what i find more annoying is when they as you, when will this be fixed. Something like this should have been fixed much sooner. instead they release a unsigned patch which does work but then prevents you from using secure boot.&lt;/P&gt;&lt;P&gt;Roll back for us was not an option, too hosts and work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Getting the patch from VMware was not an issue, provided them with all the info bundles, logs and snippets. Proved it was the same error and got patch straight away. It is possible to use a script as a workaround to bypass this but its not something you would do in a prod environment.&lt;/P&gt;&lt;P&gt;Still not as bad as a few years back when there were VMware bugs and issues with each release.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Aug 2021 15:36:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2862739#M6722</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-08-18T15:36:06Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2859465#M277180</link>
      <description>&lt;P&gt;the fix is a later version of the vib from vmware which you can request via a support SR. the release is hopefully due next month with the rest of the vmware host and vcenter patches&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jul 2021 11:20:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2859465#M277180</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-07-27T11:20:47Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2858812#M277092</link>
      <description>&lt;P&gt;The source is VMware via a sr. I obtained the patch before but it never supported secure boot. I opened up a new case to seek an ETA and was told esxi patches for 6.7 and 7 will be released next month.&lt;/P&gt;&lt;P&gt;They also confirmed it several times. This SD card patch would be included and also support secure boot.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jul 2021 15:56:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2858812#M277092</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-07-22T15:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2858539#M277072</link>
      <description>&lt;P&gt;Patch release due next month to resolve this and also support secure boot.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jul 2021 10:54:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2858539#M277072</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-07-21T10:54:57Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.0.2 becomes uncontrollable</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2857237#M6678</link>
      <description>&lt;P&gt;just get the updated one with secure boot supported.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jul 2021 20:56:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2857237#M6678</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-07-13T20:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: Server 2019 VM Blue Screens</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Server-2019-VM-Blue-Screens/m-p/2851510#M6647</link>
      <description>&lt;P&gt;it sounds like it might be an issue with the OS. have you tried moving it to another host? When you reinstalled vmware tools did you use the ones on the host or did you download a later version?&lt;/P&gt;&lt;P&gt;you might need to try a backup restore to see if the issue persists?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jun 2021 09:04:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Server-2019-VM-Blue-Screens/m-p/2851510#M6647</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-06-08T09:04:43Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.0.2 becomes uncontrollable</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2851505#M6646</link>
      <description>&lt;P&gt;These are the steps i performed before the patch.&lt;/P&gt;&lt;P&gt;stop the vpxa and hostd these must be stopped before.&lt;/P&gt;&lt;P&gt;/etc/init.d/hostd stop&lt;BR /&gt;/etc/init.d/vpxa stop&lt;/P&gt;&lt;P&gt;Check for dead paths&amp;nbsp;esxcfg-mpath -L&lt;/P&gt;&lt;P&gt;ID the sd card device and check for anything dead&lt;/P&gt;&lt;P&gt;esxcli storage core device world list&lt;/P&gt;&lt;P&gt;mine is vmhba32 so i run&lt;/P&gt;&lt;P&gt;esxcfg-rescan -d vmhba32&lt;/P&gt;&lt;P&gt;Check again&lt;/P&gt;&lt;P&gt;esxcli storage core device world list&lt;/P&gt;&lt;P&gt;if still exist&amp;nbsp;esxcfg-rescan -d vmhba32&lt;/P&gt;&lt;P&gt;esxcfg-rescan -u vmhba32&lt;/P&gt;&lt;P&gt;wait at least 5 mins because of the rescan etc etc.&lt;/P&gt;&lt;P&gt;then&lt;/P&gt;&lt;P&gt;/etc/init.d/hostd start&lt;BR /&gt;/etc/init.d/vpxa start&lt;/P&gt;&lt;P&gt;the trick is to clear it all, wait for a duration then start the services. If you do not wait enough or if they are not cleared you need to do it all again&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's assuming you have the sd card bug and there are a spam of entries with&amp;nbsp;local6.info: vmkernel: cpu24:2097581)ScsiVmas: 1057: Inquiry for VPD page 00 to device mpx.vmhba32:C0:T0:L0 failed with error Timeout&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jun 2021 08:57:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2851505#M6646</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-06-08T08:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.0.2 becomes uncontrollable</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2851350#M6640</link>
      <description>&lt;P&gt;ive used the same vib on my hpe and dell and sd card has storage issue has been fixed. There is a temp work around that involves rescanning the vmhba32 and stopping the hostd and vpxa to bring the host back online. if you do not install the vib you will be doing this each time the host drops off.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jun 2021 13:43:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2851350#M6640</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-06-07T13:43:24Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.0.2 becomes uncontrollable</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2851339#M6638</link>
      <description>&lt;P&gt;Contact VMware and request&amp;nbsp;VMW_bootbank_vmkusb_0.1-2vmw.702.0.20.45179358.vib&lt;/P&gt;&lt;P&gt;This fixes the SD card issue.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Jun 2021 12:31:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2851339#M6638</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-06-07T12:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.0.2 becomes uncontrollable</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2847304#M6621</link>
      <description>&lt;P&gt;I have noticed the exact same issue with hosts i have deployed also. The only work around i have found is a fresh install of&amp;nbsp;Dell EMC customized VMware ESXi 7.0 U2 A01 which was released a few days ago. It solves stability and NSX-V DFW netcpa issue.&lt;/P&gt;&lt;P&gt;I am working on another workaround as i do not wish to rebuild all hosts.&lt;/P&gt;</description>
      <pubDate>Sat, 15 May 2021 09:56:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/ESXi-7-0-2-becomes-uncontrollable/m-p/2847304#M6621</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-05-15T09:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere 7 vSAN Skyline error for Update Manager</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSphere-7-vSAN-Skyline-error-for-Update-Manager/m-p/2846616#M13023</link>
      <description>&lt;P&gt;im connected to the internet via proxy but also get this warning after Update 2a patch&lt;/P&gt;</description>
      <pubDate>Tue, 11 May 2021 15:19:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSphere-7-vSAN-Skyline-error-for-Update-Manager/m-p/2846616#M13023</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-05-11T15:19:44Z</dc:date>
    </item>
    <item>
      <title>NSX-V Content Pack Broke with Loginsight 8.3?</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/NSX-V-Content-Pack-Broke-with-Loginsight-8-3/m-p/2830670#M2695</link>
      <description>&lt;P&gt;Anyone else had any strange issues with dashboards with the nsx-v content pack after upgrading from 8.2 to 8.3? Dashboards no longer work correctly but everything else seems fine. Removing content packs and re-installing made no difference&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Field could not be added as filter because the field was deleted or a user saved a private field to a shared dashboard.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;On every item on a dashboard.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2021 10:16:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/NSX-V-Content-Pack-Broke-with-Loginsight-8-3/m-p/2830670#M2695</guid>
      <dc:creator>A13x</dc:creator>
      <dc:date>2021-02-18T10:16:25Z</dc:date>
    </item>
  </channel>
</rss>

