<?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>mbartle Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>mbartle Tracker</description>
    <pubDate>Sat, 25 Nov 2023 06:49:45 GMT</pubDate>
    <dc:date>2023-11-25T06:49:45Z</dc:date>
    <item>
      <title>vCenter loading wrong SRM page after upgrade to 8.6</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/vCenter-loading-wrong-SRM-page-after-upgrade-to-8-6/m-p/2935641#M14078</link>
      <description>&lt;P&gt;We had deployed SRM 8.5 and it was working fine. From the vCenter, you could select site recovery , then click Open Site Recovery and it would load the SRM page.&lt;/P&gt;&lt;P&gt;my VRA is on a .local using a self signed SSL&lt;/P&gt;&lt;P&gt;my SRM is on a .ca using a GoDaddy CA signed cert&lt;/P&gt;&lt;P&gt;On 8.5, clicking Open Site Recovery Manager would open srm-site.ca over a secure HTTPS&lt;/P&gt;&lt;P&gt;Today we upgraded to 8.6&lt;/P&gt;&lt;P&gt;Now when we click Open Site Recovery it tries to load &lt;A href="https://vra-site.local" target="_blank"&gt;https://vra-site.local&lt;/A&gt;&amp;nbsp;using a self signed cert&lt;/P&gt;&lt;P&gt;I removed SRM and VRA completely from DR site and re-installed 8.6 clean. Same problem&lt;/P&gt;&lt;P&gt;The only way I can load SRM now, is to open a new browser tab and go to &lt;A href="https://srm-site.ca/dr" target="_blank"&gt;https://srm-site.ca/dr&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;&lt;P&gt;How can I fix this ?&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2022 16:17:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/vCenter-loading-wrong-SRM-page-after-upgrade-to-8-6/m-p/2935641#M14078</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2022-10-27T16:17:08Z</dc:date>
    </item>
    <item>
      <title>Who's taking the plunge and going to guinea pig vCenter and ESXi 8.0?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Who-s-taking-the-plunge-and-going-to-guinea-pig-vCenter-and-ESXi/m-p/2933073#M284085</link>
      <description>&lt;P&gt;To those brave ones out there.&amp;nbsp; Please share your experiences.&amp;nbsp; After the disaster of 7.x that ate 16 SD cards in 4 weeks, I am not touching this with a 10 foot pole for quite some time.&amp;nbsp; I need to let vendors catch up and provide support.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Has anyone installed this ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://customerconnect.vmware.com/downloads/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/8_0" target="_blank"&gt;https://customerconnect.vmware.com/downloads/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/8_0&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Oct 2022 17:53:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Who-s-taking-the-plunge-and-going-to-guinea-pig-vCenter-and-ESXi/m-p/2933073#M284085</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2022-10-11T17:53:08Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot export vLCM image if you use a custom SSL cert (Non-Microsoft)</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-export-vLCM-image-if-you-use-a-custom-SSL-cert-Non/m-p/2890728#M92838</link>
      <description>&lt;P&gt;Well have I got some good news for you !&amp;nbsp; After 4 months of having an SR open and many many techs attempting to figure this out, they found out what was happening.&lt;/P&gt;&lt;P&gt;When you export the ISO and it opens a new browser tab (that ends up throwing the error), notice the port it is connecting to is 9084&lt;/P&gt;&lt;P&gt;Change this to 9087 and reload the page and the ISO will start downloading.&amp;nbsp; I tested this in both my vCenters (7.02 and 7.03) and it works fine.&lt;/P&gt;&lt;P&gt;I have no idea why it works out of the box on 9084 if you don't use custom SSL certs, but after this long troubleshooting I'm ok with just changing the port and reloading the page.&amp;nbsp; Let me know if this worked for you as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jan 2022 13:58:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-export-vLCM-image-if-you-use-a-custom-SSL-cert-Non/m-p/2890728#M92838</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2022-01-28T13:58:50Z</dc:date>
    </item>
    <item>
      <title>Re: migrating from vds to vss got error</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/migrating-from-vds-to-vss-got-error/m-p/2887019#M44871</link>
      <description>&lt;P&gt;You cannot migrate from vDS to vSS . You can do it the other way around . Standard -&amp;gt; Distributed&lt;/P&gt;&lt;P&gt;Power off your VM and change the network, then boot it back up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is documented in vSphere Networking manual&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 17:48:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/migrating-from-vds-to-vss-got-error/m-p/2887019#M44871</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2022-01-07T17:48:15Z</dc:date>
    </item>
    <item>
      <title>Re: log4j vulnerability workaround</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/log4j-vulnerability-workaround/m-p/2883651#M44747</link>
      <description>&lt;H3&gt;I have implemented the workaround. After I patch, do I need to roll back the workaround settings?&lt;/H3&gt;&lt;P&gt;Specific instructions will be in the workaround Knowledge Base articles, but in general the answer is no. Patching will roll the product forward and accommodate the workaround.&lt;/P&gt;&lt;P&gt;&lt;A href="https://core.vmware.com/vmsa-2021-0028-questions-answers-faq#sec19130-sub5" target="_blank" rel="noopener"&gt;https://core.vmware.com/vmsa-2021-0028-questions-answers-faq#sec19130-sub5&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Dec 2021 15:22:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/log4j-vulnerability-workaround/m-p/2883651#M44747</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-12-15T15:22:55Z</dc:date>
    </item>
    <item>
      <title>Has anyone applied the LOG4SHELL mitigations for vCenter ?</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Has-anyone-applied-the-LOG4SHELL-mitigations-for-vCenter/m-p/2883043#M92686</link>
      <description>&lt;P&gt;Here is the general advisory&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.vmware.com/security/advisories/VMSA-2021-0028.html" target="_blank"&gt;https://www.vmware.com/security/advisories/VMSA-2021-0028.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are the vCenter 7.x appliance specific steps.&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/87081?lang=en_US" target="_blank"&gt;https://kb.vmware.com/s/article/87081?lang=en_US&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Has anyone applied these yet ? Ideally I prefer to wait for an official patch from VMware&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 13:59:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Has-anyone-applied-the-LOG4SHELL-mitigations-for-vCenter/m-p/2883043#M92686</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-12-13T13:59:25Z</dc:date>
    </item>
    <item>
      <title>Cannot export vLCM image if you use a custom SSL cert (Non-Microsoft)</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-export-vLCM-image-if-you-use-a-custom-SSL-cert-Non/m-p/2881200#M92630</link>
      <description>&lt;P&gt;I have had a ticket open with support for almost 6 weeks now. The issue is :&lt;/P&gt;&lt;P&gt;If you import a custom machine SSL cert (in my case from GoDaddy) to your vCenter, you cannot export any images (either zip, ISO or JSON) from a cluster.&amp;nbsp; It throws the following error&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;H1&gt;&lt;SPAN&gt;This site can’t provide a secure connection&lt;/SPAN&gt;&lt;/H1&gt;&lt;P&gt;&lt;STRONG&gt;test-vcenter.blah.ca&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;sent an invalid response.&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Try running Windows Network Diagnostics.&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;ERR_SSL_PROTOCOL_ERROR&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;The only way I have been able to export images has been to create a new vCenter, let it use the self-signed certificate, then create a dummy cluster with no hosts, create an image and export it.&amp;nbsp; This works just fine.&amp;nbsp; We have a test vCenter plus a prod copy both using unique certs from GoDaddy and both experience same issues (7.02 and 7.03 versions)&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;Support can't seem to figure this out yet.&amp;nbsp; Can someone do me a favor please.&amp;nbsp; If you have a vCenter with a custom SSL cert, can you create a test cluster, create an image and see if it lets you export it ?&amp;nbsp; I'm just curious if this happens with anyone else.&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 02 Dec 2021 17:03:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Cannot-export-vLCM-image-if-you-use-a-custom-SSL-cert-Non/m-p/2881200#M92630</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-12-02T17:03:27Z</dc:date>
    </item>
    <item>
      <title>Re: No Coredump Target Has Been Configured. Host Core Dumps Cannot Be Saved</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/No-Coredump-Target-Has-Been-Configured-Host-Core-Dumps-Cannot-Be/m-p/2881192#M279215</link>
      <description>&lt;P&gt;This is the KB article I use when adding new hosts.&amp;nbsp; Hope this helps&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/2077516" target="_blank"&gt;https://kb.vmware.com/s/article/2077516&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Dec 2021 16:23:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/No-Coredump-Target-Has-Been-Configured-Host-Core-Dumps-Cannot-Be/m-p/2881192#M279215</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-12-02T16:23:22Z</dc:date>
    </item>
    <item>
      <title>Re: Alarm: "Host memory status"</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Alarm-quot-Host-memory-status-quot/m-p/2879305#M279058</link>
      <description>&lt;P&gt;What does the iLO / IML logs show for the memory ? Any issues or are they all active and healthy.&lt;/P&gt;&lt;P&gt;The only other thing I can suggest is to try and install the HPE Customized ESXi ISO .&amp;nbsp; It includes drivers from the vendor.&amp;nbsp; I've always used those images on my G9-G10 servers..&lt;/P&gt;&lt;P&gt;Also check the hardware compatibility guide to make sure your G6 is actually supported by this version of ESXi.&lt;/P&gt;&lt;P&gt;I hope some of this helps you find the cause. Good luck !&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 13:41:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Alarm-quot-Host-memory-status-quot/m-p/2879305#M279058</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-11-22T13:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: Alarm: "Host memory status"</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Alarm-quot-Host-memory-status-quot/m-p/2879301#M279056</link>
      <description>&lt;P&gt;Host memory status does not mean something is wrong with the RAM.&amp;nbsp; It means the ESXi host has consumed more than 80%.&amp;nbsp; When your server is running, what is the total usage of RAM with all your VMs powered on ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's not a problem, just a warning you're getting close to maxing the server out.&amp;nbsp; It will go from yellow to red once you exceed 90% usage&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 13:13:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Alarm-quot-Host-memory-status-quot/m-p/2879301#M279056</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-11-22T13:13:23Z</dc:date>
    </item>
    <item>
      <title>Re: Can't change root password on ESXi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Can-t-change-root-password-on-ESXi-6-7/m-p/2878785#M279003</link>
      <description>&lt;P&gt;Fixed the issue.&amp;nbsp; There was an entire line missing from /etc/pam.d/passwd .&amp;nbsp; No idea how that happened (this is a ESXi built into a Dell IDPA solition I was trying to change password on)&lt;/P&gt;&lt;P&gt;EMC support helped me.&amp;nbsp; We had to add this and then I was able to change the root password right away&lt;/P&gt;&lt;P&gt;# Change only through host advanced option "Security.PasswordQualityControl".&lt;BR /&gt;&lt;STRONG&gt;password requisite /lib/security/$ISA/pam_passwdqc.so retry=3 min=disabled,disabled,disabled,7,7 &lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 14:34:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Can-t-change-root-password-on-ESXi-6-7/m-p/2878785#M279003</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-11-18T14:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: Can't change root password on ESXi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Can-t-change-root-password-on-ESXi-6-7/m-p/2877777#M278931</link>
      <description>&lt;P&gt;This doesn't work. I am SSH in as root.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried to issue the command passwd and specifying the root account yet it still gives this error . Doesn't even give me a chance to enter the new password&lt;/P&gt;&lt;P&gt;passwd root&lt;BR /&gt;Changing password for root&lt;BR /&gt;passwd: Authentication token manipulation error&lt;BR /&gt;passwd:&lt;/P&gt;</description>
      <pubDate>Fri, 12 Nov 2021 17:30:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Can-t-change-root-password-on-ESXi-6-7/m-p/2877777#M278931</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-11-12T17:30:35Z</dc:date>
    </item>
    <item>
      <title>Can't change root password on ESXi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Can-t-change-root-password-on-ESXi-6-7/m-p/2877763#M278927</link>
      <description>&lt;P&gt;The only KB I could find about this refers to the password not being complex enough.&amp;nbsp; The password meets all the criteria.&amp;nbsp; The passwd command doesn't even let me enter the password, it throws this error.&amp;nbsp; I also tried from the web client, same issue.&amp;nbsp; Any idea how to fix this?&lt;/P&gt;&lt;P&gt;[root@xxxx-esxi00:~] passwd&lt;BR /&gt;Changing password for root&lt;BR /&gt;passwd: Authentication token manipulation error&lt;BR /&gt;passwd:&lt;BR /&gt;[root@xxxx-esxi00:~]&lt;/P&gt;</description>
      <pubDate>Fri, 12 Nov 2021 16:51:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Can-t-change-root-password-on-ESXi-6-7/m-p/2877763#M278927</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-11-12T16:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: ESXI not able to update to 7.0.3.00100</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXI-not-able-to-update-to-7-0-3-00100/m-p/2875269#M278729</link>
      <description>&lt;P&gt;You have to specify the full path when using -d switch&lt;/P&gt;&lt;P&gt;-d /full/path/to/package.vib&lt;/P&gt;</description>
      <pubDate>Fri, 29 Oct 2021 12:24:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXI-not-able-to-update-to-7-0-3-00100/m-p/2875269#M278729</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-10-29T12:24:03Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 7.0 U3 Broken</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874276#M44302</link>
      <description>&lt;P&gt;They released vCenter 7.0.3a last week that addresses the Lifecycle Manager issue&lt;/P&gt;</description>
      <pubDate>Mon, 25 Oct 2021 15:48:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-7-0-U3-Broken/m-p/2874276#M44302</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-10-25T15:48:15Z</dc:date>
    </item>
    <item>
      <title>VCSA on vDS - Ephemeral Port Binding Question</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-on-vDS-Ephemeral-Port-Binding-Question/m-p/2873774#M44262</link>
      <description>&lt;P&gt;I an in the process of migrating hosts to a vDS.&amp;nbsp; I have done some reading and it suggests to keep an ephemeral port group on the same vLAN that my vCenter runs on, in case of emergency.&amp;nbsp; My understanding is I could login to the ESXi hosts and add VMs to this network to help get things back up and running.&lt;/P&gt;&lt;P&gt;What I don't understand is :&lt;/P&gt;&lt;P&gt;1: Can I migrate the VCSA directly to the vDS port group or should I move it to the ephemeral one ?&lt;/P&gt;&lt;P&gt;2: Is the ephemeral port group to be used only in emergency or should the VCSA reside there permanent ?&lt;/P&gt;&lt;P&gt;I have not had a single problem migrating VMKernel and VM workloads to the vDS so far. Some folks seemed to lose connectivity to the VCSA once migrating from VSS to VDS so I dug a bit deeper and found the ephemeral port group option.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Oct 2021 12:51:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-on-vDS-Ephemeral-Port-Binding-Question/m-p/2873774#M44262</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-10-22T12:51:36Z</dc:date>
    </item>
    <item>
      <title>vDS + iSCSI Design Question / Best Practice</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vDS-iSCSI-Design-Question-Best-Practice/m-p/2870766#M40393</link>
      <description>&lt;P&gt;We have 10 hosts , each with 4 x 10GBe cards in them. We use Dell EMC SC series Arrays (one per DC)&lt;/P&gt;&lt;P&gt;2 Adapters are teamed with an MTU of 1500 running management and VM vLans and vMotion&lt;/P&gt;&lt;P&gt;1 Adapter goes to 1st iSCSI subnet - MTU 9000&lt;/P&gt;&lt;P&gt;1 Adapter goes to 2nd iSCSI subnet - MTU 9000&lt;/P&gt;&lt;P&gt;The 2 clusters are spread across 2 datacenters, but share the same IP space.&lt;/P&gt;&lt;P&gt;The only difference is site A tags the vLAN for iSCSI traffic and site B does not pass vLAN tags&lt;/P&gt;&lt;P&gt;My question is as follows :&lt;/P&gt;&lt;P&gt;I wish to migrate to vDS in part because it is now required for Tanzu on vSphere. Would it be better to create one dVS using 2 x 10GBe adapters for all management and VM traffic and leave the iSCSI traffic on standard switches&amp;nbsp;&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;Create 1 dVS for management + vMotion + vLAN traffic (MTU 1500)&lt;/P&gt;&lt;P&gt;Create 1 dVS for iSCSI (MTU 9000) however, create 4 port groups. 2 tagged for the iSCSI vLAN for site A and 2 without tags for site B.&lt;/P&gt;&lt;P&gt;It has been many years since i've had to do a migration to dVS and am not quite up to speed on what is best these days.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Oct 2021 21:40:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vDS-iSCSI-Design-Question-Best-Practice/m-p/2870766#M40393</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-10-07T21:40:20Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 7 - vCenter Server health is GREEN vc.health.error.dbjob3</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-7-vCenter-Server-health-is-GREEN-vc-health-error-dbjob3/m-p/2870473#M44131</link>
      <description>&lt;P&gt;Problem disappeared this morning. Logged into the VC appliance and the status is gone. It looks like it was some performance statistics from what i could find.&amp;nbsp; No idea but am happy this wasn't a big deal.&lt;/P&gt;&lt;P&gt;If anyone else gets this, wait 24h and see if it goes away on its own&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2021 12:29:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-7-vCenter-Server-health-is-GREEN-vc-health-error-dbjob3/m-p/2870473#M44131</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-10-06T12:29:01Z</dc:date>
    </item>
    <item>
      <title>vCenter 7 - vCenter Server health is GREEN vc.health.error.dbjob3</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-7-vCenter-Server-health-is-GREEN-vc-health-error-dbjob3/m-p/2870351#M44127</link>
      <description>&lt;P&gt;I was running 7.0.2Ud - 0500 on this machine. It was never rebooted since the upgrade from 0400&lt;/P&gt;&lt;P&gt;When i patched to 7.0U3, it now shows this in the server appliance under VMware vCenter Server&amp;nbsp;&lt;/P&gt;&lt;DIV class="ng-star-inserted"&gt;vCenter Server health is GREEN&lt;/DIV&gt;&lt;DIV class="ng-star-inserted"&gt;vc.health.error.dbjob&lt;/DIV&gt;&lt;DIV class="ng-star-inserted"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="ng-star-inserted"&gt;I thought it was an error with the upgrade so i rolled back and restored from backup back to 7.02Ud 0500 and it still shows this now.&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="ng-star-inserted"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="ng-star-inserted"&gt;The vCenter UI now shows vCenter Server Health Alarm&lt;/DIV&gt;&lt;DIV class="ng-star-inserted"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="ng-star-inserted"&gt;Any ideas how i can resolve this now ?&lt;/DIV&gt;</description>
      <pubDate>Tue, 05 Oct 2021 19:44:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-7-vCenter-Server-health-is-GREEN-vc-health-error-dbjob3/m-p/2870351#M44127</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-10-05T19:44:35Z</dc:date>
    </item>
    <item>
      <title>ESXI 7.0U3 is out as of today</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXI-7-0U3-is-out-as-of-today/m-p/2870308#M278323</link>
      <description>&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-703-release-notes.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-703-release-notes.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I don't see the update available in the appliance update section. Does anyone see it ? I wonder if they haven't published it yet. Lifecycle Manager already has the image for ESXi 7.0U3&lt;/P&gt;</description>
      <pubDate>Tue, 05 Oct 2021 16:02:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXI-7-0U3-is-out-as-of-today/m-p/2870308#M278323</guid>
      <dc:creator>mbartle</dc:creator>
      <dc:date>2021-10-05T16:02:35Z</dc:date>
    </item>
  </channel>
</rss>

