<?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>bmcb555 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>bmcb555 Tracker</description>
    <pubDate>Fri, 10 Nov 2023 23:09:00 GMT</pubDate>
    <dc:date>2023-11-10T23:09:00Z</dc:date>
    <item>
      <title>Re: Packer is complaining that vcenter_server.com/sdk is not accessible</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Packer-is-complaining-that-vcenter-server-com-sdk-is-not/m-p/2991705#M46294</link>
      <description>&lt;P&gt;The SDK uses the vSphere APIs so HTTP/HTTPs via SOAP. Is the account you're using unlocked and has the correct permission?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2023 22:26:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Packer-is-complaining-that-vcenter-server-com-sdk-is-not/m-p/2991705#M46294</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-10-18T22:26:26Z</dc:date>
    </item>
    <item>
      <title>Re: Remove IPv6 Configuration on NSX Managers</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Remove-IPv6-Configuration-on-NSX-Managers/m-p/2991704#M17004</link>
      <description>&lt;P&gt;Unfortunately the only method I know is to redeploy in a rolling fashion. If you've not integrated yet with vCenter it might be quicker just to tear down and rebuild. I hope you get a more satisfactory answer&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2023 22:08:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Remove-IPv6-Configuration-on-NSX-Managers/m-p/2991704#M17004</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-10-18T22:08:11Z</dc:date>
    </item>
    <item>
      <title>Re: Vcenter stopped working</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vcenter-stopped-working/m-p/2989996#M49523</link>
      <description>&lt;P&gt;If you've edited the file it might be worth giving the resolver services a kick&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;systemctl restart systemd-resolved&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;systemctl restart dnsmasq&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Could you also share the host file with the IP addressing blanked out?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 15:18:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vcenter-stopped-working/m-p/2989996#M49523</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-10-06T15:18:45Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple vDS with same uplink</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/Multiple-vDS-with-same-uplink/m-p/2987752#M14783</link>
      <description>&lt;P&gt;You cannot share vmnics with multiple vDS, however, depending on your vendor you can use the same physical uplink, create multiple virtual vmnics that map to the same physical uplink. These will be presented to the ESXi host as multiple vmnics which in turn can be used to create multiple vDS with.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm aware that Cisco FIs can do the above, your vendor may very. If you're equipment isn't able to do this sort of setup then you'll have to have everything on the same vDS assuming they need network access.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2023 08:09:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/Multiple-vDS-with-same-uplink/m-p/2987752#M14783</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-22T08:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall vlan segment supervision</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/Firewall-vlan-segment-supervision/m-p/2987606#M16923</link>
      <description>&lt;P&gt;It'll need more licensing but you can use VRNI for what you're trying to accomplish.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vrealize/vmw-vrni-solution-brief.pdf" target="_blank"&gt;https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vrealize/vmw-vrni-solution-brief.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You add your NSX Managers + vCenters to the VRNI and it gathers the flow information much the same way as nsx intelligence. It'll then report back to you what rules are being hit based on how you build the search criteria. It requires two VMs to function&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 13:11:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/Firewall-vlan-segment-supervision/m-p/2987606#M16923</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-21T13:11:02Z</dc:date>
    </item>
    <item>
      <title>Re: Access data from a possibly corrupt vdmk delta file</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Access-data-from-a-possibly-corrupt-vdmk-delta-file/m-p/2987585#M290196</link>
      <description>&lt;P&gt;I'd something similar in a cyber attack and was able to get the data off the disks following the below&lt;/P&gt;&lt;P&gt;&lt;A href="https://enes.dev/" target="_blank"&gt;https://enes.dev/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Now the guide is for recovering off flat files but you can follow the process from "&lt;SPAN&gt;06/02/2023 - UPDATE!" Guides you through mounting using the software and pulling it off.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 11:48:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Access-data-from-a-possibly-corrupt-vdmk-delta-file/m-p/2987585#M290196</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-21T11:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: Problem transferring VM OVF from 4.1 to 6.7, missing /dev entries</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-transferring-VM-OVF-from-4-1-to-6-7-missing-dev-entries/m-p/2987583#M290195</link>
      <description>&lt;P&gt;Sounds like something went on in the export. Maybe give the converter a try in standalone mode?&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.vmware.com/de/products/converter.html" target="_blank"&gt;https://www.vmware.com/de/products/converter.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 11:39:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Problem-transferring-VM-OVF-from-4-1-to-6-7-missing-dev-entries/m-p/2987583#M290195</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-21T11:39:37Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN Data at Rest Encryption and KMS Failure</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-Data-at-Rest-Encryption-and-KMS-Failure/m-p/2985878#M15583</link>
      <description>&lt;P&gt;I don't believe there is anything more detailed than that there is however a very good session (again old) on how KMS operates and it hasn't functionally changed as fair as I'm aware.&lt;/P&gt;&lt;P&gt;I've cut into the section you will be interested in.&lt;/P&gt;&lt;P&gt;&lt;A href="https://youtu.be/I5gR_dVqfz0?t=653" target="_blank"&gt;https://youtu.be/I5gR_dVqfz0?t=653&lt;/A&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;What happens if vCenter is offline/ failed?&lt;UL&gt;&lt;LI&gt;Depends, on boot the hosts are given the keys by vCenter. The keys are stored in ESXi memory so as long as you do not reboot the hosts, your VMs will be fine. If it comes up and vCenter is not available it will not be able to get it's host keys to then get the VM keys therefore that particular host cannot access the VMs on storage.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;What happens if 1 KMS is offline Failed?&lt;UL&gt;&lt;LI&gt;It fails over to the next KMS in the list&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;What happens if both KMS are offline/failed?&lt;UL&gt;&lt;LI&gt;Again depends if you reboot the hosts, the keys are stored in the hosts memory and are lost on reboot&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Fri, 08 Sep 2023 16:24:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-Data-at-Rest-Encryption-and-KMS-Failure/m-p/2985878#M15583</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-08T16:24:08Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN Capacity what if scenario</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-Capacity-what-if-scenario/m-p/2985865#M15578</link>
      <description>&lt;P&gt;Are you taking into account your policies are assuming all disks will be thin provisioned?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2023 14:34:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-Capacity-what-if-scenario/m-p/2985865#M15578</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-08T14:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN Data at Rest Encryption and KMS Failure</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-Data-at-Rest-Encryption-and-KMS-Failure/m-p/2985864#M15577</link>
      <description>&lt;P&gt;Here you go&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-monitoring-troubleshooting/GUID-084B3888-499F-4CD0-8954-A149560B1534.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-monitoring-troubleshooting/GUID-084B3888-499F-4CD0-8954-A149560B1534.html&lt;/A&gt;&lt;/P&gt;&lt;P class=""&gt;In an encrypted&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;vSAN&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;cluster, when communication between a host and the KMS is lost, the disk group can become locked if the host reboots. You should be fine until you reboot the hosts&lt;/P&gt;</description>
      <pubDate>Fri, 08 Sep 2023 14:30:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-Data-at-Rest-Encryption-and-KMS-Failure/m-p/2985864#M15577</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-08T14:30:35Z</dc:date>
    </item>
    <item>
      <title>Re: NSX-T REST APIs with Unique Identifier for Security Groups</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-REST-APIs-with-Unique-Identifier-for-Security-Groups/m-p/2985744#M16900</link>
      <description>&lt;P&gt;No problem, I hope it's clear! Group ID must be unique for the security groups but they can all share the same&amp;nbsp;&lt;SPAN&gt;display_name if you wanted. If this has helped you solve your issue please mark as solved.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 15:58:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-REST-APIs-with-Unique-Identifier-for-Security-Groups/m-p/2985744#M16900</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-07T15:58:50Z</dc:date>
    </item>
    <item>
      <title>Re: 2 vCenter ELM and NSX 4.0 Manager Clusters</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/2-vCenter-ELM-and-NSX-4-0-Manager-Clusters/m-p/2985732#M16899</link>
      <description>&lt;P&gt;Yes as long as you connect them to the same transport zones. What you are looking to do is multi-site NSX. It has some limitations so have a read and make sure it's the right fit for you&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-5D7E3D43-6497-4273-99C1-77613C36AD75.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-5D7E3D43-6497-4273-99C1-77613C36AD75.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 15:29:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/2-vCenter-ELM-and-NSX-4-0-Manager-Clusters/m-p/2985732#M16899</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-07T15:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: NSX-T REST APIs with Unique Identifier for Security Groups</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-REST-APIs-with-Unique-Identifier-for-Security-Groups/m-p/2985659#M16895</link>
      <description>&lt;P&gt;The group id is a unique identifier. You can call every group the exact same name but the identifier has to be different. Thats how it's been in my experience.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So for example using the exmaple in the API document&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;PUT https://&amp;lt;policy-mgr&amp;gt;/policy/api/v1/infra/domains/vmc/groups/&lt;STRONG&gt;&lt;EM&gt;webgroup&lt;/EM&gt;&lt;/STRONG&gt; { "expression": [ { "member_type": "VirtualMachine", "value": "webvm", "key": "Tag", "operator": "EQUALS", "resource_type": "Condition" } ], "description": "web group", "display_name": "web group", "_revision":0 }&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;PUT https://&amp;lt;policy-mgr&amp;gt;/policy/api/v1/infra/domains/vmc/groups/&lt;STRONG&gt;webgroup1&lt;/STRONG&gt; { "expression": [ { "member_type": "VirtualMachine", "value": "webvm", "key": "Tag", "operator": "EQUALS", "resource_type": "Condition" } ], "description": "web group", "display_name": "web group", "_revision":0 }&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You need a unique ID for each group you add otherwise it'll overwrite the previous group.&lt;/P&gt;&lt;P&gt;Pretty much every API you query is looking for that ID. Below is the API to add a rule&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;PUT https://&amp;lt;policy-mgr&amp;gt;/policy/api/v1/infra/domains/vmc/security-policies/application-section-1 { "description": "comm map", "display_name": "application-section-1", "category": "Application", "rules": [ { "description": " comm entry", "display_name": "ce-1", "sequence_number": 1, "source_groups": [ "/infra/domains/vmc/groups/&lt;STRONG&gt;webgroup&lt;/STRONG&gt;" ], "destination_groups": [ "/infra/domains/vmc/groups/&lt;STRONG&gt;webgroup1&lt;/STRONG&gt;" ], "services": [ "/infra/services/HTTP", "/infra/services/CIM-HTTP" ], "action": "ALLOW" } ] }&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it wasn't unique you'd never be able to reference it since you wouldn't know what you're calling.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 06:46:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-T-REST-APIs-with-Unique-Identifier-for-Security-Groups/m-p/2985659#M16895</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-07T06:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: How do you go about downrading your license?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-do-you-go-about-downrading-your-license/m-p/2985609#M289973</link>
      <description>&lt;P&gt;Through the vmware licenses portal. Assuming you have your keys with VMware you can move down from 8 to 7 no problems&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/81665" target="_blank"&gt;https://kb.vmware.com/s/article/81665&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 20:49:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-do-you-go-about-downrading-your-license/m-p/2985609#M289973</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-06T20:49:37Z</dc:date>
    </item>
    <item>
      <title>Re: Querying vCenter for VM info using PowerShell - Too slow</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Querying-vCenter-for-VM-info-using-PowerShell-Too-slow/m-p/2985608#M113135</link>
      <description>&lt;P&gt;If you want the code to run faster you're better off making use of the REST APIs rather than PowerCLI and call the APIs you wish to query directly. Get-VM will pull in a lot of irrelevant data.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 20:47:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Querying-vCenter-for-VM-info-using-PowerShell-Too-slow/m-p/2985608#M113135</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-06T20:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Sending logs to a remote syslog server</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Sending-logs-to-a-remote-syslog-server/m-p/2985599#M289972</link>
      <description>&lt;P&gt;Yes, for version 7 it's a little different. Create your own xml file, eg udp1514.xml&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;ConfigRoot&amp;gt;&lt;BR /&gt;&amp;lt;service id='0032'&amp;gt;&lt;BR /&gt;&amp;lt;id&amp;gt;udp1514&amp;lt;/id&amp;gt;&lt;BR /&gt;&amp;lt;rule id = '0000'&amp;gt;&lt;BR /&gt;&amp;lt;direction&amp;gt;outbound&amp;lt;/direction&amp;gt;&lt;BR /&gt;&amp;lt;protocol&amp;gt;udp&amp;lt;/protocol&amp;gt;&lt;BR /&gt;&amp;lt;porttype&amp;gt;dst&amp;lt;/porttype&amp;gt;&lt;BR /&gt;&amp;lt;port&amp;gt;1514&amp;lt;/port&amp;gt;&lt;BR /&gt;&amp;lt;/rule&amp;gt;&lt;BR /&gt;&amp;lt;enabled&amp;gt;true&amp;lt;/enabled&amp;gt;&lt;BR /&gt;&amp;lt;required&amp;gt;false&amp;lt;/required&amp;gt;&lt;BR /&gt;&amp;lt;/service&amp;gt;&lt;BR /&gt;&amp;lt;/ConfigRoot&amp;gt;&lt;/P&gt;&lt;P&gt;Copy it into the&amp;nbsp;&lt;SPAN&gt;/etc/vmware/firewall and issue&amp;nbsp;esxcli network firewall refresh. You won't be able to edit services.xml from version 7.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 19:48:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Sending-logs-to-a-remote-syslog-server/m-p/2985599#M289972</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-06T19:48:31Z</dc:date>
    </item>
    <item>
      <title>Re: Sending logs to a remote syslog server</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Sending-logs-to-a-remote-syslog-server/m-p/2985597#M289970</link>
      <description>&lt;P&gt;Yes it is possible, follow this KB&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/2008226" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/2008226&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You'll create a custom firewall service and allow it outbound on port 1514 UDP. From there configure udp:host01:1514 in your syslog settings and you should be good to go.&lt;/P&gt;&lt;P&gt;There is some additional workarounds at the end of the post on getting it to work with 7 and above.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 19:17:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Sending-logs-to-a-remote-syslog-server/m-p/2985597#M289970</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-06T19:17:57Z</dc:date>
    </item>
    <item>
      <title>Re: multicast dns(MDNS)</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/multicast/m-p/2985593#M16891</link>
      <description>&lt;P&gt;Here you go -&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/nsxt_32_admin.pdf" target="_blank"&gt;https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/nsxt_32_admin.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Have I configured multicast, yes. With NSX, no. The concept of multicast PIM and RP isn't locked down to a specific vendor, my experience with multicast is via Cisco but the concepts are the same.&amp;nbsp;&lt;/P&gt;&lt;P&gt;NSX supports&amp;nbsp;&lt;SPAN&gt;PIM Sparse Mode with IGMPv2 so I would probably configure the t0 (assuming both subnets terminate to the same t0) as a static RP for the traffic. Use that as your target/receiver.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;here is some additional information on sparse mode&amp;nbsp;&lt;A href="https://networklessons.com/multicast/multicast-pim-sparse-mode" target="_blank"&gt;https://networklessons.com/multicast/multicast-pim-sparse-mode&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have implement multicast into production&amp;nbsp;networks, nothing to really note.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 18:36:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/multicast/m-p/2985593#M16891</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-06T18:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: Partition Data Storage on ESXi to be used by any VM on the host at a time</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Partition-Data-Storage-on-ESXi-to-be-used-by-any-VM-on-the-host/m-p/2985586#M289967</link>
      <description>&lt;P&gt;No problem, be sure to mark as accepted solution if you're happy with the answer&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 17:11:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Partition-Data-Storage-on-ESXi-to-be-used-by-any-VM-on-the-host/m-p/2985586#M289967</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-06T17:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to Remove One VCenter from Link mode</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/How-to-Remove-One-VCenter-from-Link-mode/m-p/2985574#M49226</link>
      <description>&lt;P&gt;The KB does cover everything but I agree it's rather confusing and you are expected to know which steps to follow and which to ignore.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/2106736" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/2106736&lt;/A&gt;&lt;/P&gt;&lt;P&gt;William Lam has also done a similar article here -&amp;nbsp;&lt;A href="https://williamlam.com/2017/03/how-to-split-vcenter-servers-configured-in-an-enhanced-linked-mode-elm.html" target="_blank" rel="noopener"&gt;https://williamlam.com/2017/03/how-to-split-vcenter-servers-configured-in-an-enhanced-linked-mode-elm.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Will is a vExpert as well as an employee so as close to an official step by step guide you can get. Best of luck, I've completed similar work like this, the guide given was more than enough to see me through.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 19:05:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/How-to-Remove-One-VCenter-from-Link-mode/m-p/2985574#M49226</guid>
      <dc:creator>bmcb555</dc:creator>
      <dc:date>2023-09-06T19:05:57Z</dc:date>
    </item>
  </channel>
</rss>

