<?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>pras23ps Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>pras23ps Tracker</description>
    <pubDate>Thu, 23 Nov 2023 13:51:22 GMT</pubDate>
    <dc:date>2023-11-23T13:51:22Z</dc:date>
    <item>
      <title>Re: NSX-T Service Deployments</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Service-Deployments/m-p/2958461#M16165</link>
      <description>&lt;P&gt;We need to check the transport node profile which is attached to NSX-T cluster and see if the VLAN transport zone is part of it or not. I had faced same issue recently and that profile which was attached to cluster was not added with VLAN TZ. Once it was added we were able to deply the service.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Mar 2023 16:31:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Service-Deployments/m-p/2958461#M16165</guid>
      <dc:creator>pras23ps</dc:creator>
      <dc:date>2023-03-14T16:31:14Z</dc:date>
    </item>
    <item>
      <title>NSX-T Service Deployment for Network Introspection</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Service-Deployment-for-Network-Introspection/m-p/2958459#M16164</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi&amp;nbsp; Team, Have a query related to service deployment for network introspection on NSX-T. In that we create a service segment and using it we deploy service instance and the deployed service instances hardening is completed on the third party device. Now if we want to change service segment name will it affect the deployed service instances and the hardening done on the third party device. If any one can guide me on this and provide documents if any. that will be really appreciated. thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 09:20:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Service-Deployment-for-Network-Introspection/m-p/2958459#M16164</guid>
      <dc:creator>pras23ps</dc:creator>
      <dc:date>2023-03-09T09:20:38Z</dc:date>
    </item>
    <item>
      <title>NSX-T Service Deployment for Network Intrspection</title>
      <link>https://communities.vmware.com/t5/Networking-Members/NSX-T-Service-Deployment-for-Network-Intrspection/m-p/2958458#M273</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi&amp;nbsp; Team, Have a query related to service deployment for network introspection on NSX-T. In that we create a service segment and using it we deploy service instance and the deployed service instances hardening is completed on the third party device. Now if we want to change service segment name will it affect the deployed service instances and the hardening done on the third party device. If any one can guide me on this and provide documents if any. that will be really appreciated. thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2023 09:18:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/NSX-T-Service-Deployment-for-Network-Intrspection/m-p/2958458#M273</guid>
      <dc:creator>pras23ps</dc:creator>
      <dc:date>2023-03-09T09:18:52Z</dc:date>
    </item>
    <item>
      <title>NSX-T Security Group Creation via API</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Security-Group-Creation-via-API/m-p/2942204#M15776</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I am working on one of the environment, were we are doing lift and shift migration of NSX-T 3.0 to 3.2. My query is can we export the security groups from old NSX-T(3.0) and import it in to new NSX-T (3.2) via API. Can any one help me how can we create a script which will create security groups on new NSX-T and then only i can migrate the workloads (VMs) under new NSX-T. With postman from old NSX-T i have got the security groups, now i need to push it to new NSX-T. It will be really great help if any one can assist me creating the security groups via automation or scripting. thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 05 Dec 2022 16:29:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Security-Group-Creation-via-API/m-p/2942204#M15776</guid>
      <dc:creator>pras23ps</dc:creator>
      <dc:date>2022-12-05T16:29:05Z</dc:date>
    </item>
    <item>
      <title>Not able to add the removed NSX-T Local Manager back to Global Manager</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Not-able-to-add-the-removed-NSX-T-Local-Manager-back-to-Global/m-p/2919478#M14990</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;For some reason i had to remove the local manager(LM) from global which i did by following the pre-requisites i.e. global manager(GM) realted configuration done on LM were removed manually and then LM was removed from GM succesfully.&lt;/P&gt;&lt;P&gt;The issue what i am facing is that when i am trying to add LM back to GM, I am geting error "Error: Site &amp;lt;site-name&amp;gt; offboarding is not completed. (Error code: 530028)&amp;nbsp; further to troubleshoot i see on LM the default segment profile and default VPN profiles still listed of GM. I have restarted the LM controllers to see if it helps,however no luck.Need to know how can we fix it. Screen shot attached for reference. Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2022 08:28:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Not-able-to-add-the-removed-NSX-T-Local-Manager-back-to-Global/m-p/2919478#M14990</guid>
      <dc:creator>pras23ps</dc:creator>
      <dc:date>2022-07-20T08:28:25Z</dc:date>
    </item>
  </channel>
</rss>

