<?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>topic Re: NSXV LS to NSX-T Segment in Networking Members</title>
    <link>https://communities.vmware.com/t5/Networking-Members/NSXV-LS-to-NSX-T-Segment/m-p/2918332#M190</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It all depends on what all configuration changes/modification you have to do after the network cut-over like route advertisement (on T1) &amp;amp; route redistribution (on T0).&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Jul 2022 12:00:50 GMT</pubDate>
    <dc:creator>ShahabKhan</dc:creator>
    <dc:date>2022-07-12T12:00:50Z</dc:date>
    <item>
      <title>NSXV LS to NSX-T Segment</title>
      <link>https://communities.vmware.com/t5/Networking-Members/NSXV-LS-to-NSX-T-Segment/m-p/2918298#M185</link>
      <description>&lt;P&gt;Dear Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once we disconnect NSXV LS and connect corresponding NSX-T Segment, then how much time it take to advertise NSX-T Segment and communication will resume from NSX-T&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MrVmware9423_0-1657613391463.png" style="width: 400px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/96173i97AC60CB44F44B65/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="MrVmware9423_0-1657613391463.png" alt="MrVmware9423_0-1657613391463.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2022 08:17:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/NSXV-LS-to-NSX-T-Segment/m-p/2918298#M185</guid>
      <dc:creator>MrVmware9423</dc:creator>
      <dc:date>2022-07-12T08:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: NSXV LS to NSX-T Segment</title>
      <link>https://communities.vmware.com/t5/Networking-Members/NSXV-LS-to-NSX-T-Segment/m-p/2918332#M190</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It all depends on what all configuration changes/modification you have to do after the network cut-over like route advertisement (on T1) &amp;amp; route redistribution (on T0).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2022 12:00:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/NSXV-LS-to-NSX-T-Segment/m-p/2918332#M190</guid>
      <dc:creator>ShahabKhan</dc:creator>
      <dc:date>2022-07-12T12:00:50Z</dc:date>
    </item>
    <item>
      <title>Re: NSXV LS to NSX-T Segment</title>
      <link>https://communities.vmware.com/t5/Networking-Members/NSXV-LS-to-NSX-T-Segment/m-p/2920175#M206</link>
      <description>&lt;P&gt;You could also expedite this at L2 by clearing your ARP cache(s).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For L3, it will be entirely dependent on timers/hello intervals.etc. if you are using dynamic routing. Static routing should be immediate (pursuant to L2 ARP caching as above)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Jul 2022 19:03:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/NSXV-LS-to-NSX-T-Segment/m-p/2920175#M206</guid>
      <dc:creator>frennzyb</dc:creator>
      <dc:date>2022-07-23T19:03:11Z</dc:date>
    </item>
  </channel>
</rss>

