<?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>sbd27 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>sbd27 Tracker</description>
    <pubDate>Sat, 25 Nov 2023 06:45:48 GMT</pubDate>
    <dc:date>2023-11-25T06:45:48Z</dc:date>
    <item>
      <title>Re: VRMS log4j workaround broke the UI</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883135#M3524</link>
      <description>&lt;P&gt;So I updated to 8.4.0.3 and the UI came back, however, I assume the log4j issue is back. Oh well, I guess I'll wait for a patch and cross my fingers.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 18:32:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883135#M3524</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-12-13T18:32:28Z</dc:date>
    </item>
    <item>
      <title>Re: VRMS log4j workaround broke the UI</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883122#M3523</link>
      <description>&lt;P&gt;I guess I should be more specific. The Site Recovery UI is now broken with a 404-Not Found error.&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/" target="_blank"&gt;https://&amp;lt;sitemanager&amp;gt;/dr&lt;/A&gt;&amp;nbsp;returns a HTTP - 404 - Site not Found&lt;/P&gt;&lt;P&gt;Just wondering id anyone else implemented the workaround.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 17:47:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883122#M3523</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-12-13T17:47:26Z</dc:date>
    </item>
    <item>
      <title>VRMS log4j workaround broke the UI</title>
      <link>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883113#M3522</link>
      <description>&lt;P&gt;After implementing the workaround to mitigate the log4j issue my VRMS replication manager interface is now broke with a 404 error:&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/87098" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/87098&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone else seeing this?&lt;/P&gt;&lt;P&gt;Running 8.4&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 17:14:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Replication-Discussions/VRMS-log4j-workaround-broke-the-UI/m-p/2883113#M3522</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-12-13T17:14:35Z</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/2865011#M277822</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/133911"&gt;@A13x&lt;/a&gt;&amp;nbsp; Almost my entire environment has diskless server configurations from Dell (you know the parent company of VMWare). So, my Servers do not have PERC or Disk Cages, and some are R730s that do not support BOSS cards. Dell also does not support installing PERCs into servers that came from the factory without them.&lt;/P&gt;&lt;P&gt;So, now my VMWare upgrade which should have had almost zero cost is now costing me over $100k because I need to replace the R730 hosts and purchase new BOSS cards.&lt;/P&gt;&lt;P&gt;Also, BOSS cards have a 90-day turnaround right now.&lt;/P&gt;&lt;P&gt;And by the way, I have never had to do a complete host rebuild to do an upgrade.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Sep 2021 17:17:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2865011#M277822</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-09-02T17:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter High disk I/O after 7.0.2 update</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-High-disk-I-O-after-7-0-2-update/m-p/2858239#M43637</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/24614"&gt;@depping&lt;/a&gt;&amp;nbsp;That was it! Sorry for the long turn around in my response, because I was working with VMWare support and not getting far. I finally started &lt;STRIKE&gt;pruning&lt;/STRIKE&gt;&amp;nbsp;truncating the event tables (vpx_event_* and vpx_event_args_*) and the I/O finally dropped down to more normal sub 1Mbps!&lt;/P&gt;&lt;P&gt;All other resource indicators dropped too.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jul 2021 19:37:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-High-disk-I-O-after-7-0-2-update/m-p/2858239#M43637</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-07-19T19:37:37Z</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/2857900#M277032</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/2706223"&gt;@PatrickDLong&lt;/a&gt;&amp;nbsp;So you are correct. I would not recommend replacing any current embedded ESXi solution mainly because, at least with Dell, you can't! When you purchase a diskless server from Dell without a Perc card and drive cages, they do not support installing them afterwards, you are stuck.&lt;/P&gt;&lt;P&gt;What makes matters even worse for me (and I have to assume other customers) is that I have some R730s that are diskless with only the IDSDM solution, and the R730 (which is still an ESXi supported server) does not support the BOSS card . If this fix does not work I have to replace servers I did not budget for in my upgrade project.&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, all new servers that I purchase will not longer utilize a diskless config. I can easily have a non-technical person replace a bad swappable SSD RAID drive, but replacing a BOSS card or its attached SSD requires downtime and opening the hood of the server. No Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 17:16:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2857900#M277032</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-07-16T17:16: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/2857849#M277022</link>
      <description>&lt;P&gt;I guess Dell finally got their hooks into how VMWare does business. This should be a zero-day-tier1 issue. 7.0 Update 1 and 2 should have been taken down from VMWare's downloads when this problem first creeped up. The maddening part is how VMWare seems to act like this is low tier issue. I had promised my Management Team that the VMWare 7.0 upgrade project would have been completed by April 2021, its now July and I'm only 1/3 of the way done!&lt;/P&gt;&lt;P&gt;And my TAMs solution... "Can you rollback to 6.7?" WHAT? Sure lets just waste a ton of man hours getting to where I am today because VMWare is treating this like a 3rd level bug.&lt;/P&gt;&lt;P&gt;Also, the embedded VMWare solutions are horrible (at least Dell's IDSDMs and BOSS cards ) they are not really redundant and are impossible to manage. When this issue killed one of my hosts, I tried to reinstall and the reinstalls still failed, even though the iDRAC says both cards are "Online" and since SD Cards don't really re-format themselves. I had to swap the SD cards around, and then the host booted up to version of 7.0 that was months old!&lt;/P&gt;&lt;P&gt;I have now recommended to my Management Team, and I advise everyone reading this to do the same, to no longer used embedded ESXi solutions and buy servers with RAID cards with &lt;STRIKE&gt;RAID0&lt;/STRIKE&gt; (sorry I of course meant RAID1) mirrored SSD disks. The cost difference is about 1%.&lt;/P&gt;&lt;P&gt;I really hope this update comes out soon and resolves this issue, it has really put me in a bad spot.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 14:31:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2857849#M277022</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-07-16T14:31:36Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter High disk I/O after 7.0.2 update</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-High-disk-I-O-after-7-0-2-update/m-p/2855387#M43489</link>
      <description>&lt;P&gt;No, but&lt;/P&gt;&lt;P&gt;I have dug a little deeper. Llooks like something it reading the heck out of my SEAT db&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sbd27_1-1625153145034.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89821i54FD905ECCFF305F/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="sbd27_1-1625153145034.png" alt="sbd27_1-1625153145034.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sbd27_2-1625153322470.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89822iE4451BDDF3FA8449/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="sbd27_2-1625153322470.png" alt="sbd27_2-1625153322470.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sdh is the disk that holds the SEAT filesystem. I though maybe it was our monitoring software, but I disabled it and nothing. Does anyone know how to dive into postgres and get info on where these reads are coming from?&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jul 2021 15:29:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-High-disk-I-O-after-7-0-2-update/m-p/2855387#M43489</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-07-01T15:29:12Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter High disk I/O after 7.0.2 update</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-High-disk-I-O-after-7-0-2-update/m-p/2855192#M43478</link>
      <description>&lt;P&gt;I also have a separate vCenter that is much smaller then this one (only 4&amp;nbsp; cluster and about 10 hosts), and like you said it does not have the same issues. The vCenter that is seeing this issue has close to 60 hosts and 8 different clusters.&lt;/P&gt;&lt;P&gt;I plan to reach out to VMWare today.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jun 2021 12:40:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-High-disk-I-O-after-7-0-2-update/m-p/2855192#M43478</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-06-30T12:40:53Z</dc:date>
    </item>
    <item>
      <title>vCenter High disk I/O after 7.0.2 update</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-High-disk-I-O-after-7-0-2-update/m-p/2855098#M43476</link>
      <description>&lt;P&gt;After updating vCenter from 7.0.1 to 7.0.2 build&amp;nbsp;&lt;SPAN&gt;17958471,&amp;nbsp; Disk I/O on the appliance went from about 1k avg to now around 75k. The jump was so severe my Storage Team had to bring it to my attention as total I/O on our Pure SAN jumped almost 10%!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have&amp;nbsp;also noticed CPU and Memory resource utilization have drastically&amp;nbsp;increased above their normal average. Look at the chart below and you can see when&amp;nbsp;the update occurred. Rebooting the VCA did not help. Anybody else seeing anything like this?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sbd27_0-1625017190310.png" style="width: 529px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/89785i772614B8F692A90F/image-dimensions/529x240/is-moderation-mode/true?v=v2" width="529" height="240" role="button" title="sbd27_0-1625017190310.png" alt="sbd27_0-1625017190310.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jun 2021 01:43:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-High-disk-I-O-after-7-0-2-update/m-p/2855098#M43476</guid>
      <dc:creator>sbd27</dc:creator>
      <dc:date>2021-06-30T01:43:53Z</dc:date>
    </item>
  </channel>
</rss>

