<?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>frennzyb Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>frennzyb Tracker</description>
    <pubDate>Thu, 23 Nov 2023 13:54:57 GMT</pubDate>
    <dc:date>2023-11-23T13:54:57Z</dc:date>
    <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>
    <item>
      <title>Re: Mutiple Physical NIC on ESXI</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/Mutiple-Physical-NIC-on-ESXI/m-p/2915955#M14541</link>
      <description>&lt;P&gt;Neither of those are Class Bs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Classful networks don't have masks/prefixes. They can't, by definition.&lt;/P&gt;</description>
      <pubDate>Sun, 26 Jun 2022 01:55:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/Mutiple-Physical-NIC-on-ESXI/m-p/2915955#M14541</guid>
      <dc:creator>frennzyb</dc:creator>
      <dc:date>2022-06-26T01:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: VMWARE ESXi 7.0 hosts cannot communicate on same vlan but can to vlans</title>
      <link>https://communities.vmware.com/t5/Networking-Members/VMWARE-ESXi-7-0-hosts-cannot-communicate-on-same-vlan-but-can-to/m-p/2909337#M142</link>
      <description>&lt;P&gt;Do you have PVLANs setup anywhere?&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 02:50:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/VMWARE-ESXi-7-0-hosts-cannot-communicate-on-same-vlan-but-can-to/m-p/2909337#M142</guid>
      <dc:creator>frennzyb</dc:creator>
      <dc:date>2022-05-17T02:50:53Z</dc:date>
    </item>
  </channel>
</rss>

