<?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>salarmehdizadeh Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>salarmehdizadeh Tracker</description>
    <pubDate>Thu, 23 Nov 2023 13:47:08 GMT</pubDate>
    <dc:date>2023-11-23T13:47:08Z</dc:date>
    <item>
      <title>Re: NSX-T 3.1 renew self signed certificates</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-3-1-renew-self-signed-certificates/m-p/2951856#M16009</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;1. Can we extend the duration of an expired certificate?&lt;BR /&gt;2. You advised entering SAN (VIP and three manager nodes with FQDN) for a certificate, but in the CSR generating process we only can enter the Common name, there is no section for entering SAN?&lt;/P&gt;</description>
      <pubDate>Wed, 01 Feb 2023 08:01:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-3-1-renew-self-signed-certificates/m-p/2951856#M16009</guid>
      <dc:creator>salarmehdizadeh</dc:creator>
      <dc:date>2023-02-01T08:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: NSX-T 3.2 on vSphere 7u3c Hugepage issues on Edge VMs.</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-3-2-on-vSphere-7u3c-Hugepage-issues-on-Edge-VMs/m-p/2946916#M15896</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Based on VMware support advice, we migrate EDGE VMs to another cluster where EVC was disabled there and the issue was resolved and we could proceed with the Upgrade process as well.&lt;/P&gt;&lt;P&gt;I hope that it works for you.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jan 2023 11:16:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-3-2-on-vSphere-7u3c-Hugepage-issues-on-Edge-VMs/m-p/2946916#M15896</guid>
      <dc:creator>salarmehdizadeh</dc:creator>
      <dc:date>2023-01-05T11:16:27Z</dc:date>
    </item>
    <item>
      <title>Re: AVI Load Balancer routed pools</title>
      <link>https://communities.vmware.com/t5/Networking-Members/AVI-Load-Balancer-routed-pools/m-p/2940866#M246</link>
      <description>&lt;P&gt;I think that the answer is ROUTING.&lt;/P&gt;&lt;P&gt;your SEs must have reachability to your pools. it will be done by selecting the appropriate network on the vCenter cloud inside NSX ALB SEG (Network Tab) and also defining a specific route or default route for SEs.&lt;/P&gt;&lt;P&gt;if you use NSX cloud, T1 has to have a route advertisement to T0, and also T0 must have route to your physical side.&lt;/P&gt;&lt;P&gt;if you use vCenter cloud, under NSX ALB &amp;gt; Infrustracture &amp;gt; cloud resources &amp;gt; routing&lt;/P&gt;&lt;P&gt;select your cloud and define a static route if you do not use Dynamic routing.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="salarmehdizadeh_0-1669486618757.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/98565i76A37D432843EE34/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="salarmehdizadeh_0-1669486618757.png" alt="salarmehdizadeh_0-1669486618757.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>Sat, 26 Nov 2022 18:18:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/AVI-Load-Balancer-routed-pools/m-p/2940866#M246</guid>
      <dc:creator>salarmehdizadeh</dc:creator>
      <dc:date>2022-11-26T18:18:16Z</dc:date>
    </item>
    <item>
      <title>Re: NSX-T + Cloud director + shared external subnet between 2 locations</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Cloud-director-shared-external-subnet-between-2-locations/m-p/2928809#M15431</link>
      <description>&lt;P&gt;&lt;STRONG&gt;hi,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;I think that it's NOT a good idea to announce your External IP from more than one site. (it means you can't use an A/A site with the same Ext IP). at the standby site, you should append some data to BGP to use it as a secondary path.&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 10:02:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-Cloud-director-shared-external-subnet-between-2-locations/m-p/2928809#M15431</guid>
      <dc:creator>salarmehdizadeh</dc:creator>
      <dc:date>2022-09-14T10:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: NSX-T 3.2 on vSphere 7u3c Hugepage issues on Edge VMs.</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-3-2-on-vSphere-7u3c-Hugepage-issues-on-Edge-VMs/m-p/2894513#M14377</link>
      <description>&lt;P&gt;I have the same issue in the NSX Upgrading process from version 3.1.3.1 to 3.2.2 in EDGE nodes Upgrade stage.&lt;/P&gt;&lt;P&gt;I edited the EDGE VM advance feature to "&lt;SPAN&gt;featMask.vm.cpuid.pdpe1gb: Val:1" based on VMware kb&lt;BR /&gt;but, because of EVC is enabled on Cluster, it does NOT take effect for me.&lt;BR /&gt;the suggestion was about disabling the EVC but in a production environment, will disable EVC has a negative impact?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Dec 2022 18:19:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-3-2-on-vSphere-7u3c-Hugepage-issues-on-Edge-VMs/m-p/2894513#M14377</guid>
      <dc:creator>salarmehdizadeh</dc:creator>
      <dc:date>2022-12-27T18:19:53Z</dc:date>
    </item>
  </channel>
</rss>

