<?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: article 76022 - 100.64.0.0/10 network address in Cloud Activation, Architecture &amp; Billing Discussions</title>
    <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2853473#M133</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;As Rick and I explained you, these CIDR should not have been uses as it will create conflict with internal routing within VMC between routers for management purposes.&lt;BR /&gt;So, please use another subnet to avoid any conflict that won't be supported or solved by our tech support team in case of issue.&lt;BR /&gt;&lt;BR /&gt;Hope this helps anyway&lt;BR /&gt;&lt;BR /&gt;Emmanuel&lt;/P&gt;</description>
    <pubDate>Fri, 18 Jun 2021 13:27:37 GMT</pubDate>
    <dc:creator>ebernard</dc:creator>
    <dc:date>2021-06-18T13:27:37Z</dc:date>
    <item>
      <title>article 76022 - 100.64.0.0/10 network address</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850042#M120</link>
      <description>&lt;P&gt;Regarding this article #76022 need some clarification&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;[VMC on AWS ] Routed network may stop working if 100.64.0.0/10 network address is used as on-prem endpoint device address (76022)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;Question:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1) Dedicated network connection from our DC premises to AWS via Direct Connect. The service&lt;/SPAN&gt;&lt;FONT face="arial,helvetica,sans-serif" size="3"&gt;&amp;nbsp;provider is not using CGNAT IP segment 100.64.0.0/10 in their network address. In such a scenario, Is there any IP conflict? when&amp;nbsp;&lt;/FONT&gt;&lt;FONT size="3"&gt;on-prem endpoint devices (VMware)using 100.64.x.x/10 IP address.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;2)Is there any issues, If we assign Private Ip address 100.64.x.x /10 to VMware endpoints for the above scenario.&lt;/P&gt;&lt;P&gt;plz advice.&lt;/P&gt;</description>
      <pubDate>Mon, 31 May 2021 13:15:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850042#M120</guid>
      <dc:creator>Nothing_NO</dc:creator>
      <dc:date>2021-05-31T13:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: article 76022 - 100.64.0.0/10 network address</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850053#M121</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;Just to be sure, let me just repeat it differently?&lt;BR /&gt;You're using this 100.64.0.0/10 network in your on premises environment and plan to reach it from your VMs located in VMware Cloud on AWS, right?&lt;/P&gt;
&lt;P&gt;If so, you need to read this KB explaining it in details:&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/76022" target="_blank"&gt;https://kb.vmware.com/s/article/76022&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;You will see at the end that resolutions are:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Do not use the IP range - (100.64.0.0–100.127.255.255) addresses. They are always meant to be intermediary relay hops that are internal to the carrier networks.&lt;/LI&gt;
&lt;LI&gt;VMC uses the same network and specification to implement CGN style networking between the VMC Edge routers in internal routing components which can create a conflict.&lt;/LI&gt;
&lt;LI&gt;SDDCs that were created using version 1.10 or later have a smaller allocation of 100.64.0.0/16 instead of the entire 100.64.0.0/10 block. Address space other than the 100.64.0.0/16 block can be used for endpoints.&lt;/LI&gt;
&lt;LI&gt;SDDCs that were upgraded from releases prior to 1.10 do not reflect this change and will continue to have the 100.64.0.0/10 allocation present.&lt;/LI&gt;
&lt;LI&gt;VMC also uses this IP range between internal routing components it will create a conflict.&lt;/LI&gt;
&lt;LI&gt;If a packet with either a source or a destination address in the 100.64 address space that conflicts with overlapping address space internal to the SDDC, it will be delivered inside the edge and will never egress.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that helps and looking forward to read your comments&lt;BR /&gt;Cheers&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 May 2021 13:36:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850053#M121</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-05-31T13:36:35Z</dc:date>
    </item>
    <item>
      <title>Re: article 76022 - 100.64.0.0/10 network address</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850058#M122</link>
      <description>&lt;P&gt;Hello Nothing_NO and thank you for your question.&lt;/P&gt;
&lt;P&gt;As stated in the KB: "VMC also uses this IP range between internal routing components it will create a conflict."&lt;/P&gt;
&lt;P&gt;You "may get lucky" with not matching/overlapping IPs, however, as also stated: "If a packet with either a source or a destination address in the 100.64 address space that conflicts with overlapping address space internal to the SDDC, it will be delivered inside the edge and will never egress."&lt;/P&gt;
&lt;P&gt;You can also see some more Info here:&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking-security/GUID-658253DB-F384-4040-94B2-DF2AC3C9D396.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking-security/GUID-658253DB-F384-4040-94B2-DF2AC3C9D396.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;With that being said, it is highly recommended to NOT use this CIDR.&amp;nbsp;&lt;BR /&gt;If - for whatever reason - your Networking design does not allow to not use this Network, I'd highly recommend to get in touch with your specialists to discuss this in detail.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Be well &amp;amp; stay safe,&lt;/P&gt;
&lt;P&gt;Rick&lt;/P&gt;</description>
      <pubDate>Mon, 31 May 2021 13:43:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850058#M122</guid>
      <dc:creator>Rick_Star</dc:creator>
      <dc:date>2021-05-31T13:43:15Z</dc:date>
    </item>
    <item>
      <title>Re: article 76022 - 100.64.0.0/10 network address</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850104#M123</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Bernard,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;Thanks for your reply.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;We are using this 100.64.0.0/10 network in our AWS cloud.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 May 2021 16:14:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850104#M123</guid>
      <dc:creator>Nothing_NO</dc:creator>
      <dc:date>2021-05-31T16:14:09Z</dc:date>
    </item>
    <item>
      <title>Re: article 76022 - 100.64.0.0/10 network address</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850113#M124</link>
      <description>&lt;P&gt;Hi Rick,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Thanks for your reply. I'm new to VMware cloud.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Regarding the below KB, Could you explain in more detail?&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;&lt;SPAN&gt;As stated in the KB: "VMC also uses this IP range between internal routing components it will create a conflict."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; Inside my subscription, If my network (100.64.x) segment needs to communicate outside (internet) or AWS backbone it should be NAtted using public ip.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; In such a case how the internal routing components will create conflict.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 31 May 2021 16:24:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2850113#M124</guid>
      <dc:creator>Nothing_NO</dc:creator>
      <dc:date>2021-05-31T16:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: article 76022 - 100.64.0.0/10 network address</title>
      <link>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2853473#M133</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;As Rick and I explained you, these CIDR should not have been uses as it will create conflict with internal routing within VMC between routers for management purposes.&lt;BR /&gt;So, please use another subnet to avoid any conflict that won't be supported or solved by our tech support team in case of issue.&lt;BR /&gt;&lt;BR /&gt;Hope this helps anyway&lt;BR /&gt;&lt;BR /&gt;Emmanuel&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jun 2021 13:27:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Cloud-Activation-Architecture/article-76022-100-64-0-0-10-network-address/m-p/2853473#M133</guid>
      <dc:creator>ebernard</dc:creator>
      <dc:date>2021-06-18T13:27:37Z</dc:date>
    </item>
  </channel>
</rss>

