<?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>tantis14 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>tantis14 Tracker</description>
    <pubDate>Fri, 10 Nov 2023 23:03:39 GMT</pubDate>
    <dc:date>2023-11-10T23:03:39Z</dc:date>
    <item>
      <title>HCX L2 extension to cloud with hair pinning at on-prem</title>
      <link>https://communities.vmware.com/t5/HCX-Discussions/HCX-L2-extension-to-cloud-with-hair-pinning-at-on-prem/m-p/2956272#M326</link>
      <description>&lt;OL&gt;&lt;LI&gt;Is it possible to extend VLAN for HCX if customer has hair pinning due to security reasons? If no, what options we have?&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Thu, 23 Feb 2023 14:00:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/HCX-Discussions/HCX-L2-extension-to-cloud-with-hair-pinning-at-on-prem/m-p/2956272#M326</guid>
      <dc:creator>tantis14</dc:creator>
      <dc:date>2023-02-23T14:00:17Z</dc:date>
    </item>
    <item>
      <title>HCX migration-configure proximity routing</title>
      <link>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/HCX-migration-configure-proximity-routing/m-p/1870961#M163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, I am migrating large number of VMs using HCX. appreciate insight with following:&lt;/P&gt;&lt;P&gt;1. How to configure proximity routing at On-Premises and SDDC to keep traffic routing local to VM site&lt;/P&gt;&lt;P&gt;2. Break network extension between on-premise and maintain on-premise vlan in cloud for migrated VMs&lt;/P&gt;&lt;P&gt;3. Enable communication between vLAN in SDDC and migrated VM (on L2Ext network)&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;T&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Sep 2019 06:50:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/HCX-migration-configure-proximity-routing/m-p/1870961#M163</guid>
      <dc:creator>tantis14</dc:creator>
      <dc:date>2019-09-04T06:50:46Z</dc:date>
    </item>
    <item>
      <title>VMC on AWS - access ec2 through migrated VM to sddc</title>
      <link>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/VMC-on-AWS-access-ec2-through-migrated-VM-to-sddc/m-p/2221670#M173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have established connection between vmc on aws sddc to ec2. i am able to access ec2 through new VM i create in SDDC, however, i am unable to access EC2 through HCX migrated VM. , HCX migrated VM still have same IP and gateway as on prem. I have created firewall rule at sddc and aws as well. still no luck. wanted to check, if somebody has tried it earlier and how to establish connectivity between HCX migrated VM and EC2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 May 2019 16:53:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Break-Fix-Technical-Discussions/VMC-on-AWS-access-ec2-through-migrated-VM-to-sddc/m-p/2221670#M173</guid>
      <dc:creator>tantis14</dc:creator>
      <dc:date>2019-05-14T16:53:11Z</dc:date>
    </item>
  </channel>
</rss>

