<?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>MarkSen Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>MarkSen Tracker</description>
    <pubDate>Thu, 23 Nov 2023 17:32:15 GMT</pubDate>
    <dc:date>2023-11-23T17:32:15Z</dc:date>
    <item>
      <title>Re: Unable to Upgrade NSX-T 3.2.1 to 3.2.2 becuase vLCM failing NSXT health checks</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Unable-to-Upgrade-NSX-T-3-2-1-to-3-2-2-becuase-vLCM-failing-NSXT/m-p/2967326#M16395</link>
      <description>&lt;P&gt;Thanks for the reply! I did figure it out. For anyone that swings back this way, the solution for me was a bad SSL certificate in one of the vCenter services. So, when it was saying it failed to do the health check, the translation was that NSX Manager was unable to communicate with vCenter and the vLCM in a trusted manner and the connection was being aborted. Updated the thumbprint in NSX and boom, all gravy.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2023 15:17:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Unable-to-Upgrade-NSX-T-3-2-1-to-3-2-2-becuase-vLCM-failing-NSXT/m-p/2967326#M16395</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2023-05-08T15:17:39Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Upgrade NSX-T 3.2.1 to 3.2.2 becuase vLCM failing NSXT health checks</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Unable-to-Upgrade-NSX-T-3-2-1-to-3-2-2-becuase-vLCM-failing-NSXT/m-p/2967303#M16392</link>
      <description>&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;Did you ever find a solution to this by chance? Running into the same thing, though not specific to an NSX-T update but simply overall vLCM operations. Real PITA.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2023 14:44:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Unable-to-Upgrade-NSX-T-3-2-1-to-3-2-2-becuase-vLCM-failing-NSXT/m-p/2967303#M16392</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2023-05-08T14:44:27Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN ISCSI Target 6.5 OS support List ( AIX servers )</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-ISCSI-Target-6-5-OS-support-List-AIX-servers/m-p/2234416#M8656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I remember correctly also, IBMs implementation of iSCSI in AIX is very ... fundamental. Meaning, they don't have instructions available to support the entire protocol stack. Last time I dealt with this question, the implementation had a scale-out storage architecture similar to vsan in many ways. There would be a single IP for the cluster to represent storage connectivity operations, with iSCSI commands leveraged to tell endpoints which nodes to connect to for preferred vs secondary data, alert for data movement, etc. AIX did not fully support the iSCSI redirects required to make this all work, and IBM had no intention of updating the stack (at the time). This was about 3 years ago, so may have changed! &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Jun 2019 11:49:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-ISCSI-Target-6-5-OS-support-List-AIX-servers/m-p/2234416#M8656</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2019-06-20T11:49:21Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere 6.0U3 EAM Error</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vSphere-6-0U3-EAM-Error/m-p/1756320#M22386</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By any chance, do you remember what you ended up doing to resolve the issue? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Oct 2017 19:25:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vSphere-6-0U3-EAM-Error/m-p/1756320#M22386</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2017-10-31T19:25:45Z</dc:date>
    </item>
    <item>
      <title>Re: VCAP6-DCV Deploy + VCAP6.5-DCV Design = ?</title>
      <link>https://communities.vmware.com/t5/VCAP-VMware-Certified-Advanced/VCAP6-DCV-Deploy-VCAP6-5-DCV-Design/m-p/1412686#M2536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This fulfills the VCIX6.5 requirements, per Karl Childs. It won't reflect until they have released a 6.5 Deploy, or if the vendor that manages the badges adjusts the logic to show it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no ETA on either of those items. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Oct 2017 16:22:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VCAP-VMware-Certified-Advanced/VCAP6-DCV-Deploy-VCAP6-5-DCV-Design/m-p/1412686#M2536</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2017-10-31T16:22:34Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Types plug-in generator package</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Dynamic-Types-plug-in-generator-package/tac-p/2772353#M179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ah yes, exactly it. I should've caught that. Will keep going from here &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Apr 2015 20:28:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Dynamic-Types-plug-in-generator-package/tac-p/2772353#M179</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2015-04-02T20:28:59Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Types plug-in generator package</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Dynamic-Types-plug-in-generator-package/tac-p/2772351#M177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Attempting to use v2 - can't seem to get v1 loaded into vRO6 to compare. Basically when attempting to run Plugin gen -1- Create new plug-in workflow, it fails inside of the vRO client without any fanfare. Inside of vSphere web client, the following notification is logged: "TypeError: Cannot call method "getResourceElementCategory" of null (Workflow:Define Type / Define Type (item4)#7)" A Dynamic Type with no properties gets created inside of the Inventory. I may need to setup a different environment with just 5.5 to compare and make sure it isn't user error, but let me know what you think. &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Apr 2015 14:10:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Dynamic-Types-plug-in-generator-package/tac-p/2772351#M177</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2015-04-01T14:10:29Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic Types plug-in generator package</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Dynamic-Types-plug-in-generator-package/tac-p/2772349#M175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are there any particular known issues with the most recently posted version running on vRO 6.0.1? Been struggling to get this to even get into defining the host past step 1, and it seems to be due to some issue crossing between the custom plug-in generator and the library itself (unless it's just me). It appears to generate the new namespace, but then fail when attempting to launch into defining the host/type. If there are no expected issues, I can post elsewhere to seek help so as not to derail the thread. Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Apr 2015 12:40:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Dynamic-Types-plug-in-generator-package/tac-p/2772349#M175</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2015-04-01T12:40:49Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere 6 Release Date ?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-6-Release-Date/m-p/1309165#M119068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;in case the question is still outstanding... today! available for download in my.vmware &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Mar 2015 15:34:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-6-Release-Date/m-p/1309165#M119068</guid>
      <dc:creator>MarkSen</dc:creator>
      <dc:date>2015-03-12T15:34:07Z</dc:date>
    </item>
  </channel>
</rss>

